Lingolol

1 post1 participant0 posts today

Nils M HolmA few weeks ago I wondered what it takes to turn a small LISP-1 into a LISP-2. Turns out it takes just a few hours to get most things right, then some days to iron out a few subtleties, and then a couple of weeks to polish it into a piece of art. MICRO COMMON LISP is a tiny, purely symbolic, microscopic subset of <a href="https://mastodon.social/tags/CommonLISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonLISP</a>. It runs in less than 64K bytes of memory, even on <a href="https://mastodon.social/tags/DOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DOS</a> (tiny model) or CP/M. Here it is: <a href="http://t3x.org/mcl/" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://t3x.org/mcl/</a> <a href="https://mastodon.social/tags/CPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM</a> <a href="https://mastodon.social/tags/LISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LISP</a>

Nils M HolmThe Mini <a href="https://mastodon.social/tags/CommonLISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CommonLISP</a> I have been working on now runs on CP/M with 2416 free cons cells. Enough to load Ken Kahn's tiny PROLOG and run a few simple queries. The <a href="https://mastodon.social/tags/AgonLight" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AgonLight</a> (18MHz eZ80) loads the LISP part of the code (236 lines) in 11 seconds. Simple programs run at acceptable speed, but slightly more complex PROLOG queries take *minutes*. :) <a href="https://mastodon.social/tags/LISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LISP</a> <a href="https://mastodon.social/tags/CPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM</a> <a href="https://mastodon.social/tags/PROLOG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#PROLOG</a> <a href="https://mastodon.social/tags/Z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Z80</a>

@Rp12Biker :verified:The little <a href="https://oldbytes.space/tags/CPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM</a> <a href="https://oldbytes.space/tags/workstation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#workstation</a> is finished. My evening work consisted of packing it in a nice case and starting the backplane soldering. But there are still plenty of soldering points left, I'll have to do that tomorrow as well.Do any of you <a href="https://oldbytes.space/tags/Pascal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Pascal</a> nerds knows a source for porting <a href="https://oldbytes.space/tags/Eliza" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Eliza</a> to <a href="https://oldbytes.space/tags/TurboPascal3" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TurboPascal3</a>, the first good Turing test in <a href="https://oldbytes.space/tags/BASIC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#BASIC</a>? <a href="https://oldbytes.space/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RetroComputing</a> <a href="https://oldbytes.space/tags/ZilogZ180" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ZilogZ180</a> <a href="https://oldbytes.space/tags/SC126" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SC126</a>

Paolo Amoroso☝️ <a href="https://oldbytes.space/@bitsavers" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@bitsavers</a> has just posted yet another computing history treasure: the scans of the original Digital Research listings of the sources of CP/M 2.2, CP/M Plus 3.0, CP/M-86, and Concurrent CP/M-86 in Intel 8080 Assembly, PL/M, and Intel 8086 Assembly.<a href="http://www.bitsavers.org/pdf/digitalResearch/CPM_Listings/" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://www.bitsavers.org/pdf/digitalResearch/CPM_Listings/</a><a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://oldbytes.space/tags/intel8080" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#intel8080</a> <a href="https://oldbytes.space/tags/x86" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#x86</a>

SciPost PhysicsNew <a href="https://scipost.social/tags/openaccess" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openaccess</a> publication <a href="https://scipost.social/tags/SciPost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SciPost</a> <a href="https://scipost.social/tags/Physics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Physics</a>Higher spin swampland conjecture for massive AdS3 gravityRajae Sammani, El Hassan Saidi SciPost Phys. 18, 173 (2025) <a href="https://scipost.org/SciPostPhys.18.6.173" rel="nofollow noopener noreferrer" target="_blank">https://scipost.org/SciPostPhys.18.6.173</a><a href="https://scipost.social/tags/UM5" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UM5</a> <a href="https://scipost.social/tags/CPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM</a>

