	While writing programs that use an initialization (ini) file, a programmer often refers to the ini file to observe the most recent changes made by the program. This helps to determine if the program under development is writing information or settings to this file in the way it should.
	Before the advent of Initialization Monitor, this ini file had to be opened manually with a text editor each time a change was made in order to inspect the results of those changes. Initialization Monitor is designed to eliminate this need and to make it easier for the programmer to visually compare the recent changes in the ini file. This is accomplished by directly comparing the last version of this file to the new version, side by side, in a dual screen editor.
	Another benefit of this program is the way it automatically pops up to the top of the screen each time there is a change made to the ini file. This is particularly beneficial to a programmer whose screen is already overcrowded by the Integrated Development Environment (IDE) in use. This feature will even work when writing DOS programs. If the IDE is run through Windows, Initialization Monitor will minimize the DOS program and then pop up for inspection.
	Initialization Monitor was originally written by a programmer for programmers. However it can also be used by the average user to monitor initialization files while installing new Windows programs. Multiple files can be monitored by running multiple instances.
	The Initialization Monitor program is NOT Freeware. It is a shareware program. That means if you continue to use it you should send in your registration form and fee. However, for a mere $5.00 you can become a register user. This fee is intended to supplement the expenses incurred by creating such useful programs, and also as an initiative to create an update of the product. Feel free to send in your suggestions on improvements to the program, or even ideas of programs that you would like to be made available.
	This program requires two files to run. VBRUN300.DLL and CMDIALOG.VBX should be placed in the c:\windows\system directory before running Initialization Monitor.