Here's a fail-safe way to check out your SCSI device.

1) Turn EVERYTHING off.
2) Make sure your drive is plugged into the EPS/ASR, and the cable is screwed in and tight.
3) Turn on the drive.
4) If it does not have a cart in it, put it in now.
5) Wait for the disk to spin up and click into it's "READY" state.
6) Turn on the EPS/ASR, with an OS floppy inserted.
7) As the EPS/ASR prompt says SEARCHING FOR SCSI DEVICE, look at the drive, and watch it to blink. This is called the NEGOTIATION PHASE. The EPS/ASR looks for devices on the SCSI chain, and tries to get an acknowledgement from them. If it does, the Busy light on the drive "blinks" as it gives the EPS/ASR it's acknowledgement. The EPS/ASR adds that device to it's "list", and goes on checking the next SCSI ID number.
8) If your SCSI Device did not blink, either

• something is functionally wrong with your drive
• Your drive is not compatible with your specific Ensoniq sampler - check our SCSI Drive Compatibility Page for a semi-complete list of drives
• your drive is on SCSI ID #3 (that's a no-no, that's the Ensoniq's number)
• your cable is bad
• your Ensoniq's SCSI Interface is bad
• some SCSI Device physically ahead or behind that SCSI Drive in question could be interfering with the SCSI communication
• If you have a ZipDrive, there is no ZipDisk in the ZipDrive - you must one inserted during bootup.
• your drive needs to be terminated, or there is another device ahead of it in the chain which is terminated.

9) If your SCSI Device did blink, wait for the EPS/ASR to boot the OS up and running.
10) Go to CMD-SYS/MIDI-CHANGE STORAGE DEVICE, and switch to the desired SCSI ID number.
11) If you get DISK COMMAND COMPLETED, you are successful!
12) Here's what the other messages mean:

• INVALID LOAD DEVICE: The EPS/ASR did not add this to it's "list" during the Negotiation Phase
• DISK NOT RESPONDING: Something "jammed" the communications of the SCSI Device, usually in the Negotiation phase, or with your accessing. Anything from a termination problem, bad cartridge/CD, or incompatible drive could be the cause. Also this sometimes happens when you try to access the drive when it's busy doing something else.
• NOT EPS DEV or NOT ASR DEV: The command was successful, but the cart/drive is not formatted for the EPS/ASR - it probably PC formatted or Mac formatted
• It freezes: something is really wrong.
• BAD DEVICE ID: The command was successful, but the cart/drive is not formatted for any device.
• DISK NOT READY: There is no Cartridge or CD in your SCSI Device.

Back to EPS and ASR-10 Knowledge Base Index

Close Window