So can I use the OLDER ONE?
The reason being that the new one needs Net Framework 3.
Which of couse means another huge download, and my install from the
factory (destroyed by the virus) only had version 2. "I know that for
fact because the virus scanner kept saying it was infected. Version 2
was just installed by the video drivers. I dont know what net framework
does, but I only have a 40G HDD on here and dont need to fill it with
stuff I dont need, just to run a few web browsers.
Actually the computer is working fine even with those two yellow
problems in device manager, but I thought all they needed was a simple
driver. Seems some of this stuff never ends, and keeps wantingf more
and more downloads and stuff added, which I probably dont need.
I do know the battery icon is not on my taskbar like it used to be. so I
suppose it's this file. I already did have the latest version of this
file, since I downloaded ALL the XP files at a WIFI, so I did not have
to spend days downloading at home. I ran all of them, some were
rejected, some installed, this one said it needed Net Framework 3, and
several other things were installed that seem useless, like something
called NetWaiting.
Thanks
Battery MaxiMiser and Power Management features for Windows
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/1xu105u1.exe (2.7MB)
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/1xu105u1.txt
There is mention in the text file of a "Fuel Gauge" so I
assume that's the battery icon.
*******
If you're installing Win2K, then you'd use the OLDER ONE.
If you're installing WinXP, you'd install the WinXP one.
The .NET is like a bleeding sore that won't heal. The
problem is, if we identify a version you need, you download
the version, you download maybe three or four more patch
or Service Pack files, then you hop onto Windows Update,
and scores of security updates come in. Then .NET fouls up
your Firewall at boot time, the network doesn't work for the
first minute or so. And you have to use the ngen recipe to
fix that. I wouldn't be nearly so negative about .NET, if there
was a "current image" sitting there somewhere, which you
just download and it brings you right up to date. For
a person like yourself on dialup, dealing with that
crap is virtually impossible. It means dragging the
computer to your Wifi spot, because so many of the
downloads will be lengthy.
Some of the later OS installer DVDs, they have a few
folders with files of that sort present. Some DVD I've got here,
had a set of .NET and some DirectX, which was a welcome relief
from having to scrounge up all the stuff.
It's possible the installer has the .NET dependency
and not the stuff inside it. We can always hope...
Time to drag that ghu704ww.exe into a VM and
beat some sense into it. OK, that gives me
69MB of files in C:\DRIVERS\WIN\PWRMGR. So I
only ran the installer to the point that it
unpacked that folder.
When I run clrver.exe on a few of the files there...
PWMUI.exe = v2.0.50727
PWMUIAux.exe = v2.0.50727
And this article says those are .NET 2.0, same
as your video driver. There is a CLR Version table
with the version numbers in it.
http://en.wikipedia.org/wiki/.net_framework
Did something tell you that you needed 3.0 ?
I can't be 100% certain of my methodology. While
the CLR (C Language Runtime) version should be
indicating the .NET needed, it's always possible
I missed something in one of the other files. I
just checked a few .EXE files. The installer
should be telling you what you need. Version
3.0 would have a different CLR value (3.0.4506.30).
You can get the CLRVER.exe program here. It is
a command line program.
http://www.devfish.net/downloads.aspx
clrver PWMUI.exe
and it then returns the CLR version number
stored in the executable somehow.
So what I did there, is run the ghu704ww.exe file
until it unpacked stuff into C:\DRIVERS\WIN\PWRMGR.
But I didn't try running the setup.exe or anything.
I ran CLRVER on a few of the executables, to
see if they needed 3.0 or not. And they don't
seem to.
HTH,
Paul