Newer one
#1
Posted 12 March 2009 - 02:55 PM
#2
Posted 12 March 2009 - 03:39 PM
Mike
#3
Posted 12 March 2009 - 04:21 PM
#4
Posted 12 March 2009 - 05:03 PM
flash files. The script downloads both flash and flash active-x - v10.0.22.87.
Mike
#5
Posted 12 March 2009 - 06:01 PM
thanks
[]s
#6
Posted 12 March 2009 - 06:05 PM
#7
Posted 12 March 2009 - 07:35 PM
WindowsVersion=2K,XP_X86,2K3_X86,VISTA_X86,LHSERVER
the not IE version has the same limitations and also the shockwave module. if you are running an x64 version, that can explain the issue that you are having. it may also be related to the sp2 RC, because they may have changed something in that one that may prevent this module from load, but i'm not sure
[]s
#8
Posted 12 March 2009 - 08:20 PM
Cristiano, on Mar 12 2009, 08:35 PM, said:
WindowsVersion=2K,XP_X86,2K3_X86,VISTA_X86,LHSERVER
the not IE version has the same limitations and also the shockwave module. if you are running an x64 version, that can explain the issue that you are having. it may also be related to the sp2 RC, because they may have changed something in that one that may prevent this module from load, but i'm not sure
[]s
I am running x86. You could be right on there might be a change in Sp2 RC.
#9
Posted 12 March 2009 - 09:44 PM
WindowsVersion=2K,XP_X86,2K3_X86,VISTA_X86,LHSERVER
and replace it with this:
WindowsVersion=2K,XP_X86,2K3_X86,VISTA,LHSERVER
or even this:
WindowsVersion=ANY
the first one will remove the limitation for the x64 (this doesn't means that flash player will install in x64 systems). the ANY will open this module to any OS. please, on tests, do one first, then another and just do the replacements with autopatcher closed. this will make your autopatcher unofficial, so please, do it for test purposes only.
if this module loads after any of those changes, please reply
thanks
[]s
#10
Posted 13 March 2009 - 03:14 PM
Cristiano, on Mar 12 2009, 10:44 PM, said:
WindowsVersion=2K,XP_X86,2K3_X86,VISTA_X86,LHSERVER
and replace it with this:
WindowsVersion=2K,XP_X86,2K3_X86,VISTA,LHSERVER
or even this:
WindowsVersion=ANY
the first one will remove the limitation for the x64 (this doesn't means that flash player will install in x64 systems). the ANY will open this module to any OS. please, on tests, do one first, then another and just do the replacements with autopatcher closed. this will make your autopatcher unofficial, so please, do it for test purposes only.
if this module loads after any of those changes, please reply
thanks
[]s
I did with WindowsVersion=ANY and that worked but that was just for IE. I use Fire Fox as my mine one. Is that to show too?
#11
Posted 13 March 2009 - 03:31 PM
#12
Posted 13 March 2009 - 03:49 PM
WindowsVersion=2K,XP_X86,2K3_X86
After I have made the change to both they both show up now.
#13
Posted 13 March 2009 - 03:55 PM
Mike
#14
Posted 13 March 2009 - 04:39 PM
#15
Posted 13 March 2009 - 05:13 PM
5f2c77669653af0ecbbb508f90435d68
that doesn't match with the expected md5: D165A45C53C2A8C0EED17ECC632F566D
but it has the following limitations:
WindowsVersion=2K,XP_X86,2K3_X86,VISTA_X86,LHSERVER
SystemLanguage=ANY
so it should be loaded into vista. plus, the md5 for the ___windows_extras_0812.7z matches with the expected one:
EA80CE9D0EF4A745CC6EE3F1D94ED10C
so, 2 possible issues:
1 - the wrong md5 that flashplayer_IE_x86.apm has is matching with the one that you have (that wasn't loading into vista) and, because of that, apup isn't downloading the new file, creating this issue
2 - webcache. but this one is less provable. the only one that i know that it's badly done are the ones from BRT
can you do just another test? just delete those files and run apup again. it will then download the new files. after that, just look if the module is loading.
but i'm pretty sure that the md5 from that file is from the old version...
thanks
[]s
#16
Posted 13 March 2009 - 06:34 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












