LIGHTNING UK!

Maybe it's a limitation of the virtual drive tool you're using? Mounting the CUE works fine in Daemon tools and mounting the CCD works fine in Virtual Clone Drive.

Please post the family tree info. You can get that by right clicking on the drive selection box. Just close the prompt and copy + paste it from the Log window.

You'd have to mount the CUE file.

Try booting into safe mode and see if it still closes when you minimize the app. It really does vanish from task manager yeah, it's not just minimizing to the system tray or anything? The Galaxy issue is out of my hands. The OS is reporting it's an optical drive - assuming you're using the default I/O settings.

Combine tracks 7 - 96 in the cue by basically deleting entries 8 - 96 and renumbering 97+ as 8+. Drives don't like burning tracks shorter than 2 seconds long.

I 17:32:33 Source Media Type: DVD+R (Book Type: DVD-ROM) (Disc ID: CMC MAG-M01-00) They're being set to DVD-ROM anyway by the looks of it, so don't worry about it.

It didn't have an associated cdt file because that 10 track disc has no CD-TEXT info on it. Try another disc. The one with cd-text had 14 tracks on it.

This doesn't sound like its anything to do with ImgBurn, it sounds like you've built (and burnt) an ISO containing a bunch of split archive files instead of using a compression tool to extract them and obtain the actual ISO file.

I've never seen or heard of it closing when being minimised. Maybe something else installed on your machine is crashing it when you do that. It doesn't span discs. If it's not saving the log then either the app that called it up (if such a thing applies) has told it not to, or again, it's crashing out before the normal close sequence goes through the motions of saving it.

The cdt file you sent me isn't for that cue file, nor for the disc you read today with 10 tracks on it.

No, that's the disc info. I need what was written to the Log window. You can access the saved log via the help menu.

Can you email me the cue file and cdt file for the disc you read to an image please? Also, the log from where you read the disc to an image file - you can just copy + paste that. Thanks.

Sorry, I can't offer any additional advice. I send the commands and they're erroring out. You know as much as I do at this point - the OS is reporting the semaphone timeout error, it isn't from the drive itself.

Your drivers are blocking the booktype command (or correct error code). You're using cheapo CMC discs and burning them at MAX speed. Either get some decent discs or try slowing the burn down to 8x or something.

It depends on how the ISO was made. If it's bootable, the disc will be bootable.

No, you don't need to specifiy a layer break position. Yes, you just use 'write image file to disc' and proceed to burn at whatever speed your drive does the best job at on the media you've purchased. You should still be using decent discs if you want a decent quality burn.

As is hasn't just worked, I'd assume your player either just doesn't read CD-TEXT from CD-R/CD-RW discs or it's ultra fussy about the formatting of it and maybe ImgBurn isn't doing it exactly how it wants it. If you've got a CD where it shows up, read it to an image using ImgBurn and then burn it to another disc. See if the CD-TEXT info is then visible on the copy.

The 14 and 16 models use a different chipset to all of the previous LG models. The drive may automatically change the booktype to DVD-ROM. If they don't, you might be out of luck - assuming the LG booktype commands and LiteOn booktype commands both fail?

Semaphone timeout issues are usually due to some issue between your usb adapter and the usb controller. Perhaps try another cable / port / adapter.

The semaphone timeout issue is related to your usb controller / adapter combo. It's nothing to do with ImgBurn itself. Try other cables / ports.

Perhaps try another cable or different SATA port.

I don't really know why you modified any settings at all. The defaults work just fine, that's why they're the defaults!

Turn off overspeed on the drive and clear opc history, then try again.

Because the drive attempted to perform it and it failed. Buy better discs.

It does always check for a return code and sits there waiting patiently until it gets one. Without snooping on the I/O at a low level, I'm unable to see exactly what it's getting hung up on.