LIGHTNING UK!

Yes, but it's the FULL path remember! So if you had C:\test\test1\test2\some document.txt and added that, with full pathnames on you'd have 'test' in the root folder, then 'test1' inside that, 'test2' inside that and then 'some document.txt'. With full pathnames off, you'd just get 'some document.txt' in the root. There's no way to just get 'test2' in the root and 'some document.txt' inside of it. ImgBurn has really been designed for building images where you've already got the structure of the disc correctly laid out on your hdd. There are less issues with being in the root Vs not being in the root if you just add a folder rather than a file from it.

It's magic. I updated a few bits but some sites didn't mirror it again. If you look at the main website you'll see the reason for one of the changes.

You'll need to recreate the image. So extract everything from it and then 'Build' a new one.

I guess you have an LG drive then? If you search this forum you'll find a little tool you can add to your startup folder.

The only place I'd add a 'Stay On Top' option is to the context menu on the program's top left icon (right click it). That's how I've implemented that option on the 'Queue' window. You could always use Copy + Paste instead of Drag + Drop if it's a pain switching windows or you don't use a high enough resolution to let you see multiple windows.

I'd go with firmware / media myself. The image format does look different to most (all?) PS2 stuff I've ever seen though.

AnyDVD can/will change whatever it needs to. That is in no way limited to just modifying a couple of IFO files! It's all down to the content of the media it's looking at and how you have it configured. A search of this forum would find you a perfect example (from only a few days ago) where it was modifying all of the IFO/BUP/VOB files on a freshly burnt disc, that then caused loads of 'Miscompare' errors during the verify stage.

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!