We like the additional command about debug <on | off>.
We suggest to add the same capability for console output.

New command will be console <on | off>.

Action: enables (CONSOLE ON) of disables (CONSOLE OFF) which
influence the way screen output will be handle.
Syntax: CONSOLE < ON | OFF >
Remarks:
By default the user will see kixtart output on his screen.
To prevent this you can use CONSOLE OFF. It will
have the same effect as kixtart function:

RedirectOutput("nul")

but it doesn't the actual RedirectOutput setting.

Thanks.

Ruud

We suppose that SetConsole("Hide") has not the same effects as the usage of console-less kix32.exe version.

Possible difference is that the console-less version prevents a console window before the first kixtart statement will be executed.

We start not only a script from a windows environment but also within in a dos-box. For the last situation the SetConsole is not wanted. Our goal is that an user doesn't get any kind of output by using console command.
Greetings.

I agree with MCA idea about command: CONSOLE <ON|OFF>, but note that the console window should be hidden at the first time when kixtart running, until CONSOLE ON or SETCONSOLE("SHOW") statement executed.

I also concern about synchronous logon script execution especially in windows 9x, when I use the console-less version of kixtart, the logon script executed asynchronously, and vice versa for the standard version of kixtart. I think it would be a good idea to make synchronous logon script execution also for console-less version of kixtart.

Thanks

We do some checks with following code:

code:

---

  IF setconsole("hide")
  ENDIF
  ? "show 1"
  console off
  IF RedirectOutput("con")
  ENDIF
  ? "should be invisible for users"
  console on
  ? "show 2"
  IF RedirectOutput("kix-info.txt")
  ENDIF
  ? "show 3 - output kix-info.txt"

---

We run different kind of runs:

• kix32c script.kix
  show 1
  should be invisible for users
  show 2
  
• kix32c script.kix -i
  show 1
  should be invisible for users
  show 2
  => the parameter "-i" doesn't have effects.
  
• kix32 script.kix
  => a console window will be opened
  
• kix32 script.kix -i
  => nothing happens on screen.
  => this shows the situation we wanted. only we want it for a part
  of the script.
  

By implementation of CONSOLE command we want to see

code:

---

show 1
show 2

---

With the CONSOLE OFF command:

• we don't need to change the kix32/kix32c call. no additional -i
  parameter is required.
  
• using it in the script will ensure us that no output will be generated
  to the screen.
  
• using it doesn't required a change of RedirectOutput or other settings.
  only all output to screen (= CON) will be suppressed.
  

Greetings.