Menu
▾
▴
wirelessdriver-devel — Discussion of development related issues
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(16) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(12) |
Feb
|
Mar
(4) |
Apr
(6) |
May
(5) |
Jun
(3) |
Jul
(4) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
| 2003 |
Jan
(4) |
Feb
(6) |
Mar
(1) |
Apr
|
May
(3) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(9) |
Dec
(4) |
| 2004 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
(2) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
(3) |
Jul
(1) |
Aug
(5) |
Sep
(3) |
Oct
(1) |
Nov
|
Dec
|
|
From: Rob M. <ro...@ma...> - 2001-11-11 23:22:48
|
OK... I've giving it a bit of thought and I think this will help to keep everyone happy with some small compromises. I want to release the code as it stands right now without the network search code as beta 3 and then start work on getting the code reorganized and cleaned up for beta 4. If I add the network search code to the driver as is, it'll likely be limited to the Lucent Silver cards for now, and don't want to make the code any more product specific. The other option is to name this release as 3A and then to a 3B release with search code for specific cards at some point shortly down the road, but before the code rewrite is complete. So... for the next revision, I'm aiming for: 1) Isolation of all of the 802.11 code from the vendor-specific hardware code ** This is the biggest and most important change that needs to be made. 2) Automatic detection of networks 3) Clean removal and re-insertion of the card. There may still be issues with interface naming, but at least you wont crash anymore 4) Better behaviour during sleep. I'll make this new installer available to the members of this list later on today, unless anybody's got any major objections. Once I've had a few of you verify that it works OK, I'll release it to the public witht he appropriate announcements. -Rob McKeever ro...@ma... |
|
From: Steve W. <sw...@pa...> - 2001-11-07 09:23:03
|
I was browsing the help forum and saw someone had posted that they solved
the problem I had with a firmware upgrade for the Linksys router. I'm
happy to report that it worked for me too. I'm now wireless and OS X and
quite happy.
thx a million folks!
~swain
---
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
|
|
From: David R. <n1...@ma...> - 2001-10-25 18:04:42
|
I've committed updated sources for the preference pane. It will now behave like the current version of the application (ie it will now autodetect a card insertion if there isn't a card inserted when the pane is opened) and fixed the Using WEP checkbox to reflect whether or not WEP is really enabled. Also changed is the labeling of the wep key box. -- Dave |
|
From: Rob M. <ro...@ma...> - 2001-10-25 06:01:02
|
I've committed changes that make sure the network name is always available to the UserClient and is now properly reported to the IORegistry. It's a small, but important, step towards getting automatic scanning for other networks operational. -Rob McKeever ro...@ma... |
|
From: David R. <n1...@ma...> - 2001-10-24 17:56:49
|
I have just committed a new version of the configure application to the CVS repository. I've added the following: The WEP state is now shown in the check box, meaning that if WEP is set in the preferences, the check box will be checked. Also changed is that the application will now wait for a card to be inserted and then configure it, rather than quitting once it didn't detect a card which was its previous behavior. -- Dave |
|
From: David R. <n1...@ma...> - 2001-10-23 16:31:47
|
Hello - I've just committed to CVS a working preference pane target in the WirelessConfig project. To install it place it in either: /Library/PreferencePanes or ~/Library/PreferencePanes Enjoy -- Dave |
|
From: David R. <n1...@ma...> - 2001-10-23 14:33:47
|
I found out that since all of my text are in nib files they are automatically localizable. I found the documentation for Preference Panes and I'll see how long it will take to implement one. At the moment it looks like all I have to do is change a few pieces around and keep all my code that I have but I'll see. -- Dave On Tuesday, October 23, 2001, at 10:22 AM, David Ross wrote: > > On Tuesday, October 23, 2001, at 01:47 AM, Rob McKeever wrote: > >> >> On Monday, October 22, 2001, at 10:27 PM, yu...@ma... wrote: >> >>> Great stuff guys!!!! I too am now closed network/WEP enabled at home. >>> Wheeee! >>> >>> Some thoughts and questions... >>> >>> Does the userclient.app from Robs code actually do anything, or has >>> it's function been incorporated into Dave's WirelessConfig.app? Robs >>> UserClientTemplate.app compiles fine but won't launch for me. If the >>> former is correct we should probably clean the template from Robs >>> tree and integrate the required files into Daves part of the tree. I >>> may be way off here, if so please explain. >> >> Dave's pretty much duplicated what I had done in TemplateApp.c. I'm >> going to be replacing the template app with a framework in the next >> couple of days and then the template will be pretty much completely >> useless and can be removed. > > I just committed a modified project file that no longer includes > TemplateApp.c so there should be no more confusion in this case. Thanks > Rob tho for the example in TemplateApp.c or I'd not have gotten done so > quickly. > >>> >>> I'll prepare a FAQ adjustment to explain how to get the correct WEP >>> code to input into the config tool and e-mail it to you for browsing >>> before we release the new version to the public at large. >> >> We should also expand the troubleshooting section some. I'll post my >> basic steps to the developer_private list tomorrow morning. > > I'd like to see if I can find Apple's hashing mechanism so that the WEP > password would be what you would type normally. With an option to just > specify the 40 bits in hex. This will take a bit as I don't think it is > published. > >>> On that note, how soon till you are ready to release the first >>> WEP/closed version? I know there are a few more bugs in the driver >>> and GUI you want quashed before release, but I would recommend the >>> philosophy release early, release often..public releases to version >>> tracker should be tested by at least 2 of us and should have updated >>> readme's in the installer. Only Rob should make public releases >>> besides cvs. If anyone want to update the links on the home page to >>> reflect a release, or add to the faq, feel free but just let the >>> others know. >> >> I'm voting for a target of late in the week to try for a release. >> This gives us a chance to fix a few more issues, round out some rough >> spots, etc. >> >> Do either of you think we should add any additional docs to this next >> release? ...or are we good to go with what has been there until now, >> plus the possible addition of a brief troubleshooting FAQ to keep us >> all sane under the e-mail onslaught? > > I think with the new GUI app that the trouble shooting will be less as > it will handle more of the configurations they wish to try. Though > there are more things in heaven and earth that can go wrong that I'll > ever know. > >>> >>> Is it possible to make the WirelessConfig.app a preference pane ala >>> the new 3rd party panes from tinkertool/asm etc that are installed in >>> /Library/Preferences. Or would we even want this? I'd like it, if it >>> were possible. >> >> Yes... but one thing at a time. I'd also like to see either a >> Dockling or a menu bar item down the road as well. > > Supposedly the Preference pane API is published - but I haven't found > it yet. I'm guessing that it will take around 20 min to convert the app > from Application to Preference Pane mode once I get the API. The > menuitem api isn't published so I think we are going to have to ask the > author(s) of ASM to lend us their stubs. > >>> >>> What do we see as the future roles for the GUI? It currently is >>> simple and functional (the way things should be). I found that I >>> could used the Apple admin utility (or Sevy's Java Configurator) for >>> BS configuration once I had enabled WEP via Dave's GUI, so we don't >>> need to supply the whole set of admin tools. WAP discovery would be >>> very useful to add to Daves gui. Beyond that....AirSnort ;-) It would >>> be good if the help menu directed people to the FAQ and provided the >>> current FAQ. >> >> I'm going to see what I can do about public autodiscovery tomorrow and >> Wed. It would be great to have it for the next release. > > As soon as auto discovery is ready I'll integrate that into the gui. > >>> >>> We will want an icon for the WirelessConfig.app I'd be happy to give >>> it a whack unless you already have a plan. Do we want to stick with >>> this name? Other possibilities include WirelessConfigurator.app >>> WirelessAdmin.app WirelessAdminUtility.app WirelessUtility.app >>> WEP_Utility.app etc. etc. It would be good to choose a name now and >>> stick with it. >> >> I'll let you guys fight that one out. I've never been good at that >> end of things. > > I just named it the first thing that popped into my head that didn't > sound to trite. If you really wish it to change that is fine with me > and I'll go around and fix all the naming in the nibs and project > files. I will be adding localizable text today so that it can be > translated if anyone wants to (I only know English so I wouldn't be the > best person to localize). > >> >>> >>> Cheers and keep up the great work! >>> >>> Y >>> >> >> Likewise! It's been an immense help having someone to handle the >> stuff I'm not very good with. >> >> -Rob >> > > This project is fun and give me stuff to do while I wait for the HR > dept of my new job to process me. > > -- Dave > |
|
From: Rob M. <ro...@ma...> - 2001-10-23 02:13:21
|
I responded privately before I noticed that it should have been sent to the list as well - oops. Installing over top of an existing version should be OK, but to be safe, you should delete the previous version first. The system seems to want things to be owned by root, so I often use the following: 1) cd [your path]/build 2) sudo tcsh 3) rm -rf /System/Library/Extensions/WirelessDriver.kext 3) tar cf - WirelessDriver.kext | ( cd /System/Library/Extensions; tar xvf -) 4) chown -R root /System/Library/Extensions/WirelessDriver.kext -Rob McKeever ro...@ma... On Monday, October 22, 2001, at 12:09 PM, Steve Wainstead wrote: > > Got it, compiled it with no errors. Can I then just copy > WirelessDriver.kext over the old version? > > ~swain > > On Mon, 22 Oct 2001, Rob McKeever wrote: > >> Just a quick note to let everyone know that WEP support and >> closed network support has been completed and committed to CVS. >> The sample UserClient app that is included show how to set both >> features in a bsic form, as well as how to retrieve signal >> strength information. >> >> No support yet for automatic configuration on card insertion - >> this will come in the near future... we need to have some 'real' >> tools, both GUI and command line, that can read/write a >> preference file of some sort before this can be done. >> >> -Rob McKeever >> ro...@ma... >> >> >> _______________________________________________ >> 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 |
|
From: David R. <n1...@ma...> - 2001-10-22 20:51:24
|
Hello - I've just committed the fixed version of the GUI for configuring the=20 WirelessDriver. Whats New in this Version: =95 Better looking =95 Added in preferences: When you apply new setting they are now saved = in=20 "~/Library/Preferences/org.noncontinuous.WirelessDriver.plist" and on=20 relaunch of the GUI they are reapplyed with the following caveats - 1)=20= The WEP isn't echoed to the WEP box 2) The enabled state of WEP isn't=20 set 3) The WEP values are correctly sent to the card. Whats Fixed: =95 It should now have all the files in the repository. Sorry I forgot = to=20 add one of the Info.plists. =95 The file references for the included headers are now set to project=20= relative. Enjoy -- Dave |
|
From: Steve W. <sw...@pa...> - 2001-10-22 19:09:46
|
Got it, compiled it with no errors. Can I then just copy WirelessDriver.kext over the old version? ~swain On Mon, 22 Oct 2001, Rob McKeever wrote: > Just a quick note to let everyone know that WEP support and > closed network support has been completed and committed to CVS. > The sample UserClient app that is included show how to set both > features in a bsic form, as well as how to retrieve signal > strength information. > > No support yet for automatic configuration on card insertion - > this will come in the near future... we need to have some 'real' > tools, both GUI and command line, that can read/write a > preference file of some sort before this can be done. > > -Rob McKeever > ro...@ma... > > > _______________________________________________ > 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 |
|
From: David R. <n1...@ma...> - 2001-10-22 18:41:09
|
Hello - Just to let you know that the first version of the GUI configuration program is now in the CVS tree. It isn't all that pretty, but I'm going to need feedback on how to make it what everyone would want. -- Dave |
|
From: Rob M. <ro...@ma...> - 2001-10-22 17:39:41
|
Just a quick note to let everyone know that WEP support and closed network support has been completed and committed to CVS. The sample UserClient app that is included show how to set both features in a bsic form, as well as how to retrieve signal strength information. No support yet for automatic configuration on card insertion - this will come in the near future... we need to have some 'real' tools, both GUI and command line, that can read/write a preference file of some sort before this can be done. -Rob McKeever ro...@ma... |
|
From: Rob M. <ro...@ma...> - 2001-10-18 06:14:43
|
I just checked the CVS and I didn't see IOKit.framework there - it might have gotten added as part of the header caching during the build process. As of 10.1, you shouldn't need the ~/Library/Headers anymore, though, as long as the /System/Library/Frameworks/Kernel.framework/Headers/IOKit/pccard directory is populated correctly. The ~/Library/Headers folder was required when we were using a pre-release copy of IOPCCardFamily, as we needed to override the version that comes with Kernel.framework. It's unlikely we'd need to do this again, as the PCCard support is basically complete. If Apple changes something for a future version, then we'll need to do this again, temporarily, as we adapt. I got bombarded with crap this afternoon, so the update get pushed back a day or so. I'll keep you posted. Some things that will be committed to CVS at that time: 1. Multicast support fixed. This is likely the problem with AppleTalk and some games. 2. IORegistry support much improved. You can now use the registry to get signal strength and other feedback 3. The UserClient gets a big boost. This is still work in progress. ..I'll get to power control next revision. -Rob On Wednesday, October 17, 2001, at 10:14 PM, yu...@ma... wrote: > Steve, > > I see that rob has added the IOKit.framework to the > wirelessdriver cvs. I assume this replaces the need for > IOPCCardFamily headers in ~Library as the header files are > already in the wirelessdriver project. I just rebuilt it > without problems after removing my ~/Library headers. > > I believe the FAQ instructions sort of guarantee that your > IOPCCardFamily will work with future versions of IOPCCardFamily > source from Apple even if Rob has not updated them in the > wirelessdriver source in cvs. (Assume that 10.1.5 changes > IOPCCardFamily.kext). Rob, could you suggest whether or not the > instructions for getting IOPCCardFamily from Apple should be > removed from the FAQ, or just adjusted to indicate the need to > get IOPCCardFamily if a new OS update has broken the build > process. > > Yuri > > p.s. I am not a code cooker (just a user/addict) so I may be > completely wrong about this. > > On Wednesday, October 17, 2001, at 11:49 PM, Steve Wainstead wrote: > >> >> You may wish to add that it's not necessary to download IOPCCardFamily >> with OSX 10.1. Rob replied to me earlier today but I don't think he >> replied to the list; he mentioned this... it will save others >> some effort. >> >> cheers! >> ~swain >> >> On Wed, 17 Oct 2001 yu...@ma... wrote: >> >>> Steve, >>> >>> I added your more detailed instructions to the FAQ. I ran out of >>> gas filling in the fine details when I wrote the first version. You >>> don't need to have installed IOPCCardFamily to build the >>> wirelessdriver >>> but I believe you need the IOPCCFamily headers in your >>> ~/Library folder >>> (I've never tried without, so I don't know this for sure). If >>> you have >>> any other suggestions for the FAQ let me know. >>> >>> Yuriwho >>> >>> p.s. Rob will be updating the source soon so get ready to do >>> the dance >>> again >>> >>> On Wednesday, October 17, 2001, at 03:38 PM, Steve Wainstead wrote: >>> >>>> >>>> Hi Rob, >>>> >>>> Just a note that I was able to d/l WirelessDriver and build it with >>>> Project Builder, which I presume is the way to do it. I got >>>> IOPCCardFamily >>>> out of Apple's CVS and built that too (haven't installed either >>>> though). I >>>> posted on the wirelessdriver.sourceforge.net Help forum on >>>> how to get >>>> IOPCCardFamily from Apple's CVS. >>>> >>>> All this is only remarkable in that I've never built anything on >>>> Darwin/OSX... been using CVS for years though. I wasn't sure if >>>> WirelessDriver used Project Builder or not (the .pbprog >>>> extension was a >>>> good clue though ;-). I got thirteen warnings. (This is the >>>> copy in CVS >>>> right now). >>>> >>>> I didn't think it would build at all, since I hadn't installed >>>> IOPCCardFamily, but since it did I'm guessing it was b/c I already >>>> installed the .pkg. file. >>>> >>>> cheers >>>> ~swain >>>> >>>> --- >>>> 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 >>> >>> >>> _______________________________________________ >>> 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 >> > |
|
From: Steve W. <sw...@pa...> - 2001-10-18 04:49:40
|
You may wish to add that it's not necessary to download IOPCCardFamily with OSX 10.1. Rob replied to me earlier today but I don't think he replied to the list; he mentioned this... it will save others some effort. cheers! ~swain On Wed, 17 Oct 2001 yu...@ma... wrote: > Steve, > > I added your more detailed instructions to the FAQ. I ran out of > gas filling in the fine details when I wrote the first version. You > don't need to have installed IOPCCardFamily to build the wirelessdriver > but I believe you need the IOPCCFamily headers in your ~/Library folder > (I've never tried without, so I don't know this for sure). If you have > any other suggestions for the FAQ let me know. > > Yuriwho > > p.s. Rob will be updating the source soon so get ready to do the dance > again > > On Wednesday, October 17, 2001, at 03:38 PM, Steve Wainstead wrote: > > > > > Hi Rob, > > > > Just a note that I was able to d/l WirelessDriver and build it with > > Project Builder, which I presume is the way to do it. I got > > IOPCCardFamily > > out of Apple's CVS and built that too (haven't installed either > > though). I > > posted on the wirelessdriver.sourceforge.net Help forum on how to get > > IOPCCardFamily from Apple's CVS. > > > > All this is only remarkable in that I've never built anything on > > Darwin/OSX... been using CVS for years though. I wasn't sure if > > WirelessDriver used Project Builder or not (the .pbprog extension was a > > good clue though ;-). I got thirteen warnings. (This is the copy in CVS > > right now). > > > > I didn't think it would build at all, since I hadn't installed > > IOPCCardFamily, but since it did I'm guessing it was b/c I already > > installed the .pkg. file. > > > > cheers > > ~swain > > > > --- > > 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 > > > _______________________________________________ > 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 |
|
From: <yu...@ma...> - 2001-10-18 03:46:54
|
Steve, I added your more detailed instructions to the FAQ. I ran out of gas filling in the fine details when I wrote the first version. You don't need to have installed IOPCCardFamily to build the wirelessdriver but I believe you need the IOPCCFamily headers in your ~/Library folder (I've never tried without, so I don't know this for sure). If you have any other suggestions for the FAQ let me know. Yuriwho p.s. Rob will be updating the source soon so get ready to do the dance again On Wednesday, October 17, 2001, at 03:38 PM, Steve Wainstead wrote: > > Hi Rob, > > Just a note that I was able to d/l WirelessDriver and build it with > Project Builder, which I presume is the way to do it. I got > IOPCCardFamily > out of Apple's CVS and built that too (haven't installed either > though). I > posted on the wirelessdriver.sourceforge.net Help forum on how to get > IOPCCardFamily from Apple's CVS. > > All this is only remarkable in that I've never built anything on > Darwin/OSX... been using CVS for years though. I wasn't sure if > WirelessDriver used Project Builder or not (the .pbprog extension was a > good clue though ;-). I got thirteen warnings. (This is the copy in CVS > right now). > > I didn't think it would build at all, since I hadn't installed > IOPCCardFamily, but since it did I'm guessing it was b/c I already > installed the .pkg. file. > > cheers > ~swain > > --- > 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 |
|
From: Steve W. <sw...@pa...> - 2001-10-17 20:38:58
|
Hi Rob, Just a note that I was able to d/l WirelessDriver and build it with Project Builder, which I presume is the way to do it. I got IOPCCardFamily out of Apple's CVS and built that too (haven't installed either though). I posted on the wirelessdriver.sourceforge.net Help forum on how to get IOPCCardFamily from Apple's CVS. All this is only remarkable in that I've never built anything on Darwin/OSX... been using CVS for years though. I wasn't sure if WirelessDriver used Project Builder or not (the .pbprog extension was a good clue though ;-). I got thirteen warnings. (This is the copy in CVS right now). I didn't think it would build at all, since I hadn't installed IOPCCardFamily, but since it did I'm guessing it was b/c I already installed the .pkg. file. cheers ~swain --- 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 |
