It puzzles me a little that the driver would be part of Puppy, but it's missing parts! I did notice on boot-up that the wireless seems to be recognized. Is this just an oversight, or a technical issue I'm not brainy enough to comprehend?billstclair wrote:You didn't say which version of Puppy you're using. If it's Puppy 2.0x, the driver proper for the Intel Pro Wireless 2200BG is part of Puppy. But it's missing the firmware and the scripts to load the firmware. "ipw2200-fw-2.4.pup" in the "Dotpups" section at http://s3.amazonaws.com/puppy/index.html contains a packaging I did of the firmware, along with a "wireless" script for loading the driver, configuring it to connect to any unencrypted base station, and starting dhcpcd. You'll have to modify that script if you use encryption, and you'll probably have to change eth0 to eth1. Or you can use WAG in the Puppy network tools, after installing the dotpup.
Anyhoo, I'm not having much luck with billstclair's ipw2200-fw-2.4.pup referred to above, and I'm sure it's my failure to know what I'm doing. I downloaded it to the C drive (I was kind of puzzled that although it had a .pup extension, it downloaded with a .zip extension????). Anyway, I booted Puppy, and mounted (a completely alien concept to me!) the C: drive and located the file at /initrd/mnt/dev_save. I dragged the file (using Rox) to the home directory and clicked on it. I thought I extracted it, but from this point onwards I'm lost. I tried running Wag, but it doesn't seem to recognize anything, and I don't understand how it works. Can someone help me with this part?
Perhaps I should just hold fire on the USB stick, if the latest Puppy's going to enable us to save to NTFS. I don't think I can justify owning a stick for any other purpose. I don't suppose that release will automatically take care of my wireless card woes will it?Rickrandom wrote:With a bit of luck Puppy's NTFS read/write capability will be proven in a few days, and we can all save to an NTFS hard disk without the need for USB sticks, etc.