Dan
We've had no problems running it on our server. We setup batch files called
monday.bat, tuesday.bat, ... and a daily.bat that are scheduled to run on
the days the file say. Then we can add to or remove from those batch files
without ever touching the finicky AT command lines.
However, on another NT server we could never get the scheduler to run any
batch files, they always came back with an error status. So go figure.
You could send me your 'at' commands if you want me to look them over or
try them on another system.
Related Question for Stephen: Since we run analog as a scheduled task it
runs when no one's around to watch the output, but I'd like to log the
analog output. I've tried just redircting (e.g. anaolog >analog.log) but
the Win32 binary version doesn't seem to write to STDOUT, so nothing gets
to the logs. Is this a compile/platform thing, a code thing or is there
another way log the output from analog?
Thanks,
Jeremy Wadsack
OutQuest Magazine
a Wadsack-Allen publication
[EMAIL PROTECTED] wrote:
> Hi, first time post. I have read all the documents I could find and did
> not see this answered anywhere. I am trying to run analog on a windows
> NT server with the WINAT command scheduler. I do this with several
> programs and it works fine but I have been unable to make it work with
> analog. ANy suggestions or ideas would be appreciated.
>
> Dan
--
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------
