LIGHTNING UK!

What OS is it supposed to boot into? Bootable discs normally boot into a version of DOS, does your application run in DOS? Also, as I'm not 100% clear on what you're trying to do, I'll just point out that ImgBurn doesn't write images to USB thumb drives.

I know, but post 3 came across as one - even though it was missing the 'question mark'.

I can't give you any real advice on the error from your LiteOn drive until I can actually see the real error. See if you can plug the drive into another PC and try it on that. If it works, great. If it doesn't work but gives you the real error, you'll know it's related to your PC. If it doesn't work and gives the same 'No Additional Sense Information' error, you'll know it's the enclosure or USB adapter you're using that's the problem. MKM-001-00 are good discs, but the MKM-003-00 produce better results. There's an iHAS124 thread in the 'Drives' forum that shows you how the drive performed with various discs and various settings. Your LG drive just reported a 'Write Error' when trying to burn to the cheapo 'MBIPG101-R10-65' discs. As it seemed to work ok on the discs prior to and after that, I'd just ignore it. You have the option of trying the other supported write speeds, the drive may do a better job at one of those than it does at 2.4x. As you've got a LiteOn, you should take the opportunity to do some scans and see how good/bad the 'working' burns from each drive really are.

Chances are, the 'No Additional Sense Information' error is bogus and the real one is being lost somewhere - either due to the way you've hooked up the drive (USB) or a filter driver installed on the machine. Personally, I'd enable FHT and Overspeed and then burn those MKM-001-00 at 4x. Next time you buy discs, get the 8x speed Verbatims instead of the 2.4x speed ones.

So stop asking questions about it.

Try burning at 2x or 4x rather than 'MAX' (6x). Failing that, if 'VERBAT-IMd-000' aren't working well in your drive, perhaps give the 'VERBAT-IMb-000' or 'VERBAT-IMf-000' versions a go instead. The alternative would of course be to try another drive.

I don't recall you ever asking that. The question isn't something I'd intentionally say 'No' to, there are hundreds of logs in the forum that clearly show beta versions are being used. In fact, I'm never NOT using a beta version. Ah, found your actual PM to me... ...and the answer is still 'No'.

If you would like advice on the problems, please post the logs so we can see what you're working with.

I explained why it takes the time it takes, it formats the discs properly - waiting for both foreground and background bits to finish. Yours only waits for the foreground part to finish and will leave the 'BG Format Status' on '1' (meaning 'started but not running and not complete) rather than '3' (meaning complete). If you don't want it to do that, you can turn off the option in the settings (on the 'Write' tab) that makes it format properly.

Sorry, I wasn't aware it didn't already work like that! That functionality is built into the 'Listview' control used by the lower 'Disc' pane... but the 'Explorer' pane at the top uses a custom control and it has it's version of it disabled by default. I have now enabled it. Alt+Tab should be ok now (in the next release) too.

It's your machine that's stopped processing the I/O and not really anything to do with ImgBurn. It has to wait for the Windows API function it calls for doing I/O to return control to it. All I can suggest is that you try looking for updated firmware for the enclosure chipset and the usb chipset (if it's a 3rd party one - i.e. not Intel or whatever). They obviously also have driver updates for the usb controllers (and even the hubs if you have such things on the board - mine does) - make sure you're running the latest one. Right click the drive selection box and click 'Family Tree'. Close the prompt and then copy + paste everything from the Log window please.

If it's telling you that you need to write to a double layer disc, what you're attempting to burn must be too big to fit on a single layer one. As for formatting and then doing nothing, I guess some sort of error occurred. You'd have to show me the log from when that happens.

It takes as long as it takes. The drive does the formatting, not the program. The program (by default anyway) waits for both parts (foreground / background) to finish. It only formats when the 'Formatted' status isn't shown as 'Yes' in the disc info text on the right. In programming terms, that's when 'BG Format Status' isn't 3.

Real tyg02 discs should work fine in just about any drive, they're normally excellent discs. Try burning them at 8x. As you've discovered, turning verify off doesn't make a problem go away. If you're about to get hit by a speeding train, closing your eyes won't make it go away, you just won't see it hit you. Sure, maybe some things are better left unknown but the readability and accuracy of a burn isn't 1 of them. Leave Verify enabled.

Formatting a new DVD+RW disc is normal, that's just how they work. If that doesn't explain what you're seeing, please tell us more about the problem.

Because it's a prompt about the image, not about what your burning settings are. Notice it also pops up when you're creating an image file.

Tons of options are 'hidden' from the main dialog (in that they're on other tabs), I'm not going to add them all (any of them) to that prompt. Sorry.

mount each image (in turn) in a virtual drive and copy the contents to different folders on your hdd. Use whatever tool is appropriate for combining that type of content - Google it. Create a new image / burn a new disc from the combined stuff. Or yeah, just forget about combining them and burn them to their own individual single layer discs.

How were you combining them?! It's not something ImgBurn can do.

You'd have to manually combine the contents of both images, make a new image and then burn that.

Audio discs don't actually have one. If one is being displayed, it's coming from the cdtext info.

Terminate the process/task in task manager and then run imgburn and have it eject the disc.

That workaround was for a totally different issue. Try another disc, that one looks like it has already been used.

Only in the sense the program sends a larger track size value in the reserve track command! You should probably try and give some other discs a shot as there must be an issue somewhere and that's as good a place as any to start. Maybe cleaning the drive with a cleaning disc would help too?

It doesn't... but I can tell from the number of available sectors. The 'Hardware Defect Management Active' line should say 'Yes', but a little cosmetic bug in 2.5.7.0 means that it always says 'No'