HDTenEightyP/NetNews huggingface dataset:
From: a006700@hp9000.csc.cuhk.hk (Tang Sammy)
Subject: X11R5 on hpux 8.07
Organization: The Chinese University of Hong Kong
Date: Tue, 1 Sep 1992 08:35:53 GMT


Hi all,

Has anyone try building the X11R5 on HP-UX 8.07?
It seems that everything is ok except that the main.c for
xterm when compiled with -DSYSV. It complainted "_file undefined"
with an error number 1588.

I'm not too sure on what things I've missed in building the R5,
the release note is a bit too heavy to me and if I've not missed
anything in the docs, the steps for building it should be very straight.

Any comments and sorry if this is a FAQ.

Thanks in advance.

Sammy
Newsgroups: comp.sys.hp,tor.general
From: Delavar.K.Khomarlou@hydro.on.ca (Delavar K. Khomarlou)
Subject: HPIB Drivers wanted
Keywords: HPIB Drivers
Reply-To: Delavar.K.Khomarlou@hydro.on.ca
Organization: Ontario Hydro
Date: Wed, 2 Sep 1992 12:46:36 GMT

Can anyone tell me where I can get HPIB drivers for AUTOCAD Software.

I am looking for AUTOCADD Version 10 drivers for HP7220 and HP9872

Plotters.  I don't check this group often please respond via Email at

DELAVAR.K.KHOMARLOU@HYDRO.ON.CA or call me at (416) 592- 5372.

From: mjs@hpfcso.FC.HP.COM (Marc Sabatella)
Date: Wed, 26 Aug 1992 20:14:28 GMT
Subject: Re: Shared libraries have me very confused!
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.sys.hp

/ rkitts@netcom.com (Rick Kitts) /  7:05 am  Aug 24, 1992 /
>what appears to me to be an ancient HP3000 series 25 system running
>something called MPE 5.

I don't believe there was any MPE V thru MPE I machines that ended in '5'.
Series 30 was the smallest.  70 was the largest.

Oh, some protos of series 33 might have been labelled 25?
Or the ICF 25 computer family might have been the series 30 and 33.
Newsgroups: comp.sys.hp
From: gcagle@dracula.mentorg.com (Greg Cagle)
Subject: New maintainer for the FAQ
Originator: gcagle@dracula
Date: Fri, 04 Sep 1992 20:27:03 GMT
Organization: Mentor Graphics 
Keywords: faq
Followup-To: 


This is to announce the transition of the FAQ from Mark Krause
to myself. I'd like to publicly thank Mark for getting the ball
rolling and starting this thing up.

I am in the process of putting together the next version of the FAQ.
Please e-mail any submissions to me (greg_cagle@mentorg.com)
by 9/11/92 so I can assemble the next FAQ by 9/18/92. Thank!

- Greg
-- 
Greg Cagle               "Have you got a Clavin in here?"
Mentor Graphics          "Yes, but it hasn't flushed right for a month!"
greg_cagle@mentorg.com
From: ssouth@hpldsla.sid.hp.com (Steve South)
Date: Tue, 1 Sep 1992 17:10:18 GMT
Subject: Re: cable curiosity
Organization: HP Scientific Instruments Division - Palo Alto, CA
Newsgroups: comp.sys.hp

lee@ceg.uiuc.edu (Chris Lee) writes:

>Why doesn't the power cable have screws/locks of sorts to hold
>it in place?  

I suspect it is done deliberately so that it *will* pull out easily. If a
piece of equipment were to be pulled, or were to move accidentally, it is far
better that the power cord be disconnected by the plug coming out rather than
having wires pulled out of a plug. That could easily cause a fire or 
electrocution.

That's my guess.

>Chris Lee

Steve South.
Newsgroups: comp.sys.hp
From: lapp@waterloo.hp.com (David Lapp)
Subject: Re: Dumping an HP 900/710 X11 window on an HP Laserjet IIP
Date: Tue, 25 Aug 1992 17:02:08 GMT
Organization: HP Panacom Div Waterloo ON Canada
X-Newsreader: Tin 1.1.3 PL5

