I've used IPHpler on Windows 95!

[Zi-Wei Chiou]

There is a sample named IPConfig which comes with Platform SDK beta 3.
It's located at "samples/netds/IPHelp/IPConig". At the first glance, I
thought this
is the source code of the IPCONFIG.EXE utility under Windows NT, but I was
wrong. They are entire different program although they have the same name
and
almost identical output. The IPConfig sample exploits IPHelper functions to
get the
network information, whereas I don't know how IPCONFIG.EXE does it. (The
DEPENDS.EXE told that IPCONFIG.EXE does not link IPHLPAPI.DLL).

I sucessfully build the IPConfig (thanks, Tim), and I hope that it runs
under Windows
NT, Windows 95 and Windows 98:

[1]On Windows NT: Strangely, the return value of GetNetworkParams returns an
error code of 50:
//
// MessageId: ERROR_NOT_SUPPORTED
//
// MessageText:
//
// The network request is not supported.
//
#define ERROR_NOT_SUPPORTED 50L

Why?! My Windows NT 4.0 Workstation had the SP4 installed, which installed
the
IPHLPAPI.DLL also.

[2]On Windows 98: The sample runs perfectly well on Windows 98, as expected.

[3]On Windows 95: Yes, I did test it on Windows 95 and anticipated it works.
I wonder
why the IPHelper is not supported on Windows 95, if it's considered a part
of the
Winsock2 (see the documentation on
http://www.winsock.com/winsock/ws2_sdk.htm ).

I copy the IPHLPAPI.DLL and IPCFGDLL.DLL from my Windows 98/system
subdirectory to Windows 95, and expect the IPConfig runs. It does!

Any comments?

[Felix Kasza [MVP]]

Zi-Wei,

> I copy the IPHLPAPI.DLL and IPCFGDLL.DLL from my Windows 98/system
> subdirectory to Windows 95, and expect the IPConfig runs. It does!
>
> Any comments?

Yes -- you'll never know when or how it fails ...

--

Cheers,

Felix.

If you post a reply, kindly refrain from emailing it, too.
Note to spammers: fel...@mvps.org is my real email address.
No anti-spam address here. Just one comment: IN YOUR FACE!