strange boot problem, setpatch

[orange]

I have a very strange boot problem slightly connected to setpatch. The system: A2000, SCSI HDD 9Gb (sys: 1Gb, work: 8Gb, PFS3ds) on Oktagon (v6.12), Apollo2030 with disabled SCSI, Picasso II. OS3.9, no boing bags.

HDD never starts from early startup menu (with or without startupsequence). Partitions can be seen there, though.

But on cold and warm boot HDD start normally. The problem is that after reboot from setpach command, HDD doesn't start and I need to do a warm reset. its annoying  :-(
If I remove setpatch command from startup, it boots, but thats probably not a good solution.

So, is there a(ny) way to run setpatch without reset?
(manual resets work fine)
Could it be related to ApolloSCSI?


PS. with setpatch, check4gb gives me: * N S
without it it does:  * S
on 7Gb partition

[Thomas]

So, is there a(ny) way to run setpatch without reset?

Install Boingbag 1, it should fix this.

If it doesn't, change the SetPatch line in Startup-Sequence to read

SetPatch QUIET SKIPROMUPDATES "scsi.device"

If it still does not work, delete the file "AmigaOS ROM Update" from Devs.

check4gb gives me: * N S
without it it does: * S

This just means that you didn't install PFS3ds properly. Check4GB thinks it is PFS3. PFS3's identifier should be 0x50465302 and for PFS3ds it should be 0x50445302. You used the former for PFS3ds. But it does not matter, if you are sure you used PFS3ds, then everything is ok.

Bye,
Thomas

[doctorq]

If it doesn't, change the SetPatch line in Startup-Sequence to read

SetPatch QUIET SKIPROMUPDATES "scsi.device"

Alternatively

SetPatch NOROMUPDATE QUIET

Just in case you want to play around with the ROM update later on.

[orange]

Ok, did what Thomas said.
1) installed BB1,  the same problem
2) SKIPROM...,  the same problem
3) removed "..ROM update" file,  works excellent, boots from power on, doesn't even restart  but something tells me there must be some catch?

you were right about PFS, too.. Just used 'PDS3' in hdinsttools (because hdtoolbox wouldn't find drive) and check4gb said OK.

so, a big thank you Thomas.

just a small offtopic question about PFS, is it better to use the same (directscsi) version on all partitions (even sys:) or to use different versions?

[doctorq]

3) removed "..ROM update" file,  works excellent, boots from power on, doesn't even restart  but something tells me there must be some catch?

Of course, you are currently using a OS3.1 based system with updated libraries, etc, since you aren't updating the ROM by using the ROM update.

[motorollin]

I used to have this problem with my A1200. When I booted from my SCSI hard drive on 1230scsi.device, the machine would boot from the drive once, then reboot due to setpatch, then it wouldn't boot again. As a workaround, I connected an IDE hard drive (non-bootable, but formatted) to the internal IDE interface and it worked.

Eventually I burned my own 3.9 ROM chips so I no longer need the setpatch ROM update. This means I can cold boot from the SCSI drive without anything connected to the IDE interface.

I don't know if this will really help you though, as I don't think the A2000 has an on board IDE interface does it?

--
moto