Ronan Melennec (melennec@stna.dgac.fr) wrote:
: [Sorry, I let previous post out with a bad header]
: 
: Hello,
:  
:  I'm trying to do X11 window dumps on an HP Laserjet II Plus (512 Ko,
:  no PostScript interpreter).
:  
:  I'm using HP-provided tools on an HP 9000/710 workstation.
:  
:  The command :
:  xwd | xpr -device ljet -density 300 | lp -dlw
:  only has the printer print "Line too long"...
:  
:  I've tried other values for density parameter, without success
:  (with 150, only the leftmost topmost part of the window gets printed,
:  the rest of the sheet is garbage ; with 75, the whole sheet is
:  garbage).
:  
:  Could anyone suggest a working alternative ? I have FTP access.
:
I'm not sure about the density parameter but you probably
need to specify that the data is 'raw' to lp. Try:

 xwd | xpr -device ljet -density 300 | lp -dlw -oraw

Dave Lapp

From: tay@hpbbi4.BBN.HP.COM (#Michael Taylor)
Date: Thu, 3 Sep 1992 08:39:04 GMT
Subject: Re: cable curiosity
Organization: Hewlett-Packard GmbH
Newsgroups: comp.sys.hp

> This is just a curiosity....
> 
> Why doesn't the power cable have screws/locks of sorts to hold
> it in place?  

And this is just a guess, but I think it may be because we are using
"standard" power cords which don't have such a feature.

Pax,

Mike Taylor
Sales Response Center Engineer
Computer Systems Organization Europe

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Surface: Hewlett-Packard GmbH     Internet: tay@hpbbn.bbn.hp.com
	 Herrenberger Strasse 130    Phone: ++49 (07031) 14-1198
	 7030 Boeblingen, Germany      Fax: ++49 (07031) 14-2721
From: olson@anchor.esd.sgi.com (Dave Olson)
Newsgroups: comp.sys.hp
Subject: Re: What is the default blocksize on HP DAT tapes ?
Date: 30 Aug 92 00:57:41 GMT
Organization: Silicon Graphics, Inc.  Mountain View, CA

In <BtLL1z.HI7@news.cso.uiuc.edu> e-sink@uiuc.edu (Eric W. Sink) writes:

| I'm writing 4mm DAT tapes on my Indigo, and reading them on HP's.
| To get them to read on the HP, I have to set the blocksize to 256k
| manually, since that is apparently the default blocksize for the
| SGI, but the HP is something else.  I would rather force the blocksize
| on the SGI side, allowing the HP to read the tapes more easily.  So,
| what is the default blocksize for HP DAT tapes ?
| 
| SGI:
| 
| tar cvf - MYFILE | dd of=/dev/tape bs=?????

My god, why would you do it like that!  It complicates error
recovery/handling , eats up CPU resources, and is probably slower.

What is wrong with 'tar cvfb /dev/tape # MYFILE'?  We default
to 256 Kbytes (# == 512) if the b option is not specified when
the drive is a DAT.  That is half the size of the RAM buffer
on the drive.  By default, we write in variable block size, so
you get 'blocks' that are actually 256 Kbytes.  Some vendors
hardware and/or drivers can't cope with that (Sun has to be
less than 64 Kbytes - 2, at least, up through SunOS 4.1.X).
Some versions of tar also have a maximum block size that they
will tolerate.  So the best thing to do is to simply choose
a block size such that the machines you want to exchange tapes
with can handle it.
--
Let no one tell me that silence gives consent,  |   Dave Olson
because whoever is silent dissents.             |   Silicon Graphics, Inc.
    Maria Isabel Barreno                        |   olson@sgi.com
From: felixk@hpfcse.HP.COM (Felix Krasovec)
Date: Tue, 1 Sep 1992 04:14:25 GMT
Subject: Re: File-splitter for email
Organization: Hewlett Packard Co.
Newsgroups: comp.sys.hp

Try the split command.
-chewy
From: dhandly@hpcuhe.cup.hp.com (Dennis Handly)
Date: Sat, 29 Aug 1992 06:15:40 GMT
Subject: Re: Shared libc and /lib/milli.a == problems ???
Organization: Hewlett-Packard Cal Language Lab
Newsgroups: comp.sys.hp

/ bartm@cv.ruu.nl (Bart Muyzer) /  3:50 am  Aug 27, 1992 /
>Today I encountered a problem with libc.sl and /lib/milli.a. One of our users
>tried to link a *very* large program and got "error code 138" from /bin/ld.

What was the message besides "error code 138"?  (if any)

>An hour of trying reveiled that:
>	* things went wrong when /lib/milli.a was referenced.
>	* One or two times ld complained:
>		Position Independent code not in library, don't use +z

I assume you used ld -v to get this information?

Anyway, I think that /lib/milli.a is just the fall-guy.  I.e. it is the last
library/object file that ld processes before the error.  There is probably
nothing wrong with it.

>Doing so created a working executable, although ld still complained about the
>Position Independent code thing.

I've seen this message too.  Except that I immediately knew what it meant
but couldn't figure out what object file had the problem.

Basically this is a message that is trying to do you a favor.  It only
occurs with ld -v.  Unfortunately it always occurs in milli.a?
(By binary searching and lding the objects in milli.a, it appears to be
in: Mcerror.o.) 

But if it occurs anywhere else you're suppose to not compile that module
with +z or +Z.
(These options should only be used in shared libraries and not in an a.out.)
But it is only a warning, not an error, so you can ignore it.

>Questions:
>1. Is this a bug? Should there maybe be a /lib/milli.sl?

No, the message doesn't indicate the bug.
Maybe.  I.e. if there was a shared version of milli.a it would be in
the kernel and be called external millicode.
(The Procedure Calling Convensions manual has some discussion about this.)

I don't work on ld, so someone else will have to tell you about the
real problem/cause behind error code 138.
From: ajs@hpfcso.FC.HP.COM (Alan Silverstein)
Date: Fri, 4 Sep 1992 19:00:15 GMT
Subject: Re: Help! seteuid/setegid on HP9000 720 / 8.07
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.sys.hp

> seteuid()/ setegid() calls are unresolved on my 9000 720.

I don't think they're in HP-UX.  Sure enough, no manual entries.  But
"man setuid" has a SEE ALSO to setresuid(2), and sure enough, it should
meet your needs.  Good luck.
Newsgroups: comp.sys.hp
From: shengj@acf3.nyu.edu (Jia Sheng)
Subject: Building X11R5 on HPUX6.5(HP9k/360)---Thanks!
Keywords: X11R5
Organization: New York University
Date: Fri, 28 Aug 1992 18:21:27 GMT

The X11R5 has been sucessfully built and running OK. I would like to thank
Terry J. Deveau, Bob Lenk, Donald Koch for their help. Special thanks to
Jim Andrea for his kindness and patience.

--
Jonathan J. Sheng
Theoretical Chemistry, NYU
(212)998-8439
From: jon@socrates.umd.edu (Jonathan Kruger)
Newsgroups: comp.sys.hp
Subject: Re: Unkillable processes
Date: 31 Aug 92 14:15:37 GMT
Organization: University of Maryland University College

When I had this problem and talked to the HP response center they told
me that processes in an "I/O wait" state would not respond to signals.

The way it seemed to happen on our system was when a dialed in user was
disconnected due to line noise while they were in the middle of doing a
file transfer or in the Korn Shell's edit mode.

As far as I know this bug has not been fixed - SR# 5003056507 (my very
first HP-UX bug report!).
-- 
Jonathan Kruger        jon@socrates.umd.edu         UNIX & VMS Systems Staff

