WDS-3158 Jumper-settings for ID 0 or 1
K. Martinen
Another Problem with my 8580
The SCSI-Drive, a WDS-3158 is not detected by the Adaptec 1640. He's searching
for ID 0 and 1 but the drive was not found.
A Quantum Fireball TM12 (1 GB) at ID 0 is working but had CRC-Errors if i try to
install OS/2 Warp3 (Formatting with hpfs fails).
For this Parts i only have an IBM Hardware Maintenance Manual of '94. There are
Jumpersettings described for two different drive-types. One of them fits to my
drive (Dip-switches) but the settings i made did not work.
I set it to ID 0, to 1 and to 6 and nothing works. In the past there was an DOS
on this drive and it must be on there. Years in the Past the drive can boot this
DOS. I don't know if i made changes to it, i think i don't.
What i need is a complete description of the correct settings for the Drive and
a description of any possible settings on the Adaptec. Maybe i lost a jumper on
the controller and don't know it.
Need Help. :-)
Bye/
/Kay
--
from germany
Marco "wile" Paolini
> What i need is a complete description of the correct settings for the Drive and
> a description of any possible settings on the Adaptec. Maybe i lost a jumper on
> the controller and don't know it.
>
> Need Help. :-)
>
> Bye/
> /Kay
For the drive and controller:
Look here, may be useful!
http://www.webtradecenter.de/pcdisk/
--
#include <std.disclaimer.h>
Signature automatica inserita a mano.
In God we trust, all others we monitor.(NSA)
Punteggiatura: Nel caso mancasse nel messaggio, aggiungete!!
Louis Ohland
it. Does the 1640 detect it during boot, and if so, does it fail to find
a bootable partition? This may happen if the drive was not formatted on
the 1640.
http://www.ibmmuseum.com/OhlandL/SCSI/AHA-1640.html
Jumpers are factory use only.
BIOS enabled for booting off drives <1GB
K. Martinen
Thanks.
There are many WDS-types but only two with numbers near to my drive, the 3100
and 3158. But both did not match with my hardware.
Bye/
/Kay
K. Martinen
> The WDS should be set to 0 or 1 in order for the AHA-1640 to boot from
> it.
It was set to 0 and to 1.
> Does the 1640 detect it during boot,
No.
> and if so, does it fail to find
> a bootable partition? This may happen if the drive was not formatted on
> the 1640.
It was formatted with it. And it worked, 1-2 years before. But not yet.
> http://www.ibmmuseum.com/OhlandL/SCSI/AHA-1640.html
> Jumpers are factory use only.
O.K. Are the J3 and J4 Jumperblocks empty by factory (no jumpers at all) or must
there be *any* jumper in *any* position? On my 1640 i have no jumpers! Is this
the normal case?
> BIOS enabled for booting off drives <1GB
BIOS is enabled. At boot-time he states that there is no Target 0 lun 0 found,
and the same with target 1 lun 0.
If the Fireball-disk is connected he found target 0 lun 0. as Drive C:
I believe there are 2 possible cases:
1. The WDS drive is defective.
2. The ID-settings differ between the drive and my manual so i'm setting it to
the wrong positions.
Actually i prefer the 2.case... :-)
The link from Marco's Article did not help (see there).
I Put 3 Photos of the drive and details online.
The Jumper-area is under:
http://cid-a69dcfdbeb6ac5a5.skydrive.live.com/self.aspx/Lost%20and%20Found/DSCF0003^_crop.jpg
Mabe this could help to *see* the Problem.
Louis Ohland
But anyhows, my last stabs at bringing this up. Do you have a Spock?
This will allow you to use the refdisk to set and view scsi devices...
Is drive set to power on immediately? Auto-start
Is the 1640 set to enable parity? PS/2s need parity enabled.
Louis Ohland
K. Martinen
> Er, WDS-3160...
It's Okay, i knew you are meaning this one. See my other posting.
Bye/
/Kay
K. Martinen
> How about a WDS-160?
Nope. The 3160 is not the same as my 3158. It differs bare optically (e.g. not
the same). [Hope i say it correctly, my english is not good.]
> But anyhows, my last stabs at bringing this up. Do you have a Spock?
> This will allow you to use the refdisk to set and view scsi devices...
Nope2. I have only one Adaptec 1640. No Spock! No other SCSI-controllers.
The Other cards, one Mem-card, the Maynard-Tapecontroller and the 3C529 are
pulled out before this.
> Is drive set to power on immediately? Auto-start
yes, it is. I don't know how to change this. But the drive spins up
automatically. So changes are not needed.
> Is the 1640 set to enable parity? PS/2s need parity enabled.
Parity is enabled. BIOS should be active, i ran the autoconfig from the refdisk
and there are no errors.
Bye/
/Kay
--
from Germany
UZnal
> >>> it.
- The boot disk should be set to SCSI ID 0
- SCSI ID 1 is reserved for the second disk
- Enable parity on disk
- Enably sync negotiation on disk
- Check the 50-pin cable orientation, match pin-1 to pin-1
- Ensure that the SCSI bus is end-to-end terminated
- Ensure right angle cable crosses
Parity should be only enabled if all devices on the bus support parity.
When AHA-1640 is the boot adapter:
- Port I/O = lowest slot number among 330h, 230h, 130h (if any other adapter
uses these, the AHA-1640 should be installed in the lowest numbered slot)
- Arbitration level = 5
- Adapter BIOS = only one adapter BIOS enabled (multiple AHA-1640 case)
- Fairness = ON
- Sync transfer started by AHA-1640 = YES
- Sync transfer negotatiation = ON
NOTE: If you have *two already installed internal disks* in the system and
attached to another controller, and add an additional disk through the
AHA-1640, you need for it a driver, IIRC, one like ASPIDISK. For example,
with two ESDI disks and one SCSI disk from AHA-1640, the SCSI disk will not
be supported without a driver.
In my experience:
- Install ASPI4DOS.SYS if EMM386.EXE is installed and in HIGH memory.
- The total amount of DOS partitions and logical drives should not exceed 1
GB
- Non-DOS partitions like OS/2 HPFS will be recognized even when located
above the 1 GB DOS/FAT boundary, hence, you can use disks greater than 1 GB.
- Access the AHA-1604 onboard utility (mini-config) by starting DEBUG and
entering G=DC00:6 where DC00 is the default BIOS base address (replace with
the actual address).
UZnal
from
> > >>> it.
A guess based on the settings of WDS-3160:
ID 0 should be all three pins OPEN, that is, pins 1 2 3, where pin 1 is the
least significant bit. Then ID 1 translates to 100 - pin 1 jumpered, 2 and
3 OPEN. For ID 0, remove all jumpers from pins 1, 2 and 3.
Looking at the WDS-3160 settings I cannot not see anything about parity and
sync negotiation.
I got the WDS-3160 settings from here, search for "WDS":
http://www.webtradecenter.de/pcdisk/