SaustrupMy brand new <a href="https://mstdn.dk/tags/mfmemulator" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mfmemulator</a> from <a href="https://decromancer.ca/mfm-emulator/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://decromancer.ca/mfm-emulator/</a> arrived from <a href="https://mstdn.dk/tags/Canada" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Canada</a> about a week ago. It doubles as an MFM harddisk reader as well as an emulator, and I just happened to have a 40 year old disk lying around.<a href="https://mstdn.dk/tags/MFM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MFM</a> was a weird standard, at least compared to SCSI and IDE. It's much closer to that of a floppy drive, than the hard disks we use today. That becomes apparent, when you realize that there are a lot of different standards for putting data on an MFM disks, and I'm just talking ones and zeroes here, not high level data like file systems. Basically, one model MFM controller probably won't read the data that another wrote on the same disk.With that in mind, I was a little worried that the emulator wouldn't read my <a href="https://mstdn.dk/tags/CPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM</a> disk that was previously connected to an old Adaptec SCSI-to-MFM controller. To my surprise it worked like a charm, and I'm now looking at <a href="https://mstdn.dk/tags/pascal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pascal</a> source code my dad wrote in the mid <a href="https://mstdn.dk/tags/80s" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#80s</a>. I'd call that a success! 🙂

Paolo AmorosoCP/M-86 for Newbies is a starter kit for CP/M-86 with everything ready to unpack and run. It bundles the PCe PC emulator (Windows only), preconfigured PCe environments for running different CP/M-86 versions including Concurrent CP/M-86 and Concurrent DOS, and other software such as the Pirx Commander file manager.<a href="https://github.com/MarekStarobrat/Pirx.Commander/tree/main/Releases/CPM-86" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/MarekStarobrat/Pirx.Commander/tree/main/Releases/CPM-86</a><a href="https://fosstodon.org/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://fosstodon.org/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a>

Peter MountWow, I didn't realise that LibreOffice turns 40 this year with it's latest release.It started out as closed source Star Writer for CP/M in 1985 with DOS 3.2support in 1986.Then became Star Office in 1994 for Windows 3.1It became open source as Open office in 2001 and the LibreOffice fork in 2010.<a href="https://en.wikipedia.org/wiki/StarOffice" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/StarOffice</a><a href="https://en.wikipedia.org/wiki/OpenOffice.org" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/OpenOffice.org</a><a href="https://en.wikipedia.org/wiki/LibreOffice" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://en.wikipedia.org/wiki/LibreOffice</a><a href="https://area51.social/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://area51.social/tags/msdos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#msdos</a> <a href="https://area51.social/tags/dos" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dos</a> <a href="https://area51.social/tags/libreOffice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#libreOffice</a> <a href="https://area51.social/tags/openOffice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openOffice</a> <a href="https://area51.social/tags/starOffice" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#starOffice</a> <a href="https://area51.social/tags/retroComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retroComputing</a>

Shawn SijnstraAfter much testing and code comparison, the new Feb 2025 Release of <a href="https://hachyderm.io/tags/Vezza" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vezza</a> - my <a href="https://hachyderm.io/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> high speed <a href="https://hachyderm.io/tags/zmachine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#zmachine</a> is ready! Took way longer than expected to synchronize across all of the code bases, particularly making sure that all optimizations made it across all platforms - TRS-80 model 1, TRS-80 model 3, TRS-80 model 4, the CP/M versions (~18 platforms), the embedded versions (Spectrum tape, TEC-1G), and slowly pushing into the Agon Light version (which has even more updates still in progress). Lots of individual tweaks, and some major rethinks and rewrites have come together to accelerate game play.The hardest part of rewriting in this update involved rewriting the dictionary search code. I ended up going back to the original jzip interpreter, written in C for Unix waaay back when. Jzip provided much of the logic that went into ZXZVM, which provided the base for <a href="https://hachyderm.io/tags/M4ZVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#M4ZVM</a> <a href="https://hachyderm.io/tags/M3ZVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#M3ZVM</a> and <a href="https://hachyderm.io/tags/Vezza" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vezza</a>. Going back to Jzip made sense as Jzip has an even longer history; and is highly tested and stable and still maintained. This research gave me the confidence that the streamlining and changes I was making to such a fundamental part of the game would work, making all inputted dictionary searching more efficient.To work around how CP/M stores executable files I spent a lot of time re-organising the memory map to make the executable smaller. This involved rearranging where the initialization code was stored inside the increasingly complex layout. Support across multiple versions means I needed to break up variable sized code and strings to sit inside variable sized gaps, while still compiling all the CP/M versions from the same interconnected set of source files. It needed quite a few manual checks to ensure that it all worked.What this all means is that your favourite <a href="https://hachyderm.io/tags/infocom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infocom</a> <a href="https://hachyderm.io/tags/punyinform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#punyinform</a> and other text adventures will all play on your favourite z80 <a href="https://hachyderm.io/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> platforms even faster than before!More details in the devlog and downloads can be found at: <a href="https://hachyderm.io/tags/TRS80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TRS80</a> versions <a href="https://sijnstra.itch.io/m4zvm" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sijnstra.itch.io/m4zvm</a> <a href="https://hachyderm.io/tags/CPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM</a> <a href="https://hachyderm.io/tags/CPM80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM80</a> versions <a href="https://sijnstra.itch.io/vezza" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://sijnstra.itch.io/vezza</a>

