HDTenEightyP/NetNews huggingface dataset:
Date: Sat, 11 Apr 92 17:18:34 MDT
Organization: Brigham Young University, Provo UT USA
In-reply-to: datri@convex.com's message of 11 Apr 92 19:18:44 GMT
	<1992Apr11.191844.29556@news.eng.convex.com>
Reply-To: gritton@byu.edu

datri@convex.com (Anthony A. Datri) writes:

>>I heard that one can patch up the kernel to allow root to 
>>access mounted file systems as 'root' and not 'nobody'.

>You're begging to lose by doing that.  If you really want to do your backups
>across NFS like that, just add root=foo:bar to /etc/exports on the remote
>machine.  Check the man page for exports(5).

Not on HP. HP-UX still has the old NFS code that, among other things, doesn't
provide for individual-host root access. Also, there is no man page for
exports(5). On HP-UX, it's exports(4) :-)
--
James Gritton - gritton@byu.edu - I disclaim
From: oursler@kenyon.edu
Newsgroups: comp.sys.hp
Subject: HP92221M Wiring diagram wanted
Date: 14 Apr 92 19:04:47 GMT
Article-I.D.: kenyon.1992Apr14.140447.37
Organization: Kenyon College

Hiya,

	Like it says in the subject line, I'm looking for a wiring diagram
	of an HP92221M cable.  Used in this case for connecting an HP
	Portable plus to a modem. 

	I'd really appreciate any info anyone can give me.  Heck, I'll
	snail mail a snicker's bar to anyone who can provide me with the
	answer.  Void where prohibited, Not to exceed the amount of my 
	lunch money ;-)

	e-mail to oursler@kenyon.edu

	Thanks 1x10^6

						- Miles -

	-------------------------------
	Miles Oursler
	Manager of Networks and Systems
	Kenyon College
	oursler@vax001.kenyon.edu
	(614) 427-5696
	-------------------------------
From: campbelr@hpcuhe.cup.hp.com (Bob Campbell)
Date: Mon, 13 Apr 1992 21:27:52 GMT
Subject: Re: Re: VUE window appearance and bells/whistles.
Organization: Hewlett Packard, Cupertino
Newsgroups: comp.sys.hp

> I've gotten out of this in the past by re-booting.  Is there something
> less catastrophic I can do to get new hpterm windows to use the
> correct set of defaults?

Check out the man page for the xrdb command.

---------------------------------------------------------------------------
Bob Campbell                Some times I wish that I could stop you from
campbelr@cup.hp.com         talking, when I hear the silly things you say.
Hewlett Packard                                    - Elvis Costello
From: bock@pollux.usc.edu (Gene Bock)
Newsgroups: comp.sys.hp
Subject: Help from Iris Users running on HP
Date: 14 Apr 92 07:36:26 GMT
Article-I.D.: pollux.kumk2qINN7ip
Distribution: world
Organization: University of Southern California, Los Angeles, CA
NNTP-Posting-Host: pollux.usc.edu

I am using Iris, prototype object-oriented DBMS developed at HP lab and
Iris is now running HP 9000/700 720. I am creating various sizes of
databases using Iris, say, 1000 instances, 5000 instances, 10000 instances,
and so on and each instance is about 500 bytes. Problem is that 
if I create more than about 10000 instances, Iris just crashes and produces
"Broken Pipe" error message. Question is how I can fix this problem?
Any comment will be appreciated and I would like to talk to people
who have had similar problem.

THanks in advance -- Gene

email address:   bock@pollux.usc.edu
From: tml@tik.vtt.fi (Tor Lillqvist)
Newsgroups: comp.sys.hp
Subject: Re: GNU Emacs interface to xdb
Date: 6 Apr 92 23:18:15 GMT
Organization: Technical Research Centre of Finland, Laboratory for Information
	Processing (VTT/TIK)
In-reply-to: tml@tik.vtt.fi's message of 5 Apr 92 20:13:28 GMT

Here is a first patch: Without this, some xdb output would be dropped.

*** 1.1	1992/04/05 12:04:57
--- 1.2	1992/04/06 12:53:47
***************
*** 1,5 ****
  ;; Run xdb (the HP-UX proprietary debugger) under Emacs 
! ;; $Id: xdb.el,v 1.1 1992/04/05 12:04:57 tml Exp $
  ;; Copyright (C) 1988 Free Software Foundation, Inc.
  ;; Copyright (C) 1992 Tor Lillqvist
  
