Message-ID: <3F39BD2E.3000109@2rosenthals.com>
Organization: Rosenthal & Rosenthal
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4; MultiZilla v1.5.0.0) Gecko/20030622
MIME-Version: 1.0
References: <auto-000178707975@admin.nni.com>
In-Reply-To: <auto-000178707975@admin.nni.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 13 Aug 2003 00:23:15 EST5EDT4,M4.1,M10.5
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Lewis G Rosenthal <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] That T23 of mine....

Stanley Sidlov wrote:

>On Tue, 12 Aug 2003 23:23:26 EST5EDT4,M4.1,M10.5, Lewis G Rosenthal wrote:
>  
>
>>If Wi-Fi, 
>>then this (almost) makes sense. The card being recognized by card 
>>services doesn;t necessarily mean that it has been initialized & bound 
>>to any protocols (can't be bound until it's initialized; merely having 
>>resources supplied to it doesn't get it initialized, either, as it needs 
>>to have recognizable - recognizable by the NIC driver - resources 
>>assigned to it, and not just whatever's free). If the protocol isn't 
>>bound to it, you can't do DHCP, as you can't broadcast a DHCP discover 
>>packet to find a DHCP server, let alone do anything with an address from 
>>one.
>>
>>    
>>
>Then why with an older version of PCCard does it work? The only thing I am changing are the drivers for the PC Card Director software. Older version, the wifi nic binds and get DHCP at boot. 
>
Probably because, as Oliver has pointed out, some of the newer PCCard 
stuff actually backlevels some components. In particular, I would look 
at AUTODRV2.SYS.

>>I don't get the speed difference at 
>>all. I don't see what would have changed, unless there was some resource 
>>conflict which was bogging the card down before.
>>    
>>
>
>That is what I'm trying to find. 
>
>Does anyone know what the full list of IBM drivers replaced by the entire DANI Suite as setup in eCS's download replaces? 
>And does anyone know if PC Card Director is actually compatible with the DANI drivers with the PCM support? 
>  
>
Well, as Dani is on this list, she'd be the one to provide a definitive 
answer. However, from the 1.6.1 docs (which happens to be the latest doc 
version I have expanded):

    The driver attaches to OS/2's PCMCIA subsystem and takes over all
    PCCards with a function id of 4 (disk) and function extension 1 (ATA
    interface)

This indicates to me that she's only taking the place of PCM2ATA.

My understanding form what I've gleened from this list and others is 
that her driver is indeed fully compatible with PC Card Director. I've 
seen no difficulties with it.

The more I think about this, though, Stan, the more I think there may be 
a DMA issue involved with that Wi-Fi NIC and perhaps the way in which 
Dani is scanning the PC Card bus. At that, though, I think I'll stop 
jabbering and wait for someone with a better handle on this stuff to 
comment.

-- 
Lewis
---------------------------------------------------------------------
Lewis G Rosenthal, CNA
Rosenthal & Rosenthal            :  Accountants / Network Consultants
New York / Northern Virginia     :                www.2rosenthals.com
Novell Users International       :                 www.whytheylie.com
OS/2's new face is eComStation   :                www.ecomstation.com
--------------------------------------------------------------------- 
This OS/2 system (Apollo) uptime is 0 days 06:16 hours and 32 seconds


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=