"I bet one legend that keeps recurring throughout history, in every culture,
 is the story of Popeye."
Newsgroups: comp.sys.hp,alt.security
From: c0033013@ws.rz.tu-bs.de (Axel Brandes)
Subject: Re: Colour X display corrupted by console writes on HP 710
Organization: TU Braunschweig, Computer Centre (NAP), Germany.
Date: Sun, 30 Aug 1992 18:38:04 GMT


Hi!

In article <7371269@hpfcso.FC.HP.COM> brown@hpfcso.FC.HP.COM (John Brown) writes:
>   You might want to consider creating a "console" hpterm window, as in:
>
>   hpterm -C -name console
>
>   The -C option tells hpterm to become the console, the -name option is just
>   to let you know which hpterm is the console.  Then, any console messages 
>   will be sent to that hpterm window instead of the "real" console device.
>   This is fairly standard practice around here.

Okay, that it is we used to do so from the beginning of our work under
X and HP-UX.

But one detail is left: we use xdm instead of the raw console (or
vue). Is there a way to catch up output to the console with an
'invisible' object (similar to the visible one 'hpterm -C ...') ?
The crux is that we don't want to *see* something else than the
background and the xdm login window.

Thanks in advance,

Axel Brandes.
--
*=============================================================================*
Axel Brandes, RZ TU Braunschweig		  email c0033013@ws.rz.tu-bs.de
D-3300 Braunschweig, Germany			  phone 0531-391-5538   (voice)
From: hardy@golem.ps.uci.edu (Meinhard E. Mayer (Hardy))
Subject: HP CD-ROM
Newsgroups: comp.sys.hp
Organization: Department of Physics, UC Irvine, CA 92717-4575, USA
Date: 27 Aug 92 06:27:07 GMT