--- 1,5 ----
  ;; Run xdb (the HP-UX proprietary debugger) under Emacs 
! ;; $Id: xdb.el,v 1.2 1992/04/06 12:53:47 tml Exp $
  ;; Copyright (C) 1988 Free Software Foundation, Inc.
  ;; Copyright (C) 1992 Tor Lillqvist
  
***************
*** 67,72 ****
--- 67,73 ----
  ;; appears in the output.
  
  (require 'shell)
+ (provide 'xdb)
  
  (defvar xdb-prompt-pattern "^>"
    "A regexp to recognize the prompt for xdb.") 
***************
*** 216,221 ****
--- 217,223 ----
  	(if (fboundp func)
  	    (eval (list func proc (substring string (match-beginning 2)
  					     (match-end 2)))))
+ 	(xdb-filter-insert proc (substring string 0 beg))
  	(setq string (substring string (1+ end)))))
      (if beg
  	(setq xdb-filter-accumulator (substring string beg)
--
Tor Lillqvist,
working, but not speaking, for the Technical Research Centre of Finland
From: shinn@agsm.ucla.edu (Shinn-Tzong Wu)
Newsgroups: comp.sys.hp
Subject: Fortran lib?
Date: 13 Apr 92 23:41:46 GMT
Organization: UCLA, Department of Psychology, Drug Abuse Research Center

Sorry to post here, but I could not get mail to Mr. Bob Montgomery (mail
log shown below).  I just wonder where is the libhppa located since I
could not ld it?


  --- The transcript of the session follows ---
421 hpfcmr.fc.hp.com.tcp... Deferred: Connection timed out during user open with hpfcmr.fc.hp.com

  --- The unsent message follows ---
Received: by shin.sscnet.ucla.edu (AIX 3.1/UCB 5.61/4.03)
          id AA06393; Tue, 7 Apr 92 12:07:01 -0700
From: shinn (Shinn-Tzong Wu)
Message-Id: <9204071907.AA06393@shin.sscnet.ucla.edu>
Subject: Re: FORTRAN problem
To: bobm@hpfcmr.fc.hp.com (Bob Montgomery)
Date: Tue, 7 Apr 92 12:07:00 PDT
X-Mailer: ELM [version 2.3 PL0]

Thanks for the response, I read it from sys.hp and I will try it later
and let you know that we will do.  I didn't write that code (just to
port it to different systems) so it would be pretty hard for me to
trace all the passing of the working array (the real*4 space was
created by malloc in C and then passed to Fortran etc)....

Shinn
From: michael@resonex.com (Michael Bryan)
Newsgroups: comp.sys.hp
Subject: Re: Problems with SLIP (PPL) on 385, HPUX 8.0
Date: 15 Apr 92 08:36:16 GMT
Organization: Resonex Inc., Sunnyvale CA

In article <JEFF.92Apr10081114@dsndata.uucp> jeff@dsndata.uucp (Jeff Minnig) writes:
>In article <1992Apr9.162027.8012@resonex.com> michael@resonex.com (Michael Bryan) writes:
[Regarding problems with crashes and network failures using SLIP]
>> the wrath of irate users, and tried the same test again.  This time,
>> there was no panic, but at the exact time that ppl exited, the network
>> went down.
>
>We tried something very similar after installing 8.0 on a 385 late
>last year.   I had two telebits connected and tried to invoke
>ppl and the entire cluster quit working....  I think that the 
>IP code in the kernel had a self-inflicted lobotomy over something
>that SLIP (ppp) was trying to do....

Well, I found my problem, anyway.  The IP network address for both the
local and the remote host must be the same, and must be different from
any other network attached to the systems.  In my case, our HP is on
an internal network with an address of 89.x.x.x.  I setup the remote
site to use a SLIP address of 90.0.0.1, but just used our normal host
name for the local host.  Errnt.  Once I created an additional entry
in the host file with an address of 90.0.0.2, and used that name as the
local host, things started working fine.  It also worked if I put a
list of 90.x.x.x addresses in /usr/lib/ppl/ppl.ipool.

In retrospect, it makes perfect sense, and I should have done this in
the first place.  Having never setup SLIP before, though, I was just
following the manual, and it made no explicit mention of what
conditions were placed on the IP addresses.  So when it said use the
local hostname, I did.  :-/ Silly me.  I was at least smart enough to
realize that the remote host would need a different IP network number,
I don't know why I didn't think about the other side too!

At least it's solved, and perhaps this can help others, too.
-- 
Michael Bryan	        michael@resonex.com
"This isn't an argument, you're just contradicting me!"  "No I'm not."
From: werner@freya.inesc.pt (Werner Hans Peter Vogels)
Newsgroups: comp.sys.hp
Subject: 3rd part disk on a HP710
Date: 9 Apr 92 14:37:04 GMT
Organization: INESC - Instituto de Engenharia de Sistemas e Computadores, Lisboa, Portugal

We are planning to buy 4 710's but do not want to pay the ridiculous price for
HP 1.3 GB disk so we were thinking about hooking two 660 Mb maxtors to it, does
anybody have any experience with this? These two disks will be the only disks connected
to the machine (we buy them diskless ...).

Thanks a lot!!

-- 
Werner Vogels

INESC - Distributed Systems and Industrial Automation Group
        Tel: +351 1 3155150 ext 280, Fax: +351 1 525843
	e-mail: werner@inesc.pt / C=pt;A= ;P=inesc;S=werner
From: thad@btr.BTR.COM (Thaddeus P. Floryan)
Newsgroups: comp.sys.hp
Subject: Re: scsi & HP
Date: 9 Apr 92 12:28:47 GMT
Organization: BTR Public Access UNIX, Mountain View CA

In article <67870124@hpcupt1.cup.hp.com> chugins@hpcupt1.cup.hp.com (Chris Hugins) writes:
>NOTE to you 9754xx HP OEM'd disk users out there.  These disks have
>[...]
>which are sold to the OEM market.  One such requirement is for powerfail
>recovery.

Would you please describe (technically) what you meant by "powerfail recovery"?

Is that anything different from running one's system(s) on "smart" UPS or SPS
systems which can inform the host(s) to initiate a clean shutdown as necessary?

My own tests (on the 97549 disks) have indicated they're MUCH better than most
of the HDs (from other mfrs) "out there", and your comment about them not being
"qualified" by H-P is unsettling.

Of course, I do religiously perform daily and full backups no matter WHOSE HDs
I have on my systems!  :-)

Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]
Newsgroups: comp.sys.hp
From: franl@centerline.com (Fran Litterio)
Subject: xdb's disassembly mode.
Organization: CenterLine Software, Inc.
Date: Mon, 6 Apr 1992 19:31:30 GMT

