Hello!

 KK> Spinning_Cursor(char *prompt) { char *spinner = "|/-\"; clock_t go;
 KK> int spin = 0, keypress; output_function_string(prompt); do { spin %=
 KK> 4; output_function_char(spinner[spin++]); go = clock() +
 KK> CLOCKS_PER_SEC / 2 /*   This calculates the clock value of a
 KK> half-second delay, but not an absolute hard-coded delay. It is
 KK> dynamically responsive to system events. Continuation of code
 KK> execution will be tested against this clock value, and will proceed
 KK> as soon as it is exceeded, whether within the loop, or within other
 KK> code. */ do { keypress = input_function(); }  while(!keypress
&& go >
 KK> clock()); connect_error = test_connect(); }  while(!keypress &&
 KK> !connect_error); return keypress; }

The text editor messed this all up, but anyhow.. I used your
function and it worked MUCH better.. it still slows down/speeds
up under a multi-node, multitasking situation, but much less
noticably... thanks a lot... what were the
connect_error/text_connect functions for?  I'm going to modify that
function and use it wherever I use the delay() functions..because
under multitasking, these delay times also vary..sometimes even
doubled in length to what they are supposed to be.


Ciao!

... Careful planning is the key to safe and swift travel.
-*- SabreEDIT v1.72a+ [STS97]
--- Ezycom V1.48g0 01fa0167