Lazy as I am, I don't usually use the Command Reference.
So when I tried to display the current time, I guessed (badly).
Time>tStart
The characters "Time" were highlighted ocre/red, so I suspected nothing.
When this statement is executed you get "I/O Error 105."
"OK" is you only choice, so you take it.
MSched Control panel shows dialog still running.
Click stop and it appears stopped. (greyed out)
Right-click on Systray only to find that "Break" is still enabled.
Shift-Esc as many times as you want, no joy, systray break still active
Also opening and closing in editor gives ye-olde save error.
Sometimes you get macroname already exists.
Sometimes status bar shows still running the command, sometimes break seems to restart the macro - or re-run that line as the I/O Error message is re-issued.
Only one thing for it ... shutdown MSched and restart.
Now... if it was an invalid command, should be treated as a comment.
Somehow "Time" causes Msched to try something it shouldn't.
Any reason why "Time" should not be a pseudonym for "GetTime" ?
Same goes for Date vs GetDate, BTW
You can have great fun playing with these two "commands"
Time "I/O Error 105" knot.
Moderators: Dorian (MJT support), JRL
-
- Junior Coder
- Posts: 49
- Joined: Fri Oct 15, 2004 8:42 am
- Location: Johannesburg, South Africa
Tim is short for Timestamp so it tried to write to the file/device specified.
MJT Net Support
[email protected]
[email protected]
-
- Junior Coder
- Posts: 49
- Joined: Fri Oct 15, 2004 8:42 am
- Location: Johannesburg, South Africa
Hmmnn ... and DAT for DateStamp.
Any clue as to how you are supposed to recover without bouncing MSched ?
Suggest at minimum a documentation entry to give a clue.
"I/O Error 105 occurs when a write to adevice fails. If you ever receive an I/O Error 105 error, you must stop and restart the Scheduler to clear the condition."
Any clue as to how you are supposed to recover without bouncing MSched ?
Suggest at minimum a documentation entry to give a clue.
"I/O Error 105 occurs when a write to adevice fails. If you ever receive an I/O Error 105 error, you must stop and restart the Scheduler to clear the condition."