LIGHTNING UK!

It's not for me to tell you how you use my program. Use it however you like. For your sake, just make sure you're legally allowed to make copies of the disc. All you do is make an image using Read mode (saving it on your hdd) and then write it as many times as required. In the end you'll have a bunch of images on the computer's hdd that will enable you to burn extra copies later down the line without having to dig out a source disc.

What error messages? There's already an option to follow junctions - Tools -> Settings -> Build -> Page 1 -> 'Advanced' box -> Include Reparse Point Files

Those options aren't ImgBurn options, they represent how your OS is currently configured. What happens if you burn a disc, close ImgBurn, press F5 to refresh the 'My Computer' window, eject the disc, F5 again, insert the disc, F5 again? The drive icon should be changing during those different states/stages. There's a Microsoft Fix It for Autorun stuff too - http://go.microsoft.com/?linkid=9743275 (found here http://support.microsoft.com/kb/967715 )

The chipset driver won't have done any harm. It's an Intel one and will only install what's compatible with your machine. You should look into the cause of the BSOD. The (mini)dump logs usually provide enough info about what driver crashed. Filter drivers will always show up (they're values in the registry), they just shouldn't really get loaded - that's the whole idea of safemode (so as to get around issues).

Believe me, what you posted cannot ever be the only thing written in that box. It's the last thing written in that box (last section anyway).

We need to see the burn+verify log from ImgBurn.

Most autorun settings can be manipulated by ImgBurn itself. Go into Tools -> Settings and look on the Device tab.

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

Nope, and it wouldn't work anyway. You'd need a firmware update from Acer.

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.