LIGHTNING UK!

The option you're looking for is 'cycle tray before verify' and it's on the Write tab in the settings.

Where did you download it from, which 'Mirror' site? Nothing is loaded without your consent, so if you installed chromium, it's because you allowed it (didn't decline it).

fixed

As you burnt from files rather than an ISO, you can't verify the actual file content, but you can verify the raw sectors to check if they are readable (we know that at least 1 shouldn't be). Just go into Verify mode, uncheck the option to verify against an image file and press start

It doesn't automatically stop verifying, you're prompted as to what you want do - retry, abort, continue. So it all depends on how you answered the question. If you post the full log, we'll be able to tell you. It's impossible to say what's at fault. All we know is it's some combination of the 2. If the drive constantly fails to burn the discs and they're fine on another drive, it's the drive. If the discs fail to burn on all drives, it's the discs. If it's all hit and miss, it's anyone's guess as to what's wrong!

It would need to be successful.

It doesn’t ask twice by default Turn off auto calculate, it’s only asking you because you’ve enabled it. Things can change between you selecting something as part of the calculate process and then actually doing the build / burn... and it makes no attempt to check for those things.

It looks like something you’ve installed is blocking the command used to write to the disc. This is not a settings issue.

This is normally down to how quickly the drive can read the disc. If it's having trouble reading it, perhaps erroring out, it will slow it down... as would another app trying to read it at the same time - say, if Autorun is enabled or whatever and your media player automatically pops up.

Yes, I'm not really sure why it's doing that... it started yesterday at some point. Just have to give it time to get sorted out - I've also filled out one of those reports.

Well... there's no real point in the .DVD file beyond recording the layerbreak position, so you could probably just leave it set to 'AUTO' so it makes one (a .DVD) when it actually needs to. Of course I guess it really depends on what you actually want the .DVD for and how you intend to use them. Sorry, I'd totally forgotten I'd added the option of making an actual MD5 file. You'll need to enable the 'Calculate MD5 Hash Values' option in the 'Settings' -> 'General' tab -> 'Page 2' before that other option on the 'Read' tab gets enabled.

Rosanna, There's just no such thing as RAW mode for DVD/BD. Moving to different countries etc doesn't come into it.

Not really, no. You'll have to continue to use existing solutions.

Raw mode doesn't even apply to DVDs, nor ISO image.

It’ll create a .dvd if you enable the option in the settings on the read tab. The md5 is only ever written to the log window though - and that must also be enabled in the settings.

That's usually from encrypted media. So if you're trying to read a file from a CSS protected DVD Video disc.

To me, dlm means download manager. That's *not* the ImgBurn setup file. Perhaps you clicked on an advert by mistake? The do often look like a legitimate download button.

ImgBurn doesn't do any internal decoding at all. Everything is handled by the OS, either via DirectShow or ACM. I have no plans for doing any internal decoding. It literally takes 2 minutes to install the system-wide DirectShow filters and then it'll automatically work within ImgBurn.

I don't see why not.

It supports whatever DirectShow supports. Installed the DirectShow decoders (as per the AudioCD guide) and you'll be good to go. http://forum.imgburn.com/index.php?/topic/5555-how-to-write-an-audio-cd-from-music-files-using-imgburn/

The disc info you posted looks all wrong. It's missing loads of info. You didn't verify the disc when you burnt it, so we can't even tell if it was fully readable at the time (in that drive). That's quite important info when looking at issues with playback. It's good that you say it works in PowerDVD on your PC, but I wouldn't totally rely on it if it's unreadable in other devices.

Yes it is. Original compiled 2.5.8.0 exe... 11,164,672 bytes CRC32: 4B74746A MD5: 5B1874DED2D60B946F79F6664BC35322 SHA-1: 43981BD4C7FC24AEF89BE6C1F680E8949D38CF17 UPX packed exe... 2,748,416 bytes CRC32: C4A9D4D6 MD5: FDF88E419DF6A01956BC29A55E2C9C69 SHA-1: F5E606397C894AD365926C54CEBBBB71CEFE2A8F Unpacked exe... 11,164,672 bytes CRC32: 61B68E8F MD5: 40E3206C1B9C3BF466682A9A2E9E63A9 SHA-1: F95A1CBBC6F0636E0838C69EA71CDD2ED7777798 It is what it is. UPX's decompression isn't lossless afaik. The exe has been repacked with a newer UPX since its original release back in 2013... Back in June 2017 actually, which falls after the date of archive.org's copy of the exe.

No, there's no additional logging for CD-TEXT stuff. It writes what's in the CUE, that's all. Nope, no settings to change either. Your car is just favouring its internal lookup to reading CD-TEXT. You can check the CD-TEXT on the disc by going into Read mode and clicking on the little button in the Source box that's a disc with a question mark on it ('View Media Information...'). I'm afraid I have no experience of database submission, so I can't help you there.

Those weird names won’t be on the disc, so it’s something your cd player is making up - either based on some sort of internal database or online lookup. Sorry but I don’t really know what you can do about that. There’s no difference in burning wav or wma files - assuming the title and performer are the same in the cue files. That’s where the info comes from, not the tracks themselves. There is no facility to edit the cue file. The feature is purely for creating them. If you want to manipulate the cdtext info, that’s just done in notepad.

I was specifically talking about making an ISO with it... I remember reading you said the two machines didn't have a burner The page I linked to definitely shows an option whereby you can save to an ISO. Maybe it depends on the version of the program you're running though? Obviously if you could have it make an ISO itself, it would be trivial to copy it to USB and burn it on another PC that *does* have a burner. USB and CD are very different. USB has partitions etc like a hdd, CD/DVD don't. The BIOS probably emulates one though as part of the cd/dvd boot sequence - it's not something I've looked into. You've only got to Google 'bcd unreadable' and you'll find a ton of stuff where people are trying to repair their non-booting bcd. I assume the BCD file is present and correct on the burnt disc? (in the 'boot' folder)