This is a sample of the appearance of xdb's disassembly mode under
HP-UX 8.07 on a 720:

        0x0009c1cc   signal_n        STW     26,-36(0,30)
 > 121: 0x0009c1d0   signal_n+0004   LDW     -36(0,30),20
        0x0009c1d4   signal_n+0008   COMIBF,<=,N     1,20,signal_name+0044
        0x0009c1d8   signal_n+000c   OR      0,0,0
        0x0009c1dc   signal_n+0010   LDW     -36(0,30),21
        0x0009c1e0   signal_n+0014   LDO     31(0),22

Is there any way to make xdb show more than just the first 8
characters of the function name?
--
franl@centerline.com   || Fran Litterio                               
uunet!centerline!franl || CenterLine Software R&D                     
617-498-3255           || 10 Fawcett St, Cambridge, MA, USA 02138-1110
From: curt@oce.orst.edu (Curt Vandetta)
Newsgroups: comp.sys.hp
Subject: re: NFS and root
Date: 14 Apr 92 18:21:11 GMT
Article-I.D.: talon.1992Apr14.182111.166
Organization: Oregon State University, College of Oceanography


  Sorry for replying to this news group but with one stroke of the key
  I lost the news article I was replying too.

  It was brought to my attention the domain OS doesn't have dump/rdump.
  A very good reason for not using them.  I didn't mean to enfer by my
  previous posting that backup's over NFS were no good.  They are just
  more difficult than they need to be.  Also to respond to the comment
  that you can't afford to bring the machines down to back them up.  I
  understand, I do nightly backups with dump/rdump and do not bring the
  machines down.  I only bring the machines down for level 0 dumps.  Which
  I do about once every 6 months.  Once every month I do an incremental
  dump at level 2, every week I do an incremental dump at level 4, and
  every night I do an incremental dump at level 6.  A couple a shell
  scripts and cron and all I have to do is remember to put the tapes in
  the dat.

  I've tried HP's fbackup and frecover, found that they didn't provide
  the same level of functionality I can get with the system I described
  above.

  Curt
--------------------------------------------------------------------------

  Curt Vandetta				College of Oceanography
  curt@oce.orst.edu			Oregon State University

