Why you removed ndiswrapper even before being sure new version was perfectly working? I have some problems with wep/wpa and new ndiswrapper version, I had to edit wpa_supplicant init script to remove/reload ndiswrapper module on each restart and I must reload it some times before seeing my pc connected (I get this error in messages log: ndiswrapper (iw_set_encr:759): removing encryption key 0 failed (C0010015)). I think it's something related to new ndiswrapper functions so I would prefer to have 1.1 version available on portage. Thanks. Reproducible: Always Steps to Reproduce: 1. 2. 3.
If you don't report a bug. How can we know? ndiswrapper-1.2 went through a period of ~arch testing. And then it was moved into stable. No bug reports. The old version is outdated, no longer supported upstream and is known to contain issues. It does not properly work with the latest kernels and it does not work with suspend2, a popular kernel patch. It was more then logical to remove it. So don't sound amazed. As always with ndiswrapper. 99.99999% of the issues are with the Windows drivers. It's a known thing that in between ndiswrapper revisions you have to change Windows drivers sometimes. Because sometimes the new functionality of ndiswrapper calls on buggy Windows driver code.
I understand, but as you said often new release of ndiswrapper have problems that are often well hidden. That's why I would prefer to have some older unsupported (and masked) ebuild so who discover some problems with latest versions can go on working with older ones. I'll post my problem to ndiswrapper team! Thanks!
