GCoop

This is what I use and it works perfectly. On another not regarding the SSSTK. Does anyone use the Statemgr utility from the tool kit? Does it work for you in PE 2.0 and up? I cant get it to work properly. It throws an error and fails to properly register the state in the nvram. Anone have any insights?

I seem to be having much the sam eproblem as you. I integrated all patches into the admin installaion point but MS updat still reports more patches needed. Did you ever find a solution to this issue? Am I overlooking something? What I find curious is that office update (even though you cant use it for administrativce installs) reports the installation being up to date.

Any luck getting the tools to work? I can boot to pe and load all the hardware drivers but cant get the tools to work. My results so far: The new HPDiscovery from the SSTK 1.7 gives some dll -1 info but appears to run and create the hardware file. Have not tried ifhw to parse the discovery xml file. v2.3 of statemgr included with SSTK 1.7 gives an error but outputs the saved variable state however when trying to read that variable it always returns a null value. These are really the only tools i use so I have not tried to use any of the others. Any way to run exe's from PE 2.0 in compatability mode?

Any luck getting the tools to work? I can boot to pe and load all the hardware drivers but cant get the tools to work. My results so far: The new HPDiscovery from the SSTK 1.7 gives some dll -1 info but appears to run and create the hardware file. Have not trie ifhw to parse the discovery xml file. v2.3 of statemgr included with SSTK 1.7 gives an error but outputs the saved variable state however when trying to read that variable it always returns a null value. These are really the only tools i use so I have not tried to use any of the others. Any way to run exe's from PE 2.0 in compatability mode?