LIGHTNING UK!

Try changing the write type in the settings to incremental. You might just have an iffy drive. It should be working fine with that drive/firmware/media combo but obviously it isn't for you. ImgBurn doesn't make the errors up, it simply reports back what your drive/drivers tell it.

switch to read mode, copy + paste the disc info from the panel on the right.

Just decompress the exe using UPX. It's the compression that these programs have problems with... and the variation of compression used can change with each release because UPX tries about 80 and picks the best.

Everything thinks that file is 6 mins 18 secs. So I guess the issue is with the way you're recording/saving it.

What are we betting here...another 'too many secrets' problem? ston3d drunk, stick to your own thread(s) please. You don't belong in here unless you're actually helping - and you're not.

If you can upload one of the problem files somewhere, I'll take a look at it.

It makes no difference.

Are they actually made / branded by Verbatim or are they the cheapo knock-off's?

dchall8, Are you and 'quixotic25' the same person? If not, why are you in this thread? If you are, why do you have two users?!

That has nothing to do with your question / post / problem / thread.

Mirror 8 is the new Mirror 7 - it moved up one.

Yes, if the RAR contains a file that's 4GB in size (or larger), you'll need to extract it to an NTFS drive. If you only have 1 drive (and it's not NTFS), you can convert it to NTFS without losing any data. Open up a command prompt window and type: convert c: /FS:NTFS If you want/need to convert a drive besides 'c:', use a different drive letter! i.e. convert d: /FS:NTFS

That's not going to help the open file dialog boxes though, they're pure Windows API.

At least that one got the correct layer break address during the Verify stage. As the drive is unable to read the disc I can only assume that it's made a duff burn - that or the reading ability of the drive has taken a serious nose dive. Have you tried cleaning the drive at all? If not, that might be an idea.

If the standard API 'open file' dialog boxes are taking ages to open then it's probably a disconnected/messed up networked drive or something. As Shamus said, the startup time should be a few seconds (sub 5 really).

Oops I missed the 'any' part Convert if you want them to play on 'any' player. Don't convert if you just want them to play on your player.

Can you try to verify it again manually in Verify mode please? I don't really know where that odd layer break LBA came from!

Hello and Welcome If you *only* used ImgBurn to burn the AVI, yes your player must support them and hence there's no need to convert at all - thus you'll be saving yourself loads of time.

If it makes a CCD file then the program has to name it IMG as that's all the CCD will load from. So basically, it's by design. You should also see a log entry telling you it's been done. Something like... "Destination File renamed to: ....."

I'm unsure if it's a drive / driver thing or just that the drive is in use by another app and reacts slowly to unbuffered reads... who knows! The whole idea of it was to take the OS's caching out of the equation as really there's no point in the OS caching what ImgBurn is trying to read. It works for some and not for others - luckily I added an option to enable/disable it

Update to 2.4.4.0 too, if has a workaround for the buggy Nvidia drivers you're running.

Go back to 2.4.4.0, go into the settings, look on the I/O tab and turn the File I/O buffering back on. Your machine obviously can't handle it not being on.

Build mode is currently designed to work with an existing disc structure. If you need something more than that, don't use ImgBurn.

No, ImgBurn is a just a burning tool. It burns exactly what you feed it - no compression, no nothing.

It's impossible (so far as ImgBurn is concerned) for them to be remembered between opening / closing / reopening the program but then forgotten at a reboot. Either they're written to the registry or they're not.