home.social

#mz80k — Public Fediverse posts

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

fetched live
  1. #today visited the ARC@KU arcatku.org/event/arc-annual-s #retrogaming #retrocomputing exhibition with many working #Z80 #6502 #68000 etc machines, including the #BBCMicro and #Spectrum48k I had, though not the #MZ80K. Also an #Atari2600 that my brother and I had nearly 50Y ago!

  2. #today visited the ARC@KU arcatku.org/event/arc-annual-s #retrogaming #retrocomputing exhibition with many working #Z80 #6502 #68000 etc machines, including the #BBCMicro and #Spectrum48k I had, though not the #MZ80K. Also an #Atari2600 that my brother and I had nearly 50Y ago!

  3. #today visited the ARC@KU arcatku.org/event/arc-annual-s #retrogaming #retrocomputing exhibition with many working #Z80 #6502 #68000 etc machines, including the #BBCMicro and #Spectrum48k I had, though not the #MZ80K. Also an #Atari2600 that my brother and I had nearly 50Y ago!

  4. #today visited the ARC@KU arcatku.org/event/arc-annual-s #retrogaming #retrocomputing exhibition with many working #Z80 #6502 #68000 etc machines, including the #BBCMicro and #Spectrum48k I had, though not the #MZ80K. Also an #Atari2600 that my brother and I had nearly 50Y ago!

  5. #today visited the ARC@KU arcatku.org/event/arc-annual-s #retrogaming #retrocomputing exhibition with many working #Z80 #6502 #68000 etc machines, including the #BBCMicro and #Spectrum48k I had, though not the #MZ80K. Also an #Atari2600 that my brother and I had nearly 50Y ago!

  6. My rewrite of the 8255 emulation seems to have fixed the keyboard handling weirdness and cursor blink speed issues on the #MZ700 emulation. It also seems to have sorted the odd glitch I knew I still had with #MZ80K keyboard handling. The new emulation is more efficient, so I may be able to drop the Pico clock speed another 10MHz or so ...

  7. My rewrite of the 8255 emulation seems to have fixed the keyboard handling weirdness and cursor blink speed issues on the #MZ700 emulation. It also seems to have sorted the odd glitch I knew I still had with #MZ80K keyboard handling. The new emulation is more efficient, so I may be able to drop the Pico clock speed another 10MHz or so ...

  8. My rewrite of the 8255 emulation seems to have fixed the keyboard handling weirdness and cursor blink speed issues on the #MZ700 emulation. It also seems to have sorted the odd glitch I knew I still had with #MZ80K keyboard handling. The new emulation is more efficient, so I may be able to drop the Pico clock speed another 10MHz or so ...

  9. My rewrite of the 8255 emulation seems to have fixed the keyboard handling weirdness and cursor blink speed issues on the #MZ700 emulation. It also seems to have sorted the odd glitch I knew I still had with #MZ80K keyboard handling. The new emulation is more efficient, so I may be able to drop the Pico clock speed another 10MHz or so ...

  10. My rewrite of the 8255 emulation seems to have fixed the keyboard handling weirdness and cursor blink speed issues on the #MZ700 emulation. It also seems to have sorted the odd glitch I knew I still had with #MZ80K keyboard handling. The new emulation is more efficient, so I may be able to drop the Pico clock speed another 10MHz or so ...

  11. I'm not able to take part in #RetroChallenge this year, but I've just spent a few minutes enjoying last year's writeup of my #Sharp #MZ80K emulator for the #RaspberryPiPico . In the weeks after the challenge it went on to emulate the #MZ80A as well. The plan for this winter is to have a bash at #MZ700 emulation. The architecture isn't hugely different from the earlier MZs, but I'll need to implement colour output as a minimum.

    z80.timholyoake.uk/retrochalle

  12. I'm not able to take part in #RetroChallenge this year, but I've just spent a few minutes enjoying last year's writeup of my #Sharp #MZ80K emulator for the #RaspberryPiPico . In the weeks after the challenge it went on to emulate the #MZ80A as well. The plan for this winter is to have a bash at #MZ700 emulation. The architecture isn't hugely different from the earlier MZs, but I'll need to implement colour output as a minimum.

    z80.timholyoake.uk/retrochalle

  13. I'm not able to take part in #RetroChallenge this year, but I've just spent a few minutes enjoying last year's writeup of my #Sharp #MZ80K emulator for the #RaspberryPiPico . In the weeks after the challenge it went on to emulate the #MZ80A as well. The plan for this winter is to have a bash at #MZ700 emulation. The architecture isn't hugely different from the earlier MZs, but I'll need to implement colour output as a minimum.

    z80.timholyoake.uk/retrochalle

  14. I'm not able to take part in #RetroChallenge this year, but I've just spent a few minutes enjoying last year's writeup of my #Sharp #MZ80K emulator for the #RaspberryPiPico . In the weeks after the challenge it went on to emulate the #MZ80A as well. The plan for this winter is to have a bash at #MZ700 emulation. The architecture isn't hugely different from the earlier MZs, but I'll need to implement colour output as a minimum.

    z80.timholyoake.uk/retrochalle

  15. I'm not able to take part in #RetroChallenge this year, but I've just spent a few minutes enjoying last year's writeup of my #Sharp #MZ80K emulator for the #RaspberryPiPico . In the weeks after the challenge it went on to emulate the #MZ80A as well. The plan for this winter is to have a bash at #MZ700 emulation. The architecture isn't hugely different from the earlier MZs, but I'll need to implement colour output as a minimum.

    z80.timholyoake.uk/retrochalle

  16. One of the most repair-friendly computers of the 80s. Our #Sharp #MZ80K in the museum. But ultimately, it was also one of the dumbest computers ever launched.
    #RetroComputing #ComputerMuseum

  17. One of the most repair-friendly computers of the 80s. Our #Sharp #MZ80K in the museum. But ultimately, it was also one of the dumbest computers ever launched.
    #RetroComputing #ComputerMuseum

  18. One of the most repair-friendly computers of the 80s. Our #Sharp #MZ80K in the museum. But ultimately, it was also one of the dumbest computers ever launched.
    #RetroComputing #ComputerMuseum

  19. One of the most repair-friendly computers of the 80s. Our #Sharp #MZ80K in the museum. But ultimately, it was also one of the dumbest computers ever launched.
    #RetroComputing #ComputerMuseum

  20. One of the most repair-friendly computers of the 80s. Our #Sharp #MZ80K in the museum. But ultimately, it was also one of the dumbest computers ever launched.
    #RetroComputing #ComputerMuseum

  21. Look what the postie brought! I've been looking for a copy of this for years 😊

    #RetroComputing #Sharp #MZ80K #Z80

  22. Look what the postie brought! I've been looking for a copy of this for years 😊

    #RetroComputing #Sharp #MZ80K #Z80

  23. Look what the postie brought! I've been looking for a copy of this for years 😊

    #RetroComputing #Sharp #MZ80K #Z80

  24. Look what the postie brought! I've been looking for a copy of this for years 😊

    #RetroComputing #Sharp #MZ80K #Z80

  25. Look what the postie brought! I've been looking for a copy of this for years 😊

    #RetroComputing #Sharp #MZ80K #Z80

  26. That's better! (Sorry @rc2014 ... your wish is not granted!!)

    #RetroComputing #MZ80A #MZ80K

    ... this reminds me of having to fix a display driver in the PAFEC DOGS CAD software when I'd ported it to the IBM 6150 (PC/RT for any Americans reading) (the RS/6000's ancestor).

    On the IBM megapel display, I was getting strange corruption as it was interpreting some escape sequences incorrectly. I think IBM fixed the firmware in the end, but the workaround was never taken out of our code, "just in case". It scored me a trip to IBM in Innsbruck as that was the nearest office they had with the offending graphics display available at the time - it must've been very early 6150 days.

    I've attached a picture of the cowbell IBM Innsbruck gave me for installing the workaround!

  27. That's better! (Sorry @rc2014 ... your wish is not granted!!)

    #RetroComputing #MZ80A #MZ80K

    ... this reminds me of having to fix a display driver in the PAFEC DOGS CAD software when I'd ported it to the IBM 6150 (PC/RT for any Americans reading) (the RS/6000's ancestor).

    On the IBM megapel display, I was getting strange corruption as it was interpreting some escape sequences incorrectly. I think IBM fixed the firmware in the end, but the workaround was never taken out of our code, "just in case". It scored me a trip to IBM in Innsbruck as that was the nearest office they had with the offending graphics display available at the time - it must've been very early 6150 days.

    I've attached a picture of the cowbell IBM Innsbruck gave me for installing the workaround!

  28. That's better! (Sorry @rc2014 ... your wish is not granted!!)

    #RetroComputing #MZ80A #MZ80K

    ... this reminds me of having to fix a display driver in the PAFEC DOGS CAD software when I'd ported it to the IBM 6150 (PC/RT for any Americans reading) (the RS/6000's ancestor).

    On the IBM megapel display, I was getting strange corruption as it was interpreting some escape sequences incorrectly. I think IBM fixed the firmware in the end, but the workaround was never taken out of our code, "just in case". It scored me a trip to IBM in Innsbruck as that was the nearest office they had with the offending graphics display available at the time - it must've been very early 6150 days.

    I've attached a picture of the cowbell IBM Innsbruck gave me for installing the workaround!

  29. That's better! (Sorry @rc2014 ... your wish is not granted!!)

    #RetroComputing #MZ80A #MZ80K

    ... this reminds me of having to fix a display driver in the PAFEC DOGS CAD software when I'd ported it to the IBM 6150 (PC/RT for any Americans reading) (the RS/6000's ancestor).

    On the IBM megapel display, I was getting strange corruption as it was interpreting some escape sequences incorrectly. I think IBM fixed the firmware in the end, but the workaround was never taken out of our code, "just in case". It scored me a trip to IBM in Innsbruck as that was the nearest office they had with the offending graphics display available at the time - it must've been very early 6150 days.

    I've attached a picture of the cowbell IBM Innsbruck gave me for installing the workaround!

  30. That's better! (Sorry @rc2014 ... your wish is not granted!!)

    #RetroComputing #MZ80A #MZ80K

    ... this reminds me of having to fix a display driver in the PAFEC DOGS CAD software when I'd ported it to the IBM 6150 (PC/RT for any Americans reading) (the RS/6000's ancestor).

    On the IBM megapel display, I was getting strange corruption as it was interpreting some escape sequences incorrectly. I think IBM fixed the firmware in the end, but the workaround was never taken out of our code, "just in case". It scored me a trip to IBM in Innsbruck as that was the nearest office they had with the offending graphics display available at the time - it must've been very early 6150 days.

    I've attached a picture of the cowbell IBM Innsbruck gave me for installing the workaround!

  31. Just looking at how straightforward it would be to extend the Pico MZ-80K to emulate the MZ-80A as well.

    Shouldn't be too difficult, and it could potentially run CP/M.

    I've a feeling I'm just about to fall down a rabbit hole that I swore I wouldn't ...

    #RetroComputing #Sharp #MZ80A #MZ80K #PicoMZ80K

  32. Just looking at how straightforward it would be to extend the Pico MZ-80K to emulate the MZ-80A as well.

    Shouldn't be too difficult, and it could potentially run CP/M.

    I've a feeling I'm just about to fall down a rabbit hole that I swore I wouldn't ...

    #RetroComputing #Sharp #MZ80A #MZ80K #PicoMZ80K

  33. Just looking at how straightforward it would be to extend the Pico MZ-80K to emulate the MZ-80A as well.

    Shouldn't be too difficult, and it could potentially run CP/M.

    I've a feeling I'm just about to fall down a rabbit hole that I swore I wouldn't ...

    #RetroComputing #Sharp #MZ80A #MZ80K #PicoMZ80K

  34. Just looking at how straightforward it would be to extend the Pico MZ-80K to emulate the MZ-80A as well.

    Shouldn't be too difficult, and it could potentially run CP/M.

    I've a feeling I'm just about to fall down a rabbit hole that I swore I wouldn't ...

    #RetroComputing #Sharp #MZ80A #MZ80K #PicoMZ80K

  35. Just looking at how straightforward it would be to extend the Pico MZ-80K to emulate the MZ-80A as well.

    Shouldn't be too difficult, and it could potentially run CP/M.

    I've a feeling I'm just about to fall down a rabbit hole that I swore I wouldn't ...

    #RetroComputing #Sharp #MZ80A #MZ80K #PicoMZ80K

  36. Newly minted - Pico #MZ80K release 1.2.4 - bugfixes and initial support for the Japanese character ROM.

    Runs on a #RaspberryPi Pico mounted on a Pimoroni VGA Demo Base, #RC2014 Pi Pico VGA terminal card or on the self-contained RC2014 RP2040 VGA terminal card.

    More details:

    z80.timholyoake.uk/the-pico-mz

    #RetroComputing #Sharp

  37. Newly minted - Pico #MZ80K release 1.2.4 - bugfixes and initial support for the Japanese character ROM.

    Runs on a #RaspberryPi Pico mounted on a Pimoroni VGA Demo Base, #RC2014 Pi Pico VGA terminal card or on the self-contained RC2014 RP2040 VGA terminal card.

    More details:

    z80.timholyoake.uk/the-pico-mz

    #RetroComputing #Sharp

  38. Newly minted - Pico #MZ80K release 1.2.4 - bugfixes and initial support for the Japanese character ROM.

    Runs on a #RaspberryPi Pico mounted on a Pimoroni VGA Demo Base, #RC2014 Pi Pico VGA terminal card or on the self-contained RC2014 RP2040 VGA terminal card.

    More details:

    z80.timholyoake.uk/the-pico-mz

    #RetroComputing #Sharp

  39. Newly minted - Pico #MZ80K release 1.2.4 - bugfixes and initial support for the Japanese character ROM.

    Runs on a #RaspberryPi Pico mounted on a Pimoroni VGA Demo Base, #RC2014 Pi Pico VGA terminal card or on the self-contained RC2014 RP2040 VGA terminal card.

    More details:

    z80.timholyoake.uk/the-pico-mz

    #RetroComputing #Sharp

  40. Newly minted - Pico #MZ80K release 1.2.4 - bugfixes and initial support for the Japanese character ROM.

    Runs on a #RaspberryPi Pico mounted on a Pimoroni VGA Demo Base, #RC2014 Pi Pico VGA terminal card or on the self-contained RC2014 RP2040 VGA terminal card.

    More details:

    z80.timholyoake.uk/the-pico-mz

    #RetroComputing #Sharp

  41. @metin Since you seem interested in graphics, had basically none; single line of 24? chars, until someone found a way to derail BASIC interpreter and access the first columns of pixels.
    You could access pixels natively on , but again display was small. 4 colors plotter was amazing.
    had an interesting font with symbols
    could display 40 or 80 columns text and 2 switchable graphic pages, all ORed together. Could be used for page flipping, etc.

  42. @metin First personal computer I touched in 1980 was a #Micral, thanks to a high school professor that gave me access to one
    en.wikipedia.org/wiki/Micral
    Then I had several #Sharp computers, a #pc1211 that my father bought, then temporary access to a #pc1500 (with plotter!), #mz80k and #mz80b, thanks to a Sharp reseller (Mr #Laussucq, in #Dax).
    Got my first #ibmpc #Thomson clone in 1983 or 1984.

  43. @metin First personal computer I touched in 1980 was a (80-20?), thanks to a high school professor that gave me access to one
    en.wikipedia.org/wiki/Micral
    Then I had several computers, a that my father bought, then temporary access to a (with small plotter!), and , thanks to a Sharp reseller (Mr , in ).
    Got my first clone in 1983 or 1984.

  44. @metin First personal computer I touched in 1980 was a #Micral, thanks to a high school professor that gave me access to one
    en.wikipedia.org/wiki/Micral
    Then I had several #Sharp computers, a #pc1211 that my father bought, then temporary access to a #pc1500 (with plotter!), #mz80k and #mz80b, thanks to a Sharp reseller (Mr #Laussucq, in #Dax).
    Got my first #ibmpc #Thomson clone in 1983 or 1984.

  45. @metin First personal computer I touched in 1980 was a #Micral, thanks to a high school professor that gave me access to one
    en.wikipedia.org/wiki/Micral
    Then I had several #Sharp computers, a #pc1211 that my father bought, then temporary access to a #pc1500 (with plotter!), #mz80k and #mz80b, thanks to a Sharp reseller (Mr #Laussucq, in #Dax).
    Got my first #ibmpc #Thomson clone in 1983 or 1984.