Hello.
I am using windows schedules.
For some reasons one of the schedule stopped running.
I was since there was a fix of summer-time (from 12:30am to 1:30am) at the
same minute the schedule runs (it runs at each minute).

The schedule stopped running and I think it's due the above problem.
Does the schedule always write on queue or something simmiliar to queue :
what is the next time running ? Is that true ?
If it is done so, then when there is a problem, the schedule stops running
forever, because there is no schedule to write "what is the next time
running".

Is there any way to overcome the problem ?

"Mr. X." <no_spam_please@nospam_please.com> wrote in message
news:uq06Yf7lIHA.1680@TK2MSFTNGP06.phx.gbl...
> Hello.
> I am using windows schedules.
> For some reasons one of the schedule stopped running.
> I was since there was a fix of summer-time (from 12:30am to 1:30am) at the
> same minute the schedule runs (it runs at each minute).
>
> The schedule stopped running and I think it's due the above problem.
> Does the schedule always write on queue or something simmiliar to queue :
> what is the next time running ? Is that true ?
> If it is done so, then when there is a problem, the schedule stops running
> forever, because there is no schedule to write "what is the next time
> running".
>
> Is there any way to overcome the problem ?
>

There is an old known issue with scheduled tasks: If the Windows
system drive resides on a FAT32 partition then all tasks will fail
when moving to or from DST. You have to re-enter the password
for all of them, or better still, convert the partition to NTFS.