Jump to content


Download Error causes Unofficial/Unsupported status.


56 replies to this topic

#1 FDIV-Bug

    Member

  • Members
  • PipPip
  • 13 posts
  • Gender:Male
  • Location:BraSil

Posted 07 March 2010 - 10:11 PM

Like a said in the title, during Autopathcer's download part an error causes Unofficial/Unsupported status.
Is it a problem? Or can i ignore it?

here is the log

Attached File  apup.txt   25.53K   16 downloads

Edited by FDIV-Bug, 07 March 2010 - 10:13 PM.


#2 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 08 March 2010 - 12:01 AM

this issue is already driving me crazy. it's at least the 3rd or 4th time that i fix the exact same thing: the name of the file that is being downloaded was wrong all times. i fix it, upload it and 1-2 days after it, the issue is in there again. well, it is re-re-re-re-re-re-fixed again

[]s

#3 FDIV-Bug

    Member

  • Members
  • PipPip
  • 13 posts
  • Gender:Male
  • Location:BraSil

Posted 08 March 2010 - 02:55 AM

View PostCristiano, on 08 March 2010 - 12:01 AM, said:

this issue is already driving me crazy. it's at least the 3rd or 4th time that i fix the exact same thing: the name of the file that is being downloaded was wrong all times. i fix it, upload it and 1-2 days after it, the issue is in there again. well, it is re-re-re-re-re-re-fixed again

[]s

Thanks Cristiano!!!! As soon as i test the file re-re-re-re-re-re-fixed i post the results.

#4 FDIV-Bug

    Member

  • Members
  • PipPip
  • 13 posts
  • Gender:Male
  • Location:BraSil

Posted 08 March 2010 - 11:03 AM

The problem is definitely fixed, THANKS!!!!

#5 DesertJerry

    Lives In AutoPatcher Forum

  • Members
  • PipPipPipPipPipPip
  • 1,037 posts
  • Gender:Male
  • Location:Victorville, California

Posted 08 March 2010 - 07:37 PM

Not fixed here.

Read the above, ran APUP with same selections checked as always for XP Pro w/SP3, new AutoPatcher engine downloaded; ran AutoPatcher - got message about Unofficial/Unsuported Release.

I did check the AutoPatcher.exe file itself and the date/size had changed from my previous copy.

Please, please - when updating APUP.EXE or AUTOPATCHER.EXE please increment the version number accordingly - this version of AUTOPATCHER.EXE should now be: 5.6.0.101 :huh:

#6 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 08 March 2010 - 07:57 PM

ok, that will be checked. but the previews issue was related to the ptb release. i'm assuming that your issue is related to the enu script, i'm not sure about with script, but the apengine was updated. increment version right now it's an problem, because the version number was encoded into the code by hand. until replace that part of the code by an more functional one, we have to deal with this issue. autopatcher.exe was reloaded today due an issue with x64 systems. basically, it was an quick fix only. so, sorry for the trouble.

as for the issue with the script, it will be checked tonight

thanks

[]s

#7 DesertJerry

    Lives In AutoPatcher Forum

  • Members
  • PipPipPipPipPipPip
  • 1,037 posts
  • Gender:Male
  • Location:Victorville, California

Posted 08 March 2010 - 08:31 PM

More info.

Booted into XP Pro x64 - same error mesage about Unofficial/Unsupported.

Booted into Win7 32-bit - same error message.

Booted into Win7 64-bit - APUP failed "Error fetching release list" so I could not check further here.

#8 DesertJerry

    Lives In AutoPatcher Forum

  • Members
  • PipPipPipPipPipPip
  • 1,037 posts
  • Gender:Male
  • Location:Victorville, California

Posted 08 March 2010 - 11:09 PM

View PostDesertJerry, on 08 March 2010 - 08:31 PM, said:

More info.

Booted into XP Pro x64 - same error mesage about Unofficial/Unsupported.

Booted into Win7 32-bit - same error message.

Booted into Win7 64-bit - APUP failed "Error fetching release list" so I could not check further here.
Disregard the "Error fetching...' above - my fault - I forgot to remove parameter from the Optional Parameters box.

