LIGHTNING UK!

What format is your movie in? If it's not already in DVD Video format (i.e. a VIDEO_TS folder containing IFO/VOB/BUP files), you'll need to convert it so that it is. To do that you can use something like DVD Flick or ConvertXtoDVD.

I'm pretty sure it was done by humans but if you think you can do a better job, be my guest.

Update ImgBurn. Update Windows. Update the firmware on your drive. Reset ImgBurn's settings back to default values. Start using 'Verify'.

Is the drive on the ICH9R controller? Is the controller in ATA mode or do you have it an AHCI/RAID mode? ATA mode is a lot more 'compatible' with optical drives. If it's in AHCI/RAID, make sure you've loaded the latest drivers 'Matrix' drivers from Intel.com You should also clear out any buggy filter drivers using the feature in the Tools menu.

One you've got the image in the queue you can just right click that item in the list and select 'Queue Again'. There's even a keyboard shortcut for it! Then select all the images and click the 'share selected between drives' button.

Looks like you've already had a failed burn on that media. Post the log when a brand new one fails (if it does).

You don't have master/slave with SATA, everything gets its own dedicated channel. Don't worry about how windows displays things

I'm not really sure what you're saying but the queue only works for images. You can queue stuff you'd normally burn in Build mode. Well, all you could do is build the ISO's and then queue them up. If you need to burn an ISO file twice via the queue to two different drives, obvioulsy you don't need 2 copies of that file, you just add the same one to the queue again but tell it to use a different drive for burning.

nope, the 'copies' for a given queued item will only go to one drive. Write a batch file if that's easier for you.

You got an error there because you were burning to a disc that had already been partly written to. Notice the size of the disc is not what it should be: Now read this... http://forum.imgburn.com/index.php?showtopic=8000

All that would make a lot more sense if you just posted a copy of the burn log.

You need to queue the image again and point it at the second drive. 'Copies' cannot be shared between drives, only actual queued images.

So when you click the 'Browse for a file' button in the 'Source' box when you're in 'Write' mode the standard windows dialog box doesn't actually open? And when you right click an ISO and select 'Burn using ImgBurn' the program loads up ok (in Write mode) but no file is selected in the 'Source' box? Does anything get logged in the 'Log' window? What other software have you installed/updated in the past few days? Thing that work don't tend to break until something breaks them

Ok, all fixed. The error wasn't specific to PDI files but they're one of the only image types that would actually care about it. Thanks for reporting it.

Oh sorry, I thought there was a little file and then some bigger ones! (the bigger ones would be 1GB) What can I use to create the exact same type of PDI you've got there? (program name, version etc)

The PS3 plays them too. How about the sony 350 model?

It'll just split the data straight down the middle.

If anything is going wrong I'd say that K: is. ImgBurn allocates the full size of the file before it starts writing to it - and explorer will show that in the file properties. So if your drive suddenly stops writing to the file (but doesn't report an error), everything after that last successful write would just be zeroes.

This is nothing to do with ImgBurn, your drive controls the speed.

Please email me the tiny pdi file, they probably changed it a bit and now it's not detected as a pdi file. The address is in the about box.

I'm not aware of any booktype commands for BD media. The drives need to support it before a program can make it happen.

Normally the drive that's burning would be 'locked' so no other program (or ImgBurn itself) will be able to access it - hence opening another instance of ImgBurn isn't a problem. The log from the failed burn might shed some more light as to why it failed but it's not a program bug.

That graph doesn't match the burn log.

Version 1.3.0.0.... are you kidding me?! LOL

Nope never and I've never heard of anyone else saying such a thing. Find me a log of one that didn't work and maybe there will be a clue in it.