Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Amigaean on October 15, 2003, 10:06:13 PM
-
I've just upgraded my A500 to Kickstart 3.1 and am trying to install OS3.5 over the top of OS2.
I have a Dataflyer 500 SCSI disk. The OS install disk won't let me re-format the hard disk - it doesn't detect it.
It allows me to install to the existing partition, there's lots of disk activity but when it reboots it just prompts me to enter the workbench disk - it doesn't detect the hard disk any longer.
Any one got any experience of this? Any ideas how I fix it? I guess it's 'cos the OS3.5 installer trashes the drivers for the Dataflyer or because the drivers are not compatible with OS3.5 (they obviously work with kickstart 3, 'cos I can still boot OS2 before I start).
Cheers
-
I may be wrong here, but at least with OS3.9, 68020 CPU is required for installation. It very well could be the reason of your problem.
-
You'll also need 6Mb+ of Fast RAM.
-
My mistake - I've got Amiga OS 3.1 (should have guessed 'cos it's a set of six floppy disks).
I think that it's not booting from hard disk because the install has removed some of the files used by setautoboot - e.g. the device ID file).
I'll restore the hard disk back to the OS 2.04 image and backup the whole OS onto another 'partition' (it's split into DH0: and DH1:), re-install OS3.1 then copy the files that I think are needed back to OS3.1 before I let it reboot.
-
My mistake - I've got Amiga OS 3.1 (should have guessed 'cos it's a set of six floppy disks).
I think that it's not booting from hard disk because the install has removed some of the files used by setautoboot - e.g. the device ID file).
I'll restore the hard disk back to the OS 2.04 image and backup the whole OS onto another 'partition' (it's split into DH0: and DH1:), re-install OS3.1 then copy the files that I think are needed back to OS3.1 before I let it reboot.
-
think that it's not booting from hard disk because the install has removed some of the files used by setautoboot - e.g. the device ID file).
This doesn't "compute". If it can't find the harddrive it can't find the files either even if they are there.
Maybe you should try and check everything with HD-toolbox (run hdtoolbox from a shell with the device as an argument) and check if the boot-flag for the partition is there. Maybe you need to install a never version of the filesystem as well.
3.1 should have no problem running on a 500, and I cant see why the Dataflyer wouldn't work either.
I for one would try to reinstall everything from scratch with the 3.1 install-disk. If you have everything on backup I see no risk in doing that.
But you need to call the device for the harddrive-controller manually when you start up HD-Toolbox.
Is there a switch on the controller where you can turn autoboot on and off? I know that my old GVP-controller had that. That wouldn't explain why it works with the old install though...
Well, these are the things I can think of.
-
I did install 3.1 from scratch. It had no problems writing itself to disk. It just didn't start again afterwards!
I couldn't get the HD Toolbox to work. It didn't detect my hard disk. I'm interested by your statement ;you need to call the device for the harddrive-controller manually'. How do you do that?
The solution that I'm looking at is putting the required files for running SetAutoBoot from the Installation disk. There are a couple of executables and l:autoboot.codes and maybe some more. Having installed 3.1 I can then run this before re-booting. I guess that it writes something to the HD (boot record?) so that the hard drive controller's boot ROM detects it.
-
To get HDToolBox to work with the DataFlyer 500 you need to add (or change) the SCSI_DEVICE_NAME tooltype to:
SCSI_DEVICE_NAME=ExpSys.device
The default, if present, should say something like SCSI_DEVICE_NAME=scsi.device.
-
I believe you can just run:
1> setautoboot dh0:
from your DataFlyer disk, and "re-bless" your hard drive so that the Amiga can detect it properly.
You may need to only use a standard filesystem, like the Amiga FFS. I never ran 3.1 on an A500, but I remember having to do this on my 1.3/2.1 dual-boot A500 with DataFlyer.
-
Thanks Ilwrath, you confirmed what I thought!
Restored the disk back to OS 2.04 and copied the file I'd missed (l/autoboot.code) to my hacked OS3.1 install disk. Re-installed OS3.1 then ran SetAutoBoot to re-bless the disk.
Worked a dream!