ImgBurn ejects disc before verify

[Thomas_AR]

I am using IB also to burn images on commons CD's. If i activate the option 'verify' after burn, IB is ejecting the burned dics before verifying it. Inserting the disc and starting veryfing, results directly in an error message. Doesn't happen with Nero.

 

Using Windows XP2 on Sony Vaio Laptop with QSI CDRW/DVD SBW242C Drive.

What more input you need for solving this problem?

Edited January 7, 2006 by Thomas_AR

[LIGHTNING UK!]

The error message itself would be handy!

 

Also, a copy of the log.

 

You can turn that specific eject off, but that's besides the point here if it's erroring out. It shouldn't error out

[Thomas_AR]

I will burn some images later this weekend. Will post the log and a screenshot of the error message.

Edited January 7, 2006 by Thomas_AR

[LIGHTNING UK!]

Thank you

[Qyngali]

I almost always get a time out warning of sorts, that it's waiting for the disc to be recogniced. I'm guessing that's what he's seeing. Sorry I can't remember the excact wording... in any case it's nothing to worry about.

 

Of course if the verify fails for the OP it's a different problem.

[LIGHTNING UK!]

There is no timeout associated with verify. Any timeout error you see is probably coming from a driver issue.

 

We used to see a lot of them when people had drives in external cases.

[Qyngali]

Sorry for the confusion, I was wrong. I'm getting a yellow...something (how descriptive), and it just says waiting for the drive to become available (IIRC, ugh).

 

Doesn't really matter though, as I'm sure it's not a bug or problem at all. The verify finishes without any issues.

Edited January 11, 2006 by Qyngali

[LIGHTNING UK!]

That yellow one says 'Waiting for device to become ready...'.

 

It's just telling you what's going on and is supposed to be there.

 

Nothing to worry about at all.

[Thomas_AR]

Hi folks, after nearl 9 months i am back on IMGBurn, but still with the same problem. The conditions are the same. IMGBurn 2.1 is still ejcting the CD before Verifying. Did not happen with Nero.

Here the latest log:

 

I 09:26:45 ImgBurn Version 2.1.0.0 started!

I 09:26:45 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

I 09:26:45 Initialising SPTI...

I 09:26:45 Searching for SCSI / ATAPI devices...

I 09:26:45 Found 1 DVD-ROM/CD-RW!

I 09:27:44 Operation Started!

I 09:27:44 Source File: D:\Microsoft Windows XP Home Edition SP2\Microsoft Windows XP Home Edition SP2.iso

I 09:27:44 Source File Sectors: 274,743 (MODE1/2048)

I 09:27:44 Source File Size: 562,673,664 bytes

I 09:27:44 Source File Volume Identifier: WX2HOEM_EN

I 09:27:44 Source File Application Identifier: CDIMAGE 2.47 (10/12/2000 TM)

I 09:27:44 Source File File System(s): ISO9660 (Bootable)

I 09:27:44 Destination Device: [1:0:0] QSI CDRW/DVD SBW242C US85 (F:) (ATA)

I 09:27:44 Destination Media Type: CD-R

I 09:27:44 Destination Media Sectors: 359,844

I 09:27:44 Write Mode: CD

I 09:27:44 Write Type: SAO

I 09:27:44 Write Speed: MAX

I 09:27:44 Test Mode: No

I 09:27:44 BURN-Proof: Enabled

I 09:27:45 Filling Buffer...

I 09:27:46 Writing LeadIn...

I 09:28:19 Writing Image...

I 09:33:01 Synchronising Cache...

I 09:33:24 Image MD5: d8a3198c4cfb10f3af78991680cb5332

I 09:33:24 Operation Successfully Completed! - Duration: 00:05:39

I 09:33:24 Average Write Rate: 1,955 KB/s (13.0x) - Maximum Write Rate: 3,040 KB/s (20.3x)

I 09:33:24 Cycling Tray before Verify...HERE THE CD IS EJECTET!

W 09:33:28 Waiting for device to become ready...

I 09:33:42 Device Ready!

I 09:33:43 Operation Started!

I 09:33:43 Source Device: [1:0:0] QSI CDRW/DVD SBW242C US85 (F:) (ATA)

I 09:33:43 Source Media Type: CD-R

I 09:33:43 Image File: D:\Microsoft Windows XP Home Edition SP2\Microsoft Windows XP Home Edition SP2.iso

I 09:33:43 Image File Sectors: 274,743 (MODE1/2048)

I 09:33:43 Image File Size: 562,673,664 bytes

I 09:33:43 Image File Volume Identifier: WX2HOEM_EN

I 09:33:43 Image File Application Identifier: CDIMAGE 2.47 (10/12/2000 TM)

I 09:33:43 Image File File System(s): ISO9660 (Bootable)

I 09:33:43 Verifying Sectors...

I 09:37:15 Device MD5: d8a3198c4cfb10f3af78991680cb5332

I 09:37:15 Image MD5: d8a3198c4cfb10f3af78991680cb5332

I 09:37:15 Operation Successfully Completed! - Duration: 00:03:32

I 09:37:15 Average Verify Rate: 2,591 KB/s (17.3x) - Maximum Verify Rate: 3,520 KB/s (23.5x)

 

I used the standard configuration of IMGBurn, no changes made. Some idea?

[LIGHTNING UK!]

As mentioned in the 2nd post in this thread, just turn the option off if you don't want it to eject between write/verify on your laptop.

 

Tools -> Settings -> Write -> 'Cycle tray before verify'.

 

You'd advised to leave it on though because it's the only way to *properly* test that the drive can re-initialise the disc and read back what it just wrote.

[Thomas_AR]

Thanks, but shouldn't be there an other solution, because it's the only way to *properly* test that the drive can re-initialise the disc and read back what it just wrote.

Strange, that this not happenes with Nero,no?

Edited September 25, 2006 by Thomas_AR

[Shamus_McFartfinger]

Thomas, ejecting the disk before verifying it gives your drive the best possible chance of finding potential errors with your burn. Just because Nero doesn't eject the media before verifying doesn't mean that's the right way to do it.

[Thomas_AR]

Thomas, ejecting the disk before verifying it gives your drive the best possible chance of finding potential errors with your burn. Just because Nero doesn't eject the media before verifying doesn't mean that's the right way to do it.

AHHH!! Did not knew that. So that's the default behaviour? Learned something again.

Edited September 25, 2006 by Thomas_AR

[kevdriver]

Thomas AR, This is the way to properly verify a disc, eject it and reload it which starts a freash, clean read of the disc. Nero is a different program and is written different from Imgburn. Neros arthor just has it verify directly after a burn without ejecting the disc. You have an option in Imgburn to do this as well, although, I personally don't reccommend it. Whats a few seconds more knowing you'll get a accurrate verify of what you've burn't.

[Shamus_McFartfinger]

Ejecting the media refreshes the drive. When the disk is ejected and re-inserted, the drive is forced to re-read the data on it. Imgburn is then better able to compare the source and destination data and also check readability of your freshly burned disk. I hope this clears it up a bit.

[Thomas_AR]

Thanks folks, logical and for that the better way. Some seconds mean nothing if it results in a correct verify.

[kevdriver]