Is it a duplicated patch?
FDIV-Bug
09 Mar 2010
I'm using the XP SP3 PTB Realease and apparently there is a duplicated WGA patch. The 1st patch is correct but de 2nd one seems to be part of the ENU release.
Well a picture is worth a thousand words, so...
AutoPatcher066.png (49.37K)
downloads: 9
Thanks!!!
Well a picture is worth a thousand words, so...
AutoPatcher066.png (49.37K)
downloads: 9
Thanks!!!
_def_x_
09 Mar 2010
WGA is included in 2 of your releases, XP_Ptb and the Extras package, for some reason WGA is not part of the XP_Enu release.
It looks like you will have 3 updates in your release:
(1) KB892130 - both .apm and .exe are the same, so when downloading, each release will detect the file(s) in place.
(2) KB905474 - different .apm files, different .exe files, same "Title" which is why you see it listed twice.
So, if you could check your release, you should have 3 .exe files in the \wga_files\ folder, and 3 .apm files in the \modules\wga\ directory.
Spoiler
It looks like you will have 3 updates in your release:
(1) KB892130 - both .apm and .exe are the same, so when downloading, each release will detect the file(s) in place.
(2) KB905474 - different .apm files, different .exe files, same "Title" which is why you see it listed twice.
So, if you could check your release, you should have 3 .exe files in the \wga_files\ folder, and 3 .apm files in the \modules\wga\ directory.
FDIV-Bug
09 Mar 2010
Quote
It looks like you will have 3 updates in your release:
(1) KB892130 - both .apm and .exe are the same, so when downloading, each release will detect the file(s) in place.
(2) KB905474 - different .apm files, different .exe files, same "Title" which is why you see it listed twice.
So, if you could check your release, you should have 3 .exe files in the \wga_files\ folder, and 3 .apm files in the \modules\wga\ directory.
(1) KB892130 - both .apm and .exe are the same, so when downloading, each release will detect the file(s) in place.
(2) KB905474 - different .apm files, different .exe files, same "Title" which is why you see it listed twice.
So, if you could check your release, you should have 3 .exe files in the \wga_files\ folder, and 3 .apm files in the \modules\wga\ directory.
You're right gUiTaR_mIkE. I have 3 files in those folders.
For now i just marked the ENU WGA patch so that it no longer appears in AutoPacther's list.
_def_x_
09 Mar 2010
Since I don't bother with WGA or WUA (from another thread) I don't know what the prerequisites for installation
are on a non English OS, you may need both KB905474 files (or not)
.
I would hold off on installation until this gets sorted out.
are on a non English OS, you may need both KB905474 files (or not)
. I would hold off on installation until this gets sorted out.
Cristiano
09 Mar 2010
ok, the version that is at the extras version will be tagged to not load in 1046, since kb905474 is localized (but the module was set to be universal, just because it loads in all languages. if the reason is that, then msie should be universal as well, because the enu one loads in all languages and install pretty fine. of course, it will turn the OS in a mix of languages, ...). but to do that, i will check if this one isn't included in the ita script or i will create an issue to Domenico
again, this is an common mistake. most of the modules that work and have some usage from the extras package are already built-in the ptb script and i'm unsure if some of the ones that are in the extras package will not turn your OS in an mix of languages. i've set an warning about that in the first post of the ptb script long ago.
[]s
again, this is an common mistake. most of the modules that work and have some usage from the extras package are already built-in the ptb script and i'm unsure if some of the ones that are in the extras package will not turn your OS in an mix of languages. i've set an warning about that in the first post of the ptb script long ago.
[]s
Cristiano
09 Mar 2010
after think a little bit about the situation above, i come across with certain issues...
first of all, that module loads into all languages, but there's an localized version for each language. if there's an localized version, then the localized one should be present and not the enu one. for xp, an simple restriction to the language could fix the issue, but the vista and now seven scripts doesn't have the wga related modules built in. also in vista and seven, that same localized version should be present. that module loads and work fine. issue: those modules aren't built-in vista nor seven. ok, those modules in the extras package work, but there's localized versions, so why keep an generic version?
i believe that at this point, some consideration about is required. any ideas about?
[]s
first of all, that module loads into all languages, but there's an localized version for each language. if there's an localized version, then the localized one should be present and not the enu one. for xp, an simple restriction to the language could fix the issue, but the vista and now seven scripts doesn't have the wga related modules built in. also in vista and seven, that same localized version should be present. that module loads and work fine. issue: those modules aren't built-in vista nor seven. ok, those modules in the extras package work, but there's localized versions, so why keep an generic version?
i believe that at this point, some consideration about is required. any ideas about?
[]s
Cristiano
09 Mar 2010
ok, we have reached an agreement. booth wga files will be removed from the extras package and moved to the main scripts, as should be since always. kb905474 will be restricted to xp enu only. the same thing will be done with the vista and seven scripts
[]s
[]s
