Wait one...something wrong here
U say the 'wnaspi32.dll' is in the Nero folder ONLY?
Nero proggies do use their own ASPI layer so this file must remain where it is...
...BUT there should
also be a file with the same name in the windows 'system32' dir.
Symptoms such as the one U got (CD-ROM drives not found) are typical of an improperly installed or configured ASPI layer.
In fact these are the correct paths for the 4 files I mentionned in my previous post (for WINDOWS
2000/XP in general, regardless of whatever burning software is installed):
c:\*WINDIR*\system32\
wnaspi32.dll
c:\*WINDIR*\system\
winaspi.dll
c:\*WINDIR*\system32\drivers\
aspi32.sys
c:\*WINDIR*\system\
wowpost.exe
where *WINDIR* is either 'windows' or 'winnt' according to the OS (I'm not sure what it is for WinXP).
Usually these 4 files are 'adaptec' version, but this is not compulsory, at least not for 'wnaspi32.dll'.
It seems that 2 files are also missing, 'wowpost.exe' and 'winaspi.dll', so U might have to reinstall ASPI layers. However this U should know:
-
in theory the only adaptec ASPIs for Win2k and WinXP are versions 4.7xx (versions 4.6xx and below are for Win9x and WinNT only).
-
in practice ASPI versions 4.7xx are known to be riddled with bugs that cause read/write problems, and many claim to have solved these by replacing them with v4.6, even though they had Win2k or WinXP!
- Adaptec states that version 4.71.
2 is stable. Since U have that version, keep it - at least for now
So this I suggest: install (the full) ASPI 4.71.2 and reboot. You can download it
here .
After reboot make sure all 4 files have the same correct version (4.71.2) and are in the appropriate paths.
If you still have the same problems, then this you will try:
The registry you will open, and this key you will find:
'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi ces\Aspi32\Parameters'. There should be a string-type value called 'ExcludeMiniports'. IF this value is not empty, right-click modify it and delete its content. Reboot should not be necessary.
Normally these 2 aforementionned tips (install full ASPI and check the reg key) should help.
But if it doesn't...well then fate is really hounding you, isn't it?
In that case you could try reverting back to ASPI 4.6, but that's a triffle more complicated since you will need to download a package of DOS programs that includes 'killASPI' and 'forceASPI', in addition to the ASPI 4.6. There was a thread in this same forum, posted over a week ago, check it out if installing ASPI 4.7 and the reg tip didn't help.
PS. about the firmware stuff: a device's firmware is its BIOS, exactly like that of the mainboard. So it is of utmost importance since that's what interacts with the OS drivers. Towards the end of my previous post I included a link to a firmware page, I don't know if you followed it.
However judging by what U said this prob has nothing to do with the firmware, all the more so than the 2 drives U've got are quite recent, so there is no need 2 bother much about the firmware...
Nope, this prob is definitely ASPI-related, so good luck m8 - U might need it
Quote:
|
Don't put off till tomorrow what you can put off till day after tomorrow
|