These drivers are different by their architecture and only one of them can be installed, otherwise you meet a conflict conditions (both drivers share the same name).
It does not really matters which of the drivers is to use for XP, NDIS hook is easier to install but requires system reboot. While NDIS IM is more complex to install but in most cases reboot is not needed.
If i want to install the driver through snetcfg there we are specifying the names like ndisrd.inf and ndisrd_m.inf these relate to which driver exactly like IM driver or hook driver.
Also one more question if i install hook driver it will not display in Network properties?
If i want to install the driver through snetcfg there we are specifying the names like ndisrd.inf and ndisrd_m.inf these relate to which driver exactly like IM driver or hook driver.
NDIS IM
Also one more question if i install hook driver it will not display in Network properties?
Hook driver won’t be displayed in network connection properties. However, it worth to mention that NDIS IM driver also can be hidden from the network connection properties if needed.