LIGHTNING UK!

Are you sure your source image is correct? Have you done an MD5 check on it against wherever you downloaded it from? It could just be a corrupt download (or corrupt in the first place?!)

I've hidden the error message about the DeviceIoControl functions failing at startup (because wine doesn't yet support the IOCTL) but I've noticed the drive drop down comboboxes are too big and so cover up (a little of) what's below them. Also, for some reason, the splash screen image doesn't draw itself properly (nor does the enlarged / bold text - but that's common to all parts of the program using big text) Oh and it could just be me but the main window won't let any non 'Modal' windows come in front of it in the z-order - i.e. the 'Log' one, 'Automatic Write Speed' one or the 'ImgBurn Queue' one. The main 'ImgBurn' window is always visible over the top of them.

Did you not just click the 'Delete' option within the 'Filter Driver Load Order' screen? If it's just not burning DVDs of any kind, maybe the DVD burning part of the drive has messed up - is it still under warranty?

It's purely a CLI argument and none of those are mentioned within the GUI - nor will they be I'm afraid. Ini's are a pain when it comes to program updates and so I actually prefer it when people don't use them.

Yeah, the chipset inf installation util is the one you want. You should probably also have a version (old one now probably as new ones don't support i875 chipset) of the matrix storage driver. You should then check your filter drivers as one of those (silicon image, if it's installed) messes this function up.

Did you run chkdsk / check the hdd for errors? That's where your problem is coming from. You should also get the BY02 firmware and update your drive. http://forum.rpc1.org/dl_firmware.php?download_id=1917 And finally... don't waste your money on Ritek DL media. Verbatim DVD+R DL is a million times better and actually works!

How the hell did that happen?! It won't work because it didn't burn the LB position properly - because your drive didn't report the disc type. It actually looks to me as if the drive is ignoring most of the commands it's being sent - it didn't burn at the requested 2.4x either. Flash the firmware to 1.29 again and keep an eye on it to make sure it says 'successful' this time.

If your drive can't even keep up with 2.4x write speed, something must be wrong. Humour me and just follow the post in the FAQ about resetting DMA anyway. I'm not overly fond of the media you're using (nor might your drive be), but that's your decision to make.

The tool is called 'ImgBurn' - by definition it's for burning disc images. 'Write' mode is for burning existing images, it won't let you burn anything else. 'Build' mode is for you don't have an image file, but instead need to create / build one from random (non image) files that you have on your hdd. It you think about it logically, it actually makes perfect sense. If you're burning an image file, it would already be bootable / not bootable so that doesn't really come into the equation. There are guides for people who don't know what they're doing, there's not much more we can do.

Your drive just isn't burning nicely to those discs (or the basic read feature is messed up) Check for firmware updates and try some different discs - with a different MID - we recommend Verbatim (MCC dye) and Taiyo Yuden. Seeing as how you've got a BenQ, why not do a PIPO scan in DVDInfoPro (or Disc Quality scan in CD-DVD Speed) and see what the burn quality is like on those discs you're using?

That all depends on how you like to work. I personally have no need for multisession and actually don't like it much. If I want to burn something, I'll burn enough to fill a disc or burn to a rewritable. If I need to add more, I'll just burn it all again - but then it's my own fault for not remembering that extra bit in the first place. If I can't wait the extra few mins to burn the disc again (CDs/DVDs are for archival purposes so there should never be a rush), I'd use a memory stick - in fact, I almost always use a memory stick over cd/dvd. So in short, I don't know when (if ever) it'll be implemented. Sorry.

Look in the readme file.

No it's not and hasn't been since v2.0.0.0 added support for reading it from the .DVD file. Just burn a disc and verify it (using 2.2 of course) and then post a 'Disc Quality / PIPO' scan. Of course you should also post the full log. I've done a few more since your initial post and they've all been fine. Seriously, whatever the issue is, it's not the software. I bet if you compared the burn at a 'commands sent to the drive' level, both versions would be identical. As I said before, all the program does is send data to the drive, it's hardly difficult and there's very little room for error. If your drive is producing duff burns, thats nothing to do with the program - and I'm not just saying that because ImgBurn is my program, I'm saying because it's the truth.

It uses v1.02 - the standard for DVD Video discs.

Cool, thanks for letting us know

2.2.0.0 actually issues a warning for that - unless you're doing something really odd.

It's just the stuff in the MMC specs. www.t10.org

These things deteriorate over time... nothing lasts forever! Resetting DMA (as per the FAQ) can help out in certain situations. Updating the firmware, resetting DMA and using decent media are the 3 easy things to do when stuff starts going wrong. If you do those and it still doesn't work, you need to start looking at general hardware problems.

99.99% of the time, an I/O Error is a drive / media / firmware issue. The drive reports the errors, ImgBurn simply displays them.

Sounds like you've got an error on your hdd. Run chkdsk on it from a command prompt window EDIT: Snap!

Sorry, what does it say when you try to write to them? Even if it does think there's data on them, it should just offer to overwrite it. If it's not saying that, what is it saying? Any chance of a screenshot (or a log if it shows anything) ?

If you don't use B's Recorder gold, ditch (delete) the cdrbsdrv one. Likewise with dvd43llh. PxHelp20 is fine.

Your drive seems to have reset itself - that's not a good thing! Previously, your errors were coming from the 'Verify' stage. That is to say, the drive burnt the disc but them couldn't read it back - meaning it had produced a bad burn. You tend to get that on discs the drive doesn't like or just on discs that are useless anyway. Try and find some Verbatim (MCC dye) or Taiyo Yuden discs. They're much better quality than the ones you're currently using (RICOHJPN-R03-04).

Nothing on your PC should make the drive error out... after all, it's a bit of hardware. When it's burning to a disc, there's just it and the disc - nothing should be able to interfere with that. In case you've got some dodgy filter drivers installed, click 'Tools' -> 'Filter Driver Load Order'. Then hit the 'Clipboard' button and 'Paste' into a reply message so we can see what's installed on your pc. Are you sure these are the exact same discs your drive has worked with in the past? That is to say you've not just moved onto a new spindle or whatever and you've not just updated the drives firmware? There is clearly something it doesn't like about them, you just need to figure out what it is.

Do you have a log file? You might have DMA problems, in which case, just follow the post in the FAQ.