> On Oct 30, 2025, at 8:30 PM, Paul Koning via cctalk <[email protected]> 
> wrote:
> 
> 
> 
>> On Oct 30, 2025, at 7:43 PM, Glen Slick via cctalk <[email protected]> 
>> wrote:
>> 
>> On Thu, Oct 30, 2025, 4:38 PM Peter Ekstrom via cctalk <
>> [email protected]> wrote:
>> 
>> ...
>> Just a wild guess, could this possibly be an unhandled LTC interrupt issue?
> 
> Yes that seems likely.
> 
> The problem is the "go" command.  That isn't like "start" on a real machine; 
> it just sets the PC and continues.  To get the effect of the "start" switch, 
> do "reset" then "go".
> 
> paul

More: "reset" should reset all devices.  I don't remember the 11/23 well 
enough; it seems that it has a clock that keeps interrupting even if you do a 
reset.  So raise the priority to 7 (mov #340, @#177776 which is 12737, 340, 
177776).  Or use the deposit command before you do the "go": "d psw 340".

Most machines have clocks that do obey reset, for example "reset" then "go" 
will work correctly if your CPU type is 11/73.

        paul

Reply via email to