Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I'm having trouble with one VxD in perticular, APIX.VxD, and device driver that loads at startup. When i run a program called Audio Catalyst, and trying to rip a track from a CD, it brings up the rip window for a split second before a blue screen fatal oe exception error in VxD APIX....what could be causing this and how could it be fixed???
Sorry if this double posts, don't think the first went through. See if this helps.
http://www.mcs.net/~revolutn/vxdfaq.htm
0 
It is caused by your cd ripper overwriting
some specific Adaptec software files.
Remove this ripper and reinstall your Adaptec software.Upgrade to the latest versions.
0
Which Adaptec files? I did a search for APIX.VxD and the files i saw there were Adaptec files, but the one i have has Microsoft written all over it *not litterally*. So which adaptec files should i update or if the APIX can be updated, where do i go to update????
0
Oke;
Here is the story:
Aspi drivers allow CDDA32 and DAT2WAV the ability to talk to the CDROM/DAT drives.
To let this happen windows is installing 4 files.
The four files windows 95/98 standard is installing are:( location on your hdd)Windows\System\Iosubsys\APIX.VXD
Windows\System\Winaspi.dll
Windows\System\Wnaspi32.dll
Windows\System\Aspi2hlp.sysThese files are from your windows95/98 CD.
If you install adaptec software; the last file would be renamed in Aspi2hlp.bak; or something like that.
Adaptec adds a new file :
Windows\System\Aspienum.vxd
(Aspienum = aspi real mode enumerator).Older aspienum.vxd files where famous for causing trouble( atapi devices versus scsi devices)
Thats the reason why you should upgrade to the latest version of lets say easycdcreator
or directcd.At this moment , the four files you need on your system are:
windows\system\iosubsys\apix.vxd
windows\system\winaspi.dll
windows\system\wnaspi32.dllAND ONE OF THE FOLLOWING TWO FILES:
windows\system\aspienum.vxd ( Adaptec)
or
windows\system\aspi2hlp.sysCHECK THIS !!!!
you can open aspienum.vxd with word and look for the version number.
Try to get version 4.60 (1017)or later.Check if these files are there or chanced by this ripper.
If you use software from adaptec , the adaptec file must be there.
Probably the ripper chanced the aspienum.vxdthe following might be happend:
windows istalls your 4 files.
After installing adaptec , the file aspi2hlp.sys is replaced by aspienum.vxd.
(should be no problem if you use the latest version).
Your cd ripper chanced or replaced one of the above 4 files.( probably aspienum.vxd)Benno.
0
Another option:
Did this ripper add another file?
Do you now have 5 instead of the four files you need?
If so : remove it.Remove any of this files on a location where they don't belong.
0
I downloaded the Adaptec ASPI files, with the files u mentioned and one or two more. However when i tryed to install them it tells me that i'm not running adaptec software blah blah blah. And i have all the files u mentioned except aspienum. I still get the error, and i'm forced to use either analog or mscdec or something to rip my CD, but i get a static finished mp3. Also, i got a low memory warning and decided to shut down and restart my computer...and i get ANOTHER VxD fatal exception error, and i had to press the power button. Its a VxD i've never seen before *not that i've seen many BEFORE a few days ago*. *sigh* how do i replace some of these obviously old and corrupted or plain fuxed up files?? The Adaptec won't let me do it cause i don't have an adaptec adapter or software......sorry to be such a pain...but i dunno what is going on
0
Well....
Most likely you find files with the following
names:
Aspienum.bak
aspienum.vxd.
Rename the first one in aspienum.vxd and rename the last one in aspienum.bak.Most likely you find files with the following
names:
Apix.bak and
Apix.vxdRename the first one in apix.vxd and rename the second one in apix.bak.
The same with the other files.
Start with chancing one file:
lets say apix.vxd.
Rename apix.bak in apix.vxd
rename apix.vxd in apix.bak.
Shut down and restart and look what is happening.
Still a mess?
Try renaming the following file:aspienum.vxd and aspienum.bak.And so on.
2
If this is not working:
Remove the Adaptec software and the cd ripper
software.
Remove all the files mentioned above.
Shut down.
Stick your startup disk in the floppydrive or LS120 drive and reinstall windows over the old windows.
This means that windows is replacing all system files with the ones that are on the win cd.
After this:Working fine now?
Check the above mentioned files.
Install Adaptec software.
Check what is chanced.
This should be no problem.
Install your ripper.
Check what has been altered.At this point you will probably get the same errors again.
Thats because Adaptec is using its own ASPI drivers instead of the Windows drivers.
If you only use Adaptec software this would be no problem.
If you than install software which uses windows aspi drivers you run into trouble because this windows aspi drivers are no longer there.The message is:
Use only Adaptec software.
Use only software wich uses the windows aspi drivers.3
There is still the possibility that your cd ripper files are corrupted or bad programmed.
After installing win again you can first install your ripper software and check if this is working fine.
If this is not the case you should not use it.
If it is working fine than install the adaptec software.
If you run in trouble again:
Use or Adaptec
or
cd ripperSucces
Benno.
0
Can anyone help me with my problem.
My Adaptec works fine, but I seem to have a problem when I try to use CDRWIN to make cd's from a *.bin file.
I've tried the ASPI thing, but it's still a problem.
Is there another program that does what CDRWIN does *.bin -> CD ???
0  |
 Replacing explorer.exe
|
RTL 8029(AS) Ethernet ada...
|
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
