Install 3.2 on A3000 crashes

[Thomas]

What does "8 or 12" mean? How do you switch?

Which CPU does the machine have?

What error does the Guru show? The 8-digit code before the dot indicates the reason.

How did you create the SuperKickstart disk for 47.111?

Does it work differently if you load Kickstart 3.1 and then boot from the Modules disk? Or from the Install disk?

How is your harddrive partitioned (harddrive size, partition sizes)? Which file system (Version and flavour)?

[Thomas]

When the superkickstart loads, before the floppy prompt appears, hold down both mouse buttons to enter the early startup menu. In the menu go to Boot options, set the check mark for Trace Startup-Sequence, then click Ok until you are back at the main page and click Boot. Now you have to confirm each command of the startup-sequence. Which one crashes?

[Thomas]

Please run this program and attach the report here: http://thomas-rapp.homepage.t-online.de/downloads/hddreport.lha

[Thomas]

Would be better to see the report with SuperKick 3.2 active. But that's ok, too. I see nothing unusal in the report.

But I have a suspicion: Kick 3.2 requires workbench.library on disk. It searches all disks for a usable workbench.library. Probably it tries the AROS partition before it looks at the floppy disk. So it tries to load workbench.library from AROS, but this is not compatible to Kick 3.2 and crashes.

If you disable the AROS partition you can boot 3.2 normally (you can disable it permanently by unchecking automount in HDToolbox). The problem probably disappears once you install 3.2 on the WB_2.x partition because then it finds workbench.library there before it looks at the AROS partition.