7 replies to this topic

[gondwana]

Hi

Fyi
the adobe reader 10 download made my autopatcher "unofficial".
I cured this by deleting the adobe reader 9 module folder, so am now "official" again.

[_def_x_]

Can you re run apup.exe /w logging, select only the Adobe Reader 10 script and post the log file using Spoiler so we can have a look.

[_def_x_]

Quote

the adobe reader 10 download made my autopatcher "unofficial". I cured this by deleting the adobe reader 9 module folder, so am now "official" again.

It looks like Adobe Reader 9 was the problem - I would think these versions could co-exist.

What Reader 9 was giving you the problem - Reader_Pt_Br or Reader_Ita? A script might need an edit to clean up better.

[gondwana]

gUiTaR_mIkE, on 03 December 2010 - 02:57 PM, said:

What Reader 9 was giving you the problem - Reader_Pt_Br or Reader_Ita? A script might need an edit to clean up better.

Hi again
It is Reader_EN_US,

here is the log file

Spoiler

APUP Has Started
Version: 1.3

Operating System: English (1033) Windows XP Professional Service Pack 3
Current Locale: English - United States / Non-Unicode Default: English - United States
Starting APUP From: C:\Autopatcher
Date & Time: 03-Dec-2010 18:19 UTC Offset: 2

***Downloading/Processing Releases.list***

List file HTTP location: http://www.autopatch...m/releases.list
Download queue processed. Proceeding to next phase.

***Releases.list Processed: Waiting for User Input***

Exit button has been pressed!!!

Thanks

[_def_x_]

I guess we're having a communication breakdown, oh well, the release is Official, that's the important part.

When the release was Unofficial you removed Reader 9 and it was Official once more correct - this means what you removed was the problem, in this case Reader 9. If Reader 10 was the problem the release would still be Unofficial but it isn't correct - so Reader 10 can't be the problem.

There is no script selected for download so the log is useless. What really needs to be done since I have no clue what the real issue is - all the Reader scripts need to be downloaded to the same folder to determine if there is an issue in one or more scripts, the download is 80 MB so I can't do it.

[gondwana]

Sorry if I misunderstood something, I don't have the background to help much other than to provide feedback.

The reason that I removed the reader 9 folder was that after the reader 10 download, reader 9 was not shown in the autopatcher menu, so I guessed that it was supposed to be removed and the new md5 got a bad checksum.

It worked, it seems, so I will leave it to the experts to find the real reason.

[_def_x_]

Quote

Sorry if I misunderstood something, I don't have the background to help much other than to provide feedback.

I totally understand, this stuff gets confusing for sure, regardless, feedback is always appreciated.

About the new .md5 and bad checksum - I don't see an .md5 in any of the 4 Adobe scripts but lets leave it alone. I'm not trying to make it more of an issue - just trying to figure out what exactly was making your release Unofficial so it can be fix.

[Cristiano]

true, this script doesn't have an md5 file. reason: there's only a few files in the script. so, the script himself is the md5 check (except that the md5 can show rogue files). but ok, download test done. this is the log:

Spoiler

APUP Has Started
Version: 1.3

Operating System: English (1033) Windows 7 Professional 64-bit
Current Locale: Portuguese - Brazil / Non-Unicode Default: Portuguese - Brazil
Starting APUP From: D:\criar md5
Date & Time: 03-dez-2010 22:38 UTC Offset: -3

***Downloading/Processing Releases.list***

List file HTTP location: http://www.autopatch...m/releases.list
Download queue processed. Proceeding to next phase.

***Releases.list Processed: Waiting for User Input***

The Following Releases have been Picked:
apup.script
apengine.script
adobe_reader/en-us/autopatcher_adobe_reader_en_us.script

***Running Any Pre-Cleanup Routines***

