LIGHTNING UK!

No, what I mean is do those discs you've just burnt in ImgBurn not work at all? Can you not access the data on them/play them on your PC or a standalone player?

Shame you didn't include the Verify bit too If you're saying the ImgBurn discs don't work at all, gimme the exact name + version of a program that works out of the box and I'll compare some things and add options so ImgBurn can mirror it.

What makes you think that's wrong?

Got a log of the failed burns? There are only a handful of ways to do the burning / finalising so if the correct combo of settings isn't already available to give you something that works, I can quite easily add them. It's a shame that the Samsung drives have this problem but they do.

Get the latest 2.4.1.0 from the ImgBurn.com mirror, it deals with all this now. (all files are made uppercase using the 'DOS' character set)

You have an LG drive and the program would do it automatically anyway with those.

Yes that's a different type of writing The burners support Incremental, TAO, SAO/DAO and RAW write types. ImgBurn only supports the first 3. The .SUB file you see in CloneCD images is the raw subchannel data (not something the user ever gets to see) and I believe that can only be written when you're using the RAW write type.

Have you tried burning at faster speeds? You might find it burns better at 16x than at 8x. If you could get a pic of the IBG info displayed via DVDInfoPro that would really help too. If you don't have DVDInfoPro, you can attach your IBG file (zipped up or whatever). That'll show us the nice write/verify speed graphs. If the DVD-R verbs aren't working for you, you might like to try the DVD+R ones. I generally stick to Taiyo Yuden DVD-R's and Verbatim (MCC) DVD+R's.

No, 2.3.2.0 just doesn't query the drive for that info. New features get added in new releases and so your problem still stands... WHY is your machine hanging on that command?

I don't need a video, the log shows me everything I need to see. You can't read the decent discs that someone else has done and you can't burn your own ones. If I were you I'd re-read the 2nd post in this thread from Cynthia.

Yes. You only needed 5 posts to jump out of the 'moderated' group anyway - so it's no longer an issue for you. Any one of us can moderate your posts so it's not like you were missing out on anything... nobody was here looking at them.

Oh sorry I missed the 'reading a burnt copy' and assumed you'd run into a burning error with Verbatims too. So what's the problem exactly? You can't burn onto those RITEK-S04-66 discs? Get some others instead then.

You joined the forum at the wrong time, it's been turned off for new members again for a while now.

ImgBurn doesn't do 'RAW' writing and I doubt it ever will. The 'img' file would already be burnable but it just means you're limited to single session/track images.

Can we please see a log from the Verbatim burn? Also, check where they're made.

Your system must have an issue with the program querying the booktype settings. It's probably a dodgy (old) filter driver or old IDE drivers.

Audio CD's (CD-DA discs) need to be burnt onto a CD. If you just want to back the files up, you don't burn an Audio CD (CD-DA disc), you just use build mode.

Can imgburn display the right name? i.e. when you look at the disc in read mode? Post your log of the burn.

lol nah he won't!

Is Google not working where you are?

Where were your Verbatim discs made? Have you tried 4x?

The build function/code always outputs an image but depending on your choice of 'output', it's either streamed to the write/verify buffer or it's dumped to a file. There is no 'temp' file. The 'Building Image Tree' stage is where it's scanning the folders added to the 'source' window and adding all the files to its internal structure. The 'Preparing Image' bit is where it makes sense of all those files and calculates their order, physical location within the image and other stuff to do with the file systems and their layout.

Look at the 'Supported Write Speeds' text in the info panel on the right. Chances are that your drive / firmware just don't support that media at any slower speeds - if it did it would work and you wouldn't be here.

32k padding is in the file system (between files), not the file itself - so it's size doesn't change. What will/may change though is the offset pointers in the IFO files. So you won't always be able to do a file compare outside of the program between the raw files on your hdd and the files on the disc - hence the reason for making an ISO and comparing to the files within that (once mounted) to the ones on the disc. Verify does not compare file against file, it compares sector against sector. If one doesn't match then it performs a lookup to see what's at the specific LBA and displays the file name if it finds anything.

If you're in the UK, try www.svp.co.uk