LIGHTNING UK!

Sorry to be a pain but could you scroll the window and post a couple more screenshots so I can see all of the tracks?

It's actually joined on to the 'create AUDIO_TS folder' option for DVD. Do you have any info that might help me tell the difference between an AVCHD disc and a BD disc? (like other file/folder differences) EDIT: Are you 100% sure it's the 'certificate' folder that's causing the problem? All the burning guides I've seen for AVCHD have specifically mentioned adding the 'CERTIFICATE' and 'BDMV' folders to the list of things to burn. I guess you'll find out for sure when you disable automatic creation of the certificate folder via that option I mentioned and test it

Check the 'Tools' menu

The stuttering would be because you're using cheapo discs. Invest in some Verbatim / Taiyo Yuden's instead.

Sorry, the error code (a numerical values) comes direct from the OS.... ImgBurn displays the error box with that code translated into plain english (again using an API function - so it actually gets translated to your native language)

Screenshot?

Miscompares could be a dodgy filter driver and/or memory corruption. Test your machine using MemTest+ or something - leave it running for a couple of passes. You could also try the drive in another machine, and another drive in your machine.

Can it not even see an original disc? (i.e. in 'Read' mode)

Because you're using inferior discs.

No it's not normal, both should work equally well.

This isn't something ImgBurn does... you need a program that can reauthor DVDs. Try searching Google.

I'm not convinced the 'ImgBurn Support' forum is the right place for this kind of question.

For drives that throw up the 'Program Memory Area Update Failure' error you might want to disable the auto retries on finalisation failure.

It seems your machine just cannot handle having 2 buffers of that size. One buffer is for the reading part - i.e. as ImgBurn reads all the files off the hdd (think of it as a cache). That buffer comes into play for both output modes within Build mode. The other buffer is only used when burning to a disc and basically contains cached data exactly as it's sent to the burner (i.e. after all the processing). Obviously then, this buffer is not allocated when creating an image file and hence output to image does not bring up the error. If anything, you'd want the 2nd one to be bigger, not the 1st (reading) one. (Why can't you leave them both on their default values anyway?!) The actual error messages are direct from the OS. You'll have to talk to Microsoft about why they're coming up when the VirtualAlloc API function is called.

Media Player opens a 'handle' (has a connection to) all the optical drives in a machine even if it's not actually using them. When ImgBurn goes to burn something, it tries to gain exclusive usage of the drive (so no other program can mess up the write operation) and it fails because WMP is using the drive. So basically, you can only gain exclusive access on a drive if nothing else is using it.

Yup, with that kind of error code it's going to be coming from something other than the drive itself - i.e. the controller.

What drive are you reading it in? (post the full log or something) Maybe the disc is protected against copying - in which case ImgBurn cannot help you (nor can/will we).

The CUE file you're thinking of and the Cue Sheet error the program is displaying are totally different things. Load your queue and bring up the image information screen so I can see it place.

It appears to be using the wrong source path as I'm fairly sure it shouldn't be attempting to backup your entire 'C:\Documents and Settings\Owner' folder! Lots of the files in that folder will be in use and locked so no other program can read them. This will be a DVD Flick issue (as it calls ImgBurn directly) so you're probably better off asking on their forum. Of course if you're running ImgBurn manually then it's something you're doing wrong.

Do as mentioned earlier, slow the burn down to 8x or 12x.

You have 4GB data files?! lol what on earth of?! 1.50 is only useful for data because DVD Video must be 1.02... and they're the only 2 real uses for UDF at all - well, until I implemented 2.5 / 2.6 for Blu-ray and HD DVD that is.

You make the changes in Device Manager really, not the BIOS.

Laptop drives get dirty quickly because the laser is always visible and people put their grubby fingers on it (all be it by accident!).

Let ImgBurn create your disc from the VIDEO_TS folder (Read the Guides section of the this forum), don't use UltraISO - it's made a non compliant DVD Video image.

If you're sure the correct drive is selected in the box and that you're putting supported media in to it, keep an eye on exactly what the status bar says having just inserted the disc. If is says 'in progress of becoming ready' and then changes to 'medium not present' again it means the drive can't initialise the disc or some 3rd party drive is messing up communications between it and ImgBurn. If that's the case you'll need to look at clearing out your filter drivers and updating all of you software related to optical drives.