LIGHTNING UK!

You should try the DL's at one / all of the other 'supported' speeds too.

Try with the 1.09 firmware update and try at all the available speeds just to make sure they all fail in the same way.

I tried to reproduce it myself using the steps you provide but was unable to. I tried inserting the disc and clicking ok straight away, I also tried inserting the disc... waiting a while and then clicking ok. Until there's a fool proof way to reproduce it 100% of the time, I don't think it's something I can fix.

If the API reports it as 1GB then that's how big it is. Make an image rather than burning to disc, you'll soon find out how much of the file ImgBurn is actually able to read via the normal API commands.

Post the log of you burning+verifying when using the verbatim discs.

You've got a bad USB enclosure / USB controller/chipset combo and it's producing the semaphore timeout issue. Google 'semaphore timeout usb' and you'll see loads of pages talking about it. You'll probably have to get a new USB card or enclosure to fix the issue.

Copy + paste everything from the log window please, it's much more useful.

You could try again with 'Perform OPC' enabled in the settings.

Post a log of you burning + verifying.

What happens if you burn an ISO, click the 'OK' button on the 'Operation Successfully Completed!' box and then wait for ImgBurn to get back to the main screen and be showing 'Device Not Ready' in the status bar before putting the next disc in? Are you able to do that or does the drive get stuck before then? If it doesn't and it still works, put the next disc in and keep any eye on the status bar. Tell me exactly what it says when the drive seems to be taking its time to do something.

Hover over the 'Label' one with your mouse and you'll get a few more.

please post the log rather than trying to remember what was written in it.

I tend to have firmwarehq open in a tab all the time now... that search box on the front page gets a lot of use! It probably just gave me the edge over you

Update the firmware on your drive. http://www.firmwarehq.com/Lite-On/SHW-160P6S/files.html

Ah so your drive is actually being removed from the system by Windows because it's stopped processing commands - i.e. it (or perhaps the driver?) crashed. Have you tried burning onto some decent media to see if it's any different? Maybe just try burning onto a DVD+RW (the same one) a couple of times in a row.

Can you please check that when the 'Operation Successfully Completed!' box is on the screen, there are no open handles to the drive (there shouldn't be). And when you've inserted the next disc and clicked 'ok' to then end up back at the main Build screen there's just 1 handle open. There should still be 1 when the build info screen comes up after you've clicked the big 'Build' (start) button. During the burn (or an erase) there should be 2.

Read the last line of my previous post again.

Is that the only place it finds it? (ignoring that same key but in ControlSet001, 002 etc)

where exactly does it find it?

Just load up regedit and search for 'tdcmdpst'. It'll be in a filter lists *somewhere* !

If it's ever in the log window, it gets saved. I need to see exactly what you're seeing when you say it can't find the drive. If nothing is being logged, get me a screenshot of the error and a note of what's written in the status bar.

Go into Tools -> Settings and look on the 'Write' tab. There you'll find a checkbox for spare areas. When you've done that you'll need to do another 'Full' erase/format on the disc.

Have you tried burning at 4x? (note that 1x isn't actually possible... your options are 2.4x and 4x) Where are you Verbatim discs made? (look on the spindle/box) The ones from Singapore are the best. Your drive is getting on a bit now, it's probably got dirty over the years so you could try running a cleaning disc though it. Failing that, get a new drive.

Firmware update to YE05 - http://www.firmwarehq.com/LG/BE06LU10/files.html What BD-RE are you using there? Verbatim ones are the best, the one they supply (LG) is awful... incase that's what you're using. I would advise you to turn 'FastWrite' off and to reformat without spare areas.

If you read the thread below, you'll see that most programs don't report errors on CDB's that are told to return control to the program immediately. http://forum.imgburn.com/index.php?showtopic=7860 That is what I was getting at in my original post when I said you don't know what's going on under the hood. Unless you have a program to snoop in on the commands being sent to the drive (and watch what's coming back), you've no way of knowing if it's erroring out or not - and more importantly, if the program sending those commands is then relaying the error to the user.