Mark Sirota <msirota@isc.upenn.edu> wrote:
> In any case, since any decent software will be written either for MS-DOS
> or Win32 these days (sigh),
Fear not, world-weary Micro-serf, the revolution is at hand, and it flies a
penguin on its banner. :)
The Linux juggernaut is coming. Sell your Micro$soft stock.
> it would be rash to rely on the PC or the
> OS to do the timing. You must use an external timer, or one provided on
> a card.
I agree that some sort of external timer or timer card is the way to go here. It
should handle the start events, stop events, and any reset events (from workers
tripping lights, etc) and then push raw times onto some sort of sequential
stack, perhaps generating an interrupt to signal the arrival of a new time.
Even better, it could shadow the stack in NVRAM - so that if the computer
crashed (Win1901 version) all the times would still be available.
Done this way, the computer and OS are relieved of any real-time timing issues.
Heh, team.net is starting to read more and more like linux_kernel. :)
DG
|