Click to See Complete Forum and Search --> : ASPI could not initialize


PacMan
May 30th, 2002, 05:57 PM
Hi,
I have a iomega ZIP 650 cdrw drive. I’m running XP pro. Every time I burn a anything on it, it goes to 100% then freezes when it’s doing the “cover or labeling” part. I am using easy cd creator Platinum. Recently, I tried other programs and I got errors saying ASPI could not initialize. I downloaded this program called, “aspichk.exe (ASPI Installation Verification)” and I had the files “WNASPI32.DLL, WINASPI.DLL, ASPI32.SYS, and WOWPOST.EXE. The message, after running the program to check my ASPI said, “ASPI is properly installed, but it is unable to initialize. It is uncertain what has caused the failure(0xE4)”.

These 4 files, I manually put them in their windows\system, windows\system32\ and windows\system32\driver. Again.. this is on XP pro. Do I have to do anything to the registry?

If anyone has any idea or can recommend me to any software to help me troubleshoot this problem, plz help me. Thank you and I’m sure I left out some information you may need, so plz feel free to ask. Thank you.

Todo
May 30th, 2002, 06:33 PM
Well a few things, have you successfully been able to burn a CD, either data or audio. have you tried using different media. are you using CD R disks or CDRW. Have you downloaded the update to Roxio? take a look at this link:

<a href="http://www.roxio.com/en/support/roxio_support/ecdc/ecdc_xpFAQecdcv5p.html" target="_blank">roxio</a>

PacMan
May 30th, 2002, 07:15 PM
Hi Todo
Thanks. Yeah, back when I had 98 SE installed, I was able to burn both cd-r and cd-rw for audio and video. I did update easy cd creator to XP. It’s something to do with the ASPI, which I have no idea what is. Cause the program that checked my ASPI, found it to be installed correctly, but couldn’t initialize <img border="0" title="" alt="[Eek!]" src="eek.gif" /> . I have no idea what is going on. :rolleyes:

Todo
May 31st, 2002, 12:23 AM
</font><blockquote><font size="1" face="Trebuchet MS, Verdana, Arial, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Trebuchet MS, Verdana, Arial, Helvetica, sans-serif"> Hi Todo
Thanks. Yeah, back when I had 98 SE installed, I was able to burn both cd-r and cd-rw for audio and video. I did update easy cd creator to XP. It’s something to do with the ASPI, which I have no idea what is. Cause the program that checked my ASPI, found it to be installed correctly, but couldn’t initialize . I have no idea what is going on. </font><hr /></blockquote><font size="2" face="Trebuchet MS, Verdana, Arial, Helvetica, sans-serif">Okay, i've looked at the Microsoft KB. heres an article that might be related.
<a href="http://support.microsoft.com/search/preview.aspx?scid=kb;en-us;Q285910" target="_blank">article</a>
if it doesn't help, just look at the knowledge base for ASPI could not initialize

condor
May 31st, 2002, 02:40 AM
download and install the ASPI version 4.70

you can download it from <a href="ftp://147.234.1.253/pub/aspi_v470.exe" target="_blank">Here</a>

after you d/l the file run it, it will extract to c:\adaptec

open a command prompt and go to c:\adaptec\aspi

type:

install x86

this will reinstall an updated ASPI layer and should resolve your issues..

if you're still having problems after this update you might be using IDE drivers that make your IDE drives behavce like SCSI

in that case you must uninstall these drivers and use the native windwos driver. after a reboot your system should detect the hard drives and cd-roms again and ASPI function should gop back to normal.

if you include the system specs (chipset etc..)
we might be able to explain how to remove these drivers from your system.

good luck

NooNoo
May 31st, 2002, 04:58 AM
And don't forget to turn off native burning in xp, xp doesn't use aspi as such, and the native burning was written by roxio and clashes with easy cd - go figure!

GimpBizkit
June 5th, 2002, 09:28 PM
I had a similar problem that I was able to resolve by running the ForceAspi program that you can get <a href="http://www.doom9.org/software.htm#supportutils" target="_blank">here.</a>