ok thanks

I found out what the problem was i cant get it to work with the wep but without it it works fine :S so im tryna fix that now

Hangdog, thanks for the input. I didn't realize that it was as easy as changing the permissions on the rc files to prevent loading. I actually did that with an old ifcfg-wlan0 file on my Mandrake system before I dumped it. I'm really liking Slackware--I can't believe how much control you have over it...it's the perfect OS if you can actually figure out what the heck you are doing. Of course, I would still be pulling out my hair and reinstalling Mandrake if it wasn't for the help of people like you.
Anyway, I think I'm going to stick wiith 2.4.26 for now. From what I've read it's a great kernel, and so far it's been doing everything I need without trouble. And I'd rather not tackle something as major as recompiling the kernel yet--I'm still learning. Although the howto's in the Slackware forum make it sound a lot easier than I thought it would be.
MikeyMike, I've heard that the Fedora 2 core can cause some problems with modprobing ndiswrapper, but if you do have the driver loaded, you should be able to get it running by following the commands in the INSTALL file that comes with ndiswrapper. Then all it should take is running dhclient or dhcpcd. Wait a sec...You are using ndiswrapper, right? I can't remember if you said what drivers you were using. If you aren't using ndiswrapper, then I am of no help whatsoever. Like Hangdog said, there is a great thread specifically dealing with your card--check it out. If I recall, someone put together a really thorough how-to article for the card. Search this site--there's plenty of info here.

yup i have ndiswrapper Im jus havin a problem with connectin with a network with WEP so i have to keep switchen to windows to use the internet... can you pm me the suggestion you have for me to get the WEP to work cause it works fine when i turn off the WEP but i need WEP to be on

Thanks

How are you trying to set the WEP key? You should be able to use iwconfig wlan0 key YourWEPKeyHere

If that isn't doing the trick, post the details of what you are doing and what the outputs of iwconfig are.

ok im settin it like

iwconfig wlan0 key open MyKEY

and cause i have an open connection and it dont work on restricted

but if i do it the way you said will it still work?

Well, the only way to know for sure it to try it and see.

By the way, when you are asking for help, details are key. Since you are the only one sitting at your keyboard, you do need to post the outputs of what you are doing.

MikeyMike, try running:
iwlist wlan0 scanning
That should tell you all the settings that your router needs...
Also, when you have your key and essid set, iwconfig wlan0 should show you something other than all 00:00:00... for your AP. Then ifconfig wlan0 up should let you get an IP via DHCP when you run dhclient or dhcpcd. And make sure to set the essid last. Like Hangdog said, post your output... The output from iwconfig and ifconfig will usually tell you where you're hanging up.

wlan0 IEEE 802.11g ESSID:"My Essid" Nickname:"localhost.localdomain"
Mode:Managed Frequency:2.437GHz Access Point:
Bit Rate=24Mb/s Tx-Power:25 dBm
RTS thr=2347 B Fragment thr=2346 B
Encryption key:4630-3933-2D44-3137-342D-4538-3632-2D46-4335-422D-3231-4133-2D38-4239-462D-4130 Security mode:restricted
Power Managementff
Link Quality:99/100 Signal level:-70 dBm Noise level:-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:50 Invalid misc:3211 Missed beacon:0

ok theres my output I changed some of the stuff for obvious reasons but for some reason the key changes and it turns to restrictive?

also im a newbie so what is "dhclient or dhcpcd"

thanks for the help

Well, even with the restricted setting, it looks like you are seeing the access point. I think this is good.

Dhclient and dhcpcd are programs used to look for a dhcp server and request an IP address. As far as I know, dhcpcd is pretty much used only in Slackware (I may be wrong about that though) and dhclient is used most everywhere else. Some distros may have both. In any case, the syntax is similar;

dhclient wlan0
dhcpcd wlan0

You may want to have a look at the man pages for whichever one you use (probaly dhclient) as there are probably flags you can set to make it more verbose about what it is doing.

thank you so much without yall I would not have got it to work... Thanks so much im really thankfull for the help...

that dhclient wlan0 thing got it to work btw