In-reply-to: <200412180044.iBI0iXjR023851@sputnik.angelwireless.com>
Message-id: <0I8W00DVLRB22C10@mxout1.netvision.net.il>
MIME-version: 1.0
Content-type: TEXT/PLAIN
Content-transfer-encoding: 7BIT
References: <200412180044.iBI0iXjR023851@sputnik.angelwireless.com>
Date:  Sat, 18 Dec 2004 09:54:37 +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] Cisco 350 and Wep

** Reply to message from madodel@ptdprolog.net on Fri, 17 Dec 2004 19:43:01
-0500


> In, on 12/17/04 at 07:37 PM,
>    "Mark Dodel" <madodel@ptd.net> said:
> 
> I saw the following posted on ecomstation.support.networking today from
> "P.R. Nienhuis" regarding using the old Cisco340 driver (from hobbes) to
> set a WEP40 key, then using the new Cisco340/350 driver and the WEP will
> still work.  I don't use encryption so I haven't tried it but I thought
> I'd pass it on in case someone was interested.
> 
> Mark
> 
> >-> Subject: Re: PCMCIA
> >-> Date: Fri, 17 Dec 2004 23:12:59 +0100
> 
> >Stan Goodman wrote:
> ><snipped>
> >> I'll try to find it and read it, which shouldn't be hard as Google 
> >knows 
> >> only three documents about it. But it is probably irrelevant. The 
> >card I 
> >> will have to work with is Cisco 352; apparently there is one driver 
> >for it, 
> >> a Beta. .....<snipped>
> 
> >FYI, the driver for Cisco 340 (cisco340.zip, hobbes) works too with  352 
> >cards - it fully supports 40 (64) bit WEP encryption but not the WXLAN
> 
> >widget.
> >But - once the 340 driver has written the WEP key to the card, you can
> 
> >dump it and use the 350 beta driver and the WEP encryption still 
> >works..... (plus -of course- you can use the WXLAN widget.)
> 
> >The 350beta driver simply lacks the physical ability to actually set  WEP
> 
> >keys or use 128 bit WEP keys (although its MPTS edit menus suggest it 
> >can).
> >Otherwise, it works OK, AFAICS.
> 
> >Both the 340 and 350beta driver are socket services compliant, i.e. at
> 
> >minimum they need pcmcia.sys (basedev), a pcmcia socket services  driver 
> >for your hardware (basedev too; e.g. on a Toshiba: IBM2TOS1.SYS, or  one 
> >of the SSPCIC<or so>.SYS drivers on other H/W), and that should do for
> 
> >basic PCMCIA stuff (it does here).
> >I don't use EZPlay or Card Director or whatever-it-is-called etc, my 
> >system and all PCMCIA cards run fine w/o.
> 
> >Philip
> 
> >---END FORWARDED MESSAGE---

Thanks, Mark. You beat me to it.

-- 
Stan Goodman
Qiryat Tiv'on
Israel

"When your enemy falls, do not rejoice." -- Proverbs 24:17

"It's a wise Frenchman that knows his own father." -- Mark Twain
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=