Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

1

[Solved] Verification Failures

Started by Guest_hendos4_*, Nov 18 2008 11:04 PM

You cannot reply to this topic
Go to first unread post

4 replies to this topic

#1 Guest_hendos4_*

Guests

Posted 18 November 2008 - 11:04 PM

Hi everone,

I Downloaded for the first time last night for XP 1.8 gig after making selections for addons ect. and twice twice during the download i recieved the following: One or more files failed verification. Please run Autopatcher Updater. If problem persists. Please report to The forums at Autopatcher.

Well here I am, now this morning I thought I would only download the minimum ticked which was Auto Patcher Updater 1.0.5, Auto Patcher Engine 5.6.81 & Auto Patcher for XP SP3 (86). then do each extra item one at a time, to see when error message came into play. Well it came in after the inital download. Can anyone tell me does it matter or does it have to be fixed. Is there a problem my end or is it with the current files on autopatcher.

Sincerely

hendos4

Back to top

#2 Cristiano

Super Helpful Guy

Veterans
3,851 posts

Gender:Male
Location:Brazil (Santa Maria - RS)

Posted 18 November 2008 - 11:48 PM

we need the log to be able to fix the issue. can you please run apup with /log option and pick the exact same scripts that you have selected before? so far, you may get an shockwave verification failure, due an recent update.

[]s

Back to top

#3 anceltu

Newbie

Members
3 posts

Posted 19 November 2008 - 08:11 AM

please fix this:

Download Error: E:\apup\xp_sp3_enu.rti
File size does NOT match. Expecting 0, but found 57093!!!

Back to top

#4 Cristiano

Super Helpful Guy

Veterans
3,851 posts

Gender:Male
Location:Brazil (Santa Maria - RS)

Posted 19 November 2008 - 08:30 AM

yesterday, was solved an issue regarding an update to wmp10. it was an quick fix and the maintainer was away from his machine, so, the script was left unsigned, that was the reason for the release be unsigned. anyway, the expected size should not be 0

[]s