jackson312
New member
When you format them you can rename them, but if you change them in the HDtoolbox, bad things can happen.
I discovered by trial and error it likes to name things like davideo said. Seagate drives are usually start with an "S", but I did try an old Seagate drive (with Commodore stamp). It wanted just to put "HD0", "HD1", ...
I managed to get the machine up with a 36 Gig SCSI (Seagate Cheeta). It is attached directly to Warp Engine. I have the cable running under the metal bridge. When I get the bracket, I will be able to connect the external CDROM using that. For now I am using an A2091
---------- Post added at 23:27 ---------- Previous post was at 23:24 ----------
I had a quick question. The system won't come up unless there is a CD in the CDROM drive.
I was able to get rid of the dependency on the EMERGENCY-CDROM by moving it out of the Devs/DosDrivers, but the system still wants something in the drive, or it won't boot.
Any suggestions on which "extras" are the most useful?
I discovered by trial and error it likes to name things like davideo said. Seagate drives are usually start with an "S", but I did try an old Seagate drive (with Commodore stamp). It wanted just to put "HD0", "HD1", ...
I managed to get the machine up with a 36 Gig SCSI (Seagate Cheeta). It is attached directly to Warp Engine. I have the cable running under the metal bridge. When I get the bracket, I will be able to connect the external CDROM using that. For now I am using an A2091
---------- Post added at 23:27 ---------- Previous post was at 23:24 ----------
I had a quick question. The system won't come up unless there is a CD in the CDROM drive.
I was able to get rid of the dependency on the EMERGENCY-CDROM by moving it out of the Devs/DosDrivers, but the system still wants something in the drive, or it won't boot.
Any suggestions on which "extras" are the most useful?