LIGHTNING UK!

You don't install them inside ImgBurn, the filters are installed for the whole system to use. Normally when you get the filters you aren't given options about where to install them, they're just installed. ImgBurn calls up DirectShow and DirectShow knows where to find them.

1. Check with that manufacturer of your PC to see if there are any firmware updates for the drive. 2. Slow the write speed down to 8x or something 3. Buy better discs. Taiyo Yuden or Verbatim. v2.4.1.0 is out now btw. If you want to update the DVDFlick version you need to copy the ImgBurn.exe (and other files) over to the 'C:\Program Files\DVD Flick\ImgBurn' folder.

Please post your log.

An image created via Read mode is a 1:1 copy. That should definitely work when mounted in DAEMON Tools.

Ok, so the fix for this (as now confirmed by the OP) is to disable Unicode support for the UDF file system. You do that via the 'Disable Unicode Support' checkbox on the 'Advanced' -> 'Restrictions' -> 'UDF' tab in the main window when you're in Build mode.

Please post the log, then we can help you.

AFAIK, all the bootsectors do is point to NTLDR. Was that really lowercase in the folder on your hdd? If so, what on earth made it that way?! btw, the silent update on the ImgBurn.com mirror has this change implemented already, just incase you want to try it

It's like the music CD's you buy in a shop. i.e. ones you can play on *any* standalone cd player - without them needing to support mp3/wma etc.

I doubt less audio savvy people would be working with 48khz source flies

Sorry, I'm no audio guru and have no idea what this 'abx' stuff is / does. Technically ImgBurn isn't doing anything wrong, so if there's something wrong with what's on the CD you'll be better off discussing the filters that perform the 48 -> 44khz conversion on a site that's appropriate for such talk (and I'm sure you already know about those!). Maybe between you, you can find a better filter for such conversions. Of if in doubt, convert it yourself first in whatever program does it best and then burn the converted files.

And you weren't running it in 'compatibility' mode or anything? Maybe it was the colour depth then, otherwise I'm all out of ideas!

Your directshow filter has just converted it to 44100 (which is what CD-DA is), shouldn't be anything to worry about. btw, 2.4.1.0 is a lot better for audio than 2.4.0.0 was - you should update.

Doh, ignore that... the option already exists in the form of the 'DOS' character set. You do not want to use the 'Standard' one. lol and I see the last sentence in your post actually said that. Ok, the option will be changed from ASCII to DOS then for Windows install CD's. I guess I was lucky that my original files already had the correct 'case' and it installed using ASCII.

I really don't get why that's a problem. If you take an original disc and service pack it, those options work fine - I tested it myself yesterday from an original SP1 disc which I then updated to SP3. If you use the 'Standard' character set then certain files will have their names changed. The only way to avoid that is to use ASCII. (ASCII allows for upper and lower case, plus additional characters) If MS didn't want the installer to work with lowercase files then they shouldn't have made them lower case in the service pack. Nothing else in MS world is case sensitive so why is the installer? Anyway.... I guess I need a new 'Advanced' option whereby ImgBurn will convert all the file names to uppercase in the ISO9660 file system or something. I wouldn't expect having additional file systems on the disc would cause a problem, the installer will only read from the one it knows about.

Could be the OS? If the commands aren't supported then the old one is used.

How comes you didn't just tell it not to check for updates when you installed it?

That's not an Audio CD image, it's audio files in a data image.

Nope, it's burn or nothing I'm afraid.

It's magic! Or maybe it's just down to a different file system implementation?

Please just trust me, it's not ImgBurn. You can't 'check' DMA settings, you need to do as the post in the FAQ says and uninstall the controller + reboot.

These things do just die I'm afraid - and your drive is ancient now. You might also like to fix your DMA settings as there's no way you should be getting so many 'Buffer Recovery' lines in the log if you're only burning at 4x. Well, not unless you were doing a million and one things on it at the same time as burning.

As I say, it's out of my hands. If the drive reports that it's not properly formatted (and 'prefer properly formatted +RW' is enabled) then I'll act on it.

The 'Formatted' status value is reported by the drive itself, it's not the program making it up. Formatting on one drive and then trying to write on another can have the same effect. (Drives prefer discs they've formatted themselves) If the formatted status changes when you've only just ejected + reinserted the disc, I'd have to say the drive is having trouble initialising it properly. Maybe you should try some other/better rewritables? I've got some 8x Verbatim ones that certainly don't have this problem. I do my initial full format on the disc when it's unwrapped and that's it then.... direct overwrite from then on btw, if you burn onto the disc with Nero it'll kill the 'Formatted: Yes' status and set it back to what yours currently says.

That's a machine configuration error and has nothing to do with the application. ImgBurn only reports what the drive tells it, the errors are not from the program itself.

They're using CLI already I believe, just that it should use the 'system' version of ImgBurn (i.e. C:\Program Files\ImgBurn) and not it's very own local copy.