LIGHTNING UK!

Like I said before, when I/O is stuck you can't terminate anything. Windows just doesn't work like that I'm afraid. The command your drive/machine is hanging on is one of the most basic / common ones and it REALLY shouldn't be a problem for it. Could you please post a copy of your 'Filter Drivers' listing. The option for that is in the Tools menu. You should also update the firmware on the drive. You're a good few behind now. http://www.liteonit.com/DOWNLOADS/ODD/LH-2...rmware/BL05.zip

The recommended settings are the default ones, that's why they're default

You ARE (or at least should be) given the option to retry... did you not do so?

The left is for data, the right is for audio. The tooltips will tell you that too hopefully!

Ok well that's not possible I'm afraid so I guess you're kinda stuck now. Maybe you can send off your cracked copy and get a replacement disc?

Please follow my instructions again, that log doesn't show/tell me anything I can use to assist you.

Well what are you trying to 'Verify' about it? If you want to check you read it off the source disc correctly, just put that disc back in again and verify it against that. You don't normally Verify a file, it's assumed that if the drive reported no errors during the read operation then the image is fine. Burning the file and then verifying that disc against the file isn't going to tell you anything. If you suspect issues with the file, you must verify it against the original disc (or rebuild it if it was based on files on your hdd).

You can't verify an image so to speak. It's to verify the disc - and optionally compare it to an image file.

You can probably ditch: GEARAspiWDM PFC PxHelp20 I very much doubt that'll fix the issue though. Looks just like a drive/firmware/media issue to me - but then you already know the drive is about 20 years old!

We have a Guides section if you don't know what you're doing. They'll walk you through it step by step.

This is by design. It doesn't work correctly if you have 'Auto' enabled and then automatically try to start writing the image - 'Auto' calculate is therefore ignored for anything passed via CLI. So basically the two are mutually exclusive.

That's only in the ISO9660 Volume Label box. The others (Joliet and UDF) both support spaces and if either of those file systems are present you'll never see the ISO9660 one. btw, you've never been able to have spaces in the ISO9660 box but previously when you tried it would throw up an error message. Now it's much more user friendly and instead that 'space' gets turned into an underscore.

The OPC command sending wasn't in previous version at all. Drives tend to do it automatically when you send the first 'Write' command, this just allows the program to pick up on problems that little bit earlier and there's less chance of it killing a disc in the first few seconds of writing.

There's a button in Write mode, how 'direct' do you need it to be?!

Correct, this is by design. What I should really have done was make an option in the settings, I just wanted to get away from it defaulting to the ImgBurn folder (as it's not accessible under Vista).

Fixed that earlier today actually.

If the drive won't write to it (or erase it) then there's not much you can do. Try another disc.

(Duplicate threads merged)

When I/O gets stuck, it's REALLY stuck. You can't terminate the ImgBurn process because at that point in time it's not in control, your OS is - as that's what's dealing with the I/O request. Load the program up and press F8 before you insert the disc. Then insert the disc and when it's stuck, copy + paste the last few lines from the log window into your next reply. It'll tell us exactly which command the drive is having trouble with and we'll take it from there.

This is what happens with BD-RE (and DVD-RAM) media. Drives perform automatic write verification as they go along and the 'Verify' part slows down the overall 'Write' process. (Note that this verification is not the same as the one ImgBurn does AFTER the Write operation). Go into the settings and on the 'Write' tab enable the 'FastWrite' option.

Ah sorry, seems I did some things incorrectly on Vista. It's looking at a different 'Devices' dropdown box to figure out which one is selected and under Vista that box is always empty. I'd only tested it on XP as I can't access firewire devices from within VMWare. It's fixed for the next version. You could try changing the compatability settings to make your OS look like XP to ImgBurn... but be warned, a few other things within the program might look a little different!

If the discs aren't protected then there shouldn't be an issue using Read -> Write modes. I cannot and will not do anything to help you bypass any protection on the disc. To do so would be suicide for me.

Just to let you know, I've implemented a button / context menu option to sort by the Tag's track number.

The errors come from the drive. It doesn't matter which version of the program you use, if the drive is going to error out then it's going to error out. End of story. Reverting in an attempt to get past an error doesn't help anyone.

Not by ImgBurn, no.