LIGHTNING UK!

If it burnt and verified ok, it's beyond the scope of what this forum is here for. http://forum.imgburn.com/index.php?showtopic=12200

Am I supposed to do something with that? If you have a problem with ImgBurn, please tell me what it is and provide information from ImgBurn itself, not another program.

I leave the old one just to annoy people

You can't magically add support for something the hardware wasn't designed for. I've only ever known of 1 drive to have a firmware update to enable burning a different format of disc, but it could already burn DVD-R and was just adding support for DVD+R (or vice versa). I've never seen a firmware to enable DVD burning on a CD writer. Buy yourself a new DVD burner.

There is no problem with any of that stuff in the program itself. Such problems would cause issues for everyone and that simply isn't the case. It's down to your drive to do what's asked of it. If it returns errors / incorrect info then that's totally out of my hands.

Like I said, you need to be making a fair comparison and you might not be. You can enable something called 'spare areas' when formatting a disc which in turn enables a drive's 'Defect Management'. That can help to overcome bad sectors by remapping them to the 'spare areas' on the disc. ImgBurn defaults to formatting without spare areas because it frees up more space on the disc that can then be used for user data.

It works ok with the UTF-16 files that ImgBurn itself can spit out. Likewise, it's able to read a UTF-8 file that I created by opening the UTF-16 one in UltraEdit and saving it again (under a different name) in UTF-8. Can you upload the CUE file please, I'll test it here.

The first error is the real/important one. So your drive reported some sort of 'Write Error'. Try burning at 8x or 12x, your drive may do a better job at those speeds than it's currently doing at 4x. If it fails at those speeds too, try some discs from a different spindle. If it fails on those too, try cleaning it with a cleaning disc. If it still fails after that, invest in a new drive.

Others programs don't all erase like ImgBurn and don't catch all the errors ImgBurn does. That's especially true of programs that don't do their own drive I/O and rely a 3rd party burning library. At the end of the day, the drive has complete control over these things so what fails in one program will fail in another too. You just have to make sure you're comparing apples with apples and not with oranges. You can see here that ImgBurn works just fine with BD discs when the hardware / media do what's asked of them. http://forum.imgburn.com/index.php?showtopic=16152

I'm sure if you google for them you'll find a DOS bootable floppy disc image that loads CD-ROM drivers. Add that as the bootable image part of a disc you burn and you're away. There's no way of knowing (without burning it and testing it) if it'll support your machine and CD-ROM though. If you find one that does support your machine, all you have to do then is add the firmware flasher and firmware binary to the disc. Then from the command prompt once the disc has booted you'd change to the drive letter of the cd-rom and load the flasher. The flasher/firmware files on the CD won't be any different to what you'd have copied to your DOS bootable USB stick so I don't see why it would be any more reliable.

That's via the 'Burner Max' firmware yeah? That's totally different. The firmware has been modified for that specific task... and it isn't really overburning because the firmware thinks that's just how much free space is on the disc.

If you've already tired to burn 2 discs, one with 'DVD+R Reserve Track' enabled and another with it disabled and they've both failed at exactly this point... >> W 22:39:55 Failed to Write Sectors 2295104 - 2295135 - Reason: End of User Area Encountered on This Track ... give up, your drive doesn't support overburning.

They built the master image/disc with ImgBurn. That master disc was then sent to the replication/duplication plant and loads more identical discs were then created - ALL of which will have the 'ImgBurn' Imp ID because that's what created the master image/disc in the first place. I've already told you that... several times. For someone with 'Interests' such as yours, I find it a bit weird that you seem to be struggling to grasp what I'm telling you. If I didn't know better I'd think you were just trying to wind me up.

ok and does it do the same with 'DVD+R Reserve Track' enabled in the settings? It doesn't matter what custom size you set just so long as it's beyond the value of 'Free Space'. Like I said before, you want to figure out if your drive can do it 'full stop' first. If it does let you overburn and the overburn amount (custom size) you've selected was successful, you just increase the custom size and try again until it errors out.

You can create a master image for replication/duplication with whatever program you want. They've just decided to use ImgBurn.

Discs burn from the inside (near where the hole is) to the outer edges of the disc. If you overburn a disc, you're just writing data closer to the edge. The edges are the least reliable part of a disc, hence why you wouldn't normally burn on those parts - or at least not outside of the disc's specifications. It's like having a fence 1m from the edge of a cliff to keep the public safe... but now you want to move the fence so it's only 10 cm away. What if the edge crumbles away and people fall off?!

It has what?! That screen shows exactly what it showed in the log when you read the disc.

etfsboot.com is a Microsoft thing, I have no idea what it actually does - but it's not going to load a random exe for you or get you into DOS. A DOS bootable usb stick with the flasher and firmware binary on it should be all you need. I really wouldn't waste time with a bootable CD, I certainly didn't back when I was running an Intel motherboard.

Press F5 and use your eyes.

If that 'Betrayed At 17' was an original rental disc, the people that authored and created the master disc must have used ImgBurn for the job. I bet that 'TOWER_HEIST_G51' ISO doesn't show ImgBurn in the Imp ID field once loaded in Write mode.

But that source disc has a file system built by ImgBurn. Get a disc that *wasn't* built by ImgBurn and read that. The ISO created from that (non ImgBurn built) disc won't display 'ImgBurn' as the Imp ID when you load it in Write mode, I promise you.

You really haven't. Post me the log where you've read a disc to an image file so I can see the implementation ID before and after the read. There's no code in ImgBurn that can even do what you're saying, so I know it can't possibly be happening!

You haven't been in Read mode if the Implementation ID is now 'ImgBurn' in your images (and the source disc doesn't also show 'ImgBurn'). It would only say that if ImgBurn has actually build the ISO (and the file system within it).

In what way?! It's a drive thing. Either they can overburn certain discs a bit or they can't. I don't make the rules with this stuff.

There's only 1 option you *might* need to change - the 'DVD+R Reserve Track' one in the settings on the Write tab. If you configure Discovery mode to write more data than listed for 'Free Sectors' in the disc info text on the right, it'll either work or it'll error out. If it fails with 'DVD+R Reserve Track' disabled, try it on another new disc with it enabled. If it fails both ways, your drive can't do it. Of course failure comes at different levels. It writing to anything beyond the 'Free Sectors' value is a success. Where it gets up to beyond that point is the amount of overburn your drive can do on the media you're using. Different discs will allow for less/more overburning.