SMIDI/SCSI problem -Sound Forge - PC - MAGIX Community Forums Archive

Subject:SMIDI/SCSI problem Posted by: dondelion Date:7/28/2004 3:24:06 AM I'm trying to take advantage of the seemingly wonderful capabilities of SMIDI but my PC won't detect the A3k.I don't have a SCSI hard drive - I just want to send samples from Sound Forge to the A3k memory and then save them to ZIP...I also don't currently have the cables for A3k to ZIP to PC (I have them for A3k to PC and A3k to ZIP). In the sampler SMIDI configuration dialogue box for SCSI I have two options for ATAPI (CDROM?) and one for ASC (SCSI Card?). When I select ASC and try and send or receive I get an error. On booting up the PC my Advansys ABP930 PCI SCSI adaptor doesn't detect the A3k neither does XP but I know the adaptor and the A3000 SCSI port work as they can detect the ZIP drive and have also tested the cable. I receive an error message from my SCSI card - error: init taget 0x15 error: pci not found bios error - in the Advansys BIOS and XP doesn't even aknowledge the existence of the A3000. I have installed some ASPI drivers from the Adaptec site but still nothing...any ideas? Sorry if this is a hardware problem rather than anything to do with Sound Forge but I'm stuck (the SCSI card is no longer made and no support is available), Thanks in advance, Donovan Sellings
Subject:RE: SMIDI/SCSI problem Reply by: Chaim Date:7/30/2004 2:40:47 PM Hi Donovan, I would seriously consider swapping out the Advansys card for one with solid support on XP, and a better reputation for compatibility. My preference would be Adaptec. If you don't have one, maybe you could borrow an Adaptec card and see if your system recognizes the A3K? Also, this is kind of basic but make sure the A3K SCSI address is not the same as the Zip drive; they must be unique AND they must not use the address of the SCSI card, which usually defaults to ID 7. Also, pay attention to termination- either enable it on the last device on the chain, or use an active external terminator. 90% of SCSI errors we've encountered over the years were due to improperly set bus IDs and/or termination issues. --Charlie

Subject:SMIDI/SCSI problem

Posted by: dondelion

Date:7/28/2004 3:24:06 AM

I'm trying to take advantage of the seemingly wonderful capabilities of SMIDI but my PC won't detect the A3k.I don't have a SCSI hard drive - I just want to send samples from Sound Forge to the A3k memory and then save them to ZIP...I also don't currently have the cables for A3k to ZIP to PC (I have them for A3k to PC and A3k to ZIP). In the sampler SMIDI configuration dialogue box for SCSI I have two options for ATAPI (CDROM?) and one for ASC (SCSI Card?). When I select ASC and try and send or receive I get an error. On booting up the PC my Advansys ABP930 PCI SCSI adaptor doesn't detect the A3k neither does XP but I know the adaptor and the A3000 SCSI port work as they can detect the ZIP drive and have also tested the cable. I receive an error message from my SCSI card - error: init taget 0x15 error: pci not found bios error - in the Advansys BIOS and XP doesn't even aknowledge the existence of the A3000. I have installed some ASPI drivers from the Adaptec site but still nothing...any ideas? Sorry if this is a hardware problem rather than anything to do with Sound Forge but I'm stuck (the SCSI card is no longer made and no support is available),

Thanks in advance,

Donovan Sellings

Subject:RE: SMIDI/SCSI problem

Reply by: Chaim

Date:7/30/2004 2:40:47 PM

Hi Donovan,

I would seriously consider swapping out the Advansys card for one with solid support on XP, and a better reputation for compatibility. My preference would be Adaptec. If you don't have one, maybe you could borrow an Adaptec card and see if your system recognizes the A3K? Also, this is kind of basic but make sure the A3K SCSI address is not the same as the Zip drive; they must be unique AND they must not use the address of the SCSI card, which usually defaults to ID 7. Also, pay attention to termination- either enable it on the last device on the chain, or use an active external terminator. 90% of SCSI errors we've encountered over the years were due to improperly set bus IDs and/or termination issues.

--Charlie