LIGHTNING UK!

Your drive is reporting that disc as still being empty - obviously that's not a good sign if it's meant to have just finished burning it! It could be a drive problem (dust/dirt on the laser or a fault) or a simple case of it not liking the 'Ritek' CDs you're using. Try another disc and see if it does the same again.

At a guess, it means your drive did a bad job of burning the disc. Load the program up again, switch to Read mode and copy + paste all the disc info from the box on the right when that disc is in the drive.

That would only work on discs that support direct overwrite (DVD+RW, BD-RE). Other ones would block a write operation to an out of sequence LBA. So basically, no there isn't and there won't ever be That's where defect management would come in on BD media - as mentioned in your other thread.

Update the firmware on your drive. http://www.firmwarehq.com/Pioneer/BDR-206D/files.html Try the other supported speeds. RITEK don't exactly make the best discs but it was probably just a one off.

There's really only 3 things you *can* do. 1. Clean the drive and hope for the best. 2. Buy some other discs - Verbatim or Taiyo Yuden (Victor JVC) 3. Buy another drive.

Correct.

When it's enabled, the drive verifies as it burns - this basically halves the burn speed. Any failed sectors are then remapped into the 'spare areas' (reserved) part of the disc.

You've burnt 500 'MBIPG101-R05-01' at 6x (which according to the drive isn't even a supported speed - so it's probably 4x or 8x) ? Maybe you got a bad spindle or your drive is dirty - even the latest firmware dates back to 2007 so it's quite possible.

Sorry, were you in contact with 'Frank' before or after reading my post? I just want to know if they're going to fix the 'Medium Not Present' bug really I believe their forum has the latest versions. I've never seen a BD-ROM with physical errors on it so it's unlikely your problem will get 'fixed' by updating software. What you need is a new disc or a different drive with better reading capabilities.

Which version of AnyDVD are you running? The 'Medium Not Present' error being returned by the drive (but in actual fact, AnyDVD) looks like a bug to me. You should report it to them - assuming you're on the very latest version (including betas - v7.0.3.2 as of this moment). It's probably reporting that (incorrect) error because the disc is unreadable (scratched / dirty / faulty).

Your drive reported a 'Write Error' when trying to burn to the disc. You're using low quality DVD+R DL media, read this - http://forum.imgburn.com/index.php?showtopic=8000 Why are you even using DL discs in the first place? The program did tell you that your image would fit on a regular SL disc just fine (see below). That doesn't look right. Don't try and reuse a disc that has failed previously, you're just wasting your time.

That isn't a disc to disc copy. Build mode makes a new file system based on the contents of the 'Source' box. Reading to an image and then Writing preserves the original file system. If you really must do that workaround method of disc-to-disc (it's only saving you a few mins and in fact, you've lost them again by asking this question!), you'll have to pick one of the layer break positions from the list. Use the stars to help you. The double layer DVD Video guides in the Guides forum may also help.

Artificially slowing down the reading/writing to and from your hdd isn't going to make the final ISO any different - it's digital after all Can you try playing the ISO (via a virtual drive) using some proper (licensed) Blu-ray software on the PC to see if it has the same problem? (PowerDVD / TMT etc)

Your problem is nothing to do with the speed at which the ISO gets built. Compare the files in the ISO to the ones in the folders on your hdd and you'll see they're identical. It sounds more like an issue with the media player.

I've been told you have an original Bravo unit that was manufacturered in August 2003. I understand this model hasn't ever been supported by PTRobot (going by a quick look through the software archive) so I'm afraid you're out of luck. There's a version of PTBurn (from 2005) that may work with it but that would be via totally different software (whatever you used before I guess). I must have got lucky when I picked my unit up from ebay - I certainly didn't know anything about certain models being unsupported at the time and just went for one that was a great price!

The 'Sony' name stamped on the discs doesn't mean anything, you're using 'RITEK-F16-01' dye/MID discs. Sony could chop and change the dye/MID they use whenever they like - so a spindle of discs you buy today might not be the same as the one you got last week. Yes, your drive might benefit from being cleaned. It would probably also perform a little better on some quality discs - Verbatim or Taiyo Yuden (Victor JVC). That said, slimline drives aren't my favourite.

To be fair, they did answer the question about the error code, I just didn't mention it to you - and that's my fault. At which point I asked you to provide them (the debug/trace ones). As for the crashing, if there was ever something concrete that would enable me to reproduce the crash, I'd do it and fix it asap. It's very hard to fix something I can't reproduce.... I've tried and failed several times. If you aren't already doing so, make sure you tell the program to send me the crash dump.

As it happens, I had a reply from them last night but hadn't had a chance to relay it back to you... They said... I will reply to them confirming it's a firewire connection to the drive and USB to the robot (as I already asked you that question) and perhaps link them to this thread in case they're interested. As for their other questions, perhaps you could answer those when you get a minute. Thanks.

That's the problem, your drive is returning incorrect info - due to a firmware bug. You might be able to find a firmware update to fix the issue by visiting the website of whoever manufactured your laptop.

Please look at that disc using IsoBuster. It'll show you the two file systems on the disc and show you the names recorded in each one. I'd like to think you'll see that the UDF side of things is correct and has spaces in the names where they were originally. So then what we need to figure out is why Windows is only loading the ISO9660 file system and not the 'better' UDF one. There is no setting in ImgBurn that can make it convert spaces to underscores for all file systems. It only ever does it for the ISO9660 one - as per the specs.

You can use whatever the drive reports is available. The 122* figure sounds like the typical size of a BD-R disc. The 118* figure sounds like the typical size of a BD-R disc that's been formatted with spare areas enabled, thus enabling the drives defect management.

Can you do a full erase on the disc? Right click the drive selection drop down box and you'll find 'Erase' on there. or click the Erase button in the Destination box when in Write mode.

That sounds normal for an ISO9660 filesystem. What are you trying to use the disc in that only supports ISO9660 rather than Joliet or UDF (which do allow spaces) ?

When you're in Read mode, copy + paste the disc info from the box on the right please. Oh and make sure you're using the current version of ImgBurn first please - v2.5.7.0

You wouldn't get that error if you're just trying to change the 'Advanced Settings', it's totally unrelated. You need to bring up the 'Change Advanced Settings' window and that can be done in numerous ways.... 1. Right click the drive drop down selection box and pick the option from the context menu. 2. Once you're in a mode where a drive is active (i.e. anything other than Ez-Mode Picker), click Tools -> Drive and find the option on that menu. 3. Press the 'Change Advanced Settings' button down the bottom right of the main window when in Write mode (plus some of the others).