CDRLabs.com

I searched the forums and found this problem to be prevelant but no real solution posted.

The system originally had Nero 6.xxx installed on it, that came with the DVD writer. The user installed Roxio 6 and installed all of the updates available.

Writing with either Nero or Roxio now causes it to lock up at 3-5 percent. Windows Media Player writes fine.

This CD Writer is a Yamaha 20X CD-RW, the one that they released specifically for music with built in jitter correction, its 2 years old. The user is writing at 2X.

I want to say it has something to do with ASPI but am not sure. The DVD Writer(NEC 16x) worked perfect before Roxio being installed. I know there are a ton of Nero/Roxio conflicts. We did uninstall both, and install only Roxio but the problem persists.

Athlon 64 3500+
1 Gig Corsair XMS PC3200 2-2-2-5 Ram
Matrox G650 AGP Card
MSI Neo2 NForce 3 939 MB
NEC 16X Dual Layer DVD Writer
Yamaha CDR, sorry forget the model but it worked perfect in the previous machine.
2 Seagate 160Gig NQC Drives in RAID 0

I know its a software conflict, I fixed this a while ago on another machine but do not remember exactly how.

Anything to give a quick try?

Thanks

hello econnelle. welcome to CDRLabs.

in Roxio's website, support section, you can find something called Roxio Zap. it's for cleaning the registry after uninstalling Roxio software.

in Ahead's website you can find some registry cleaning utilities - General CleanTool, Nero Clean-tool, InCD clean-tool etc. (there are a few such clean-tools, i'm not sure what's the differences between them).

try downloading these, clean the registry completely and install one program.

when you had Nero and Easy CD Creator installed, did you also have InCD and DragToDisc installed as well?
Nero and Easy CD Creator should co-exist in harmony. however InCD and DragToDisc are known to be incompatble with each other (packet-writing programs do not live well toghether, never install more than one).

Thanks!

Thats really what I was looking for, a cleaning program for both.

I'll fix it up tommorow and see how it goes.

welcome
let us know how things worked out.

Neither one of those fixed the problem actually.

Turning off IMAPI at the end did fix it however.

Thanks again for the help, good advice to have for the future.