LIGHTNING UK!

nvidia drivers are the cause of most problems Leave the write type on DAO rather than incremental.

The wnaspi32.dll just needs to be in the ImgBurn program folder. You shouldn't make it system wide really.

That's not my area. Stick with Virtual CloneDrive or DT, they do a much better job than I could do.

Give the Nero WNASPI32.DLL a shot along with changing the I/O interface to ASPI.

It certainly wouldn't do any harm to try it. It'll either work or it won't.

Surely 2.1B is newer? http://www.firmwarehq.com/NEC/ND-3500/files.html

The data is probably all physically there, just the TOC might not have been updated properly due to the error during finalisation - as such, some drives might have a problem recognising the disc and correctly reporting its size/layout etc.

They're only supported up to 8x on your burner.... and the CMC dye really isn't all that good.

Post a copy of the log please. We need actual details rather than just what you can remember.

http://www.firmwarehq.com/download_1028-fi...c_QS12.EXE.html Try that firmware update. The 'MKM-001-00' dye you're using is the best you can get for DL media so if it won't even burn those properly, you know you're in trouble. 'write errors' are certainly not normal and so basically your drive is having trouble finalising the disc. Looking at it, it seems to be quite an old model now... perhaps you should invest in a new one.

Windows 7 - x86 - Build 7000 I 22:48:18 ImgBurn Version 2.4.2.11 Beta started!I 22:48:18 Microsoft Windows 7 Ultimate Edition (6.1, Build 7000) I 22:48:18 Total Physical Memory: 1,047,332 KB - Available: 697,540 KB I 22:48:18 Initialising SPTI... I 22:48:18 Searching for SCSI / ATAPI devices... I 22:48:18 Found 1 DVD

I don't think there's anything odd going on here.... everything looks perfectly normal to me with regards to higher error rates on the 2nd layer.

When you try 7048, please do make sure ImgBurn is the first and only thing you put on after the basic OS install.

These will (both?) apply to you then. http://www.intel.com/support/chipsets/inf/ http://support.intel.com/support/chipsets/imsm/

I'd like to see the log when the drive is connected properly to the Intel PATA controller via a nice 80 wire cable with the drive set to 'master' and positioned at the end of the cable.

What does the PIPO graph look like if you scan at 4x? Also, switch to 'Block' rather than 'Line' for 'Show PIE' and 'Show PIF'. Have you tried burning at the other 'Supported' write speeds?

Your system is reporting that the drive is on a 1394 (firewire) interface?! Something isn't quite right there... you might want to double check the drivers are all working properly. I've tried builds 7000 and 7048 via vmware and it's been fine for me.

The OS doesn't really come into it. ImgBurn sends an I/O command to the drive, the drive processes it and returns either 'success' or 'failure'... or at least that's how it's supposed to work. For whatever reason, yours has got stuck and then 1.5 hours later the command has 'timed out' - resulting in a bus reset. Issues like this are likely to be caused by dodgy drivers more than anything else. What controller does your motherboard use?

Your system is messing up the error codes and that's why it's not working as it should do. Is your drive on an nvidia controller by any chance?

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

The discs in your original post were DVD+R, these are DVD-R. If your drive only supports 8x burning, you might be better off buying 8x discs - Taiyo Yuden TYG02 are about the best you'll get (I use them all the time). Of course the other option is to forget your internal drive exists and get yourself a new external drive (or internal drive in an external case).

Can you copy + paste the disc info from the panel on the right when you're in Write mode please.

It might not even be protection.. it might just be a scratch / dirt on the disc that's preventing your drive from reading it. (I don't recall if PS2 DVD's had intentional bad sectors on them)

memtest tests your ram. If you had lots of errors listed in memtest, yes it's your ram! Yes, it's your ram issues that are causing the miscompares. In fact, your machine should be very unstable in general... how have you not noticed it before now? apps must be crashing left, right and center.

Wrong ASPI. Take that one off again and just use the nero aspi dll as mentioned in an earlier post.