NewsArchive
07-20-2011, 04:00 AM
Hi Friedrich,
I have the following problem:
I use the /E2 switch to specify the folder and file name for the event log.
Example:
setup.exe /E2
C:\Users\Administrator\Appdata\myCompany\Logs\2011-07-19_15-18-21.txt
If my setup detects, that it runs on a "real" terminal server
(application server) and the server is running in execution mode, it
switches the server into installation mode (by calling
%SYSDIR32%\change.exe USER /INSTALL) and restarts itself with all actual
command line parameters.
Now, there is a conflict between the sb event log from the first process
and from the second process.
As a solution, I suggest a new parameter /E3.
The behaviour of /E3 should be identical to /E2 except that /E3 checks,
whether the file already exist. If the file exists, it adds (x) just
before the file extension. x is an consecutive number, starting with 2.
Example:
setup.exe /E3 c:\logfile.txt
If "c:\logfile.txt" exists, SB would use "c:\logfile(2).txt".
If "c:\logfile(2).txt" also exist, SB would use "c:\logfile(3).txt" and
so on.
In addition, I would like to query the actual used log file name with
the full path. This could be done by extend the function "Get System Info".
What do you think?
Thanks in advance.
Markus
I have the following problem:
I use the /E2 switch to specify the folder and file name for the event log.
Example:
setup.exe /E2
C:\Users\Administrator\Appdata\myCompany\Logs\2011-07-19_15-18-21.txt
If my setup detects, that it runs on a "real" terminal server
(application server) and the server is running in execution mode, it
switches the server into installation mode (by calling
%SYSDIR32%\change.exe USER /INSTALL) and restarts itself with all actual
command line parameters.
Now, there is a conflict between the sb event log from the first process
and from the second process.
As a solution, I suggest a new parameter /E3.
The behaviour of /E3 should be identical to /E2 except that /E3 checks,
whether the file already exist. If the file exists, it adds (x) just
before the file extension. x is an consecutive number, starting with 2.
Example:
setup.exe /E3 c:\logfile.txt
If "c:\logfile.txt" exists, SB would use "c:\logfile(2).txt".
If "c:\logfile(2).txt" also exist, SB would use "c:\logfile(3).txt" and
so on.
In addition, I would like to query the actual used log file name with
the full path. This could be done by extend the function "Get System Info".
What do you think?
Thanks in advance.
Markus