LIGHTNING UK!

Power on / bus resets are never a good thing. The disc verified ok though so I doubt there's any problem with it. Visit www.bustrace.com and find the filter driver load order 'free' utility on the site. Run it, select your plextor drive and then copy + paste what it say for filter drivers loaded on your PC. Maybe there's another old one that's messing things up.

It's a shame media player does what it does but I guess it has it's reasons. You'd kind expect it to just keep a handle open to the optical drives when it's actually playing a CD - but that's not the case, it keeps them open even when you're playing MP3's etc. I assume media player 11 is the same? Anyone tried it?

No, that's totally unrelated. As far as the OS is concerned, as soon as you open Media Player, all your optical drives are 'in use'.

Don't worry about the ISO / MDS file stuff, ImgBurn is clever enough to take care of it - and it certainly would just attempt to burn a 9k file! The MDS (NOT MD5, that's TOTALLY different!) file is just used to provide ImgBurn a little more info about the ISO file. In this case, it's needed so that the layer break is in the correct place. Without the MDS file ImgBurn has no way of knowing where it's supposed to be, hence the MDS is very important.

Use Joliet instead of UDF. There was a problem with my UDF implementation on old Win9x based OS's that didn't/doesn't show up under XP etc. That has been fixed for the next version (it was fixed a couple of months ago in 'beta' versions - which of course you don't have access to, sorry!).

I probably wouldn't have bothered installing the 'Intel Application Accelerator Driver'. There's been a long standing issue with it doing weird things. The standard Microsoft drivers are fine. Looks like you've got a mixture of 'ForceASPI' and Adaptecs real ASPI installed there. Again, I wouldn't have bothered. No modern software uses ASPI (MS did away with it from the base install of the OS for a reason!) and any that do still require it can use something like FrogASPI - which is an SPTI wrapper (or Nero's WNASPI32.DLL which I believe does the same thing).

The errors are just what your drive reports, I can't do anything about them. Very rarely do I see a drive showing as '(ATAPI)', you might want to check your motherboard / ide drivers. 99% of the time it says '(ATA)'. If it's on a 3rd party controller card the drive would show up as '(SCSI)'. God knows what makes it show up as '(ATAPI)' - but it's certainly not 'normal'.

Samsung's bitsetting commands suck. I've done my best with them and they work ok on the one and only samsung drive I have (not that model). No others have been tested. You have to do the bitsetting every time you burn with a samsung. So bitset, then burn.

Sorry, your drive isn't supported at this time. I'll try and tweak it so the next version might work ok.

They can look them up for you again if you provide them with your name, email address etc. Failing that, it's in the registry somewhere.

What's the typical format for these things (assuming you've used them before!) ? Using the OS's 'Short Date' format (from the regional settings), is it date first then time, or vice versa? i.e. HHMMSS_DDMMYYYY or DDMMYYYY_HHMMSS

That's not at all difficult, except for the fact that there's just not very much room for such things! I could put one on the auto generate volume label window though - the window that comes up when you don't specify a volume label in the main one.

If you hit 'yes', you won't have a proper layer break. You NEED to rebuild that image so that it's compliant with the DVD specs regarding layer break positioning.

Pass, can't you refer back to the email you were sent containing the serial number?

Looks like a duff disc to me. That's not to say I'd overspeed 2.4x media to 8x anyway. Being the price they are, I'd rather leave the machine a little longer and let it burn at the media's rated speed.

It could be something else on the bus that's stopping data from getting to the drive - especially if the pioneer is the slave device. Burn something and look at the write speed graph data via DVDInfoPro. Perhaps post up a screenshot or something so we can look too. Post the normal log too while you're at it please.

WMP11 probably uses the IMAPI service for burning so you have to make sure that's enabled. It might also decide it's not a burner because it won't accept the commands a burner should do - i.e. the 'Set Write Parameters' one!

It would appear your drive doesn't support the media you're using. As suggested by polopony, check for and update your drives firmware. If there are no updates available or that doesn't work, buy some different discs.

If it burns and verifies, the disc is ok in the burner. Decent discs (Verbatims and Taiyo Yudens) work in more players / other machines than cheaper stuff. This is not the place to discuss xbox issues so please don't.

Be warned, unless the drive supports the 'DVD+R - EEPROM' option, that bitsetting setting will reset itself back to DVD+R every time you reboot the PC or the drive loses power.

Like corny said, you should be on A106.

You might not have a DVD burner, just a DVDROM and a CDRW burner. If that's the case, you're out of luck.

I think it does support it. When in Write mode within ImgBurn, click on the little 'Book' icon down the bottom right. Then switch to the LiteOn tab and try the DVD+R options, setting it to use DVDROM as the new setting. If it works and you get a 'Successful' message, the next DVD+R disc you burn should come out with its booktype set to DVDROM.

ImgBurn only handles data images, not audio ones. Try something like Burrrn for audio.

Why do you think it's lost the ability to see your burner for what it is? Because it says 'CdRom' in device manager? It always does that, all mine on my ITE card say the same thing.