LIGHTNING UK!

ImgBurn is fine, let it do what it thinks best. DVD Video uses 'ISO9600 + UDF' - period! You should not have a VOB file any larger than 1GB (- 2KB) in size. If you have, you've messed up some options somewhere in whatever created it. So basically, you have a 'source files' issue here, not a burning one. Until it's a burning one, this isn't the place for you to be asking questions (because we can't / won't answer them) - Sorry!

DVD Dec wouldn't be parsing the filesystem, that's why. Open the drive in explorer, highlight all the folders, right click and select 'Properties'. It takes aaaaaaagggggeeeees to count up all the files etc and show you the sizes. Sorry but that's just how these slow devices work. What I'll do is add an option to turn off the parsing, or to automatically cancel it if it's taking too long - i.e. over 20 / 30 seconds.

Your drive is just creating burns it can't then read back properly. To start with, update your drives firmware to v1.06 http://forum.rpc1.org/dl_firmware.php?download_id=1681 Then try finding some decent DVD+R discs. We recommend Verbatim / Taiyo Yuden. Go for the 8x ones as that's all your drive will cope with.

*cough* Update ImgBurn *cough*

There are no 'facts' here, all you're doing is playing a game of Russian roulette. If you try something enough times, it's bound to happen eventually. When you use Verbatim media, that would mean you occasionally get a duff burn. When you use the other brands, that would mean you occasionally get a good burn. I don't expect you to understand the technical side of the issue you're experiencing and how the software plays no part in it, but you really shouldn't be quite so cocky about the whole thing. It'll only come back to bite you on the arse - and I mean that in a friendly way!

There are loads that don't need to be there. He should only really be overriding the ones he NEEDS to set differently to the default ones. To remove the 'burn with imgburn' options, you just unclick the 'File Association' checkboxes in the settings and close the program down. If they're still there it's because another program has changed the file association stuff and I've no way of knowing where they are now.

Just exactly which files do you see in your VIDEO_TS folder on the disc?

You have a 4GB VOB file?! You might like to look into what you're doing a bit more. Clearly you're not quite there yet.

It's probably something in the settings. Perhaps the location of the logs / ibg / ibq files? It certainly wouldn't just make it for fun! EDIT: hang on, I remember now, it's from 'DVD Flick' cus the author didn't make the imgburn settings ini file properly! His name is Dennis Talk to him about it, it's his problem, not mine really.

Nah, most of them are the same thing. It's a heavily 'optimised' disc with loads of duplicates that only exist in one physical location but are referenced from loads of different folders. The actual size if you add all the files up comes to 25GB or something. The image is only 4gb.

Enable 'Verify' when you burn so the program checks the discs are actually readable. When you look at the burnt disc in explorer, do you have 'AUDIO_TS' and 'VIDEO_TS' folders in the root of the disc?

lol 270,000 files, 10,000 folders. No wonder it takes a while!

16x is only reached at the end of the disc. The quality of the media also plays a part. The drives are clever and will slow themselves down if they think the burn quality isn't up to scratch. So you need to be burning a FULL disc, AND onto decent media to get the full 16x / 18x etc.

Yes, that's it's function - unless the image file is split into multiple parts, in which case it'll also tell the program how to reconstruct it (by listing all their names). I urge you NOT to change the layer break setting to 'Manual' and instead to just use the .DVD for the purpose it was intended.

You don't ever need to touch the manual layerbreak selection option. Jeez I wish people would update their guides! If the program detects a .DVD file of the same name as the ISO you open, it'll prompt you to open the .DVD instead. It will always actually do that itself automatically and will prompt you when it's done it. If there's no .DVD to be found, obviously it won't prompt. The .DVD file contains the LB info needed to burn the image correctly. The two are a pair of files, you shouldn't delete either one of them.

That's because the drive can't write to the disc at all. It's erroring out at the very first 'Write' command. You're actually quite lucky they're still ok to use!

Nope, no circles there! Search for one of the LBA addresses mentioned and you'll see it only comes up once. What you've got there is a disc with probably thousands and thousands of files on it. The seek time on a CD is quite slow and so it doesn't get to read many per second - hence it takes ages. If you could send me the first 25mb (compressed!) of the image, I'll see if I can tweak it. (5mb is normally enough but this disc is out of the ordinary). Other than that, just leave it going and it'll eventually finish.

These are hardware issues. The software doesn't even come into it.

Buy Verbatim DVD+R DL discs, the rest are useless in comparison. Burn at 2.4x Check for any firmware updates too.

Press F8 and get me a debug log please. The drive is probably just messing up processing a command.

Looks like you're just getting bad burns with that drive. Try it on another PC and try another drive on your PC.

Perhaps it's a heat related problem then?

Does it burn and verify ok? The LB looks ok. It's bitset to DVDROM. After that, it's not really an ImgBurn issue I'm afraid. All I'd personally say to do is ditch the Ricoh discs and start using Verbatims. Buy the MKM-001 dye ones (2.4x speed) and burn them at 2.4x. You should also update your firmware. http://forum.rpc1.org/dl_firmware.php?download_id=2238

Your mate is using verbatim discs... I can't see what you're using. Other than that, everything looks fine. A log of the burn would help though.

You shouldn't believe everything you read. Things change! No, your problems shouldn't be Vista related. The errors should be coming directly from the drive itself. The image / software being used / OS have nothing to do with anything. This is purely a hardware / media issue.