- vcf-midatlantic - lists.vcfed.org

who was first ...
by Jeffrey Jonas 02 Jan '26

02 Jan '26

An interesting article: https://computerhistory.org/blog/the-neverending-quest-for-firsts/ links to https://computerhistory.org/blog/programming-the-eniac-an-example-of-why-co… Visitors to the Computer History Museum frequently want to know: what was the first computer? The first personal computer? In his recent post, “Programming the ENIAC: An Example of Why Computer History is Hard <https://computerhistory.org/blog/programming-the-eniac-an-example-of-why-co…>,” Computer History Museum Board Chair Len Shustek notes that one of the difficulties of computer history, and indeed, history of technology in general, is the question of “firsts”: what was the “first” X, or in alternate form, “who [first] invented X?” The problem is that for many of these “firsts,” there is no simple answer, because as Len pointed out, “What ‘first’ means depends on precise definitions of fuzzy concepts.” What seem to be questions with easy, factual answers quickly devolve into debates over semantics ...

3 2

MARCH Workshop - JAN 10-11, 2026
by Jeff Salzman 02 Jan '26

02 Jan '26

Coming up in a little over a week, the first MARCH Workshop of 2026. Signup sheet is here: https://docs.google.com/spreadsheets/d/1wZfxlcyORhpSiPJso0Qc-MMWypN_m6muR7O… General Workshop details can be found here: Repair Workshops @ InfoAge – Vintage Computer Federation <https://vcfed.org/repair-workshops-at-infoage/> Note that the new location on the InfoAge campus for the Workshops is in Building 9010D, and details on that building location are on the Workshop details page above. See you there! Jeff Salzman VCF-MidAtlantic Steering Committee MARCH Workshop Manager

1 0

Re: [vcf-midatlantic] AI Computer Museum Docent - BETA - DEMO
by Ralph Broom 02 Jan '26

02 Jan '26

