Thread: Solution for ASPI problems in EAC (No CD Found Problem)

After trying everything else - Adaptec ASPI, vob ASAPI - I got Nero's ASPI and put it into the EAC program folder. After that, things are peachy.

I run Win2K with an external Firewire drive that EAC would not recognize at all before Nero ASPI installed.

Get Nero ASPI at
ftp://ftp6.nero.com/wnaspi32.dll
from this page
http://www.ahead.de/en/index.html#c1004602999110

Originally posted by Unregistered
I had that same problem. I'm not sure what I did specifically to solve it. But here is what I did

1) removed/uninstalled EAC
2) cleaned out all its registry entries
3) installed the ASPI layer from adaptec
4) installed EAC
5) set EAC to use external ASPI layer
6) restarted EAC

and now it works fine for me. Hope this Helps

Thank you sooo much! And also, thanks to everyone on this page who contributed! EAC now detects an Audio CD in my drive! No tu try it out!

Peace,
Ryan

Originally posted by justin_case
i solved all my aspi-problems so far by copying wnaspi.dll from my \win32 dir into the application directories of the programs having trouble. i'll check the links above in a minute, though..

/jc

Originally posted by justin_case
i solved all my aspi-problems so far by copying wnaspi.dll from my \win32 dir into the application directories of the programs having trouble. i'll check the links above in a minute, though..

/jc

this worked for me...thank you!

i will now add my 2 cents as well.

i copied nero burning rom's (ahead software) wnaspi.dll to the EAC directory to solve a completely different problem: EAC would not detect my external USB CDD.

after configuring EAC to use the installed external ASPI, it works PERFECTLY!

now i know why EAC rulez! ;-)

btw. i still cant convince my audiograbber to work with my USB CDD...

damasta

Hi,

I posted the message "real solution to aspi problems in win2k/XP", which is now sticky in this forum.

When I wrote that message I was using Adaptec ASPI 4.71, and it worked very well with the registry fix suggested by Yakumo.

However, Adaptec has recently released the version 4.71.2, which is very dangerous in some circumstances.

At first, 4.71.2 worked more or less fine in the computers I installed it (the only problem was that EAC showed the ASPI option greyed out and was not selectable).

So I applied the Yakumo fix, and the result was complete disaster: Blue Screen Of Death at the next boot, and then a sudden restart, repeating this cycle again and again.

The only solution posible: to press F8 key when Windows starts and recover the system choosing "Last known good" configuration.

I did the same on four different computers (chipsets VIA KT133, KT133A, KT266 and KT266A) just to be sure, and the result was the same in all of them: Blue Screen Of Death!!

So, please be very careful with the Yakumo fix, especially if your mainboard has a VIA chipset.

Also, I think maybe it would be a good idea to edit my old post to give this warning to the people before they start applying the fix to version 4.71.2. It is very dangerous to do so!

Thanks a lot.
Best regards.

hey, maybe somebody here can help me - I'm having EAC/ASPI problems too.

I had EAC running correctly, until I installed adaptec direct cd. now I get this error:

Code:

The ASPI interface could not be initialised correctly! (Error E8h)
(No host adapters found)

EAC fails to load after that, so no chance of changing settings.

I tried running forceaspi, which would not work - I get this error:

Code:

Cannot import Win9x\Win9x.reg: Error opening the file. There may be a disk of file system error.

aspichk reports that the aspi layer is installed correctly, but that there are no host adapters. I tried installing an Adaptec 2940 SCSI adapter, but that didn't seem to help anything. I also uninstalled adaptec direct cd and easy cd, and EAC, and reinstalled easy cd and EAC. no luck.

I'm running win98, Adaptec ASPI 4.6, most current version of EAC (forgot which and can't check) and a plextor drive. any suggestions on what to do?

D'loading wnaspi32.dll from Ahead (Nero) did the trick for me (plus the stuff mentioned earlier...thanks to all!) for my ext Yamaha F1 USB drive. In my case though, I didn't need to uninstall EAC or clear out the registry. Had wrong version in the EAC dir. The one from the Adaptec ASPI v4.71.2 package didn't work.

Had to learn German to register as a member. If you don't want to take the time go here.

Xenno

Terrible. Just terrible
MAybe EAC should work without aspi drivers like all othe programs do(ist this so?)

When i installed wnaspi32.dll in the eac directory, EAC worked well.
BUT.....
Explorer and all the others windows programs could not read the cd drives anymore.
I uninstalled EAC restart the comp and everything could again work fine again with the drives.

So it is or EAC is working well and no other program OR all other prgrams but no EAC

I use XP
disabled the built in burning issues

?????????????????????????????????????????????????????????

