HP3000-L Archives

January 1995, 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:
Richard Gambrell <[log in to unmask]>
Reply To:
Richard Gambrell <[log in to unmask]>
Date:
Wed, 25 Jan 1995 10:48:45 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (57 lines)
According to M J L:
>
> Of course we are mostly running Windows NT Workstation or Windows For
> Workgroups 3.11 (with MS 32 bit TCP/IP drivers).  The Image client
> will not work with the WFW ODBC drivers and will not ride the
> Winsock dll for NT workstation.  SIGH.
>
> HP's efforts are focused on Windows '95 ('96?)....and the Response
> Center told me that Windows NT was no longer a strategic direction
> for HP (whatever that means...)
>
> So, until I can get a couple of "spare" systems retro installed with
> LAN Manager and HP ARPA services and an old version of Windows 3.1
> to be able to run the client, we've pressed on to use Power Builder
> and SQL Server for our testing and development, and Image on the
> HP3000 is idle.
>
Try buying a new Vectra with Windows 3.1 - everybody, it seems, ships
WFWG 3.11 instead. I have heard (don't recall where) that OpenView
applications like DTC manager and Interconnect manager don't work well
under WFWG either. How did HP miss the boat on this one? It is the
same way Cognos missed the growing use of Winsockets, so PH Client for
Windows requires the old tcp/ip from HP or WRQ, and can't be used with
*current* network drivers like Microsoft's 32 bit tcp/ip?
 
You might get the idea that these companies are just not keeping up with
what their customers are doing or where the market is right now. Some of
this is Microsoft's doing - by keeping the Windows 95 in front of everyone
for so long, but not delivering.
 
My biggest disappointment with HP is that the systems people keep trying
to sell me Unix and 3000 servers with terminals or underpowered "Windows
client PCs" - yet the PC people at HP have some nifty PCs and server
(Netserver) products that just stay ahead of the "larger" systems.
[For example, the PCs support 100VG-Anylan and has since Aug. I think
support on the 9000 is announced, but not available and on the 3000 is
just a rumor at best.]
 
Netware 3.11 support for MPE is another one like this, where HP finally
is close to catching up with the market - if you can put up with not
deleting a Netware file from within MPE, but the market is now moving
toward Netware 4 and Windows NT. Will HP finish 3.11 or will it get
going on Netware 4 and NT soon enough to keep up this time?
 
I know it takes lots of time to insure reliability and to test combination
of products, but that is the challenge  - keep up with the market or
die, while keeping good quality controls, etc.!
 
Sorry for the bandwidth - I'll get off the soapbox now.
 
 
--
-- - - - Speaking for myself and not necessarily anybody else - - - - - -
Richard Gambrell        | Internet: [log in to unmask]
Mgr. Tech. Services     | POT:      504-483-7454     FAX: 504-482-1561
Xavier University of LA | Smail:    7325 Palmetto, New Orleans, LA 70125

ATOM RSS1 RSS2