|
Failed to Initialize ASPI Device
|
|
|
morgainee
Newbie
|
20. February 2006 @ 17:00 |
Link to this message
|
|
I am almost computer illiterate except that I can use Dvd Shrink and Nero 6. Now, my DVD Shrink has the above error and I have managed to download other ASPI devices and remove, and reload the DVD Shrink program several times. I don't know how to do much else except use the DVD Fab or Decriptor with the above two programs. I need some help with the ASPI Device problem, but unfortunately, it has to be in pretty simple terms. These things about layers and all that, are above me, but I have read and done everything I can find to do on my own. I have been to every website I can find. I don't know how to use Nero without Shrink first. I have spent hours on this and am frustrated and out of ideas. Please help.
Thanks,
Morgainee
|
|
Advertisement
|
 |
|
|
Moderator
3 product reviews
|
20. February 2006 @ 17:51 |
Link to this message
|
|
Senior Member
|
20. February 2006 @ 18:06 |
Link to this message
|
The aspi driver that comes with nero maybe corrupt. What you can try and do is perform a search on your PC for the WNASPI32.DLL file, once found delete it. Download the new WNASPI32.DLL file from the link provided and use it in its place, reboot the PC after the file has been replaced.
http://ww2.nero.com/nero6/enu/WNASPI32.DLL.html
NOTE: If using nero6, you should be running version 6.6.0.18 and not the current 6.6.1.4 (will not autoburn when used with shrink).
This message has been edited since posting. Last time this message was edited on 20. February 2006 @ 18:06
|
|
morgainee
Newbie
|
20. February 2006 @ 23:06 |
Link to this message
|
I managed to download the adaptec but could not get the WNASPI32.Dll to load for anything. I tried everything and finally sent an e-mail to the msn support to see if they could tell me what the problem was. I am running the updated version of the Nero. I just updated it about 3 days ago and I don't know if you can go back to the other version once you've updated it, can you? How? Will Neroping.exe be of any help? Also, what is WMA plug in? Does that have to do withthe shrinking? This is all so confusing! I should more technical and less artistic I guess! Thank you so much for your help. Maybe between us I can get this thing up and running again!
Thank you so much,
Morgainee
|
Senior Member
|
21. February 2006 @ 04:46 |
Link to this message
|
Lets start over and try this:
As I stated above, If using nero6, you should be running version 6.6.0.18 and not the current 6.6.1.4 (will not autoburn when used with shrink). Uninstall nero from your system using the nero general cleantool found here then reboot the PC:
http://ww2.nero.com/nero6/enu/General_CleanTool.html
Next, install nero version 6.6.0.18, here are the links:
http://httpdl2.usw.nero.com/Nero-6.6.0.18.exe
http://httpdl1.usw.nero.com/Nero-6.6.0.18.exe
To make sure you're using the current version of DVDshrink, download it from here (english zip file):
http://www.mrbass.org/dvdshrink/
And last, to make sure your ASPI layers are installed and operating correctly, download force aspi from the link provided, you'll also find instructions on use.
http://radified.com/ASPI/forceaspi.htm
EDIT:
Here's a guide for using nero to burn your video files to disk without using shrink for the autoburning process.
burning with nero
http://www.dvd-guides.com/content/view/40/59/
If you proceed as I have described, your problem should be no more.
Take your time and do it right, Good Luck.
This message has been edited since posting. Last time this message was edited on 21. February 2006 @ 05:34
|
|
morgainee
Newbie
|
21. February 2006 @ 20:15 |
Link to this message
|
I have successfully installed Nero and ASPI. Now when I try DVD Shrink it comes up with an error and cannot continue. Fail to initialize ASPI Device. When I check Nero info. tools it says ASPI is installed and working properly. Somehow even after removing and reinstalling DVD Shrink and the ASPI Device this exact error still comes up no matter what else I change. I think I'll just give up on this one. I took my time and did it right three times last night, from 8pm - 1am and no success...
Thank you so much for your help and for your precise directions. Wish they had worked. I'll read up on burning with just Nero. If you know of anything else give me a shout.
Morgainee
|
Moderator
3 product reviews
|
21. February 2006 @ 21:25 |
Link to this message
|
|
|
morgainee
Newbie
|
23. February 2006 @ 11:46 |
Link to this message
|
I have tried ForceASPI and DVD Shrink still doesn't recognise the device. Thank you for all your help. I've learned a lot though.
Morgainee
|
Junior Member
|
10. March 2006 @ 20:10 |
Link to this message
|
Maybe some of this's a bit off thread but couldn't resist adding onto my comments.
wnaspi32.dll comes up as missing when opening DVDIdentifier and WinDVD5 downloaded it from http://www.dll-files.com/dllindex/dll-files.shtml? The wnaspi32.dll download then was again offered by an un-named popup window w/this link http://www.dll-files.com/dllindex/download.php?wnaspi32download0U...
It informs users...
We recommend you to unzip the file to the directory of the program that is requesting the file. If that doesn't work, you will have to extract the file to your system directory. By default, this is
C:\Windows\System32 (Windows XP). It denotes other system's directories too.
Reboot your computer
If the problem still occurs, try the following:
1. Press Start and select Run
2. Type CMD and press Enter
3. Type regsvr32 "filename".dll and press Enter
=======================
Initially I still was getting the error after installing this dll, even after re-booting, and even after then trying the 'Run' thingy and re-booting. It didn't seem to work as it just kept re-printing out the initial line it prompted me with and I still got the 'missing..' error.
Even though I'm oddly no longer getting the 'missing..' error, I find
that the dll is no longer seen in my system32 folder. Maybe it will stick this time as I replaced it again today (before downloading ForceASPI).
Oddly again, I finally discovered another wnaspi32.dll in my D:\Program Files\Fogware E-mail Backup (program's) folder! And having found no Winaspi.dll (which is supposed to be in my C:\WINDOWS\System folder), nor did I find the other two ASPI files (or layers) on my system either (XPHome/SP2/Sony VAIO) even though for the most part, things seem to be doing well enough using only Click to DVD in conjunction with DVDIdentifier, DVDDecrypter and DVDShrink.
But as my OEM optical drive has always been very picky about what it will play, sometimes refuses to play at all, I resolved to reading up on this ASPI thing and am in process of using it, even though I also expected to see it as a program in add/remove and didn't.
I also use a LG' GSA 5160D super multi rewriter that woks very well, and I use (which I wouldn't recommend as its a piece of trash that you're lucky if it works out of the box, let alone for more than 8 weeks, as I'm into my third replacement of it already) a LiteOn VHS-DVD recorder LVC-9006.
|
Senior Member
|
12. March 2006 @ 23:26 |
Link to this message
|
Die CMC Mag!!! |
Junior Member
|
13. March 2006 @ 03:40 |
Link to this message
|
Thanks for the reply.
Your avitar, animated GIF or whatever is an absolute riot.
Since my post, I installed ASPI and used ASPICHK to confirm the installs.
Still no joy as my Pioneer drive still refuses to play or even recognize a perfectly playable disc is inserted.
As I read about another Sony computer user who reports after uninstalling his Sony XCP Trojanware, he has restored his DVD capabilities which were exactly like mine.
As such, I've been looking into the XCP and MediaMax fiasco that Sony, BMG and I think even Columbia have covertly installed their Trojans w/o EULA notice or uninstalls.
I'm now trying to figure out if I have any of this crap on my system even though my googling on which CD's are known to have infected users systems didn't list anything I've played on my machine, and even though I've since formatted last September, in that I still have 40 Gb of downloaded and copied music, it seems easier to try and check if I have the Trojan(s) than continuing to google the purveyors of that crap.
I ran across one blog where its recommended to simply try to rename your favourite ripping software as $sys$whatever.exe and then run it again. If you notice that the DRM system can no longer detect it, and thus you'll get good copy of the track you try to rip instead of one filled with noise, this is positive proof the OS has been infected by the XCP or MediaMax trojan.
But I don''t know what it actually means where it says "If you notice that the DRM system can no longer detect it". My duh-ness is showing.
Thanks again for the reply.
|
Senior Member
|
13. March 2006 @ 05:21 |
Link to this message
|
@wguru
Wow. Youve done some good research on this. Id have to see that blog to fully understand what they are talking about, and maybe even then i wouldnt understand :)
I would look for a rootkit or trojan detector and run that rather than messing with renaming files. Ive probably got that on my system too as i was a BMG club member back in the days, and i ripped many of those originals to my HD. I just use McAfee anti-virus and it hasn't found anything so far, but im not sure it can find these types.
You could also try un-installing the driver for that burner, and rebooting the system. Windows will detect it, and install the drivers on reboot.
We haven't seen a Nero log, so i cant say what else may be going on.
Die CMC Mag!!!
|
Junior Member
|
13. March 2006 @ 13:16 |
Link to this message
|
No Anti-spyware detects rootkit Trojans and in this case it is reported that Sony has already gotten to the antispyware co's and XCP is puposely being overlooked by anti-spyware scanners.
As for trying rootkit scanners, I'm thinking there are so many legitimate rootkits out there that it chancy to expect on of the 16 or so to detect XCP As and as I couldn;t/didn;t find a scanner advertising it does detect XCP, I'm holding off on going that route.
And besides, even if you knew the XCP exe's name and one tried deleting it from the system, there's obviously the likelihood that its basically boobytrapped with a drivers that are unsafe to unload w/o rebooting (i.e.; crashes your system).
With respect to that, I read that it's never safe to unload a driver that patches the system call table (since some thread might be just about to execute the first instruction of a hooked function when the driver unloads); if that happens the thread will jump into invalid memory. There?s no way for a driver to protect against this occurrence, except I did find a suggestion that might resolve that threat.
However, while researching these Trojans involved with a number of CD's made by Sony, Columbia and BMG (which install First 4 Internet DRM, XCP and/or Sunncomm's MediaMax), I ran across a blog which poses an interesting solution for users who might incur a systems crash when unloading a driver that patches the system call table.
As it's never safe to unload a driver that patches the system call table (since some thread might be just about to execute the first instruction of a hooked function when the driver unloads); if that happens the thread will jump into invalid memory. There?s no way for a driver to protect against this occurrence.
So it should be possible to allocate some non-pagable memory, write a couple of assembly instructions to it that checks a state variable and jumps to the detour or to the original function?
The service dispatch table would point to this assembly code instead of pointing directly to the detour function. Then the driver could be unloaded without any risk.
Until I find more out, and maybe find something that will detect this particular crap, I'm leaning towards the unmasking trick using only something I don't mind running w/o my control over it.
When this stuff runs, however its set up to start with is the way it will run forever (updates, phonong home, etc., etc.).
Again I'm hoping that as I don't ever recall having seen a EULA when playing a Sony, etc., music CD (note the EULA doesn;t disclose the rootfit and that the only reason Sony was successfully sued) that maybe I didn't accept a such EULA from SonicStage, or other programs Sony has engraced me with.
So I'm only guessing that I have about a 50-50 chance at having it on my OS.
|
Junior Member
|
13. March 2006 @ 13:28 |
Link to this message
|
|
I meant to instead to say "No Anti-spyware detects rootkit Trojans "which the maker has gotten to the anti-spyware makers"'.
|
Junior Member
|
13. March 2006 @ 13:42 |
Link to this message
|
|
|
|
Advertisement
|
|
|
Senior Member
|
17. March 2006 @ 12:58 |
Link to this message
|
@wguru
You have gotten into this rootkit thing much deeper than i have. I did run a rootkit detector, and it didnt find anything except klitecodec.exe and Pgcedit.exe but i know what those are.
Here is the scanner i used.
http://www.sysinternals.com/Utilities/RootkitRevealer.html
Good luck, and keep us informed as to what you find on these rootkits.
Die CMC Mag!!!
This message has been edited since posting. Last time this message was edited on 17. March 2006 @ 12:58
|
