FastATA MK4 and OS3.9 NsdPatch

[ancalimon]

Is setpatch supposed to mount my partions above 4gb limit after ata3.driver is loaded? (I wonder if the problems I am having are related to this)

I am using Blickick after "ata3.driver quiet" command which loads my patched modules from Amigaosromupdate file.

Should I put # in front of scsi.device entries inside NsdPatch.cfg file since I am using FastATA adapter?

[daxb]

I would check FastATA doc about this. Normaly you should start blizkick first, then ata3.driver and then SetPatch without scsi.device update because ata3.driver build his own scsi.device version that is in use.

[ancalimon]

Originally Posted by daxb

I would check FastATA doc about this. Normaly you should start blizkick first, then ata3.driver and then SetPatch without scsi.device update because ata3.driver build his own scsi.device version that is in use.

Why should blizkick be started before ata3.driver?

[thomas]

Because Blizkick removes everything else from memory. Everything run before Blizkick is unnecessary overhead.

[ancalimon]

Originally Posted by thomas

Because Blizkick removes everything else from memory. Everything run before Blizkick is unnecessary overhead.

Just checked and it seems like version of scsi.device is 44.2.

So I guess I will have to live with the command ata3.driver resident quiet (and a second reboot) which comes after blizkick...

I hope nothing serious is lost because of me writing on the partions above 4gb.

[thomas]

Without ata3.driver you should see scsi.device 40.x, otherwise your SetPatch command is not correct (see daxb's post).
With ata3.driver you should see version 60 or higher.

You could try something like this:

ata3.driver quiet
diskchange dh1:
diskchange dh2:
diskchange dh3:

With IDEfix it works like this. So you can avoid an additional reboot. Perhaps it works with ata3.driver, too.

[daxb]

You can do it like Thomas wrote to avoid a second reboot. I do it similar with my FastATA MK1 except I do after ata3.driver:

DH2: <>NIL:
DH3: <>NIL:
[...]

to activate partitions that aren`t automatically. A "diskchange dh1:" should have the same effect.

[thomas]

Entering just DH2: as a command implicitly executes a CD command which means it really changes the current directory. This means the rest of the script works differently than without this command. I would not use this. DiskChange just accesses the given drive without any impact on the current process.

[daxb]

It is a script lauched from S-S. So that doesn`t affect S-S startup (I guess). We already discussed (years ago) diskchange vs. DHx:. Can`t remember the results.

[ancalimon]

Originally Posted by thomas

Without ata3.driver you should see scsi.device 40.x, otherwise your SetPatch command is not correct (see daxb's post).
With ata3.driver you should see version 60 or higher.

You could try something like this:

ata3.driver quiet
diskchange dh1:
diskchange dh2:
diskchange dh3:

With IDEfix it works like this. So you can avoid an additional reboot. Perhaps it works with ata3.driver, too.

I think without a reboot, version scsi.device still reports old scsi.device. So in any case I have to reboot for the v60 scsi.device to become active.