From: "Al Heath" Received: from mxout4.mailhop.org ([63.208.196.168] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 376118 for os2-wireless_users@2rosenthals.com; Sun, 24 Sep 2006 16:00:44 -0400 Received: from mxin2.mailhop.org ([63.208.196.176]) by mxout4.mailhop.org with esmtp (Exim 4.51) id 1GRa9X-000Go1-Ed for os2-wireless_users@2rosenthals.com; Sun, 24 Sep 2006 16:00:39 -0400 Received: from e32.co.us.ibm.com ([32.97.110.150]) by mxin2.mailhop.org with esmtp (Exim 4.51) id 1GRa9R-000IG2-5s for os2-wireless_users@2rosenthals.com; Sun, 24 Sep 2006 16:00:33 -0400 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e32.co.us.ibm.com (8.13.8/8.12.11) with ESMTP id k8OK0R04024707 for ; Sun, 24 Sep 2006 16:00:27 -0400 Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by d03relay04.boulder.ibm.com (8.13.6/8.13.6/NCO v8.1.1) with ESMTP id k8OK0RJh251490 for ; Sun, 24 Sep 2006 14:00:27 -0600 Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k8OK0Qpp026084 for ; Sun, 24 Sep 2006 14:00:26 -0600 Received: from d03nm122.boulder.ibm.com (d03nm122.boulder.ibm.com [9.17.195.148]) by d03av01.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k8OK0Qbi026071 for ; Sun, 24 Sep 2006 14:00:26 -0600 Importance: Normal Sensitivity: Subject: Re: [OS2Wireless]Re: T23 internal cards success To: "OS/2 Wireless Users Mailing List" Date: Sun, 24 Sep 2006 15:00:20 -0500 Message-ID: X-MIMETrack: Serialize by Router on D03NM122/03/M/IBM(Release 7.0.1HF269 | June 22, 2006) at 09/24/2006 14:00:26 MIME-Version: 1.0 Content-type: multipart/alternative; Boundary="0__=09BBFB60DFF809718f9e8a93df938690918c09BBFB60DFF80971" Content-Disposition: inline X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -1.7 (-) --0__=09BBFB60DFF809718f9e8a93df938690918c09BBFB60DFF80971 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable >> On the WEP key... are you prefixing it with 0x? I was doing that on the 'ssid' command utility. Didn't think about hav= ing to do that also on the gui screen. Duh... senile moment on my part. Perhaps when xwlan truncates the field to 1/2 of what you just entered,= it should put up a warning and ask if your really wanted a hex key, or jus= t simply detect that situation as hex when you enter into the field of 0-= 9, a-f characters only and the length is exactly double what it is going t= o store... I guess with command line utilities I think I have to "think"= whereas when using a gui I expect the system to do "thinking" for me. But when I tried that 0x prefix in xwlan, it did save the full key and connect fine. So user error. But after a while, the system frooze aga= in. So I think I'll stick to the command line utilities. I'm not crazy abo= ut having to hold the power button down and go thru the chkdsk recovery at= unexpected times. Maybe it is something about the way the gui is polli= ng for status to update the icon's bars? I dunno... Guess I could experi= ment with the gui and exit it after it connects and see if that keeps the sy= stem as stable as when using just the command line commands. I don't seem t= o have that stability problem on my T43 ... but they use different genmac= card drivers. Anyway... I probably shouldn't hijack this thread. Thanks for the obvious hint Al H= --0__=09BBFB60DFF809718f9e8a93df938690918c09BBFB60DFF80971 Content-type: text/html; charset=US-ASCII Content-Disposition: inline Content-transfer-encoding: quoted-printable

>> On the WEP key... are you prefixing it with 0x?

I was doing that on the 'ssid' command utility. Didn't think about hav= ing to do that also on the gui screen. Duh... senile moment on my part= . Perhaps when xwlan truncates the field to 1/2 of what you just ente= red, it should put up a warning and ask if your really wanted a hex key= , or just simply detect that situation as hex when you enter into the f= ield of 0-9, a-f characters only and the length is exactly double what = it is going to store... I guess with command line utilities I think I = have to "think" whereas when using a gui I expect the system = to do "thinking" for me.

But when I tried that 0x prefix in xwlan, it did save the full key and = connect fine. So user error. But after a while, the system frooze aga= in. So I think I'll stick to the command line utilities. I'm not craz= y about having to hold the power button down and go thru the chkdsk rec= overy at unexpected times. Maybe it is something about the way the gui= is polling for status to update the icon's bars? I dunno... Guess I = could experiment with the gui and exit it after it connects and see if = that keeps the system as stable as when using just the command line com= mands. I don't seem to have that stability problem on my T43 ... but t= hey use different genmac card drivers. Anyway... I probably shouldn't = hijack this thread.

Thanks for the obvious hint
Al H= --0__=09BBFB60DFF809718f9e8a93df938690918c09BBFB60DFF80971--