emusonacid!

Hi guys.

Some info here on SCSI connection and sample dumping and a question to follow:

I recently got my "EMU Server" up and running with 4 (yep, 4!) SCSI controllers to allow me to connect my 4 EMU samplers up on individual SCSI Chains thus eliminating issues with conflicting SCSI IDs and drive contention etc. After a lot of grief trying to get my old version of Sound Forge (V4.0) to communicate with any sampler, I did some research and discovered that there is a difference in the way that Windows XP handles communication with SCSI devices when compared with older Windows versions which may render certain software relying on ASPI API calls useless. So if you are experiencing the issue where windows recognises that a sampler is connected yet your sample dump software does not even after you have upgraded the SCSI drivers and installed the ASPI protocol, it could be that the software is just not compatible. For the record, the latest version of Sound Forge (V8.0) works perfectly where V4.0 failed.

Now, on to my question; the PC has recognised and prompted for drivers for my E4XT and ESI-32 however, my e6400 Classic remains ignored. The SCSI card (Adaptec 2940) reports both the e6400 and its internal hard drive when it preforms its device scan on boot up. The SCSI port on the sampler is functioning correctly as I have used it to read and write successfully from a zip drive. Can anybody make any suggestions as to why XP won?t recognise the sampler or even how to force XP to find it? Could the internal hard drive, if set with SCSI termination on, cause the sampler to be invisible as far as Windows is concerned?

Cheers,
Adam-V

Hi alone.

Can anybody make any suggestions as to why XP won?t recognise the sampler or even how to force XP to find it?

which OS version have you? my e6400 classic was recognized by XP when i upgraded in OS 4.62 , no way under EOS 3.00b.

but i never dealed with a scsi network, it is diretly connected to my laptop via a pcmcia card

That is interesting although I don't think the EOS version should cause this. I was running 2.5 then upgraded it to 3.0. I know for a fact that V2.5 supported SCSI sample dump as I have had my old e6400 working perfectly on an old PC before they both died. If it is the EOS version casuing thin then I guess I'm Screwed and I will have to work out another way to rensfer samples to the e6400.

cheers,
Adam-V