RE: Stupid cfexecute

2001-12-06 Thread lsellers
At 01:55 PM 12/6/2001 -0500, you wrote: >I just tried it without a timeout value and it goes through but the program >doesn't work. I have tried calling it through cmd.exe and it does not return >more than 2000 characters. It just doesn't seem to work with CF 5. Rmtcmd >sends a remote command to t

Re: Stupid cfexecute

2001-12-06 Thread Jamie Jackson
II >Dixon Ticonderoga >Web Developer Extraordinaire > >-Original Message- >From: Jamie Jackson [mailto:[EMAIL PROTECTED]] >Sent: Thursday, December 06, 2001 1:36 PM >To: CF-Talk >Subject: Re: Stupid cfexecute > > >Two questions: > >*Have you tried it wit

RE: Stupid cfexecute

2001-12-06 Thread Adrian Cesana
, 2001 10:55 AM To: CF-Talk Subject: RE: Stupid cfexecute I just tried it without a timeout value and it goes through but the program doesn't work. I have tried calling it through cmd.exe and it does not return more than 2000 characters. It just doesn't seem to work with CF 5. Rmtcmd send

RE: Stupid cfexecute

2001-12-06 Thread Robert Everland
t Everland III Dixon Ticonderoga Web Developer Extraordinaire -Original Message- From: Jamie Jackson [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 06, 2001 1:36 PM To: CF-Talk Subject: Re: Stupid cfexecute Two questions: *Have you tried it without the timeout attribute? *Have you

Re: Stupid cfexecute

2001-12-06 Thread Jamie Jackson
Two questions: *Have you tried it without the timeout attribute? *Have you tried name="c:\\winnt\system32\cmd.exe" (admittedly, I don't know what rmtcmd.exe is) *How much data does this return when done at the command line? (A reply to one of my old posts follows) >Actually, there is an "undocume