FIXCLOCK Copyright (c) Irving Maron 1992-93 All Rights Reserved Introduction FIXCLOCK.EXE permits you to adjust the clock rate of the computer system real- time clock, to speed-up or slow-down clocks that are not running accurately. FIXCLOCK is designed for computer systems whose master, battery-operated clocks can be reset by means of MS-DOS function calls. Installation Procedure The clock rate adjustment is achieved by copying FIXCLOCK.EXE to a convenient drive:path, and inserting the command [drive:][path]FIXCLOCK in the AUTOEXEC.BAT file. The first boot-up after insertion of the FIXCLOCK command will be inter- rupted by FIXCLOCK's installation procedure, which requires entering two clock rate correction constants (in seconds per week). Subsequent boot-ups are not interrupted. FIXCLOCK then checks the system clock at each boot-up, and resets the clock, based upon the clock rate correction constants that you entered during installation. The [drive:][path]FIXCLOCK command inserted in the AUTOEXEC.BAT file should be placed with the setup commands, and before any command that changes the directory from the root directory of the boot drive, or that starts an applic- ation, or that starts WINDOWS. The first correction constant entered, called "Real-time clock rate adjustment", accounts for clock drift on normal days when the computer is turned on and used. The second constant, called "Additional adjustment for non-operating days", is provided for computers that exhibit clock drift, during periods of a day or more when the computer is not booted-up, that is different from the drift when the computer is operated. The additional adjustment is an incremental correction to the first correction constant. If the additional correction is not required, or if you are not sure whether or not it is required, enter zero. Changing Correction Constant To change the correction constants anytime after the initial installation, enter <[drive:][path]FIXCLOCK S> at the DOS prompt from the root directory of the boot drive. Use this procedure to take account of any remaining clock rate inaccuracy noted after initial setup. When entering a new correction constant, use the previous constant adjusted for the additional clock drift. For example, if you initially observed that for periods when the computer is operated, the uncorrected clock gained 30 seconds/week, then the installation procedure would have guided you to enter -30 as the real-time clock rate adjustment (the neg- ative sign for slowdown). If you then note that the clock still gains 5 seconds every 2 weeks (2.5 seconds/week), you should then change the constant to -32.5. (If the clock had begun to lose 5 seconds/week after the initial installation, you would have had to change the constant to -27.5 instead.) The correction constants can be adjusted as many times as you like in order to zero-in on the correct values for your clock. Whenever the correction constants are adjusted, the date and time are recorded in an ASCII file named FIXCLOCK.ADJ in the directory from which FIXCLOCK.EXE is called. This information can be useful in determining the clock drift-rate correct- ion. The date and time recorded in FIXCLOCK.ADJ can be read by entering (from the C:> prompt) either "type fixclock.adj" or "edit fixclock.adj". Additional Note If you enter the command from a directory which is not the root directory of the boot drive, FIXCLOCK will go through its installation procedure (if you permit) and create a configuration file, FIXCLOCK.INS, in that direct- ory. Then if you should enter again from that same directory, FIXCLOCK will adjust the system clock according to the correction constant recorded in the FIXCLOCK.INS file. (It will not correct more than once each day, and not correct at all on any day that the INS file is created or updated.) Therefor, if you are experimenting with FIXCLOCK and find yourself being invited to an installation, you should decline. If you are too polite to decline, then be sure to enter zero for the correction constant. Payment FIXCLOCK was initially made available as user-supported "Shareware", with the request that users pay $10 for using it. The response has been so underwhelming that we have been able to reclassify it as "Freeware". Use it in good health! Irving Maron 76614.2666@compuserve.com April 23, 1995