xpanmanx, You're quite welcome for the code.

Couple other issues/questions though.

This looks almost like you're expecting this to launch during a logon script. You're mixing code that would show on a DOS CONSOLE window which is one of the reasons for using KiXforms is to do away with that stuff.

You should normally not be showing anything except what can be seen in a GUI format within KiXforms using this method.
    Questions:
  • 1. Do you want the Admins to be able to make choices?
    (if so that can be done within KiXforms as well)

  • 2. If you want the Admin to make a choice then why have different .ini files?

  • 3. Why would you have the .ini configuration files in the same folder as the script unless they are isolated from other .ini files? Currently you're not filtering out specific ones so ALL .ini files would show up in the list.


Personally I would choose one way or the other.
Either DO NOT give the Admin a choice beyond picking which configuration (then have the script automatically perform all tasks listed in the ini file)
OR - Setup the KiXform to show/allow the choices that will be possible to change.

In any case I would remove or silence all code that attempts to ouput to a DOS window and setup the form to run from a shortcut on their desktop and use a COMMON folder on all systems.

Also, I would use a registry read for the firewall and other programs and not HARD CODE the path. If you need help or suggestions further in that area please let us know.

Good luck and best wishes.