LIGHTNING UK!

ImgBurn is just a burning tool - what goes in = what goes onto the disc. You'll need something besides ImgBurn if splitting is what you're after. Try using Google to find your answers.

Erasing the disc isn't the problem, I've erased DVDRAM before without any issues. (I could erase another one right this second if it would mean anything?!) The problem is just with the drive/firmware/media combo. Try getting some panasonic dvdram discs and forget the ritek ones.

Yes it's basically the same process. You might want to change the file system option to include all 3 options but that really is up to you and will depend on where you intend on using the disc. Personally I'd have to say you're better off sticking with the single layer discs - they're more reliable not to mention cheaper.

Just open the exe with winrar or something. You can get the dvdform exe from it that way.

Try here http://panasonic.co.jp/pcc/products/drive/...PDrv5301NEN.exe

I've not had enough experience of DVDRAM to know if there's any way around this. It just seems as though there's something wrong with the disc - or at least the drive doesn't appear to like it very much. In a last ditch attempt, you might like to turn off the 'spare areas' option in the ImgBurn settings (on the Write tab). You could also try Panasonics DVDFORM tool and see if that works.

Try another full erase and post a copy of the log.

The erase within ImgBurn removes everything (including the file system itself - if there was one) on the DVD-RAM disc. The disc can then only be used for burning images to via 'Write' mode or files to via 'Build' mode (another proper burning tool). The OS won't deal with it until the disc has been formatted and the file system recreated. btw, what makes you think it ended prematurely if there was no error message? If it failed, there would be a message of some sort!

You had a system glitch some way before the layer break. I'm afraid it really is down to you to figure out what caused it. First things to check are up-to-date motherboard bios, drive firmware, cable to drive (+ location on cable and jumper configuration). Try burning with just that one drive on the cable (if it's not already like that). Update all the chipset / ide drivers in the system. Check your filter drivers (can be done via the 'Tools' menu in ImgBurn) and remove and drivers that aren't from Microsoft and aren't fairly recernt (i.e. year 2006+) - well, remove or update the programs that put them on.

No, ImgBurn is just a burning tool. What you need is something that can reauthor multiple titles / dvds into a whole new one. I've never wanted / needed to do that so I can't really help. That said, you can find help on just about anything if you search Google.

An ISO is a disc image. You can't merge them, they must each be burnt to their own discs. If you break the ISO down and extract the files from within it (mount in DAEMON Tools + copy the files out of the virtual drive using Explorer), you could then combine them that way. It's a bit more complicated than that but it's beyond the scope of this 'ImgBurn' forum. As for the error, check for firmware updates and try different discs. Your drive seems to have issues burning to media using the CMCW02 dye.

Sorry yeah, 'dropping' it would assume it's NOT already ticked in the GUI

Drop the preservefullpathnames switch. If you use that it means you'll get a 'data' folder with 'sourcecode' in that and 'vlan_setup' in that.

ImgBurn won't fix your files for you. If they're broken in the first place, they'll be broken on the disc. If they weren't broken, the disc you burnt would already work. Get the files playing properly (with menus or whatever you're making) first AND THEN start thinking about burning them.

Going by this list.... Yes, chewy is telling you they're not supported by your drive. The 2.4x ones are though. Hence MKM 001 being listed and not your MKM 003 ones.

Reinstalling might fix things - so long as you update all the bios/drivers/firmware along the way too!

Putting it in the same units, it's: Nero = ~1 GB ImgBurn = ~0.0015 GB (Where '~' means Approx) The way you're saying things is a little confusing - I guess that's because English isn't your native language.

Your drive is old and only supports DVD+R media. If you're using DVD-R media, that's why it doesn't work.

That's not a drive error, it's a Windows error where the DeviceIoControl API is failing. It'll probably mean more to you than it does to me... what with it being in German and all that

I really need to see why the command is failing. To do that I need you to enabled 'I/O Debug Mode' just before you burn. Simply press the F8 button before you click the 'Write' button. Then once it's has errored out, press F8 again to disable 'I/O Debug Mode', save the log and attach it in your next post. btw, can I assume you've at least tried cycling the power on the PC?!

Yes, it does help if the CD/DVD is inserted around the right way!

The booktype stuff often fails when one of the close track/session/disc commands fails. This is more the drive's fault than ImgBurns - I simply tell the drive to do before the burn and it should then remember that it needs to when it gets to the end of the burn. It's not an actual function that ImgBurn has to perform.

You had your answer in the 2nd post. Ditch the Ritek/Ricoh dyes discs and get some Verbatims DVD+R 2.4x ones instead (MKM dye). Burn at 2.4x.

That's what ImgBurn already does in order to burn the image. But with a 'complex' image (i.e. multisession/track - which a VCD is), that doesn't work. The 'complex' image is just burnt as a 'simple' image hence all multisession/track information is lost and the disc will not play.

You just make a file called ImgBurn.ini in the app directory donta. ImgBurn will then load/save to that instead.