Nero can't find CD-Writer in Win2K - plz help
- Thread starter borogovio
- Start date
cdorders
1
Oh yes he need the drivers! I've got two Asus mainboards with VIA 694X-DP chipset that they perform better with VIA drivers. The same goes with Elite, Gigabite and any other mainboard based on the VIA 133/133A chipset that works under Win2k. OnlyWinXP support the all the mainboard devices perfectly!!!
cdorders
1
Since you own a parallel drive, update your ASPIs to v4.71 (NOT v4.70 because it's buggy). Reinstall Nero and be sure that it's the latest version and uses an unblacklisted serial. Check also if your drive is ok with other machines (to assure it's not faulty or broken). Then let me know again.
cdorders:
* The drive works nicely with Nero in this same PC when I boot in Win98, or in my older PC (also Win 98). Furthermore, it works in Win2k with NTI CD-maker
* I'm using Nero 5.5.8.2 (latest as far as I know), with the serial downloaded both from h++p://w*w.cdrsoft.cc . I guess it's not a blaclisted serial, as other features - like the wav editor - do work.
* I've installed the ASPI 4.60 or 4.70 or 4.71, but no luck
* I'm pretty sure now it is related with the communications via the parallel port, as the scanner part of the printer is also not working in Win2K
* The drive works nicely with Nero in this same PC when I boot in Win98, or in my older PC (also Win 98). Furthermore, it works in Win2k with NTI CD-maker
* I'm using Nero 5.5.8.2 (latest as far as I know), with the serial downloaded both from h++p://w*w.cdrsoft.cc . I guess it's not a blaclisted serial, as other features - like the wav editor - do work.
* I've installed the ASPI 4.60 or 4.70 or 4.71, but no luck
* I'm pretty sure now it is related with the communications via the parallel port, as the scanner part of the printer is also not working in Win2K
cdorders
1
Check the the drivers for the port of Win2k. There must be a problem with the drivers, since the drive performs well in Win98. If possible, remove the port and reinstall it. Try using the drivers bundled with the CD Rom of your mainboard. But remember for Win2k removing and then reinstalling from the beggining a device can be most of the times a solution to any problems caused by it. 
Hi Guys,
CDorders, there is no use trying to make this drive work on 2k. It doesn't work at all. My experience with all way of installing the drivers ended in my screen becoming blue. Borogovio had more luck than me. As you can see it has to do with the motherboard. I tried to install the drivers from HP on a COMPAQ ARMADA Portable using win 2k, result blue screen, no matter what I did. Now I tried it on a SOYO and the result was identical. Another "strange thing is that I could use it, on the portable, as a CD-ROM, but not as CD-Writer. Every where I looked for information the result was the same, it doesn't work. So I believe it is no use. What keeps me thinking and thinking is why in the case of Borogovio it works with NTI and in my case on the portable it was seen as a CD-ROM.
The good news is tha I make it work on XP using the drivers from HP and reinstalling the ASPI Layer manualy. It works perfectly with NERO (and Express) and (sorry for using it, but wanted to test it myself) Win ON CD 5.02. In both burning engines i got a good working CD.
My advice would be, use XP, altough I would recomend to stay with 2k and burn using 98. The probability of getting coasters is higher, but I think you can live with it. Make the right choice and happy burning .
Cheers,
El_Matador
CDorders, there is no use trying to make this drive work on 2k. It doesn't work at all. My experience with all way of installing the drivers ended in my screen becoming blue. Borogovio had more luck than me. As you can see it has to do with the motherboard. I tried to install the drivers from HP on a COMPAQ ARMADA Portable using win 2k, result blue screen, no matter what I did. Now I tried it on a SOYO and the result was identical. Another "strange thing is that I could use it, on the portable, as a CD-ROM, but not as CD-Writer. Every where I looked for information the result was the same, it doesn't work. So I believe it is no use. What keeps me thinking and thinking is why in the case of Borogovio it works with NTI and in my case on the portable it was seen as a CD-ROM.
The good news is tha I make it work on XP using the drivers from HP and reinstalling the ASPI Layer manualy. It works perfectly with NERO (and Express) and (sorry for using it, but wanted to test it myself) Win ON CD 5.02. In both burning engines i got a good working CD.
My advice would be, use XP, altough I would recomend to stay with 2k and burn using 98. The probability of getting coasters is higher, but I think you can live with it. Make the right choice and happy burning
.Cheers,
El_Matador
cdorders
1
Ok, then borogovio you probably have to burn in 98 and keep your Win2k as it is. I believe there is no problem switching to 98 for writing only, right? I think it's the best thing to do, as also mentioned by El_Matador. I would not recommend you to go for XP. Keep your current system OSes but burn in 98.
Just wanted to post in this thread. I just recently got a HP DVD200e (HP DVD200j) Ricoh OEM DVD+RW drive which comes with both Firewire and USB but it's connected by Firewire. ForceASPI 1.7 (Adaptec 4.60 (1021) using KILLASPI followed by INSTASPI sees everything on my SCSI/IDE bus including my SCSI scanner except for the Firewire drive. using KILLASPI followed by install xp32 and then the following registry patch for Adaptec 4.71 had the same results as 4.60 (1021). This patch is required for certain programs seeing the drive. Nero 5.5.9.0 sees the drive fine without using ASPI. EZ CDCreator 5.1 Platinum/DirectCD 5.1 won't see the drive until one runs the Drive Support 5.1j update. DiscJuggler 4.00.1020 sees the drive with no problems as well. CDRWin 3.9a, Feurio! 1.6.5 as well as CDRIdentifier 1.63 can't see the drive via ASPI at all.
Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32]
"ErrorControl"=dword:00000001
"Start"=dword:00000002
"Type"=dword:00000001
"MatchFlags"=dword:00000000
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
72,00,69,00,76,00,65,00,72,00,73,00,5c,00,61,00,73,00,70,00,69,00,33,00,32,\
00,2e,00,73,00,79,00,73,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32\Parameters]
"ExcludeMiniports"=""
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32\Enum]
"0"="Root\\LEGACY_ASPI32\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001
This is the exact message from Feurio!, anyone have any ideas since it seems that Adaptec's ASPI layer only supports SCSI/IDE devices or maybe additional registry entries needs to be changed, added. I am running WinXP Pro.
WARNING: CD-ROM-device(s) 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): "J:\" 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"
Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32]
"ErrorControl"=dword:00000001
"Start"=dword:00000002
"Type"=dword:00000001
"MatchFlags"=dword:00000000
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
72,00,69,00,76,00,65,00,72,00,73,00,5c,00,61,00,73,00,70,00,69,00,33,00,32,\
00,2e,00,73,00,79,00,73,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32\Parameters]
"ExcludeMiniports"=""
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Aspi32\Enum]
"0"="Root\\LEGACY_ASPI32\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001
This is the exact message from Feurio!, anyone have any ideas since it seems that Adaptec's ASPI layer only supports SCSI/IDE devices or maybe additional registry entries needs to be changed, added. I am running WinXP Pro.
WARNING: CD-ROM-device(s) 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): "J:\" 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"
Just an update...
I found a solution that is working for Feurio! 1.65, CDRWin 3.9a, and Exact Audio Copy 0.9 Beta 4 getting the drive to show up and working but CDRIdentifier v1.63 still doesn't see the drive so maybe it's a limitation of CDRId. What I did was put WNASPI32.DLL in C:\WINDOWS\SYSTEM32 from Nero ASPI from w*w.cdspeed2000.com since it seems like Adaptec ASPI 4.60 and 4.71 isn't able to support Firewire/USB devices but SCSI/IDE only.
I found a solution that is working for Feurio! 1.65, CDRWin 3.9a, and Exact Audio Copy 0.9 Beta 4 getting the drive to show up and working but CDRIdentifier v1.63 still doesn't see the drive so maybe it's a limitation of CDRId. What I did was put WNASPI32.DLL in C:\WINDOWS\SYSTEM32 from Nero ASPI from w*w.cdspeed2000.com since it seems like Adaptec ASPI 4.60 and 4.71 isn't able to support Firewire/USB devices but SCSI/IDE only.