Several postings asked similar questions so I have consolidated them
together:
>> What if there were a simple real time process to determine the
outstanding
>> patches for your specific MPE and subsystem versions?
>Like, say, "patchman"? (developed by Mark Bixby)
>How does this script differ from patchman?

First, our patch selection script is not meant as a replacement for Mark
Bixby's excellent PATCHMAN script. The way I look at it, PATCHMAN is a real
time alternative to the power patch process. It connects, evaluates, and
downloads all of the outstanding patches for that HPe3000 system.

Our patch analysis script is designed to be a diagnostic tool, even for
HPe3000 systems that are not connected to the internet. (very few HP3000
systems can ping HP.COM) In many situations we have customers that are
experiencing a problem and we would like to see if their are specific
patches that they don't have that address the symptoms. I'm sure that may
other software support groups have the same problem: Does the customer have
HP product Y or Patch X installed? Consider all of the postings about 100BT!
One sure method to determine this is have them run our script and include
their email address in the distribution.

Also, we wanted to develop another practical HPe3000 demo application. In
this case a combo script/email from the HPe3000 application.

Finally, I forgot to give Ed Stouder credit for his contribution to the web
interface. Sorry Ed.

Cordially,
Mike Hornsby
Co-founder/Chief Technical Officer
Beechglen Development Inc. (beechglen.com)
513-922-0509
[log in to unmask]