Bob, impressive beta! I talked with it about a few things I know pretty well and have had to explain to others. I noticed it sometimes reads the markdown literally ("hash"). Other verbal tics will be more tricky. Some technical terms have slang pronunciation the speech engine wouldn't know about. It got SCSI correct about half the time, and started off with a great deconstruction of the term. C64 "SID" and "VIC" chips it always initialized. TRS-80 was "eight-zero", etc. Maybe a table? The voice and inflection are very good. I noticed that for longer responses it starts speaking slowly and sped up as it went until it was quite fast. Speaking of fast, the responses to questions began very quickly after my speech stopped. This is great, as many voice models have a noticeable processing delay before responding. This felt more naturally conversational. It handled interruptions well. A simple prompt injection failed, great! I didn't try hard. I asked for exhibit information responses in a few languages which it did well. The speech model had a noticeable American accent! Curiously it responded immediately in Spanish, but took about 20 seconds to start in Japanese. I asked a question in Dutch but it didn't understand so English inputs only at this time? I'm wondering if you've got the LLM to prefer local knowledge you've given it before going to its training or the web. A couple of times it stopped speaking in the middle of a sentence. I don't know if it thought it detected a speech interruption. Made me consider when this is used on a phone speaker in the museum with other unrelated speakers around it. I think this will be a great addition to the museum. Regards, Ralph Broom On 2026-01-02 07:00, vcf-midatlantic-request(a)lists.vcfed.org wrote: > Send vcf-midatlantic mailing list submissions to > vcf-midatlantic(a)lists.vcfed.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.vcfed.org/mailman/listinfo/vcf-midatlantic > or, via email, send a message with subject or body 'help' to > vcf-midatlantic-request(a)lists.vcfed.org > > You can reach the person managing the list at > vcf-midatlantic-owner(a)lists.vcfed.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of vcf-midatlantic digest..." > > > Today's Topics: > > 1. AI Computer Museum Docent - BETA - DEMO (Bob Roswell) > 2. who was first ... (Jeffrey Jonas) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 2 Jan 2026 02:28:06 +0000 > From: Bob Roswell <broswell(a)syssrc.com> > To: vcf-midatlantic <vcf-midatlantic(a)lists.vcfed.org> > Subject: [vcf-midatlantic] AI Computer Museum Docent - BETA - DEMO > Message-ID: > <CY4PR0401MB3586D6F293D1175602B08EF7B0BBA(a)CY4PR0401MB3586.namprd04.prod.outlook.com> > > Content-Type: text/plain; charset="us-ascii" > > > I wrote a voice chatbot that is somewhat guided to be a knowledgeable docent at our computer museum. > This is available for testing for the next few days: (If it does not crash) > > https://museum.syssrc.com/docent > > Privacy - > You will need to give microphone and video permissions. The video is not in use, but I have not figured out how to make the WEBRTC component not ask for camera privileges. Your voice will NOT be saved, but I will have a speech to text transcript of your speaking, and the answers the AI gave. I won't know who you are except your IP address will show up in my logs. > > I'd love any feedback! So far, I am amazed at what it can do, but remember it is an AI, and can and does make stuff up. > > Tech Stack: > Pipecat (Framework) > DeepGram: Text To Speach > Cartesia: Speech To Text > OpenAI: Large Language Model > Python scripts that I wrote based on Pipecat examples > > I'll also be curious to see what my bills are! If it goes crazy, I will need to shut it off! > > > > Bob Roswell > broswell(a)syssrc.com > 410-771-5544 ext 4336 > > Computer Museum Highlights<http://museum.syssrc.com/> > > [cid:image001.png@01DC7B64.5C0834E0] > > > > ------------------------------ > > Message: 2 > Date: Fri, 2 Jan 2026 03:57:28 -0500 > From: Jeffrey Jonas <jeffrey.scott.jonas(a)gmail.com> > To: vcf-midatlantic <vcf-midatlantic(a)lists.vcfed.org> > Subject: [vcf-midatlantic] who was first ... > Message-ID: > <CAOCNM4SVNENsYTk4+1vTDg32pKqc5Rg7cLkVoUAa-RXEV7vDkw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > An interesting article: > https://computerhistory.org/blog/the-neverending-quest-for-firsts/ > links to > https://computerhistory.org/blog/programming-the-eniac-an-example-of-why-co… > > Visitors to the Computer History Museum frequently want to know: what was > the first computer? The first personal computer? In his recent post, > ?Programming > the ENIAC: An Example of Why Computer History is Hard > <https://computerhistory.org/blog/programming-the-eniac-an-example-of-why-co…>,? > Computer History Museum Board Chair Len Shustek notes that one of the > difficulties of computer history, and indeed, history of technology in > general, is the question of ?firsts?: what was the ?first? X, or in > alternate form, ?who [first] invented X?? The problem is that for many of > these ?firsts,? there is no simple answer, because as Len pointed out, > ?What ?first? means depends on precise definitions of fuzzy concepts.? What > seem to be questions with easy, factual answers quickly devolve into > debates over semantics ... > > > End of vcf-midatlantic Digest, Vol 92, Issue 2 > ********************************************** >

1 0

AI Computer Museum Docent - BETA - DEMO
by Bob Roswell 01 Jan '26

01 Jan '26

I wrote a voice chatbot that is somewhat guided to be a knowledgeable docent at our computer museum. This is available for testing for the next few days: (If it does not crash) https://museum.syssrc.com/docent Privacy - You will need to give microphone and video permissions. The video is not in use, but I have not figured out how to make the WEBRTC component not ask for camera privileges. Your voice will NOT be saved, but I will have a speech to text transcript of your speaking, and the answers the AI gave. I won't know who you are except your IP address will show up in my logs. I'd love any feedback! So far, I am amazed at what it can do, but remember it is an AI, and can and does make stuff up. Tech Stack: Pipecat (Framework) DeepGram: Text To Speach Cartesia: Speech To Text OpenAI: Large Language Model Python scripts that I wrote based on Pipecat examples I'll also be curious to see what my bills are! If it goes crazy, I will need to shut it off! Bob Roswell broswell(a)syssrc.com 410-771-5544 ext 4336 Computer Museum Highlights<http://museum.syssrc.com/> [cid:image001.png@01DC7B64.5C0834E0]

