LIGHTNING UK!

It's not my conflict to look into.

TYG02 are my favourite discs

Looks like the same issue to me. Both times the drive errored out with the error 'Peripheral Device Write Fault'. It's just having trouble burning to the disc. Try cleaning the lense with something. If that doesn't work and you have the same problem with another spindle of verbs, you really should consider getting yourself an external drive.

I doubt the 'Platform' (as IsoBuster calls it) is the problem. The values I use for 'OS Class' and 'OS Identifier' (both set to 0) simply mean 'undefined'. Technically, 'Windows 95' (OS Class = 5, OS Identifier = 0) isn't even allowed under UDF 1.02, it's not part of the spec. (page 70 of udf102.pdf)

I don't mind sending you the beta build if you fancy giving that one a go at building your image and seeing if it passes the eclipse tests.

and try to figure out why your machine can't maintain a steady stream of data for burning at 8x. It's not good to be running into buffer recovery all the time.

Now you need to read the 'end of the world' guide.

You follow the double layer dvd video guide in the Guides forum.

Where are the discs from? The ones from Singapore are the best. If your drive won't even burn MKM-001-00 discs without failing then it's probably time to invest in a new external burner - I hate laptop drives with a passion!

That or one that supports RAW mode burning and the type of image file you've got, yes.

Build mode just works with the files and therefore not at a level where subchannel even comes into the equation.

Try some Taiyo Yuden DVD-R 8x (TYG02 dye) instead then.

Ok and 12x, 16x and 20x? I can't believe ASUS would release a drive with firmware so bad that it won't even write to Verbatims! That said, I don't like their DVD-R that much anyway. I'd always take Verbatim DVD+R over their DVD-R any day.

leave redbook and imapi, delete the rest. You are telling it to close - by clicking on the red X.

Yes, DVD Flick or ConvertXtoDVD. btw, you want DVD Video files (IFO/BUP/VOB files), not MPG. I don't know, I'm just the ImgBurn author! Might I suggest you search Google?

Yes I found it a few weeks ago when I was making some other tweaks. How many ImgBurn ISO's do you think you could send that guy to put through his eclipse software before he gets annoyed?! Obviously I'll do everything I possibly can to get a 'PASS' !

Can we see a log from a 8x or 12x burn of the Verbatims please.

Looks like you've just burnt an AVI file... does your player actually support them? (i.e. DivX, XviD etc)

I did notice I was missing a '*' at the start of one of the fields so maybe that's it. It passes the Philips UDF verifier regardless, but it looks more 'correct' when compared to other tools with the * in front of the 'ImgBurn' text (the field is used to show which program created the file system).

As I say, DVD Flick's final output it supposed to be IFO/BUP/VOB files in a DVD Video folder (called 'VIDEO_TS') which then gets burnt with ImgBurn. I don't know where the MPG file comes into it, maybe it's just a temp file.

Nope, it's not how any are seen! They're either ATA, SATA, SCSI or RAID. Fiber is when your drivers are screwed.

DVD Flick doesn't make AVI files, it makes IFO/BUP/VOB files (i.e. DVD Video) - well, ASAIK anyway! If the picture is scrambled then perhaps the source file is encrypted and therefore cannot be converted/burnt to disc. Are you sure the source file isn't locked down by DRM?

I just take 'Access is denied' to mean 'In use', don't read too much into it. Basically it just means anything it's not allowed to open.

Well if it lists the files along with the 'Access Denied' message you can go and check a few of them I guess.

Ok so I've figured out the problem... the nvidia drivers don't/can't handle more than 18 bytes of sense area buffer being made available - at least not when processing the 'TEST UNIT READY' command. ImgBurn allocates 24 bytes for all its I/O and I guess that hits a bug in their code and they don't fill the buffer properly - meaning ImgBurn receives bogus error codes etc. Anyone fancy reporting it to nvidia?