Variable transition from external file to Window's system registry

Hard core C programmer needed to modify existing personal firewall program written in C (compiled under Cygwin's gcc compiler) for the Windows OS. This is the first of many projects to come modifying the current application. As such, this project acts as both a learning exercise and a doorway to future assignments to the successful bidder. Currently all user defined variables (or 'options') are being stored on five (5) external text files which reside on the same directory of the application, and can only be changed by editing the files. The project's objective is to convert this method of storing / changing the options by a combination of the four methods listed on the enclosed word document. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Complete ownership and distribution copyrights to all work purchased. ## Platform Windows 95 Windows 98 Windows 2000 Windows NT Windows XP Internet Explorer 5.0+ ## Deadline information Programmer must be willing to work on all future phases of the project. TIME EXTENSION WILL NOT BE GRANTED UNDER ANY CIRCUMSTANCE. Coding Guidelines: 1) A log file should be maintained to list any of all project files that have been added / removed / or, changed. 2) Comment as much as possible within the source code. Comments can help or they can clutter. They help when they are differentiated from the code they describe. One line comments do not offer effective separation between the comment and the code. Block identifiers do, by surrounding the code with a clear, definable pattern. Example: /****************************************************************** * This will stand out clearly in your code! *****************************************************************/ if ( thisVariable == thatVariable ) { DoSomethingVeryImportant(); } ...