Greetings all, well as the heading says this is a very beta release. Would prefer just for the moment for those that are familar with wireless and using nidswrapper to test.

I downloaded the ndiswrapper tarball for vector linux, just to get easy access to all the windows driver files. I then installed each one for puppy and tarred them all up. As you can imagine this is a rather large download, around 3megs but should support many cards.

Once I know the scripts work nicely, no sanity checking for the moment as I just started scripting around christmas last year and have only attempted some rather basic stuff from time to time, I would like to split the scripts and seperate the drivers so it is only a small download.My idea would to be to name each file by it's pci-id and have a table and download link.....

My upload should complete in about 30 minutes, so please wait.

Please read the README.TXT, which is installed into /root/my-documents/wifi

Have just looked so far, bladehunter, but looks good to me.
Folks had better be aware that they need to have ndiswrapper and Perl installed. I have been tinkering with the versions provided by John Murga.

Bladehunter you definitely are a star!
The Airplus drivers include the VID/PID for my DWL-650+ (PCMCIA card) so I ran your dot pup and set up the wireless.conf and now I'm surfing the web using Puppy and the wireless card.
There were a couple of errors reported:
Error for wireless request "Set Sensitivity" (8B08) :
SET failed on device eth1 ; Invalid argument.
Error for wireless request "Set Fragmentation Threshold" (8B24) :
SET failed on device eth1 ; No such device.
Will try to work out what they relate to; eth1 is definitely present and correct. Probably finger trouble on my part.
Don't know what was wrong with my previous attempts to use ndiswrapper with this card, but your version definitely works.

Tested some more today.
1. For some reason, the combination of ndiswrapper and the driver does not like Sensitivity, RTS Threshold and Fragmentation Threshold being set by wireless.conf. Allowing them to default gets rid of error messages and does not seem to affect operation, although the thresholds are much higher than those set in the .inf file.
2. Setting the key before setting the ESSID does not turn on encryption. I thought at first it was finger problems on my part (again), but moving key setting to follow setting the ESSID works fine.
3. So far, have been manually invoking the wireless script and then setting the IP address etc. by hand or using DHCPCD. The latter seems to have a problem because it finds old .PID files and thinks that it is already running; will look at that some more.

Once the wireless link is operating it seems rock solid, running for hours without problems.

I am sure the problem was not with your dot-pup since it seems to perform well with a lot of other cards.

I did farther reasearch on my wifi card and found that all the linux folks said to stay away from it and no reports of anyone getting it to work. Although it used the 8180 chipset the way it accesses the chipset is completely forign and these even had problems on vindows machines.

I will report that I bought an Orinoco Gold Classic card. Plugged it in, Booted up and was online. no config at all. Pupp 1.0.3 is one smart pup. Dont loose those drivers!_________________Puppy Linux...
It just works!

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum