LIGHTNING UK!

What controller is the drive attached to? Right click the drive selection box and click 'Family Tree'. Close the prompt and then copy + paste everything from the Log window. If an I/O command fails and the sense data is set to the equivalent of 'No Additional Sense Information', it's probably because the real sense data has got lost along the way somewhere. Settings wise, OPC off (which is default anyway), write speed 4x, and eeprom/advanced settings of FHT/SmartBurn on (all others off) worked best for me during testing.

You can't do it in 1 step. I just meant you can already script it to perform a read operation and then a write operation via a simple batch file - and you can do that yourself.

It doesn't work at file level, it read sectors. When it can't read a sector, it skips to the next one - upon your say so. It telling you which file an errored sectors belongs to is just a bonus. Whilst technically valid, I feel your suggestion has little real world usage outside of the issue you're having. If you frequently get problem discs like this, try some actual recovery software - they may already have features like this. It's not something a non-specialist reading tool needs.

I will never add something that just saves the person making the suggestion 5 seconds in their own personal 'process'. If you want a program that does everything you need, write it yourself.

If it's just sat there doing nothing, the I/O command must be stuck somewhere. Unfortunately, I can't force your system/drive to process the commands. The program simply submits them and then waits for a response. Try in safe mode. If it works ok then, it's probably driver related - either the driver for the actual controller the drive is attached to or a 3rd party filter driver that the I/O commands are passing through.

And again Adrianvdh, you reply to something you know nothing about. This is why you've topped my 'Most annoying member' list since the very first day you signed up here. 1. This is something you should research yourself. It all depends on which media and speeds you intend to use. Some drives will do a better job than others on a given media at a given speed. Look in the drive testing forum and browse the MyCE forums to make your own mind up. 2. They shouldn't do, no. 3. Cache is the buffer that data gets put into when software sends it to the drive and before the drive has actually written it to the disc. When the cache/buffer empties out, the burner has to pause for a while and wait until it gets more data. Back in the old days (pre 'Burnproof' type technology), that would be an instant coaster. New drives don't have that problem - hence the reason for drives being released with less and less cache these days. 4. Yes, the CB-PLUS/CB-ROBOT drives are nice (and they overburn straight out of the box). In recent years, Optiarc drives have been my 'go to' drives if someone wants a decent all-rounder. One of the main things going for LiteOn drives is that they can scan (aka PIE/PIF or PIPO) discs nicely. Optiarc drives can do it too, but I have less faith in what they report - but that could just be me being used to using LiteOn's for the task. 5. Worked on in what way? Making the broken function in 2.5.7.0 work?! Yes, that was looked at soon after that 2.5.7.0 release. That's not to say it's perfect but it should at least do the job. I probably shouldn't have even bothered with it in the first place, I expect you're the only person in the world that actually cares about it.

If I don't reply, it's usually because I'm not interested in doing so - usually because it's a stupid suggestion or it's been covered before.

It shows you the total size and the current position. If you really need to see how many sectors are left as a number, do a quick sum in your head.

I've no interest in adding that.

The button ('Open containing folder') to the left of the 'Destination' field can be used for that.

You can do that yourself.

Yes, attempting to use the 2133520 will always fail. and by 'fail', I mean report that error/warning. That isn't the actual reason behind the complete failure. The complete failure of the operation comes down to your drive having a problem with the 'MBIPG101-R10-65' MID discs you're using. Try some others, as per that thread I linked you to.

Your drive will always fail to set the layer break position to 2133520, it can't physically do it. You need a drive that supports overburning DVD+R DL media for these larger disc images. As for the error during the burn, refer to this... http://forum.imgburn.com/index.php?showtopic=8000

I take it the USB installer won't find the files on a DVD if it's just in the drive (and not bootable) ?

...from the instance of ImgBurn that's using the drive.

1. There is and should still be an 'etfsboot.com' file in the 'boot' directory - or at least there is in the Win 8 images I've got. 2. Due to the above, this question is invalid. 3. Yes

The first thing you should do is find out what you've actually got. Do you have a Blu-ray player or just a regular DVD player that has a 1080p output setting (so it performs some sort of upscaling on regular DVD content) ? If you have a Blu-ray player, you'll be able to play proper HD content (BD Video discs, AVCHD, maybe even MKV files). If you have an upscaling DVD player you'll just be able to play the same stuff you've always been able to play - regular DVDs.

Post the log please, not a screenshot - as per the pink box up the top.

You're only going to get the same response to this as you did your last thread about an unreadable Blu-ray disc. http://forum.imgburn.com/index.php?showtopic=20924

AWS isn't a speed, it's a feature - that you have to configure. All you've done there is burn another disc at max speed. Buy the real Verbatim discs with the MKM-003-00 MID.

ImgBurn will never do video encoding.

It doesn't look like your drive can actually overburn DVD+R DL, even if it's technically supported by the tool (in the sense that it doesn't fail). You're using rubbish discs though, buy the Verbatim 8x MKM-003-00 ones as recommended just about everywhere.

Your drive is reporting some variation of a 'write error' when attempting to burn those 'RITEK-S04-66' discs. If it doesn't want to burn them, buy some other ones - as per the thread I linked you to.

Post the log of you burning + verifying the disc please. Oh and this should have been in the 'Support' forum - consider it moved.

http://forum.imgburn.com/index.php?showtopic=8000