LIGHTNING UK!

So if you didn't do anything, you can't have had verify enabled at all. If it failed to start the verify, you'd have had to click the 'stop' button, then accept that you wanted to cancel. I'm sure you'd have remembered doing that

What exactly did happen once it had finished burning then? Did it just go back to the main screen, or did it sit there on the burn progress screen? If it was the latter, the message in the status bar would tell you what's going on. My guess is that after cycling the tray, the drive failed to initialise the disc again and so the program just sat there waiting for it to become ready - which would never happen unless you eject + reinsert the disc. That bit is actually automated (for max 3 times), depending on the error returned by the drive when it failed to intialise properly. The log you've attached there obviously wasn't the one where you had the problem as it burnt + verified ok!

I would guess it depends on what exactly you mean by 'backup prog' (i.e. are we talking Nero or Veritas BackupExec?!). If it's the latter, I very much doubt it would be making a normal ISO image - in which case ImgBurn wouldn't burn it at all due to the lack of a recognised filesystem. There is currently no method of burning unrocognised images, just by specifying sector size of the unknown image etc. That is something I will no doubt sort out later on.

If you notice that it doesn't ask to erase when it should, take a copy of all the info in the panel on the right and forward it onto me please

Sorry db, I think you're on your own on this one. I just put a burnt cdrw in the drive and the program correctly says 'Ready (Disc Needs Erasing)' in the status bar. Then once I'd selected my image and clicked 'Write', it said: "This disc needs to be erased before you can write to it. Would you like to erase it now?" with Yes / No options. If your drive didn't initially detect the disc as erasable (or where Current Profile = CDRW), that might explain it. The feature to erase CDRW automatically is there if everything else is working ok.

Get a couple of each... that's what I always do!

Something so simple as that should already be in there.... let me check and see why it's not working for you.

Tried it again, deffo works here. The log clearly shows 'Exporting Graph Data...' after the Write operation and then again after the Verify one. DVDInfoPro 4.610 shows both lines as it should do.

It should save after the write, and then again after the verify (overwriting the other one). On both occassions it'll be written into the log that his has happened. A quick look at the code shows it 'should' work ok... I'm checking CLI flag in both places. Will do a test run and step through the relevant code to see what's up. Cheers btw, please forgive me for CLI related problems, I never use it and so never find them! EDIT: First test stepping through worked fine. Any chance you could give me a typical example of the FULL line of CLI parameters that it's failing with?

lol 4th million post about this feature! It's being worked on.

Just wondering if that was another brand new disc or one you'd tried to format on your BTC drive? If it was the latter, maybe the BTC screwed it up and that's why it failed first time?!

No, they're not preformatted. Don't confuse them with floppy discs! I've made imgburn get the disc into the real formatted state before it just allows direct overwrite, that's all. It's totally down to the programmer if you leave it in limbo or not, I chose not to. You should always do one full format in a program that waits for the background part of the format process to finish (i.e. ImgBurn), or set it going and then wait 15 - 20 mins in a program that doesn't. Only then will they really register as being fully formatted. During the background format process, the drive will probably NOT appear to be doing anything. Some may flash the led once in a blue moon but again, that's down to whoever makes them and each drive is different.

I just wrote some data to one of my +RW's, then erased it again. No problem with the statusbar line my end. It correctly registers as just 'Ready' rather than 'Ready (Disc Not Empty)'. I 12:34:53 Operation Started! I 12:34:53 Device: [2:1:0] _NEC DVD_RW ND-4571A 1-01 (J:) (ATA) I 12:34:53 Media Type: DVD+RW (Disc ID: RICOHJPN-W11-01) (Speeds: 2.4x, 4x) I 12:34:53 Quick Erase: No I 12:34:53 Erasing Disc... I 12:49:21 Operation Successfully Completed! - Duration: 00:14:27 I'm actually not a huge fan of verbatim +RW discs. Had too many occassions where they just didn't initialise in the drive properly - even after just burning them. The verify would fail because the drive never became 'ready' again after cycling the tray. No such problems with the Ricoh ones so far.

They lie to you! A quick erase on such media is just a 'Write' of the first 500 - 800 sectors with a bunch of zeroes. You can't 'Write' to a brand new +RW without formatting it, that's just the way they work. If you try, the drive will error out. All those programs are doing is starting off a full format but not waiting for the background part of it to finish - hence the format is actually left in limbo and your disc never reaches the 'Formatted: Yes' state like it should do. As I've said many many times, you should only need to do a full format once (to get it in that 'Formatted: Yes' state - as reported in info window on the right) and then you can just overwrite the data on it each time.

It should do that anyway shamus. It would appear your format isn't erasing the data on the disc properly or something. Straight after a full format, all sectors should have been put back to 'zero'. Your discs still have a filesystem on and that's why they're showing as 'disc not empty'. As DVD+RW uses direct overwrite, don't see this as a huge problem, it's not.

Try updating the drives firmware too. http://forum.rpc1.org/dl_firmware.php?download_id=2110

It lies. That's just the foreground part, not a full format (which also includes the background part) - or it's mearly erasing, which is just burning nothing to the first 500 or so sectors. I think yours is stuck on the background bit - like I said, you can tell ImgBurn not to wait for background format, but it'll still then ask you to format the disc every time you try to burn - hardly ideal EDIT: DOH! Hadn't moved onto page 2 when I posted and didn't see your reply shamus Now I've also seen your other post terrypin, you'd do well to give up on that drive and wait for your new one to turn up!

You could just read the install dir from the registry - or the gui person could. HKEY_CURRENT_USER\Software\ImgBurn\ Name = 'InstallDirectory' Take that and stick a '\ImgBurn.exe' on the end of it

ImgBurn will soon have ISO building capabilities too - but it won't be aimed at building special XBox ISO's or anything!

In theory, you could just pass the normal .dvd file via the /SOURCE CLI parameter, and also use the /LAYERBREAK CLI parameter. Of course that doesn't help if you're not running/calling ImgBurn from within your own program!

I was actually the one who started CloneCD using .DVD files. Trouble is, I then progressed onto MDS and it stuck with .DVD. Back then, DL weren't around and so there was never a need for the layerbreak value to be put in the file. I will look into adding support for this newer type of .DVD file and it'll be in the next release. Oh and you guess correctly, I can't give out the MDS file format info

Your HP firmware dates back to 22/10/2004. http://h10025.www1.hp.com/ewfrf/wc/generic...item=pv-25114-1 You'd probably benefit from updating it with the much newer 'real' liteon firmware, dated 22/03/2006 http://www.liteonit.com/DOWNLOADS/ODD/SOHW...are/DR8VS0M.zip You may however need to perform a degree of 'crossflashing' to update it. The people over at cdfreaks will help you with that. Just look in their LiteOn forum.

You need to use PgcEdit to create your disc image if it's a double layer one. ImgTools Classic isn't really right for that job.

Erm... because it's new (ish), free and hasn't gotten that far yet

Would I be right in thinking this GD-ROM image would have the audio track at the start etc? The start of the file looks a right mess! As mentioned above, ImgBurn only supports basic single session, single track images.