|
ECS Home Automation and Security Archives |
learn more
| view messages for this
month | NetBloc® | terms of use | search
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects
Subject: From: Date: | RE: [ecs] 2.3.19 released Reynolds,Martin Sun, 29 Aug 2004 11:06:00 -0700 |
Sun, 29 Aug 2004 11:06:00 -0700
Under windows 2000, the windows directory is called "WINNT" not
"WINDOWS".
According to the log, ECS issues the command:
"windows\system32\cmd /c "TASKLIST" proc pid.tmp 2> NUL"
Under W2K Server, this directory does not exist. The command would have
to be:
"winnt\system32\cmd /c "TASKLIST" proc pid.tmp 2> NUL"
But that doesn't work in the more common case of a system directory of
WINDOWS.
So I created a dummy c:\windows\system32 to hold the CMD command. I put
tasklist in there as well. May not be needed, as tasklist is in the
path.
I don't understand why you have to explicitly call out the windows
system directory. It should be in the path by default. There again,
this may be the fix for an earlier problem.
Should probably check with Rob to see if his winnt\system32 directory
has the tasklist command in it - mine does, but I put it there on the
last go around with this one.
-----Original Message-----
From: Mark Gilmore [mailto:mark1@markgilmore.net]
Sent: Sunday, August 29, 2004 10:33 AM
To: ecs@netbloc.com
Subject: RE: [ecs] 2.3.19 released
Hi Martin,
So why the need for these other steps ?
At 12:17 PM 8/28/2004 -0700, you wrote:
> >
> >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"
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects