OK, who stole my updated scsi.device?

[Karlos]

A strange thing happened today.

I was writing a file to a partition that spans the 8GB boundary of my main A1200's hard disk and got "Error 45".

The fact that the partition was on that boundary piqued my curiosity. When I checked the version of my scsi.device, it was 40.12 from way back when.

I haven't seen a version that old since before I installed OS3.5 :-o

The thing is, I'm currently using OS3.9 bb2 on the machine in question. I don't recall it ever failing to load the updated ROM modules before. Now, I do know that the old scsi.device just can't go past 8GB and that's one of the reasons I went for OS3.5 (and subsequently 3.9) in the first place.

Anybody know why it's failing to load? I checked the startup-sequence and none of the clauses that usually cause setpatch to skip scsi.device updates seem to be true.

The HD is >8GB and attached via the motherboard. Remaining machine specs are:

A1200 with KS3.1 roms,
CPU: 68040@25MHz / 603e @ 240MHz (BPPC)
RAM: 256MB 60ns.
GFX: BVision

[Karlos]

Very strange. Are your other updated modules working (Workbench->About should show 3.9 ROM and v45)?

It gets stranger. I've booted OS3.5 from cold now and it has no issues. I then warm rebooted into 3.9bb2 which now works but is using the already installed 3.5 rom updates.

If I cold boot 3.9bb2, no rom updates are loaded. It's pretty bizzare.

[Karlos]

My OS3.5 installation has the following rom update file in DEVS:

AmigaOS ROM Update
102000 bytes, version 44.6 (21/12/1999)

My OS3.9bb2 installation has the following rom update files in DEVS:

AmigaOS ROM Update.old
127956 bytes, version 44.26 (17/09/2000)

AmigaOS ROM Update.BB39-2
321768 bytes, version 44.57 (25/02/2002)

AmigaOS ROM Update
321768 bytes, version 44.57 (25/02/2002)


Not entirely sure why I have 2 copies there but I am assuming that the only one that would be used is the one labelled  "AmigaOS ROM Update" in any event.

[Karlos]

Hm, looks like you have the nsdpatch.cfg (or some other file) from 3.5, instead of the 3.9 one.

That'd be odd, since 39 was installed on a clean partition. I wonder if it's been overwritten? You can do strange things when you are half asleep.

[Karlos]

I guess everthing worked before. Changed something recently ?!

It did. A few weeks ago, I recall restoring some system files from a backup. I wonder if I got the wrong ones?

For all I know, this particular problem could have been waiting since then