Help: Using FastAta1200 with Blizkick

[Ancalimon]

I have a Blizzard 1260

I'm trying to setup Blizkick for a single reboot system with AmigaOS3.9

The first command in Startup-Sequence is ATA.Driver QUIET  (there's also a stack 8192 line but I have no idea why it's added there. It comes after ATA3.Driver. Shouldn't it be before Ata3.Driver?)

My blizkick command line comes after ATA3.Driver.

I've also edited the Setpatch command with NOROMUPDATE argument so that it does not update anything and reboot the system.

The problem is this: Ata.Driver reboots the system once, Blizkick reboots the system a second time (adding some modules and also the updated things that I splitted from AmigaOS ROM Update file and updated from Boingbad3 and BoingBag4) and than I get another reboot. What am I doing wrong?

Should I add Ata3.Driver after Blizkick since I guess Blizkick removes Ata3.Driver from memory?

More than 10 years ago when I was using an older version of Ata3.Driver, I remember that I only needed one reboot when I used Ata3.Driver with Blizkick.

[Ancalimon]

Elbox does not have FastAta1200 MK4 on their webpage.  They only have MK3.  Who is making this MKIV and its updated files that I bought from AmigaKit?

I just tried to change the command:

ATA3.driver QUIET RESIDENT

to

ATA3.driver QUIET

and now I don't get three reboots but just one reboot. But my drives don't show up that way. I have to reboot once again by hand so that the drives show up.


bbond007:  I only have a 060 too (what more can you have! ) and OS3.9 runs perfect here. You should too.

[Ancalimon]

The FastATA driver patch the scsi.device : so you must put 'ATA3.driver Quiet' after BlizKick !

So I have to make FastATA.driver reboot the machine once again after Blizkick installs the OS3.9 ROM Updates, some modules and reboots the machine??

Is blizkick writing over something which fastata.driver writes to memory?

bbond007: Apart from the cold reboot during which some files inside the 3.1 ROM are updated, my boot time is 5 seconds using AmigaOS3.9 . It's been so long since I used 3.1 I don't remember how it was. (I also have a 060-50)

AmigaOS3.9 setpatch causes another reboot if you don't use blizkick. By using blizkick I have only one reboot. (when I didn't have this FastAta1200)


....

I will try using ata3.driver as a module with blizkick. I hope it works.

[Ancalimon]

Tried ata3.driver as a module inside Blizkick but won't boot from hdd. HDD light turns on and machine freezes. On the boot menu I see many different partions.

[Ancalimon]

Who is making this MK4 version FastATA1200 ?  The latest I can find at Elbox page is MK3.

[Ancalimon]

On my setup, FastATA don't reboot the machine here...

How's that possible?  When it doesn't reboot the machine once, I don't get most of the partions that are after the 4gb barrier on my hdd.

I had to add the ata3.driver quiet resident command after Blizkick to have all of my partions. If I don't add the resident argument, I don't get a second reboot caused by ata3.driver but then I don't get my partions.

I don't know, but it is different hardware. I think someone tried my driver with the FastATA III and reported back it did not work.

I guess only the MACH chip is a more recent one.