DVD to DVD Error=100

[hanschiu]

I sent a message to customer support and never received a response.

Everytime I burn a DVD and ask it to verify the disk I get the following error:

16:26:41: Analyzing of DVD started
16:26:51: Analyzing of DVD completed successfully
16:26:51: Copy process started
16:57:48: Copy process completed successfully
20:18:18: Burn DVD folder (C:\Documents and Settings\Han\Desktop\Temp\Temp\FullDisc\BRIDGES_OF _MADISON_COUNTY\) started
20:54:31: Burn DVD completed successfully
20:55:12: Verify DVD started
20:55:16: Task_3 failed! Error=100



Oddly enough the DVD seems to burn and work just fine. I am using version 6.0.6 and I am burning onto TDK +R media using a Toshiba Tecra M5 with a +/- RW read right drive. The error occurs every single time without fail.

Here are the other log files:
DVDFab 6.0.6.0

0m 35.98s: detected dvd
0m 36.03s: drive D
0m 36.03s: video dvd 1
0m 36.03s: volume label BRIDGES_OF_MADISON_COUNTY
0m 38.92s: got copyright 1 f0
0m 39.53s: got udf/iso
0m 41.70s: got discinfo
1m 05.67s: got dvdinfo
233m 00.32s: detected dvd
233m 00.48s: drive D
233m 00.48s: video dvd 0
233m 00.48s: volume label
269m 53.18s: detected dvd
269m 53.43s: drive D
269m 53.43s: video dvd 1
269m 53.43s: volume label BRIDGES_OF_MADISON_COUNTY

Burn log



2009-09-10 20:46:04 ---- ******************** Log session stop 10-Sep 20:46:04.375 PID 652********************
2009-09-10 17:02:11 Info Current Drive selected : 1:0:0 - MATSHITA DVD-RAM UJ-841S 1.21 [D] (Ide)
2009-09-10 17:02:11 Info Using Advanced SPTI interface
2009-09-10 17:02:11 Info System default language : English (United States)
2009-09-10 17:02:11 Info User default language : English (United States)
2009-09-10 17:02:11 Info DLL Version : 4.0.4.462
2009-09-10 17:02:11 Info DLL : C:\Program Files\DVDFab 6\vso_hwe.dll
2009-09-10 17:02:11 Info Version : 6, 0, 6, 0
2009-09-10 17:02:11 Info ExeName : C:\Program Files\DVDFab 6\DVDFab.exe
2009-09-10 17:02:11 Info OS : Microsoft Windows XP Professional (Build 2600: Service Pack 3)
2009-09-10 17:02:11 ---- ******************** Log session start 10-Sep 17:02:11.296 PID 652********************


PLEASE ADVISE and copy my email

[GregiBoy]

Matshita drives are notorious for causing problems.

Also, most drives in portables tend to overheat when used hard.

Error 100 = DVD_Error_OpenFile so to me it sounds like the drive is not resetting properly after the burn.

If the burns are working fine, I would just tor off verify.

I would also move from the TDK media to either Verbatim or Taiyo Yuden as TDK is of suspect quality.

[troy512]

yeah its just a verify error. if the disc plays don't worry about it. turn verify off.

[RalphH]

Verify error=100

I get the same error EVERY TIME. I am using an LG 20X (it died yseterday so now I am using a LG 22x) both internal. I write at 12x and am using SONY 16X "AccuCore" DVD-R. Most (98%) DVDs are made with no error but why have a verify function if it does not work. Seems to me the verify does not even start.

[maineman]

I get the same error EVERY TIME. I am using an LG 20X (it died yseterday so now I am using a LG 22x) both internal. I write at 12x and am using SONY 16X "AccuCore" DVD-R. Most (98%) DVDs are made with no error but why have a verify function if it does not work. Seems to me the verify does not even start.

VSO's verify function has been problematic for many users for at least a year now. It's performance is inconsistent at best.
As you know, VSO is Fab's default burn engine and as such is integrated with the dowload and install unless opted out.

I have no answer as to why have it...if it doesn't work, but hopefully VSO can provide you with some answers


Should you want to, contact VSO support:

http://www.vso-software.fr/support.php

If you wish to verify, personally, I'd recommend Img. Simply, it works.
I don't use the verify function, but I do use Img almost exclusively and never have a "bad" burn unless it's PBCAK...

[RalphH]

I have installed ver 6120 and find that verify no longer gives the error 100. Now the verify says "started" but just sets there. Quite by accident I have discovered that when the copy is completed if I eject the disk and then reinsert it before or after "verify started" that the disk verify actually starts and will complete. Takes a very long time though, hour to hour and half