LIGHTNING UK!

Check the source ISO again. It looks small to me - only ~2.5GB rather than the ~4.3GB I'd expect from a 'shrunk' disc.

Yes, that's the general message behind the thread I linked you to.

Those discs are 'RICOHJPN-D01-67', not 'MKM-003-00'. Again, please refer to the post I linked you to earlier. The 'Invalid Address For Write' error isn't important, you're only getting that after a 'retry'. The initial error is the important one.

Yes, it defaults to ISO9660 + UDF (1.02) because it's the most compatible and that's what a typical DVD Video disc uses - I guess that was its primary function at the time. XP can't read (understand) UDF 2.50 or 2.60 without a 3rd party driver. The extra bits in 2.50 and 2.60 only creates backups (mirror copies) of the data that UDF readers use to figure out which files are on the disc and where they are (various file system descriptors). The main copy is usually before all of the file data (i.e. at the start of the disc) and the mirror copy is then located after all of the file data (i.e. at the end of the disc). The actual file data is only ever stored once - so once that's damaged, it's damaged. I'm sure there will be a comparison chart between the various versions of UDF on the web somewhere. Have a search and see if you can find such a thing if you want more info.

Show us a log of you burning decent Verbatim MKM-003-00 discs on your internal drive please.

If that's the drive you just purchased, take it back and get a 'known' (decent brand and half height, NOT slimline) drive instead. Read this... http://forum.imgburn.com/index.php?showtopic=8000

You can access the saved logs via the help menu.

You can use what you like. 1.02 is the most compatible but 2.50+ provide extra protection against file system corruption (and therefore data loss) as a result of scratches etc.

Sorry, I can't answer that question. You'd have to burn a few discs at each speed and then scan them to check the quality. It really depends on the drive and firmware as to which speed gives the best results.

You can burn whatever fits on the disc. Only certain players will support playing raw files like that though, yours may require a proper BD Video structure - in which case you'll need to author your 10 (or any amount of raw video files) into the proper structure and make yourself a menu. You can use something like MultiAVCHD for that. You can't do multisession with ImgBurn and even if you could, the above still applies. Just adding another raw m2ts file to the disc may not work if your player doesn't play files / discs like that.

You didn't verify the burn but I'm sure it burnt everything you gave it. As such I think the problem probably lies with your source image.

Make an ISO from those same source files, mount it in a virtual drive (Virtual CloneDrive etc) and then play it via a proper BD video software player (PowerDVD etc). If that works, it should also work when burnt to disc - in that same software player anyway. Playing the raw files isn't the same as playing the disc as a proper BD video disc. A straight copy of an unprotected disc to an ISO and then burning back to a new blank should work fine though... there no real room for error in that.

You're using your F: drive as the source and destination... that's not possible. Use 'Read' mode to make your image from the F: drive and then 'Write' mode to write the image back to your F: drive.

Ah, that one gave you a proper 'Write Error'. (refer back to 'post #2') I assume you have no spare SATA ports on your Intel controller and that's why you've connected it to a Silicon Image chipset based card?

There's no way for me to say for sure either way without trying other hardware/media to narrow down where the issue is. The error should be coming from the drive itself. What controller is the drive attatched to? Right click the drive selection box and click 'Family Tree'. Close the prompt that comes up and then copy + paste everything from the log window please.

It looks like your drive is having trouble burning to the discs you're using. There's nothing ImgBurn can do to prevent that from happening, it's hardware having a problem with hardware. It's up to you if you want to try some different discs or try a different drive. Crossflashing your ASUS to the latest LiteOn firmware might give you better results. Check the MyCE forums for info on that, I'm sure it's covered somewhere.

No, the speed ramps up over the entire disc. It'll only reach max speed right at the end.

Drag and drop from Explorer or switch the 'Input' mode to 'Advanced' in the menu at the top of the main window.

Why can't you just use the 'Create CUE File' feature to add your music tracks (which you appear to have managed already), then add your 2nd session (disc image with a green '+') and put that 'OneCrypt.bin' file in it as a track? You can then load that CUE in 'Write' mode and burn it. I have no idea if the disc will magically become copy protected... I doubt it but then I did hear there's a certain sequence of bytes you can burn to CD that'll give you an unreadable sector.

How have you tried to do it so far and what hasn't worked about it? The 'Create CUE File' feature is pretty simple to use.

What you've done there is rebuilt the file system based on the files that were on your source disc (i.e. you used Build mode). That's not the same as making a sector by sector copy of the disc (i.e. using Read mode). It will have corrected a few values in the IFO / BUP files so they were correct based on the new layout of files within the image (sector offsets etc).

Almost everything I install these days offers a totally different program too, it's the way of the world. Untick a box or two and you've opted out. The greyed out 'custom' box has been mentioned several times. It is just grey though and not actually disabled (i.e. you *can* still click it). I've told OpenCandy that people don't like it and I'm lead to believe they're in the process of getting rid of them or at least offering us devs a chance to opt out of using them.

and that drive can't overburn on the good discs either. http://forum.imgburn.com/index.php?act=findpost&pid=145573

There is no way to do that I'm afraid.

People that have a reason to enable any of the auto loader options wouldn't normally get confused by an empty / disabled device box (baring in mind everything else is disabled too) when the status bar/log window clearly says that a device scan is in progress.