Subject: | |
From: | |
Reply To: | |
Date: | Wed, 3 Jan 1996 18:11:45 EST |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On Wed, 3 Jan 1996 17:29:21 GMT Kriss Rant said:
>To order MPE/iX software documentation on CD-ROM with a
>new HP 3000 system, option 0BC must be specified with the
>media product, 51453B or 51454B. Option 0BC includes a one
>user license for HP LaserROM/PC (P/N 50725B) and HP CD
>Extensions for MPE/iX (P/N B3683AA). Additional user
>licenses must be ordered separately. HP CD Extensions
>require MPE/iX 5.0.
*cough*
>HP CD Extensions is a client/server utility that allows
>PC applications to access a CD-ROM drive mounted on an
>HP 3000 system.
*snicker*
>Since the CD Extensions require MPE/iX 5.0, you may wish to
>purchase the A3184A CD-ROM Drive, which is a newer Drive for
>MPE/iX 5.0 systems.
This sounds *WONDERFUL* doesn't it? We thought so too as did some other
customers. We ordered a CD-ROM and an 8-user license for CD Extensions.
Unless they have completely redesigned the product, you're in for a few
surprises when you receive your new toys.
(1) The CD-ROM server software on the HP3000 uses the *same* TCP port as
the new OpenDesk server (for the OpenDesk clients). Not fun if you
are an OpenDesk site.
(2) The CD-ROM extensions sit beneath Microsoft's MSCDEX driver which gets
loaded at boot time. The extensions are also a TSR driver.
(3) You must have an active TCP stack running (I think NDIS-based) before
loading the extensions, else it will fail.
(4) If you are using any of the newer, civilized Windows-based TCP stacks
(RNS/Windows, Trumpet Winsock, and many others) your stacks aren't
loaded until Windows is loaded (or the stack is invoked from Windows).
In short, unless you're running a totally DOS-based TSR TCP/IP stack, you
can use the extensions. We had a grand total of zero qualifying machines.
We retained the CD-ROM (at least you can get pull releases on CD-ROM and
the process reduces overall downtime for updates). We returned the box of
CD Extensions unopened.
It was a beautiful idea with a horrible implementation, and based on the
responses we received to questions about the above serious problems, it
appears to be another dead-end product with no future. I would love to
see it promoted to Winsock compliance and the listening port either changed
or a configurable option, but it's been over a year with no progress.
Get the LaserROM documentation. Put it on a Novell or NT server. Enjoy.
Of course, setup your license tracking software to only allow one concurrent
user. Works great, lasts a long time.
Jeff Kell <[log in to unmask]>
|
|
|