Does anyone on the net know whether the HP CD-ROM player can be used
with SGI-machines? I have colleagues who have both HP 9000/720-s and
an SGI station and we are palnning on sharing a CD-ROM drive. 
--
Hardy 
-----
Meinhard E. Mayer,  Department of Physics, UC Irvine 
e-mail: hardy@golem.ps.uci.edu (preferred) or MMAYER@UCI.BITNET

Newsgroups: comp.sys.hp
From: Steinar.Haug@delab.sintef.no (Steinar Haug)
Subject: Re: Sun Vs. HP system administration
Organization: SINTEF DELAB, Trondheim, Norway.
Date: 26 Aug 92 16:11:18

In article <1992Aug26.052741.24845@spatial.com> alek@spatial.com writes:
>>* Can I set up my HP as a client of Solbourne (yellow pages) ?
>>  I think the answer is YES but how hard is it to get this
>>  setup working.
>Yes - see /etc/netnfsrc - it's pretty trivial. BTW, all of my YP/NIS Slaves
>are Suns, so I've only test the YP client side of the HP's.

We have used 9000/400 running 8.0 (and earlier 7.05) as YP/NIS slave servers.
Seems to work just fine, but there are security problems:

1. HP's YP implementation doesn't have (the equivalent of) the latest security
patch from Sun (100482-02). Thus anybody who can guess your YP domainname can
dump your passwd map, and find your passwords (by using crack or similar
programs) at their leisure. Sun's patch enables you to control which hosts
(which IP addresses) are allowed to access your YP servers.

2. As far as I know HP hasn't picked up Sun's ypbind modifications. This means
that the ypbind process on your HP systems can be made to rebind to another
YP server *from the outside* (somebody out in the big IP world doing an RPC
call to your ypbind process). ypbind on Suns (as of around SunOS 4.1 or so)
will refuse this - unless explicitly allowed through startup options.

So, because of point 1 above, we have shut down all our HP slave servers,
and now use only Suns as YP servers.

I must admit that I'm really looking forward to HP-UX 9.0, in the hopes that
HP will have addressed at least some of these problems...

Steinar Haug, system/networks administrator
SINTEF DELAB, University of Trondheim, NORWAY
Email: Steinar.Haug@delab.sintef.no, 
	sthaug@idt.unit.no, steinar@tosca.er.sintef.no
Newsgroups: comp.sys.hp
From: chris@rz.uni-karlsruhe.de (Christian Finger)
Subject: Re: Tcsh/term wierdness during login from Sun
Keywords: tcsh 6.01.00 hpux termcap sun
Reply-To: finger@rz.uni-karlsruhe.de
Organization: Computer Center, University of Karlsruhe, Germany
Date: Fri, 4 Sep 1992 16:31:50 GMT

In article <1992Sep3.165210.3154@tamsun.tamu.edu>, greg@omnivore.tamu.edu (Greg Economides) writes:
| I am having problems using tcsh 6.01.00 on an HP 9000/720 using hpux
| 8.07.  The problem is related to the term shell variable and /etc/termcap.
| 
| When I log in to the HP from a Sun (telnet, rlogin) tcsh locks up when the
| term variable is "sun-cmd".  It does not lock up if term is "sun".  When I
| say "locks up" I mean that I do not get a command prompt and am also not able
| to 'intr' (control-C) or suspend the process from the keyboard.
| 
| I have already placed the termcap entries for "sun" and "sun-cmd" in the
| HP's /etc/termcap.  
       ^^^^^^^^^^^^
| 
| Any hints or suggestions?
| 
| Peace,
| --
| Greg Economides,   Systems Administrator, Center for Biosystems Modelling
| Texas A&M University
| Internet: econ@tamu.edu
| Fuzzy logic -- "Everything is not always something"

You may have a look at the first lines of /etc/termcap:

# @(#) $Revision: 37.1 $

# Important:
#       This file is here only for compatibility purposes.
#       It is not referenced by the curses(3X) library routines,
#       the termcap(3X) emulation routines, or the terminfo routines.
#       Instead of /etc/termcap these routines use the terminfo(5)
#       terminal data base under /usr/lib/terminfo.

Try putting a file named sun-cmd in /usr/lib/terminfo/s.

