LIGHTNING UK!

What happens if you re-enable the 'Verify' option? I just want to see the point at which it fails. What controller is the drive attached to? Right click the drive selection box and click 'Family Tree'. Close the prompt and then copy + paste all the info from the Log window.

Your drive doesn't support those discs (MBIPG101-R10-65), buy some others. http://forum.imgburn.com/index.php?showtopic=8000

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

The standard character set doesn't support the 'dot' character for anything other than the separator between the file name and file extension. (XXXXXXXX.YYY) As you have files that require 2 dots, you simply cannot use the 'standard' character set and must change to a less restrictive one (as you've already found out).

It makes no difference.

It could be, yes. You won't know until you try though.

Your drive reported a 'Write Error' as it tried to burn the disc. Have you tried burning at 4x? Oh and you were burning MKM-003-00, not MKM-001-00 as stated in your initial post.

That's why the program has the ability to check for updates. I guess you disabled it.

The problem wasn't just with finalising it, you got a retry right at the start of the burn too. Slower doesn't always equal better and sometimes it makes things worse.

v2.5.0.0 from July 2009 ? I'm sure you can do better than that.

What newer firmware have you found for it? 1.01-A0 seems the latest to me and you're already running it. Have you tried burning at 4x?

You should start at the first byte in Sector 0. There is no end marker, that's why you just go by the 'capacity' of the disc. If programs choose to limit what they read to a value written in a file system within the image, that's down to them. Doing so isn't fool proof though and that's why I don't do it - unless reading from a DVD+RW / BD-RE where it can actually make a massive difference (because the disc capacity is always reported as the full/maximum capacity of the disc). When ImgBurn is used to 'Build' an ISO, it always does so in a way that drive padding isn't an issue/used.

Ok but can it still see other discs ok? Original CD / DVDs? Ones you've burnt in the past (single layer I guess) ? Other blank single layer discs? If it's reporting garbage like that for all discs, you have to assume the drive is faulty. If it's only reporting garbage for the double layer discs you've just purchased, it must be that the drive's firmware doesn't support them. Buy some others and hope it likes those.

Assuming the drive can still see other discs correctly, it must just not like those.

I like to write on my discs with a CD pen so I'd choose discs with a surface like those in the first link rather than the 'printable' ones in the second. I'm pretty sure Victor JVC bought Taiyo Yuden so all of the new stuff on the market will probably have their name on it. The whole 'value' thing in the name of those discs puts me off, but they could just give them that due to the very basic shiny silver top layer and basic shrink wrap packaging (no spindle tub etc).

I only ever buy Verbatim and Taiyo Yuden.

You'd have to figure out where DVD Flick puts its temp files / output the project to and delete them.

You can pause it but you can't stop and restart it. Once the disc has been burnt (even partially), it stays burnt.

Have you tried burning at all of the supported write speeds?

It really doesn't look well. Did you try cleaning the drive with a cleaning discs as suggested earlier? and how about trying discs from another spindle? Maybe some MKM-003-00 instead of MKM-001-00? Consider getting yourself a USB enclosure and put a decent half height (i.e. non slimline) drive in it.

Have you tried burning more DVD+R DL's since post # 10? If so, what happened with those? Do you use DiscJuggler on your machine? I noticed the pfc filter driver being listed in the screenshot you posted before. I wonder if it might be worth trying to burn from within safe mode, or perhaps inside a 'live' Windows XP as found on Hiren's Boot CD?

No, don't disable smartburn, just buy some better discs. If you haven't already done so, try burning at 8x too.

Indeed, applications can't really crash Windows, only drivers do that. You should examine the minidump file to see what actually crashed it - assuming you meant you got a 'blue screen of death' ?

I used a program called ID3-TagIT 3. It's old now but does the job.

Ok well it doesn't work with the Windows 7 SP1 DirectShow filters either... but it does work with the ACM (a fallback) method. You must be missing a driver or something on your machine for ACM not to work. As mentioned in a previous post, the filters usually fall over due to there being something not quite right with the metadata (tags) in the file. I used a generic tagging util to remove the v1 and v2.3 ID3 tags and now DirectShow loads it fine. At this point, I can only assume the problem is with the ~700KB album art that's in the metadata! EDIT: Yes, that's it, it's the album art causing the problem. I just removed the pic in my tagging tool (leaving all the rest of the meta data) and now it works with DirectShow.