Can i create Multiple VLANs using MUX

Hi,
Can I create Multiple VLANs using the MUX Sample Driver.
Recently very strange behaviuor is occuring.
I installed and uninstalled the MUX 2-3 times and they are appearing as
MUX Sample Driver # 2 , 3 , 4 , 5 etc.

But I can actually set the OID_GEN_VLAN_ID in only 1 of them using NDISUIO.

Pls Explain ??

What I meas is that why doesnt NDISUIO protocol binds to all Virtual
Miniport Drivers(IM) but only one of them ??

Can I enumerate all the Virtual Network Adapters that the MUX creates ?

TIA
Regards
Tarun

RohitR
Wed Mar 16 17:13:58 CST 2005

------=_NextPart_0001_686D6081
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Re-Installing and Un-Installing MUX driver many times leaves some registry
entries undeleted. Which may cause false mux instances to appear in device
manager/Network Connections Folder. You can clean the registry : Go to :
HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE
10318}. You'll find many entries under this, which you can investigate. Try
to delete any entries manyally if you find them as false. Usually, only the
entry with highest #X is valid (like MUX Sample Driver # 2 , #3 , #4 , #5,
only #5 should be valid, and previous ones may be left overs from previous
un-installations). I hope this helps.

Thanks,
Rohit
------=_NextPart_0001_686D6081
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Re-Installing and Un-Installing MUX driver many times leaves some registry entries undeleted. Which may cause false mux instances to appear in device manager/Network Connections Folder. You can clean the registry : Go to : HKLM\\SYSTEM\\CurrentControlSet\\Control\\Class\\\{4D36E972-E325-11CE-BFC1-08002bE10318\}. You'll find many entries under this, which you can investigate. Try to delete any entries manyally if you find them as false. Usually, only the entry with highest #X is valid (like MUX Sample Driver # 2 , #3 , #4 , #5, only #5 should be valid, and previous ones may be left overs from previous un-installations). I hope this helps.
\par
\par Thanks,
\par Rohit
\par }
------=_NextPart_0001_686D6081--

Tarundeep
Thu Mar 17 14:01:01 CST 2005

Rohit Raina [MS] wrote:
> Re-Installing and Un-Installing MUX driver many times leaves some registry
> entries undeleted. Which may cause false mux instances to appear in device
> manager/Network Connections Folder. You can clean the registry : Go to :
> HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002bE
> 10318}. You'll find many entries under this, which you can investigate. Try
> to delete any entries manyally if you find them as false. Usually, only the
> entry with highest #X is valid (like MUX Sample Driver # 2 , #3 , #4 , #5,
> only #5 should be valid, and previous ones may be left overs from previous
> un-installations). I hope this helps.
>
> Thanks,
> Rohit
ya thanks a lot.