1 0

Stewart Cheifet died Dec. 28, 2025
by Jeffrey Brace 31 Dec '25

31 Dec '25

https://obits.goldsteinsfuneral.com/stewart-cheifet He came to VCF East years ago: https://youtu.be/Ncnje4DdRxE. I had tried to get in touch with him the last 5 years without success. I wonder if he was going through some illness. He will be missed! I know him best for his hosting of Computer Chronicles. Jeff Brace

4 3

20 tables left for VCF East 2026!
by Jeffrey Brace 31 Dec '25

31 Dec '25

Tables are going fast! Register here for exhibitor tables: https://forms.gle/XZSjtMRjKMRTxFNn9 Register here for vendor tables: https://forms.gle/XmhAWvjN94r6jdVFA Jeff Brace VCF East Showrunner

1 0

Looking for help on dealing with monitor cataracts on VR201 monitors.
by Herbert Johnson 30 Dec '25

30 Dec '25

> [Dave Shevett] I have 3-4 DEC VR201 monitors that have the dreaded cataracts problem. > I am extremely nervous working on CRTs > I'm happy to work with someone (supervised repairs) or give these to > whomever wants to fix them. Goal is to get my Pro-380 and my DECmates up > and running with a clean video again soon goo --> CRT face 0) Lots of people are scared of messing with CRTs. Lots of reasons, mostly around unfamiliarity. I'm scared to provide advice - "I did what you said and lost [anatomy, fluids] when the CRT [imploded, broke, shocked me]". So anything I say is full of "hold me harmless" statements, I'm scared of legal action. 1) Slightly confusing request from Dave. If you want clean video monitors, why would you "give these [away]" after some one fixes them while you watch and supervise? Maybe you mean "I will provide them locally to someone for (help with?) repair so I can get them back as repaired for use". Anyway, please clarify your terms of work and exchange. Would not hurt to give your general location, doesn't seem like shipping is part of the intentions. 2) As far as people who respond but don't know what Dave is talking about. Here's some reference info, but rather than lecture here, I'll point to lectures on my WEb pages: https://www.retrotechnology.com/restore/adm3a.html Look for "Comments about CRT repairs" for some discussion. This is a problem across many terminals of the era. Buried on the page is a link of one way to repair: https://www.retrotechnology.com/restore/adm3a_nick.html .. but do more homework than I have done. There's lots of way to remove the gooey faceplate from the CRT, research will find examples. Or, obtain another CRT without faceplace, but it has to be (mostly mechanically) compatible. Besides, if the old CRT is functional why obtain another? But it may not be, the screen brightness fades with use (homework). I'm not responsible for any of this information, hold me harmless from any consequences. But the subject interests me, and in fact I have a few of these DEC VR2XX moldy monitors myself. Regards Herb Johnson -- Herb Johnson, New Jersey USA http://www.retrotechnology.com or .net preserve and restore 1970's personal computing email: hjohnson @ retrotechnology dot com or try later at herbjohnson @ comcast dot net -- Herbert R. Johnson, New Jersey USA https://www.retrotechnology.com OR .net preserve, recover, restore 1970's computing email: hjohnson AT retrotechnology DOT com or try later herbjohnson AT comcast DOT net

3 2

OrangePC Octopus Cable
by Andrew Mattera 30 Dec '25

30 Dec '25

Hi all, I am in possession of an OrangePC expansion card for Macintosh, basically a Pentium based PC on a card. however I believe I'm missing the octopus cable. If anyone out here knows what I'm talking about and has this cable, I would be very grateful if you would let me probe the connections for five minutes to possibly recreate these cables. There will be no damage done to the cable, and you won't even notice the procedure was done. it's completely non-invasive. Thanks, Andrew Mattera

