LIGHTNING UK!

It would probably have been easier to put it into a resource file if I was using Visual C++ but the Borland apps work differently. I've the feeling it will be a huge job to make it so it can read every single bit of GUI text from a file that I'm in no rush to do it! Thanks for the offer of helping to translate or whatever though.

Pretty much, yup. It just has 'loading, please wait...' under it too.

The layer break (switch) position on DVD-R DL media is fixed, on DVD+R DL media you can move it around. So unless your DL image was originally built with a layerbreak at EXACTLY the same point the fixed DVD-R DL one is at, you'll never get a proper burn. When the physical layerbreak position doesn't match the IFO files properly, some players will just hang / crash etc. If you can move the physical layerbreak position on the media (as is the case with DVD+R DL), this clearly isn't an issue.

DAO and SAO are (internally) identical. The correct name, going by the mmc specs, is SAO (for CD) and DAO (for DVD). ImgBurn cannot burn multitrack / session images anyway so don't bother wasting your discs!

It's all hardcoded, hence why nothing exists so far! I would never add a systray / minimised option to cli. It's unfair to 'hide' the app, I've spent too much time on it to have people think some other program is magically doing the burning.

I'd overlooked the issue of auto calculate being enabled when doing things via CLI. I actually fixed that about 10 seconds before I read this post. (Spooky!) CLI stuff is really of no interest to me, it's there for those that use it. I don't use and so I don't really do any testing on it. Also, CLI parameters only apply once (they're reset after being used). So the auto calculate probably used up the initial settings meaning the real build then prompted again. Ignoring the auto calculate option on a CLI build gets around all these issues and that's what I've just implemented. Thanks for taking the time to look into + report this.

Do you have a log of the burn? Which version of the program were you using?

Acronis do some great utils for various disk based activities - if you're ever in the market to buy another one!

They're normally only copies of icons taken from the exe's anyway. God knows why MSI's work that way.

davidw89, If you've added a single folder to the 'source' box in ImgBurn, that folder WILL exist in the destination ISO (or drive). UNLESS you click 'yes' to say it's the only folder and it should represent the Root folder of the image, where it will then only put the contents of that folder in the image.

God I made a real arse of myself there didn't I ! lol Ok so I looked at the code and you're quite right, the code is set to always compare Build mode written data against the original image (bunch of files). I honestly have no idea why I made it that way originally, perhaps I had a reason back then.... now I don't. I will change the code so it also looks at the checkbox in the Write tab within settings. Once again, my apologies for getting muddled up.

That option is nothing to do with verifying after build mode - and as such has no chance of having the effect you want it to! You want the 'Compare Against Image File' option in the 'Write' tab in the normal 'Settings' screen. Of course that will then mean none of your burns will verify against the original file data. The option in the main verify screen you're talking about is for a standalone verify. Where you can either just check the disc is readable or you can compare it to an existing image.

Even if the ISO was corrupt, it wouldn't stop ImgBurn burning it. The drive just sees the data as data, it doesn't know (or care) what it is. Whilst you might get error playing the corrupt disc back, it wouldn't make any difference to the actual burning phase.

There are loads of places you can mess around with for Autorun stuff. ImgBurn can control the major one which is a single value for all drives. Then there's a DWORD value where each bit represents a drive letter. I believe there's another to enable/disable on certain drive types. Then theres an autoplay data cd/dvd and autoplay audio cd/dvd option too. I'm sure google could help you find all the keys you need.

'Operation Aborted' mean you aborted/cancelled/quit the build! It shouldn't be anything to worry about as YOU caused it. As Kenadjian said, ditch the Ritek DL's and go for Verbatims.

So you don't like the decent new one but were ok with the previous 'box' one? On principle, I don't want to remove it (it serves a purpose) but I might allow reverting to the old style for those of you who prefer the simple things in life.

Although it might seem like the program is at fault I can assure you it's not. Those errors come from the drive, it's impossible for the program to make them up. If it can't read something, the drive returns an error. The program mearly turns it from a couple of numbers (known as 'sense data') into plain english. That's the 'L-EC Uncorrectable Error' bit you're seeing there.

Do you get an actual error from ImgBurn? If you do, copy + paste the entire log please. If you don't, there's not much anyone can do. It's probably your drive/media so check for firmware updates and buy better discs.

From what I've seen of ratdvd, it's like the slowest util going, so I/O throughput probably won't be a big issue!

Just so I know exactly what you mean when you say 'crash', are we talking the blue screen of death? Computer basically reboots? If we're just saying the windows gui freezes, you should still be able to see the log window - yes? Go back to the old fashion method of using a pen + paper to write it down! I only need the last few lines, the term 'CDB' should be in one of them, and then its 'Interpretation' (i.e. what it means in english!). If you're getting BSOD, you must have a dodgy driver or something in there somewhere. Does it matter where the IDE drive is connected? i.e. primary / secondary channel - master / slave device. How about a USB -> IDE adapter. Does it still mess up then? Try looking at what filter drivers you have installed by using the freeware util you can find at www.bustrace.com If you get a bsod, you should be able to get a memory dump from windows itself. Probably in C:\WINDOWS\MiniDumps or somewhere like that.

It means your drive can't read what it just burnt. Are you using crappy discs by any chance? Is your firmware on the drive up-to-date?

Well I would guess that Allow means everyone ON the list has access and Deny means everyone NOT ON the list has access. So unless you want to add every MAC Address in the world to the list (other than your own!), I would go with 'Allow'. Of course if this is a per MAC address option rather than a global one (lol global would be shit!), just type in your own ones and select Allow.

If you're after pure (sector by sector) disc to disc copy, you'll have to look elsewhere (stick with nero). ImgBurn can't do it.

Hardly any drives will burn at 1x now on any media. Just look at the 'Supported Write Speeds' text in the info panel on the right. Verify speed isn't anything to do with the burn speed. The program configures the read speed bit at max when it sets the write speed, it also then sets it to max again before the verify for most drives - unless you've specifically set the 'Set Read Speed' option in the settings. If it's reading slowly, either that's all your drive could manage or you don't have DMA enabled. You can change the buffer size yourself, I don't need to do that for you. Just look in the settings.

wpa / wpa2 is the encryption type you want. You then just add a password phrase of 8 - 63 characters. Something like 'ImgBurnRocks!' Just make sure you have recent wireless drivers for your laptops or they might not support wpa. Don't forget the firmware on the router too!