LIGHTNING UK!

You're getting a lot of unknown error codes there... in fact, they're all unknown! What controller is the drive connected to? The drive must be about 8 years old now.... rather than wasting time with it, you could pickup a new burner that might actually work properly with your media?

Check for dodgy filter drivers too. (Tools menu) It's one thing for the lock to fail and report an error, it's another for the OS to just get stuck processing the command. You might like to update the firmware on your drive when you get a minute too.

It looks / sounds like a Jmicron controller. You can get drivers for that from here (I used them on mine ): ftp://driver.jmicron.com.tw/jmb36x/Win2k_xp_Vista/ Just go for the latest ones - by date.

Try cleaning the drive. It might just be on its way out.

Optical drives don't really like anything other than 'ATA' mode. If you can't use it (which obviously you can't), make sure you've got the latest Intel Matrix drivers installed (assuming you have an Intel board!) and that your drive's firmware / motherboard's BIOS is up-to-date.

Thank you for the donation

It ignores them. I have no idea how they should be handled or how to apply any processing based on their values.

The BACKUP folder on one disc only has 2 files in it. On the other one it also has copies of the PLAYLIST and CLIPINF folders that you can also see within the BDMV folder. So basically, just copy those two folders from the BDMV folder into the BACKUP (so the data is duplicated) - that's the whole idea of the BACKUP folder Likewise, remove the 2 folders from the non-working image that aren't present in the working one. Note that when I say 'remove' I mean put them somewhere safe out of the way - but where you can still get at them!

I don't think the 965 has an IDE port so it must be running off a 3rd party chip. Look in the SCSI/RAID controller branch instead. Intel driver wise, you probably want the latest Intel Matrix ones. http://downloadcenter.intel.com/Detail_Des...al&lang=eng The graph data thing might be taking a while because of your OS language? Is it in English? (Your IP suggests it might be German ) It's calling upon performance counters you see and if the English ones don't exist then it has to run extra code to get the localised names.

The 'Bus Type' comes from the driver so it's down to them to report ATA, SCSI, SATA etc. Which controller chip is used for PATA on that board? Jmicron? Silicon Image? A driver update from their website might 'tweak' what it says. I can't do anything about the empty but not empty disc problem. I can only go by what the drive is telling me, and in this case it clearly thinks it's empty. ImgBurn will unlock the drive tray before trying to eject it, that's why it works and Windows version of 'eject' doesn't. The tray is normally locked at the start of the burn and unlocked at the end. Obviously the unlock never happens because you're terminating the process.

Yes it's normal for the buffers to be full during the burn - you wouldn't want it any other way! Try speeding the burn up to 4x, the drive might actually do a better job. Are you sure the problem isn't with the xbox itself?

Pointing out the obvious, one has PLAYLIST and CLIPINF (duplicated to) inside the BACKUP folder and the other doesn't. One has AACS-- and CERTIFICATE folders and the other one doesn't. I assume PowerDVD itself has all the latest update patches installed?

You might be, who knows! All I really wanted is for you to not cancel the burn.... ie. leave it on the 'Creating Graph Data Thread' message and see how long it sits there for. The 'Creating Graph Data Thread' message isn't visible on my machine (nor should it be on yours) because it's done so quickly. I'd assumed your machine was stuck on that message forever but it seems it was just taking ages and you'd always been too hasty to cancel. I've just sorted the problem with it getting stuck when you cancel the burn at that point - it was because the function that waits for a thread can't cope if the thread isn't actually running at the time (i.e. it's suspended). I would have been interested to see the disc info for the disc that failed to burn because it wasn't empty.

Post the complete log of you building an image from the set of files that then wont play. Then open the ISO up with IsoBuster. Right click the file system in the left section (the branch under 'track') and click the folder/file info -> list in edit window -> lba full path option. Copy + paste all that info into the post too please.

How long are you leaving it on the 'Creating Graph Data Thread' bit? Can you leave it for like 10 mins... after that time just terminate the process - don't bother with abort because ImgBurn isn't in control anyway and so will not be able to. The drive will have been locked and dismounted by the program, that's probably why you can't use it in explorer.

PowerDVD won't play home-made BD images if Alcohol is emulating a BD-ROM (any image > 8.5GB in size). BDMV is probably the only folder you need in the root of the disc, all the files/folders are in that one. Try mounting the image in Virtual CloneDrive instead.

Does it fill the buffer ok? Basically, what does the message in the status bar say BEFORE you hit the 'Abort' button?

Had it died for all media (including single layer) or just that one? Anyway, enjoy burning to your Ricoh's!

Onto 1 DVD?! In DivX format (std resolution) they'd probably be 350mb each and that's about the best you'll get. You'll need a player that supports divx files of course. If you need them in DVD Video format (if your player doesn't support divx) you'll probably want to limit it to 3 or 4 episodes per disc or the quality will suffer. I don't know how this 'downloading from amazon' thing works but they might even be locked down (DRM) to your PC so burning to DVD might not be an option.

This is an nvidia driver issue which I've worked around for the next version. There are other threads here in this forum that go into more detail.

So you can't cancel the operation and if you terminate the process it doesn't actually go anywhere? That's basically what happens when I/O gets stuck - it's out of ImgBurn's control. Have you done any driver updates since it last worked ok? Have you installed any software that could have added extra (filter) drivers that might not be playing nicely? Which controller is your drive connected to? What 'mode' is it running in? (i.e. ATA, AHCI, RAID)

The difference between 'Device' and 'Image File' output methods is that 'Device' burns the data direct to a disc and 'Image File' creates an ISO image file on your hard drive - which you can then burn to disc later on via 'Write' mode.

Try some Verb DVD+R or Taiyo Yuden DVD-R/DVD+R first before going down the 'is the drive broken?' route.

That's about 10x speed then I guess? Doesn't sound like you have anything to worry about.

Your drive is making duff burns and it then can't read back what it just wrote. What speed are you burning at? Try 8x or 12x. If all else fails, ditch the media and buy some Verbatim / Taiyo Yuden discs instead.