HP3000-L Archives

September 1997, Week 4

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:
"Stigers, Greg ~ AND" <[log in to unmask]>
Reply To:
Stigers, Greg ~ AND
Date:
Thu, 25 Sep 1997 10:06:18 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
As I read the message, the company building on sand was HP, basing the
HP NetServer on NT. Not that I should talk about using confusing
metaphors...

Our 3Ks are ran by an outsourcer, whereas our LAN is in house. Oddly,
our project's LAN / server is an HP product. Interesting coincidence,
and it is just that. We also develop on the LAN, using Micro Focus
WorkBench, then upload to the 3K for system testing, modeling, and
production. If Micro Focus integrated the PC workbench with the 3K
product the way it is with their mainframe products, or even let us buy
from them and provide adequate support (even, it does this on the PC and
that on the 3K, tell us why), we would use their compiler and debugger
(their 'animator') on the 3K in a heartbeat. Shame not to see better
integration between product from either vendor; that's the stuff of
which golden handcuffs are made. Maybe one could switch, but why would
you ever want to?

>----------
>From:  Denys P. Beauchemin[SMTP:[log in to unmask]]
>Sent:  Tuesday, September 23, 1997 6:09 AM
>To:    [log in to unmask]
>Subject:       Re: [HP3000-L] MPEiX 6.0
>
>HP is in California.  Microsoft is in Washington state.  Just an observation.
<snip>
>The HP Netserver.  Based on Microsoft's
>NT Server operating system (building on sand rather than rock is a
>particular tendency of companies based in California I guess)
<snip>

ATOM RSS1 RSS2