LIGHTNING UK!

That's interesting then as they're using the Verbatim dye (MCC 03RG20)... I guess they're just fakes (or very low quality and Verbatim threw them away) and that's why the drive is complaining with those disc and not any others.

Ok, now see if you can verify a disc against an image on your hdd without the buffer being empty all the time. It'll be interesting to see if the problem is just when you're burning to the drive or if it happens when you're reading from it too. The file on the hdd will be accessed in exactly the same way in both Write and Verify modes you see, so that bit is constant. Did you check your intel matrix (raid) driver? I believe the latest version is 8.5 or something.

Yeah a software read will be translated into 2 hardware reads so that the 'striped' data is read off both drives and then returned to the calling application as a normal chunk of data.

How are your drives configured? I'm sure a setup like that must be using SATA but on the off chance that there's some legacy PATA involved that could be where the problem is coming from. PATA never did like 2 drives on the same channel being used at the same time. The use of the burner is probably preventing I/O to the hdds and hence your machine runs like a dog. When you did that test burn in Discovery mode did you find that the machine stayed working just fine? How about if you run hddtune on the hdds at the same time as burning. Do you notice any slowdowns in hdd read or DVD burn speed? I assume you've got the latest intel matrix drivers installed (or whatever applies for your raid setup) ?

So if Verbatims burn in it ok, are you saything that the 'Recording Management Area Information' problem only occurs when you have a certain type/brand of disc in the drive? i.e. You can insert a blank Verbatim and it won't hang/pause as ImgBurn queries the drive to obtain certain info about the disc? I can see from the disc info above that it doesn't appear to have an issue returning this info on a burnt Verbatim disc.

The disc info from the LG drive with burnt DVD-R media would be nice too please. I'm not too fussed about what burnt it.

Your drive returned the error codes consistent with the error 'Write Error' - meaning it had problems writing to the disc. The cause for that can only be related to the drive, its firmware version and the media you're using. If those 3 aren't a good combo you'll get a duff burn - as you did. The most obvious fix is to use better media, hence the reason for the 'Verbatim 2.4x DVD+R DL disc' thread.

Some people really have no idea do they!

Sort out why your machine can't sustain the write buffer for an 8x burn too.

It's not a bug, it's just your machine / drive doesn't do what it's meant to. As has been pointed out, your drive is old and has problems of its own. Commands should either work or be rejected, hanging really isn't my problem and all I end up doing is implementing workarounds for buggy drives. How about the answer to my question from earlier? Back to the empty disc... once it has finally been initialised (even if it takes a few hours), please copy + paste the disc info text from the panel on the right so I can see what the drive is returning and why it doesn't think the disc is empty.

Generally speaking you just Google 'APE DirectShow' and 'FLAC DirectShow' and then install the one from the first result. However, I have no idea if they work with x64 as I've never tried / used it properly. The madFlac one from the guy on Doom9 might be ok and if it's not you can just post in the thread to ask him to fix it.

http://forum.imgburn.com/index.php?showtopic=8000

Check event viewer too, it might show that there are errors on your hdd or something. You can test if it's the hdd by burning a disc in discovery mode - where only memory is used because the data is made up on the fly.

Bring up task manager before you start burning. Is the CPU% usage at 100% all the time during the burn? (which process is using it all up?) If so, it still really seems as though DMA is the problem - regardless of you saying you've checked it or whatever. Did you do your 'fresh install' and then put ImgBurn on BEFORE *anything* else and try it that way?

Do you actually mean 'Getting Disc Recording Management Area Information' ? The text you provided doesn't exist in my code. Can you also please tell me if it does the same thing when you put in a disc you've already burnt?

There are a couple of others about it and they'll say the same thing... No Device drivers are not my area and there are already some excellent freeware utils for this job.

It's not my area and I have no interest in it, sorry.

Being branded by 'Philips' doesn't mean anything, it's the dye that's important and yours are using the 'RITEK-S04-66' one. The best / most compatible one is 'MKM-001-00' and you'll only find that on Verbatim DVD+R DL 2.4x speed discs.

Your drive isn't old at all and I don't know why it's having a problem burning them, it just is. Try burning in safe mode and see if you have the same problem.

You can't cancel it, once the command has been submitted the rest is down to the drive.

The clue is here... Just cancel the verify.

Go through all the other speeds available to you too. These are the ones your drive is supposed to support on that media... If none of them work, you're probably out of luck. Where are those Verbatims made? Look on the box / case / spindle / package. Get some of the 2.4x ones as mentioned in that thread you read earlier.

READ -> http://forum.imgburn.com/index.php?showtopic=8000

Because some of these things just don't work properly! You can disable them, but on some level they're still running. Keep hunting down the problem app, I'll make a mental note of ones that don't play nicely

Do you have any desktop theme type programs running? Something is obviously getting at the exe before any real code (i.e. my stuff) is run and it's bombing out. Normally that's caused by AV (as mentioned earlier) but it could of course include anti spyware, malware, rootkit type utils. Basically anything that works at a very low level and checks programs when they load. You could give decompressing the exe a go (that's what most of these AV type programs don't like), you just need to download UPX and run it with the switch to decompress the imgburn.exe file.