From: Michael E. <mre...@ho...> - 2001-11-17 20:39:25
|
Turn it over and get the model number. Then check it against this page: http://www.bookendzdocks.com/dockid.html As for the WEP password field being blank, I found that interesting as well. My guess is that since the card is already programmed, it works fine after sleep. But it doesn't show up in the box because you probably can't retrieve your active code from the card itself -- just a guess. Mike >From: Steve Wainstead <sw...@pa...> >To: Rob McKeever <ro...@ma...> >CC: Michael Eckhoff <mre...@ho...>, ><wir...@li...> >Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results >Date: Sat, 17 Nov 2001 12:45:23 -0500 (EST) > > >I've had no problems with sleep/awaken on my Powerbook. (I actually don't >know if it's a Lombard or Wallstreet or whatever. If someone could point >me to a resource that explains this, please do). > >However I find that after booting, the card won't work until I open the >Preferences panel, and then it instantly connects to my router. (I don't >have to take any action at all except open System Prefs and then >WirelessConfig.) > >The other oddity is that I never have to enter the Network Equivalent Key, >and the field is always blank. It would be more consistent with other >interfaces if something like "*************" appeared in the box. I feel >like I'm somehow using WEP without a password. > >Also, is there any reason why "Network Equivalent Key" isn't just called >"Network Password"? > >~swain > >On Wed, 14 Nov 2001, Rob McKeever wrote: > > > ...and I know what needs to be done to fix that problem, > > too :-) That's one of the two main objectives for the next > > revision. > > > > The problem with sleep was that many people were seeing the > > powerbook go to sleep, then refusing to wake up. I've also > > heard from a lot of people that are finding it to be working > > just fine, so... ? I figured I'd error on the safe side. I'm > > going to have the next version make the interface temporarily > > unavailable and power down the card just to be on the safe side. > > > > I'll let you know when I've got stuff to test. Probably about a > > week or so before I get any real time to play, though. > > > > -Rob > > > > > > On Wednesday, November 14, 2001, at 09:34 PM, Michael Eckhoff wrote: > > > > > > > > Heh... nice how that works, eh? > > > > > > Anything else that needs testing? > > > > > > BTW, on my Powerbook G3 Lombard Bronze, I can suspend/resume > > > just fine. In fact, I can suspend, unplug my card, pack up and > > > go home, put my card back in, and resume and everything works > > > just fine. The card also appears to shutdown when the system > > > goes to sleep since all the link lights go dark. What is > > > everyone else seeing? > > > > > > Only thing I can't do is remove it and put it back in while the > > > system is live (documented problem :). > > > > > > Mike > > > > > >> From: Rob McKeever <ro...@ma...> > > >> To: "Michael Eckhoff" <mre...@ho...> > > >> CC: wir...@li... > > >> Subject: Re: [Wirelessdriver-devel] IP Multicast Test Results > > >> Date: Wed, 14 Nov 2001 21:28:05 -0800 > > >> > > >> It's always nice to see that the patches I put in without > > >> testing actually work :-) > > >> > > >> Thanks for the feedback! > > >> > > >> -Rob > > >> > > >> On Wednesday, November 14, 2001, at 09:19 PM, Michael Eckhoff wrote: > > >> > > >>> > > >>> It looks like IP Multicast is working fine. I have not spent a > > >>> lot of time testing, but here are my informal results: > > >>> > > >>> I was able to receive IP multicast packets with 100% success at > > >>> about 40pps and 300k packets. > > >>> I was able to receive IP multicast packets with 100% success at > > >>> about 13pps and 512k packets. > > >>> I was able to receive IP multicast packets with about 99% > > >>> success at about 11pps and 1024k packets. > > >>> > > >>> No duplicate packets were detected - so the stack appers to be > > >>> handling everything correctly. > > >>> The program uses a very basic serialization to ensure that > > >>> packet order and is maintained (on a LAN only - all bets are > > >>> off for WAN) and data corruption does not occur. > > >>> > > >>> I havn't looked into tuning my AP for IP multicast. it is > > >>> currently set to only allow 2 meg to be used for multicast. > > >>> When I find time, I may try to adjust these settings to see > > >>> what the max is that I can get. > > >>> > > >>> At any rate, it does appear that everything is working. > > >>> > > >>> Thanks! > > >>> > > >>> Mike > > >>> > > >>> _________________________________________________________________ > > >>> Get your FREE download of MSN Explorer at > > >>> http://explorer.msn.com/intl.asp > > >>> > > >>> > > >>> _______________________________________________ > > >>> Wirelessdriver-devel mailing list > > >>> Wir...@li... > > >>> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > > >> > > > > > > > > > _________________________________________________________________ > > > Get your FREE download of MSN Explorer at > > > http://explorer.msn.com/intl.asp > > > > > > > > > _______________________________________________ > > Wirelessdriver-devel mailing list > > Wir...@li... > > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > > > >--- > http://www.panix.com/~swain/ >"Without music to decorate it, time is just a bunch of boring >production deadlines or dates by which bills must be paid." > -- Frank Zappa > > >_______________________________________________ >Wirelessdriver-devel mailing list >Wir...@li... >https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp |