LIGHTNING UK!

lol ok, can't get anything from that log except that it wasn't even close to finding any potential candidates. Go the PgcEdit route and see what it recommends. I think it tells you where you need to be adding extra cells - something I guess I should implement within ImgBurn too.

You switch to Verify mode, select the dvdrom (after putting the burnt disc in it), select the image you just burnt and then click the big 'Verify' button. It's impossible to say for sure (100%) that replacing the drive will fix all your problems, all you can do is try. Borrow a drive from someone if you can... put yours in another pc or try your discs in another drive. Only by trial and error will you get to the bottom of it.

Try closing it again manually. Click 'Tools' -> 'Drive' -> 'Close' -> 'Track/Session/Disc'. Do all 3, in that order.

So long as it's real 'MKM-001-00' dye and not fake stuff you'll be fine. I'd read that some Sony discs had started using it rather than CMC dye or whatever they used before - and that's great news! As for why it can't find any cells, I would guess the project is too big and ImgBurn just can't align anything whilst getting the correct amount of data on each layer. You can (I can!) find out more in if you get build mode all set up as if you were trying to burn that project, but instead of hitting the 'Write' button, hit the 'Calculate' one. But before you do that, press F6. Then when you click 'Calculate' it should stick a whole load more info into the log. Save the log to a file and attach it in your next post.

Can you verify the disc in the 'DVD-ROM' you appear to have rather than the writer? (hopefully it's not a virtual drive!) To be honest I'd just replace the AOPEN with something else and hopefully that'll work ok.

lol sorry it wasn't what you wanted to hear but if the controller doesn't work, the controller doesn't work! (It's fine for the 2 eSata enclosures/drives I have attached to it though). Normally when you get UltraDMA CRC32 errors you can just change the cable and they'll go away. Try that and if you're lucky it might work - it didn't for me. You might also want to try updating the bios on your motherboard. It might come with a newer jmicron bios. The latest abit bios for my board only puts the .69 bios on for the jmicron chipset but I think they're on .71 or something now. As mentioned previously, it's worth considering a little ITE8211 / 8212 (or Silicon Image 680) chipset PCI card to run the IDE drives. You can pick them up on ebay for

That jmicron controller is utter shite (I've got the same one on a new abit IP35 Pro board). I got the same error from the drives I had on mine and so I just replaced them with some newer SATA ones. I do have an ITE8212 card in a PCI slot though and that's got 4 IDE drives on it that all work fine.

Blimey this is getting to be a very common sight with Samsung drives! It would appear the drive is producing bad burns, try cleaning it. You might also like to try some Verbatim DVD+R media instead of the DVD-R ones. Your very best bet though would be to get a decent external drive. Those slimline ones in laptops are never any good.

I honestly don't think you've any need to touch these. The NEC works fine and so in that sense there can't be a problem. I only said to remove the asapi one because the copyright date mentions 2001 - which of course makes it very old - unless they just don't ever update it.

Don't output to an ISO in Shrink, just output the DVD Video files and then use ImgBurn's build mode.

Looks like you're getting duff burns from the drive - hence the reason for the verify stage failing. Try this firmware update. ftp://ftp.aopen.com.tw/pub/firmware/dvd+r...1608arr_111.exe

ASAPIW2K is all I'd get rid of. I'd update the others by updating the relevant programs.

It's normal for 'Device Buffer' to be at 0% during the verify phase - that's because it represents the data from the cd/dvd drive and the other 'buffer' represents the data from the hdd. Obviously the hdd is loads faster than the cd/dvd so you'd expect the 'image buffer' to be full and 'device buffer' to be empty. To see if it's 'going anywhere', just look at all the counters on the screen. They'll be incrementing as it compares data and the 'verify rate' will show you the exact speed. If in doubt, post a screenshot or something so we can see what you think you're seeing. btw, your log just showed us the burning stage - and even that was still in progress!

Well if you follow the curve of the graph, if it's already at 80% cpu usage and it's only burning/reading at 12x, by the time it gets to 16x you'd be past 100% - which of course isn't possible! So I guess the drive wouldn't ever actually reach the full 16x, or at least it wouldn't be able to maintain that speed without the buffers going a bit mad. The drive itself is fine, don't worry about that.

That's not my area I'm afraid. Have you tried Virtual CloneDrive from http://www.elby.ch/ ?

ImgBurn checks for the presence of a 'known' file system and those firmware images don't have one. It's not often you come across an ISO with it's own proprietary format, so it's not something I've really paid much attention to.

1. Update ImgBurn - http://www.imgburn.com/ 2. Update the firmware on your drive. You should be running v1.04 now, not v1.01 - http://support.necam.com/Optical/downloads...CND354_v104.exe 3. Ditch the CMC discs and buy Verbatim DVD+R DL ones instead. Verbatims are by far the best.

Oh, they'll be fine then. It would only be an issue if you had a bin/cue of an audio cd or something (where the 'bin' would then be data from multiple tracks). CUE support has been added for the next version which I hope to release fairly soon.

Well unless you just got a dodgy batch of discs, I don't really see what else it could be. If it can't burn to Verbatim DL discs, there really isn't much hope for it making a decent burn on any of the other brands.

Sorry Paul.S, there's nothing I can tell you that'll get those images working with current versions of ImgBurn. I've made the next version support them though.

If it's a single session / track image (BIN file) it'll burn fine. If not, no it won't. The reason it doesn't make you search for the CUE file is because CUE files are not supported in the version that's currently available. (v2.3.2.0)

I'm sure that drive can't be that old... it's still a current model! Pretty bad if it's died already. Hope the new drive works ok for you.

The error from the BenQ is it's own problem. The error from the NEC was my fault - that's why you should always update the program. Even if you don't actually have an issues with old versions, there WILL be bugs that you're just not seeing and they could be screwing up all of your discs in ways you can't see yet. You only need to look at the extensive changelogs to see all the things that get fixed / improved - and I don't do that for the good of my health

Yup.

Still at 80% CPU when reading at only 12x! I imagine it would die before it reached 16x