it's either the kernel's netcode or ndiswrapper module that ships with the kernel. i doubt the ndiswrapper library itself is to blame since the results vary across kernels while keeping the same ndiswrapper version.
i have 3 kernels installed on maverick, and below represent my observations.
2.6.32-24: ndiswrapper connects
2.6.34-5: ndiwsrapper connects if i kick it a bit
2.6.35-13: ndiswrapper can only scan
it's either the kernel's netcode or ndiswrapper module that ships with the kernel. i doubt the ndiswrapper library itself is to blame since the results vary across kernels while keeping the same ndiswrapper version.
i have 3 kernels installed on maverick, and below represent my observations.
2.6.32-24: ndiswrapper connects
2.6.34-5: ndiwsrapper connects if i kick it a bit
2.6.35-13: ndiswrapper can only scan