home.social

#opensimh — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #opensimh, aggregated by home.social.

  1. TFW think you have an output bug running your #PDP8 PAL code under #OpenSIMH, and then it turns out you just did a `HLT` right after printing the final character, and the emulator had stopped EVERYTHING before the pretend teletype had finished printing.

    ```
    DONE, TSF
    JMP .-1 /WAIT FOR TELETYPE READY
    HLT
    ```

    FIIIINE.

  2. TFW think you have an output bug running your #PDP8 PAL code under #OpenSIMH, and then it turns out you just did a `HLT` right after printing the final character, and the emulator had stopped EVERYTHING before the pretend teletype had finished printing.

    ```
    DONE, TSF
    JMP .-1 /WAIT FOR TELETYPE READY
    HLT
    ```

    FIIIINE.

  3. TFW think you have an output bug running your #PDP8 PAL code under #OpenSIMH, and then it turns out you just did a `HLT` right after printing the final character, and the emulator had stopped EVERYTHING before the pretend teletype had finished printing.

    ```
    DONE, TSF
    JMP .-1 /WAIT FOR TELETYPE READY
    HLT
    ```

    FIIIINE.

  4. TFW think you have an output bug running your #PDP8 PAL code under #OpenSIMH, and then it turns out you just did a `HLT` right after printing the final character, and the emulator had stopped EVERYTHING before the pretend teletype had finished printing.

    ```
    DONE, TSF
    JMP .-1 /WAIT FOR TELETYPE READY
    HLT
    ```

    FIIIINE.

  5. TFW think you have an output bug running your #PDP8 PAL code under #OpenSIMH, and then it turns out you just did a `HLT` right after printing the final character, and the emulator had stopped EVERYTHING before the pretend teletype had finished printing.

    ```
    DONE, TSF
    JMP .-1 /WAIT FOR TELETYPE READY
    HLT
    ```

    FIIIINE.

  6. #pkgsrc has no fewer than three different #simh packages. Lets pick #opensimh, because... it would take too long to explain (I also prefer my drama in non functional code and blinkenlights rather than human interactions)

    With the config from the previous toot in netbsd-10.simh, the ISO in place, and permission and space to create the ra92 files, lets try "simh-vax netbsd-10.simh" and ... a complaint about the networking (oops, we'll come back to that), creating files and attaching and

    /4

  7. #pkgsrc has no fewer than three different #simh packages. Lets pick #opensimh, because... it would take too long to explain (I also prefer my drama in non functional code and blinkenlights rather than human interactions)

    With the config from the previous toot in netbsd-10.simh, the ISO in place, and permission and space to create the ra92 files, lets try "simh-vax netbsd-10.simh" and ... a complaint about the networking (oops, we'll come back to that), creating files and attaching and

    /4

  8. #pkgsrc has no fewer than three different #simh packages. Lets pick #opensimh, because... it would take too long to explain (I also prefer my drama in non functional code and blinkenlights rather than human interactions)

    With the config from the previous toot in netbsd-10.simh, the ISO in place, and permission and space to create the ra92 files, lets try "simh-vax netbsd-10.simh" and ... a complaint about the networking (oops, we'll come back to that), creating files and attaching and

    /4

  9. #pkgsrc has no fewer than three different #simh packages. Lets pick #opensimh, because... it would take too long to explain (I also prefer my drama in non functional code and blinkenlights rather than human interactions)

    With the config from the previous toot in netbsd-10.simh, the ISO in place, and permission and space to create the ra92 files, lets try "simh-vax netbsd-10.simh" and ... a complaint about the networking (oops, we'll come back to that), creating files and attaching and

    /4

  10. #pkgsrc has now fewer than three different #simh packages. Lets pick #opensimh, because... it would take too long to explain (I also prefer my drama in non functional code and blinkenlights rather than human interactions)

    With the previous config in netbsd-10.simh, the ISO in place, and permission and space to create the ra92 files, lets try "simh-vax netbsd-10.simh" and ... a complaint about the networking (oops, we'll come back to that), creating files and attaching and

    /4

  11. Unfortunately, (or fortunately if you consider my living space), I do not have a VAX 11/780, only a VAXstation 4000, and further more I'm not even at said living space, so today we'll be going with a copy of #simh (or rather #opensimh) /2

  12. Unfortunately, (or fortunately if you consider my living space), I do not have a VAX 11/780, only a VAXstation 4000, and further more I'm not even at said living space, so today we'll be going with a copy of #simh (or rather #opensimh) /2

  13. Unfortunately, (or fortunately if you consider my living space), I do not have a VAX 11/780, only a VAXstation 4000, and further more I'm not even at said living space, so today we'll be going with a copy of #simh (or rather #opensimh) /2

  14. Unfortunately, (or fortunately if you consider my living space), I do not have a VAX 11/780, only a VAXstation 4000, and further more I'm not even at said living space, so today we'll be going with a copy of #simh (or rather #opensimh) /2

  15. Unfortunately, (or fortunately if you consider my living space), I do not have a VAX 11/780, only a VAXstation 4000, and further more I'm not even at said living space, so today we'll be going with a copy of #simh (or rather #opensimh) /2

  16. @lore Fast enough to approach 1 VUP in #OpenSimH would be nice.

  17. @lore Fast enough to approach 1 VUP in #OpenSimH would be nice.

  18. @lore Fast enough to approach 1 VUP in #OpenSimH would be nice.

  19. @lore Fast enough to approach 1 VUP in #OpenSimH would be nice.

  20. @lore Fast enough to approach 1 VUP in #OpenSimH would be nice.