Before the problem:
Adaptec 2940 Ultra/Ultra-wide SCSI controller. Two hard drives
and CD-ROM on internal 50-pin Connector (narrow; 8-bit). External LS-120 SCSI drive (8-bit device) on an external 16-bit
bus (special SCSI cable 68-pin at PC and 50-pin at device).
Then had head crash. Original boot drive is toast. Bought a new
SCSI drive, a 68pin (wide; 16-bit) one. Now the SCSI controller has three strings:
Still on 50-pin cable: one hard drive and the CD-ROM.
External LS-120 setup unchanged.
On new 68-pin cable: the new replacement hard drive, the boot drive.
Using the Adaptec SCSI utility, the SCSI BIOS was set to boot from the LUN (6) of the new drive. Also, fast support was enabled.
Much of this works OK. At boot time, the SCSI BIOS is installed
successfully. It finds all SCSI devices. The new drive was C: and the other older drive was D: Ive been able to use DOS FDISK to partition and format the new drive, so that it now has a primary dos partition and two logical drives in an extended partition. From a DOS diskette did a SYS C: and thus have a very minimal system on the new C-drive which boots OK.
Heres the problem. In the good old days when all the SCSI devices were on the same narrow bus, I had a DOS bootable diskette which loaded drivers like ASPI8DOS.SYS from Adaptecs EZSCSI 5.0. This was followed by other drivers like MSCDEX, and by booting from that diskette I was able to access the CD-Rom.
Now however, the ASPI8DOS.SYS fails and the system hangs during boot. So no access to the CD-ROM, which I need because I have all the data backed up from the original (crashed) drive and want to copy it to the new drive. Also, running DOSINST from the EZSCSI diskette does not work either. If I choose for it to scan for the controller, it hangs. If I choose to pick a controller, it does not give me the 2940 as a choice (which is a bit peculiar since it did so when all devices were on the narrow bus.)
All this might be because I now have a mixture of 16-bit and 8-bit devices. Some questions/thoughts:
1> Would updated EZSCSI drivers be needed?
2> Or maybe updated SCSI BIOS for the 2940
3> Does something need to be fixed in the CMOS bios?
4> Maybe the support for "fast" is causing a problem
with the LS-120.
5> Could I not disable the "fast" support and see what
happens? But I should be able to run the new drive
at the fast (16-bit) speed.
I have looked at the Adaptec web page, and nothing seems to address this directly. Any thoughts?
Adaptec 2940 Ultra/Ultra-wide SCSI controller. Two hard drives
and CD-ROM on internal 50-pin Connector (narrow; 8-bit). External LS-120 SCSI drive (8-bit device) on an external 16-bit
bus (special SCSI cable 68-pin at PC and 50-pin at device).
Then had head crash. Original boot drive is toast. Bought a new
SCSI drive, a 68pin (wide; 16-bit) one. Now the SCSI controller has three strings:
Still on 50-pin cable: one hard drive and the CD-ROM.
External LS-120 setup unchanged.
On new 68-pin cable: the new replacement hard drive, the boot drive.
Using the Adaptec SCSI utility, the SCSI BIOS was set to boot from the LUN (6) of the new drive. Also, fast support was enabled.
Much of this works OK. At boot time, the SCSI BIOS is installed
successfully. It finds all SCSI devices. The new drive was C: and the other older drive was D: Ive been able to use DOS FDISK to partition and format the new drive, so that it now has a primary dos partition and two logical drives in an extended partition. From a DOS diskette did a SYS C: and thus have a very minimal system on the new C-drive which boots OK.
Heres the problem. In the good old days when all the SCSI devices were on the same narrow bus, I had a DOS bootable diskette which loaded drivers like ASPI8DOS.SYS from Adaptecs EZSCSI 5.0. This was followed by other drivers like MSCDEX, and by booting from that diskette I was able to access the CD-Rom.
Now however, the ASPI8DOS.SYS fails and the system hangs during boot. So no access to the CD-ROM, which I need because I have all the data backed up from the original (crashed) drive and want to copy it to the new drive. Also, running DOSINST from the EZSCSI diskette does not work either. If I choose for it to scan for the controller, it hangs. If I choose to pick a controller, it does not give me the 2940 as a choice (which is a bit peculiar since it did so when all devices were on the narrow bus.)
All this might be because I now have a mixture of 16-bit and 8-bit devices. Some questions/thoughts:
1> Would updated EZSCSI drivers be needed?
2> Or maybe updated SCSI BIOS for the 2940
3> Does something need to be fixed in the CMOS bios?
4> Maybe the support for "fast" is causing a problem
with the LS-120.
5> Could I not disable the "fast" support and see what
happens? But I should be able to run the new drive
at the fast (16-bit) speed.
I have looked at the Adaptec web page, and nothing seems to address this directly. Any thoughts?