Problems with ASPI... Help needed...

Hi, everybody
After I installed ASPI (472a2 or so) layer on my WinXP, my CDRidentifier was unable to detect CD writer. Then I manually remove two files which ASPI installer copied to %windir% and CDRIdentifier works just fine. The same thing I get with EAC and even under Win2000.
The question is: ASPI installer adds some keys to registry, anybody knows, which they are?
Why are there problems with ASPI under XP, when Installer has option to install ASPI under XP? And after I installed ASPI, ASPIchecker say ASPI files missing. Why is this all happening?
 
Well tell the true bro I've had no problems under XP but does not help your case. Best thing to do is install aspi v 4.60 by the way thats what I use. Most user find this version more stable then any of these new released version out now.Once install remember to re boot pc B4 use. Try CompelAspi or force aspi ;)
 
Download ForceAspi,use the "killaspi" .exe to get rid of your 4.7x version,reboot,use Instaspi to install 4.60,reboot again,and I'm almost shure that your problem is gone.... ;)

PS:don't forget to turn of your virusscanner when performing these actions...:D
 

dx

1
ForceASPI is not warez. So use the files Zver provided, follow the html instructions and you'll be fine :)
 
I have already installed aspi 4.60 downloaded from ClonyXXL site, everything is OK, but I can try Zver's copy.
I have readed, that author of ForceASPI is forbiden from making ForceASPI anymore, so... :-(

For Zver:
You know, in Slovakia word zver means animal... :)
 

dx

1
If you use ForceASPI_17 it should work.

As an added security measure, use dumpASPI to backup your newly installed 4.60.1021 ASPI layer. This way you can use restASPI to restore it in case it gets wrecked for some reason. It's all in the Index.htm file. ;)
 
LTR1210B:

I got the following from Burnatonce FAQs. I think it is what you are talking about:

Uncompress Adaptec's ASPI 4.71 and copy "wnaspixp.dll" to "windows\system32\wnaspi32.dll".


Run Adaptec's ASPI 4.60 which should now install without complaint.


Optionally, run aspichk to confirm ASPI 4.60 is correctly installed.
 
Unfortunately aspichk just routinely sees if the necessary files are present, and not if the ASPI registry entries are intact- so it is not so reliable.
 
How do you ensure that the registry values are correct?? I mean, is there a utility that specifically corrects the ASPI-related entries?

OR, does anybody know the locations and values of the necessary entries so that it can be done manually with regedit?
 
If you open the ForceASPI scripts (.bat files) with notepad, you will find the registry strings needed.
Else, you could use the "Ahead Registry Checker" utility, which works quite well.
 
try this :

______________________________________________

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32]
"ErrorControl"=dword:00000001
"Type"=dword:00000001
"Start"=dword:00000002

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32\Parameters]
"ExcludeMiniports"=""

__________________________

Copy and save it into a registry file and merge it into your registry

Have fun
 
I have installed Adaptec's ASPI 4.60 and everything went OK. Then I download ForceASPI_17 and have found it is 4.60. So didn't install it.
Instead I have manually copied all ASPI files from 4.71 from Adaptec (not only two for XP, but all four files(I have used other two files for Win98)) and run registry update. Then aspichk said "ASPI installed correctly". Everything is OK now. EAC running, ClonyXXL running, CDrIdentifier running... :)
 
If you want to use aspi 4.70 in xp and above you'll only need two files... So what I usually do if moving from an 4.60 installation is run kill aspi...from ForceASPI_17 ..this will remove any traces of previous aspi

Reboot

install aspi 4.70 and above

merge the registry fix and walla...youre done after a reboot

if it still doesnt work try changing the
"Start"=dword:00000002
to
"Start"=dword:00000001
 
Top