I found the dynamic link library, wnaspi32.dll in a couple of Windows' subdirectories on my XP SP2 machine.

I'm setting up EAC. Is there any advantage to copy/pasting it to the EAC folder or is this functionally equivalent to letting EAC find it as it executes its interface options upon installation. Question three: any reason to download a seperate copy of the dll into the EAC Program Folder?

Unless you have an ASPI layer installed, you will need to place the wnaspi32.dll dile in the EAC directory for it to use it.
I personally just use the inbuilt native Win 2000/NT driver and it works fine for me (I use WinXP Pro).
Try EAC without it, if it hangs while reading CD's then try the ASPI interface.

Mitch A.,

Thanks for your reply. I need to clarify one issue. When you suggested as a plan B for a sytem hang, did you mean anything other than placing the wnaspi32.dll file in the EAC directory? I do not know the difference between that action and, as you said, .

Thanks,
-MWA

He's suggesting that you configure EAC to use the native interface and if it works you don't have to worry about anything else.

If it doesn't work, then yes, you need to place a copy of wnaspi32.dll in the EAC directory. If this still doesn't work, you might have to try a different driver.

http://wiki.hydrogenaudio.org/index.php?ti...nload_page#ASPI

Finally, you must have admin rights to use EAC unless you use nero's BurnRights, which still requires admin rights upon initial use.