LIGHTNING UK!

Try updating the drives firmware (to KS0B) http://forum.rpc1.org/dl_firmware.php?download_id=2056

Are you running Vista? You may have to point the destination file to somewhere you can actually save to - i.e. not the root of the drive.

Have you done anything recently like updating the firmware?

If Verify fails, you've got issues. Do not ignore them - ask for help.

If you abort when it's saying the leadin is being written, it's already too late if you're trying to avoid a coaster. ImgBurn doesn't actually do anything with the LeadIn, it's a drive function. Different drives handle it in different ways. Some will write it when the first 'Write' command is sent to the drive and that command won't finish being processed until the leadin has been written and the 'Write' has completed. Others will accept write commands until the buffer is full AND THEN go about doing the leadin. As such, it's a 'best guess' situation. Either way, if it's taking far too long to move onto the 'Writing Image' stage, it's a sign the drive is having issues writing to the media. If your drive is decent, it's firmware up-to-date and you're using decent media then there shouldn't be any problem.

What's telling you they're too big? If that drive really is formatted using NTFS, I don't see why 4GB would be an issue.

Oh I'm with you. Ok well that can't really happen or a custom ordering wouldn't be possible. (well, not without more options, context menus etc) Sorry but this is your issue really!

I don't see how this is an ImgBurn problem really, any program that sends the command via SPTI would fail in the same way - in theory at least.

The last command sent is the problem one - and it shows the drive that's having issues. Update the firmware on the samsung drive and perhaps it'll fix the issue. http://forum.rpc1.org/dl_firmware.php?download_id=1676 You should be on F509.

I'm confused. ImgBurn sorts by name already, it always has done and that can't be changed (in the current version).

It wouldn't work at all if that was the case. This is just a bug in a driver somewhere along the line.

Read it in 'Read' mode (yes, to an image files), then 'Write' it in Write mode.

Why would it say 'operation completed sucessfully' if it wasn't actually doing something? Your initial post made it seem as though the application was idle when it stopped responding. The info in the log window will tell you what it was doing and of course there's also the text in the statusbar.

The drive appears to have issues with the disc. Look for firmware updates for it and consider switching to some Verbatim DVD+R DL media.

ok well that's a coaster now. Do you have the log of the failed burn? I doubt the specific error you've taken a screenshot of was the first one to pop up - it would be VERY odd if it was.

For the MDS thing, ImgBurn goes a step beyond DVD Dec and will actually examine the IFO files etc to locate the layerbreak. So where it was vital in DVD Dec, it's less vital in ImgBurn. Yup, read and write is the same process it's always been Oops, forgot to mention this earlier (having read your PM etc), thank you for the donation and I'm glad you found ImgBurn eventually

Ditch the CMC DL discs and get Verbatims instead - they're the only ones worth buying. Check for firmware updates for the drive too, they often improve things.

put that blank back in the drive and whilst in 'Write' mode, copy + paste all the info from the little window on the right.

Take a look at the FAQ, it tells you how to troubleshoot this problem - basically one (or more) of your drives is misbehaving.

The guides you're talking about are for 'Build' mode. If you have an image then you use 'Write' mode - there's also a guide for burning images. btw, the layer break info is stored in the MDS file, without it ImgBurn has to make it up/ask you where you want it.

Yeah that's not good. You can't really get the command wrong so I've no idea why it's not working, sorry. Maybe a (filter) driver is blocking it.

Press F8 when you think it's stuck doing the sync cache part. If it repeats a few lines in the log each second it's still busy and just bad reporting on the drives part if it really is done - either way, I can't do anything about that I'm afraid. As for the ejecting / reinserting, i'll need a debug log for that portion of the burn (i.e. press F8 before it tries to eject and then again once it should have done it.) What if you click the 'eject' button manually in the program? does that work then? (it's all the same commands internally)

Oh ok. So how comes you were using Build mode if you were just pointing it at an optical drive? Why not just use 'Read' mode and get a proper 1:1 image?

Is the F:\ drive a HDD or an optical (CD/DVD etc) drive? If it's a hdd, run chkdsk on it.

Well there are only a few ways for things to load when you reboot your PC, the most common of which are: 1. It's in the 'Startup' folder in the Start Menu. 2. It's in the 'HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run' key within the registry. 3. It's in the 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run' key within the registry. 4. Autorun from a CD or something similar. None of these are touched by ImgBurn itself so whatever the issue is, I'm afraid it's something you, someone else or some weird bit of software has done. Get the 'Autoruns' program from http://www.microsoft.com/technet/sysintern...s/autoruns.mspx and maybe it'll reveal something.