Win2K on old Dell 233.
At first ASAPI_from_VOB.EXE bombed when launched.
(might have been a user rights problem, but I don't think so)
Then I installed ASPI 4.71 from Adaptec.
That ran and ASPICHK said it was all fine, but EAC and CDEX still didn't work.

Later I re-ran ASAPI_from_VOB (after trying a few things). Now EAC and CDEX both work fine!
NOTE: to run Apps from a Power User profile, I did a SHIFT + Right-Click and typed in the name and password for the Administrator without logging off.

ASAPI installed the "WRONG" ver. Wnaspi32.dll (12-1999) in the Windows\System32 folder.

Wnaspi is ver. 1.0.6 while the rest of ASPI files are v. 4.6 or 4.7 according to ASPICHEK. (I had extracted the ASPI 4.7 using Winzip, hence having the separate ASPICHEK file in a folder.)

I even tried manually replacing Wnsapi32.dll in the \windows\system32 folder, renaming the "wrong" one, thinking that now VOB had done some 'configuration' that would allow the new "right" ver to work, but no go.

So I renamed the new version and "un-renamed" the "wrong" Wnaspi32.dll to restore it.

When I run EAC or CDEX from a Icon, I *could* SHIFT + Right-Click to a) avoid 'running' as Administrator all the time, while b) being able to launch those progs as Administrator. If I launch directly as a Power User, it still doesn't work, due to user rights.

To make it easier, I changed properties on the Shortcut to say
runas.exe /user:compname\adminame "c:\EAC94\EAC.EXE"
This prompts me in a DOS window for the password for the Administrator account, and starts the program.

I followed a tip and downloaded the 'newer' larger file size Wnaspi32.DLL from Ahead (Nero) and copied that file to my EAC and CDEX folders, just in case that might work 'better' (how could I tell if it was 'better'?).

That seems to work fine too.
I probably needed all the other ASPI drivers (aspi.sys, wowpost, etc.) installed first before that 'standalone' Wnaspi32 would work.

PS, I remove the Default --R3mix from EAC compression settings to avoid VBR which is problematic on my portable MP3 player.
I use:
--lowpass 19.7 --priority 1 --verbose
--lowpass 19.7 is SPECIFICALLY recommended at one of the audio engineer links. It filters extraneous hi-freq info not audible and leaves more "room" for more good sound.
I also used the link on EAC for the latest version of LAME v 3.93 which I put in it's own folder.

Now I just gotta find a valid CD to use to set Offsets.

geekman1

OK, after reading more, I'm trying LAME version 3.90.2 MMX from Dibrom, instead of 3.93.1. I don't know if I'll be able to hear a difference but we'll see.

Wondering on possible audible/size difference btw the two and what about using the --r3mix setting instead of the --alt --preset --standard?

R3mix seems to use some advanced "nypsytune" settings that sound like they might be worthwhile. Any problems?

Geekman
Gary Goodman
G@NEO.RR.COM

I don't understand why I have WinXP Pro and have encountered no problems burning CDs at all. I have been trying to learn what ASPI is in the first place. I see all these people tallking about it, but the only responses I get are "It let's Windows talk to SCSI devices." Is there some inherent conflict in XP with burning CDs? If so I have never encountered it. I have WinXP Pro SP1, Nero 5.5.10, a Lite-On 48x12x48 and use EAC. Will ASPI drivers increase my performance, or should I leave well enough alone? Any input will be appreciated.

Originally posted by Unregistered
I've tried and tried to resolve this matter, but keep coming back to square one.

I've downloaded and installed EAC. I've downloaded and installed ASPI v 4.71 AND the "fix" located at the top of this message. My EAC file is full of ASPI files, but yet when I try to use EAC the program does not recognize a disc in the drive. I've hacked and hacked and still cannot come up with anything. I went to the "options" folder and tried to change the "use of SCSI interface", but the two are greyed out and the only option checked is for Win NT/2000. I am a Win XP user.

So, PLEASE, can someone tell me what I need to do. I'm completely exasperated. I'm not very computer savvy, but I'm not a dummy either. I just need a plain english explanation about what I'm doing wrong and how to fix it.

Thanks so much,


I'm having this problem also

Lisa

Hello all,

I have a very nasty problem with my dvd/cd-rom , and the solutions given by others don't seem to work for me. I have win 98se, and after creating an image file with eac my system won't recognize my audio-cd's any more, no matter which program I use. I installed the wnapsi32.dll in the same folders as the applications which should work with the audio-cd but nothing helps. My sytem still sees data-cd's I insert, but any other cd's, either audio or with avi/mpeg arn't recognized. Deinstalling and installing eac won't help. Is my dvd/cd-rom drive gone or is it a sofware problem. If so, how can I solve it?

Many thanks,

Jos