LIGHTNING UK!

Your drive doesn't appear to like the cheapo media you're using. (Note that 16x is NOT a supported speed for your drive/firmware/media combo. You should try some other speed from the list of 'Supported' ones) You must have disabled verify on your previous burns. Without it, we can't tell if it was actually successful or not. Just because a 'Write' operation appears to go without a hitch does not mean the disc will actually be readable - that's the whole reason 'Verify' (after 'Write') is enabled by default.

The data is on there or verification wouldn't have worked. I assume you've tried removing the disc, rebooting and then reinserting the disc?

http://forum.imgburn.com/index.php?showtopic=6376

Normally you'd just right click the drive selection drop down box. There's an option to check for firmware updates on the menu that pops up. Don't worry about doing it for your drive though, 'Firmware HQ' doesn't have anything for your drive. Yes, the 2 failed discs are useless.

Your drive reported a 'Write Error' when trying to burn the discs. The problem is nothing to do with *what* you're trying to burn to the discs. Have a read: http://forum.imgburn.com/index.php?showtopic=8000

This has nothing to do with ImgBurn really does it (I'll move it to 'Chat') Try cleaning the drive with a cleaning disc - or just buy yourself a new one - they're cheap now.

ImgBurn has that diagnostic stuff too, it's part of the 'Auto Loader Control' feature. I've just sent you an email to get the ball rolling with testing what I've done so far.

Did you enable 'Test Mode' or something? If you post the log of that burn, we don't need to guess anything. (As per the pink box up the top )

The write error is covered here - http://forum.imgburn.com/index.php?showtopic=8000 Correct, you don't need the eSATA driver unless you're hot plugging externally. There's an updated firmware for your LiteOn drive - http://www.firmwarehq.com/Lite-On/iHOS104/files.html

Ok so do you have a similar pdf for the Microboards KDK-1000? Surely the 'unload' flow for that one would be more like the Vinpower Cube? (Because the output tray is directly below the drive and the 'A' command therefore wouldn't be suitable as it can't pickup and drop in one go)

If your drive is now on the gsata ports, it's probably connected to a JMicron controller. Use the drivers from here: ftp://driver.jmicron.com.tw/SATA_Controller/Windows/ Now that you've installed your OS, can't you put the drive back on the Intel controller? Please post a log of you burning and verifying one of these problem DL discs.

Any chance you could take a video of what I mentioned in my previous post? i.e. bring up hyperterminal and send the 'I' command to load a disc.... then capture what the robot / drive do on the video. Some sort of remote connection to a PC would help with testing but it's always better if I can see the robot at the same time. Hmm I wonder if a webcam pointing at the robot would do the trick... maybe! I think I've done enough to the program now to at least get us past the 'V' command at the start. Can I email you the new build? Should I use your forum email address?

As a very important side note, when you issue the 'I' command ('Load') on your generic devices, what *exactly* happens? I'm asking this because I have to control the drive (the drive tray) myself when working with the Vinpower device. So I have to ensure the tray is closed, then issue 'I' so it picks up a disc from the input bin, then eject the tray, then make it drop the disc, then close the tray again. To unload I have to open the tray, then pick the disc up, then close the tray, then drop the disc. It's not easy to get the command flow right when you don't have access to the device!

I'm not going to mess around with config files but I'm in the process of trying to tweak my existing code so that some 'generic' models may also be supported. I'll need to send you a new version to test out - as I don't have access to any 'generic' auto loaders.

The problem with those is that the robot doesn't return an 'X' before it returns the name of the device (having been sent 'V00'). ImgBurn expects any 'valid' response (i.e. from a real robot) to begin with 'E' or 'X'. (E = Error, X = Success) So your ImgBurn log from the Scrible device says 'Invalid Response.' (meaning no E or X was received). The ImgBurn log from the Amtren shows it being caught out because the robot identifies itself as an 'Elite-Micro V1.21..'. The 'E' in its name makes ImgBurn think there was an error. I don't know why Vinpower decided to tweak the response to the 'V00' command so it sent the E or X before sending the name of the device, but I'm glad they did!

Ok well this is no longer a 'bug'. The program is doing exactly what it should be doing - based on current settings. The file in the network location has the 'FILE_ATTRIBUTE_REPARSE_POINT' attribute flag set and that's why it's being skipped. As for *why* it has that flag set, I've no idea.

Technically, ImgBurn doesn't care if it's a Vinpower autoloader (it doesn't care about the name of the device), it just needs to support the exact command set that it's coded to use. ImgBurn sends V00 and C00 to the com port. Your log showed ImgBurn not getting any sort of response from the robot within the required time (1 second for those 2 commands). I guess it's the '00' bit that's messing up support for your generic robot. Try that in hyperterminal and see if the device gets hung up.

The book type command is failing on your system because of some issue with your drivers (they're blocking it). Make sure you install the latest chipset / controller drivers for your motherboard. If it's an Intel board you'll want to install the INF chipset drivers and the Rapid Storage Tech drivers.

http://forum.imgburn.com/index.php?showtopic=12200

You can't change the book type on BD media anyway, it only applies to DVD media (and then it's just DVD+ (plus) format DVDs).

You should try the remaining 'supported' write speeds. If they all fail too, you probably need to look at trying a new spindle of discs. Depending on the results with those, you might want to consider cleaning the drive with a cleaning disc. If it still doesnt work after that, get yourself a new drive - just a standard DVD burner would do - an Optiarc 726x or something. btw, service pack 1 is out for your OS now.

Can you please show me the log from you doing that? It tells you in there if files are being skipped for one reason or another. Also, which 'Input' method are you using? Standard or Advanced?

Ah well, you're out of luck then I guess.

If you look at that disc in Explorer (examine the contents), how does it compare to discs you've burnt in the past that actually work? How long did it take to burn the discs when you used Nero? What make/model DVD player do you have?

Please post the log of the burn you did that didn't work.