Lunduke
News • Science & Tech
The story of the 1991 HP DOS Palmtop
Evolving from an enhanced calculator... to a full DOS compatible PC in your pocket.
November 20, 2023
post photo preview

The HP 100 / 200 LX palmtops are nothing short of spectacular little machines. Pocket-sized, clamshell, battery powered, MS-DOS computers — with a fascinating (and highly useful) array of hardware and software.

Want to use a modem? Expand storage and functionality with a PCMCIA card? Run full DOS software — and even Windows 3.0 — on the go? All were possible with these little, hand-held marvels.

And, when I say, “Run Windows 3.0”… I really mean it. Here is a picture taken by a Lunduke Journal Community member of their own, personal HP 200LX. Running a full edition of Windows 3.0 (in Real Mode — the 200LX’s 80186 CPU doesn’t support Protected Mode).

But how did these amazing little pocket computers come to be? Let’s take a little tour of the history of the HP LX line, which all started in 1988 at Hewlett-Packard… with a product idea code-named “Cheetah”.

Note: Much of this history is compiled from the notes and memories of Everett Kaser, a programmer who worked on this project (and many others) at HP, combined with bits and pieces gleaned over years of study of these wonderful computers.

1988 - Codename “Cheetah”

 
 

It all started in Corvallis, Oregon — a small city, around an hour and a half outside of Portland, Oregon — at the office known as the “Corvallis Division”.

Image courtesy: hpmuseum.net

The Corvallis Division had already seen some noteworthy success in developing multiple HP computers, including the HP 85A in 1980:

The original idea for “Cheetah” was to be a personal information manager pocket device, powered by the Saturn CPU — which was already in use by multiple HP calculators and ranged from 640 kHz up to around 8 MHz.

The Saturn CPU from an HP 48SX calculator

What’s more, the entire system would run on just 32KB of RAM and use a nearly identical physical design to the HP 19B calculator (with a vertical clamshell design, with a keyboard on the left).

1989 - Codename “Jaguar”

In early 1989, the team made the decision to come up with a new physical form factor. It was at this point that the codename for the project was changed to “Jaguar”.

Instead of keeping to the same look of the HP 19B seen above… they would make a design using a more standard clamshell — with a screen on top, and keyboard on bottom. Like a traditional laptop. But pocket-sized.

And thank heavens they made that change. Because it just wouldn’t have been as cool had they stuck with that original, side-by-side design.

Everything else, though, still remained the same. The Saturn CPU. Not running DOS. Basically just a calculator… but with a lot of personal information management type software built in.

It was also decided that this device needed a spreadsheet program. An idea that would radically alter the direction of the project.

Lotus 1-2-3 leads to MS-DOS

Imagine yourself back in 1989. Now. When I say “Spreadsheet Software”… who do you think of?

You think of Lotus 1-2-3. That’s who.

And, as luck would have it, Lotus had an internal goal of working with a hardware vendor to create what they called a “Portable 1-2-3 Machine”. It seemed like a match made in heaven! HP could develop the hardware and some of the software, and Lotus could provide 1-2-3 (and also develop some of the other software components).

There was just one problem: Lotus 1-2-3 didn’t run on the (very limited) Saturn CPU. It ran on DOS. With an Intel 8086 class CPU.

So the team at HP made the — incredibly wise — decision to ditch the Saturn CPU and turn the “Jaguar” project into a DOS compatible computer. Intel processor and all.

Initially, while “Jaguar” was going to be DOS compatible… they were not going to allow any random DOS software to run. It was going to be locked down to only run the software supplied on the ROM of the device (from HP and Lotus). Quickly this was relaxed, and the ability to drop to a standard MS-DOS prompt was added.

Because… it was iust such an obvious thing to do.

1991 - The HP 95LX

Development of this new 8086, DOS powered device — now dubbed “Jaguar II” — moved ahead at an incredibly fast pace, with the release planned to happen just 13 months after the basic specs were decided upon. Software, hardware, all of it.

