LIGHTNING UK!

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?

As it's not ImgBurn that's actually doing anything here, it's out of my hands. The LeadIn section of the log is made up. I just write the entry for fun really and move onto 'Writing Sectors' once the drive has accepted more data than will fit into its internal cache/buffer. Different Write Types could be a factor here - i.e. SAO/DAO Vs Incremental. Switch ImgBurn to Incremental and see if the time matches Neros. That's not to say I recommend you leave it on that, I just thought you might like to try it.

Then they are probably in use. Which files are you having problems with exactly?

If it's a DVD+RW, you could essentially just use Discovery mode. That'll write zeroes to all the sectors. Note that this wouldn't be the case for DVD-RW media because that requires a proper 'format' command to be issued in order to make the disc 'empty' again.

Where's everyone getting these awful discs from just lately and who's recommending they buy them?! PRINCO are cheap rubbish, invest in some decent 8x ones by Verbatim or Taiyo Yuden.

Fibre is just another form of drive connectivity. It's used by enterprise hard disks and certainly not something an optical drive should be reporting is in use.... and that's down to your drivers. Unless you have an Intel chipset motherboard, don't install any board/controller drivers from the manufacturer. A basic install of XP SP3 should work just fine.

That was years ago, elby stopped selling it and another company started.

Your system is returning total cr** for the sense information. It's not the drive so it must be the nvidia drivers and I have no idea why they do it, sorry. Was there actually a disc in the drive when that 2nd log was created? It's one thing to bugger up the sense data but another to report that the I/O command failed when it didn't. The good news is that I'll be able to install my freshly RMA'd PSU back into my AMD nForce 4 based board tomorrow and see what's up. That said, if you're saying Nero works as-is, you should be able to just copy the wnaspi32.dll file from the nero program folder into the ImgBurn one and tell ImgBurn to use the ASPI I/O interface.

I could and did think of that but it's probably better if it's tested by the person that made the suggestion in the first place.

If you just do the group policy setting, I see no problem with it.