When I put in a CD with Windows drivers, the Windows module failed to install into /etc/ndiswrapper. I found that the script fails if the path has a space character. Fixed.
There was a syntax error in an 'if' statement. Fixed.
I had booted with pfix=ram, and I had removed the Puppy live-CD to put in the Windows wireless driver CD, but then the Network Wizard failed to load the 'ndiswrapper' module. The 'modprobe' script was unable to fetch it off the CD.
I have fixed this problem by building Puppy with 'ndiswrapper.ko' already in the 'pup_400.sfs' file, so it doesn't have to be fetched.
Wireless with a Windows driver is now working, and that's what I'm running right now. An open network -- as my nearest neighbor is 2.5 Km (1.5 miles) away, I'm not bothered with encryption!
I'm testing Puppy with 2.6.25 kernel. I've got a Netgear WG311 wireless card, and the 188.8.131.52 native driver was useless ...I forget which one it was... anyway, running with the 2.6.25 kernel no native driver has claimed the card.
Comments:Posted on 30 Apr 2008, 6:08 by urban soul
I am working on the wag profile management gui these days. (See screenshot in http://www.murga-linux.com/puppy/viewtopic.php?t=26935).
(Anybody else?) When I am finished I paste it in the lastest version of wag-profiles.sh (I wont touch net-setup.sh) and PM it to you.
Posted on 30 Apr 2008, 8:37 by BarryK
Re: wag GUI
urban soul, that's great! Pup 4.00final is very close, so we will aim for the overhaul of the Network Wizard GUI for 4.1. It will give us some breathing space to work on it leisurely.
Hmmm, I'll have to check this blog script. I had turned on the bbcode menu for comments, but it isn't displaying. It was sometime back.