I'm new to kix scripting, so there's probably a very simple answer to this.
Background: I've written the following simple script - WRITEPROFILESTRING ("C:\windows\GSS.INI" ,"LAN" , "User ID" , @USERID) ..which is followed (in a batch file) by calling a network exe to start the application that uses the above ini file.
Problem: When the program launched from the batch file it leaves a dos box in the background which will confuse my rather simple users...
Question: Is there a way, in a kix script not a batch file, to launch the application, maybe sleep for 2 seconds and shut down the dos box with out shuting down the application?
I've actually just figured this out myself. If you call the application from within the script, doing away with the need of a batch file, create a shortcut with the following command line; c:\windows\wkix32.exe -i kixscript.kix .. instead of; c:\windows\kix32.exe kixscript.kix ..the script will run in invisible mode and not cause a problem.
This is probably really obvious for seasoned kixtarters...
well, does the program produce the box or kixtart? wkix32.exe should not itself produce a window if you don't make it to (in that case -i needed)
your simple script just needs to silence the outcome. so, instead of: WRITEPROFILESTRING ("C:\windows\GSS.INI" ,"LAN" , "User ID" , @USERID) just use: $returncode=WRITEPROFILESTRING ("C:\windows\GSS.INI" ,"LAN" , "User ID" , @USERID)
that is explained in faq. think it was "console displays 0's and 1's or similar, check that out. and then, once this correction is done, just fire the proggy up with run. this way, the script will exit. if you fire it with shell, your script will stay there and reserve some 2-6 megabytes of ram.