Christian
-- 
  .     Christian Finger         |  Tel   : (+49) 721/608-4038
 |||    Computer Center          |  Fax   : (+49) 721/32550
\|||    University of Karlsruhe  |  EMail : finger@rz.uni-karlsruhe.de
    /   Postfach 6980            |  X.400 : S = finger; OU = rz
        D-7500 Karlsruhe 1       |          P = uni-karlsruhe; A = dpb; C = de
From: stuart@TIVOLI.COM (Stuart Jarriel)
Newsgroups: comp.sys.hp
Subject: Re: HPView Icon Labels: Meaningful text?
Date: 27 Aug 92 23:25:53 GMT
Organization: Tivoli Systems, Inc

This program can set the title bar and icon label on any running 
hpterm or xterm.

#include <stdio.h>
#include <stdlib.h>
#include <string.h>

#define ESC '\033'
#define BEL '\007'
#define STRING_MAX_LEN 200

main(argc,argv)
int argc;
char **argv;
{
  int len, i;
  char *buffer;
  char *term;

/* you must have one word as a title */
  if (argc < 2) exit(1);

/* if X is running, WINDOWID will be set */
  if (strlen(getenv("WINDOWID")) == 0) exit(0);

/* lets make room for a BIG name */
  if ((buffer = malloc(STRING_MAX_LEN)) == NULL) exit(0);

  for (i=1; i<= argc; i++)  {
    if ((strlen(buffer) + strlen(argv[i])) > STRING_MAX_LEN) {
      perror("window title too long");
      exit(1);
    }
    buffer = strcat(buffer,argv[i]);
    buffer = strcat(buffer," ");
  }

  len = strlen(buffer);

/* If there is no term environment set ... */

  if ((term = getenv("TERM")) == NULL) exit(0);

/*  This sequence if term has 'hp' in it */

  if (strstr(term,"hp") != NULL) {
    printf("%c&f0k%dD%s",ESC,len,buffer);
    printf("%c&f-1k%dD%s",ESC,len,buffer);
  }

/*  This sequence if term is an xterm or vt100 */
  
  if (strstr(term,"xterm") != NULL) {
/* sets window then icon */
/*  printf("%c]2;%s%c",ESC,buffer,BEL);
    printf("%c]2;%s%c",ESC,buffer,BEL);  */

/* sets BOTH at the same time */
    printf("%c]0;%s%c",ESC,buffer,BEL);
  }
}
Newsgroups: comp.sys.hp
From: chris@rz.uni-karlsruhe.de (Christian Finger)
Subject: EISA expander / 730 vs. 750
Reply-To: finger@rz.uni-karlsruhe.de
Organization: Computer Center, University of Karlsruhe, Germany
Date: Fri, 28 Aug 1992 18:57:51 GMT

I'm looking for an EISA expander for an hp730. I'm especially interested
in infos about the performance (a card using the expander vs. a card in the 
original slot).

There was a thread about this in february this year, but there were only rumors 
about Danford Corporation developing such a beast.

Btw, are there any other differences between an hp730 and an hp750 other
than cache size, no. of EISA slots and the price?

Any infos are appreciated,
	C.Finger


-- 
  .     Christian Finger         |   SMTP:
 |||    Computer Center          |   finger@rz.uni-karlsruhe.de
\|||    University of Karlsruhe  |   X.400:
    /   Am Zirkel 2              |   S = finger; OU = rz
        D-7500 Karlsruhe 1       |   P = uni-karlsruhe; A = dpb; C = de
From: ak10+@andrew.cmu.edu (Andrew Joseph Kompanek)
Newsgroups: comp.sys.hp
Subject: "script" broken in HP-UX 8.07??
Date: 25 Aug 92 13:57:35 GMT
Article-I.D.: andrew.4eaenDK00WB4AvP0gq
Organization: Carnegie Mellon, Pittsburgh, PA

I recently updated an HP 9000 720 to HP-UX 8.07 from 8.05.  The program
"script" (which simply logs terminal output to a file) no longer works:

I get the starting message "Script started, file is <foo>"
and then it immediately dies with the message
                   "Script done due to signal 10, file is <foo>"

Where could this signal be coming from?

