What exactly would you like to know about Wrun.ini?
There are quite some things that you can play around with in that file, but what the heck for??
Normally this file should be left untouched...
Unfortunately, I will have to disagree with lior, this file is an important part of the tool configuration management, but only in companies with no established WR set up protocols. My rational is the following – if a group has been using the tool for a while, it will most likely come up with an automated installation and configuration procedure to minimize the need for hand-tweaking the suite.
Instead of going through each of the parameters, allow me to supply a use case for wrun.ini. An advanced user may use this config to load a set of compiled modules or call a harness (another config) controlling the modules. There are actually quite a few parameters in the file, and one can specify a great deal of configuration settings via wrun.ini; still, for the most part, it is used by those a bit more advanced, and to some extent by those who prefers to modify application configuration through file manipulation, rather than associated wizards and menus.