Hello Peter,

We are a little bit confused about what you said (or what we understand you
said :-) ) last year in Colorado and what the Toolkit 3.0 online help says.


Please can you explain the exact difference between

"Normal Read Timeout" (NRTO) and "Wait for something" (WFS).

assume a request for 3 characters (DosRead) with a Timeout of 100ms.
(the read request is done at time : 0. x means a character arrives
at this time on the machine).

          0         50       100       150       200       250  ms
          | . . . . | . . . . | . . . . | . . . . | . . . . |
 Case 1   |         x         x         x
 Case 2   x         x         x
 Case 3   |        xx                       x
 Case 4   x         x                       x
 Case 5   xx                  x
 Case 6   xx                                x
 Case 7   x                  x                  x


            NRTO         WFS
 Case 1:    150ms         ?
 Case 2:    100ms         ?
 Case 3:    150ms+TO      ?
 Case 4:    150ms+TO      ?
 Case 5:    100ms         ?
 Case 6:    155ms+TO      ?
 Case 7:    198ms         ?

Here are my problems:

I cant see a difference if a device driver is at the gebin in state NRTO or
- as the toolkit docu says in case of WFS - in state "NoWait" (NW) and
"at the time the request would have completed due to No-Wait
processing," change into state NRTO.

Also i cant understand, if in
 "... it waits for some data to be  ..."
the some means that after the change of state the read waits for 1 character
(with a maximum timeframe of TO) or if it waits for all of the charachters.

maybe this is exactly the difference?

Here from Toolkit 3.0 online help:

  If the physical device driver is doing Wait-For-Something Read Timeout
  processing, the physical device driver processes the request initially as
  if it had No-Wait Timeout processing.  If no data was available at the
1>time the request would have completed due to No-Wait processing, the
2>request is not completed.  Instead, it waits for some data to be
1>available before completing the request.  However, the physical device
1>driver does enter Normal Read Timeout processing for this request.
  Therefore, if no data is available after the Normal Timeout processing
  interval, then the request is completed anyway.  The request never
  waits longer than it would have due to Normal Read Timeout
  processing.


 WARPED!, Mario

---