|
Author
|
Topic: ASPI error hangs v1.82; Win2k - (Read 2 times)
|
Agent Cooper
Junior Member  From:
Registered: Apr 2003
Posts: 4
|
I recently upgraded from Windows 98 to Windows 2000 (fresh reinstall), installed Audiograbber 1.82, and have been unable to rip tracks ever since.When I try to rip a track, the entire system hangs (even the mouse) for several minutes. Eventually it returns with "Aspi error" in the information field of the track list. I'm using a Plextor PlexWriter IDE drive that worked fine in MSCDEX mode, Win98. I installed the latest ASPI drivers from Adaptec. Here's the info from aspichk: ASPI32.SYS v4.71.2
WOWPOST.ECE v4.6 (1021)
WINASPI.DLL v4.6 (1021)
WNASPI32.DLL v4.71.2 "ASPI is properly installed and fully operational." Any ideas? Does Audiograbber keep a detailed log file anywhere? This has rendered the product useless and is very frustrating. Thanks,
Cooper
|
KevinB52379
Member From:
Registered: Jun 2001
Posts: 208
|
I see a problem already. Different file versions? you have two aspi layers mixed in. Search for a program called forceaspi. run the killaspi restart computer. then run installaspi, and reboot. problem should be solved now. ------------------
Kevin B.
|
moonroy
Administrator From:Sweden
Registered: Jan 99
Posts: 2158
|
And also, on WinNT/2K/XP it is always nice to be logged on as administrator while ripping. With an aspi layer properly installed it shouldn't matter, but when it comes to windows you never know...------------------
moonroy www.mp3.com/enuresis
|
gee_wiz
Junior Member From:hell
Registered: Apr 2003
Posts: 9
|
Sorry to intrude on your thread Agent cooper, I am having a similar problem in windows xp with the aspi error in Audiograbber 1.82, I ran the force aspi utility, and then checked to make sure my aspi was correct (version 4.60) Does anyone have any insight to what my problem may be?
|
tappel
Member From:New York, USA
Registered: Sep 2001
Posts: 88
|
gee_wiz: did you try the suggestion of using killaspi and then rebooting/reinstalling? I once had some real weirdnes on my Win2k machine and that did the trick.With that said, there seem to be some persistent problems with aspi and AG on XP/2000 machines and I, for one, have no real answers. I recently had to do a total reinstall (new PC) of Win2k -- I didn't install aspi, I'm using Win 2000 calls; -- and AG is working fine. That never happened before, I always had to use aspi. Go figure.
|
Agent Cooper
Junior Member From:
Registered: Apr 2003
Posts: 4
|
Tappel:"I didn't install aspi, I'm using Win 2000 calls; -- and AG is working fine" Huh? Please enlighten me on "using Win 2000 calls". Is there some option besides ASPI or Analog ripping? I figured the mis-matched file versions were "normal" for that ASPI release; I'll try the forceinstall and see if it works. Thanks,
Cooper
|
Agent Cooper
Junior Member From:
Registered: Apr 2003
Posts: 4
|
OK, I've tried two things:I used forceASPI to install version 4.60. I did this properly: killaspi, reboot, install, reboot, verify version numbers. AG still hangs when ripping. Then I blew away 4.60 with killaspi, rebooted, and installed the 4.71.2 drivers from Adaptec. Aspichk.exe again shows mixed version numbers: 4.71.2 and 4.60. I have to assume those versions are correct, and two of the files simply weren't updated between 4.60 and 4.71.2. In any case...AG still hangs the computer. - Cooper
|
Agent Cooper
Junior Member From:
Registered: Apr 2003
Posts: 4
|
OK, I seem to have solved my problem.What I had to do was a) install the ASPI manager 4.71.2 and b) select "Call drive via ASPI manager" in the ASPI tab. Until I deleted and reinstalled the ASPI manager, I couldn't select "use ASPI manager." The selection "use Win NT/200 calls" was forced...and that seems to be why I was hanging. Thanks for the help guys,
Cooper
|
moonroy
Administrator From:Sweden
Registered: Jan 99
Posts: 2158
|
Great that you fixed it yourself! Strange though that ASPI wouldn't work for you!? Using win98 and ASPI it previously worked for you, right?------------------
moonroy www.mp3.com/enuresis
|
gee_wiz
Junior Member From:hell
Registered: Apr 2003
Posts: 9
|
Hello, Im glad that Agent Coopers problem was fixed, but mine wasnt, yes I did the kill aspi command correctly, with the reboots and all, maybe I need to do what Agent Cooper did, but alas, I am only an idiot.
|
cb7
Junior Member From:
Registered: Dec 2000
Posts: 8
|
Howdy,I tried Agent Cooper's solution but it didn't work. However, ForceASPI worked for me. I previously had installed the Adaptec 4.71.2 ASPI layer, but it still wouldn't let AG (1.82build2) use ASPI calls to my CDRW drive. So I went and got ForceASPI. I ran the killaspi.bat, rebooted, and ran chkaspi to determine that indeed ASPI was gone (and it was.) Then I ran instaspi.bat, and rebooted. Then I fired up AG, and voila, I am now able use ASPI calls to the CDRW drive, and have encountered zero ASPI read errors since then. Life is good! Running chkaspi again, I noted that ForceASPI uses ASPI layer version 4.6, which many have said is the "latest stable" version. Sounds good to me (literally!) This is the hardware I'm running on: Athlon XP Barton 2500+
2x256MB Samsung PC2700 DDRAM CAS2.5
MSI K7N2 Mainboard
MSI VTD8X AGP card
Chaintech generic 6-channel soundcard
Maxtor 80GB ATA133 7200RPM
Maxtor 30GB ATA100 7200RPM
Plextor Plexwriter 48x24x48 (internal IDE), which I was about to return, thinking it was defective, until I tried the ForceASPI!! Best of luck to you, Chuck
|
UBBFriend: Email This Page to Someone! 
Click here to bookmark this thread!
Audiograbber Forums
posted 05 April 2003 11:05 
posted 05 April 2003 16:16