Download queue processed. Proceeding to next phase.
Executing shell command: del "D:\criar md5\apup_bin\uz.exe"
Executing shell command: rmdir /S /Q "D:\criar md5\win9xnt"
Executing shell command: move /y "D:\criar md5\modules\stand_alone\AdbeRdr940_en_US.apm_files\AdbeRdr1000_en_US.exe" "D:\criar md5\modules\stand_alone\AdbeRdr1000_en_US.apm_files\AdbeRdr1000_en_US.exe"
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdr940_en_US.apm_files
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdrUpd941_all_incr.apm_files
Executing shell command: del "D:\criar md5\modules\stand_alone\AdbeRdr940_en_US.apm"
Executing shell command: del "D:\criar md5\modules\stand_alone\AdbeRdrUpd934_all_incr.apm"
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdr933_en_US.apm_files
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdrUpd934_all_incr.apm_files
Executing shell command: del "D:\criar md5\modules\stand_alone\AdbeRdr933_en_US.apm"
Executing shell command: del "D:\criar md5\modules\stand_alone\AdbeRdrUpd941_all_incr.apm"
Executing shell command: move /y "D:\criar md5\modules\stand_alone\AdbeRdr930_en_US.apm_files\AdbeRdr933_en_US.exe" "D:\criar md5\modules\stand_alone\AdbeRdr933_en_US.apm_files\AdbeRdr933_en_US.exe"
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdr940_pt_BR.apm_files
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdr930_en_US.apm_files
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdrUpd931_all_incr.apm_files
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdrUpd932_all_incr.apm_files
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdrUpd933_all_incr.apm_files
Executing shell command: del "D:\criar md5\modules\stand_alone\AdbeRdr930_en_US.apm"
Executing shell command: del "D:\criar md5\modules\stand_alone\AdbeRdrUpd931_all_incr.apm"
Executing shell command: del "D:\criar md5\modules\stand_alone\AdbeRdrUpd932_all_incr.apm"
Executing shell command: del "D:\criar md5\modules\stand_alone\AdbeRdrUpd933_all_incr.apm.apm"
Executing shell command: del "D:\criar md5\adobe_reader_en_us.rti"
Executing shell command: rmdir /S /Q D:\criar md5\modules\stand_alone\AdbeRdr920_en_US.apm_files
Executing shell command: del "D:\criar md5\modules\stand_alone\AdbeRdr920_en_US.apm"
Executing shell command: del "D:\criar md5\adobe_reader_92_en_us.rti"
Executing shell command: del "D:\criar md5\adberdr9_enu.rti"
Executing shell command: del "D:\criar md5\modules\AddOns\__adberdr.apm"
Executing shell command: rmdir /S /Q "D:\criar md5\modules\AddOns\__AdbeRdr"
Executing shell command: xcopy /y /e /i D:\criar md5\modules\AddOns\AdbeRdr920_en_US.apm_files D:\criar md5\modules\stand_alone\AdbeRdr920_en_US.apm_files
Executing shell command: rmdir /S /Q D:\criar md5\modules\AddOns\AdbeRdr920_en_US.apm_files
Executing shell command: del "D:\criar md5\modules\AddOns\AdbeRdr920_en_US.apm

***Starting Detection Routine Phase***

Missing file D:\criar md5\modules\stand_alone.apm
Item Windows Stand Alone Parent Module is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://www.autopatch...and_alone.apm--

Missing file D:\criar md5\adobe_reader_EN-US.rti
Item adobe_reader_EN-US.rti is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://www.autopatch...der_EN-US.rti--

Missing file D:\criar md5\modules\stand_alone\AdbeRdr1000_en_US.apm
Item AdbeRdr940_en_US.apm is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://www.autopatch...000_en_US.apm--

Missing file D:\criar md5\modules\stand_alone\AdbeRdr1000_en_US.apm_files\AdbeRdr1000_en_US.exe
Item AdbeRdr940_en_US.exe is missing or its parts are not completely downloaded. Adding whole download for this item to the queue.
--Adding http://ardownload.ad...000_en_US.exe--

***Downloading Releases***

Files to be Downloaded: 4
Download queue processed. Proceeding to next phase.

***Processing Cleanup Routines***

and it shows as official in here. and yes, the modules folder was empty. so, may be possible the presence of an rogue file in the user side. solution: look for:
adobe_reader_EN-US.rti
stand_alone.apm
AdbeRdr1000_en_US.apm
AdbeRdr1000_en_US.exe

if all that is present, then the script should be official, but it also becomes unofficial if anything else is present. so, please look into your local folder and make an list of the files that are under apup folder

thanks

[]s