Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Windos
win32.3rdparty
win32.directx.audio
win32.directx.ddk
win32.directx.graphics
win32.directx.input
win32.directx.managed
win32.directx.misc
win32.directx.networking
win32.directx.sdk
win32.directx.video
win32.dirx.grap.shaders
win32.gdi
win32.international
win32.kernel
win32.messaging
win32.mmedia
win32.networks
win32.ole
win32.rtc
win32.tapi
win32.tapi.beta
win32.tools
win32.ui
win32.wince
win32.wmi
windows.mediacenter
winfx.aero
winfx.announcements
winfx.avalon
winfx.collaboration
winfx.fundamentals
winfx.general
winfx.indigo
winfx.sdk
winfx.winfs
  
 
date: Mon, 26 May 2008 14:30:50 -0700,    group: microsoft.public.win32.programmer.wmi        back       


Data Derived From Where?   
When using the Win32_ComputerSystem object to obtain the "model" property 
value --where does WMI derive this value from? The registry? The oeminfo.ini 
file? Anybody know?

JW
date: Mon, 26 May 2008 14:30:50 -0700   author:   Jerry West

Re: Data Derived From Where?   
Interesting question. I got curious and tried running
a script with Regmon and Filemon running. It turned
out that WMI retrieved a great deal of system data
from the Registry, which it didn't need to process the
WMI call in the script. (I've never understood the stunning
volume of repetitive and irrelevant Registry calls made
by Microsoft products.) As far as I could tell, there's no
model number in that retrieved data.

   On my system the Model property accurately returns
the motherboard model. ("MS-6330" from MSI.) The box
is homemade, so there's certainly no OEM data. And the
data doesn't seem to be in the Registry. I'd guess that
it's probably retrieved from the data provided by the BIOS
at boot. My understanding is that it's really the BIOS that
provides most of the hardware information to begin with.
Windows just processes what the BIOS tells it. On Win9x,
if you read system memory starting from about the 1MB
offset, you can return a large block of BIOS data. For instance,
the BIOS firmware date starts at &HFFFF5 as a plain text
string. I imagine a similar block of data is available on WinNT
systems, but 3rd-party software is not allowed access
on NT. Maybe WMI is using its own device driver to
retrieve that data.


> When using the Win32_ComputerSystem object to obtain the "model" property
> value --where does WMI derive this value from? The registry? The
oeminfo.ini
> file? Anybody know?
>
> JW
>
>
date: Tue, 27 May 2008 00:18:57 -0400   author:   mayayana

Re: Data Derived From Where?   
I tried testing this as well....the registry value was precisely the same 
value reported by WMI --all the way down to the 16 extra spaces to the right 
of the value. Interestingly, every computer I looked at had these 16 extra 
spaces to the right of the model value. Admittedly I have all Dells but the 
one Gateway I checked also had this unusual attribute. I only mention this 
because it was just rather odd, perhaps even suggestive that wherever this 
value gets populated from for the registry and where WMI obtains it from is 
the same location. Like you, my machines do not have a oeminfo.ini file so 
that wouldn't be it. The next logical assumption is the BIOs itself. But I 
could not find such a string within the BIOs. Deleting the registry value 
had no effect on what WMI reported for the value.


JW


"mayayana"  wrote in message 
news:%230td0C7vIHA.1768@TK2MSFTNGP03.phx.gbl...
>  Interesting question. I got curious and tried running
> a script with Regmon and Filemon running. It turned
> out that WMI retrieved a great deal of system data
> from the Registry, which it didn't need to process the
> WMI call in the script. (I've never understood the stunning
> volume of repetitive and irrelevant Registry calls made
> by Microsoft products.) As far as I could tell, there's no
> model number in that retrieved data.
>
>   On my system the Model property accurately returns
> the motherboard model. ("MS-6330" from MSI.) The box
> is homemade, so there's certainly no OEM data. And the
> data doesn't seem to be in the Registry. I'd guess that
> it's probably retrieved from the data provided by the BIOS
> at boot. My understanding is that it's really the BIOS that
> provides most of the hardware information to begin with.
> Windows just processes what the BIOS tells it. On Win9x,
> if you read system memory starting from about the 1MB
> offset, you can return a large block of BIOS data. For instance,
> the BIOS firmware date starts at &HFFFF5 as a plain text
> string. I imagine a similar block of data is available on WinNT
> systems, but 3rd-party software is not allowed access
> on NT. Maybe WMI is using its own device driver to
> retrieve that data.
>
>
>> When using the Win32_ComputerSystem object to obtain the "model" property
>> value --where does WMI derive this value from? The registry? The
> oeminfo.ini
>> file? Anybody know?
>>
>> JW
>>
>>
>
>
date: Tue, 27 May 2008 07:50:24 -0700   author:   Jerry West

Re: Data Derived From Where?   
This is the value of Win32_ComputerSystem.Model MappingStrings qualifier:

SMBIOS|Type 1|System Information|Product Name

SMBIOS specification:

http://www.dmtf.org/standards/published_documents/DSP0134v2.5Final.pdf


-- 
urkec


"Jerry West" wrote:

> I tried testing this as well....the registry value was precisely the same 
> value reported by WMI --all the way down to the 16 extra spaces to the right 
> of the value. Interestingly, every computer I looked at had these 16 extra 
> spaces to the right of the model value. Admittedly I have all Dells but the 
> one Gateway I checked also had this unusual attribute. I only mention this 
> because it was just rather odd, perhaps even suggestive that wherever this 
> value gets populated from for the registry and where WMI obtains it from is 
> the same location. Like you, my machines do not have a oeminfo.ini file so 
> that wouldn't be it. The next logical assumption is the BIOs itself. But I 
> could not find such a string within the BIOs. Deleting the registry value 
> had no effect on what WMI reported for the value.
> 
> 
> JW
> 
> 
> "mayayana"  wrote in message 
> news:%230td0C7vIHA.1768@TK2MSFTNGP03.phx.gbl...
> >  Interesting question. I got curious and tried running
> > a script with Regmon and Filemon running. It turned
> > out that WMI retrieved a great deal of system data
> > from the Registry, which it didn't need to process the
> > WMI call in the script. (I've never understood the stunning
> > volume of repetitive and irrelevant Registry calls made
> > by Microsoft products.) As far as I could tell, there's no
> > model number in that retrieved data.
> >
> >   On my system the Model property accurately returns
> > the motherboard model. ("MS-6330" from MSI.) The box
> > is homemade, so there's certainly no OEM data. And the
> > data doesn't seem to be in the Registry. I'd guess that
> > it's probably retrieved from the data provided by the BIOS
> > at boot. My understanding is that it's really the BIOS that
> > provides most of the hardware information to begin with.
> > Windows just processes what the BIOS tells it. On Win9x,
> > if you read system memory starting from about the 1MB
> > offset, you can return a large block of BIOS data. For instance,
> > the BIOS firmware date starts at &HFFFF5 as a plain text
> > string. I imagine a similar block of data is available on WinNT
> > systems, but 3rd-party software is not allowed access
> > on NT. Maybe WMI is using its own device driver to
> > retrieve that data.
> >
> >
> >> When using the Win32_ComputerSystem object to obtain the "model" property
> >> value --where does WMI derive this value from? The registry? The
> > oeminfo.ini
> >> file? Anybody know?
> >>
> >> JW
> >>
> >>
> >
> > 
> 
> 
>
date: Tue, 27 May 2008 13:17:44 -0700   author:   urkec

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us