Subject: From: Date:

RE: [ecs] 2.3.19 released Reynolds,Martin Sat, 28 Aug 2004 11:34:18 -0700

---

 Sat, 28 Aug 2004 11:34:18 -0700
I think that I got it...

Console now behaves as expected, browser autospawns.

The workaround is:

Create c:\windows\system32 (default system directory is is "WINNT" under
server 2000, not "windows")

Find a copy of cmd.exe form another system and stick it into the new
directory.

I put tasklist there as well, but I don't think that is necessary.
Maybe we just have to add cmd to the ecs directory. Didn't try that. I
don't know if the explicit path overrides the default path.



Console log below:

8/28 11:23:58 S EXE:cmd=TASKLIST > proc pid.tmp 2> NUL dsp=0
8/28 11:23:58 S EXE:cmd(win2000)=\windows\system32\cmd /c "TASKLIST >
proc pid.tmp 2> NUL"
'\windows\system32\cmd' is not recognized as an internal or external
command,
operable program or batch file.





-----Original Message-----
From: Mark Gilmore [mailto:mark1@markgilmore.net] 
Sent: Saturday, August 28, 2004 6:38 AM
To: ecs@netbloc.com
Subject: RE: [ecs] 2.3.19 released

if you enter "TASKLIST" in the \ECS directory (at cmd line), does it not

run the pgm ?
if not, then the copy was not properly done.

At 09:14 AM 8/27/2004 -0700, you wrote:

>Doesn't solve the problem - should I have copied it to c:\windows?

---