LIGHTNING UK!

When the 'Create MDS' option is set to 'Auto', I'm pretty sure it shouldn't be creating an MDS file for single layer media... unless you are putting the file on a FAT32 drive or something and it's having to split the image? The MDS has nothing to do with the type of disc (or rather the content of it) and it certainly wouldn't make any difference to it auto playing or not.

As usual, you can download it and view the changelog by visiting the main website. http://www.imgburn.com/ Special 'Thanks' to all the beta testers, translators and donors!

why don't you turn off auto calculate? It's because you've turned that on that it's prompting every time. Calculate when you've added all your files (which couldn't you just do in 1 go anyway via drag+drop?)... or just change the file system to something that includes joliet. Why are you (only) using UDF anyway? btw, 2.4.4.0 has an option to auto answer that prompt. Look out for it when it gets released (later tonight)

First post updated for v1.0.0.7 base file and new differences report. Sorry for making you do some of the options on the Build mode tab in the settings again (I messed something up without meaning to and it broke it!), hopefully you can copy + paste what you translated it to last time.

Verify only tells you that it can be read in that drive, not that it'll work in anything else. Every drive has different capabilities when it comes to reading and a computer BD drive is more likely to read BDRE media than a PS3 which is probably geared more towards reading pressed BDROM's. The whole thing about leaving the spare areas enabled is that if a sector on the disc is found to be a bit dodgy, it can be mapped out of use. When you use the entire disc (no spare areas), that can't happen and your bad sector becomes 'available' for use again, even if it's not readable/writable.

That's so not gonna work. Why not Google for a proper method?

Ah, the % will be present when ImgBurn is writing zeroes to the sectors.... but not when the drive is actually performing the format/erase and certifying the media (this is an internal process). The whole thing will be much clearer in 2.4.4.0 The thing with 2.4.3.0 is that when immediate I/O is disabled and the format command fails, you don't know about it. By default 2.4.3.0 will attempt to format with full certification first, if that fails then it'll attempt to do it quickly without any certification. So what might actually be happening for you is that the format command fails will full certification (as it does when immediate i/o is enabled - and this is what SHOULD be happening or there's a bug in the drives firmware!) and then the quick one succeeds - thus you end up with an erase operation that seems to have completed without error.

Did you try that driver? Did you try it with just one drive on the cable? Did you try it with a totally different cable? Card wise, just ebay 'Sil0680'. (as in 'Silicon Image 680')

Ok so basically you've got your drives on a Marvell controller - and they are awful for optical drives. I assume you've tried the latest marvell driver? http://dlsvr.asus.com/pub/ASUS/misc/sata/M...060_XPVista.zip Otherwise you have little choice but to get a PCI card for the drives (make sure it's got a Silicon Image 680 chipset) or buy some SATA ones.

Do you know what motherboard you have?

What controller is the drive on? Do your drives share the same cable? If they do, have you tried it with just 1 drive? Have you tried a new cable? You want as short a cable as possible - and make sure it's a decent 80 wire one.

OMG, are you kidding me?! Just look at any online store and find some discs made by Verbatim or Taiyo Yuden. It's not hard, my 7 year old niece could do it. I'm beginning to think you're just taking the piss and winding us (mainly me) up.

My previous reply was aimed at 'Roger_Sun', not you. Have you (JakasE) got some Verbatim / Taiyo Yuden media yet? If not, do so and then get back to us. If you reply with anything other than a log where your drive is attempting to burn Verbatim/Taiyo Yuden media I'm doing to delete this thread and ban you from the forum.

You can't do this. You have to put 1 image on 1 disc, that's the way images work. You'll have to extract the contents of both images and reauthor / combine them - which is nothing to do with ImgBurn. So basically, it's probably not worth your time or effort.... live with the few extra discs!

Maybe you got a faulty drive? You can see here that Cynthia's DVR-216D burnt them just fine - http://forum.imgburn.com/index.php?showtopic=9541&st=0 and I know first hand that my DVR-216 has no problems with the 2.4x MKM-001-00 Verbs.

Leave your log window open when using the program and copy + paste from it directly once you've burnt a disc which comes up with this error. Even when using the log file, it's just plain text and so it shouldn't be hard to select the appropriate session using the mouse / keyboard and then just copy + paste that bit... it's just basic copy + paste skills.

To get a screenshot, hold down the ALT key and press the Print Screen one. Then 'paste' it into Paint or something similar.

I've already said I'll probably change to using Vista icons at some point and I don't really need help with that. Personally I wouldn't have gone for the blue laser but the rest looks about right (because it's the same as we have now!).

You should be using Verbatim DVD+R DL media, not Verbatim DVD-R DL.

It'll probably stop playing.

Just FMI (for my information!), can you post the disc info from that newly formatted BD25 please?

I'm not sure there are any layman's terms. You either know what you're doing or you learn what you're doing... there is no simple answer. Post a screenshot of the options you're presented with.

So a 'normal' account in vista doesn't work but an admin one does? (I assume UAC is enabled but it never prompts?) That doesn't really make sense. Running as admin is an awful way to do things really, you can''t then D+D into the program.

Make sure you tick that box again, it's there for debugging purposes really and the erase command is not the only one to make use of it. Not using immediate I/O means it'll hog the bus and no status (i.e. % complete) can be provided. Also note that unless 4 different attempts to format the disc fail, the 'erase' process in ImgBurn wouldn't display an error when that Immediate I/O setting is disabled. When enabled, you at least know there was a problem somewhere along the line even if a later command succeeds. I've changed how 2.4.4.0 does things so that if it fails, you'll know about it - and without any special hidden retries on the program's part.

Read the ReadMe.txt file.