10 Nov
2021
10 Nov
'21
6:37 p.m.
It's possible that NML is gronking on a negative number of
milliseconds.? I suggest you try my updated patch and let us know what
happens.
??? At label NMXTIM + 9 lines, (Decimal) change
??????????? IDIVI T3,JIFSEC???????? ;CONVERT TO NUMBER OF MILLISECONDS.
??????????? SKIPL T2??????????????? ;MAKE SURE WE HAVE A POSITIVE
NUMBER OF SECONDS
??????????? TDNE T1,[XWD -1,600000] ;MAKE SURE NO DATE OVERFLOW
???? To:
??????????? IDIVI T3,JIFSEC???????? ;CONVERT TO NUMBER OF MILLISECONDS.
??????????? MOVMS T3??????????????? ;Ensure milliseconds are always
positive ??????????? MOVMS T2??????????????? ;Ensure seconds are always
positive ??????????? TDZA T1,[XWD -1,600000] ;Ensure no Julian half day
overflow
On 11/10/21 10:54 AM, Robert Armstrong wrote:
? ? not date related this time (or at least I don?t think it is)?
? Every time I boot TOPS-10 (7.04, KS10, simh) I get stopcode NTMNEC.?
The job running is NML and the user PC is 511522.? This is a debug
stopcode so the system keeps going.
? The manual says of NTMNEC ? ?Some routine took the? non-skip?
return,? but did not give an error code by calling NTExxx. ?This means
that the program returned? to? top level? and? field? NXERR was zero.?
Determine which routine is failing, and make the? error return give an
error code.?
? Has anybody else seen this?? Is there a patch?? It?s getting a bit
annoying, not to mention that it keeps crash dumping.
Thanks,
Bob