LIGHTNING UK!

Have you tried cleaning your drive? Do you have access to any other dvd burners that you could use to get the disc id of the media you have?

Yes, ImgBurn is freeware. Yes, you've been done. You should try and get a refund.

I have no idea what you're talking about. Was the PDF even from here? (I didn't know we had any!)

Look for an updated firmware for your drive. Failing that, buy some different discs.

Is there any chance you could 'tag' a tiny sample (like 10 seconds or so) of a wave and email it to support?

That can happen DirectShow won't accept the file and ACM decoding has to kick in. If the MP3 has the wrong value inside it for its length, ImgBurn can reach the end before it's supposed to. The problem has been fixed for 2.4.3.0.

Nothing in that was you even attempting to burn a disc! Open the program, burn something and then copy + paste from the log window when it's stuck on the 'sync cache' bit. The log window is open by default on a fresh install. If you've closed it down, open it up again via the 'View' menu.

Your drive can't read back what it just wrote. Bad disc? Bad quality burn from your drive? Try cleaning the lense with a cleaning disc.

And you're trying to burn at a speed (2.4x) the drive will ignore anyway because it only supports 4x, 6x and 8x on that media. Try burning at 6x or 8x, it might mean you don't have to bin the remaining discs before you start buying Verbatims.

If it ever did do that, I've already fixed it because it sure doesn't do it now.

I wasn't aware the WAV format really used tags?

It's the same person mmalves! jeniece, please stop opening new threads about the same issue... it's getting annoying very quickly. Don't use beta software (especially an OS!) if you don't know what you're doing - and it would appear you don't.

Where's the ImgBurn log?! Post ImgBurn logs on the ImgBurn forum please, keep your Nero ones for their own support team. So anyway.... Your drive bombed out with a 'Write Error' That happened at sector 2088800 which is about 50% on the disc I expect... exactly the same place you said ImgBurn reported an error. So basically, give up with the memorex discs and buy Verbatims. Once you've done that, if they still fail, try cleaning your drive. If it STILL doesn't work, buy a new drive.

It's probably due to the controller your drive is connected to and the mode it's in / driver that's in use. Do you have access to any other PC's you could try it in?

You probably need the 2.4x speed verbatims (MKM-001-00 dye) with an old drive like that.

Nope, no special settings. Just make sure you're using Taiyo Yuden discs and burn at roughly half the max speed your drive supports on them. i.e. if it lists 48x, burn at 24x or something. Just as it does for MDS / ISO burning, if you select the BIN and a CUE is present, ImgBurn will tell you that you should have picked that instead and use it automatically. I guess I could update the guide(s) to mention BIN/CUE files.

I'm afraid so.

The LB you set in your authoring program will have SPLIP set to 'No' so it'll be pretty obvious which one it is. If you don't select that one then ImgBurn will set the old one's flag back to 'yes' anyway. I don't think having 2 cells where the SPLIP flag is set to false is a big issue anyway, it's more likely to be a problem when it's NOT set and the drive has to switch layers (i.e. a seamless layer break) but even then all the newer players seem to cope with that just fine (and superbit dvd's have been authored in this way since the format was first released).

You're only the 2nd person to have reported this as a bug in the entire time it's been in the program but I'm wondering if I should make it more obvious that it's the 'Usage' percentage and not anything to do with processing?

Probably using old firmware, crappy discs or burning too fast for your drive/firmware/media combo. Post the log any we'll be able to offer some decent advice (copy + paste from the log window when it's stuck at that end bit).

You already have a thread on this do you not?! If the file's MD5 checks out ok and it burnt + verified ok you should be contacting Microsoft about the problem... oh and let's not forget that it's BETA software. If you aren't good with PC's then you shouldn't be using it!

Yeah just 'borrow' the nero wnaspi32.dll and stick it in ImgBurn's program folder until I release a new version of ImgBurn that has a workaround for NVIDIA's buggy drivers and will make SPTI work again.

I've been thinking about this some more and I was wondering if you'd tried doing via the files 'archive' attributes? So basically you reset the archive attribute on all your 'old' podcasts, just leaving it switched on for all this months one. That means the new ones + any additional ones you download this month will have their 'archive' attributes set. Then you tell ImgBurn to backup your podcast folder and check the 'Include Archive Files Only' box (or rather save it as 'on' in your project file). You also then tell ImgBurn to reset the archive attribute once it's finished making the image/burning the disc. That would work wouldn't it?

Revert to older ones or select a different I/O interface in the settings. The current nvidia drivers mess up if you ask for anything over 18 bytes of 'sense area' data (which ImgBurn does). Most 3rd party I/O interfaces appear to limit whatever you ask for to 18 so that gets around the issue.

Ok, the answer is still no I'm afraid.