In-reply-to: <41C87B67.3040804@clanganke.de>
Message-id: <0I9300DPS9EIMM@mxout4.netvision.net.il>
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
References: <0I8V00MBU4RH83@mxout5.netvision.net.il>
 <41C43D5F.3060604@clanganke.de> <0I8X00DITBN02B50@mxout1.netvision.net.il>
 <41C87B67.3040804@clanganke.de>
Date:  Tue, 21 Dec 2004 22:11:06 +0200
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Stan Goodman <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] PCMCIA, Cisco 352, and Thinkpad T21

** Reply to message from Christian Langanke <cla@clanganke.de> on Tue, 21 Dec
2004 20:37:11 +0100


> 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.

I am very sorry that I gave you that impression, and apologize.

At the moment, I am more confident than I was about understanding the process
and the software, thanks to remarks by several of the other users here. 

As to your paragraph above, I would have liked to perform the experiments that
you mention, e.g. try to connect to a hotspot, but I am limited somewhat by the
fact that I don't yet have the Cisco card in hand. It is waiting for me abroad,
and I have been trying to get things set up to the greatest extent possible,
given this limitation, because it will be hard for me to do so once I put the
card in, try to connect to a LAN, find that I can't do so, and have no other
machine handy, wired or not, with which to consult this group. As I have said
previously, I am sure that my efforts, questions, and doubts may make me see
paranoiac (substitute another word if you wish), but that is the prospect I
have been trying to avoid by prior preparation. I think I have done so, and
believe/hope that things will work when I have the card and an available
wireless LAN. In addition to that, as far as I know (and as far as the hotspot
list at <ttp://www.wi-fihotspotlist.com/browse/> tells me, the nearest hotspot
or otherwise available to me wireless LAN is not closer than 100km from me --
not really convenient.

> 
> >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?

A couplel of people have said that they have, or will generate, a list of steps
that they go through during a planned new install with equipment much like
mine. I would like to see that. That's pretty much what I meant by checklist.
> 
> >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...

http://hobbes.nmsu.edu/cgi-bin/h-browse?sh=1&dir=//pub/os2/system/drivers/network
> 
> bye, Christian

-- 
Stan Goodman
Qiryat Tiv'on
Israel

"When your enemy falls, do not rejoice." -- Proverbs 24:17

Imitation is the sincerest form of plagiarism.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=