LIGHTNING UK!

If your drive reports a read error at any point during the verification phase, I'd consider that disc to be a little suspect, even if it eventually managed to read the problem sectors after x retries. Different drives are more/less capable at reading problem sectors than others, so it may totally fail in another drive or it may not show an error at all. Verification is good for that drive at that moment in time. I guess it wouldn't hurt to retry the burn at 4x, the drive might do a better job of burning it. Please note that it's not ImgBurn claiming it can be burnt at 8x, it's the firmware in your drive. ImgBurn can't do anything your drive isn't programmed for - that's the purpose of the drive's firmware... to control all of the burn parameters for every different media.

As this is the ImgBurn Support Forum, please start by posting the disc info displayed by ImgBurn - which happens to be exactly what was asked for in the 2nd post (1st reply) in the thread you linked to.

Ok, I've found the problem and can see why it would sometimes work / not work. It turns out that the fields aren't populated during the initial analysis phase and are actually populated (refreshed from the file) when you select the track or go to save the actual CUE file. No such population / refresh occurs when just displaying the track listing.

Don't worry, the order in which they come through isn't important. Can you please double check then when you get an incorrect track listing file, clicking on the individual files in the list does indeed display the correct CD-TEXT info in the title/performer boxes. It makes absolutely no sense that the info would display correctly in one place and not the other. They're both reading from the same variables. If it turns out that it's wrong in both places (but only sometimes), it would mean it's occasionally running into some sort of issue with parsing the file - maybe it's being locked out by some other software on your machine (AV or whatever). Also, does it matter if you drag+drop the files Vs adding them via the 'browse' box? I'm assuming no errors are being reported in the Log window as it tries to analyse the files (and extract Tag info) ?

So where it says 'Default CD-TEXT (Disc / Track)' down the bottom right of the 'Create CUE' window, you have 'Tag' selected in both drop down boxes? The only time the track listing would use the file name is if the track's configured CD-TEXT Title and Performer are both empty. btw... yes, you should/can get an email if a reply is posted in a 'followed' thread - subject to your notification settings, which you can configure here: https://forum.imgburn.com/index.php?/notifications/options/&type=new_comment

When you add one of the problem files to the 'create cue' window and enable the 'Tag' option for CD-TEXT, does it fill out the 2 fields below with the correct info you expect to see? By design, the individual track performer info is removed if it matches the performer of the disc. That's why your 9 and 10 didn't have it. If I add someone's album and all the info is filled out everywhere, I want the album name and performer at the top and then all I need are the song names, not the performer and song names. That's duplicating info for no reason.

The log is more useful. The screenshot suggests the os has lost its connection to the drive. Bad cable/ USB port perhaps?

and… closed.

Your hdd will report an error if it cannot write the data for some reason. It'll also report an error if it tries to read the data and detects that the data doesn't match with the ECC. HDDs also have spare blocks they can use in place of any sector that's found to be bad. The remapping of bad sectors is done automatically and you, the user, wouldn't know it's happening. S.M.A.R.T info can report on such remappings/reallocations. So to sum up this topic (before it gets closed)... Corrupt files stay corrupt. Test for corrupt files by checking the MD5 or SHA-1 against a known 'good' value (or by using the 'Test' feature of a compression tool if dealing with zip/rar archives etc. If a storage device develops a bad sector and you attempt to read data from it, you'll be told about the problem. If a storage device develops a bad sector and you attempt to write data to it, the device might try to remap the bad sector to a known good one, or it will error out and you'll be told about the problem.

That's good then. Just FYI, such issues would be reported as a 'Miscompare', not an 'I/O Error'.

You're basically repeating yourself again (or asking questions I've already answered) and I've warned you about repeatedly doing that in the past. Please stop or I'll ban this account too. If the file was corrupt before you burnt it to disc, it'll still be corrupt on the disc and ImgBurn won't tell you about it (unless it's even more corrupt on the disc - then the statement below applies). If the file on the disc is different to the one on your hdd, ImgBurn will tell you so as part of the verification process.

I've already said what an I/O Error is (where ImgBurn is concerned). On a more generalised note, I/O stands for Input / Output. It's the sending and receiving of commands / data to and from a device. A drive isn't going to know if a file is corrupt (before/as it was written to it) - that's where CRC / MD5 / SHA-1 checks etc come in. In the case of a zip / rar file etc, the compression utils usually have a 'Test' feature built in that can be used to verify the contents of the compressed files. If you download a file and want to check it's ok, check its MD5 / SHA-1 using a tool suitable for the job - something like HashTab perhaps. Once it has checked out 'ok', you're fine to burn it to disc and ImgBurn's burn+verify will let you know if what ends up on the disc doesn't match with what's on your hdd.

I answered that earlier.

Yes, if it burns and verifies ok, the disc is good.

An I/O Error can be anything where a device (optical) reports an error processing a command. If there’s a problem reading or writing a file on your storage device (hdd), the Window API function will also return an error and ImgBurn will display the details.

No, general corruption of the file is not a hardware problem.

Yes

ImgBurn just burns what you give it. It doesn’t know what subtitle files are. Whatever you feed it must already be in the format your playback device supports.

>> I see what you mean. Instead of waiting all day for the Device Not Ready (Medium Not Present - Tray Closed) message to disappear, you are suggesting I eject the disk and then reinsert it for X amount of times. I will try that this weekend. Could it not be a problem with the disks themselves? Exactly. That message isn't going to change unless you actually do something - it's already a final / resting type message. It could be a problem with either of them. Something, somewhere isn't working very well if the drive thinks it has burnt the disc ok but then cannot reinitialise said disc after cycling the tray. It could be the discs, but you've used them before. The drive was able to initialise them when they were blank - it burn them and then couldn't initialise them 2nd time around... so maybe it's a hardware fault. Posting a log of the burn would help, as at the moment, we have no idea about which drive/discs you're using.

When it pops out (technically, it's cycling the tray between write and verify), you are just pushing the tray back in, yes? Don't remove the disc. If the disc is in the tray and yet the drive is returning that status (medium not present - tray closed), it sounds like a hardware issue to me. Please eject the tray and reinsert it. Does the drive manage to initialise the disc after x attempts at doing that? (The details of the disc will become visible in the info panel on the right within ImgBurn)

It's going back a good few years now, but only real LiteOn iHAS drives were capable of burning them nicely - and only really on the MKM-003-00 discs. The Vinpower Digital 'plus' drives have been designed (firmware modified appropriately) to support it. You'd have to get one of those and put it in a suitable USB enclosure.

Yes, I’d say it’s an issue with your drive. Also, you’re trying to burn one of those oversized images and you can only do that with certain drives. These days, you’ll need to buy a ‘plus’ model of one of the Vinpower Digital offerings (Plextor/ pioneer/optiarc).

Put a new blank disc in the drive and don’t touch it with anything other than ImgBurn. It’ll do what it needs to do in order to use it.

If you can’t even force close it, it’s probably not ImgBurn itself that you’re waiting for… it’ll be something lower level - a system driver or something.

It’s unlikely you’d have written/saved them to your hdd without an error popping up if there was actually a problem writing them to the disc. Likewise, if there was a problem reading any of the sectors they’re stored on, you’d have seen an error message. You can test the zip and rar files by opening them in your compression util and clicking the Test button. The util will tell you if the crc isn’t what it should be.