Hi all,
does anybody know what entity (or what part of the IMSAMP’s INF file)
prohibits the direct bindings bypassing IMSAMP?
I mean:
- before IMSAMP installation, the system can have such bindings:
TcpIp -> Ethernet0
TcpIp -> Ethernet1
- the IMSAMP’s INF file creates a virtual NIC device for each real NIC
device - after IMSAMP is installed, the bindings must be:
ImSamp -> Ethernet0
ImSamp -> Ethernet1
TcpIp -> ImSampVirtualEthernet0
TcpIp -> ImSampVirtualEthernet1
- so, what facility blocks the TcpIp -> Ethernet0 binding after ImSamp is
installed?
Another question:
- what are the w2k’s Notify Objects (INetCfgxxx)? Am I right that they
provide a way for a network component developer to insert his/her own binary
code inside the NCPA binding engine? - was there any Notify Objects in Win9x (the w2k’s NCPA is visually like
Win9x one and NOT like NT4’s one)?
regards,
Max
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com