| ECS Home Automation and Security Archives |
| Subject: From: Date: | RE: [ecs] 2.3.19 released Mark Gilmore Sun, 29 Aug 2004 12:21:25 -0700 |
ok - will do At 11:20 AM 8/29/2004 -0700, you wrote: >Why not: > >"cmd /c "TASKLIST" proc_pid.tmp 2> NUL" > >This should work as long as tasklist and cmd are present, and in the >path. > >W2K server is dead anyway, if it does not have the tasklist command >loaded (which I think is the case). > >This way, you won't get burnt by Windows loads that are named something >other than "windows" - happens when you reload a system, but want to >keep the original system directory. > >-----Original Message----- >From: Mark Gilmore [mailto:mark1@markgilmore.net] >Sent: Sunday, August 29, 2004 11:15 AM >To: ecs@netbloc.com >Subject: RE: [ecs] 2.3.19 released > >ok - there are apparently very significant differences btw various >win200 >systems. >i'll make ecs look in both dirs in the next rev. >thanks > >At 11:06 AM 8/29/2004 -0700, you wrote: > > >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" > > > > > > > >--- > >Incoming mail is certified Virus Free. > >Checked by AVG anti-virus system (http://www.grisoft.com). > >Version: 6.0.742 / Virus Database: 495 - Release Date: 8/19/2004 > >Mark Gilmore >http://OmnipotenceSoftware.com > > > > >--- >Incoming mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.742 / Virus Database: 495 - Release Date: 8/19/2004 Mark Gilmore http://OmnipotenceSoftware.com
--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.742 / Virus Database: 495 - Release Date: 8/19/2004