I've been wondering... what is the difference between the aspi drivers and w2k's native interface? Which is better and why?
btw: i installed aspi 4.70, but eac chacked it AND grayed it out. The log file says i'm using w2k native interface... have i done something wrong?
I am also curious to know the difference.
My thoughts on the subject are this. ASPI is an interface standard written for stability, portability, and reliability. The NT native interface while trying to provide many of the same features is not a standard, nor portable, nor as reliable. But that could be said for all Microsoft's programs. If the native interface is working for you then stick with it. I myself prefer to use ASPI.
hmmm... yes, i've heard that before. So, ASPI is the one i'm going to use. 4.70 does not work for me (win2k and 2 IDE drives - teac 524E and pioneer dvd 16/40). 4.60 maybe?
Just out of curiosity... is there a significant difference between 4.70 and 4.60 'forceaspi'? Or, in other words, is there a reason why i should bother trying to make 4.70 work if i can just install 4.60...?
You can safely use 4.60. I don't know what's new with 4.70 but since it is giving so much trouble to everyone, the changes are probably not that good...
you can try copying the wnaspi32.dll from the windowssystem32 folder to the folder EAC is installed to. this has worked for a few people that had trouble with aspi 4.70 and EAC.
I copied the wnaspi32.dll to the EAC folder, but it was the same as before. Then i dumped the current aspi layer using forceaspi 1.7, and installed 4.60, but it still won't work... it seems i'll just have to stick with the 'native' stuff
Maybe helpful:
http://aspi.radified.com/ (http://aspi.radified.com/)
i have used both win2k and winxp's built in routines and have had no problems burning or ripping cds. i guess im lucky?
If you really want to install a layer, just get VOB ASAPI. It works just as well as Adaptec's 4.70 on my all SCSI system.
Poor VOB never gets any mention.