LIGHTNING UK!

Just remember that the first error is the real error. In your case... That's what the drive returned as the error code when it said it failed. During the burn, the drive is in full control. There's nothing I can do to force it to write to the sectors and there's nothing I can do to make it error out. It either works or it doesn't. The burn quality is determined by the drive/firmware/media combo and although a disc may burn successfully, you never know (unless you scan it) just how good/bad the actual burn is/was. So whilst your old NEC might have been able to burn those RICOH DL disc, it *might* have been VERY close to failing and you'd never really know about it until it actually goes over the edge and errors out. Out of interest, have you tried burning them at the various speeds supported by the writer? (in case it offers 2.4x, 4x, 6x, 8x etc)

Yes, the LB info is stored in the MDS file that gets created in Read mode and that info is then read back out again by Write mode.

Why's this in 'Chat' ?! Moved.

I wonder if that drive supports 'Disc Quality' scanning in CDSpeed? Give it a try on the verb you just burnt

Coolio

Damn, just when I thought I had it sussed! I've reported these today http://bugs.winehq.org/show_bug.cgi?id=11657 http://bugs.winehq.org/show_bug.cgi?id=11659

Just use Read mode and then Write mode.

Make your own thread please HarleyHawk. If you have a problem, post the log.

I'm pretty sure the discs are protected, so no.

Have you only tried 4x burning? There are lots of other 'supported' write speeds that *might* work.

You might like to update the firmware on the drive in that changer, yours is kinda old now. As for the locking thing, I didn't notice anything odd last time I used it for multiple burns. I'll try and give it another look today at some point if I get the chance.

Sorry, I meant the commands I send to the drive. As mmalves said, if it looks like you're trying to burn more than the disc can hold you'll be prompted with a message saying it probably won't fit. It's then down to you to attempt it or not. There's nothing you actually need to enable/disable....the ability is just always there.

Verbatim or Taiyo Yuden will be fine. They're the two best.

So basically anything that also involves reading from the hdd appears to kill it. It would therefore make sense that the buffer bar must be dropping off from 100% when it starts to die. That should be pretty obvious if you keep an eye on it. Personally, I keep well clear of 'Cable Select', it's evil! When burning data, are your hdd's sata or just on the other ide channel?

Is there anything interesting in the Dr Watson folder? C:\Documents and Settings\[username]\Local Settings\Application Data\Microsoft\Dr Watson

Not the cgl, the entire log from windbg. It should contain loads more info than that. It lists where all the various modules/dll are loaded into the memory address space. Then the bit where it crashes should list the address that crashed and hopefully it'll match with one of those modules. I'm pretty certain the crash isn't inside ImgBurn's own code. I can't even reproduce it under Win 95 / NT4 and everything crashes on that! lol

I really need the entire thing, sorry!

How about a copy of the windbg log? The cgl shows everything is fine, it hasn't logged any errors.

Next thing to try is running it in winbdg as mentioned in a previous post. http://www.microsoft.com/whdc/devtools/deb...installx86.mspx Load up windbg and click 'File' -> Open Executable. Point it to the one I just sent you. You'll then see some stuff scroll in the window and it'll appear to pause. Click the 'Debug' menu and then 'Go'. ImgBurn should then load up. Go into Read mode and insert your disc. Hopefully it'll then capture some sort of error.

Email sent

I don't think they're newer at all, they're just 'Mad Dog' ones. (Mad Dog drives are NEC ones) 1.F1 is probably based on 1.01, 1.F2 based on 1.02 etc. So 1.04 IS the latest.

cdi support is un-official as I don't have the specs. What type of image is it supposed to me? A simple data disc? An audio disc? Burn the file in whatever program you used to create it.

The data is ok, the verify proves that. The trouble is, when the drive doesn't finalise the disc properly it can lead to problems in other drives - where they won't be able to read the disc at all (they'll fail to initialise it). If it's important stuff, burn another copy. Either way, do the firmware update. 1.04 is the latest for your model - direct from the nec site, I just looked it up!

You're burning at 20x there which is actually 4x over the rated speed. Slow the burn down to 12x (or 16x tops) and you might be ok. If you configure the 'Automatic Write Speed' feature (as per the Guides), you won't have to worry about things the next time you burn media with this dye.

Yeah