Causes:

1. SCSIWorks! Software was installed without choosing a HOST ADAPTER in the install program.
2. Cables installed incorrectly, bad cables, or a bad card.
3. A conflict with another card in the computer system.

Solutions:

1. Rerun the installation and choose "Automatic Search For Host Adapter." If the "Automatic Search For Host Adapter" returns with no host on the line "Trantor Host Adapter", do a manual selection with arrow keys to select the correct host adapter.
2. Retry the adapter with NO cables attached. Bad cables or damaged cables can shut the adapter down. Replace the bad card.
3. Remove all other cards, check the default setting on Trantor card. All switches are OFF or down as a default on Trantor cards.

Causes:

1. Cables installed incorrectly, or bad cables.
2. A conflict with another card in the computer system.

Solutions:

1. The ASPI manager(s) failed to find a host adapter. Remove all cables from the adapter and reboot. If host adapter is found now, one or more cables may be defective or 180 degrees out on the internal connector, (pin 1 is on pin 50) reverse the cable and retry.
2. Remove all other cards, check the default setting on Trantor card. Network, 16 bit Video cards and the Intel SATISFAXION boards can use the same addressing space.

Causes:

1. Hard Disk Drivers installed (TSCSI.SYS) with no HARD DISK installed, or an unformatted drive.
2. Hard Disk Drivers installed (TSCSI.SYS) in the config.sys with the BOOT ROM enabled.
3. The Hard Disk was formatted with another SCSI controller that does not support ASPI or has special format.

Solutions:

1. Remove "TSCIS.SYS" from config.sys and reboot. Or run Tformat.exe to format the drive.
2. Remove "TSCSI.SYS" from config.sys or disable BOOT ROM.
3. Some controllers like Western Digital only work with other Western Digital controllers, or the controller supports 1024 sectors I.E.: WORM or multi-function drives, which Trantor drivers do not support.
   

1. The Hard Disk has not been Partitioned.
2. The Hard Disk was formatted with Tformat and customer did not answer "Y" to make hard disk bootable in Tformat process.
3. Hard disk was formatted on another manufacturers controller first.

Solutions:

1. Do high level format on the hard disk. I.E.: TFORMAT.
2. Run TFORMAT and answer "Y" to making the hard disk bootable.
3. If the controller is Western Digital nothing can be done, reformat the drive with current controller using TFORMAT.

Causes:

1. The SCSI device is not turned on, or not cabled correctly.
2. The SCSI device is ON but fails INQUIRY command.
3. The SCSI device is sharing the same SCSI ID with another device.
4. Wrong device driver loaded for device type.

Solutions:

1. Turn SCSI device on, and check power connectors to insure they are connected.
2. The SCSI device may be dead, or not supported by Host Adapter. Device may need default jumper setting changed. Such as the drive should Spin up and Come Ready on its own.
3. Check all SCSI devices to verify that each device has separate SCSI ID. Range is 0-6 or SCSI ID's. If set to 7 it will show all LUN's (7 drives).
4. Check config.sys to make sure correct driver loaded for the drive type I.E.: TSCSI.SYS for a hard disk, not a CD-ROM.
5. Make sure the SCSI cable has not been plugged into the parallel port instead of the port on the SCSI board. Both ports use a DB 25 connector, and can easily be confused. Note: (This is rare but it does happen).

Causes:

1. The SCSI Hard Disk has failed to boot as the primary drive. The drive was not formatted properly with TFORMAT. The Primary hard disk is not at SCSI ID 0.
2. Termination is not correct, or TERMPWR was not provided by the HARD DISK for the host adapter.

Solutions:

1. Run TFORMAT with this option specified "/S60". If you have a TSROM on a T128 or T228 only. This will not work on T130b, T160, or T260 host adapters. I.E. TFORMAT /S60 (this sets sector size). If necessary boot from a floppy with just the ASPI MGR loaded in the config.sys and no other drivers. Then format drive. Set the primary hard disk at SCSI ID 0.
2. Check the host adapter to make sure the termpwr resistors are still on the card and that they are REMOVED from all the internal drive(s). Also verify that the drive is providing TERMPWR.

Causes:

1. During the TFORMAT process you get a CMD Failure (command failure). These are VENDOR specific codes, call the vendor to find out what the error means.

Solutions:

1. The most common problem is trying to PARTITION a drive that is NOT low level formatted. Rerun TFORMAT with this option. I.E.: TFORMAT /L . This will do a low level format for you.

Causes:

1. SCSIWorks! Software was installed without choosing a HOST ADAPTER.
2. The SCSI device is not supplying 5 volt dc on pin 38 of the 50 pin centronics connector.
3. A print spooler or printer cashing software is enabled.
4. An extension cable was used between the MINIscsi and the parallel port of the computer.

Solutions:

1. Rerun the install and choose "Automatic Search for Host Adapter". If the "Automatic Search for Host Adapter" returns with no host on the line "Trantor Host Adapter", do a manual selection with arrow keys to select the correct host adapter.
2. Verify that the SCSI device is supplying TERMPWR. Plug a printer into the parallel port pass- thru of the MINIscsi, hit a print screen, if you don't get a print out or receive a garbled printing you have NO TERMPWR. Or use a multi-meter to check pins 38 and 37 on the 50 pin connector of the drive. (38 is hot, 37 is ground.)
3. Make sure that any printer SPOOLERS are turned OFF. This will hang the MINIscsi. The Print Manager in Windows should be turned OFF.
4. Remove the extension cable, MAX. length is 6 inches and must be double shielded. The MAX. length of cable from the pass-through port on the MINIscsi to the printer is 6 feet. MINIscsi + 6 foot cable = 9 feet. Longer cables may cause the MINIscsi to fail.

Causes:

1. Hard Disk Drivers installed (TSCSI.SYS) with no HARD DISK installed, or an unformatted drive.
2. Hard Disk Drivers installed (TSCSI.SYS) in the config.sys but only has a CD-ROM.

Solutions:

1. Remove "TSCSI.SYS" from config.sys and reboot. Or run Tformat.exe to format the drive.
2. Remove "TSCSI.SYS" from config.sys. Install the CD-ROM software again if needed.

Causes:

1. The SCSI device(s) is not turned on.
2. The SCSI device is on but fails INQUIRY command.
3. The SCSI device is sharing the same SCSI ID.

Solutions:

1. Turn SCSI device on.
2. The SCSI device may be dead, or not supported by Host Adapter. Device may need default jumper setting changed. Such as the drive should Spin up and Come Ready on its own.
3. Check all SCSI devices to verify that each device has separate SCSI ID. Range is 0-6 for SCSI ID's. If SCSI Id is set to 7 it will show all Lun's (7drives).
4. Try the /Mnm option on the manager line in config.sys. I.E.: Device=C:\TSCSI\MA358.SYS /M14.

To help you determine if you have a supported parallel port the following are the port specification right out of the book.

AS A RULE OF THUMB

Desktop Computers: 99% of the time have UNI-Directional ports.

LAPtop Computers: 4 years or older have UNI-Directional ports.

LAPtop Computers: Less than 4 years old usually have Bi-directional ports.

NOTEBOOK Computers: 99% of the time have Bi-directional ports.

NOTEBOOK Computers: Newer models have EPP/ECP Ports.