Achim wrote:
choice doesn't wait the specified number of seconds, it's waiting time
is shorter
this breaks compatiblity with ms/pc/drdos batch files
eg. 3 seconds if 6 is specified, 6 seconds if 20 is specified, 16 if
60 and so on
(tested only on win98 dosbox) msdos', pcdos' and drdos' choice
commands work perfectly on win98

Subject: using delay()

Weird.  I confirmed this.  When I wrote the code, I used a delay()
function to wait 500ms, so the program should have a resolution of
1/2sec.  The code is:
>   /* Grab the key.  Don't exit until we found it. */
>
>   for (wait = 0; ; wait++)
>     {
>       if (def_wait > 0)
>     {
>       delay (500);            /* wait for half a second */
>
>       if (kbhit())
>         {
>           key = getch();        /* grab the key */
>         }
>       else if ((wait * 2) > def_wait)
>         {
>           key = def_key;        /* grab the default key */
>         }
>     }
>       else
So maybe I did something wrong?  If you use /T:y,5 then this part of
the loop should execute at max 10 times (1/2sec * 10 = 5sec).  I
wonder if delay() isn't working properly on faster hardware???

Changing owernship to Jim Hall

Hi, you should really use sleep(seconds) rather than delay(milliseconds),
because delay() often gets the timing wrong if you use an old compiler
along with a fast CPU. Sleep uses the clock time so it is more reliable.
Delay often uses a delay loop. You can also read out the timer tick
counter at $40:[$60] to have some reliable clock with even 1/18 second
resolution.

Fixed in version 3.7.  Thanks!