Image courtesy: palmtoppaper.com

In the end, the HP 95LX managed to ship just a couple months later than planned — in April of 1991. Which is darned impressive considering the massive investment in both hardware and software.

The final 95LX shipped with an NEC V20 CPU (which was an 8088 compatible processor at 5.37 MHz), 1MB of RAM, and up to 32MB of removable storage. The operating system was MS-DOS 3.22, which booted from ROM.

All of this was powered by AA batteries. Which, let’s face it, is pretty cool.

It included a host of custom built, personal information management software and — of course — Lotus 1-2-3.

Image courtesy: oldcomputers.net

Just look at it. Full QWERTY keyboard. Even has a 10-key numeric keypad. And Function keys. It might be a small keyboard, with little membrane keys… but it’s complete and surprisingly usable. It even has arrow keys (see the top right of the keyboard).

But it wasn’t perfect. Not yet.

The HP 95LX was an impressive (and incredibly fun to use) little DOS palmtop. But it had some problems.

The first was the display. A non-standard 240x128 LCD (with a 40x16 text mode). This presented significant compatibility issues with existing DOS software.

The second was the speed. The 8088 compatible CPU was a bit… to put it mildly… pokey. And a great deal of existing software simply required more oomph.

The third was battery life. It wasn’t bad, running off a set of AA batteries. But the team knew they could do better.

1993 - HP 100LX - Codename "Cougar"

Over the next two years the team worked to fix those problems — all while refining and improving the built-in software.

The, rather funky, 240x128 display of the 95LX was ditched for a standard, monochrome CGA display at 640×200. This allowed for greatly enhanced software compatibility with existing DOS software. Including, believe it or not, games.

For example here is Space Quest 3 running on an HP 200LX (which is using the same display and CPU of the HP 100LX):

Image courtesy: members of the Lunduke Journal Community

And here is a snapshot of SimCity running on the built-in CGA display:

Image courtesy: Palmtoptube.com

The NEC V20 “8088” CPU was swapped out for an 80186 compatible CPU (a “Hornet”) running at a higher clock speed. This was a significant boost in both horsepower and CPU functionality — which allowed the running of many software applications that traditionally required an 80286 processor.

Then the voltage was dropped from 5V to 3V. Effectively giving a significant gain in battery life.

Of course there was also the software upgrades — both to the included, in-house developed launcher and an upgrade to MS-DOS version 5.0.

All of which combined to make the 100LX and 200LX (which were nearly identical in most ways) extraordinarily compatible with desktop DOS-compatible PCs. Considering all of this was powered by two AA’s and could fit in your pocket?

Nothing short of spectacular.

And, to think, this all started out as what was — essentially — a nice HP calculator with some personal information manager stuff built-in.

Thank heavens the team decided they needed a spreadsheet.

community logo
Join the Lunduke Community
To read more articles like this, sign up and join my community today
7
What else you may like…
Videos
Podcasts
Posts
Articles
Open Source AI Definition: Not Open, Built by DEI, Funded by Big Tech

Run by an "Anti-Racist, Decolonizing" Activist, the new Open Source Definition is anything but Open.

The article:
https://lunduke.locals.com/post/5917220/open-source-ai-definition-not-open-built-by-dei-funded-by-big-tech

More from The Lunduke Journal:
https://lunduke.com/

00:18:35
GNOME bans Manjaro Core Team Member for uttering "Lunduke"

The GNOME team has censored -- and deleted the account -- of the maintainer of Manjaro Linux GNOME Edition. Why? Because he linked to a Lunduke article.

GNOME bans Manjaro Core Team Member for uttering "Lunduke":
https://lunduke.locals.com/post/5908516/gnome-bans-manjaro-core-team-member-for-uttering-lunduke

More from The Lunduke Journal:
https://lunduke.com/

