Re: WMI usability
- From: "Sam Hobbs" <samuel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 7 May 2006 23:48:32 -0700
"Goppi" <Goppi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0A32FB16-4F08-4F05-AD50-F15ECAA20FA2@xxxxxxxxxxxxxxxx
Ok, I correct myself - it seems the only other efficient method to get
thesesettings is through the registry. You could perhaps hack the IO ports
on
the NIC card, but I don't consider this as the way to go.
My preference and understanding is the opposite, but I am not an expert in
this area. If the registry is a documented solution then it is a good
solution. Unless the registry is documented, I consider it to be a hack.
To "hack the IO ports on the NIC card" in NT/2000/XP and above it is
necessary to write a device driver. There are at least two other
possibilities that are documented either officially or unofficially. First,
DeviceIoControl is the the function for interfacing with a device driver,
and it is likely the data is available that way. Another possibility for
networks is software that implements low-level access to networks and such.
.
- References:
- Re: WMI usability
- From: Sam Hobbs
- Re: WMI usability
- From: Goppi
- Re: WMI usability
- Prev by Date: Re: WMI usability
- Next by Date: Virus protection info on windows XP
- Previous by thread: Re: WMI usability
- Next by thread: Re: WMI usability
- Index(es):
Relevant Pages
|