English Amiga Board - View Single Post

roy bates · 03 June 2012, 15:20

when you run the ata3.driver from shell has the system already booted?

are you trying to run the ata3.driver from the early startup?if so i think your not ment to run it this way hense the reason it has to be at top of the startup sequence.

if your worried that overclocking your accelorator may make these not work,mine is a apollo 1260@100mhz

edit:ive just noticed your softkicking 3.1 what kickstart is in your amiga ? is it version 3.0 if your softkicking can you make sure its after the ata3.driver.

the reason im saying make sure the driver for this is at the top of the ss is because it patches the scsi.device as the machine boots the drive anything above and before it will probably make it crash anyway because of the way it works,like softkicking before this driver will crash your system.

03 June 2012, 15:20	#15
roy bates Registered User Join Date: Apr 2011 Location: birmingham Age: 55 Posts: 2,827	when you run the ata3.driver from shell has the system already booted? are you trying to run the ata3.driver from the early startup?if so i think your not ment to run it this way hense the reason it has to be at top of the startup sequence. if your worried that overclocking your accelorator may make these not work,mine is a apollo 1260@100mhz edit:ive just noticed your softkicking 3.1 what kickstart is in your amiga ? is it version 3.0 if your softkicking can you make sure its after the ata3.driver. the reason im saying make sure the driver for this is at the top of the ss is because it patches the scsi.device as the machine boots the drive anything above and before it will probably make it crash anyway because of the way it works,like softkicking before this driver will crash your system. Last edited by roy bates; 03 June 2012 at 15:39.