It's broken/orphaned.
(Note: I'm continuing this discussion from here.)
The modules\AddOns\__tweakui.apm script specifies:
[OperatingSystem]
WindowsVersion=2K,XP_x86,2K3_x86
and
[Installation]
(null - i.e., empty)
Thus, it's installation is dependent on a child script, for which none exists that specifies "2K" for the parameter "WindowsVersion".
This explains why it appears as a selection in the AutoPatcher utility, but selecting it produces no installation behavior. I'd be willing to hop on board and help correct this if it would help. I see that the AutoPatcher application has been re-engineered (since I last used it) to be script-driven which is pretty cool (modular/extensible). I'm not sure what kind of constraints the development team has in place for this new architecture, however. Specifically:
I believe The TweakUI infrastructure (v2.10) that's currently being downloaded is post-Windows 2000 and is not backwards compatible with Windows 2000. The child scripts correctly denote this. The last Windows 2000 compatible version of the utility is 1.33, which I cannot find anywhere on microsoft.com (surprising, right?).
Questions:
1) How does the development team address this (file origin)?
2) (Unrelated) I have not been able to figure out what determines patch order/placement in the application and was wondering what drives this?
Let me know - thanks...
I cannot install TweakUI because...
Started by BlackholeForever, Jun 08 2008 07:55 PM
4 replies to this topic
#1
Posted 08 June 2008 - 07:55 PM
#2
Posted 08 June 2008 - 09:13 PM
Ok, found TweakUI v1.33 on Microsoft.com:
http://download.microsoft.com/download/win...-US/Tweakui.exe
That wasn't easy...well, actually it was (once you know where to look
)
http://download.microsoft.com/download/win...-US/Tweakui.exe
That wasn't easy...well, actually it was (once you know where to look
#3
Posted 08 June 2008 - 11:03 PM
Ok, did a little more surfing. This articles explains a lot:
Microsoft-Killed-AutoPatcher-No-More-Third-Party-Windows-Updates
That answers the question regarding constraints on file origin and some of the motivation for the re-engineering...
Microsoft-Killed-AutoPatcher-No-More-Third-Party-Windows-Updates
That answers the question regarding constraints on file origin and some of the motivation for the re-engineering...
#4
Posted 08 June 2008 - 11:03 PM
actually, the version that you've downloaded isn't for wxp. and, by the way: the version 1.33 is a little bit outdated. you may found v 2.1 in here:
http://www.microsoft.com/windowsxp/downloa...ppowertoys.mspx
[]s
http://www.microsoft.com/windowsxp/downloa...ppowertoys.mspx
[]s
#5
Posted 09 June 2008 - 02:32 AM
Cristiano, on Jun 8 2008, 06:03 PM, said:
actually, the version that you've downloaded isn't for wxp. and, by the way: the version 1.33 is a little bit outdated. you may found v 2.1 in here:
http://www.microsoft.com/windowsxp/downloa...ppowertoys.mspx
[]s
http://www.microsoft.com/windowsxp/downloa...ppowertoys.mspx
[]s
Exactly. What's not working is TweakUI for Windows 2000. Version 2.10 does not install on my system (without error), so I believe version 1.33 is required.
Regardless of which version is required/(works), the script itself is broken under Windows 2000.
Edited by BlackholeForever, 09 June 2008 - 02:34 AM.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












