Last year I find an excellent script from Fabian which collect the user & software & network information.

In one of the line:

SHELL "%Comspec% $CommandOption c:\windows\command\sort.exe < C:\Temp\Tmp1.dat > C:\Temp\Tmp2.dat"

It work excellent in win9x and NT. But you know win2k is about to launch in our school. I just find that the above line will pop up a crash like messagebox and will terminate the script. How can I solve this?

I am sorry that I haven't check will sort.exe are already installed in Win2k the path "c:\windows\command\", but I think if there are no such execute file, kixtart should just by pass.

Thanks for anyone concern.

Gilbert Ng

Anyway, the command works with the aforementioned mods.

You probably don't need to specify where SORT is as it either in 9x or NT/2K as it is in the search path.

- Kent

[ 08 September 2001: Message edited by: LLigetfa ]

Kyder is right when he says "probably" and Les is right when he says to use the variables (IMHO)...

We have found a few machines in our orginization that would not run any programs from the command prompt that normally would. It turns out that some piece of software had improperly edited the path and caused the windows folder along with a few other folder to no longer be in the path.

Example: the %windir%\notepad.exe in this case would still work but notepad.exe alone would not along with any other programs in the windows folder.

Myself I try to use the Registry or SET variables whenever possible to point to the correct path, but on most machines it should work just by calling it as Kyder says.

Must confess, I was shooting from the hip. I need to make sure brain is engaged before putting mouth (fingers) in gear! %systemroot% would only work from NT/2K. Win95 has no such variable. the nearest equivalent is %windir%. MurphyProofing is the part of programming I really hate. Having to anticipate waht may go wrong and coding for it.

Gilbert,
Spark up a CMD window and run your script from it. Any KIX message that may flash and disappear will stay in the CMD window. You could add a few print lines and pause with get $ to determine if it is really crashing on that line. Also, try running the script with the /d (debug) switch and step through the script.

Let us know how you make out.

[ 09 September 2001: Message edited by: LLigetfa ]