DC> KK>   timeouts online and loss of carrier.
DC>   opendoors comm library which automatically checks for
   I thought it might. I have it, registered, with source, but
   never got around to using it. Still moving along with
   classes and no time for personal projects.
DC> KK>   using the BIOS timer, which keeps the system clock
DC> KK>   ticks since midnight. You can find it at 0x0040006c.
DC>   So I could use this instead of the delay() function?
   Right. But I can only speak in terms of DOS on this one,
   and with the caveat that it may be effected by any ISR
   which tampers with the timer and does not adjust the
   increment rate for the BIOS clock properly.
   ( Though they all should, of course. :)
DC>   the delay times REALLY slow down.. but like that spiral
DC>   that was fixed, I want to apply the same idea whereever
DC>   I use the delay fucntion to cut down or lessen these
DC>   slowdowns . :)
   Then the BIOS clock should help.
   You will probably want to make it more friendly by testing
   for a multi-tasking environment early on and setting a flag,
   and then switching timing routines according to the flag,
   using the time-slice to surrender processor time if there is
   a multi-tasking OS in place and a simple loop to burn clock
   cycles if there is not.

> ] Opossums on the Information Rustic Road.....................

---