00:17:16
GNOME Ousts Elected Board Member in Secret, Tells Nobody for 2 Months

Secret meetings. No transparency. Total chaos at the GNOME Foundation as they remove Sonny Piers, one of their Board Members, without telling anyone. This all happens right as the GNOME Executive Director quits, GNOME announces dire financial circumstances, and a disastrous "5 year plan" focusing on DEI.

The article:
https://lunduke.locals.com/post/5899324/gnome-ousts-elected-board-member-in-secret-and-tells-nobody-for-2-months

More from The Lunduke Journal:
https://lunduke.com/

00:37:30
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

Heads up:

The Lunduke Computer Operating System forum is getting some structure... and, for those of you looking to get involved, posts are starting to go up discussing specific areas available for contribution.

https://lcosforum.lunduke.com/

I installed Llama 3.1 8B locally on my $600 windows 11 machine (Ryzen 7 mobile processor, 8 cores, 64gig ram, integrated gpu). Not exactly a high performance genai machine.

Initial impression? Pretty nice. Quick enough - but not nearly as quick as ChatGPT.

I told it about Lunduke and OSNews and asked for a Haiku:

Truth stands strong against hate
Lunduke's voice echoes love loud
Light shines in the dark

With some more prompting we arrived at:

Bytes of love prevail
Osnews' hate crashes to zero
Lunduke's code saves

Not bad. I gave it one of my blog posts to review, and it did a solid job. Then we discussed diabetes and such. Even this 8B version, is nice.

The 70B version will probably run on my machine.

Looking forward to someone taking off the censorship. A model this good, uncensored, running locally? Game changer.

"source" (Linux Command) 👨‍🏫 I know it from a "User Level Red Hat" Course that I took in Community College (Tech School).

post photo preview
Editor of OSNews calls for the murder of a Conservative, Jewish Tech Journalist
Leftist Extremist OSNews says Lunduke is "Nazi" who must "die".

The Editor of OSNews.com has declared that I, Lunduke, am a member of the Nazi party -- and encourages others to murder me.

I repeat: A Tech Journalist has stated -- as a matter of fact -- that a proud Jewish man is a Nazi that must be killed.

Absolutely insane.

On Friday, July 26th, the Editor of OSNews.com (Thom Holwerda), posted the following to his Mastodon account:

"Hey linuxrocks.online, you have a nazi infestation. Considering your instance seems to use only approved registrations, this surely raises about a million red flags."

 

Source: Mastodon

 

What was the "Nazi infestation" he speaks of?  He includes a screenshot of The Lunduke Journal account to make it clear who he was refering to.

While this is already absolutely insane (no sane person would call a proud Jewish man a member of the Nazi party)... it gets far, far worse.

A few hours later, the OSNews.com Editor followed up with the following statement:

"Since the instance linuxrocks.online is openly, knowingly, and willingly hosting nazis, I'm going to block the whole instance. If you're a follower on said nazi instance, I suggest you reconsider your choice of instance.

 

No quarter for nazis. The only good nazi is a dead nazi."

 

Source: Mastodon

 

"No quarter for nazis. The only good nazi is a dead nazi."

Am I a Nazi?  Obviously not.  But, that Tech Journalist says that I am a Nazi.  And I must be killed.

Which means, according to the Editor of OSNews, "The only good [Lunduke] is a dead [Lunduke]."

Is it libel?  Without question.  Is this a clear threat of violence?  Absolutely.

He also appears to be stating that anyone who simply exists on the same server as me is, by proximity, also a Nazi.  And they must also be murdered.

Few Will Condemn This

I wish I could say this was a completely isolated incident.

The sad fact is, a number of Tech Journalists share the extreme, Leftist, disturbed, violent views of the Editor of OSNews.  They believe that many groups (including both Conservatives and Jews) are evil "Nazis" who must be murdered.

And, while many other Tech Journalists do not agree with those warped, twisted ideas... few, if any, will speak out against those calls for violence and death.

