[Bug 32482] New: Windows Sysinternals "PsInfo" tool fails to retrieve "Physical Memory" value from "HKLM\\Hardware\\ResourceMap\\System Resources" registry key

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=32482

             Bug #: 32482
           Summary: Windows Sysinternals "PsInfo" tool fails to retrieve
                    "Physical Memory" value from
                    "HKLM\\Hardware\\ResourceMap\\System Resources"
                    registry key
           Product: Wine
           Version: 1.5.19
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: programs
        AssignedTo: wine-bugs at winehq.org
        ReportedBy: focht at gmx.net
    Classification: Unclassified


Hello folks,

Windows Sysinternals "PsInfo" tool fails to query for some system properties...
Making this bug about "Physical Memory".

Output:

--- snip ---
$ wine ./PsInfo.exe 

PsInfo v1.77 - Local and remote system information viewer
Copyright (C) 2001-2009 Mark Russinovich
Sysinternals - www.sysinternals.com

Querying information for nexus4...fixme:ole:CoInitializeSecurity
((nil),-1,(nil),(nil),0,3,(nil),0,(nil)) - stub!
System information for \\nexus4:                                               
Uptime:                    Error reading uptime
Kernel version:            Microsoft Windows XP, Uniprocessor Free
Product type:              Professional
Product version:           5.1
Service pack:              3
Kernel build number:       2600
Registered organization:   
Registered owner:          
IE version:                6.0000
System root:               C:\windows
Processors:                4
Processor speed:           2.6 GHz
Processor type:            Intel(R) Pentium(R) 4 CPU
Physical memory:           0 MB
Video driver:              
--- snip ---

Trace log (processor info = ok, physmem = missing):

--- snip ---
...
0024:Call advapi32.RegOpenKeyExW(80000002,0042f520
L"Hardware\\Description\\System\\CentralProcessor\\0",00000000,00020019,0032f96c)
ret=00404a33
0024:Ret  advapi32.RegOpenKeyExW() retval=00000000 ret=00404a33
0024:Call advapi32.RegQueryValueExW(00000054,0042f510
L"~MHz",00000000,0032f970,0043c0e4,0032f968) ret=00404a58
0024:Ret  advapi32.RegQueryValueExW() retval=00000000 ret=00404a58
0024:Call advapi32.RegQueryValueExW(00000054,0042f4e8
L"ProcessorNameString",00000000,0032f970,0043d538,0032f968) ret=00404a81
0024:Ret  advapi32.RegQueryValueExW() retval=00000000 ret=00404a81
0024:Call advapi32.RegCloseKey(00000054) ret=00404a95
0024:Ret  advapi32.RegCloseKey() retval=00000000 ret=00404a95
0024:Call advapi32.RegOpenKeyW(80000002,0042f210
L"Hardware\\ResourceMap\\System Resources\\Physical Memory",0032f930)
ret=00403b17
0024:Ret  advapi32.RegOpenKeyW() retval=00000002 ret=00403b17 
--- snip ---

Wineboot already creates a couple of hardware related registry keys:

Source:
http://source.winehq.org/git/wine.git/blob/7f9dfe273a80d31e3f8c5bd0c100c81370aa6f38:/programs/wineboot/wineboot.c#l168

Might be useful to add "Hardware\\ResourceMap\\System Resources" key here along
with actual physmem value.

Regards

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.