LIGHTNING UK!

You can't fix it, it's broken (yes, a bug). Like I said, you need v2.1 In the mean time, you'd get away with just turning off the 32k ifo/bup padding - as that's what's causing the error.

You need version 2.1 (when it's out)

It's not a dual layer problem, it goes for an disc where the program has to apply padding to the IFO/BUP. It has been fixed (and that has been mentioned several times). Just wait patiently for the next version.

Background formatting (which is the bit that takes the time) is exactly what it says.... a 'background' process. It's down to whoever makes the drive to show/not show progress in the form of flashing lights etc. Most do nothing. I can assure you that if ImgBurn sits there formatting it, the drive IS formatting. There are no minimum times etc built into ImgBurn so it'll finish when the drive reports it has finished.

You still have DMA issues even if speed isn't one of them. So you could still do with reading that post and following what it suggests. Incase it doesn't cover this too, update your motherboard / IDE drivers and check you're using a decent 80 wire IDE cable.

It calculates it based on the number of sectors it has to read or write. If those differ between disc / images, the MD5 is different. You will only get the one version of the MD5 - the one that's correct at that moment in time. I will not be changing anything in that respect, sorry.

It's a bit naughty of Windows to not provide the app with enough time slices (especially when set to 'High' priority) to maintain the buffer at 100%. I've added support for reg settings that'll override default thread priority. You can mess around until your heart is content when v2.1 gets released.

Could you please copy + paste everything from the 'Log' window. If the drive can't read the discs and initialise them properly (as would seem to be the case here), you need to: 1. Ensure your dvd drive can actually burn dvds - not just read them. 2. Ensure your dvd drive is running the latest firmware version. 3. Try some other (better) discs. Brand name means nothing, you need to go by the dye type used.

No, sorry.

I don't remember seeing such a field anywhere. I guess you could put one in one of the other fields though.

Indeed, ImgBurn is not for CDDA audio data - unless it's an MP3 type data disc you're building. I would recommend such an app but I don't know of any freeware ones. If I ever burn CDDA stuff I use Cdrwin from www.goldenhawk.com Have a go at Googling for freeware CDDA apps if that's what you're after.

Filling the device buffer is just sending the 'write' command to the drive. I'm not actually filling a buffer - so to speak. I *could* boost the priority of the write thread but that could starve others of cpu timeslices. If it's a real problem for you, stick to using Nero. If it was a widespread problem, you probably wouldn't be the only one reporting the issue and maybe I'd have even experience it myself. It's bloody hard to do anything about weird happenings when they're only occurring on 1 pc.

Thank you life, received and much appreciated

I can't imagine an ISO would fail. An ISO should be 2048 / MODE1. Does the image have a valid filesystem? What is the disc supposed to play/be used in? What created the ISO? If you can send me the first 5mb of the the image I'll examine it and tell you why it doesn't load. An NRG one... quite possibly as ImgBurn only supports the most basic type and I don't actually have the specs for the NRG file format. Never heard of 'TOC' images so I cannot comment on those.

ImgBurn can read from wherever explorer can, that's just how things work in Windows. Build mode is for *any* type of files, it's not specifically aimed a video_ts stuff. Remember that ImgBurn is a 'burning' tool, not a copying tool. It burns existing content that you have on your hdd (or anywhere else explorer can read from).

Morning boys

30mb blu?! Last time I checked the downloads were over 100mb in size!

Spend all that time doing the layerbreak stuff and then miss the basic ordering of VIDEO_TS files..... that would be pretty silly wouldn't it! It builds the images as 'fully compliant' as I know how to make them.

Yes, but it's the FULL path remember! So if you had C:\test\test1\test2\some document.txt and added that, with full pathnames on you'd have 'test' in the root folder, then 'test1' inside that, 'test2' inside that and then 'some document.txt'. With full pathnames off, you'd just get 'some document.txt' in the root. There's no way to just get 'test2' in the root and 'some document.txt' inside of it. ImgBurn has really been designed for building images where you've already got the structure of the disc correctly laid out on your hdd. There are less issues with being in the root Vs not being in the root if you just add a folder rather than a file from it.

It's magic. I updated a few bits but some sites didn't mirror it again. If you look at the main website you'll see the reason for one of the changes.

You'll need to recreate the image. So extract everything from it and then 'Build' a new one.

I guess you have an LG drive then? If you search this forum you'll find a little tool you can add to your startup folder.

The only place I'd add a 'Stay On Top' option is to the context menu on the program's top left icon (right click it). That's how I've implemented that option on the 'Queue' window. You could always use Copy + Paste instead of Drag + Drop if it's a pain switching windows or you don't use a high enough resolution to let you see multiple windows.

I'd go with firmware / media myself. The image format does look different to most (all?) PS2 stuff I've ever seen though.

AnyDVD can/will change whatever it needs to. That is in no way limited to just modifying a couple of IFO files! It's all down to the content of the media it's looking at and how you have it configured. A search of this forum would find you a perfect example (from only a few days ago) where it was modifying all of the IFO/BUP/VOB files on a freshly burnt disc, that then caused loads of 'Miscompare' errors during the verify stage.