LIGHTNING UK!

lol can't you read Japanese?! I didn't check the exe personally so I didn't see where it linked to etc. Normally it's just a case of selecting the right drive and clicking 'start' though - so even in foreign languages, it's quite a straight forward process. Still, so long as you're on JL13 now, that's all that matters. Disc wise you want to be looking at MCC or TY (Tayio Yuden) dyes. No need to pay massive attention to the 'brand' name, it's the dye that's important. Oh and yes, the log seems to show your drive having trouble burning to the media. If your firmware is up-to-date, the only other thing you can do is buy better (supported) discs.

Can't say as I've ever heard of / seen that media before! ?1 for 4 isn't really all that cheap, you can get decent discs for that price from www.svp.co.uk Try the newer JL13 firmware available from here: http://forum.rpc1.org/dl_firmware.php?download_id=2126

If the layerbreak bit plays ok then you've nothing to worry about. Your player probably just isn't fussy about them - as is the case with most players now. Keep an eye out for v2.1 as it will/should fix this issue.

You'll only be missing a few sectors at the end davidw89. You may need to close the disc manually but it should still play ok.

It makes sure there's at least 32k worth of data/nothingness between the IFO and the BUP file. That's supposed to be enough data to ensure they're not phyiscally next to eachother on the disc. i.e. one file is round one side of the disc, the other file is on the other side. Click Tools -> Options. Switch to the 'Build' tab. The 32k IFO/BUP padding option is down the bottom on that screen.

Do you still have the files you built the ISO from? If so, are they DVD Video files? i.e. IFO/BUP/VOB ones. During the initial build did you get a 'Create Layer Break Position' dialog box come up? If you did, can you please get it up on the screen again and take a screenshot of the window - perhaps with the same option selected that you selected when you actually built the image. Basically the MDS file is wrong and that probably means the padding for the layer break is wrong too. (Since v2 was released I've fixed a couple of bugs to do with 32k padding on certain sets of dvd video files. One of these bugs could indeed cause this padding problem.)

The option is in the settings on the 'Build' tab. Unless you just so happen to scratch the DVD so that it cannot read one of 'IFO' files, you'll never have a need for 32k padding. It's a 'nice' option, not a 'vital' one.

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.