LIGHTNING UK!

Do you really mean CDRW? It will only format brand new DVD+RW (or those that haven't been fully formatted), nothing else. All others are erased or simply overwritten.

With enough time and effort, anything is possible. This isn't something I would do though.

The full log would help. I've never seen that status code (error) from a drive before... weird!

This never really occurred to me in the initial v2.0 release. Since then, someone else already pointed it out and so I've already made the next one (v2.1) maintain the hidden attribute.

Please understand this isn't an ImgBurn problem so to speak so it's not a case of finding something compatible with it. AnyDVD will cause all programs that verify against the original ISO file to fail. Just disable it via a right click on the system tray icon, it takes about 2 seconds.

Sorry, this won't be happening.

I guess Silicon Image aren't building their drivers properly then. Seen a couple of instances where this API call fails and the machine shows signs of certain SI hardware / drivers).

Oh and burning wise, it's better to use ImgBurn than DVD Dec anyway. It's far Superior, especially for DL DVD Video stuff. You just have to disable AnyDVD because it has a nasty habbit of changing data on the freshly burnt disc before that data reaches ImgBurn's Verify proceedure. Because the data has changed (compared to the image ImgBurn just wrote), it will fail verification.

What 'mode' did it mention on the main screen where it displays the 'Sectors' info? It's probably just in a format where the user data takes up more than 2048 bytes. If that's the case, it's impossible to convert down to 2048 bytes without losing data - hence it won't convert.

Whatever you add in that list is added to the root. So if you add a folder, the folder appears in the root (not its content - unless it's the only folder and you click 'yes' on the prompt). If you add a file, the file appears in the root. So as you're adding 2 files (with the same name), it's as if you're adding 2 files (with the same name) to the root directory. If you want the one in the temp folder to be in a 'temp' folder you need to 'preserve full pathnames'. Basically, think of that 'Source' box as THE root folder.

Have you installed / not installed some drivers that were / were not installed before? How about any other programs that do stuff with drives etc? If the message really won't go away and you can't find the reason why, just diable the 'Disable Media Change Notification' option in the settings.

Thanx, I'll give it a shot... tho I think I'll need to disable that option rather than enable it. It's lowercase filenames that choke the NT loader, if I'm not mistaken. Sorry, I misread your previous post. I read 'uncheck' as 'check'. So yeah, you'd need to turn that option off. It's off by default anyway - hence my added confusion

Check the 'Allow Full ASCII Character Set' option. That'll allow you to use lowercase file names in the ISO9660 filesystem.

Uninstalling Diskeeper 10 does indeed sound like an odd fix! Do let me know if the problem comes back though because I'll install xp64 and take a look.

No not at all, I just see no point in supporting a format that's not really used by people!

Just because v2 can do more (in the sense of having a 'Build' mode), it doesn't mean anyone is forcing you to use it! The existing modes work exactly the same as they've always done.

Something so low level as that is purely a machine issue, not ImgBurns. How positive are you that the miscompares were related to the RAM timings? Did you try burning the same content to a disc time and time again, with and without that setting? With 1T it ALWAYS failed and with 2T it was ALWAYS ok - without having changed ANYTHING else? Do the miscompares vary if you just do a verify manually in 'Verify' mode several times or are they always in the same places at the same sectors?

Hmm I'd have thought the 'Verify' checkbox on the initial screen would have been a dead giveaway!

Support for 'Layer Jump Recording' is something I spent a lot of time on but it turned out to be no use for what I (we) needed it for. That 'need' was to make DVD-R DL media behave like DVD+R DL when it comes to layerbreaks. With DVD+R DL media, the layerbreak position can be moved around. On DVD-R DL media that's not possible, it will always totally fill the first layer up before going onto the second. From a bit of quick reading, I thought LJR was the answer but like I said, it turns out it wasn't. That option is pretty much just there for possible future use, for people who know what they're doing and are looking for exactly that feature, or for people who just want to mess about with that technology. The fact that you asked about it means I can assure you that you don't need to use it If you're really interest in it, take a look at the MMC v5 specs over at www.t10.org

Nope.

Even if PgcEdit / IfoEdit do point out that the file is padded, I don't think there is anything 'wrong' with it. The player is only going to read what it needs to so who cares if there's 4k of slack space at the end of it? IMHO, there's no need to 'fix' the IFO files just because of a little slack space. Of course if you have other bits wrong with your IFO files, that's down to whatever killed them in the first place. When building an ISO, you generally assume the files were already ok for burning. I can't see an authoring program producing a VIDEO_TS set that just simply wouldn't play, that would be crap! (and I'm sure people would moan so they fix it).

DVD Dec didn't find these errors, it reported everything as successful even when it wasn't. Detection of these types of errors is new in ImgBurn. As corny said, use Verbatim discs, the others are useless. Also, update your drives firmware - you're a few versions behind. http://forum.rpc1.org/dl_firmware.php?download_id=2109

It's up to you if you want the program to test and see if the disc burnt correctly - that's what 'Verify' does. If you're not fussed about verifying your burns, just uncheck the 'Verify' box on the front screen.

Not sure if I could support it, but even if I could, I wouldn't!

'Clear Recent Files List' on the 'Events' tab in the settings has that effect. I realise it's not named as such but I figured if you wanted to remove one set of history, you'd want to remove the others too! I'll see if I can't get the mds extension to use the same case as the original one. I'd thought about doing it before v2 was released but then figured was there really any point?!