HP3000-L Archives

March 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Neil Harvey <[log in to unmask]>
Reply To:
Neil Harvey <[log in to unmask]>
Date:
Sat, 18 Mar 2000 09:29:05 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines)
Yes, and IMHO, it's downfall was that it was not CPU upgradeable, had
limited memory capability, and had to have a bootp server - i.e. did not
boot from native NT. It leaned more towards Novell (remember when HP had a
Novell/NT crisis?), and 100mbps LANS were rare.

It was a few years before it's time, and paradoxically, we spent more time
on ten of these than we did on two hundred "normal" PC's.

IIRC, the final straw was zero support for Windows 95 (they were Win 3.11,
and somewhat, WfWG capable).

But I keep seeing similar concepts, and probably with Terminal Server,
things will pick up again.

Neil


-----Original Message-----
From: Marti Jarsey [mailto:[log in to unmask]]
Sent: Saturday, March 18, 2000 12:17 AM
To: [log in to unmask]
Subject: HP Windows Clients


Once upon a time.......

there was a 'discless PC' called the Hp Windows Client.  I believe this
little gem had an e-prom which would connect to a bootp server and get it's
IP address and software, namely Windows and Reflection, from the server.

Does HP still provide a similar solution?

ATOM RSS1 RSS2