L
lorax26
Guest
After I installed hl2.exe I noticed a little more I/O activity on my box than usual. After running task manager and selecting the I/O Reads column and I/O writes column from view-select columns, I now see that it is constantly reading and writing and the memory constantly grows.
Out of curiosity I downloaded procmon from sysinternals.com to see exactly what it was doing. Usually I would use filemon but filemon does not work with my version of Vista.
Steam.exe is constantly accessing the following registry keys:
HKCU\Software\Valve\Steam
HKCU\Software\Valve\Steam\LastSteamExecutionTime
HKCU\Software\Valve\Steam\steam.exe\UpTimeMostRecent
In the past 3 1/2 minutes my used memory has grown from 7+MB to 12+MB, an additional 20,000 reads have been posted and an additional 30,000 writes have been posted.
Any idea why these keys are being monitored and why so often?
My work around for now is to not start steam.exe unil I want to play but I would still like to know if this behavior is experienced by anyone else.
I'm running Vista x64 and hl2 runs great in 64bit mode but since steam is a 32bit app maybe this has something to do with the WOW emulation used by vista x64 to run 32bit apps.
Anyone else seeing the same behavior?
Out of curiosity I downloaded procmon from sysinternals.com to see exactly what it was doing. Usually I would use filemon but filemon does not work with my version of Vista.
Steam.exe is constantly accessing the following registry keys:
HKCU\Software\Valve\Steam
HKCU\Software\Valve\Steam\LastSteamExecutionTime
HKCU\Software\Valve\Steam\steam.exe\UpTimeMostRecent
In the past 3 1/2 minutes my used memory has grown from 7+MB to 12+MB, an additional 20,000 reads have been posted and an additional 30,000 writes have been posted.
Any idea why these keys are being monitored and why so often?
My work around for now is to not start steam.exe unil I want to play but I would still like to know if this behavior is experienced by anyone else.
I'm running Vista x64 and hl2 runs great in 64bit mode but since steam is a 32bit app maybe this has something to do with the WOW emulation used by vista x64 to run 32bit apps.
Anyone else seeing the same behavior?