All Hope Is Not Lost

In those vile messages quoted above, the Editor of OSNews was clearly attempting to bully the administrator of a specific server -- whose only crime was allowing me to exist.

How did that server's administrator respond?  In an incredibly reasonable way:

"We do not appreciate name-calling here. Would you like to present your evidence that a user needs to be removed rather than going straight to name-calling."

 

Source: Mastodon

 

No name-calling.  Present evidence if you have a concern.

Reasonable.  Calm.  Practical.

Seeing that sort of response gave me just a little extra hope for the future of the Open Source and general computer industries.  If we can get more brave, reasonable, thoughtful people -- like that server administrator -- speaking against the hate and violence of people like the Editor of OSNews... we might just stand a chance.

(Of course, no response given -- by the OSNews Editor -- to this reasonable request.)

A Related Thought From Lunduke

Let's pause, and take a step back.  I'd like to talk, for just a moment, about politically charged discussions (like this one) within the broader Tech World... and on The Lunduke Journal specifically.

When I first started The Lunduke Journal, I focused entirely on the technical aspects of computing.  "Stay clear of politics, Lunduke," I told myself.  "Stick to the happy tech stuff!"

And, by and large, I managed to stay true to that for many years (with no more than a passing, momentary blip into politically charged topics once in a blue moon).

But, here we stand.

At a time when people are being banned from Open Source projects solely because of their political leanings (often leading to the complete destruction of those projects).  When entire Open Source organizations and concepts are being re-shaped -- into something not-at-all "Open" -- by political activists.  When Big Tech corporations are regularly discriminating against people based on the color of their skin or their sex.

And when, like we saw today, a Tech Journalist declares that Conservative Jewish Nerds (and the people who exist near them) are "Nazis" who need to be murdered.

Staying quiet on these issues is simply not an option.

Not for The Lunduke Journal.  And not for any other Tech Journalist worth a damn.

It is well past time to speak out against this insanity.  If you are a Tech Journalist (in whatever form... articles, podcasts, videos), shine a light on these stories.  Show people the damage that is being done to the world of computing by these political extremists.

The Lunduke Journal can't do this all alone.  But if I have to do it on my own... I will.

Because I love computing.  I love the history of it, the technical aspects, the future... all of it.  And computing is worth saving.

So, I will keep covering all of it.  Even if these extremists keep threatening to kill me.

Read full Article
post photo preview
Funny Programming Pictures Part XLIX
Mogwai & Michael J Fox Edition

Not all of these pictures are about programming and computers.  Some are about Mogwai and Michael J Fox.   Just felt right.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Read full Article
post photo preview
Open Source AI Definition: Not Open, Built by DEI, Funded by Big Tech
Run by an "Anti-Racist, Decolonizing" Activist, the new Open Source Definition is anything but Open

The Open Source Initiative is preparing to finalize what they call "The Open Source Aritificial Intelligence Definition" -- a set of rules which A.I. systems must adhere to in order to be considered, officially, "Open Source".

And everything about it is truly peculiar.

From the fact that it considers "No Data" to be "Open Data" (yeah, try to wrap your brain around that little nugget) to the corporate sponsorship (from corporations in the "Closed Source A.I." business)... to the "anti-racist, decolonizing" consultant they hired to put the whole thing together.

Yeah.  "Decolonizing".  The whole thing is just plain weird.

A Little Background

The Open Source Initiative's cliam to fame is that they are the steward of what is known as the "Open Source Definition" (aka "the OSD").  A set of rules which any software license must adhere to in order to be considred, officially, "Open Source".

The "OSD" began life back in 1997 as the "Debian Free Software Guidelines", written by Bruce Perens.  Later, with the help of Eric Raymond, that document morphed into the "Open Source Definition"... at which point the two men created the "Open Source Initiative" to act as a certification body for the OSD.

