Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Problem with ASPI-layer (Read 5704 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Problem with ASPI-layer

I appear to be having a problem with my ASPI-layer (and i am using Windows XP).

This is reported in Feurio:
Quote
WARNING: CD-ROM-device(s) were not detected by the ASPI-manager!

You have configured the access mode "ASPI" for Feurio!, i.e. Feurio! uses the ASPI-manager for accessing the devices.

But Feurio! noticed, that the drive(s): "F:\, G:\, I:\" were not detected by the ASPI-manager - so Feurio! can't access this/these drive(s).
Probably your ASPI-manager isn't up-to-date, or you're using USB- or Firewire-drives, that are not recognised by the ASPI-manager.

To use this/these drive(s), either you can update the ASPI-manager, or toggle the access-mode of Feurio! to "DeviceIoControl". To do this, please select at the menu "Program" the entry "Program parameters", then select the property sheet "Access mode" - there select "DeviceIoControl".


And the system diagnosis shows this:
Quote
The ASPI-driver consists of inconsistent versions.
The different files of the ASPI-driver installed on your system have different version numbers.
Most probably an update has been installed incompletely!
PLEASE INSTALL THE ASPI-DRIVER AGAIN!


But i have tried installing the ASPI layer several times (both ASPI v4.71.2 and Force ASPI 1.7). And i have used Force ASPI's "killaspi" to remove old versions before i installed. It still doesn't seem to work. I have read that i can use the DeviceIoControl access mode instead. But when i do that, my drives does not appear in the device-list (only my virtual drives).

I don't know whether it matters, but my drives are: A S-ATA harddrive (boot drive) with two partitions. My CD-Writer as primary master. My CD-ROM as primary slave. A harddrive with a single partition as secondary master.

Problem with ASPI-layer

Reply #1 –
Quote
I appear to be having a problem with my ASPI-layer (and i am using Windows XP).

This is reported in Feurio:
Quote
WARNING: CD-ROM-device(s) were not detected by the ASPI-manager!

You have configured the access mode "ASPI" for Feurio!, i.e. Feurio! uses the ASPI-manager for accessing the devices.

But Feurio! noticed, that the drive(s): "F:\, G:\, I:\" were not detected by the ASPI-manager - so Feurio! can't access this/these drive(s).
Probably your ASPI-manager isn't up-to-date, or you're using USB- or Firewire-drives, that are not recognised by the ASPI-manager.

To use this/these drive(s), either you can update the ASPI-manager, or toggle the access-mode of Feurio! to "DeviceIoControl". To do this, please select at the menu "Program" the entry "Program parameters", then select the property sheet "Access mode" - there select "DeviceIoControl".


And the system diagnosis shows this:
Quote
The ASPI-driver consists of inconsistent versions.
The different files of the ASPI-driver installed on your system have different version numbers.
Most probably an update has been installed incompletely!
PLEASE INSTALL THE ASPI-DRIVER AGAIN!


But i have tried installing the ASPI layer several times (both ASPI v4.71.2 and Force ASPI 1.7). And i have used Force ASPI's "killaspi" to remove old versions before i installed. It still doesn't seem to work. I have read that i can use the DeviceIoControl access mode instead. But when i do that, my drives does not appear in the device-list (only my virtual drives).

I don't know whether it matters, but my drives are: A S-ATA harddrive (boot drive) with two partitions. My CD-Writer as primary master. My CD-ROM as primary slave. A harddrive with a single partition as secondary master.
[a href="index.php?act=findpost&pid=240934"][{POST_SNAPBACK}][/a]


I would definitely recommend you to install Adaptec's 4.60 ASPI version. 4.7x are known to have a lot of problems including installation. 4.60 "just works", and I have it installed and working fine on MANY computers...

You can download it from many places, including Adaptec, but there are tricks to getting it installed if you don't actually have an Adaptec SCSI adapter in your PC. Just Google to find instructions. If you have problems, post back here and I'll try to help.

Problem with ASPI-layer

Reply #2 –
But doesn't Force ASPI use ASPI v4.60?

Problem with ASPI-layer

Reply #3 –
I just noticed that Force ASPI copies all the files to C:\Windows. That isn't the correct folder for Win XP, is it?

Problem with ASPI-layer

Reply #4 –
Quote
But doesn't Force ASPI use ASPI v4.60?
[a href="index.php?act=findpost&pid=240938"][{POST_SNAPBACK}][/a]


Don't know, never used it...

Problem with ASPI-layer

Reply #5 –
Quote
I just noticed that Force ASPI copies all the files to C:\Windows. That isn't the correct folder for Win XP, is it?
[{POST_SNAPBACK}][/a]

Aspi files normally are in 'C:\Windows\system32\' or 'C:\Windows\system32\drivers' that mostly have a higher system priority than the 'C:\Windows' directory. So maybe check these two folders maunally for obsolete aspi files that may cause conflicts.
After removing existing aspi and Feurio files/software try to install [a href="http://www.adaptec.com/worldwide/support/suppdetail.jsp?sess=no&language=English+US&prodkey=ASPI-4.70]Adaptec's Aspi[/url] and Feurio again.

As far as i have seen now i also have a mix of Aspi versions on my system:
Aspi32.sys :  4.71.2
WowPost.exe : 4.6 (1021)
WinAspi.dll :  4.6 (1021)
WnAspi32.dll : 4.71.2
However it works fine like this.

Problem with ASPI-layer

Reply #6 –
Quote
I just noticed that Force ASPI copies all the files to C:\Windows. That isn't the correct folder for Win XP, is it?
[a href="index.php?act=findpost&pid=240940"][{POST_SNAPBACK}][/a]



I think you actually want the .dlls in the windows\system32 folder. dropping the nero .dll in that folder is always a solution to consider if that doesn't solve it.(the vob/pinnacle asapi shouldn't conflict and comes with an installer, although i'm not sure it's supported by the same range as adaptec.)


384 beat me to the punch on the folder

Problem with ASPI-layer

Reply #7 –
Quote
Quote
I just noticed that Force ASPI copies all the files to C:\Windows. That isn't the correct folder for Win XP, is it?
[{POST_SNAPBACK}][/a]

Aspi files normally are in 'C:\Windows\system32\' or 'C:\Windows\system32\drivers' that mostly have a higher system priority than the 'C:\Windows' directory. So maybe check these two folders maunally for obsolete aspi files that may cause conflicts.
After removing existing aspi and Feurio files/software try to install [a href="http://www.adaptec.com/worldwide/support/suppdetail.jsp?sess=no&language=English+US&prodkey=ASPI-4.70]Adaptec's Aspi[/url] and Feurio again.

As far as i have seen now i also have a mix of Aspi versions on my system:
Aspi32.sys :  4.71.2
WowPost.exe : 4.6 (1021)
WinAspi.dll :  4.6 (1021)
WnAspi32.dll : 4.71.2
However it works fine like this.
[a href="index.php?act=findpost&pid=240949"][{POST_SNAPBACK}][/a]


While you say you're not having problems, I can definitely say as an experienced SCSI user that it is not a wise idea to have multiple ASPI versions installed in Windows. It's OK that certain programs have their own ASPI layer, this can be quite common... Nero for example has one. But these are only used by that particular program, not Windows in general, because they are usually not full ASPI implementations... they usually only implement the functions that particular software needs. And they are NOT installed in the Windows or Windows system folders, they are usually in the program's own folder, or a sub-folder.

I would recommend you use the Nero info tool, which has a useful ASPI checker. It will display the ASPI versions installed and tell you quickly if ASPI is working or not. You will normally have 4 ASPI files: wnaspi32.dll, aspi32.sys, winaspi.dll, wowpost.exe. It is not a good idea to have different versions mixed here.

While some people use the later 4.7x versions from Adaptec, they are not the most reliable or stable. Sometimes the installer doesn't even properly install the APSI files or create the proper registry settings. Adaptec's ASPI 4.60 is the most stable and reliable version, and works fine in XP.

Edit: Here are the file paths on my XP system:

aspi32.sys is in \windows\system32\drivers
winaspi.dll is in \windows\system
wnaspi32.dll is in \windows\system32
wowpost.exe is in \windows\system

Problem with ASPI-layer

Reply #8 –
Use the Google search link below to find a download site of your choice for the .reg file that allows Adaptec's ASPI to work with Win2K and WinXP:
ASPI Fix

Problem with ASPI-layer

Reply #9 –
Quote
Use the Google search link below to find a download site of your choice for the .reg file that allows Adaptec's ASPI to work with Win2K and WinXP:
ASPI Fix
[a href="index.php?act=findpost&pid=241122"][{POST_SNAPBACK}][/a]


The point is, if you use Adaptec's 4.60, you don't need the "fix"! The fix is only needed when you use the new broken 4.7x installation.