|
KCK -> RE: InCD Illegal Request (12/3/2002 2:42:54 AM)
|
CDL: I'm afraid the next stop could be to look for some ASPI fixes, or just reinstalling 98... Let's go back over some previous points; this might help you or other poor readers in the future. 1. Acbhlpr.vxd apparently comes from the Adaptec/Roxio burning plugin for WMP as well. In general, on Win98x, one should look for the following suspect drivers in C:\WINDOWS\SYSTEM\IOSUBSYS: Acbhlpr.vxd, Cdr4vsd.vxd, Cdralvsd.vxd, Cdudfrw.vxd, Cdudf.vxd, Cdrpwd.vxd as well as for these DLL-s in C:\WINDOWS\SYSTEM: Cdral.dll, Cdrtc.dll, Cdr4dll.dll The usual fix is to rename .vxd to .vx_ and .dll to .dl_. 2. Some people report also problems with the IOSUBSYS drivers Drvwppqt.vxd, Drvwq117.vxd which come from MS/Seagate Backup (parallel-port type), but might also be installed for SCSI devices. You do have them, possibly from the scanner adapter, but if they worked in the old configuration, you needn't touch them. 3. The original Win9x ASPI layer comes from Adaptec, and the usual headaches are due to too many versions distributed by both Adaptec and other companies (which choose a version which works best or conflicts least with their products). Thus removing all Adaptec entries from the registry might have been too harsh. Second, ASPI reinstallation doesn't boild down to copying files; one needs proper registry adjustments as well. So can you check if ASPI is installed and working correctly? Well, even if an ASPI check utility says OK, the only sure way of getting ASPI back to its pristine state is reinstalling Win98... If you let Google search for "Adaptec ASPI layer", etc., you'll find a lot of fixes; maybe some of them could work for you. 4. Relative to the already waisted time, upgrading Nero and InCD is peanuts, and who knows, it could help. Remove InCD 2.28 first, then upgrade Nero, then install InCD 3.51.61 (this is "upgrading" in Ahead's terms). 5. I agree with your comments on Ahead's support, but I don't believe they peruse this or other forums regularly. As you noticed, Ahead concentrates on development at the cost of documentation and support. Thus it wouldn't suprise me if you decided to call quits at this time. Maybe some the next version will work for you. I had problems with 3.31, which were fixed by 3.51.61.
|
|
|
|