OT: Windows is too expensive

geoschmo · #1 March 9th, 2007, 09:26 PM

Ok, I didn't do that yet, but I've made some progress. I found a post one place stating the XP driver may not work and to try the other versions. I got the driver to install with no errors by using the Win2K driver instead of the XP driver. Here's what I get now...

lsusb
Bus 001 Device 002: ID 0457:0163 Silicon Integrated Systems Corp.
Bus 001 Device 001: ID 0000:0000
ndiswrapper -l
Installed drivers:
sis163u driver installed, hardware present

It looks like progress to me, but I still cant' seem to figure out how to get the device to connect to my wireless network. And the led on the adapter isn't on. Any ideas?

Geoschmo

parabolize · #2 March 9th, 2007, 09:41 PM

Code:



sudo depmod -a

sudo modprobe ndiswrapper

Then look at the end of /var/log/messages for errors. Then go into System - Administration - Networking and set stuff up. If all works run this to load the mod at startup:
Code:



sudo ndiswrapper -m

geoschmo · #3 March 9th, 2007, 09:56 PM

Ok, didn't see any errors in the log file. But when I do this...
sudo ndiswrapper -m

I get this...
modprobe config already contains alias directive

parabolize · #4 March 9th, 2007, 10:15 PM

Look for ndiswrapper in the list
Code:

gedit /etc/modules

geoschmo · #5 March 9th, 2007, 10:22 PM

Quote:

parabolize said:
Look for ndiswrapper in the list
Code:

gedit /etc/modules

# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

lp

That's all. Don't see ndiswrapper in it.

parabolize · #6 March 9th, 2007, 10:27 PM

Open it again this time as super user:
Code:

sudo gedit /etc/modules

Add it at the bottom of the list and save like so:
Code:



# /etc/modules: kernel modules to load at boot time.

#

# This file contains the names of kernel modules that should be loaded

# at boot time, one per line. Lines beginning with "#" are ignored.



lp

ndiswrapper

edit: Why o why has it taken to double spacing stuff inside code tags? It wasn't a few posts ago...

geoschmo · #7 March 9th, 2007, 10:36 PM

Para, I owe you a beer.

Wireless is workign great now. Thanks for all the help.

Geoschmo

Renegade 13 · #8 March 14th, 2007, 07:04 PM

Personally, I don't understand what everyone's problem with XP is. I've never had any major difficulties with it that weren't my own fault for messing around with stuff I didn't understand at the time

No viruses, trojans, etc, no instability, nothing. Been a smooth ride for me ever since my first computer with Win 95 on it.

*(Now will probably have a rash of problems, after making the above statement!)*

geoschmo · #9 March 14th, 2007, 08:22 PM

Quote:

Renegade 13 said:
Personally, I don't understand what everyone's problem with XP is. I've never had any major difficulties with it that weren't my own fault for messing around with stuff I didn't understand at the time

XP has been quiet stable and decent for me as well. My only complaint is, as the thread title says, it's too expensive.

capnq · #10 March 15th, 2007, 05:25 PM

Quote:

Renegade 13 said: Personally, I don't understand what everyone's problem with XP is.

From what I've read about them, XP and Vista both include a number of "features" and deliberate design decisions which IMO are Bad Ideas. (Mostly involving security and DRM issues, which I'd rather not get into a lengthy discussion of.)

I'm hoping to buy a used system in the near future, which is probably going to have XP already installed. I don't intend to connect it to the net until I've done some research on what settings I have to change to ameliorate the security problems.