emusonacid! legacy

I would like to know if anybody got to succesfully run SoundForge 4.5 in a Windows 2000 or XP box and were able to use SondForge to upload/download samples to their EMU via SCSI/SMDI. What I have found is that SoundForge 4.5 cannot find the SCSI devices under Windows 2000 or XP but it will under Windows NT 4.0, which I have succesfully tested and I am currently running; even EOS Link works under Windows NT 4.0 controlling two EMU Ultras via two SCSI cards (of course, not before messing with Visual Studio runtime libraries and WINASPI). Let me know.

Dorian

I've had SoundForge 4.5 running under win2k using scsi to transfer samples without issues. I think you need to get the aspi layer sorted to make it work - you can get the drivers from adaptecs website.

stu wrote:I've had SoundForge 4.5 running under win2k using scsi to transfer samples without issues. I think you need to get the aspi layer sorted to make it work - you can get the drivers from adaptecs website.

Interesting. I was using a Symbios/LSI SCSI card and although W2K/XP recognized it, SoundForge couldn't even see the host target; it only worked in NT. I have since replaced the card with an Adaptec 2930 and a 2940, so I'll reinstall W2K and XP and see what happens. It's important to note that whenever I tried to load banks through EOSLink and the Symbios card, NT bluescreened but once I started using the Adaptec cards, it worked fine.

Tried W2K with SF4.5 and Adaptec's native drivers and the WINASPI from EMUSONACID and no luck; SF4.5 just doesn't seem to "see" the SCSI host (Adaptec card). Didn't load W2K SP4, so I need to try that next, but I just think SF4.5 needs to see the SCSI system like NT4.0 sees it, don't know why.

I recall there are some specific flags you have to set for a successful install of the APSI drivers - it requires some manual fiddling - otherwise the wrong (e.g. Win98) driver gets installed.

review the batch scripts that come with the installer.

Also - you might want to look at FrogASPI - its a new refresh on the APSI layer.

I have successfully used SF 4.5 in the past on XP via LSI Logic scsi adapter (Tekram 810U) which was $20 at the time with SF 4.5, Mobius, Wavesurgeon , Recycle 2.0 - all of which of course is no longer supported.
Recycle was the best one for throwing a lot of data at the sampler...

M

kalide wrote:I recall there are some specific flags you have to set for a successful install of the APSI drivers - it requires some manual fiddling - otherwise the wrong (e.g. Win98) driver gets installed.

review the batch scripts that come with the installer.

Also - you might want to look at FrogASPI - its a new refresh on the APSI layer.

I have successfully used SF 4.5 in the past on XP via LSI Logic scsi adapter (Tekram 810U) which was $20 at the time with SF 4.5, Mobius, Wavesurgeon , Recycle 2.0 - all of which of course is no longer supported.
Recycle was the best one for throwing a lot of data at the sampler...

M

Tried the "X86" switch and even FrogASPI but no luck. What version of SF4.5 are you running? I am running SF4.5a; could there be a fix in the updates?

Hi guys, just saw your communication of some time ago - hope you can help me.

I have a very nice E 6400 Ultra connected via SCSI to my PC with Adaptec SCSI card and under Win 98 SE.

I have been using Wavelab v3.04G for long, and on a previous (and a bit skrewed) PC that died meanwhile, I could manage SMDI sample transfers in both directions.

My new PC can connect with the sampler, e.g. using the Xtrakk freeware program, I can load samples onto my sampler. But Wavelab won't do it.

I now bought a Sound Forge XP 4.5 and just loaded it ... how can I check if it recognizes my sampler? No explanations in the manual, and apparently no button on the menu either ...??


Many thanks!

drdel