FDY&*# Nero...

[Sasq]

Had a strange problem with Nero 6 a few weeks back. I disabled the imapi from services, still no go. I ended up deleteing the drive from the system device list - after imapi was killed. let it redetect, and worked fine after that.

Dan

[Wombat]

Is it 4%? That's where Nero is for me when it writes the table of contents, and it locks up my computer for a second while it does it. I used to have burns abort there sometimes with the Via 686B bug. Also, if you've got something else running at realtime priority (like Winamp), it can mess that up as well.

What about setting up the burn, and checking the "Simulation" box?

[Kooldino]

Originally posted by Marshmallowman
Is this shooting up to a %, like its filling its cache(8% of a full disk) or is it pretending to burn for a while then aborting(50%of a full disk)?

Like it's filling it's cache. It would jump to 4% on a "full" disc, and on a disc with a few mp3's randomly thrown on, it would jump to 50% or so. That's what lead me to beleieve it was just filling it's cache.

The first case me bad media or to fast a burn speed(for the cd's)..etc

I tried a couple of diff CD's. And I've lowered the burn speed down super low. Same thing.

the second could be anything..bad aspi..etc

Tried multiple ASPI versions.

When you look at the coasters it produces can you see how much of the CD it writes?, eg untouched or half fillled?

That's the thing...it doesn't actually make any coasters. It aborts before the drive actually starts writing.

[Kooldino]

Originally posted by Sasq
Had a strange problem with Nero 6 a few weeks back. I disabled the imapi from services, still no go. I ended up deleteing the drive from the system device list - after imapi was killed. let it redetect, and worked fine after that.

Dan

Well, I tried disabling IMAPI...and I tried deleting the drive from the device list, but not in that order. I guess it's worth a try?

[Kooldino]

Originally posted by Wombat
Is it 4%? That's where Nero is for me when it writes the table of contents, and it locks up my computer for a second while it does it.

Yes sir! That's it, 4%.

I used to have burns abort there sometimes with the Via 686B bug. Also, if you've got something else running at realtime priority (like Winamp), it can mess that up as well.

Interesting.

What about setting up the burn, and checking the "Simulation" box?

I'm pretty sure I tried that and it did the same thing.

[Kooldino]

Oh, btw, it's on an Epox 8RDA+ and WinXP.

[Gurm]

Is that a VIA board? Are you running George's Latency Patch (tm)?

Gpar_

[Admiral]

I think it's a nForce 2 board.
Set a manual value for the ultra buffer.
Try putting the writter alone on a controller (secondary master).

[Kooldino]

Originally posted by Admiral
I think it's a nForce 2 board.
Set a manual value for the ultra buffer.
Try putting the writter alone on a controller (secondary master).

I'll try the secondary master tonight.

What's the ultra buffer?

[Admiral]

The extra ram buffer (takes up from your main memory, up to 80mb), under preferences.
Though I guess it has to do more with buffer underun problems rather than cache.
And if you're there you could also increase the cache to 700mb or so.

[Marshmallowman]

nforce 2 boards may have some problems with IDE drivers from nvidia, you could try the MS IDE drivers.

[Kooldino]

Originally posted by Marshmallowman
nforce 2 boards may have some problems with IDE drivers from nvidia, you could try the MS IDE drivers.

How do i get a hold of those?

[Marshmallowman]

The standard ones that come WITH windows...

[Kooldino]

Originally posted by Marshmallowman
nforce 2 boards may have some problems with IDE drivers from nvidia, you could try the MS IDE drivers.

Ok, so I went on the lead for the IDE drivers and played around a bit. I double checked and made sure I had the newest mobo drivers from Epox's site. And I did. So I figured, "what the heck, might as well try Nvidia's reference drivers". Bingo. Worked like a champ (so far). Now here's what I don't understand. When I got my board back in Oct, and these NEW drivers weren't available, why didn't I have this issue?

[cjolley]

Synchronicity!

Just had the same problem today!
Interestingly, it would work for me but lock up if my brother-in-law was logged in.
The cd burner would just lock up with the burn light on and I'd have to restart to get it to get it wake up.

It turned out that if anyone tried to burn a music cd using the wizard it would lock after writing the list of filenames on the cd.

Try burning without the wizard.
chuck