Useful Batch files- Homechicken Software-Software Developers' Kit

[Ashenfire]

                     Homechicken Software- Software Developers' Kit (HCS-SDK)

Download Kit

Purpose

• Lay the foundation for any batch programmer to utilize templates from this kit to make personalized batch files for his/her purposes.
• Lay the foundation for any NON programmer to enjoy programs created with the kit tools.
• Maintain control over backup / restore using templates designed specifically for this process, so the programmer can do more designs and less  maintenance.
• Provide a foundation or structure that a new or seasoned designer can utilize newly designed programs with mundane tasks that don't get rewritten every time the programmer creates a new design.
• This is PINNED to show the importance that all the magic starts by downloading the two packed files and installing them in order; for success.

Ver 4
        The install is for developers and users.  It can allow any source and target a user chooses.  Its fast if the installer:

1.  Agrees to the source and target locations.
2.  Presses 'I' to install.
3.  Presses 'U' to update configuration settings in the installation folder.
4.  Presses 'G' to update registry settings.  This is important for running generic programs required for the kit.
5.  Presses 'A' to abort.

            **Deploy Design (part B of the HCS-SDK) allows the user to remove registry entries and still gain access to generic programs.
             All other functions are for people who want extra power or knowledge in their install and want to do more
             than just install and leave.

 

The Homechicken Software Developers kit is a small set of programs that support ALL projects or operate on their own as

handy utilities but not all are necessary to make the projects functional.

For example:
ANSICON.COM
SPCCOUNT.BAT
BOX.BAT
BOX1.BAT
CURSOR.BAT
COLORR.BAT

These programs make ALL other programs operational but it is not desirable to copy them to multiple locations for each
project.  They are installed once and the path is recognized in the environment.

The registry update is optional. It is to save the installed location to be utilized later. It is not necessary unless a new project does
not detect path statements and relies on the registry to correct this.

The registry can be useful also, if the user removed the DeployDesignUtility path statement which is appended to the SYSTEM path.
In this instance, any project using the SDK will HEAVILY rely on a registry statement; instead of the INI declared path statement.

 

Enjoy!

Edited December 25, 2019 by Ashenfire