OS crash on real Amiga, but works fine on WinUAE

[mindprober]

Well, I wasn't expecting it to be totally smooth...

I completed a ClassicWB OS 3.9 install under WinUAE 3.3.0 per the instructions. I already had experience with the OS 3.1 version of ClassicWB and also installing OS 3.9 on a real Amiga 3000 years back so were no problems prepping or completing the install.

The system boots fine under WinUAE. I transferred the contents of the WinUAE "System" to a 1GB partition I created on a newly acquired SanDisk 16GB CF card. I didn't bother making other partitions because I knew I would need something better than 3.1 to create partitions larger than 4GB. I was sure to change the MaxTransfer setting when I originally prepared the partition.

After moving the compact flash over to my Amiga 1200, I get a GURU error on boot. The WinUAE environment was NTSC based even though a PAL HiRes Laced screenmode is used. It does not get that far into the boot sequence though. I am almost inclined to believe it has something to do with the CF media. The CF adapter is a pretty generic one. No ribbon cable. I can boot to the Kickstart boot menu just fine.

Any ideas on what I should look at first?

[mindprober]

More things to note:

1) I also have KS 3.1 ROMs installed.  

2) I simplified things a little by only including the PAL and NTSC monitor drivers. I originally had a lot more in there.

3) The system does not GURU when I boot with my ACA 1232 accelerator removed. However, I just see a black screen and no other activity.

4) I can boot from my WB 3.1 floppy and see the System partition on other desktop icons from the OS 3.9 install and access the data on the CF just fine.

5) My ClassicWB 3.1 (LITE) system I installed on a 4GB CF for my A500 boots fine in the A1200 with or without the accelerator.

Seems like there is something about the installed OS 3.9 the real Amiga 1200 does not like. Maybe I will try putting a plain vanilla OS 3.9 w/BB2 on another CF see how it likes that.

I wonder if I need to be using ACATune? The A500/OS 3.1 system did not need it but then it was being used with an ACA500 which did its own thing with Kickstarts.

[mindprober]

This is it:

http://eab.abime.net/showthread.php?p=1105821#post1105821