LIGHTNING UK!

I don't think Acer released anything newer than the GRS6 firmware it's currently using.

Only needed A and the disc info from C.

That's what I'm here for

Oh wait, you've probably left the program in advanced build mode. The command line bits just configure the gui. It's not an actual cli app. So try adding the parameter to get the program in standard input mode.

There's nothing really special about what you're trying to do. The default options work fine. Just enable the md5 one so that one extra bit of info gets logged. If you want to query anything within the log or about what's happened, just post the full log of the burn + verify session and then post the disc info of the burnt disc when taken from Read mode.

Remove /start and check the various options in the GUI are as you'd expect them to be.

Without a verification log, there is nothing for us to go on. Put your dodgy disc in the drive and just verify it quickly. There isn't much you can do if your drive fails to produce a decent burn, beyond adjusting the write speed. It all comes down to the drive, firmware and media combo being used. The file system is irrelevant.

The CD things you're talking about are to do with the layout of the sector on the disc. It's the 'mode' of the sector rather than anything else. Mode 2 Form 2 has less in the way of error correction stuff compared to mode 1 or mode 2 form 1. Anyway, when it comes to DVD and BD, none of that applies. You can write 2048 bytes to sector and that's it. There's no difference between the file systems when it comes to protecting the files written on the disc. If a sector that maps to the middle of a file becomes unreadable, it's unreadable and no file system is better than any other one in that respect. If you're burning large files like that, I'd simply stick with just using UDF. The others don't really cater for modern day needs.

If you want to create an image file by reading the disc, yes.

I've only mentioned the md5 setting. That's in the settings on the 'general' tab... Page 2. 'Calculate MD5 Hash Values'. Read mode issues a few different commands to write mode when initialising the disc - as obviously it's meant for discs with data on them rather than blank ones. Those commands provide mode info about the disc and it all gets written in the disc info box on the right of the main window.

Drives do sometimes round up the number of sectors being burnt to the end of the ecc block. That's to say, the number burnt is then a multiple of 16 (or 32 for BD). So the best thing to do in these situations is build the image whereby its size is a multiple of 16. ImgBurn always builds its images in this way. That way, when you burn it, no 'padding' gets added by the drive and the image can be read back perfectly to the size it started off at - md5 etc matching perfectly. Burning to DVD+R usually always results in the burnt size being a multiple of 16. For DVD-R, its basically down to the individual drive and probably even firmware revisions of said drive. They never used to round up, but these days there are less options for optical hardware and more probably do.

That log shows it burnt and verified just fine. So... what's the actual problem and why did you burn it to a double layer disc?

If you enable the MD5 option within the settings, the program will log the MD5 of the disc once it's burnt and/or read/verified it. You can compare that value to what's on the website. Failing that, do what I said before and burn the disc, then read it back to a new image. Run any md5 / sha1 tool against that new image and see how the results compare to what's on the website.

ImgBurn reads each sector from the image and disc, comparing the two at byte level. You could use the program's internal md5 stuff or use something like hashtab to calculate md5 / sha1 on the image once ImgBurn has created it. There's no guide for verifying, no. Just go into write mode, load your image, load your disc and click the start button.

What's wrong with burning it in one machine, reading it back in another and md5'ing that image? Oh and this sounds like a very generic question and nothing to do with ImgBurn. You could ask it in 'chat' or any optical media related forum.

Your issue is external to ImgBurn. I suggest you run Microsoft's cd/DVD fix it tool. Just google for it.

That's the formula as it currently stands in the unreleased version. I don't recall which figure / calculation was being used in 2.5.8.0

The program uses the Mode 1 / 150KB/s speed for its CD speed calculations. For transfer rate 'x' values, the appropriate 1x speed is *calculated* rather than *picked* from a list - where the list would have to cover 2048, 2332, 2336, 2352 and 2448 sector sizes. Speed = KBs / (150 / (2048 / sectorsize)) So it's a calculation rather than 'switch / case' or 'if' statements. Right or wrong, that's just the way I've done it. I think it must be the '150' in the above calculation that is using a different constant/value in v2.5.8.0.

I don't recall the value that was being used for the conversion to an 'x' rating in 2.5.8.0. My only hope is that the one it's using now works correctly! Specifically, the 'effective write speed' log entry takes the value from the drive. It queries it to find the current write speed and displays it 'as is' in the log. The value is in KB/s according to the MMC specs. I then do my best to guess at the 'x' speed it relates to... but I don't really know if it's using 1000 as a KB or 1024 as a KB. As I say, different drives do different things.

Where did I say that?! If the image won't fit on the disc, you'll get a prompt saying it doesn't fit. If you want to make sure your drive has done at least a semi readable burn (readable by the burner itself, if nothing else), yes, you should verify your burns.

Why is this in the 'chat' section? If your image is smaller (lesser) than the size of the disc, obviously you won't get an option to overburn or truncate. Don't mess with settings you don't understand. Go back into the settings and revert to default. Post the log if you're running into issues with your burns. Make sure it shows you burning and verifying a disc.

It's down to you to get the right driver and slipstream it into your installation folder. As I hinted earlier, there's a way (method and program probably) that'll help you do exactly what you're trying to do. Once you've built your folder correctly, you can burn it with ImgBurn as per the guide.

There's an old issue with the cd speeds (just the translation into '???x'). It was fixed at the time of the report, but that fix isn't present in any 'released' versions of the program. http://forum.imgburn.com/index.php?/topic/21692-2580-cd-burning-speed The value in the log comes from the drive itself. Different drives report different values. 176 is frequently used for 1x CD speed... but then so is 150. Google the 2 values (along with the term 'cd speed') and maybe you'll find the answer?!

This isn't really an ImgBurn question. There's a certain way of doing what you want. http://lmgtfy.com/?q=add+driver+to+xp+installation+cd

ImgBurn lists the supported speeds in the box on the right. They're the speeds your drive reports it can write at on the media you've inserted and I'm afraid there's no way to override them. ImgBurn always 'asks' the drive to burn at whatever speed you've selected, it's down to the drive to use that speed or pick the closest one from whatever it actually supports.