LIGHTNING UK!

Look on an xbox related site, this forum is for ImgBurn.

With that specific error, yes.

Mode 2 only applies to CD discs.... so I guess it's a CDROM version yeah?

If it's not a movie DVD, there's no IFO file to get the layerbreak info from. The physical layerbreak position of the DL media will be showing in the info panel on the right when you have the disc in the drive. Just scroll down to the bottom of the text.

Try the 1.21 firmware update. After that, yeah, consider them to be coasters

Yeah, cells or chapters. You just really need them around the midway point - i.e. between 3 and 4GB if the image is 6.7GB

You can't burn multiple iso images to one disc, no. An ISO is an ENTIRE disc image - even if it's actually a lot smaller than the destination media. If you want the contents of images on the same disc, extract them all somewhere and recreate the disc.

You need to insert some chapters / cells so that you can split it nicely. If there aren't any in the regions that 'should' work as a layer break position, there's no way to make a proper layer break. Using other tools wouldn't get around that, they'd just be ignoring the specs if they worked. I too could just burn it and forget about correct alignment, but I decided not to.

vade, Please don't hijack threads. Normally I'd now tell you to go make your own, but as it's pretty clear you're trying to read a protected disc, I won't bother. ImgBurn will not read protected discs and there's to be no discussion of such things on this forum, capisce?!

If you say you've tried 2 machines, can I assume that those machines (when running a real copy of XP etc) work fine? When under wine, what happens if you run a standalone verify? Does it always find errors in the same sectors / byte locations?

It would really help to see a log of you burning something. The program doesn't ever really 'hang', it just waits for your drive to finish processing certain commands and may appear to have hung. When the drive responds (be it with success OR failure), the program will continue. If the drive stops responding - or it's state never changes (as can happen when doing 'sync cache', 'closing track / session / disc'), it's normally a sign that the drive doesn't like the discs you're using. If you're not doing so already, use Verbatim or Taiyo Yuden media. They're by far the best.

New drive or new media... take your pick! They just aren't getting along very well at the moment, hence the error.

You can't burn complex images (which VCD's are) with Imgburn. Single session / track only - and that's especially true if it's an nrg file because I don't have the nrg file format specs.

I'm afraid not, no. I don't know how to make use of additional CLI switches to get info into my script. If you're doing this for a company, why not just stick the exe (plus other files) in a network location? Then you only need to update it in one place. You could also make a simple MSI for it and push it out that way.

It's '/S', not '/s' (case sensitive - lol, don't ask me why, I didn't make NSIS!).

ImgBurn is just an image / file burning tool. It won't make anything special for you, everything is burnt as-is.

Discovery mode just burns zeroes (i.e. 00 00 00 00 00 00 00) to the disc, you know that yeah? You simply select how much you want to burn and then click on the Go button. Depending on your settings, the drive will then burn that amount of 'nothing' to the disc and then verify it (attempt read it back). When it's done, you can examine the graph data in DVDInfoPro and also perform PIPO scans if your drive supports it. Take a look at all the posts in the 'Drives & Media' forum. They're all done using Discovery mode + PIPO scanning in DVDInfoPro/CD Speed.

This is all linked in with some other CLI issues where the mode is switched whilst the program is already busy in a thread. (Those issues already exist as bug reports) I believe I have fixed the issue in the beta I'm currently working on and it will of course be available whenever the next 'final' release is made to the public.

That depends on what you're doing, often you might not want hidden + system files. Everyone has their own way of doing things and it's not hard to locate that settings. Sorry but it stays as it is.

That would also not cause the verify to fail. It's failing for some other reason.

Same applies, check for firmware updates and buy some decent media.

The program doesn't actually have control at this point, it's stuck while the DeviceIoControl API call is running. Even if you terminate the process, it won't recover because all the I/O subsystem is screwed. Just reboot the PC. Unless you can find a tool to force a bus reset, that's all you can do (and even they can often cause a BSOD). Do yourself a favour and buy some decent discs.

Scroll up in the window you copied that one from?! Failing that, look in 'Help -> Imgburn Logs' In your previous thread, Blutach told you to update the firmware on the drive, did you do it? http://forum.imgburn.com/index.php?s=&...ost&p=47595

Table Of Contents. That message is coming directly from your drive - it's unable to read the disc.

Posting a log of the burn would really help. "Invalid address for write" normally occurs AFTER another error.