OS 3.9 installation problems.
 

I have an A4000 with A3640, 3.1 ROMS and OS3.1 set up on 4GB CF under WinUAE. I created emergency boot disk, which went ok. When I booted with the disk, I got a 80000004 guru about my games partition. I set the max_transfer value to 0x01fee. No help. Booted from HD and did the installation from CD. Installation went ok but when I tried to boot to 3.9, I got the same guru. Formatted the partitions and did a fresh install of 3.1 from floppies. Now back to emergency disk boot with a result that I get an infinite busy pointer.

Any help is appreciated.

Use WinUAE to install 3.9. Install Boingbag 1 before you try it in your A4000 for the first time.

This should be 0x1fe00. Everything else does not make sense.

Sorry, was typing it from the back of my head. It is 0x1fe00.

I'll try the installation in UAE next.

I now got the OS3.9 with boingbags installed in WinUAE, thanks to your giude, Thomas!
It also loads in A4000. There is one thing, though. The uaescsi.device haunts me during bootup by cachecdfs complaining that it can't find the uaescsi.device. I checked devs/dosdrivers for CD0 properties but CD0 wasn't there, or at least it didn't have an icon. Where can I find, where cachecdfs is referring to uaescsi.device?

It's called EMERGENCY_CD. You can rename it to CD0 if you like. Then load it into a text editor and change DEVICE= and UNIT= to your needs.

Ok, thanks!

I also get a random 80000004 guru. By googling I found that it is related to hard drive. Should I try to modify the max_transfer value even more down?

I don't think so. 80000004 is a CPU exception: illegal instruction.


MaxTransfer causes file corruption, not CPU crashes.

Crashes can be caused by bad power supply (therefore HDD related if the HDD draws too much power), bad RAM, battery acid leaking to the motherboard, loose contacts between parts, for example between the CPU module and the motherboard, or overheating.

Crashes can also be caused by bad software of by a bad combination of good software.

Did you partition the CF card after booting from the emergency disk, i.e. did you use the new FastFileSystem? Mixing different versions of the file system might be a cause for crashes, too.

You might also try to revert 68040.library to the version which comes with WB 3.1.

Didn't partition it from emergency disk.

It seems that I'm going to have to restore my install from the backup hdf that I made so I can first partition the hd again from emergency disk and then copy the contents from the backup.

No need to partition again. Just replace old FastFileSystem in HDToolbox by new one (in Add/Update dialogue).