But, after that was fixed and APUP did its thing, AutoPatcher was run and the same eror message appeared about Unofficial/Unsupported.

Started #2 system and got the same error message when APUP was run, AutoPatcher updated in XP Pro w/SP3 and Win7 32-bit.

Also, on all Win7 systems when AutoPatcher is run and the List of available items appears the last item in the list is: Stand Alone - there is no heading mentioning Adobe.

#9 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 08 March 2010 - 11:36 PM

> there is no heading mentioning Adobe.
the module has to be updated. when the script was done, we didn't had an detection for seven yet, so the module doesn't load with seven. that will be fixed by tomorrow. right now, i'm too busy to do that (2 machines to fix, besides mine. mine stays in the last position of my list, so...)
please, disregard that. i've fixed one of the machines far sooner than expected. the adobe reader script was updated to add seven compatibility.

i will do an download test with the xp enu script. maybe that help track the issue. you had only the xp enu script, right?

[]s

Edited by Cristiano, 09 March 2010 - 12:07 AM.


#10 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 09 March 2010 - 02:59 AM

download test finished. an issue regarding the shared module Windows Update Agent v7.4.7600.226 was found. the script was re-signed and uploaded. so please, check if that solves the problem

[]s

#11 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,466 posts
  • Gender:Male

Posted 09 March 2010 - 07:39 AM

Cristiano said:

an issue regarding the shared module Windows Update Agent
If this problem is similar to the issue with WGA being in both the XP_Ptb and Extras package, but not in XP_Enu, I would suggest,
if these programs are important to the OS, and not language neutral, remove them from Extras and have them in the OS release.

The idea is that you know the OS package will be downloaded first over the Extras so have WGA and WUA be included in the OS scripts. :)

#12 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,466 posts
  • Gender:Male

Posted 09 March 2010 - 10:54 AM

...and not to forget MU (the wonderful muweb), which I believe is in the Extras as well :blink:

I'm not telling anybody what to do but it seems a better idea to consolidate these features into each OS script,
WGA, WUA, MU, they seem more relevant to an OS than the Extras, but I don't use any of them so what do I know :ph34r:

#13 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 09 March 2010 - 11:08 AM

