Adobe Reader 10 unofficial
gondwana
03 Dec 2010
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.
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_
03 Dec 2010
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_
03 Dec 2010
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.
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
03 Dec 2010
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
Thanks
_def_x_
03 Dec 2010
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.
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
03 Dec 2010
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.
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_
03 Dec 2010
Quote
Sorry if I misunderstood something, I don't have the background to help much other than to provide feedback.
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
04 Dec 2010
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:
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
Spoiler
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
