Article View: comp.os.os2.programmer
Article #1352Re: realtime application
From: Fred A Putnam
Date: Wed, 02 Sep 1992 23:39
Date: Wed, 02 Sep 1992 23:39
19 lines
1482 bytes
1482 bytes
rvaniwaa@copper.denver.colorado.edu (Ronald J. Vaniwaarden) writes: >In article <Btyt27.JqD@world.std.com> fred@world.std.com (Fred A Putnam) writes: >>... >>time at all because they are being time-sliced with each other and with the >>rest of OS/2. The timer ticks are virtualized, and do not track in real time. >I have often wondered about this idea. Does this mean that if you are >running a program for which you wish to time the length of execution, that you >will get the actual processor time rather than the real time? I know in >Windows, you end up with the real time rather than processor time. You will wind up with the real time, just as in Windows. The virtual timer works the same way in OS/2 as it does in Windows, such that over an extended period of time, the correct number of virtual clock interrupts are delivered to DOS, though they are not delivered at regular intervals. -- Fred Putnam, LABTECH, fred@labtech.com, 1-800-TRY-LABTECH
Technical Details
Message-ID:
<Btz5qF.FFM@world.std.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!eff!world!fredReferences:
<1992Sep2.064726.6351@nuscc.nus.sg> <Btyt27.JqD@world.std.com> <3705@copper.Denver.Colorado.EDU>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.os2.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!cis.ohio-state.edu!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!eff!world!fred From: fred@world.std.com (Fred A Putnam) Subject: Re: realtime application Message-ID: <Btz5qF.FFM@world.std.com> Organization: The World Public Access UNIX, Brookline, MA References: <1992Sep2.064726.6351@nuscc.nus.sg> <Btyt27.JqD@world.std.com> <3705@copper.Denver.Colorado.EDU> Date: Wed, 2 Sep 1992 23:39:50 GMT Lines: 19