Did you download both the .inf and .sys files for the windows ndis driver?
This site's wiki has a wireless section as well that covers installing and using ndiswrapper.
I wonder if your installation of ndiswrapper and the ndiswrapper kernel module was completed successfully.
First, the kernel module doesn't seem to be a tar file as "Lenard" posted. Try:
sudo gunzip ndiswrapper.ko.gz
instead. This will uncompress the file to "ndiswrapper.ko". Just for your information, .o are object files. .ko files indicate to you that the file is a kernel module as well.
Look at the output of "uname -r". Does it display "22.214.171.124.tex1.lve". This is the version of your running kernel. For each kernel installed, there is a corresponding /lib/modules/<version>/ directory where the kernel modules for that kernel are installed. If this is your only kernel, then the answer is probably yes.
If the installation of ndiswrapper wasn't completed successfully, try running these commands, just in case:
sudo /sbin/depmod -a
sudo /usr/sbin/ndiswrapper -m
The first one should have been done during the installation of ndiswrapper. The second one may not do anything useful in your case. It adds new library paths that may have been added during an installation. It may actually be done periodically in the background or when you boot. But doing it anyway manually sometimes helps.
The third command installs an /etc/modprobe.d/ndiswrapper file which adds an alias for wlan0. It may instead add the line to /etc/modprobe.conf. If it was already done, it will tell you so, and the error message saying the alias exists isn't anything to worry about.
Being a USB device, your system also needs USB related kernel modules loaded. They probably are, but it is something to consider. A listing from "sudo /sbin/lsmod" will list the kernel modules that are loaded. If the "modprobe ndiswrapper" part succeeds, you will see that one of the listed modules is "ndiswrapper".
ps. I wrote this from memory. I hope I got the paths to lsmod, ndiswrapper, depmod and ldconfig correct. You may also cd to root first instead of using "sudo". Most often, to use sudo, you may need to add yourself to the "wheel" group, and then run "visudo" as root to allow the wheel group to run "sudo". This entails finding the commented line and removing the initial "# " characters to uncomment it. After that sudo should work for you. Some distro's like Ubuntu will have this part done already, and using Ubuntu, you need to use sudo to run commands as root. This is a good thing actually.
Display the version of ndiswrapper that you are using. There is one version that had problems and wouldn't load in the corresponding kernel module. I know this because it is the version that SuSE 10.1 used initially. I uninstalled the systems ndiswrapper version and ndiswrapper kernel module and installed ndiswrapper from source. This sites wiki and the ndiswrapper wiki have instructions to do that.
Make sure you didn't download a windows driver for 64 bit if you have a 32 bit computer. Also, if you still have problems wrapper the windows driver, or the driver doesn't seem to work, you can go to the ndiswrapper wiki
, locate your device and download the driver that is known to work from the supplied link.