Message-ID: <20030731224201.89999.qmail@web13205.mail.yahoo.com>
In-Reply-To: <auto-000175636071@admin.nni.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 31 Jul 2003 18:42:04 EST5EDT4,M4.1,M10.5
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Jonas Buys <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: OS/2 Wireless Users List: Still Don't Get It.


--- Stanley Sidlov <stanleys@cybernex.net> wrote:
> On Thu, 31 Jul 2003 11:02:25 EST5EDT4,M4.1,M10.5,
> Jonas Buys wrote:
> 
> >
> >Channels!!  You have 11 channels in US, 13 channels
> in
> >EU, and some other number in Japan.  All devices in
> >the same WLAN must also have the same channel. 
> This
> >is a more precise specification of the 2.4GHz band.
> >XP's drivers might have another default channel
> than
> >the default one by the OS/2 driver.  You should
> verify
> >that both WAP and PCCard have the same channel.
> 
> So can you specify which channel?  I'm using channel
> 10 on the AP as it seems to work better around
> the house. The AP is supposed to be good for 800"
> (255M), and so is the card.  Channel 10 is reputed
> to be less spread spectrum (I've read elsewhere) and
> I looked and modified the NIF parameters in MPTS,
> The SSID match, the WEP128 Key 1 match, and Key 1 is
> specified. Still nothing. You feel that the
> actual NIF that loads should also be modified to the
> most common settings?

Try to get everything running without WEP first.  WEP
is something special in some cases, I've experienced.
I don't quite understand your question about the NIF
file.  Anyway, once that PDF is complete I will put
online newer NIFs with settings that make more sence
then "Merry Christmas!" SSID names or so :)

> >HÞhÞ, XP hides the hardware details from the user.
> >That why most users having HW troubles on XP can't
> >resolve them :)
> 
> But I use the manufactuer's driver and
> configuration. I can easily set the SSID, WEP
> encryption and
> password, and even force the channel if I wish. The
> issue for me was simply that I had to learn to use
> the IBM Connections software to create profiles that
> disabled the 'other' nic when activated, so that
> I could switch between the Intel NIC and the PCCard.

I see.

> >Consider it some "bug" in WifiState.  Please! 
> FIRST
> >configure your WLAN using the REAL tools, thus MPTS
> >and the NIF file, and then use WifiState!
> 
> What real tools? EPM and MPTS?

What does EPM comes to do in the game?  Just MPTS is
enough.  When you add a network card in MPTS, then it
appears in that lower left field, you just select it
and click the Edit button, and you needn't use EPM. 
Of course, if you find it easier to edit the NIF file
using EPM, you can do so, it's the same anyway. (And
yes, those were the tools I referred to).

> >You needn't change this setting (IRQ) for NetGear
> and
> >LinkSys, it's done automatically.  How?  Well, as I
> >said, Open MPTS, install driver, click driver in
> lower
> >left field, click Edit or somewhat similar...  Then
> >enter the decimal number in the appropriate field,
> and
> >that edits the NIF automatically.
> 
> It appears to grab the lowest one, and I need it for
> a USR/DELL Modem card. How's polling work, well
> or poorly?

Polling?  That's an outdated technique; I really
wouldn't waste time on that.  About performance, I
daren't say; I've never personally used it.  But I
read somewhere that it is sometimes used for printers
(DOS), but that it has its limitations.  If you need
that particular IRQ for DELL card, then change the IRQ
for the wireless LAN card to an IRQ that is either:
1/ Not used yet, thus you assign a unique interrupt
integer to the WLAN card
2/ You use a shared interrupt.  YES, it's possible in
OS/2, but you MUST mind that all drivers of the
devices that share the same interrupt support shared
interrupts.  Anyway, the WLAN drivers support sharing
of interrupts.
I would recommend the first option.

> >MAC?  Why do you need that for?  I've tested all
> those
> >cards over here
> 
> It has been suggested that MAC access to the AP be
> enabled if available, as a extra precaution against
> non-authorized access. However, it is disabled at
> the moment on the AP. I would suppose that you could
> use this to clone an MAC address so long as you were
> the only one at that AP it may be alright.

I see.  Well, seems interesting, will test it with
some of the WLAN cards over here when I can find the
time.

Hope this helped you...
Regards, JB/2.

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=