»

[k4lmp]

Anyone have any ideas why I can run AmigaOS 3.9 on my A2000 (details in sig.), but if I try to boot ClassicWB 3.9, it doesn't work? I noticed with WinUAE setup the same as my A2000, it does the same thing, however, if I set it up as an AGA 1200, it boots fine. Since WinUAE does the same thing, I don't think it is a hardware problem, just maybe the ClassicWB trying to load something my A2000 won't do. Does it add something to regular AmigaOS 3.9 that my A2000 won't run? Like I said, it runs regular 3.9 fine.

Thanks,
Jeff

[nyteschayde]

Totally guessing, but perhaps it's a ROM update specific to the A1200? Or perhaps it's something else. I was thinking about writing a showexecute CLI command that basically would write out the line it's going to execute before executing it. It would help trouble shoot issues like these. It could also log a file to a RAD drive or something or any non-FFS drive; wouldn't want it to crash during a write and invalidate the disk; I swear FFS likes to invalidate itself if you just look at it funny.

[Darrin]

I have it running fine on my A2000.

From memory, set it up on WinUAE (configure UAE as best you can to match the specs of your A2000 - CPU, chipset, etc before you do the install), make sure you set your screenmode in prefs to something your A2000 and monitor can display (very important)!, copy the files over to your A2000's media (hard drive, CF card, etc), plug the media into your A2000 and boot.

[mfilos]

ClassicWB 3.9 has by default Copper enabled!
Since Copper is an AGA related program, you should disabled it prior using it on your A2000.
One quick method without using WinUAE is by booting without Startup-Sequence using the Early Startup Menu and on command prompt issue:

1> cd C
1> execute Copper_disable

Just to be safe, you can disable a lot of components using the menu made by Bloodwych like Copper, StackAttack, BorderBlank, CyberBugFix, Fblit/Ftext, BlazeWCP, IconBeFast etc and then enable one at a time once your system boots succesfully