LIGHTNING UK!

These I/O errors are VERY rarely from bugs in the program, but are from your drive (and it's firmware) not supporting the media very well. Usual things to check... 1. You're using decent media. 2. You're using REAL (not fake) media (still decent, as per number 1 !). 3. Your drive is running the latest firmware.

ok, /info and /log have been implemented. Yes, ImgBurn will perform a quick erase when it needs to. The only time it does a 'full' anything is when a dvd+rw is not in the 'Formatted: Yes' state. Thinking about it, the retries only applies to the writing stage. Retrying during verify is pointless as it doesn't then give a true representation of the discs readability. That's kinda why I hadn't made a user configurable 'Retries' option for the verify stage. As for the 'is +RW empty?' stuff, the info in the panel on the right won't really help you there. The only place that shows the discs read/write status (as the program detects it) is in the statusbar. I guess this info would also therefore need to go into that info file? Doesn't the IBG stuff say you can't use it without first running it by me? I'd need to know exactly where/why you're using it. Demos/screenshots of how it'll be used etc.

It was never something I didn't want to do... quite the opposite in fact! The actual task is not a small one, that's why it's taken until now for me to pluck up the courage to do it!

/erase doesn't make it erase, that's automatic anyway if the program decided it needs to. All it does it assume the user clicked 'yes' to the 'This disc needs to be erase / formatted before it can be written to... is that ok?' message box. /retries seems overkill to me. Why not leave it on the default - 20. I don't see why your program would need to change that. /log is do-able. I'll look into it when I get a chance. /info - this would need another file name passed to it. I'm not going to stick it in the normal log. You can only tell if a formatted +rw is empty by guess work really. You have to examine the sectors and see if you can recognise a filesystem. Otherwise, as you say, it always shows 'Status: Complete'

There's a little program you can add to your startup that'll do it - incase you're not already aware of it I think I read about it over at the cdfreaks forum.

Copy + paste the log please so I can see how you have things configured.

I don't see why it would, no. Bad drivers can cause some problems but they don't normally stop the drive from doing everything DVD related! I'd love to hear about the tests they have you perform to see if it can burn DVDs or not - surely they just make you burn something?! There is no other way they could test that functionality. If Dell won't give you a new drive, you'll have to splash out the ?30 or so yourself on a new one.

Sorry, it's undergoing big changes that'll make its release v2.0. The next version may not be around for a few weeks yet - depending on how much time I have to spend on it.

If it's failing on everything, it's probably broken - ignore what the manufacturer says. I've seen a few drives that don't work on DVD but CD still works, they've all been broken and a new drive has not had the same issues. You could always try and borrow a drive from someone and see if that has the same problem (where it was ok in that other persons machine).

Nope, not really. Power calibration errors can only be fixed by firmware updates - as it's a sign that the current one doesn't support the media.

lol ok, gimme my xbox360 I added support for the newer style .dvd files that contain the layerbreak info and relaxed the filesystem checking for large images - as if they're being burnt to dvd, they can only use 1 sector type / size!

Happy Birthday Jmet

lol yeah! Too much 24/7 partying (or it could be work...one of the two )

Nope!

It refuses to burn 'unknown' images. Known images are those containing a filesystem that it understands - i.e. iso9660, joliet, udf. This will be sorted one day.

It's being worked on (bit short on time this week).

Hmm that's a very random error report! As you can read for yourself, it's quite happy responding to the 'test unit ready' command with the correct 'Logical Unit not ready, Operation in progress' sense data for 4 seconds or so, then it just randomly returns 'Power On, Reset, or Bus Device Reset Occurred' sense data. As the drive IS responding to commands, I cannot see why it / the I/O subsystem thinks it has timed out. Not only that, a bus reset would normally mean a slight pause in I/O request. The log shows one was sent straight after the one that failed, and it was processed that same second and returned the correct status. So quite why your machine is behaving in that way is beyond me I'm afraid. Maybe you've got a faulty filter driver installed somewhere along the line and it's giving out bogus status data. Or maybe the BenQ firmware is at fault... who knows. I can only rely on the info my program receives. If I receive errors, I report errors. Simple as that.

Can't you just untick it on the main page? It will save that setting when you exit. Then the next time you load it, it won't be ticked. (side note, that option in the setting isn't to do with turning the entire verify function off It just makes it ONLY read the disc, not read the disc + compare what's read against the image file)

When you consider it to have hung, press the F8 key and see if you can see I/O commands being added to the log. If you can, the program is still working fine.

Things have moved on quite a bit since the 107 days, maybe upgrading your burner WOULD be a good idea too The new 111D is pretty damn cheap.

The old versions never checked for errors during the sync cache / close track commands. So they've probably always been there, just you're only seeing them now. As all of the burns in the drives and media forum were done with this version, I think it's safe to say the initial errors are not bugs in the program (as we never once had an error). That error is worrying though (for you), as it implies the device timed out doing something and so the driver has reset the bus. That's never good! If you don't mind, next time you burn a disc, press F8 before doing so. Then save + upload the entire log when the burn finishes. That would tell me a lot more about what's going on.

UDF error is where the program didn't build the filesystem properly. Miscompare is where the data on the disc doesn't match that of the image. So either the disc messed up or something else is manipulating the data 'on - the - fly' so to speak. Yes, both a bad.

Who knows. Luck? Maybe those 10 were from a slightly different batch. They do get mixed up on spindles too sometimes. You can read loads of stuff on Power Calibration Errors using Google if you're so inclined.

The meaning is that your drive doesn't support those discs. But I'm sure that's fairly obvious by now!

Are you sure you didn't just change to a new spindle of discs or anything? From the tests done for the 'Drives & Media' forum, I found the RITEK-R03-02 ones to be pretty bad. You'd do well to stop using them and go with higher quality media.