home.social

#f83 — Public Fediverse posts

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

  1. I'm currently checking out options for doing a little coding on a #MSX1 system (real and emulated, when abroad). There's an adapted #F83 #Forth here (github.com/janaite/msx-forth83) but while it's working, it's not optimized for 40 colum mode. And on MSX1 you only have 40 columns.

    Then there's a #BASIC compiler from the former, dutch "#MSX #Club #Gouda" named #Mozart which compiles your MSX BASIC code and gives you some speed improvement - it's here (download.file-hunter.com/Progr).

    And, of course there's #TurboPascal3 for MSX which does support 40 column mode (run TINST.COM to set up screen). It's also here (download.file-hunter.com/Progr)

    Aside from that you could use a C compiler like #SDCC or #BDSC under #MSXDOS1 ...

  2. I'm currently checking out options for doing a little coding on a #MSX1 system (real and emulated, when abroad). There's an adapted #F83 #Forth here (github.com/janaite/msx-forth83) but while it's working, it's not optimized for 40 colum mode. And on MSX1 you only have 40 columns.

    Then there's a #BASIC compiler from the former, dutch "#MSX #Club #Gouda" named #Mozart which compiles your MSX BASIC code and gives you some speed improvement - it's here (download.file-hunter.com/Progr).

    And, of course there's #TurboPascal3 for MSX which does support 40 column mode (run TINST.COM to set up screen). It's also here (download.file-hunter.com/Progr)

    Aside from that you could use a C compiler like #SDCC or #BDSC under #MSXDOS1 ...

  3. I'm currently checking out options for doing a little coding on a #MSX1 system (real and emulated, when abroad). There's an adapted #F83 #Forth here (github.com/janaite/msx-forth83) but while it's working, it's not optimized for 40 colum mode. And on MSX1 you only have 40 columns.

    Then there's a #BASIC compiler from the former, dutch "#MSX #Club #Gouda" named #Mozart which compiles your MSX BASIC code and gives you some speed improvement - it's here (download.file-hunter.com/Progr).

    And, of course there's #TurboPascal3 for MSX which does support 40 column mode (run TINST.COM to set up screen). It's also here (download.file-hunter.com/Progr)

    Aside from that you could use a C compiler like #SDCC or #BDSC under #MSXDOS1 ...

  4. I'm currently checking out options for doing a little coding on a #MSX1 system (real and emulated, when abroad). There's an adapted #F83 #Forth here (github.com/janaite/msx-forth83) but while it's working, it's not optimized for 40 colum mode. And on MSX1 you only have 40 columns.

    Then there's a #BASIC compiler from the former, dutch "#MSX #Club #Gouda" named #Mozart which compiles your MSX BASIC code and gives you some speed improvement - it's here (download.file-hunter.com/Progr).

    And, of course there's #TurboPascal3 for MSX which does support 40 column mode (run TINST.COM to set up screen). It's also here (download.file-hunter.com/Progr)

    Aside from that you could use a C compiler like #SDCC or #BDSC under #MSXDOS1 ...

  5. I'm currently checking out options for doing a little coding on a #MSX1 system (real and emulated, when abroad). There's an adapted #F83 #Forth here (github.com/janaite/msx-forth83) but while it's working, it's not optimized for 40 colum mode. And on MSX1 you only have 40 columns.

    Then there's a #BASIC compiler from the former, dutch "#MSX #Club #Gouda" named #Mozart which compiles your MSX BASIC code and gives you some speed improvement - it's here (download.file-hunter.com/Progr).

    And, of course there's #TurboPascal3 for MSX which does support 40 column mode (run TINST.COM to set up screen). It's also here (download.file-hunter.com/Progr)

    Aside from that you could use a C compiler like #SDCC or #BDSC under #MSXDOS1 ...

  6. I guess I'm a little lost here ...

    so I am currently trying to get the CP/M version of #F83 #Forth by #Laxen and #Perry to do what I want.

    The problem is that I can use BLOCK, UPDATE and SAVE-BUFFERS and any new data written to a block is preserved for the current session. But as soon as I quit Forth and call it up again, using the block file I've just modified, the changes are gone as if they have never been written to disk.

    Any ideas?!

  7. I guess I'm a little lost here ...

    so I am currently trying to get the CP/M version of #F83 #Forth by #Laxen and #Perry to do what I want.

    The problem is that I can use BLOCK, UPDATE and SAVE-BUFFERS and any new data written to a block is preserved for the current session. But as soon as I quit Forth and call it up again, using the block file I've just modified, the changes are gone as if they have never been written to disk.

    Any ideas?!

  8. I guess I'm a little lost here ...

    so I am currently trying to get the CP/M version of #F83 #Forth by #Laxen and #Perry to do what I want.

    The problem is that I can use BLOCK, UPDATE and SAVE-BUFFERS and any new data written to a block is preserved for the current session. But as soon as I quit Forth and call it up again, using the block file I've just modified, the changes are gone as if they have never been written to disk.

    Any ideas?!

  9. I guess I'm a little lost here ...

    so I am currently trying to get the CP/M version of #F83 #Forth by #Laxen and #Perry to do what I want.

    The problem is that I can use BLOCK, UPDATE and SAVE-BUFFERS and any new data written to a block is preserved for the current session. But as soon as I quit Forth and call it up again, using the block file I've just modified, the changes are gone as if they have never been written to disk.

    Any ideas?!

  10. I guess I'm a little lost here ...

    so I am currently trying to get the CP/M version of #F83 #Forth by #Laxen and #Perry to do what I want.

    The problem is that I can use BLOCK, UPDATE and SAVE-BUFFERS and any new data written to a block is preserved for the current session. But as soon as I quit Forth and call it up again, using the block file I've just modified, the changes are gone as if they have never been written to disk.

    Any ideas?!

  11. I'm not proud of this, but I was in a hurry and it works (now the clock cycle police are after me 🚔​ )...

    EDIT: to put the icing on the cake, I re-named it 8RSHIFT ... gotta go ...

    #F83
    #Forth
    #QuickAndDirty
    #AndYouWantItDirty
    #RetroProgramming
    #HowNotToDoIt

  12. I'm not proud of this, but I was in a hurry and it works (now the clock cycle police are after me 🚔​ )...

    EDIT: to put the icing on the cake, I re-named it 8RSHIFT ... gotta go ...

    #F83
    #Forth
    #QuickAndDirty
    #AndYouWantItDirty
    #RetroProgramming
    #HowNotToDoIt

  13. I'm not proud of this, but I was in a hurry and it works (now the clock cycle police are after me 🚔​ )...

    EDIT: to put the icing on the cake, I re-named it 8RSHIFT ... gotta go ...

    #F83
    #Forth
    #QuickAndDirty
    #AndYouWantItDirty
    #RetroProgramming
    #HowNotToDoIt

  14. I'm not proud of this, but I was in a hurry and it works (now the clock cycle police are after me 🚔​ )...

    EDIT: to put the icing on the cake, I re-named it 8RSHIFT ... gotta go ...

    #F83
    #Forth
    #QuickAndDirty
    #AndYouWantItDirty
    #RetroProgramming
    #HowNotToDoIt

  15. I'm not proud of this, but I was in a hurry and it works (now the clock cycle police are after me 🚔​ )...

    EDIT: to put the icing on the cake, I re-named it 8RSHIFT ... gotta go ...

    #F83
    #Forth
    #QuickAndDirty
    #AndYouWantItDirty
    #RetroProgramming
    #HowNotToDoIt

  16. So #gForth has been inspired by #VolksForth which is based on #F83 - is this roughly correct?!

    #Forth

  17. So #gForth has been inspired by #VolksForth which is based on #F83 - is this roughly correct?!

    #Forth

  18. So #gForth has been inspired by #VolksForth which is based on #F83 - is this roughly correct?!

    #Forth

  19. So #gForth has been inspired by #VolksForth which is based on #F83 - is this roughly correct?!

    #Forth

  20. So #gForth has been inspired by #VolksForth which is based on #F83 - is this roughly correct?!

    #Forth

  21. Using #openMSX to prepare a custom 360KB disk image (MSX1 machine with MSX-DOS 1.80) for my #Sony #HitBit machine that will include #ZSM #assembler and #F83 #Forth ...

  22. Using #openMSX to prepare a custom 360KB disk image (MSX1 machine with MSX-DOS 1.80) for my #Sony #HitBit machine that will include #ZSM #assembler and #F83 #Forth ...

  23. Using #openMSX to prepare a custom 360KB disk image (MSX1 machine with MSX-DOS 1.80) for my #Sony #HitBit machine that will include #ZSM #assembler and #F83 #Forth ...

  24. Using #openMSX to prepare a custom 360KB disk image (MSX1 machine with MSX-DOS 1.80) for my #Sony #HitBit machine that will include #ZSM #assembler and #F83 #Forth ...

  25. Using #openMSX to prepare a custom 360KB disk image (MSX1 machine with MSX-DOS 1.80) for my #Sony #HitBit machine that will include #ZSM #assembler and #F83 #Forth ...