still struggling with ndiswrapper

[James Pifer]

> As I recall, you previously had the system locking up when you did the
> modprobe step.  This seems to be some progress.
> 

Yes, step in the right direction...

> Use ndiswrapper -l to see the interface drivers and device are present.
> 

Yes, driver is loaded and hardware present. 

> Have you tried using iwlist to see if the adapter finds any local access
> points? It should see the access point even if it does not connect, and
> should tell you about it.

Sure does. 

> 
> Other things that might interfere are mode, channel (I think 1-12, but 6
> is usually the default for the AP), and maybe others.
> I usually try to get the connection without encryption, then enable
> encryption later.
> 

Yes, had not specified the channel but tried it with channel 6 which is
what my router is using. Still no luck. I was trying it with encryption
off for a while. I can try it again. 

> My ifcfg-wlan0 is:
> 

I'll give this a shot too. 

> IPV6INIT=no
> ONBOOT=no
> USERCTL=no
> PEERDNS=yes
> GATEWAY=
> TYPE=Wireless
> DEVICE=wlan0
> HWADDR=
> BOOTPROTO=dhcp
> NETMASK=
> DHCP_HOSTNAME=
> IPADDR=
> DOMAIN=
> ESSID='my_essid'
> CHANNEL=6
> MODE=Managed
> RATE=Auto
> 
> That worked first time with dhcp, although I have done the same with
> static IP addresses as well.  The only things I change for a static IP
> is IPADDR, GATEWAY, NETMASK, and BOOTPROTO
> 
> If I am using WEP the entry is made in keys-wlan0

Thanks,
James