SaustrupAs promised: a complete deep clean of the late <a href="https://mstdn.dk/tags/70s" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#70s</a> <a href="https://mstdn.dk/tags/GeminiMicrocomputers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GeminiMicrocomputers</a> parallel <a href="https://mstdn.dk/tags/keyboard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#keyboard</a> by <a href="https://mstdn.dk/tags/Rotec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Rotec</a>. Everything disassembled, cleaned, lubed, rubber liners treated with silicone and brand new rubber feet installed. All keys are working, but some don't sit as well in their sockets as they used, so I expect the keys to stay in place if I hit someone with it! :D Also some electrical issues with scanning of the key matrix being incredibly slow - but it lives!! 🙂And yeah, the "DISASSEMBLE FROM PCB SIDE" sticker was added by me. Taking this apart the wrong way will end in disaster. Learned that the hard way. No spiders were hurt in this cleaning, although they had clearly taken up residency at some point.<a href="https://mstdn.dk/tags/vintagecomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vintagecomputing</a> <a href="https://mstdn.dk/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://mstdn.dk/tags/keyboards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#keyboards</a>

Ian NeillClimbing out of the CPM/Zork rabbit hole for now...I have fixed and reformatted the Z80 Z-Code Interpreter source, and successfully assembled it for RunCPM... And it works.Going to play the game for a while, and then get back into my Kim-1 rabbit hole.Anyway, all my CPM/Zork efforts are here:<a href="https://github.com/ilneill/MyInfocom" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/ilneill/MyInfocom</a>Enjoy!<a href="https://mastodon.ie/tags/CPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM</a> <a href="https://mastodon.ie/tags/RunCPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RunCPM</a> <a href="https://mastodon.ie/tags/Z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Z80</a> <a href="https://mastodon.ie/tags/Zork" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Zork</a> <a href="https://mastodon.ie/tags/Infocom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Infocom</a>

Ian NeillHaving a break from other "rabbit holes" to return to <a href="https://mastodon.ie/tags/CPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM</a>, and I'm away from my hardware, so it's emulation only.Got <a href="https://mastodon.ie/tags/runCPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#runCPM</a> up my laptop and had to get <a href="https://mastodon.ie/tags/Zork" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Zork</a> running. Found the eblong Infocom archive and the <a href="https://mastodon.ie/tags/Z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Z80</a> the Z Interpretator source (+ Zork Z3 file).Fixed some issues and it assembled with <a href="https://mastodon.ie/tags/z80asm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80asm</a> but when I ran it the text display was not right. I recognised escape code issues. Dug into the Z80 code and found the problem. Hours later I found the reason.Wyse codes, not VT100/ANSI 😉

Wintermute_BBSFor those of you who are interested in my latest project, <a href="https://oldbytes.space/tags/dxbbs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dxbbs</a> you may like to know that I've done some code cleanup, renamed existing variables and introduced new ones, especially for the message base files. this is in preparation of handling multiple message bases.I've also implemented "message flagging/unflagging" in combination with the msg_purge routine. The latter takes some time to process all messages since it actually creates a re-indexd copy of all files for the selected message base. So I thought it would make sense to "flag" messages for deletion, effectively excluding these from being listed or read and then have the option to physically delete them and re-arrange the message file during a maintenance window, where there is enough planned downtime for such an action.Let me note that the code is by no means an example for proper <a href="https://oldbytes.space/tags/forth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#forth</a> programming. I'm not there yet, but in case you are interested, here's the link:<a href="https://gitlab.com/ufud-org/rc2014-dxforth/-/tree/main/bbs?ref_type=heads" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gitlab.com/ufud-org/rc2014-dxforth/-/tree/main/bbs?ref_type=heads</a><a href="https://oldbytes.space/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> <a href="https://oldbytes.space/tags/bbs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bbs</a> <a href="https://oldbytes.space/tags/rc2014" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rc2014</a> <a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://oldbytes.space/tags/dxforth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dxforth</a> <a href="https://oldbytes.space/tags/retrocoding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocoding</a>

