The advantage of 2.06 is that you can boot from hard disk having installed drivers, whereas with 1.04 you need to boot from a floppy containing the hard disk drivers. Actually, that's not true. TOS 1.04 (even TOS 1.00) can boot from an ACSI hard disk just fine. No floppy disk required. (TOS 2.06 ad...

TOS ROMs missing. IMP DMA. High-res pictures in ZIP file.

hmm ok, so more work is needed for monster then... don't get it.. The link to EmuTOS that I posted shows how Monster wants to be initialized before you can call Maddalt. If it's unclear: Is Jo Even Skarstein (joska) a member of your forum? He coded that and could surely explain what needs to be don...

Like I said above: If you're not running the Monster alt-RAM "driver", you cannot simply use Maddalt. You have to do what the driver does: enable Monster alt-RAM first.

I still don't understand what you want to do. I took out the # as devpack docs said it was floating point stuff so I stopped using it.. This has nothing to do with floating point. In 68k assembler syntax, a "#" simply denotes an immediate value. For sure, there must be good 68k ASM tutorials out the...

Without really understand what you're trying to achieve in the first place, I notice the following things: - No Maddalt does not take its arguments in kilobytes. (And $4000 wouldn't be 4000 kilobytes, anyway.) - You're again missing the "#". MOVE.L $4000,D0 does not move the number $4000 into D0, it...

OK, so the assembler needs a FPU on the development machine to handle floating point constants. WTF! They could have easily done that entirely in software. I know why I don't like Devpac much. The particular line... FMOVE.S #1.001,FP0 ... compiles fine under Hatari with 68030 + FPU, if I use the 680...

What is the statement in line 423, then?

EDIT: Also I wonder if the combination of 68040/68881 is even allowed in Devpac, considering that the 68040 has a builtin FPU.

Not that I have much experience with Devpac, but the syntax of the OPT P line should be different according to the manual:

https://www.xilinx.com/support/documentation/customer_notices/xcn15006.pdf Unless there's a document superseding this one, they've not been manufacturing them since the start of 2016. So stocks will definitely be dwindling. "The purpose of this notification is to communicate that Xilinx is disconti...