LIGHTNING UK!

ImgBurn has a fallback in the 'Create CD CUE File' window whereby any 'unknown' file that's So either select 'all files' for the file type in the browse box or drag + drop your mpa files into the window. I've added support for 'MPA' in the next version of ImgBurn so they'll show up automatically. As for the PCM/WAV thing, you'll need to provide more info as I was unable to reproduce it earlier. A good way to test things is to load the file in GraphEdit. ImgBurn basically works in the same way it does.

If you've got a problem, post the log. I've done a few DL burns today and they've all written / verified perfectly.

Sorry, I kinda meant the 'shaking window' thing rather than making it active. I remember seeing someone else with this exact same problem aaaages ago. I honestly can't remember if he ever got to the bottom of it, he probably just reinstalled the OS or something.

If your machine is basically pausing ImgBurn when it's not the active window then there's nothing ImgBurn can do about it. The process priority is already set to 'High' by default when burning. You need to look elsewhere for the root cause of the problem.

Please provide the complete log, that one is missing important information.

I need the log showing the error and also all the disc info as taken from the panel on the right when in Read mode. Make sure you're running 2.4.1.0 too please.

Sometimes you have 2 SATA controllers on a motherboard. One that's part of the main chipset and the other via a 3rd party controller. You might need to check the manual to work out which is which.

What's the PCM/WAV that won't come out properly? Is the file extension actually PCM? A file with the PCM file extension is written 'as-is' as I kinda assumed it would be 44kHz 16bit. Without the user manually entering the file format, I'm not even sure it's possible to know what the contents of a PCM file are. I just decoded a 48kHz WAV file and that worked fine for me. MPA will probably work if you actually try it - assuming DirectShow can interpret it of course.

The program is not in control at the point where it's stopping - I know this because you're unable to abort. Basically it's sent a command to the drive and it then waiting for the OS or whatever to process it. Control is only returned to the application once it's either completed successfully or errored out. You're not getting either of those things happening and that's why the whole system kinda hangs - the I/O subsystem has hung/crashed and rebooting is the only way forwards. Do you know which controller your drive is connected to? Are the drivers up-to-date for your motherboard? What about the bios? You could try following the post in the FAQ relating to resetting DMA (it involves uninstalling your controller and rebooting) - this often fixes a lot of problems.

You might want to change the 'Write Type' back to SAO/DAO in the settings too.

The cue sheet is not the problem, it's fine.

Try any of them. I don't think the files have anything to do with the issue. Use the eject button in imgburn to get the disc out. The tray is locked, that's why the button won't work. ImgBurn issues the unlock command before the eject one so it gets around that problem.

Do you have any decent CD-R discs to try it on?

It would appear the drive is giving up as it moves over to track 3. If you were to attempt to burn that same CUE again (say 5 times), does it fail each time in the exact same place? (please don't just guess if you've not tried it!) If you then try to burn another cue (on the same disc, without rebooting etc) does it work fine first time?

Do you still have the file that didn't decode properly? I wonder if I might be able to detect this issue during the analysis phase so I can inform the user and save them wasting a disc. It must be certain files encoded in a certain way with a certain (possibly buggy) program.

A write error is just a write error. So for whatever reason, the burner was unable to write to those sectors (or ones before it - due to buffering). The more you burn, the 'older' the drive gets. It could also be dust on the lense or a decrease in the quality of the discs. For the 100 odd you've burnt, maybe they were only just ok and now that things are a tiny bit worse they're failing.

You can't call anything a bug until you know what the actual cause is! Where's the log of the burn? Do you have a screenshot of what's on the screen when it's stopped and no longer doing anything?

This is a drive/firmware/media issue. If you really have burnt 100 RITEK-S04-66 discs with only 4 failures I'd personally consider you to be very lucky.

The program doesn't even look at the image content if the MDS value is valid.

I can't actually see a problem with that info. Assuming your disc's layer break info is correctly recognised as:

NTSC / PAL doesn't even come into it. ImgBurn is a burning tool, not a conversion one so the file stay in whatever format they are in on your hdd. Tell Pinnacle you want NTSC output and you'll be fine.

What does the disc info look like in the window on the right in ImgBurn with that MDS mounted? (copy + paste it all) There must be *some* reason why ImgBurn doesn't think 2070432 is acceptable.

Your media is rubbish and that's what caused the power calibration error - the drive just doesn't like them. A firmware update might improve support for them but I haven't checked to see if there is one for your drive. The DMA error is caused by your system configuration. If you search the forum I'm sure you'll find other threads where it's been covered before.

Your best chance would be with 2.4x MKM-001-00 Verbatim discs, not the 8x MKM-003-00 ones.

Magic? Mine certainly only burns at 1x with FastWrite disabled. 2.4x would be overspeeding anyway would it not?!