Fun Historical Tidbit: The Open Source Initiative likes to tell a long-debunked story about the creation of the term "Open Source" which they know is historically incorrect.  That little tidbit isn't critical to what we're talking about today... but it's just plain weird, right?

Flash forward to today, and both of the founders -- Perens and Raymond -- have been forced out or banned from the Open Source Initiative entirely.  Now the organization, free from the influence of the founders, is looking to expand into the newly exciting field of "Artificial Intelligence".

Thus: The creation of "The Open Source A.I. Definition"... or the OSAID.

The Anti-Racist Leadership

To create this new "OSAID", the Open Source Initiative hired Mer Joyce from the consulting agency known as "Do Big Good".

 

Mer Joyce: Process Facilitator for the Open Source AI Definition

 

Why, specifically, was Mer Joyce hired to lead the effort to create a brand new "Open Source" definition, specifically focused on Artificial Intelligence?

  • Was it her extensive background in Open Source?
  • Or her expertise in A.I. related topics?
  • Perhaps it was simply her many years of work in software, in general?

Nope.  It was none of those things.  Because, in fact, Mer Joyce appears to have approximately zero experience in any of those areas.

In fact, the stated reason that Mer Joyce was chosen to create this Open Source definition is, and I quote:

 

"[Mer Joyce] has worked for over a decade at the intersection of research, policy, innovation and social change."

 

Her work experience appears to be mostly focused on Leftist political activism and working on Democrat political campaigns.

As for the consulting agancy, Do Big Good, their focus appears to be equally... non-technical.  With a focus on "creating an equitable and sustainable world" and "inclusion".

 

The "Values" of "Do Big Good".

 

When "Do Big Good" talks about what skils and expertise they bring to a project, they mention things such as:

  • Center marginalized and excluded voices.
  • Embody anti-racist, feminist, and decolonizing values.
  • Practice Cultural humility.

 

How "Do Big Good" works.

 

Note: Yes.  They wrote "decolonalizing".  Which is not a real word.  We're going to give them the benefit of the doubt and assume they meant "decolonizing".  Spelling errors happen.

Now, how does "Embodying decolonizing values" help to draft a definition of Open Source Artificial Intelligence licensing?

No clue.  But, apparently, "decolonizing" and being "anti-racist" is important to the Open Source Definition and software licensing.

You'll note that the only software-related skill this "Do Big Good" company appears to have is that they can "work virtually or in-person".  In other words: They know how to use Zoom.

In fact, this consulting firm only gives three examples of client projects they've worked on.  And the other two are non-technical policy documents for the government of Washington State.

 

The other work of "Do Big Good".

 

Why this agency, and this individual, was hired to lead the work on the OSAID is beyond baffling.  Just the same, this appears to be part of a larger pattern within Open Source and Big Tech: Hiring non-technical, political activist types to lead highly technical projects.  It doesn't usually go well.

The Diverse Working Groups

Considering that the leadership hired to oversee the OSAID's creation is extremely non-technical --  and almost 100% focused on "anti-racist" and "decolonizing" activism -- it's no surprise that one of the first steps taken was to create "working groups" based entirely on skin color and gender identity.

 

"The next step was the formation of four working groups to initially analyze four different AI systems and their components. To achieve better representation, special attention was given to diversity, equity and inclusion. Over 50% of the working group participants are people of color, 30% are black, 75% were born outside the US, and 25% are women, trans or nonbinary."

 

What does having "25% of the people being Trans or nonbinary" have to do with creating a rule-set for software licensing?

Your guess is as good as mine.

But, from the very start of the OSAID's drafting, the focus was not on "creating the best Open Source AI Definition possible"... it was on, and I quote, "diversity, equity and inclusion".

The best and brightest?  Not important.  Meritocracy?  Thrown out the window.

Implement highly racist "skin color quotas" in the name of "DEI"?  You bet!  Lots of that!

"No Data" = "Open Data"

With that in mind, perhaps it is no surprise that the OSAID is turning out... rather bizarre.

