Recent content by splorp

Speaking of AT&T gear … I have both an EO Communicator 440 and 880, in the box. Those are a couple of the oddball tablets in the collection.

I believe it was an HDMI adapter/upscaler.

An adapter is nice to have kicking around, regardless. If you can’t locate an actual Newton adapter, there are a number of commonly available Sony adapters that work quite well. From the Newton FAQ: Which power adapters can I use?

I didn’t take a many photos today, but here’s a handful of things I enjoyed.

Hey! Another Canadian! I’ll be the guy with the MessagePad 2100.

The Japanese edition is basically the same layout, images, order of sections … just translated.

I have a copy of Defying Gravity (and a copy of the Japanese translation). In fact, I actually had three additional copies in my Newton collection that I just gave away on the NewtonTalk mailing list this week! And … I re-read it every few months! Agreed, they should be more images of the...

I’ve listed a number of 3D printable replacement part designs for Aapple Newton devices in the Newton FAQ. 🔗 Can I create replacement parts for my Newton device using a 3D printer? There currently isn’t a Newton category in the wiki … is it ok to go ahead and add one?

I’ll make sure to document some of the festivities at any rate.

Yes, VCF PNW is happening! I’ll be there … with at least one Newton device in tow. May 2 – 3, 2026 Tukwila Community Center 12424 42nd Avenue South Tukwila, WA 98168 https://vcfpnw.org

The hum is always present in backlit Newton devices. It’s caused by the switching power circuit and affects the high voltage transformer associated with the EL backlight. I’m wondering if pulling things apart and reassembling the eMate moved a few things slightly to cause the hum to be more...

Huzzah! Mmmm … tables.

Thanks, Eric! I’ll give this another go as soon as I can.

Here’s a minimalist version of the site rendered on my Newton MessagePad 2100 using Courier. For some reason, I can’t get the site to load using the Newt’s Cape browser. It conks out with a “headSpec” error … maybe something to do with a malformed HTTP header?

There’s another one being planned for January … stay tuned.