LIGHTNING UK!

The concept of layer breaks died out with DVD. Whilst layers phyiscally exist on the BD disc, you just ignore them and treat the disc a larger single layer one.

2.5.6.0 -> 2.5.7.0 Language_File_2.5.7.0_Differences_Report.zip Language_File_2.5.7.0_Differences_UnifiedDiff.zip

Avast's 'Sandbox' again? http://forum.imgburn.com/index.php?showtopic=19669

Oh well, it was worth a shot. We'll just have to wait until I hear back from Primera.

I've got one of their Nimbie USB units. They're the only ones supported by ImgBurn AFAIK. Yes, they work with ImgBurn's Batch Read mode. I wouldn't worry about that right now though, your robot should work just fine. Did you try disabling the other CD/DVD drive in your machine via Device Manager like I said? I'm wondering if their DLL isn't just getting confused about the drives in the machine Vs drives in the duplicator.

If it doesn't support the commands then you're out of luck. In any case, the booktype isn't important for playback in that device.

Try reading the disc in your other drive. Whichever one it's in now just can't read it properly.

Ah, that's my fault. IMG+CCD images seem to require pregap data in the data file. The traditional BIN+CUE ones don't as it's generated by the program. I've just changed my code so that the pregaps are included when outputting in CCD compliant image file.

Ah yes, sorry, I misread the drive's identifier for something from an old DVD drive. All of LiteOn's new BD drives (including the 2 I own) have iHBSxxx / iHESxxx type names. You should be good to go then

Yes you will, with Read mode's 'Batch' option. I've contacted Primera's developer support asking them in what situation the PTRobot_EnumDrives function would/could return 503. I'll let you know if/when I hear back from them. In the mean time you might like to try disabling the other drive (DVR-106D) you have in your PC via Device Manager and see if that makes it work. It looks like your bravo unit connects to the PC via Firewire... is that correct? Does it just have a single connection to the PC?

Try the Bravo version 1.25 (PC) one instead then please. You may need to ensure the printer drivers are installed correctly first - http://www.primera.com/driverdownload.php

ImgBurn's device enumeration method has nothing to do with the problem. Ideally you'd install SP3 so that the 'Device Interface' option can work though. It's a Primera DLL function that's failing and it's failing with an error code (503 - 'PTROBOT_INVALID_DRIVE') the SDK documentation doesn't list as one it'll return! Can you try the 1.29/1.43 firmware update that's available for your Bravo II please. http://www.primera.com/firmware_upgrade.html

When did you take them from it though... today or some time in the past? I update the DLLs when I notice primera have updated them. So put ImgBurn v2.5.6.0 on (the current version) and update to the new dlls. Then try again and post a new log. Oh and yes, SP2 will work fine. I was simply pointing it out as service packs are released to add features and fix general problems / security issues.

The bravo II is exactly what I have and it worked fine last time I tried it. Why aren't you using the current set of DLL files... or are you and it's just the wrong SDK version being returned? Make sure you're using the current version of ImgBurn too. Oh and of course SP3 for XP has been out for years now.

cdspeed comes as part of the Nero suite. You can find it on their site or on various generic software news/download sites. You don't need both programs though, ODC will do. Notice I did state you need a LiteOn Blu-ray drive to perform the quality tests though, not all drives are capable of it.

No, it just means that's what they're designed for. You burn at whatever speed your drive does the best job at. That varies by drive/firmware/media - hence the reason for burning a disc at each 'supported' speed and then checking the quality via the likes of opti drive control. cdspeed and opti drive control are both program names and the programs were made by the same person. Opti drive control is just the newer of the two. You got the I/O error because your drive didn't like something about the disc. The drive reports the error, ImgBurn simply displays it to the user.

Post a log of you burning + verifying a disc that then doesn't play. If just the one player is having a problem with one batch of discs then it seems to me the problem is between the two of them. Maybe another spindle of discs wouldn't have the same problem or perhaps cleaning the player would enable it to read the discs.

I've pretty much covered everything on this subject here - http://forum.imgburn.com/index.php?showtopic=19743

The raw BIN file doesn't contain enough info to let Virtual Clone Drive know the audio track exist. You'd need to load the CUE file - which it doesn't support. You can make ImgBurn output a CCD file (in the Settings on the Read tab), you should be able to load that in VCD.

Performing a (successful) verify operation proves the disc is 100% readable in the drive that just burnt it. My advice would be to ignore your friends and let ImgBurn do it's *full* job. If you then want to double check the disc by trying it on your intended playback device then so be it. The 'VERBAT-IMd-000' dye/mid is rated for 4x burning but the only way you'd know how well your drive can burn them at that speed (or any speed) is to do some disc quality scans - for which you'd need a LiteOn blu-ray drive and something like Opti Drive Control / CDSpeed. If you're getting bad burns at 2x and 4x, you might want to start looking at getting some different discs (perhaps the 2x or 6x versions of the Verbatims) or doing something with your drive (cleaning it or replacing it).

At this point you should probably try cleaning the drive with a cleaning disc before giving it another go. If it fails again, bin the drive and get yourself a new one.

They're the three commands you can send to a drive in order to make it finalise a disc. If they don't work then the drive can't close the disc. Now you've done all 3, please go into Write mode and copy + paste all the disc info from the box on the right when that disc is in the drive.

How many have failed like that? Can you try with the 'Perform OPC Before Write' option disable (as is the default setting) ? If the program always lists the following, your drive seems to be having a problem initialising the discs. The size is way off what it should be.

I linked you to the firmware updates. They're what you're supposed to have tried installing/updating and not lightscribe software - which has nothing to do with anything. Like I said before, you drive is too old to support the 'RITEK-S04-66' MID/dye discs you're trying to use. It has nothing to do with what you're trying to burn onto them.

It's a combination of the two Your drive is too old to support the 'RITEK-S04-66' media code. Maybe a firmware update would fix that? http://www.firmwarehq.com/Lite-On/DH-16AYH/files.html