User ( posted:

Thanks for the correction, after reading your post I seem to remember that
it is not good practice to use the TSLINIT script because of the reasons
you posted and
because if you have a bad compiled module that you are trying to load, the
tslinit script will stop and then Winrunner stops in the middle of
Also you can specify the path of the start up script in the wrun.ini,
under the [WrEnv] heading and the setting XR_TSL_INIT=C:\your start up
script. This is where winrunner
stores the script you specify in the WR options tool.
And I do agree this is a much better way than I previously mentioned,
because if you keep all your compiled modules and startup script on a
network drive
then all you have to do for a new install of winrunner is copy the wrun.ini
to the machine with the new install (win 2000 to the C:\winnt directory)


| ||
| | |
| | |
| | 08/28/2002 |
| | 03:59 AM |
| | Please |
| | respond to |
| | winrunner |
| | |
| |
| To: |
| cc: |
| Subject: RE: [winrunner] How to load a compile module in memory during sta rtup |
The method Michael gave you is fine as far as it goes. Because you have now
modified a 'system' file you will need to ensure that if you install
WinRunner on another PC you make the same alteration.


Use a WinRunner startup script. When WR starts it will run its own
initialisation files, wrun.ini, tslinit etc. and then looks for a user
created startup script to run, if one exists it runs it. This startup
is where you should (as recommended by Mercury) place things like compiled
module loads, global variable declarations, environment settings etc. To
tell WR where its startup script is set it up via the WR options tool NOT
just from the command line as indicated by Michael.

Alan Church
BTexact Technologies