--------------------------------------------------------------------------
  "Since I have no more sick days, I'm calling in dead today"
--------------------------------------------------------------------------
From: dhandly@hpcuhe.cup.hp.com (Dennis Handly)
Date: Tue, 14 Apr 1992 10:21:00 GMT
Subject: Re: problem with XDB
Organization: Hewlett-Packard Cal Language Lab
Newsgroups: comp.sys.hp

/ steve-t@hpfcso.FC.HP.COM (Steve Taylor) / 10:44 am  Apr  8, 1992 /

>If this is a PA-RISC system, it's possible the assignment doesn't get 
>completed until the first instruction of line 418.

This type of problem should have been fixed before customers got it, on
HP-UX 8.0?

It will occur on MPE/iX 4.0, if you are using Toolset to debug, and have
a procedure call as the first statement of a procedure and it has no
parameters.
From: alech@hpindda.cup.hp.com (Alec Henderson)
Date: Tue, 14 Apr 1992 21:30:44 GMT
Subject: Re: looking after streams accounting command / HPUX
Organization: HP Information Networks, Cupertino, CA
Newsgroups: comp.sys.hp

Annie Tanguy writes:

>	I am new to HP. For a specific client, but for my curiousity too,
>	I would like to know the command I must type to see whether there
>	are failures in the streams buffers allocation.

Annie,

STREAMS is not part of HP-UX 7.0x or 8.Ox.  HP will be providing STREAMS
(as a separate product) on top of a new HP-UX release later this year.  Have
your HP sales rep contact me directly if you need more details.

Regards,
Alec Henderson

Telephone: T/408-447-3965			Hewlett-Packard
FAX:       408-447-3660				Information Networks Division
E-mail:    alech@cup.hp.com	        	19420 Homestead Road MS 43L9
HPDesk:    Alec Henderson/HP6600/1B		Cupertino, CA  95014  (USA)
Newsgroups: comp.sys.hp
From: alanm@trin.edu (Alan McCain)
Date: Tue, 7 Apr 92 21:43:03 GMT
Subject: emacs for HP
Organization: Trinity Divinity School and Trinity College
Keywords: emacs

Can someone tell me where I might be able to ftp the HP-enhanced version of
emacs?  

Thanks,

Alan
-- 
  Alan McCain                                        UUCP: trinity!alanm
  Systems Administrator                              Internet: alanm@trin.edu 
  Trinity College and Divinity School
  2065 Half Day Rd.
  Deerfield, IL  60015
  (708) 317-8173
Xref: sparky comp.sys.hp:5003 comp.dcom.modems:6314
From: bartm@cv.ruu.nl (Bart Muyzer)
Newsgroups: comp.sys.hp,comp.dcom.modems
Subject: Re: Setup for V42bis/NMP5 on HP9000/835???
Keywords: HP 9000/835, Tornado 9600 modem
Date: 7 Apr 92 13:29:39 GMT
Organization: University of Utrecht, 3D Computer Vision Research Group
Originator: bartm@mind.cv.ruu.nl

In <1992Apr6.141203.5940@cv.ruu.nl> I wrote:

>Hi,
>
>I'm trying to get NMP 5/V42bis working between modems and I'm not sure how to
>setup things.
[... and references to  NMP5 MNP5 SMP5 ...]
What I'm trying to say is: MNP5. That's the only good abbreviation.
Sorry for any confusion,

