the DLL

NTDEV
1

Can someone throw some light on how the notifyobj if MUX works. Who loads
teh DLL and in which process context? I tried process explorer, without any
results!

2

The MUX driver INF file must reference the NotifyObject DLL. When NDIS load
the MUX driver the INF is examined. If a NotifyObject is found in the INF
file, then NDIS will call it before actually loading the driver.

Examine the WDK samples carefully. If you INF is wrong, then the
NotifyObject won’t be called.

Examining the setupapi log files should be helpful. Use Windows Search to
find them. I forget where under the Windows folder they reside.

Also, http://www/wd-3.com has an article by Stepahn Wolf about “Getting
Trace from NETCFG.DLL”

Good luck,

Thomas F. Divine

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Friday, January 05, 2007 2:04 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] the DLL

Can someone throw some light on how the notifyobj if MUX works. Who loads
teh DLL and in which process context? I tried process explorer, without any
results! — Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

3

Thomas,

Thanks for the replies.

The MUX driver INF file must reference the NotifyObject DLL.

There are two INF files, which one are you referring to?

If a NotifyObject is found in the INF file, then NDIS will call it before
actually loading the driver.

Where in the INF is all this specified?

Examine the WDK samples carefully. If you INF is wrong, then the
NotifyObject won’t be called.

I have the Win2K3 SP1 DDK, would that do?

Examining the setupapi log files should be helpful. Use Windows Search to
find them. I forget where under the Windows folder they >reside?

What are the names of these log files?

A P

4

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Friday, January 05, 2007 3:15 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] the DLL

Thomas,

Thanks for the replies.

The MUX driver INF file must reference the NotifyObject DLL.

There are two INF files, which one are you referring to?

[PCAUSA] That would be muxp.inf.

If a NotifyObject is found in the INF file, then NDIS will call it before
actually loading the driver.

Where in the INF is all this specified?

[PCAUSA] Please look in the INF file.

Examine the WDK samples carefully. If you INF is wrong, then the
NotifyObject won’t be called.

I have the Win2K3 SP1 DDK, would that do?

[PCAUSA] Yes. Read about the MUX sample.

Examining the setupapi log files should be helpful. Use Windows Search to
find them. I forget where under the Windows folder they >reside.

What are the names of these log files?

[PCAUSA] setupapi.log

Thomas F. Divine

A P

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

5

Thomas, others,

Thanks for the responses and your patience.

  1. what is the mux_mp.inf used for then?

  2. > [PCAUSA] Please look in the INF file.
    Sorry, I couldn’t locate it, maybe because I don;t een know what exactly I
    am looking for!

  3. Mux.dll is also called at system boot time. Is this correct, so set up
    the objects of the adapters. Is that correct?

  4. Can you tell me, after reading I find that most of the operations are
    done in the user mode DLL mux.dll. It is called at install time and also at
    system boot time, the COM interfaces it extends are for this purpose. So
    does this mean, that NDIS aalso, is like printer and video drivers, where a
    lot of the driver part is in user land?

  5. Can some one give me a pointer, as to how when an application needs to
    connect to the internet the call gets translated? Does winsock use COM
    internally? Else what are the interfaces for? i am sorry, I have been pushed
    into this, without any prior knowledge, and hence some stupid questions.

regards,

A P

6

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of A P
Sent: Friday, January 05, 2007 10:43 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] the DLL

Thomas, others,

Thanks for the responses and your patience.

  1. what is the mux_mp.inf used for then?

  2. > [PCAUSA] Please look in the INF file.

Sorry, I couldn’t locate it, maybe because I don;t een know what exactly I
am looking for!

[PCAUSA] Search for “dll” in the INF file.

Read the MUX NotifyObject code.

Read the WDK topics on installing NDIS drivers.

  1. Mux.dll is also called at system boot time. Is this correct, so set up
    the objects of the adapters. Is that correct?

[PCAUSA] Not as far as I know.

It is called at initial installation time. It is also called when the
network configuration is changed by adding and removing adapters, etc.

  1. Can you tell me, after reading I find that most of the operations are
    done in the user mode DLL mux.dll. It is called at install time and also at
    system boot time, the COM interfaces it extends are for this purpose. So
    does this mean, that NDIS aalso, is like printer and video drivers, where a
    lot of the driver part is in user land?

[PCAUSA] Not called at boot time.

The notify object is not part of the NDIS driver. Instead, it supports the
user-mode network configuration operations related to your driver. When
network components are added or removed the notify object can veto bindings,
insure that your adapter is bound only to physical miniports, etc. After the
configuration operations are complete the notify object is unloaded and the
decisions that it has made will be used to determine whether your driver
should be loaded and what it should bind to.

  1. Can some one give me a pointer, as to how when an application needs to
    connect to the internet the call gets translated? Does winsock use COM
    internally? Else what are the interfaces for? i am sorry, I have been pushed
    into this, without any prior knowledge, and hence some stupid questions.

[PCAUSA] No questions are stupid.

BUT please read the MSDN topics about network architecture.

AND if you are interested in user-mode and Winsock then this is not the
right mailing list for you.

Thomas F. Divine

regards,

A P

— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 To unsubscribe, visit the List
Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

7

> connect to the internet the call gets translated? Does winsock use COM

internally?

No. It uses IOCTLs to afd.sys in the kernel.

–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com