LIGHTNING UK!

What has this got to do with anything?

Try some of the things mentioned here - http://forum.imgburn.com/index.php?showtopic=8000

Right, get the drive off the Marvell controller and onto a proper Intel port.

Not really, no. Wii discs are copy protected. If a drive can't just read the disc normally (like any other disc), it's not going to work in ImgBurn.

The only reason NT4 worked is because the program used (only uses) drive letters to open drives under that OS. Newer OS's had the (better) option of using device classes or interfaces. It works best under Wine when using ASPI. SPTI (even via drive letters) would often result in no drives being detected. I don't know why but their handling of SPTI stuff is pretty awful. It's a shame These are the only ASPI related lines I see in Ubuntu 11.10 (x86) with Wine 1.3.36. Have you already tried to remove Wine and all its settings, and then reinstall? I don't know if a normal uninstall (or whatever it's known as under Linux!) would remove them or not? If you can wipe out the file it uses for the Windows registry, maybe it would fix the problem when it creates a new one? Good luck with it! edit: Seems you've fixed the problem In my experience, the SPTI device detection was also hit and miss depending on if a (blank) disc was inserted when the program was loaded. That's why I opt for ASPI now as it doesn't seem to care. Technically, SPTI is superior as it supports locking (exclusive access) and other bits like that.

This is more of a Linux / Wine question than anything to do with ImgBurn. Wine has to present the drives via ASPI and I guess translate I/O into the native Linux format. For some reason, that doesn't seem to be working properly on your setup. I personally don't have the knowledge to help you with that. Do you get anything useful in the Wine semi-debug-like log as ImgBurn starts (if loaded from a terminal window) ?

Have you tried cleaning the drive? How about trying some Verbatim DVD-R discs instead of the DVD+R ones?

It's not something we can explain, it's just something the drive is doing. You'd have to ask the people that wrote the firmware.

Technically, it's looping, not hanging It's not that it can't physically read something from the disc (so read errors aren't and issue), it's that it's looking for a certain bit of subchannel info that the drive is reluctant to provide. I'm afraid there's little I can do about it when I don't have a drive+disk to reproduce the issue on. I've read all the disc I have easily at hand in one of my Samsung drives (they seem to be the worst for this) and they all worked fine. When I'm next in the mood, I'll extend my testing to a bunch more discs and see if I can find one that has the same issue. In the mean time, use Exact Audio Copy to get a decent image of the disc (with correct gaps etc - I'm not sure what, if anything, ultraiso does with them).

Try the other supported write speeds. Try cleaning the drive with a cleaning disc. Your version of ImgBurn is out of date. You should install Windows 7 Service Pack 1.

Assuming you provided a valid BD video structure (an authoring job), correct/incorrect playback is nothing to do with burning or ImgBurn. ImgBurn just burns as-is. Do you have the latest TMT3 patches/updates installed? Have you tried it with a trial/demo of TMT5? Maybe it was an issue in TMT3.

If it's failing to burn everything, it's probably had it. As you say you don't have a cleaning disc, try the manual method (carefully!) with one of those cotton bud things dipped in white spirit or something. You should update to latest version of the program.

Yup, give it a go. Cleaning the drive may help... as might buying some new discs.

It improves it by creating a disc that actually works properly. You can't magically turn a multisession disc into a single session disc by pretending those other sessions don't eixst - which is what it did before. All you end up with when you do that is a new disc where only the data from the first session is accessible. Stuff in later sessions doesn't exist at all.

Does this firmware update work on your drive? Try it. http://www.firmwarehq.com/HP/dvd640b/files.html The discs you're using are old, have you had them sitting around for a few years?

Reflashing resets the eeprom to default values. So it will have wiped out learnt media (opc stuff) and reset the settings (FHT/OHT/OS/SB). They worked ok for me but only for the first burn. After that my results went downhill again. You just have to be prepared to waste a spindle finding settings that work. As the drives are cheap, you might consider it an option just to get another one. Compare the two and use the best one.

Your drive can read BD discs, it can't write them.

The settings I used for each attempt can be seen in the logs. The post you should be looking at is this one - http://forum.imgburn.com/index.php?showtopic=18871&view=findpost&p=136519 If it doesn't automatically jump to the right place, it's post #20 in the thread. I started with default settings, had 3 total failures, cleared OPC history and then got a decent 4th. After that things got worse again and I started to mess with the settings.

It's not worth reflashing, no. This is a controller/driver issue.

If it burns without error, it overburnt. It'll be fine, just try it.

1 sector = 1 frame = 1/75th of a second. So that's all you'd lose if it fails at the end - but it might overburn anyway.

Yes, optical drives don't like 3rd party controllers very much. Stick with the real chipset ports where possible.

Does your board have native 6gbps or is that 6gbps controller a Marvell or something? Right click the drive selection drop down box and click 'Family Tree'. Close the prompt and then copy + paste the family tree info from the log window.

Isn't that just the drive spinning a badly balanced disc? Regarding the KProbe results, it's so much easier to look at the graph rather than read/interpret numbers. If you only provide one or the other, please provide the screenshot/graph. I did say later burns might play up again. It took me 7 attempts from a spindle of 20 to get settings that produced consistent burns.

Do you have the drive on a Via card by any chance? If so, get it off it... they don't work well together. Put the drive on your motherboard chipset's SATA controller. Oh and don't write in CAPS.