X-Account-Key: account1 X-UIDL: 38848 X-Mozilla-Keys: Return-Path: os2-wireless_users-owner@2rosenthals.com Received: from 192.168.100.5 (hawking [192.168.100.5]) by 2rosenthals.com (Hethmon Brothers Smtpd) id 20041221143824-15620-7 ; Tue, 21 Dec 2004 14:38:24 -0500 (Hethmon Brothers Smtpd) id 20041221143821-3964-7 ; Tue, 21 Dec 2004 14:38:21 -0500 Received: from mx1.mailhop.org ([63.208.196.170]) by mxout1.mailhop.org with esmtp (Exim 4.43) id 1CgpqR-000NDJ-UY for os2-wireless_users@2rosenthals.com; Tue, 21 Dec 2004 14:38:56 -0500 Received: from waldorf.webpack.hosteurope.de ([217.115.142.71]) by mx1.mailhop.org with esmtp (Exim 4.42) id 1CgpqR-000CnW-Ma for os2-wireless_users@2rosenthals.com; Tue, 21 Dec 2004 14:38:55 -0500 Received: by waldorf.webpack.hosteurope.de running Exim 4.34 using asmtp (TLSv1:RC4-MD5:128) from p5084a3b8.dip0.t-ipconnect.de ([80.132.163.184] helo=clanganke.de) id 1CgpqJ-0007sw-6R; Tue, 21 Dec 2004 20:38:47 +0100 Message-ID: <41C87B67.3040804@clanganke.de> User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0) Gecko/20020530 X-Accept-Language: en MIME-Version: 1.0 References: <0I8V00MBU4RH83@mxout5.netvision.net.il> <41C43D5F.3060604@clanganke.de> <0I8X00DITBN02B50@mxout1.netvision.net.il> In-Reply-To: <0I8X00DITBN02B50@mxout1.netvision.net.il> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop by DynDNS.org X-Spam-Score: -2.6 (--) Date: Tue, 21 Dec 2004 20:37:11 +0100 Sender: os2-wireless_users-owner X-Listname: os2-wireless_users@2rosenthals.com Reply-To: os2-wireless_users@2rosenthals.com From: Christian Langanke To: os2-wireless_users@2rosenthals.com Subject: [OS2Wireless] PCMCIA, Cisco 352, and Thinkpad T21 X-List-Unsubscribe: Send email to mailusers-request@2rosenthals.com X-List-Owner: mailusers-owner@2rosenthals.com Stan Goodman wrote: >>I'd say, RTFM, so see the INF file, section usage. >> >> > >That's one of the least attractive sets of initials in the industry.. > Maybe, but don't ask me, I did not invent it. Sorry, but you gave well the impression that you did not know anything of what is documented. After all you said something like "I installed the driver, it is recognized by XWLAN, now what ?". I then would have expected that a user would at least try to connect to a hotspot, and yes, read the manual about that. Same for connection profiles., where all dialogs have their own context sensitive help panel. I would well expect that questions are left when having read through the usage section, but I would not expect that somebody would have no clue at all. >Anyway, So far I have no problem with XWLAN or its documentation. My questions >are about the entire process, and about any additional steps that have to be >taken outside of the driver -- widget combination. So far, it seems that I am >on the right track, because several points have been raised both here and in an >NG that seem to be helpful, but unlikely to be in the widget's documentation. I >would not be surprised if there are more such in the checklist that has been >promised. > Hmm, what I take from this is that there is no getting "started section". I am afraid though, that this would contain a lot of links to the existing help pages, but yes, it would help getting into the matter more easily. If we can work out a list of what should be in there, I will be glad to include it. It may also make sense to just refer to the FAQ Lewis intends to create. With checklist I assume you mean this FAQ? >For example I was told yesterday in ecomstation. support.networking that it >would be a good idea to run the Cisco 340 driver from Hobbes before changing to >the Beta driver that supports XWLAN, in order to get the benefit of WEP. That >would not have been in your INF file. > Somebody please tell me how this can be done. I mean, AFAIK an upload of WEP keys cannot survive a reboot, and this would be necessary if XWLAN cannot be used to switch between drivers. How can that work ? Has somebodday reading this list tried it (please post with explicit subject !) And please someone pass me a pointer to that driver, I would be glad to get that to work. It nevertheless may well be that the old driver cannot be properly integrated ewith XWLAN, as certain parts of the driver interface may be missing... bye, Christian ------------------------------------------------- Christian Langanke COS2E & CWSE Team OS/2 Ruhr e.V. cla@clanganke.de =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To unsubscribe from this list, send a message to steward@2rosenthals.com with the command "unsubscribe os2-wireless_users" in the body (omit the quotes). For help with other commands, send a message to steward@2rosenthals.com with the command "help" in the body (omit the quotes). This list is hosted by Rosenthal & Rosenthal P.O. Box 281, Deer Park, NY 11729-0281. Non- electronic communications related to content contained in these messages should be directed to the above address. (CAN-SPAM Act of 2003) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=