home.social

#martypc — Public Fediverse posts

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

fetched live
  1. @nazokiyoubinbou Thanks for that, I'll retry in #MartyPC at some point, however given my HP 200LX blows up at exactly the same point, I think it's the interpreter's fault, not the emulator.

  2. @nazokiyoubinbou Thanks for that, I'll retry in #MartyPC at some point, however given my HP 200LX blows up at exactly the same point, I think it's the interpreter's fault, not the emulator.

  3. The #pasmo assembler has this really neat feature where it'll accept #z80 opcodes and then do its best to emit equivalent #Intel8086 instructions. Effectively, this is the "assembly-level" forward compatibility that Intel advertised for migrating code from 8080 to 8086.

    It certainly isn't perfect - a few instructions are unimplemented and have to be manually fixed, and I'm not sure I've caught all the subtle bugs where flags behave differently ... but, here's Palo Alto TinyBasic running on #MartyPC under DOS, in only a few hours work!

    #retrocomputing #basic #TinyBasic

  4. The #pasmo assembler has this really neat feature where it'll accept #z80 opcodes and then do its best to emit equivalent #Intel8086 instructions. Effectively, this is the "assembly-level" forward compatibility that Intel advertised for migrating code from 8080 to 8086.

    It certainly isn't perfect - a few instructions are unimplemented and have to be manually fixed, and I'm not sure I've caught all the subtle bugs where flags behave differently ... but, here's Palo Alto TinyBasic running on #MartyPC under DOS, in only a few hours work!

    #retrocomputing #basic #TinyBasic

  5. I thought it might be a good idea to reach to the basics trying to debug that #FreePascal bug which makes even simplest programs fail to run on i8086/msdos (my #TP7 game port still “”works””, until it reaches #DOS API calls). So thought it might be possible to target the #8086 and run #MartyPC by @gloriouscow

    While I pretty much know that the code jumps somewhere randomly and then goes along executing emptiness, I still need to find out why…
    and how to set breakpoints on INTs :p

  6. I thought it might be a good idea to reach to the basics trying to debug that #FreePascal bug which makes even simplest programs fail to run on i8086/msdos (my #TP7 game port still “”works””, until it reaches #DOS API calls). So thought it might be possible to target the #8086 and run #MartyPC by @gloriouscow

    While I pretty much know that the code jumps somewhere randomly and then goes along executing emptiness, I still need to find out why…
    and how to set breakpoints on INTs :p