Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Time problems

1 view
Skip to first unread message

Jan Hendrik

unread,
Jun 14, 2009, 12:30:58 PM6/14/09
to
I use GWBASIC.EXE (80.608 bytes)
(it's old, I know, like me)

Sometimes it loses its grip on the time.

For instance
On 17:22:00 time$ prompted 03:52.53
On 17:23:00 time$ prompted 03:54.37
On 17:24:00 time$ prompted 03:56.14
On 17:25:00 time$ prompted 03:57.52
On 17:26:00 time$ prompted 03:59.28

I can't find any relationship between the two.

When I close and subsequent restart the programm it gives the correct
(system-) time.

Familiar to somebody ?
And, found a solution ?
Hope to hear from somebody.


Todd Vargo

unread,
Jun 14, 2009, 4:52:44 PM6/14/09
to

Post your code so we can examine it.

--
Todd Vargo
(Post questions to group only. Remove "z" to email personal messages)

rebel

unread,
Jun 14, 2009, 9:44:39 PM6/14/09
to


Booted to DOS, or DOS in a winbox?

Rob Chambers

unread,
Jun 17, 2009, 3:59:12 PM6/17/09
to
Jan Hendrik wrote:
> I can't find any relationship between the two.

PC internal clocks are notoriously variable, and only tend to update
every 0.2 seconds or so. Many years ago I tried to use it for timing an
experiment, but had to resort to the built-in clock on the A/D converter
card I was using to sample the data.

Rob

Todd Vargo

unread,
Jun 17, 2009, 4:58:01 PM6/17/09
to

I still would like to see the OP's code with an indication of how long
GWBASIC was running for it to return the 1.5 hour difference. Also, it would
be nice to know what "close and subsequent restart the programm" actually
means. It could mean, 1) restarting only the .bas program, 2) restarting
GWBASIC in same COMMAND.COM session, 3) restarting the entire COMMAND.COM
session.

0 new messages