LIGHTNING UK!

This is the ImgBurn support forum. ImgBurn burns as-is and so doesn't really come into it. I suggest you Google what you're looking for, the whole NTSC -> PAL (or vice versa) thing has been done to death.

Your drive doesn't like the disc you're trying to use. A firmware update may fix that. Failing that, get some different discs.

Don't do what mmalves said, it's wrong info and could cause other problems. If anything you'd want to checked 'Yes' anyway to make sure it was always correct for DVD Video - but of course it would then be wrong for your mp3 player. So basically, just stop being so lazy. Make a couple of IBB files. Save one where it includes Joliet and one without. Then load whichever one you need.

Must be corruption somewhere along the line then. Check the cable to the drive and test your computer's memory using Memtest+ or something. No need for debug mode unless I specifically ask for it btw. It actually makes logs much harder to read.

What's wrong with just changing the file system dending on what you're going to burn?

DMA wouldn't apply to the burner if it's USB, but it could apply to the hdd.

When you're doing scans, select 'Block' rather than 'Line', it looks a lot better. Also, save your screenshots in PNG format and not JPG. They look loads better. Burn DL media at 2.4x. Obviously make sure both drives (writer + scanner) have the latest firmware.

Or leave it on 'AUTO' and configure the 'Automatic Write Speed' feature as per the Guide so you never have to worry about setting the speeds for that media in the future. http://forum.imgburn.com/index.php?showtopic=4249

Try slowing the burn down too, you might have more luck. 8x or 12x seem to produce the best quality burn.

Nec I would think. It all depends on what / how they've implemented it in the firmware though. The tabs in the bootype window are the for 'type' of commands the drive supports, not for the brand name stamped on the drive.

I can't do anything with that. The drive is reporting some enormous size for the disc. I can only go by what it's telling me.

Ok so now the drive is saying it can't write to the disc. Time to get some Verbatims then I guess!

All you can do is update the firmware on the drive and change to different discs. At the moment the drive is basically saying it can't initialise the disc - hence the error message in the status bar - 'Logical Unit not ready, Cause not reportable'. No software will work until the drive sees the disc properly.

The log isn't showing any error. What do you think the problem is? What's the message in the status bar? Ditch the Ricoh discs and buy some decent Verbatim DVD+R DL ones instead. Burn at 2.4x You can also update your firmware to A117 - http://forum.rpc1.org/dl_firmware.php?download_id=1841

Try to get some Taiyo Yuden CD's. They're about the best you can get. If they don't work, nothing will.

ImgBurn burns as-is. So if you want a DVD Video compliant disc you need DVD Video files - i.e. IFO/BUP/VOB files.

There's nothing wrong with that except possibly the discs you're using - RITEK-D01-01. We recommend that you ONLY use Verbatim DVD+R DL media.

I've also added a '/PORTABLE' CLI command (and reg setting) for the next version so it will save settings (to an ini file or whatever it's configured to do) but won't touch the file extension stuff (which it normally would regardless) that is always registry based. So now there are combinations to suit everyone's needs.

Or when you're in one of the writing modes, hit the little button with a CD (and a rubber - erasing it!) on it that's just below and to the left of the drive selection box.

lol well if nothing else, your post has let me fix a typo in the word 'Eror' - or 'Error' as it's supposed to be Try this firmware update. http://h10025.www1.hp.com/ewfrf/wc/generic...=en&lang=en If it doesn't work, get some different discs.

If you're getting the same message then it makes sense that the exact same fixes / suggestions apply to you. Update the firmware Change media Clean the drive Buy a new drive

It allows you to verify it at a later date or in a different drive, nothing more. Data burnt directly in Build mode is still subject to 100% verification but it's obviously only valid so long as the information about that 'on-the-fly' image is stored in ImgBurn's memory.

Disabling it should be fine. The thing to remember is that I/O errors are drive/media issues. Miscompares *could* be due to 'other software' (i.e. AnyDVD) manipulating the data on the fly. 'Other software' would not introduce I/O errors.

The CLI stuff only manipulates existing GUI settings. As changing the volume label obviously isn't just a setting somewhere (you have to bring up the 'change volume label' screen, load the file, change the fields etc) it's not possible to do it - well, not without loads of feature specific coding. You do actually need a CLI app for this, not a GUI one that just happens to accept a few CLI switches.

ISO9660 only uses the 1 descriptor though and it's always at sector 16. UDF has loads of descriptors and they can be in different places depending on which ones are present.