LIGHTNING UK!

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.

Generally, you'd install the codecs so you can 'play' the files in any directshow compliant player. MP3 is built into the OS though.

Your AV might be kicking in slowing it all down, I really don't notice any on my machine. Perhaps if you have 1 million apps running on a Pentium 133Mhz, it might cause an issue To disable it, just uncheck the appropriate 'Warning' box in the Settings (General tab).

I don't recall ever saying a 'Copy' mode wouldn't be implemented, quite the opposite infact. You don't really need to suggest thing like this, they're 'no-brainers'.

It is indeed odd, like you say, it would be hell if it did it on data sectors! A 'sample' of CD-DA is just 4 bytes yeah? (remember I'm not an audio person and generally deal in 'sectors' when burning stuff!)

I didn't think MS's stuff had ever been case sensitive, that's a Linux trait.

When you say 'write offset', is it basically where I write 2352 bytes of data (i.e. an audio sector) to a certain LBA and then read it back and the two differ? If I compare the two, I should then find that at a certain offset, the data from the read begins to mirror exactly what was written, with the stuff before it just being junk? I guess it wouldn't be hard to just insert a few bytes of nothingness into the buffer before the real data. I noticed that during my own testing actually. The only drive that seemed able to write exactly what I sent it (so I could compare it exactly when read back) was my Lite-On.

You should probably give up with burning DL's on that drive and get yourself another one. If you don't, it'll end up costing you more money in wasted discs.

You can only do that on DVD+R/+RW media and you'd need to ensure the 'DVD+R Reserve Track' option is not enabled in the settings if using DVD+R.

No, something is wrong if it's saying that.

1. Drive is getting old 2. Firmware is out of date - http://forum.rpc1.org/dl_firmware.php?download_id=2110 3. Media is old/bad in the first place 4. ImgBurn version is old (and buggy!)

It's very unlikely that a disc would have something so close to a whole second without it actually being a whole second - so the problems comes from the whole 'pregap detection' thing not being accurate enough (drives can return different values each time I try). Snapping is my attempt to get around that. Turn it off by setting it to 0 if you like. It only applies when reading a disc, not writing one.

Fixed in silent 2.4.1.0 update on ImgBurn.com mirror. Shhh, don't tell anyone!

Looks like all of them are being enabled. Not a big deal as this doesn't apply to 99.9% of people.

It doesn't matter too much, I'll get them either way. However, given the option it's probably better if they're emailed. Use the address in the program's 'About' box. To make things easier, if you can just call it 'french.zip' that'll save me some time. Oh and change the 'sourcelangid' to 2057 (English UK) rather than 1033 (English US). TargetApplication can just be 'ImgBurn'. Thank you.

Fixed in silent 2.4.1.0 update on ImgBurn.com mirror. Shhh, don't tell anyone!

Fixed in silent 2.4.1.0 update on ImgBurn.com mirror. Shhh, don't tell anyone!

Interesting... you must have a v1.5 file that's not using unicode for the file name... I assumed they all would. Please email me the mds file so I can examine it properly. Look in the program's about box for the address. Thanks. btw, you can get around it by hex editing byte 17 in the mds file from 05 to some number lower than that. (i.e. 01, 02, 03 or 04!)

The 'Medium Not Present' message is what the drive is reporting to the program. So either you don't have a disc in the drive or the drive doesn't support the disc.