CLOCK

These are the files you need. You can send them from the package contents below.

• CLOCK.COM → A:\SOFT programa de DOS 7.9 KB

No need to put FILE_ID.DIZ, CLOCK.DOC: they are manuals, source code or supporting material. Read them here and save 44.8 KB on a 1 MB disk.

1. Copy CLOCK.COM to A:\SOFT. They are DOS programs: run them from the DOS icon, or add A:\SOFT to the PATH in C:\AUTOEXEC.BAT to call them by name.

Derived from the package contents and the 200LX conventions. It installs to A: on purpose: C: is a RAM disk and every byte there is memory taken from the system.

than installing CLOCK after the other program has started, which is
     usually impossible).  You need to either DISABLE CLOCK (with CLOCK /D or
     Ctl-Alt-C,Esc), or put CLOCK exactly where you want it to be on the
     screen BEFORE you start this kind of program.





                        CLOCK 2.12            Page 16 of 22



     Because CLOCK is continuously writing over the top of whatever the
     running program is trying to put on the screen, CLOCK needs to know what
     the program is trying to put on the screen.  CLOCK needs to know this so
     that when the CLOCK moves or becomes hidden (by DISABLING CLOCK, page 7,
     or by moving the screen cursor under the CLOCK), CLOCK can "restore" to
     the screen what is supposed to be there when CLOCK isn't.

     There are two ways programs can write things to the screen.  The first
     is by writing directly to video memory (which is very fast, but has
     compatibility problems), and the second is to go through the Operating
     System (DOS) and the BIOS using the Video Interrupt (slower, but more
     compatible with other programs like CLOCK).

     When you see CLOCK flashing on and off, it is because CLOCK is
     temporarily "hiding" itself when it thinks another program is trying to
     do something with the screen.  As soon as CLOCK thinks the other program
     is done with the screen, it turns itself back on.  The reason CLOCK
     sometimes "messes up" the screen for other programs is because CLOCK
     can't always tell when another program is doing something to the screen.
     CLOCK does the best it can, but unfortunately isn't perfect.

     If a program writes to the screen using the Video Interrupt, CLOCK
     "intercepts" things, and is able to keep track of what is supposed to be
…

Literal excerpt from CLOCK.DOC, exactly as it came in the package.