LIGHTNING UK!

1. No idea. That's just how it's coded in the firmware. 2. ImgBurn handles your drive automatically... it's a LiteOn. The current configuration of your drive's advanced settings is displayed in the log you posted in your previous thread. The only option your model supports changing is the 'SmartBurn' one. 3. You'd have to search for what smartburn actually does. This is a drive feature and nothing to do with ImgBurn.

They're the same discs.

That log is just the 4x one yeah? It still didn't work The error your drive returned looks like a bit of a bogus one to me and not what I'd expect from a drive that's in the middle of burning something. Can you try some totally different discs? Ignore the brand name, they need to not be using the PHILIP-R04-000 MID / disc id.

I don't recall having ever seen a HD DVDRW disc before, and as it's a dead format, I don't suppose I will again. Your drive seems to think the disc needs formatting - as it's the one rejecting the write commands and returning that error code / reason. All I can suggest is that you try doing a full erase on the disc and see what happens. I'd be interested to see the disc info from the box on the right when you're in Write mode. Could you copy and paste all of it for me please?

If it was dead, this forum wouldn't be here. More releases will follow, I just haven't had time to work on it. Things are quieting down, so I hope to get back into it a bit more.

So basically, your drive doesn't like the discs you're using. See if there are any firmware updates for it. Does it do the same if you burn at 4x? Failing that, you'll have to try different discs or a different drive.

This is what's wrong... Your drive is misreporting the size of the track. LTS is 'Logical Track Size', and as you can see, it's being reported as '1' sector (2048 bytes). A firmware update may fix it. Here's one I found earlier... http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=R185338 If that doesn't fix it, you'll have to read the disc in another drive without that firmware bug.

I've done it today by adding a 'Disc Timestamp' option within the Settings on the Write tab / Page 2. That option can be set to 'None', 'System' or 'Custom'. It still defaults to 'None' though, whereby the command isn't issued.

You need to post the log. Please also copy and paste all of the disc info from the box on the right when you're in Read mode and the problem disc is in the drive.

That's a bit of a weird 'reason' to be getting from the OS if the device hasn't been disconnected... and I'm assuming it hasn't been disconnected because there's been no 'device removal detected' message added to the log. Sorry, I don't really have an answer for that one.

Post the log please, not a screenshot. That said, the screenshot shows your drive is unable to read the disc. This is nothing to do with ImgBurn.

I can add an option that makes the program set and update the timestamp via the 'send disc structure' command - as per the MMC specs.

It's just not something I've ever thought about making it do. There are no dates stored in ImgBurn's 'build mode' project files, so date fields always get filled out with the current one. No attempt is made to fill anything out with the actual burn date, hence why you've seen it doesn't get changed / updated when burning a prebuilt ISO file.

No, ImgBurn can't do that I'm afraid. ImgBurn doesn't write the burn date in the file system either, only the creation date. Of course if you build and burn straight away or burn on the fly, that's close enough.

It looks like something is blocking access to the drive. Another bit of software maybe? Does the same thing happen after rebooting? Check the drive are working ok (no yellow exclamation mark) in Device manager. Try running Microsoft's CD/DVD Fix It utility.

This was covered in an earlier post. Number 8 to be exact. You'd have to try your drive to see how it behaves with DVD-R media, I don't know what it'll do.

There are no options to change. You'd have to go by the initial burn and verification process. Assuming the image/device md5 listed after the verify stage has completed matches what's on the website, make note of the padded md5 ImgBurn displays (if any). That would then become your reference md5 for checking the disc. Once you've got that reference md5 written down somewhere, you can use verify mode to generate an md5 for the disc and compare it to it. If you use media your drive doesn't 'pad', there will be no padded md5 listed and then the md5s should all match. (Image, device, website). You can then compare the website md5 against the md5 generated in verify mode.

It looks ok to me. As per one of my previous replies, drives will round up what they burn to the nearest ECC block, especially when burning DVD+R media... which is what you're using. That's why you have 2 'Device' MD5 values. One 'padded' and one that isn't. The one that isn't padded matches the image md5 and should hopefully match what's on the website you downloaded it from.

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.