actually my wireless card is not supported either, so I\'m using ndiswrapper and it works fine for me.
Has anyone here actually got NDisWrapper to work? If so which distro did you use and which dependecies did you have to download?
Why do I get the feeling that you\'re not reading that carefully?
Yes, I have gotten Ndiswrapper to work. Several times from the source tarball they offer, and once via the gentoo ebuild. Distros would be Fedora Core 1 and 2, and Gentoo. Ndiswrapper has no dependencies to run, but you\'ll need recode to convert the windows driver from hex to ascii.
Gee, so in all your years of linus you havnt had a single error. Not even one. In what 4 years of computing you have never witness a dialog box with the error symbol come up? I find that hard to believe. I had 5 in the first few days of trying linux.
What dialog box? Linux on its own has no dialouge boxes, sounds to me like your having a problem with your desktop environment. That is not Linux\'s fault. My window manager (fvwm) has no dialogue boxes, but yeah, no errors.
I think the main point is that linux takes forever to configure and it takes a pretty comprehensive understanding. So no, it\'s not for everyone, you have to be willing to struggle with it. But once you know it, it is a far more flexible, customizeable, and stable OS.
EDIT: Spelling, content
EDIT: Whoops. Some things I forgot to mention about ndiswrapper, that really need to be said, both in the interest of complete honesty and of helping you out should you ever elect to give it another shot:
1. ndiswrapper requires a 2.6 kernel
2. ndiswrapper requires that you have kernel source installed. You do not have this by default in many distros, which may be why you could not get it to build.
3. /usr/src/linux must be a symbolic link to the source of the kernel that you are using. I think something else has to point there, too, but I forget what. It\'s in the ndiswrapper documentation, anyway.
4. While I never had any trouble compiling it, (until recently, see 5) for the longest time any version of ndiswrapper past .08 (including the gentoo ebuilds) would give me a run-time kernel panic when I tried to modprobe it. For that reason, I used .08 for a very long time.
5. When I upgraded my kernel to 2.6.11, my version .08 would no longer build. I crossed my fingers and held my breath and tried the latest gentoo ebuild, and it worked.
6. You will need both the .inf and the .sys part of the windows driver. Use recode to convert the .inf file to an ascii file, and it must reside in the same directory as the .sys file. When you give ndiswrapper the path to the driver, give it the ascii file.