> with WGA being in both the XP_Ptb and Extras package
KB892130 is common to all scripts, but not KB905474. this last one is localized. but you are right. certain things should never be moved from the main package to extras. this was done thinking more in one language only, but if you think well, when an shared module is updated, you have to remember a lot of things, like warn others and this doesn't happen all times. this time, it was my mistake (i've forgot to update my local folder with the new file), but could be the exact same thing that was happening before: a lot of times, non-english users download the enu release as well (yes, disregarding ms policy about sell localized versions and state that it's illegal sell enu versions in non-english countries, they do it in here, a lot of times). with this action, if an release manager doesn't warn all others, problem. duplicated files, modules being loaded twice, unofficial issues, etc. worst: when this split was done, every single script that had those files had removed those files and moved to extras. but as yours know, not all things runs to every single thing. in the .net package, by instance, there's certain modules that only load in win2k, making xp, vista and now seven users download things that never will load in their systems. this could be solved, but then all those modules should be moved to his own package, but then it makes the release manager worst. in the last year, i think that i have located all shared modules and there's a lot of them. mostly, the updates for wmp are all shared, among other things.

even worst, to undo that, it's tricky, because the release manager must update several scripts at once. but there's an even worst thing: certain modules, that was supposed to be common, just doesn't work if your OS isn't an enu one.

> WUA be included in the OS scripts
that was my idea, but then, what do with the other OS's that also has this one? i can do that, but if i do, then i will create an extra load of work to others. worst: until some time ago, i had to deal with those that was downloading the extras package with the ptb and was loading the same module twice. until realize what was the reason for that...

[]s

#14 DesertJerry

    Lives In AutoPatcher Forum

  • Members
  • PipPipPipPipPipPip
  • 1,037 posts
  • Gender:Male
  • Location:Victorville, California

Posted 09 March 2010 - 10:18 PM

View PostDesertJerry, on 08 March 2010 - 11:09 PM, said:

Also, on all Win7 systems when AutoPatcher is run and the List of available items appears the last item in the list is: Stand Alone - there is no heading mentioning Adobe.
Just ran my Win7 32-bit and 64-bit systems - AutoPatcher now has Stand Alone > Adobe - so that problem is fixed.

#15 FDIV-Bug

    Member

  • Members
  • PipPip
  • 13 posts
  • Gender:Male
  • Location:BraSil

Posted 10 March 2010 - 11:28 AM

I'm getting download erros again. (sad, but true)

Here's the log:

Spoiler

*I can't attach the log, i'm getting the following error: Error You aren't permitted to upload this kind of file

Edited by Cristiano, 10 March 2010 - 11:41 AM.
spoiler


#16 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 10 March 2010 - 11:41 AM

congratulations!!! seems that you was the first one to report an update into booth flashplayers and this affects even the extras script enu. but i can't take the detections for this one in here, nor sign the files.

so please, just ignore the error until tonight, when the scripts will be updated to math

[]s

#17 FDIV-Bug

    Member

  • Members
  • PipPip
  • 13 posts
  • Gender:Male
  • Location:BraSil

Posted 10 March 2010 - 11:53 AM

View PostCristiano, on 10 March 2010 - 11:41 AM, said:

congratulations!!! seems that you was the first one to report an update into booth flashplayers and this affects even the extras script enu. but i can't take the detections for this one in here, nor sign the files.

so please, just ignore the error until tonight, when the scripts will be updated to math

[]s

I'm doing my best. :lol:
Thanks por the fast reply!!!

[]s

Edited by FDIV-Bug, 10 March 2010 - 11:54 AM.


#18 _def_x_

    audi 5k

  • Veterans
  • PipPipPipPipPipPip
  • 1,466 posts
  • Gender:Male

Posted 10 March 2010 - 12:19 PM

I guess the links are static, they seem to be good. The files have been updated, but it doesn't seem to be
related to the version number -> new size / hash only. BTW, I took the links from the xp_ptb script.

Name: install_flash_player.exe (notIE)
Ver: 10.0.45.2
Size: 1924976
MD5: 7A00F09FD89CF49CF3FF4EF2E828ADEC

Name: install_flash_player_10_active_x.exe (IE)
Ver: 10.0.45.2
Size: 1956656
MD5: 5F6C243A10337A4269F994CD8B3A6137

#19 IceCubeR

    Newbie

  • Members
  • Pip
  • 2 posts

Posted 10 March 2010 - 03:07 PM

View PostgUiTaR_mIkE, on 10 March 2010 - 12:19 PM, said:

I guess the links are static, they seem to be good. The files have been updated, but it doesn't seem to be
related to the version number -> new size / hash only. BTW, I took the links from the xp_ptb script.

Name: install_flash_player.exe (notIE)
Ver: 10.0.45.2
Size: 1924976
MD5: 7A00F09FD89CF49CF3FF4EF2E828ADEC

Name: install_flash_player_10_active_x.exe (IE)
Ver: 10.0.45.2
Size: 1956656
MD5: 5F6C243A10337A4269F994CD8B3A6137

Hi today i start using APUP (i'm behind a proxy) and i got the same error; here's the log:

Attached Files



#20 Cristiano

    Super Helpful Guy

  • Veterans
  • PipPipPipPipPipPip
  • 3,851 posts
  • Gender:Male
  • Location:Brazil (Santa Maria - RS)

Posted 10 March 2010 - 04:38 PM

> I guess the links are static
yes, they are.

> BTW, I took the links from the xp_ptb script.
they are the same ones that are in the extras enu script, but there's certain things in the extras enu that doesn't work in ptb, so...

@IceCubeR: the issue isn't fixed yet. i have an appointment right now, but i will fix the links in about 2 hours. issue: the script will become unofficial (but they already are, due those files)

[]s





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users