Case in point: The OSAID declares that the complete absence of the data used to train an A.I. system... does, in fact, qualify as "Open".  No data... is considered... open data.

If that sounds a bit weird to you, you're not alone.

Let's back up for a moment to give a higher level understanding of the components of an A.I. system:

  1. The Source Code
  2. The Training Data
  3. The Model Parameters

If you have access to all three of those items, you can re-create an A.I. system.

Now, we already have the OSD (the Open Source Definition) which covers the source code part.  Which means the whole purpose of having the OSAID (the Open Source AI Definition) is to cover the other two components: The Training Data and the Model Parameters.

Without an exact copy of the Training Data used in an A.I. system, it becomes impossible to re-create that A.I. system.  It's simply how the current generation of A.I. works.

However, the OSAID does not require that the Training Data be made available at all.  The definition simply requires that:

 

"Sufficiently detailed information about the data used to train the system, so that a skilled person can recreate a substantially equivalent system using the same or similar data."

 

At first that sounds pretty reasonable... until you really think about what it means.

This means that an A.I. system would be considered "Open Source A.I." even if it provided zero data used to train it -- it simply must be possible for someone to use the closed, proprietary data... if they should happen to obtain it.

That's like saying "My software is open source.  But I'm not going to let you have the source code.  But, if you did get the source code -- like through espionage or something -- you'd be able to use it.  Which means it's open source.  But you can't distribute or modify that source.  Because it's mine."

Now, an argument could be made that the source code for an AI system could be open even if the data is all closed... and, therefor, it would be "Open Source" under the old OSD.  Which is absolutely true.  But, in that case, why have an "OSAID" at all?  Why not simply keep the existing OSD and focus on that?

Well... I think we have a simple answer to why this OSAID is so utterly strange...

The Corporate Sponsors

The Open Source Initiative is not a huge foundation, especially when compared to some.  But it's revenue is not insignificant.  And it's growing.

In 2023, the Open Source Initiative brought in a revenue of $786,000 -- up roughly $200,000 from the year prior.

 

Source: Open Source Initaitive 2023 Annual Report

 

And who sponsors the Open Source Initiative?

Google.  Amazon.  Meta.  Microsoft (and GitHub).  Red Hat.  And many other corporations. 

 

A Sampling of the Open Source Initiative Sponsors.

 

 

Many of these companies have some noteworthy things in common:

  • They are in the A.I. business in some way.
  • They make use of "Open Source" in their A.I. products.
  • They use "Open Source" as a promotional and public relations tool.
  • They, in one way or another, work with a closed, proprietary set of A.I. training data.
  • They have significant "Diversity, Equity, and Inclusion" efforts.

When you add that all together, this "Open Source AI Definition" begins to make a lot more sense.

It is, in short:

An effort to create a "Certification" which will declare all of their A.I. systems (no matter how closed their data is) as "Open Source"... while simultaneously being run by a DEI activist organization with a focus on racial and gender identity quotas.

It checks a whole lot of check boxes.  All at once.

What Impact Will This Have?

While many may argue that this "OSAID" is simply irrelevant -- and can be ignored by the broader "Free and Open Source Software" industry -- that misses a key impact that is worth noting.

That being: The continued corruption of both the ideas and the organizations of Open Source.

Not only has the Open Source Initiative banned their founding members (and re-written their own history)... they are now seeking to create a new "Open Source Definition" which will allow for systems consisting primarily of closed, proprietary data to be considered "Open Source".  Thus making their Big Tech financiers happy.

The meaning of the term "Open Source" is being actively modified to mean "A little open, and a lot closed".  And many of the same corproations which are funding this effort are also funding things like... The Linux Foundation.

Which means this corruption and dilution of the concept of "Open Source" is likely to spread far beyond the reaches of one, small (but growing) licensing certification foundation.

Also, apparently, decolonizing values... or something.

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals