LIGHTNING UK!

Where exactly are you seeing this 'unsupported' message in powerdvd? You're not talking about the 'movie remixes' bit on the right that says 'This feature is not supported for the current disc format' are you? Obviously that just means that 'movie remixes' (whatever that is!) isn't supported for bluray. If that's not what you're talking about, I can't see why your PowerDVD has problems and mine doesn't. If you're not already using the verbatim BD-RE discs, give them a go because they work ok in my ps3.

There's nothing to 'crack' mate, it works fine I'd run ImgBurn's images through the Philips UDF verifier and tested them in PowerDVD and on the PS3 before the program was ever released with UDF 2.50+ support.

You did what?! You don't build a new image with the bin/cue inside it, the BIN file IS the ISO image. Just rename *.bin to *.iso. Personally I can't see that working though because technically the images are in the wrong format for using the 'ISO' extension. Still, I have no idea how this 'HD Loader' program wants / deals with its files so maybe it'll work.

So people just look for the 'Help' option regardless of which program it's in? I suppose if you don't know any better then ImgBurn could appear to just be part of DVD Flick.

Ah ok, I thought you might have been using a new one. I've done about 5 burns tonight testing this (on Verbatim BD-RE in my H20L) and they've worked in PowerDVD and the PS3 just fine. Maybe the laser just needs cleaning?! Is the system software on it up-to-date? Is your powerdvd up-to-date? That's not exactly 'bug free' software itself!

The program will rip to ISO when the sector format on the disc is Mode 1. When it's not, you get a BIN/CUE. The BIN is basically the same as ISO so maybe just renaming it would work?!

DVD-R DL discs are useless, don't waste your time / money on them. You want Verbatim DVD+R DL 2.4x (MKM-001-00 dye) and nothing else. For the locking issue, please read the FAQ. For the xbox stuff, please read an xbox forum... this isn't really the place for it.

Forget the whole 2hr / 6hr thing, it's rubbish. All you need to know is that you can fit 4.37GB of data on a DVD-R / DVD+R disc and ~8.5GB on a DVD-R DL / DVD+R DL disc. If you don't want to buy double layer (DL) discs for the stuff you're burning you will need to 'shrink' it. I'm not going to tell you how to do that because Google is more than capable.

You can't use PowerDVD to play from an image mounted in DT now, the latest DT had changes that prevent it from working.

It's probably easier to just have Nero and ImgBurn create an image (rather than burn to disc) and then compare them. You could also try reading a nero disc to an image and burning the image in ImgBurn. Obviously then we know the content would be identical (removing the differences in file systems from the equation).

Do the folder structures of the Nero / ImgBurn discs (or images) match? What about the file data itself? Make an image in each program, mount the images in DAEMON Tools (using 2 virtual drives) and then use a program to compare the files on both drives - something like Beyond Compare should do the trick

It'll only update things when the pointers in the IFO's are wrong. If you don't fix them then players won't like the disc.

BD drives perform automatic verification during the write, that's what slows it down. You have to enable 'FastWrite' in the settings so that ImgBurn will then try to tell the drive not to do that.

Ohhh you're running it via DVD Flick! That doesn't save your settings at all. (Their doing, not mine) If you want ImgBurn to work properly for when you're burning outside of DVD Flick you need to have a standalone one... i.e. install it normally having downloaded it from www.imgburn.com

Oh, sorry I see what you mean now. No, leaving it enabled won't harm anything.

The only way to do it is to forget the extras folder for a second, make an image, build par2 files based on the files inside the image (mount it in DAEMON Tools or something) and then add the extras folder. You might find you're better off just par2'ing the image file and burning the par2's from several discs on a disc of their own (and burning 2 copies?!).

No, another drive in the system shouldn't cause this error. I've got 6 in mine and I've never had it. How many times have you actually seen the 'mismatch' error? Maybe it was just a one off anyway? Debug mode simply logs all the I/O stuff. It doesn't alter what's being sent to the drive so you don't need it enabled in order to get a working burn! All it does is mess up the log and make it hard to read - unless you (well, I) actually require the raw I/O command info and responses. As with any logging, the more you do, the slower the program runs. So basically, don't enable it again unless I ask for something the requires it!

lol me too! I'm sure I'll get it running properly one of these days... if I had Vista Ultimate on I might make more use of it via the Media Centre thingy.

ImgBurn is more about burning than reading. You can use ImgBurn's CLI and some other app to control the unit for the read part, ImgBurn will only use the currently selected slot. For burning (from the Write Queue), ImgBurn will automatically burn individual images to media in different slots.

Don't worry about the errors, a lot of them are expected... but you only know that when you understand them - and that's my job really, not yours Worry about stuff you see (when debug mode is disabled), not stuff you don't see.

Sorry but I've seen it before where people have already come to their conclusions. Being blunt about it just saves us both time. ImgBurn defaults to using the SAO write type, Nero may be using Incremental. Your drive should write perfectly well using either one but sometimes they just don't. That's nothing to do with the software, it's a hardware thing. Select the other write type and continue on your merry way.

It's not the end of the world anyway, you can just tell it not to capture graph data. That is of course just a workaround and not a fix for what is obviously a bigger problem.

ImgBurn has to correct certain pointers when it burns to disc due to the layout and positioning of the files. The layout isn't the same when you look at the files as files... but then DVD players don't do that, they go by the pointers.

Whatever your time doing QA has taught you, software cannot introduce errors during the burn - well, not with the type of burning going on here anyway. If the drive makes a crappy burn, it's the drive/media/firmware at fault - end of story. It would (and do) say exactly the same thing if my program was the one that worked and something else didn't.

Read the FAQ, it tells you what to do when that happens.