Hi, > Thanks Loris, > > I guess the safest approach is to just look in the registry and then warn > the user in case a protocol is assigned. I presume other protocols will show > up here too, the most likely being NetBEUI and IPX. Is this correct?
Yes. Essentially, every protocol must have an entry under the Services hive. > Also > what about Win9x? Will it have the info in the same spot? Sorry, I've not a precise idea. The only thing that I remember is that the win9x registry is a huge mess from this point of view. I don't have a win9x machine at hand, but I remember that the information about the interfaces and protocols is somewhere in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\class\net HKEY_LOCAL_MACHINE\Enum\Network\MSTCP HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\class Loris > Jens. > > > > For TCP/IP, I think you can look at the > > > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TcpipHKEY_LOCAL_MACHINE > > \SYSTEM\CurrentControlSet\Services\Tcpip registry hive, in particular the > > linkage subkey. > > It should also be possible to modify the TCP behavior modifying this key, > > however I think it's a quite dangerous activity... > > > > Loris > > > > > I have another question. Since I am using the packet stuff in place of a > > > standard protocol I am disabling or removing these in the windows > network > > > settings. However, this doesn't prevent the user from putting them back > > > again. So where can I see which protocols are assigned to which adapter > > and > > > can I safely kick them out in code? > > > > > > Thanks, > > > > > > Jens. > > > > > > > > > > > > > > >
