By
richie
Fri Mar 08, 2024 5:03 pm
I read that you changed boot disks and replaced the SCSI drive.
With regards to the zip drive, I take it you have alternated between setting the drive with termination on and off, and alternating between SCSI ID 5 / 6 right? I'm pretty sure that SCSI ID 6 on the 2000 is reserved for the 2000's controller. So if you do have the ability (depending on your zip drive variant) to switch to a lower SCSI ID, that would be great.
With regards to the boot drive, does the 2000 make any attempt to seek (do you see the light kick in to indicate that it is attempting to load data off of the disk drive?)
Other than that, I do have a theory that could be worth attempting - utilizing something like a Zulu SCSI, SCSI2SD where you can actually set the SCSI ID to be whatever you want, so I do wonder what would happen if you set the primary boot to SCSI ID 0 (you could actually set several virtual ids from 0 to 4 but for now we'll keep this to 0), to prevent the SCSI bus from attempting to seek anything above 0.
The problem is, even if we can prove the theory correct, in that loading a drive off SCSI ID 0 prevents the 2000 from freezing, there still lies the issue of the boot drive not loading an OS. The only alternative then would be to find someone on here with one of the aforementioned SCSI emulators I mentioned, have them upload their drive img file with OS 1.72 already saved on it, consequently bypassing the floppy drive all together.
Just some ideas for you to explore man, good luck.
I've blessed the post so god is with you.
MPC 1000 / 2000 / 2000XL / S900 / S1000 / S2800 / S3000XL / S6000
ROLEX GMT 116769TBR / SILK ISFAHAN RUG