Getafix
Experienced Member
Hi,
I am trying to get an Adaptec 1520 to go in my AT. SCSI BIOS is 1.4. I am using this with a BlueSCSI. At startup I see the bios and it sees the drive (reports it correctly as a Quantum Fireball) and assigns it as D: (I have an MFM drive in there as well). If I load aspi2dos.sys it also reports setting up Int 13 for drive D: With or without aspi2dos.sys, PC-TOOLS' si.exe will report a second drive (up to 1Gig capacity with my current, default, jumper settings). However, dos does not recognize this second drive as valid (format d: will report it as not a valid drive). More worrying is that ezscsi will always say: no host adapter. Another thing I find weird is that when I set the J9 jumper from I1 to I0 (from IRQ 11 to IRQ 10) the BIOS still reports the Jumper settings as IRQ 11 at boot-up time.
Is it possible the card is bad (I don't see the red LED ever come on)? Has anyone else set up a 5170 to use SCSI2SD or BlueSCSI with an Adaptec 1520? I have tried using gsetup to set the 1st drive to 0 and the card did report making the drive C: and then did a boot from floppy. But of course still no drive C: I should say that my HD0.HDA file is (currently 750M) of all 0's. Setting 2 drives in the IBM BIOS caused the card to say there are 2 drives and move on (do nothing), as I expected.
Any thoughts on what I may be seeing? Should I try an alternate 5170 BIOS (I want to do that anyway but it would be good to know if there's a known incompatibility with the original BIOS). I am pretty new to all things SCSI (other than replacing SCSI drives with SCSI2SD or BlueSCSI on apple or next computers). BTW I am not using any TSRs (so no PC-Tools caching, for example).
I should add that fdisk will say that it could not access disk 2. I then choose disk 2 and create a partition, and reboot. fdisk again reports it cannot access drive 2, and the partition information is no longer there when I choose drive 2 and list partition info. Looking at the HD0.hda in a hex editor shows that it has been modified. At specific offsets (every 0x4000 for a length of 0x01FF) 0xF6 was written into the file.
Thank you
Stefan
I am trying to get an Adaptec 1520 to go in my AT. SCSI BIOS is 1.4. I am using this with a BlueSCSI. At startup I see the bios and it sees the drive (reports it correctly as a Quantum Fireball) and assigns it as D: (I have an MFM drive in there as well). If I load aspi2dos.sys it also reports setting up Int 13 for drive D: With or without aspi2dos.sys, PC-TOOLS' si.exe will report a second drive (up to 1Gig capacity with my current, default, jumper settings). However, dos does not recognize this second drive as valid (format d: will report it as not a valid drive). More worrying is that ezscsi will always say: no host adapter. Another thing I find weird is that when I set the J9 jumper from I1 to I0 (from IRQ 11 to IRQ 10) the BIOS still reports the Jumper settings as IRQ 11 at boot-up time.
Is it possible the card is bad (I don't see the red LED ever come on)? Has anyone else set up a 5170 to use SCSI2SD or BlueSCSI with an Adaptec 1520? I have tried using gsetup to set the 1st drive to 0 and the card did report making the drive C: and then did a boot from floppy. But of course still no drive C: I should say that my HD0.HDA file is (currently 750M) of all 0's. Setting 2 drives in the IBM BIOS caused the card to say there are 2 drives and move on (do nothing), as I expected.
Any thoughts on what I may be seeing? Should I try an alternate 5170 BIOS (I want to do that anyway but it would be good to know if there's a known incompatibility with the original BIOS). I am pretty new to all things SCSI (other than replacing SCSI drives with SCSI2SD or BlueSCSI on apple or next computers). BTW I am not using any TSRs (so no PC-Tools caching, for example).
I should add that fdisk will say that it could not access disk 2. I then choose disk 2 and create a partition, and reboot. fdisk again reports it cannot access drive 2, and the partition information is no longer there when I choose drive 2 and list partition info. Looking at the HD0.hda in a hex editor shows that it has been modified. At specific offsets (every 0x4000 for a length of 0x01FF) 0xF6 was written into the file.
Thank you
Stefan
Last edited: