Gidday all,
I continue boggled.
After Peter Harrison made this helpful suggestion yesterday:
> > Yep. Logging on as administrator does not give the scheduler
> > administration rights. If you look in your services for the scheduler
> > and select thr startup button you will see that you can change the
> > logon, and thus permissions of the scheduler.
...I said I'd try it. I did -- on three machines. The schedule service
is set to run as the administrator, and the machine is rebooted,
and a dirt-simple command like THIS is queued:
at 10:24 "cmd /c dir >c:\output"
...and it is confirmed as being in queue ok with a simple "at"
...and 10:24 rolls around and there is a split-second of disk
activity, but no "output" file. The exact same command run
without the "at" generates the output file just as expected.
I've tried "/interactive" (not that it should matter) with no effect. I've
tried running more substantial programs which would leave
evidence of having run (they don't). I'm absolutely flummoxed by
this.
Machines are both NT 4 SP3, nothing unusual about 'em that I
know of... Surely the scheduler is SO commonly used that we
must be missing something obvious here????
Further suggestions, or an ice pack, much appreciated. (That's
pAck, not pIck, folks <g>).
cheers,
peter
==================================================
Peter Hyde, SPIS Ltd, Christchurch, New Zealand
* TurboNote: http://TurboPress.com/tbnote.htm
-- small, FREE and very handy
* Print-to-Web automation http://TurboPress.com
* Web design, automation and hosting specialists
Find all the above and MORE at http://www.spis.co.nz
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
