Message-ID: <41AF82A0.7010901@clanganke.de>
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4a) Gecko/20030401
MIME-Version: 1.0
References: <20041201201159-38559-8@molen> <41AE1C07.2040706@clanganke.de> <200412012309289.SM00249@basement> <200412012340226.SM00249@basement>
In-Reply-To: <200412012340226.SM00249@basement>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Thu, 02 Dec 2004 22:01:20 +0100
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Christian Langanke <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] Wireless LAN Monitor

Will Honea wrote:

>** Reply to message from "Will Honea" <whonea@codenet.net> on Wed, 1 Dec 2004
>23:09:55 -0700
>
>
>  
>
>>Christian, I was wondering where the the standalone program is at present - all
>>I see on Netlabs is the Xwlan widget binaries - unless I'm seriously missing
>>something.
>>    
>>
>
>Never mind - RTFM!  
>
Yes :-)

>I'd still like details of any build peculiarities - it
>looks too straightforward to be true as it is <g>.
>
Until now I missed to implement a makefile.inf, as I did for other 
projects, I think about doing that in a resonable timeframe.

But the makefile with one exception checks for all required components 
(toolkit, compiler, HText/2 precompiler), please see bin\required.txt or 
just execute nmake (at least therefore you require the eCS Toolkit).

In addition to that you need to make the Workplace Shell Toolkit (WPSTK) 
available (wpstk.netlabs.org), but ... unfortunately the current XWLAN 
uses APIs not being included in the currently available V1.20 of that 
toolkit, but only in the cvs dev  tree of it (I have still to ship that 
binary release). So you would need to compile that on your own and 
create a binary package in order to build the current XWLAN. The 
drawback of that approach is that for the XWLAN project you would neet 
to extend the INCLUDE and LIBPATH to the correct directories of the 
source tree of your compiled WPSTK.If you can wait for the next binary 
release, this would be much more easy for you.

Other than that, it _is_ straight forward, this is one of my principles 
I strictly follow when setting up projects on netlabs.org.

I will add an entry to bin\required.cmd for the WPSTK.

 From your previous mail:
 >If you have dropped those builds, I'd like to pick that up without the 
emx dependencies.

There is none available with emx dependencies. While the project 
supports IBM C Set/2 and VAC3, it does not support the gcc at all 
(unlike the Workplace Shell Toolkit)

 >If you have a quick tutorial

Sorry, still missing. You can do nothing more than execute nmake in the 
working dir to learn about the make symbols you can use, this will 
explain the modules of the tree.

 >and possibly a pointer the to buglist as of where you dropped this 
version I should be able to catch it up fairly quickly.

AFAIK there are no known bugs.

 > Ulterior motive here - all my development and debug stuff is for 
VACPP or
 >Watcom and I've got to port the D-Link driver anyway.

VAC 3 is supported (it may work with VAC4 also). If you intend to port a 
driver for a given PCMCIA card, and would like to implement the 
interface to Wireless LAN monitor,  you should concentrate on 
src\lib\drvapi, and int her onto the module drvaccess.*  Please note 
that not all WLAN_SIGNAL* and WLAN_STATUS_* symbols are implemented by 
the driver, this is documented in the header file.

These calls are used in the common GU library (see src\gui\common), 
which contains most of the widget code, being called by the executable 
frame modules (src\gui\wlanstat and src\gui\xwlan).


If you have knowledge on how to access PCMCIA hardware, it may make 
sense that you contribute to Willibald Meyers NDIS wrapper project, 
which is pre-alpha and can load Win32 NDIS drivers, including Wireless 
LAN drivers. While the author currently works on supporting minPCI 
(XWLAN) cards, he has no knowledge on PCMCIA. So if you could bring in 
that knowledge, your D-Link problem may be solved even without a driver 
port, and it would help to support lots of other PCMCIA cards as mell. 
If you are interested in that, please contact Adrian Gschwend and tell 
him, send email to: ktk@netlabs.org

thanx, 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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=