LIGHTNING UK!

Go into device manager and try removing the 'controller' entries from under the 'ide ata/atapi controller' branch, then reboot. Make sure you verify when you burn. Try a cleaning disc in the drive too.

That firmware is now available here - http://www.firmwarehq.com/download_1146-fi...G_X152.zip.html

ImgBurn always closes/finalises the disc when it burns. It's not something you need to do manually.

Open the log window (or rather, stop closing it!) and then copy + paste from it.

Use better (write once) media, your drive doesn't like that dye.

Pioneers booktype automatically (well, on DVD+R DL anyway) and burning tools cannot change the settings.

Use some decent discs. Rewritables aren't any good at the best of times... stick to DVD-R or DVD+R. Verbatim / Taiyo Yuden discs will give you your best chance at a successful burn.

You can access saved logs via the 'Help' -> 'ImgBurn Logs' menu option. btw, you have an old version of ImgBurn installed. You should update to the latest one.

If you don't/haven't closed the log window then you can just copy + paste everything from it. That log window is designed to be left open all the time. It's an integral part of the program.

Within ImgBurn, click Help -> ImgBurn logs. You'll find the log file in the folder that pops up. Might I also suggest you reopen the log window (View -> Log) as it's designed to be left open all the time.

check eventviewer and see if windows file protection is putting it back there. If not, it's probably a virus.

Yeah do that, your Aopen drive seems rubbish.

Get some 8x Taiyo Yuden (TYG02 dye) discs.

Thanks. Now I'm no expert on the ogg/vorbis comments but it would appear to me that the field length of the COVERART_UUENCODED is wrong in the file. It lists it as 32250 bytes when in actual fact it should be 32558. Comments are laid out like this... As such, ImgBurn tries to read the next comment's length from a place that's in the middle of the previous comment and is then getting some huge value for the length - which the program cannot then allocate memory for and it causes a crash. I've implemented a sanity check whereby if the comment size exceeds the file size it'll just bomb out of parsing the comments.

ramthx, So it looks like it's sten.tfx that's crashing. I've never heard of it before so try googling it. Locate the file on your hdd and delete/rename it, that should fix it. (It still looks like something dodgy to me!) ericdee, Make your own thread.

ISO is for Mode 1 / 2048 files. BIN (with an accompanying CUE) is for everything else. That's the way it's supposed to be (standards are standards for a reason!) and you shouldn't override it because you have some strange concept in your head that all your images should be ISO's.

Yes, it's a bad disc.

It's actually paused at the point you're looking at, you need to press F5 (or Debug -> Go) inside WinDbg to make it run properly.

Open it inside WinDbg (free download from Microsoft) and maybe it'll capture/log where the problem is.

If you still have an example of such a problem file, I'd like to have a play around with it myself to check the crash was in the directshow filter and not ImgBurn itself. Is there any chance you could email it to the support address in the program's 'About' box?

Are you saying that all your ogg files do this or just the one?

This isn't anything to do with ImgBurn and you're more likely to get help on a forum dealing with tsmuxer and the whole acvhd thing than on here. Doom9's forum springs to mind.

Do you see the splashscreen or nothing at all? If it's the latter, either you've got a virus that's stopping it from loading or one of your antivirus/spyware/malware utils is playing silly buggers and doing the same thing. Find out which one is correct and (in the case of software playing silly buggers) report it to the vendor.

Look harder! Tools -> Settings -> Build -> Advanced -> Image Start LBA.

Even the newest firmware for that drive dates back to 2005. Those discs are probably too new for it, try the 2.4x ones instead (MKM-001-00 dye). Of course the other option is to buy a new drive.