LIGHTNING UK!

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.

Change 'Output' to 'Image File' when you're in Build mode.

Why would you WANT to use media that you've been told is rubbish? Do you have so many of them that you can't write them off?

The whole thing comes down to the drive/firmware/media. If the 3 aren't a good combo you get problems like yours. 'RITEK-F16-01' is the dye your discs use. The brand name is not important, the dye is. The problem is nothing to do with the software.

Generally you just leave it on SPTI. There's no way to have everyone use a default bunch of settings without forcing the program to load from (and use) an INI file. I guess I could make ImgBurn use any that exist in HKLM if the set under HKCU aren't present. You could always add a HKCU default set in a login script?

OMG you're making such a deal about this! I'll add the same options to verify mode that read mode has in terms of handing read errors. Now please quit your whingeing. EDIT: I might have to get you to test it... I don't ever have any discs that fail to verify due to read errors.

No, ImgBurn is a burning tool. It's an advanced version of DVD Decrypter's 'Write' mode.

'RITEK-F16-01' are rubbish, buy some better discs. Get Verbatim or Taiyo Yuden. Get the 8x stuff because your drive is old and won't support newer 16x discs properly.

The brand name doesn't mean anything. It's the dye that's important and they use 'CMC MAG. AM3'. CMC is pretty awful. You'd be much better off buying Verbatim or Taiyo Yuden.

You're using cheap media the your drive can't read/burn properly.

Although the first track should be Mode2/Form1 I guess that's changing and that's why you're getting the error. I honestly don't know as I've never tried reading a playstation game.

Ok so delete the 'MediaType' line.

Because CDR just burn better and can be read afterwards by more drives. The problem you're having is that the CDRW burns ok but the burn quality is so low that the drive cannot then read it back. If the drive that wrote it 2 mins before can't read it, what chance do other drives have?!

Look at the disc with IsoBuster or something. You'll soon know if there's anything on the disc.

Those 90/100 minute cds still report all the disc info as if they were a standard 80 minute one. So just 'continue anyway'.

If you reset the settings they stay put. If you uninstall they get wiped.

Use a CDR not a CDRW.

Ports 5 and 6 on the intel chipset would be the most likely to work of any. I believe some boards let you have RAID for the first 4 and ATA for 5 and 6. The weird name controller is DAEMON Tools or Alcohol 120% etc. jmicron drivers can be found here ftp://driver.jmicron.com.tw/jmb36x/Win2k_xp_Vista/

None of that is anything to do with AWS, it's because you reset the settings or uninstalled / reinstalled and those are the new 'default' settings for 2.4.2.0 or whatever you're using.