LIGHTNING UK!

The best way to see what DT is emulating is to load ImgBurn in Read mode and point it at the DT drive. The 'Current Profile' in the disc info on the right will tell you everything you need to know. Make sure your DT is up-to-date too because they messed up in the first version that reported BD media for large (> DVD DL size) images.

Notice he said 'in an external enclosure'. Internals and externals are the same drives, just one comes in an enclosure and one doesn't. You're free to pickup your own enclosure and put any 'internal' drive into it that you fancy.

It doesn't work like that. If you load the large image in DT, it's down to DT to make it look like a BDROM (or BDR actually). Anything over normal DVD DL size should be loaded like a BDR and PowerDVD will then play it. The MDS file is normally used to tell DT which media type it should emulate but ImgBurn only ever makes DVD style MDS file - and the DT people won't give me the updated specs so I can make BD ones. Ditch DT and use Virtual CloneDrive instead. You can easily make a .DVD file with the appropriate 'MediaType' parameter and VCD will then emulate that media type. Actually I believe it will parse the ISO and do that automatically now - just make sure you get the latest beta version from the slysoft forum.

So basically, you're getting the locking issue when using Build mode (and nothing but Build mode). I assume 'Output' is always set on 'Device' ? And you're only burning single copies?

See if you can figure out anything specific you're doing (i.e. some sequence of events) that makes ImgBurn randomly have 4 handles on the go. I can burn from a queue all day long and not run into that problem so it must be something more complex than that.

Is your drive connected to an NVIDIA controller?

Like I said, ignore the ISO exists (do not load it, do not do anything with it - besides giving it its proper name again). Load the DVD file and burn.

Please read the FAQ, it explains the problem and tells you how to figure out what's using the drive.

You've messed things up by renaming the file. sw-racepro.iso.iso should be: sw-racepro.iso Then when you load the iso it will tell you off and load the dvd file instead - which is what you should be doing in the first place (i.e. ignore the iso). The layer break info is in the dvd file and it instructs ImgBurn on how to burn the double layer iso image.

Buy the 2.4x verbatim discs (MKM-001-00 dye), not the 8x ones (MKM-003-00 dye).

Decompress the exe using UPX and then try it. You might have some low level tool (AV/spyware/adware monitoring etc) installed that sees the UPX compression in the exe file and thinks it's something nasty. The program has a lot of error catching stuff built in so it's hard to get any sort of error within the code and the user not then get an error message on the screen. It would have to be really bad for it to just vanish from memory without an ImgBurn error OR a Windows one.

Put the disc in the drive and then copy + paste the disc info from the panel on the right.

So that proves it then. You've still go some low level app running that's killing the ImgBurn process - probably because it's sees the UPX compressed EXE and thinks it's evil.

Yup, dispute it all the way. You were ripped off - plain and simple.

0 = fine 1 = operation couldn't start (no media?) 2 = write/build/read failed 3 = verify failed That's your lot!

Buy the MKM-001-00 ones, your drive might offer 2.4x on those.

They're perfectly normal. The drive just takes a second to recalibrate the laser power in an attempt to give you the best burn possible.

Hi, I believe someone reported the missing window issue a while ago and I think I've sorted it for the next release.

You don't add all the dvd, mds and iso files to the queue, you only add one of them - and that can either be the dvd one or the mds.

Your source files are not complete. Don't waste any more discs until you've sorted them. This 'Fix VTS Sectors' is in internal process.

Sorry, I got myself confused there. It's the 'Standard' one that ImgBurn limits to A-Z, 0-9 and _. For the DOS and ASCII options it just blocks the reserved characters - such as : \ / etc. ImgBurn uses WideCharToMultiByte with 'CodePage' set to 'CP_ACP' when making its ISO9660 file identifiers.

Decompress the exe with UPX, that normally gets around whatever crappy software is preventing it from loading.

Different OPC Cynthia. That one wouldn't have any effect on the burn graph as it's just one command issued before the burn starts. The Walking/Active/Online one is what causes the regular dips in the buffer/write speed graph.

No idea, sorry. Reinstall Windows.

You're going to need to provide examples of what you're seeing. AFAIK, ANSI is ANSI. The character set is fixed and ImgBurn limits the letters used in file names to the correct ones.