Frequent failure to verify media

[dontasciime]

I only ever use xp's SPTI (98%) and Winaspi32.dll the other 2% never had any issues burning over 6,000 discs.

 

I would agree with you on Nvidia IDE I never use it and prefer MS for all my nforce boards, However I have never had any problems with Via's Ide.

[hetster]

so whats your opinion on where the erros are occuring?

in the ripping stage or the burning stage..eg is the error in the iso or the burnt dvd..and is there a way of verifying a on the fly copy then i can eliminate the hdd alltogether

[LIGHTNING UK!]

Verify that same disc a few times against the same image.

 

Does the error ever change? (by that, I mean the LBA of the error and the byte values)

 

You could have a duff cable that's causing corruption to the data stream. It could also be your memory - run memtest+ on it.

[hetster]

ok ran mem test for 20 mins and its all fine..

the LBA is in different positions every burn as stated before..23%..60% all different places (check the last 2 logs all 3 different LBA positions). but after rescanning a failed to verify disk the error on the disk no matter how many times its scanned is in the the same place..1 error in the same LBA address. i dont know wether its the burn with the error or the iso..i'm thinking of upgrading pc anyway and that would require a reformat anyway.if that doesnt cure it i dunno what will lol..as stated before they are also new cables...that was my first step in troubleshooting..that and resetting the ide controllers to make sure i was in udma 4

 

 

got a failed to verify disk and rescanned..and same single error in exactly same place..

 

FIRST SCAN

 

I 11:18:05 Verifying Sectors...
W 14:21:52 Miscompare at LBA: 1619491, Offset: 1062
W 14:21:52 Device: 0x6E
W 14:21:52 Image File: 0x2E
W 14:21:52 Total Errors in Sector: 1
I 14:21:52 Verifying Sectors...
I 14:31:04 Device MD5: c65607ce278d262212bfac15c0f32511
I 14:31:04 Image MD5: c647adcf6507ae8819a7eadf071272f4
I 14:31:05 Operation Successfully Completed! - Duration: 03:12:59

 

SECOND SCAN (VERIFY ONLY)

 

I 14:31:49 Verifying Sectors...
E 14:40:03 Miscompare at LBA: 1619491, Offset: 1062
E 14:40:03 Device: 0x6E
E 14:40:03 Image File: 0x2E
E 14:40:03 Total Errors in Sector: 1
E 14:40:03 Failed to Verify Sectors!
E 14:40:03 Operation Failed! - Duration: 00:08:14

 

i canceled at first error..seemed pointless going to end now i know error is in same place.

Edited January 23, 2007 by hetster

[hetster]

well if ya cant help with imgburn maybe you could help me with this

 

Dear Technical Support,

 

18 months ago, I upgraded to Girlfriend 1.0 from DrinkingMates 4.2,

which I had used for years without any trouble. However, there are

apparently conflicts between these two products and the only solution

was to try and run Girlfriend 1.0 with the sound turned off.

 

To make matters worse, Girlfriend 1.0 is incompatible with several

other applications, such as LadsNightOut 3.1, Football 4.5, and

Playboy

6.9.

Successive versions of GirlFriend proved no better.

 

I tried a shareware program, Slapper 2.1, but it had many bugs and

left a virus in my system, forcing me to shut down completely for

several

weeks.

Eventually, I tried to run GirlFriend 1.2 and Girlfriend 1.0 at the

same time, only to discover that when these two systems detected each

other they caused severe damage to my hardware.

 

I eventually upgraded to Fianc

[LIGHTNING UK!]

Sorry, all you can do now is start swapping out hardware until the problem goes away.

[dontasciime]

hetster

 

single and hand.

Edited January 26, 2007 by dontasciime

[hetster]

well i think i found the culprit..

 

i uninstalled alcohol 120% and instaled latest version but disabled the virtual drive..so far 5 outta 5 all verified 100%

 

maybe a virtual drive conflict? is this a known bug?

[LIGHTNING UK!]

You'd have to ask that question over at the alcohol forum.

 

ImgBurn doesn't have problems with anything so long as it doesn't mess up basic communication to the drive!

 

If 3rd party apps install drivers (ImgBurn does not) and those drivers mess things up, there's no way for anyone to know.

 

It's just a case of getting the machine back to the stage when it DID work and then perhaps installing normal software until it doesn't - perhaps that's what you did anyway?

[hetster]

was pure luck lol..i had been trying different ways to burn DL on the fly..none of the software seemed to work so i started to update things and still no luck..alcohol 120% was my last resort so i got latest version..as it was installing i thought i dont even need a virtual drive..i never mount anything anyway so i'd install with the minimum it needed..but again it wouldnt copy on the fly..so i tried imgburn/dvd decryptor method again..and since uninstalling the virtual drive i havent had a single fail on verification..i'll keep everyone posted anyway just in case anyone else has the same problems as i did..

[LIGHTNING UK!]

In theory, DAEMON Tools and Alcohol 120% should have very similar virtual drive drivers. I know loads of people using DT without any issues when verifying - myself included.