LIGHTNING UK!

You can't booktype DVD-R discs.

Your drive did a bad job of burning the discs at 4x, try the other supported write speeds. Try with some Verbatim / Taiyo Yuden media - they're better quality discs. You can't write over the top of an already burnt DVD-R disc, that's why the write button isn't enabled. (look at the message in the status bar at the bottom of the main window) Windows 7 'Service Pack 1' has been out for ages now, you should install it.

That box on the right scrolls - copy + paste the whole thing please. It looks like your discs may be unsupported by the drive though. http://forum.imgburn.com/index.php?showtopic=8000

No. Corrupt files are only corrupt to the playback device. The burner doesn't know or care - data is data. If your drive failed to burn, it's probably media / write speed / firmware / drive related. Sometimes a drive will burn using one write type (e.g. Incremental) but not another one (e.g. DAO/SAO - ImgBurn's default setting). That's a drive/firmware/media issue too - it should be able to burn with both equally well. It's important you Verify your burns to know if the disk is actually readable (to the burner at least). This may help you find old logs - http://forum.imgburn.com/index.php?showtopic=14632

I'd go with it being a hardware issue then (as was always my first guess).

Yes, refer to post #3

When the command is first sent (status changes to 'setting l0 data zone capacity'), do you hear the drive making noises? If it was me, I'd try (yet) another drive. Or try your current one in another machine with the same media to see if it does the same thing. This issue is nothing to do with ImgBurn, it'll either be your hardware or something OS related (drivers etc).

Try 4x and 6x. If your drive still can't burn them (and assuming the discs aren't faulty), invest in a better drive. Slimline drives are all pretty rubbish.

and you've got a space after the '\' character. If you don't know how paths work in Windows, use the browse button rather than typing it in manually.

That could be part of copy protection - notice the odd TOC with data, 2 audio and then data again. Because ImgBurn doesn't use 'raw' writing, it may never work.

Someone has submitted a patch for Wine now so it should be fixed in the next release.

If the drive looks like a share to ImgBurn, it'll try and call the NetUseGetInfo API function and that'll cause a crash. Maybe removing all the drives in Wine config doesn't really remove them all. Nope, updating Ubuntu wouldn't help. The issue is with Wine.

Submitted as WineHQ bug - http://bugs.winehq.org/show_bug.cgi?id=29173

Out of interest, could you please go into Read mode (Create image file from disc) and copy + paste all the disc info from the box on the right (the box scrolls) when the problem disc is in the drive. Thanks.

If your drive and discs don't want to work together then there's nothing I can do about it. It's a hardware issue. I told you exactly what (eventually) worked for me. If you're 100% sure you've followed exactly what I said then you've done all you can. Buy some other discs and/or another drive - see if you have the same issue with the new one(s).

Yup, that's another problem between the drive and the card. It might be one you can clean up by using a top quality (i.e. SATA3) *short* cable between them. Personally, I'd just forget about using the Via card with that drive.

It appears to be crashing inside an API call (NetUseGetInfo)... so it's probably a bug in Wine and therefore out of my hands. The code in my 'IsNetworkDriveDisconnected' function hasn't changed in years. As for the cpu and admin thing, well, don't forget that Wine is doing stuff between the app and your real OS. I don't suppose it emulates a limited user just because you're a limited user in the real OS. Update: What I'm seeing in Ubuntu 10.10 / Wine 1.3.33 is this... The function is only called when you have a network share configured in the 'Wine configuration'. Feel free to report Wine's apparent lack of an implementation of 'NetUseGetInfo' over at Wine Bugzilla - http://bugs.winehq.org/ Update 2: Ah and the reason it's only starting to crash now is that it uses run-time dynamic linking on the netapi32.dll file (only via GetModuleHandle) and can only call the NetUseGetInfo function if it's successful. As it happens, netapi32.dll wasn't automatically being loaded by the app (prior to 2.5.6.0) and so the function never got called because GetModuleHandle would have failed (returned NULL). It can only get the handle of loaded modules. Starting with 2.5.6.0, one of the 3rd party components loads it and so my call to GetModuleHandle(netapi32) is now successful - which then means the NetUseGetInfo function can be called. Wine have messed up there really. They shouldn't have exported the function if there was no implementation (not even a stub) for it.

Try it with the latest firmware on your drive - http://www.firmwarehq.com/Optiarc/AD-7260S/files.html If that doesn't work you'll have to try it in another drive - or use another app.

That's due to your Via card (or its drivers). If you need to have the drive attached via a PCI card, get one using a Silicon Image chipset (e.g. the Sil3512 chipset). The alternative is to go USB 2.0 (or 3.0) -> SATA... but then there's always a risk of running into a 'semaphore timeout' issue.

Please copy + paste everything from the log window. If you go into Write mode (write image file to disc) when there's no disc in the drive and then insert a disc, you should notice the message in the statusbar at the bottom of the main window changing. If it just ends up on 'medium not present', I don't see how any other program can be working - unless that 'medium not present' error code is a false one supplied by a filter driver.

If no discs work at all (cds, dvds - originals, burnt discs and blanks), your drive has probably died.

Please don't follow that guide, it's all wrong/complete rubbish. You don't ever want to force PIO mode. Update the firmware on your drive - http://www.firmwarehq.com/Pioneer/DVR-112D/files.html Try cleaning the drive with a cleaning disc. Burn at the other supported write speeds - there's nothing to say 4x will produce the best quality burn - obviously in your case it isn't working at all!

If your drive can't see (recognise/initialise) the disc you've put in it, try some other discs.

This is nothing to do with ImgBurn. Assuming these are 'DVD Video' ISO images, the aspect ratio comes from the IFO and VOB files - and this information isn't modified in any way by the burning process.

Glad to read you got it sorted