LIGHTNING UK!

....and that's why the program has the option to check for updates automatically. You've obviously not done it manually since April, or even looked at the website!

Indeed they would have, but not now I guess after all the sh*t they went though

I guess I could add a /SRCLIST one to accept a text file.

Did you have 'Test Mode' enabled? If so, uncheck it and try again. Have ImgBurn verify the burn too and if you get problems after that, copy + paste everything from the log window.

Add a pipe ('|') between them or use an IBB file.

I don't know about kvcd but a (s)vcd has 2 tracks and you can't make them when you only have the bin file. You need the CUE too. Even then, 2.3.2.0 can't handle multiple track or CUE files so you're stuck either way.

Press F8, then Tools -> Search for.... Save the log and upload it (or copy + paste)

There was once a version someone made that called ImgBurn instead. No doubt if you search Google you'll find it somewhere.

Yup, the problem lies with the DVD-ROM (Pioneer DVD-127) I can't work out if there are any updates for it either - everything Google returns is in Chinese If we look at the log, we can see it accepts some of the 'GET CONFIGURATION' command but then stops dead on this last one. (See, it does the first ok (46 02 00 1D), but not the second (46 02 00 1E). It's quite rare for a drive to do that. Anyway, as blu pointed out, the drives say they're on a 'SCSI' type controller. Obviously it's not a real SCSI card but an interface with a driver making it look/work like one. I can only assume you've got a new motherboard without a decent on-chip IDE port and so are having to use the 3rd party Jmicron one - or whatever else they've stuck on it. That's to be avoided at all cost really and if you do need to put them on it, ensure you're using the Microsoft drivers (which shouldn't make it look like a 'SCSI' one) or use the latest from that 3rd party (so it fixes bugs - but even then it may never work). At the moment though, if you want ImgBurn to work you need to disable the pioneer dvd-127 in device manager.

It only works on CD's and DVD- (minus) format media. Basically it's where the laser isn't running at full power and doesn't actually burn anything to the disc. You might also know it as 'simulation' mode.

Unless you can find some sort of driver update, I'd probably give up with that card and try to find another one that doesn't use the NEC chipset. eBay is great for that kind of thing, you can pick them up for like £5 -£10.

Hard to know where the problem lies without you doing a bit more testing. Can you read discs faster than 0.2x? You might have massive firewire issues where all the commands are failing, i've seen that before on someone's PC. You might be able to find a hotfix or something for it from Microsoft. Even a motherboard bios update could do the trick (assuming the firewire is built onto it?).

DVD-RAM is a totally different format of media - in the same way you get DVD+R and DVD-R.

It's normally something on the sidebar - or media player (but that would be obvious!).

No probs, I'll still be here when you get back from work! Oh and yes, you can just burn from the files that have already been created, no need to run DVDFlick again (I don't think!).

The word 'detecting' doesn't exist in ImgBurn's source code. Could you please provide the real message. A screenshot of the main app window would be nice too, along with a copy + paste job of the text in the log window (open it via the 'View' menu if you've closed it - and then leave it open in future!)

What was the 'source' of the disc - an original DVD? ImgBurn cannot copy original copy protected discs.

ImgBurn doesn't have any drivers, it's an exe, a text file an a couple of wav files - that's it! Take a look at the system using Process Explorer (google it). It might show you a bit more info.

crossflash to a 1633, then you can run the real 1633 firmware updates direct from liteon. The cdfreaks forum will have this covered, take a stroll over there.

Update ImgBurn too.

lol I know the RAID volume is your hard disc, but in the MB BIOS, you either have 'ATA', 'RAID' or 'AHCI' - and that's for the entire controller (i.e. all 6 ports). You can't run a RAID volume if you're in ATA mode, hence you can't be in it. Don't ever go by the ASUS site for Intel drivers, get them direct from Intel. The Matrix one is from here: http://support.intel.com/support/chipsets/imsm/ The Chipset one is from here: http://www.intel.com/support/chipsets/inf/ As mentioned earlier, only the 1.22 Pioneer firmware supported that media dye properly (even then it's not perfect!) so if Plextor's 1.00 firmware isn't based on that, you need to be using different media.

The only way to get that info is to load each disc into the drive one by one. Obviously that takes aaaaagggeeeees.

You've got an 'Intel Raid 0 Volume' listed in your screenshot, so I can only assume it's NOT in the standard (S)ATA mode. The drive would also probably be listed as (ATA) rather than (ATAPI)... but I couldn't be 100% sure on that. btw, 'AUTO' write speed doesn't mean anything if you've not configured the 'Automatic Write Speed' settings - look in the Guides forum.

Use Verbatim DL media, your drive doesn't appear to like those.

Ah ok, you've got it connected to the ICH9R controller by the looks of it - rather than the jmicron one or whatever else they also implement. I avoided using RAID (or AHCI) on my P35 based board because drives seem to prefer just being on a normal (S)ATA controller. Since you're using AHCI, make sure you keep your motherboard bios and the Intel Matrix driver up-to-date.