Any advice,
Drew
Andrew Kompanek
Dept of Human Genetics
University of Pittsburgh
e-mail: drew@chimera.hgen.pitt.edu, ak10@andrew.cmu.edu
Newsgroups: comp.sys.hp
From: fred@cv.ruu.nl (Fred Appelman)
Subject: Re: Dumping an HP 900/710 X11 window on an HP Laserjet IIP
Date: Tue, 25 Aug 1992 17:50:46 GMT
Organization: University of Utrecht, 3D Computer Vision Research Group
Keywords: xwd, xpr, lp

In <1992Aug25.145159.25119@cenaath.cena.dgac.fr> melennec@stna.dgac.fr (Ronan Melennec) writes:
> The command :
> xwd | xpr -device ljet -density 300 | lp -dlw
> only has the printer print "Line too long"...

Shouldn't you set "lp" in raw mode. Something like "lp -dlw -o raw". I think
that should help.

	Fred
From: versloot@rwzl01.zld.rws.nl (Jack versloot)
Newsgroups: comp.sys.hp
Subject: Help wanted on hpterm
Keywords: X, hpterm
Date: 4 Sep 92 08:37:39 GMT
Organization: Dutch Min. of transport Zeeland, Middelburg


Help wanted on the following problem.

First some information:
Language: FORTRAN
Machine : HP9000
Terminal: hp

I have a program doing the following:
   - set up protected fields on the terminal
   - let the user enter some data in these fields
   - reading lines from the terminal (with the entered information) with:
        READ (*, '(A)') line

To read lines ESCd is sent to the terminal. The character*512 variable
line is searched for ESC[ (begin protected field) and ESC] (end
protected field). All information between these two codes will be the
information entered by the user.

This works FINE for a real hp-terminal. On a X-window with hpterm it
doesn't work however! The last field on each line is misformed: the
code for 'end protected field' is missing.

My question: 
   Why?
and more important:
   What can I do about it?

Is hpterm not completely compatible with a hp-terminal or should I (maybe)
give hpterm some options or what?

If you have the answer please send it by E-mail to the
following address:

             ingen@rwzl01.zld.rws.nl
Newsgroups: comp.sys.hp
From: rusty@wyle.wyle.ingr.com (Rusty Wiginton)
Subject: What is the 7xx series compatible with ?
Organization: Intergraph Corporation, Huntsville, AL.
Date: Wed, 26 Aug 1992 23:31:48 GMT

The way I understand it from the Tech Support people at HP, there is a
switch you can set to make the 700 binary compatible with the 800 and
visa-versa. I'm not sure about the others however. Check the FAQ and TFM.

-- 
                                      Rusty Wiginton (205)730-7567 
                                      (UUCP) uunet!ingr!b17a!rusty
                                      (Internet)rusty@b17a.ingr.com
From: njconway@ccvax.ucd.ie
Newsgroups: comp.sys.hp
Subject: odump - we don't got it
Date: 31 Aug 92 10:42:21 GMT
Organization: University College Dublin

In article <31480235@hpcuhe.cup.hp.com>, shoe@hpcuhe.cup.hp.com (Jim Schumacher) writes:
> 
> As far as telling whether an archive library contains object files
> that are PA1.1, there is an unsupported tool in the contrib fileset
> called odump that comes in handy. odump -u for usage:
> 
> ...
>
> jim shoe

I asked another 700 user in our building and he said he also had odump in
the /usr/contrib/bin directory, but we ain't got nuttin in /usr/contrib at
all...

(Feeling cheated ;)

Should we have it (we started with 8.07, he with 8.05), or failing that, is
it ftp-able, and (even) worthwhile fetching ?

:)

Neil
njconway@ccvax.ucd.ie
neil@nebula.ucd.ie

Newsgroups: comp.sys.hp
From: fred@cv.ruu.nl (Fred Appelman)
Subject: Re: What is the 7xx series compatible with ?
Date: Wed, 26 Aug 1992 19:14:56 GMT
Organization: University of Utrecht, 3D Computer Vision Research Group

In <BtLKwt.HG5@news.cso.uiuc.edu> e-sink@uiuc.edu (Eric W. Sink) writes:

>If I compile binaries on my 720, HPUX 8.07, will they run on any
>other series of the HP 9000 ?  For example, I have heard of Series
>800, series 400, series 300, etc...  What am I compatible with, in
>theory ?

300 and 400 series use 68030/68040 code and are binary compatible.
The 800 and 700 can be compatible. The 800 code always runs on a 700,
the 700 code only runs on a 800 if you have the compiler generate
PA1.0 code. 

	Fred
Xref: sparky comp.sys.hp:9656 comp.lang.fortran:3145