problems installing os 3.9

[digiflip]

when fully installed and reboots

i get this error



software error 8000 0008 task 68015040

stays in loop

the reboot kick thing is working off emergency flopppy but not when fully installed

i am using ide fix on floppy to boot of cdrom

[digiflip]

using a blizzard 1230 iv 50mhz 68030 and 64 mb ram

[digiflip]

tried installing amiga sys and upgrading to amiga os 3.9 too and get same error. Trying classic wb os 3.9 version see if this works.

[foleyjo]

put some echo in your startup-sequence
ie
echo 1
echo 2

then you can see how far through the startup it gets before it resets.
Might give an idea of where the problem is

[digiflip]

not sure how echo things will work since its when the it load romupdate.rom when get error

[digiflip]

think its ide fix what was causing problems, ie when was installing via emergency disc, the screen kept getting nag screen from ide fix

installed after installing classic wb adv sp.
 installed fine now

[digiflip]

trying again today with classic wb os 3.9 version loads fine in winuae but when installed on real amiga get red software error when boots from os 3.9 soft kick rom i think.

[doctorq]

Try adding NOROMUPDATE to the SetPatch line. This way you can see if the problem is because of the ROM update or not. If it is, you will have to enable the ROM update again and then leave out specific updates by adding for instance SKIPROMMODULES "scsi.device" to the SetPatch line instead.

You can see which updates there are in the ROM update by splitting it with romupdatesplit from the BlizKick package.

[digiflip]

not sure how i can do that know seems to stay in loop and not boot off floppy now lol,

think going to take day off from amiga tomorrow and complete my hackingtosh since I got a gigabyte motherboard

[paul1981]

not sure how i can do that know seems to stay in loop and not boot off floppy now lol,

think going to take day off from amiga tomorrow and complete my hackingtosh since I got a gigabyte motherboard

Turn the power brick off and on again, and boot with no startup-sequence, or from a floppy.

[digiflip]

thanks paul i might try that.

maybe i should try putting the update rom in blizkick thing and jumper it on my blizzard.

any1 have a guide on how to make the 3.9 custom rom for bliz kick?

[digiflip]

came across this problem again whilst reinstalling os 3.9 with smart file system, the error meant first partition was larger than 4 gb, made partition under 4gb and booted fine, now on with ami kit install and reinstall of whdload

[rvo_nl]

well, that is obvious boot partition should be below 4gb. after 3.9 rom is active, partitions larger than 4gb are visible and usable. glad you solved it.

[Oldsmobile_Mike]

Personally I recommend keeping boot partition under 500MB and as the first partition on the drive.  Best way to avoid compatibility issues with any other programs.