Extreme Kits ЖWe have a few of these in stock now, more coming soon. <a href="https://mstdn.social/tags/RomWBW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RomWBW</a> <a href="https://mstdn.social/tags/z80" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#z80</a> <a href="https://mstdn.social/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> emulated on a Pi Pico. <a href="https://extkits.co.uk/product/pico-romwbw/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://extkits.co.uk/product/pico-romwbw/</a><a href="https://mstdn.social/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RetroComputing</a>

Wintermute_BBSwhoa, this has been a productive coding run tonight. must be the "Garlic Funk" strain, real good one - nice aroma, quite inspiring yet not too hard on the brain.so, writing byte-accurate data and a corrsponding index file work technically ( a little tuning is still required ). nice.next on the list is the other way around, reading the data that is now being written correctly.I can't say it often enough, but coding <a href="https://oldbytes.space/tags/Forth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Forth</a> really fits my way of thinking. Who would've thought?!<a href="https://oldbytes.space/tags/fourtwentytime" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fourtwentytime</a> <a href="https://oldbytes.space/tags/retrocoding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocoding</a> <a href="https://oldbytes.space/tags/bbs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bbs</a> <a href="https://oldbytes.space/tags/rc2014" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rc2014</a> <a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a>

Blake PattersonThe Secret Father of Modern Computing: How Ed Roberts created the personal computer industry—and then walked away<a href="https://every.to/the-crazy-ones/the-secret-father-of-modern-computing" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://every.to/the-crazy-ones/the-secret-father-of-modern-computing</a><a href="https://oldbytes.space/tags/Altair" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Altair</a> <a href="https://oldbytes.space/tags/computinghistory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#computinghistory</a> <a href="https://oldbytes.space/tags/computers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#computers</a> <a href="https://oldbytes.space/tags/vintagecomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vintagecomputing</a> <a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://oldbytes.space/tags/retrocomputers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputers</a> <a href="https://oldbytes.space/tags/vintagecomputers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vintagecomputers</a> <a href="https://oldbytes.space/tags/S100" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#S100</a> <a href="https://oldbytes.space/tags/CPM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CPM</a> #8080 <a href="https://oldbytes.space/tags/IMSAI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IMSAI</a> <a href="https://oldbytes.space/tags/EdRoberts" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#EdRoberts</a> <a href="https://oldbytes.space/tags/ACM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ACM</a>

Erik 📻🪐🚲Rate my setup <a href="https://mastodon.radio/tags/clockworkpi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#clockworkpi</a> <a href="https://mastodon.radio/tags/rc2014" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rc2014</a> <a href="https://mastodon.radio/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://mastodon.radio/tags/uConsole" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#uConsole</a> <a href="https://mastodon.radio/tags/Z180" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Z180</a>

erazmus 🇨🇦It even comes with a copy of the Technical Manual! <a href="https://mastodon.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://mastodon.social/tags/retro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retro</a> <a href="https://mastodon.social/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://mastodon.social/tags/8bit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#8bit</a> <a href="https://mastodon.social/tags/northstar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#northstar</a>

erazmus 🇨🇦Just acquired a beautiful Northstar Advantage. The keyboard mostly works, but I'll still do a foam-and-foil replacement on it. The 15Mb hard drive is full of software, and it came with 4 boxes of disks, manuals, and a dot-matrix printer (not shown). This will keep me busy for the winter, and will make an excellent companion to my Northstar Horizons :) <a href="https://mastodon.social/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a> <a href="https://mastodon.social/tags/northstar" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#northstar</a> <a href="https://mastodon.social/tags/8bit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#8bit</a> <a href="https://mastodon.social/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://mastodon.social/tags/retro" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retro</a>

Walrus 🏴󠁧󠁢󠁷󠁬󠁳󠁿Once upon a time, I had a Nascom 1. But this is my Nascom 2, before I added an amber monitor. It must have been late 1980s...<a href="https://toot.wales/tags/computers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#computers</a> <a href="https://toot.wales/tags/nascom" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nascom</a> <a href="https://toot.wales/tags/cpm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cpm</a> <a href="https://toot.wales/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#retrocomputing</a>

Recent searches

Search options

Administered by:

Server stats:

#cpm