You still lack a couple of basic techniques for handling a Linux computer - this is not meant in a negative way. It's just that I see that you're very new at Linux.
I think that this medium, a web forum, is too slow to help you in an appropriate manner. You might get faster help on an interactive medium like IRC.

Try the ##slackware channel on the Freenode network, there are always people online who can guide you.

And as an answer to your question: did you install ndiswrapper at all, before you downloaded a Windows driver for your card? The ndiswrapper is not part of Slackware.
You can however try a ready made package if you want. Take this one for instance (look in the "pkg" directory and pick a package with a version number that matches your kernel).
And before you ask :-) Your kernel's version kan be determined by running . A package of ndiswrapper-1.4 for a kernel with version 2.4.31 would be: ndiswrapper-1.4_2.4.31-i486-1.tgz
Hope this helps you.

PS:
If you compile ndiswrapper yourself, it will generate a module for your own kernel automatically.

Eric

In answer to your question:

did you install ndiswrapper at all, before you downloaded a Windows driver for your card?

I tried, but was unsuccessful. I found out my kernel version--2.4.26. And I entered:

ndiswrapper-1.10_2.4.26.tar.gz*

and I got the error message:

:command not found

So I went to the website you referenced above, and I didn't see an ndiswrapper version for my kernel version.

Any other suggestions?

How do I compile ndiswrapper?

It might be easiest to use my build script:
Download the files at this URL like this:
Then "cd" into the build subdirectory that has been created in the current directory and run the script that builds ndiswrapper for your kernel:
The ready-made package can be found in the /tmp directory after the build finishes. You can install that package using: A requirement for building the package, is that you have the sources for your kernel installed (which means that you should have installed the "kernel-sources" package; when you choose for a full install while installing Slackware on your computer, this package will have been installed for you).

I'm updating the build script now, and uploading a package for ndiswrapper version 1.10.
When you mentioned a 2.4.26 kernel, that would indicate you're running Slackware 10.0. Why such an old Slackware when you0re obviously just learning Linux? Slackware 10.2 will make like a lot easier for you than 10.0, especially when your ndiswrapper finally works and the next step (configuring your wireless interface) announces itself...

Eric

I won't be able to download to my linux box until I get my network card working with ndiswrapper. So I would presume that I would have to download one of those files to CD-ROM then copy it to my directory that contains the network adapter files and everything else? Is this right? Then what do I do? Thanks!

By the way, I am using Slackware 10.1, just for the record.

johnvillegas:

I've been reading your posts, and I feel your pain. Maybe a Linix dummy, me, can offer some advice. Experts have tried to help you, but it is apparent you don't understand. It's also apparent that you have little knowlege of Linux, and you're digging yourself deeper into a hole.

Stop what you are trying to do and start from the beginning. Your network will wait. You will have to learn to walk before you run. Get the book "Slackware Linux Essentials." If you will do a search, on this forum, for a post titled "Comprehensive Linux Guide," you will find a whole list of reading material. Sometimes an author will leave something out, and you'll need to look elsewhere. I spent hours with Google before I got it straight how to set the printer up with CUPS.

Try not to depend on answers from others. You won't learn much that way. You will learn (hopefully) from your mistakes and by doing it yourself. If you screw up badly, so you do another install. God knows, I've done a half dozen so far.

You'll need to edit files, and it looked like you were trying to use VI. That and EMACS are complex editors. Use JOE which is a simple WYSIWYG editor. All help is right on screen, and with three commands you can bring up a file, edit it, save it, and exit.

Hope I haven't been offensive. I started 25 years ago on a homemade CP/M computer, no internet forums, and little documentation. Just stating what has worked for me and at this point, as I said before, I'm a Linux dummy hoping to someday run with it.

Try to read all that was said in this thread. You will be able to find out for yourself what you'll have to do, and please PLEASE read some documentation too. You do not seem to understand the difference in the two separate steps you have to make:

• download ndiswrapper sources, compile and install ndiswrapper
• use ndiswrapper to install the Windows driver files, so that your wireless card can be activated.

Anyway, I can give you some fresh info.
First make sure you download the ndiswrapper files using the commands I showed you (on a computer with Internet access). Then use a CDROM or a USB stick, or a floppy for my part, to transfer all that to your wireless PC, change to the directory where you copied the files and run the ndiswrapper.SlackBuild script to compile the package. Install the package (found in /tmp after the compilation finishes) using installpkg, and run this command:
If that does not complain, check if your network interface has been created: run . You should see an "eth" interface there. If the wireless card is the only network card, you should see a device "eth0". Otherwise, you will see a new eth1, or eth2, depending on how many network interfaces you already had (ndiswrapper just takes the next higher unused number).
Then, make sure that this will still work after a reboot: run
Your card is now ready to be configured. Use the command to do that - it is a dialog driven program that generates a network configuration file based on what you answer.

Eric

Looks like everything worked. Many thanks! But I already ran netconfig before I started all of the ndiswrapper stuff. Do I need to do it again?

Also, I tried to ping google.com to see if I got outside, and I got an unknown host error.