Message-ID: <3FD500D5.2000509@hyder.org>
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.4.1) Gecko/20030918
MIME-Version: 1.0
References: <20031208192951.DAD18336971@basicbox4.server-home.net>
In-Reply-To: <20031208192951.DAD18336971@basicbox4.server-home.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Mon, 08 Dec 2003 17:53:09 -0500
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Ray Hyder <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] Can't copy to/from server



Jens Glathe wrote:

>On Sun, 07 Dec 2003 23:04:48 -0500, Lewis G Rosenthal wrote:
>
>Hi all,
>
>  
>
>>I realize. What's happening is solely on the client side.
>>
>>    
>>
>>> The signal strength indicator on WifiState drops to yellow and
>>>the system locks up and/or becomes sluggish until I get WifiState closed and
>>>then the system is responsive again.
>>>
>>>      
>>>
>>That's interesting to note. With WiFiState closed, if you start a 
>>transfer, does it behave normally?
>>
Lewis, no it still fails...  As an added bonus when it fails with 
WiFiState closed and you open WiFiState the whole system hangs...


On to Jens comments...

Hi Jens!

>Thinking about this, I recall a note about a PRISM 2.5 hardware error on the linux developer list. 
>Transmit/Receive is using the BAP0 (Base Access Pointer or something like this) register, and IOCTL is 
>using BAP1. I have no real influence on this unless I'd redesign the HCF library. If an access to BAP0 and 
>BAP1 occurs within 5 microseconds, the chip can lock up one or both of the BAP registers (AFAIR) and 
>nothing goes from there. Since 5 microseconds is a pretty short time, but an awfully long time to let the CPU 
>do nothing in between, I don't have a real fix for this. This could happen more often if you have lots of 
>simultaneous transfers going on.
>
Jen's ,  this happens when there is nothing going on (in my case), on 
the lan, except a  copyfile  from one system to the other...  Pretty 
simple...

Bad card?
Bad driver?

Curious minds want to know...   Thanks for your work!  - ray


-- 
 
Ray Hyder
 
=====
 
"It is wonderful to be here in the great state of
 Chicago."
 
 - Dan Quayle
 
=====


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=