1 0

Looking for help on dealing with monitor cataracts on VR201 monitors.
by Dave Shevett 29 Dec '25

29 Dec '25

I have 3-4 DEC VR201 monitors that have the dreaded cataracts problem. In short the glue on the front of the crt has deteriorated, and the front of the screen is all blotchy and icky. The monitors work, it just looks terrible. I am extremely nervous working on CRTs (I did field repairs on Wang OIS and WPS terminals all through the late 80s, and absolutely hated doing the ole "ground the anode to the chassis" bit (scary), but in this case you also need to disassemble the tube frame and scrape / heatgun off all the goo, while still making sure the tube isn't going to implode. I'm happy to work with someone (supervised repairs) or give these to whomever wants to fix them. Goal is to get my Pro-380 and my DECmates up and running with a clean video again soon (hopefully before VCF-east). Thanks! -d

3 2

Re: [vcf-midatlantic] Oregon Trail Hallmark ornament
by bernieS 28 Dec '25

28 Dec '25

Here's a link to a YouTube video of the Oregon Trail Hallmark ornament in operation. https://www.youtube.com/watch?v=gPA2sWnrDmc (Start at 3:30 in the video if you want to skip the unboxing part.) The display appears to be a LED backlit lenticular image, which requires viewing from different lateral angles to switch between two surprisingly high-resolution images: the Oregon Trail menu screen, and the status message, "You Have Died from Dysentery". It's a clever design. Power consumption from the (3) 1.5V LR44 'button' batteries is kept to a minimum this way. Some people have hacked these Hallmark 'Keepsake' ornaments by instead attaching (3) AAA or AAA batteries hardwired to the battery terminals. Three such batteries--especially if they're long-life lithium cells--would likely keep the ornament illuminated for weeks or longer. Hallmark has long been innovatively incorporating electronics technology into its greeting cards, holiday ornaments, and other products. In the early 1990's they introduced the first greeting card with a digital audio recorder/playback device incorporated into a surprisingly thin greeting card for $7.95 retail. The idea was you could record ten-second audio message to your loved one in a greeting card, which when opened would play to them loud and clear. Clever! Phone phreaks and hackers quickly recognized this as a golden opportunity and removed the tiny electronics module from the card and used it to record Automated Coin Totalling System (ACTS) coin-deposit audio signals emanating from the handset earpiece on payphones of local exchange carriers--or better yet from the handset of a phone you called and then depositing more quarters because the ACTS tones were attenuated in the payphone earpiece but were loud and clear in the called party's phone which allowed better recording quality. Then the user could make payphone calls and play back the recorded coin-deposit tones into the handset's microphone by pressing the module's momentary switch to spoof the phone company's ACTS system after it verbally prompted them to "Please Deposit 25 Cents For The First 5 Minutes" (or much more money for Long-Distance calls) in lieu of depositing coins. Such a device, in its various incarnations spanning more than three decades while ACTS was in use, was called a Red Box by the phreak/hacker community. The so-called Hallmark Red Box was hands-down the least expensive and simplest way to create a Red Box, and was popularized by an article entitled "A Gift From Hallmark" that was published in 2600 Magazine back then. I'd read in an electronics trade publication that Hallmark bought millions of digital audio recording chips from Information Storage Devices, Inc. for use in a talking greeting card they planned to release on a certain date. On that day I bought one as soon as the Hallmark store nearest me opened. Phone company payphones by design never returned change for unused call minutes. Cheating callers out of their change was more profitable. With many millions of payphone calls made each day around the U.S. back then, these unearned profits quickly added up to millions of dollars per week for local phone companies and A&T. Some people would keep a running total of how much money the phone company stole from them this way and use their 'credits' to make payphone calls with their Red Box. This led to controversy about who was actually defrauding whom. Thanks for the memories, Hallmark! -bernieS

1 0