LIGHTNING UK!

It looks like there's something wrong with your 'C:' drive. The file you're trying to burn is unreadable. Run chkdsk on the drive and have it scan for bad sectors.

Good old NVIDIA If you can't get any driver updates from their website, try installing 'Virtual CloneDrive' from Elaborate Bytes / SlySoft and then switch the I/O Interface in ImgBurn's Settings (I/O tab) to 'ElbyCDIO'. That may get around whatever's messing up.

You mean your *drive* worked just fine, it wasn't a program issue to begin with

It definitely doesn't write anything to the registry until it has been shut down. If those keys are suddenly reappearing, something else is putting them there. Maybe something like 'Process Monitor' from Microsoft/SysInternals could help you find out what's doing it. That said, the keys aren't a problem. It's whatever's under the HKCR\.iso that's important. You should also be able to right click an ISO file, select 'Open With' and then edit the default program that way. Explorer has its own way of dealing with default file associations and they can override the settings you see in HKCR (which is itself a merged HKLM and HKCU).

If ImgBurn is configured like that, it isn't going to be touching the registry when you close it down... and it certainly doesn't touch it when you open it up. Open up RegEdit and take a look at HKCR\.iso The 'Default' setting in there (if there is one) is what'll be being used as the default program for such files.

You should probably at least try 8x before then buying yourself some Verbatim MKM-003-00 discs. You may also like to try enabling the 'Perform OPC Before Write' option in the settings on the Write tab. A new drive like yours shouldn't really be having problems with that media, but the quality of that MID can vary a lot and that option may get around it.

CD-DA Audio uses all 2352 bytes of the sector, so there's none of the extra error correction built in that you'd usually associate with data tracks/sectors. Reading slower can produce better results.

The tooltips tell you what they're for. Hover your mouse over them. One is for Data tracks, the other is for Audio tracks.

Tdk is just the band name, your disks are Ritek - as shown by the 'Disc ID / MID'. Do you have to use rewritables? If not, I'm sure you'll have more luck with some decent 'write once' discs.

Update the firmware on your drive. http://www.firmwarehq.com/LG/GSA-4163B/files.html If it still fails, use different discs.

Right, so you're losing the connection to your NAS server for some reason.

It probably depends on how thoroughly a program looks at the disc to find sectors containing data. A quick erase doesn't make a DVD+RW look empty (at least not in the same way it would on a DVD-RW or CD-RW), it simply writes zeros to the first few hundred sectors - which wipes out the initial file system descriptors. I can't read an 'empty' BD-RE in my drive (just tested), so something must have happened to make it think there 'might' be something on the disc worth reading.

I'm glad that solved the problem.

Pioneer drives have a 'quiet drive' feature that adjusts the read speed to keep the drive quiet. You may find a tool to disable it if you're lucky - the next version of ImgBurn has that functionality built in (but it hasn't been tested on a '20xD' drive, just the more feature rich '20xM' versions. btw, there's a 1.40 firmware update available for your drive. http://www.firmwarehq.com/Pioneer/BDR-208D/files.html

If you're burning an ISO, why are you in Build mode and not Write mode?

What does it do as you resize the window? What about if you minimise / maximise it? I don't do anything with the listbox in that window, it's just set to fill the entire client area (i.e. the size of the parent window). The rest should be handled by the development environment or Windows itself.

It's normal for the drive you've got and how you're using it. Don't worry about it.

You should be able to mount the CCD and just use read mode to make a new image (bin/cue/CCD) from the virtual drive. No need to burn the image.

There's something going on with your destination drive. So the 'V' drive.

I'm not seeing the family tree info in that log. Just copy and paste from the log window once you've done what I said above.

Thanks for the report, I'll look into it and fix it.

It's just the way some drives work and report that info.

Only daemon tools really. It's the most complete one available.

Maybe a controller / driver issue. Right click the drive selection box and click 'family tree'. Close the message box and then post the log containing that info please.

If the long file name is over 255 characters, the OS would convert to and use the 8.3 format.