>Please reply by e-mail to 'bartm@cv.ruu.nl' or by posting in this group. Thank
>you all in advance,

							>] Bartm [<
-- 
Bart Muyzer, Systems and Network Administrator, [NIC-Whois handle: BJM9]
     3D Computer Vision, Room E02.222, University Hospital Utrecht,
     Heidelberglaan 100, 3584 CX Utrecht, Holland. E-mail: bartm@cv.ruu.nl
     Fax: +31-30-513399. Tel: +31-30-506711 (w), +31-3402-52157 (h). 
Newsgroups: comp.sys.hp
From: moconnor@pms704.pms.ford.com (Mike O'Connor)
Subject: Re: HP Suggestions
X-Disclaimer: Not an official spokesperson for Ford Motor Co.
Reply-To: Mike O'Connor <mjo@fmsrl7.srl.ford.com>
Organization: "Fordz"
Date: Sun, 5 Apr 1992 19:58:28 GMT

In article <rivs3INNfhe@agate.berkeley.edu>
smoot@roger-rabbit.cs.berkeley.edu (Stephen [Steve] R Smoot) writes:

:What is the net address to send HP suggestions about how to improve their
:future systems?  is there one?

I'd try comp-sys-hp@ucbvax.berkeley.edu.  :)



-- 
 Mike O'Connor                     |  Ford Motor Company, USA
 Applications Systems Analyst      |  CPD P&MS ECC Core Software
 Phone #:  +1 (313) 390-4008       |  P.O. Box 2053, ECC MD-7
 Fax #:    +1 (313) 845-0576       |  Dearborn, MI  48121-2053
From: ajs@hpfcso.FC.HP.COM (Alan Silverstein)
Newsgroups: comp.sys.hp
Subject: Re: Where are lex and yacc? (hpux 8.02/9000/827)
Date: 16 Apr 92 20:29:21 GMT
Organization: Hewlett-Packard, Fort Collins, CO, USA

> Are lex and yacc available on HP-UX systems...

Apparently so.  I found them in the C-TOOLS fileset on one S300 system
in our lab.  I don't know if they cost extra but I bet not.
From: ajs@hpfcso.FC.HP.COM (Alan Silverstein)
Newsgroups: comp.sys.hp
Subject: Re: Examine core files
Date: 14 Apr 92 20:22:56 GMT
Article-I.D.: hpfcso.7370872
Organization: Hewlett-Packard, Fort Collins, CO, USA

> Since HP's "file" command neither recognizes core files nor tells which
> program the core is from...

Nice idea.  I submitted it internally as an enhancement request.  No
promises.
Newsgroups: comp.sys.hp
From: franl@centerline.com (Fran Litterio)
Subject: Re: window resize automatically changes environment?
Organization: CenterLine Software, Inc.
	<1992Apr7.173320.13873@cupnews0.cup.hp.com>
Date: Tue, 7 Apr 1992 21:11:45 GMT

In article <1992Apr7.173320.13873@cupnews0.cup.hp.com> ld@cup.hp.com (Larry Dwyer) writes:

> >                           Why mix the old (LINES/COLUMNS) and new
> > (SIGWINCH/TIOCGWINSZ) functionality in a single application?
> 
> Not everyone has an X display, so, the TERM variable is still needed.

Yes, TERM is needed, but not LINES and COLUMNS.  Applications that
need to know the size of the terminal at startup time can use terminfo
or curses.  Later SIGWINCH/TIOCGWINSZ is all that's needed.  Vi under
BSD is a good example of this.

> If one were running X with an <arbitrary size> window and did a telnet
> to another system, how would vi know what size to set it's window?  It
> cannot ioctl() the connection through which the telnet is established
> to determine the window size, so, it uses LINES/COLUMNS.

Yes, but that's a limitation of the telnet protocol.  Note that
rlogin's use of pseudo-terminals to implement network-transparency
allows the TIOCGWINSZ ioctl() to work across an rlogin connection.
--
franl@centerline.com   || Fran Litterio                               
uunet!centerline!franl || CenterLine Software R&D                     
617-498-3255           || 10 Fawcett St, Cambridge, MA, USA 02138-1110
From: pbm@hpfcso.FC.HP.COM (Peter McLain)
Date: Tue, 7 Apr 1992 15:20:12 GMT
Subject: Re: window resize automatically changes environment?
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.sys.hp


> I'm still curious: Why mix the old functionality (LINES/COLUMNS) and new
> functionality (SIGWINCH/TIOCGWINSZ) in a single application?  Why not 
> ignore LINES and COLUMNS in favor of the size as reported by the TIOCGWINSZ
> ioctl()?

    I haven't kept up with POSIX for the last couple of months, but the
    last draft of the UPE that I read required vi and more to use the values
    of LINES and COLUMNS if they were set.

Peter McLain
pbm@hpfclj.fc.hp.com
Newsgroups: comp.sys.hp
From: franl@centerline.com (Fran Litterio)
Subject: Re: window resize automatically changes environment?
Organization: CenterLine Software, Inc.
Date: Mon, 6 Apr 1992 18:54:23 GMT

In article <17780156@hpfcmgw.FC.HP.COM> chan@hpfcmgw.FC.HP.COM (Chan Benson) writes:

> > franl@centerline.com (Fran Litterio) writes:
> >
> > Yes, but how bogus that vi (and presumeably the other utilities you
> > mention) performs the TIOCGWINSZ ioctl() to get the terminal size
> > _only_ when it receives SIGWINCH, and not at startup time!  If the
> > LINES and COLUMNS environment variables are not set (or not set
> > correctly) vi mis-draws the screen.  You have to resize the window to
> > make vi notice its size.  Why mix the old (LINES/COLUMNS) and new
> > (SIGWINCH/TIOCGWINSZ) functionality in a single application?
> > 
> > And I thought I could finally do away with all use of LINES, COLUMNS,
> > and /usr/bin/X11/resize on my 8.07 machines.  Sigh.
> 
> You'll have to describe how you invoke vi to produce this problem. Given
> that the shells all respond to SIGWINCH by setting LINES and COLUMNS and that
> hpterm makes sure they get set if you're using the -e option, I'm having
> a hard time figuring out how to duplicate your problem.

In either an hpterm or xterm having more than 20 lines, type this
(pardon the Bourne/Korn-ism):

	$ LINES=20 /usr/bin/vi somefile

In either an hpterm or xterm having more than 24 lines (vi's default),
type this:

	$ unset LINES
	$ /usr/bin/vi somefile

Then resize the window vertically and watch vi do the right thing upon
receiving the SIGWINCH.

> Could you do me a personal favor and make your future postings a little 
> less hostile and a little more informative? I can't tell if you just want
> to complain or if you actually would like some assistance.

I didn't mean to sound hostile.  Sorry.  I'm still curious: Why mix
the old functionality (LINES/COLUMNS) and new functionality
(SIGWINCH/TIOCGWINSZ) in a single application?  Why not ignore LINES
and COLUMNS in favor of the size as reported by the TIOCGWINSZ ioctl()?

All the shells respond to SIGWINCH by resetting LINES and COLUMNS, but
only if they are already set.  If LINES and COLUMNS are ever manually
unset, the shells do not set them on a SIGWINCH.  If LINES and COLUMNS
are ever manually set to incorrect values, and an application like vi
is started without first resizing the window, then we see the above
strange behavior.  I would caution against holding the point of view
that the shells solve the problem by catching SIGWINCH.  If I ran into
the problem, I think others will too.
--
franl@centerline.com   || Fran Litterio                               
uunet!centerline!franl || CenterLine Software R&D                     
617-498-3255           || 10 Fawcett St, Cambridge, MA, USA 02138-1110
Newsgroups: comp.sys.hp
From: franl@centerline.com (Fran Litterio)
Subject: PA-RISC assembly language question.
Organization: CenterLine Software, Inc.
Date: Wed, 8 Apr 1992 23:16:11 GMT

According to HP 700 "Assembly Language Reference Manual", section
"Registers and Register Mnemonics":

    In addition, there is a special register mnemonic defined as %previous_sp
    that allows access to the previous value of the stack pointer.  This
    should be used in the position a base register would ordinarily be used.

I can't figure out how to use the %previous_sp mnemonic in an assembly
language function.  Of all the methods I tried only this one assembled
without a syntax error, but I'm not sure it does what I want, namely
to save the old SP value into the location referenced by -4(%r30):

	#include <soft_reg.h>
	...
	my_function
		.proc
		.callinfo	frame=64,calls,save_sp,save_rp
		.enter
		ldo	0(previous_sp),%r22
		stw	%r22,-4(%r30)
		ldo	-1(%r0),%r28	; Return -1 for now.
		.leave
		.procend

I also don't understand why the documentation calls it "%previous_sp"
but /usr/include/soft_reg.h defines only "previous_sp".  The 700
assembler does not accept "%previous_sp".
--
franl@centerline.com   || Fran Litterio                               
uunet!centerline!franl || CenterLine Software R&D                     
617-498-3255           || 10 Fawcett St, Cambridge, MA, USA 02138-1110
Newsgroups: comp.sys.hp
From: toma@db.TC.Cornell.EDU (Rory Toma)
Subject: HP 9000/7xx advice sought
Organization: Not bloody likely around here!
Distribution: comp.sys.hp
Date: Tue, 14 Apr 1992 01:31:11 GMT

I have some questions regarding the HP/Apollo 9000/7xx series.

Does emacs, gcc, g++ etc. compile and run fine?
Have there been problems using 3rd party drives?
How do they function in a mixed (Sun & HP) environment?
How does I/O (disk & net) fare vs. Sun Sparcs?
How many X-terminals, diskless stations can a 710 or 720 handle?
Complaints or praise?

Thanks
--
toma@tc.cornell.edu - Rory Toma

Apple & IBM - Bringing us closer to the world of yesterday, only they're
not going to tell us how they did it, and they'll sue anyone who helps!