HDTenEightyP/NetNews huggingface dataset:
From: lee@ceg.uiuc.edu (Chris Lee)
Newsgroups: comp.sys.hp
Subject: Xtex on hp 700s: font problems
Keywords: Xtex has problems making fonts
Date: 11 Nov 92 16:38:59 GMT
Organization: University of Illinois at Urbana


I'm trying to get Xtex (2.18.5) to work on a HP9000/720 machine.  For
some reason, the fonts just don't seem to be made properly...it does
display the encapsulated postscript figures, but the text looks quite
horrible because of the fonts.

I have the full TeX3.14 distribution installed, and I am using
HPUX 8.07 and HPs C compiler (not the bundled one).

In the config file, I have defined:
     XTEX_FONT_PATH=/admin/tex/lib/xtex
     FontDesc=/admin/tex/lib/fontdesc

When the directory /admin/tex/lib/xtex exists, Xtex exits with the
following error.

     X Error of failed request:  BadValue (integer parameter out of range for operation)
       Major opcode of failed request:  51 (X_SetFontPath)
       Value in failed request:  0x5
       Serial number of failed request:  136
       Current serial number in output stream:  187

When the directory does not exist, Xtex goes on and tells me all the 
fonts it's missing, and in the dialogue box gives the messages (1 of many)
     TeXtoXfont cmr10 85 85 1000 sun  /admin/tex/lib/xtex 2>&1
and
     [ exec ] TeXtoXfont cmr10 85 85 1000 sun /admin/tex/lib/xtex 2>&1
     ./TeXtoXfont: xdpyinfo: not found
     1st mftobdf -dpi 85 cmr10
     mf \mode:=sun; mag:=1000/1000; scrollmode; input cmr10 </dev/null
     This is METAFONT, C Version 2.7
     [ LOTSA METAFONT OUTPUT deleted]
     Font metrics written on cmr10.tfm.
     Output written on cmr10.85gf (128 characters, 5156 bytes).
     Transcript written on cmr10.log.
     mftobdf -dpi 85 cmr10
     Mftobdf failed for some reason on cmr10.85.bdf
     Missing cmr10.85 ( -mag 1000 -scaled 1000 cmr10 )

Now, I can't find the tfm and 85gf files ANYWHERE!  Also, the fact that 
mftobdf fails sorta troubles me.  I tried running mftobdf manually, and
even there, no output seems to be written.

Is this (yet) another X fontism that I am not aware of?
Has anyone had similar problems (and hopefully solutions)?

Thanks in advance.
-- 
Chris Lee
University of Illinois Urbana
lee@ceg.uiuc.edu
(217)244-2903
From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
Newsgroups: comp.sys.hp
Subject: Re: Xaw include files for HP 425 w hpux 8.0
Date: 9 Nov 92 12:20:55 GMT
Organization: Naval Research Laboratory, DC

In article <1dl8ulINNn1h@sbusol.rz.uni-sb.de> ph11mlar@sbusol.rz.uni-sb.de (Arthur Recktenwald) writes:

>main.c: 43: Can't find include file X11/Xaw/Viewport.h
....

  Your problem is actually even worse than you think.  You are missing
both Xaw header files and Xaw library files.  IFF you have ftp access,
you can get replacements from MIT's X11 site (export.lcs.mit.edu) via
anonymous ftp.  You are also missing several other libraries that HP
refuses to sell unbundled or include with the OS, for example Xmu.  If
you don't have ftp access, you are shit out of luck (like most US Navy
sites are).

  Please also call up your HP sales rep and ask him point blank why HP
sold you a system that is missing essential parts of the MIT Core X11
distribution and make it clear that the only acceptable practice is
for HP to include the ENTIRE MIT X11 Core distribution.

Ran
atkinson@itd.nrl.navy.mil
Newsgroups: comp.sys.hp
From: zcnj01@hou.amoco.com (Cecil N. Jones)
Subject: OpenMail
Reply-To: zcnj01@hou.amoco.com
Organization: Amoco
Date: Wed, 11 Nov 1992 14:53:41 GMT


I am interested in HP's OpenMail X.400-based mail solution. I know a lot about it already, but I would like to hear from someone who has actually used it, that is, a HP OpenMail customer. Any info will be appreciated.

Thanks,


---
  Cecil N. Jones    Amoco Production Co.  Houston, TX  713-588-5716
  Jones_Cecil_N/ets_ess@hou.amoco.com              
  The opinions expressed are solely my own.

Newsgroups: comp.sys.hp
From: bpja@codex.com.au (Brett Adam)
Subject: Casting from loose to strict alignment - what does this mean?
Reply-To: bpja@codex.com.au
Organization: Codex Software Development Pty Ltd
Date: Thu, 12 Nov 92 07:59:22 GMT

Ok, I'm beginning to clutch at straws but my memory problems have me somewhat  
annoyed. The following applies to HP 700 series.

With all warnings on (+w1) using cc in ansi mode, I'm getting occasional  
warnings of the following nature:

cc: "ni_glue.c", line 767: warning 530: Casting from loose to strict alignment.

Does anyone have a precise definition of what this means/indicates? I'm new to  
the HP environment and am unsure as to how important this may be in the scheme  
of things.

Thanks for any help.

-- 
-------------------------------------------------------------------
Brett Adam                                      
Xedoc Software Development Pty. Ltd.           Melbourne, Australia
Phone    :                                           +61 3 696 2490
From: kirkl@cmdrdata.cs.byu.edu (Kirk Duffin)
Newsgroups: comp.sys.hp
Subject: Starbase Radiosity and RayTracing Library
Date: 6 Nov 1992 18:36:19 GMT
Organization: Digital Equipment Corporation
Distribution: world
Reply-To: kirkl@cmdrdata.cs.byu.edu (Kirk Duffin)
NNTP-Posting-Host: cmdrdata.cs.byu.edu

We recently acquired some HP 9000 machines.  Included in the
documentation was a description of the
Starbase Radiosity and Ray tracing package.  However, the files that are
to be used for that package
(/usr/include/sbrr.c.h and /usr/lib/libsbrr.a) are nowhere to be found. 
We down loaded all of the
Starbase files off of CD_ROM, but still can't find the above mentioned
files.  We called HP to try to
get some help from them, but they were less than helpful and gave us
essentially no information.
Has anyone found the radiosity/ray tracing stuff, and if so where is it?
Is it on one of the CD-ROM
disks, and if so, which one, and under which fileset?
From: jinx@zurich.ai.mit.edu (Guillermo J. Rozas)
Newsgroups: comp.sys.hp
Subject: mmap on HP-UX 9.0 on s700
Date: 7 Nov 92 03:11:13 GMT
Article-I.D.: chamarti.JINX.92Nov6221113
Reply-To: jinx@zurich.ai.mit.edu
Organization: M.I.T. Artificial Intelligence Lab.

I've been reading the documentation (LaserRom) for the mmap system
call in HP-UX 9.0 and I have some questions about how it applies to
the s700.

The documentation claims that mapped files shared among multiple
processes must be mapped to the same virtual address in all the
processes because of architectural restrictions.  It also claims that
MAP_FIXED generally will fail even if it is a private (MAP_PRIVATE)
mapping.

On reading the 1.1 architecture reference I found that there is a
limited degree of virtual address aliasing allowed by the architecture
(version 1.0 allowed none).  64-bit global Virtual addresses differing
only in 12 specific bits space-identifier bits are allowed to be
mapped to the same physical address.

Additionally, as far as I know, the current s700 hardware (models 705,
710, 720, 730, and 750, I don't know about the 74x) have direct-mapped
caches which properly divide 256kbytes, thus the caches should be able
to support aliasing of virtual addresses whose lower-order 18 bits
match.

What I don't understand is why a stronger restriction is imposed on
the use of MAP_FIXED in conjunction with MAP_SHARED.  The restriction
specified for the s700 (and for the s800, but I can understand it in
this case since there are machines based on version 1.0 of the
architecture) should be weaker, namely that only certain addresses are
valid for MAP_FIXED, but the restriction stated is that the addresses
must be the same.

Can someone explain this to me?

Is there any range of addresses (e.g. between 0x40000000 and
0x80000000) for which MAP_FIXED in conjunction with MAP_PRIVATE will
not fail?

I ask this because there is a GNU package (mmalloc) that uses mmap
instead of sbrk to allocate memory.  It can be used to detach the
memory segment for subsequent re-attachment, or for other purposes.
However, there is an implicit assumption in the code that successive
calls to mmap can allocate a contiguous range (the way that calls to
sbrk do) by specifying the address for later calls, yet this is not
(apparently) guaranteed to work on the s700 in HP-UX 9.0.
Newsgroups: comp.sys.hp
From: gordon@maxwell.uwaterloo.ca (Gordon R. Strachan)
Subject: Re: HP VUE backdrops -- colour ???
Keywords: VUE backdrop colour
Organization: University of Waterloo
Date: Sun, 8 Nov 1992 18:23:57 GMT

In article <1dcccbINNkfn@rave.larc.nasa.gov> jeffc@magician.larc.nasa.gov (Jeff Cleveland) writes:
>In article <1992Nov5.204454.11031@nb.rockwell.com>, robbie@nb.rockwell.com (Edward MacRobbie) writes:
>> 
>> 
>> Re-posting of unanswered questions:
>> 
>> 
>> 	(1) Does anybody know if a colour bitmap can be 
>> 	    placed as a backdrop on a HP730 running HP VUE ?
>>                      ...if so how ?
>	Not in vue 2.x. The format used for backdrops is an X bitmap,
>	and is only monochrome. HP/UX 9.0 and vue 3 is supposed to
>	contain better color support -- color icons and the like. Hopefully
>	color backdrops will be included as well.

Well, you can always set your backdrop resource to none so VUE won't put
up the pseudoroot window.  You can then use programs like xloadimage to
load a colour image onto the root window.

Gordon


Newsgroups: comp.sys.hp
From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
Subject: Re: New to HPs...Thinking about buying one...need advice...
Organization: Naval Research Laboratory, DC
Date: Wed, 11 Nov 1992 16:01:48 GMT

In article <721483576.8584@minster.york.ac.uk> aaron@minster.york.ac.uk writes:

>The hardware is good but HP-UX is neither one thing nor the other,
>and certainly not as easy to port things onto as it should be. Also
>it annoys me that HP-UX don't send me patches when they fix one pf
>the many bugs, or the response centre staff seem ignorant of its
>existence even when you quote the number at them.

Agreed.  

  To be quite blunt, I'd like to see HP migrate HPUX to be fully
System V Interface Definition (SVID), Version 3 compliant.  HPUX is
currently fully compliant with SVID 2.0 which dates back to the
mid-1980s.  The most recent OSF operating system specification is SVID
3 compliant as is System V Release 4, so it is not closed or
proprietary (heck, its the only case I can find where OSF and USL
agreed on something).  I don't care whether HP rolls its own kernel,
uses the OSF kernel, or goes with an SVR4 kernel.

  The POSIX standards are often not sufficient for real portability
and HP Marketing uses standards as a defense against doing The Right
Thing.  POSIX compliance is necessary but not sufficient.

Ran
atkinson@itd.nrl.navy.mil
From: ron@topaz.bds.com (Ron Natalie)
Newsgroups: comp.sys.hp
Subject: Re: Should HP 720 monitors be left on when not in use?
Date: 6 Nov 1992 14:13:06 GMT
Organization: BDS Systems
Distribution: world
NNTP-Posting-Host: topaz.bds.com

What is also not mentioned here is that the quality of the monitor decreases
with it's power on time.  Turning off the HP monitor (the screen blanker
in the HP X is no good for this) will keep your monitors looking sharper.

-Ron
Newsgroups: comp.sys.hp
From: martins@hpl.hp.com (Henrique Martins)
Subject: Re: ~/.Xdefaults ignored by X11R4 and X11R5 under HPUX 08.07 ?
Date: Wed, 11 Nov 1992 06:34:41 GMT
Organization: Hewlett-Packard Laboratories, Palo Alto, CA

In article <HARLAN.92Nov10104715@haduk.cms-stl.com> harlan@cms-stl.com (Harlan Stenn (PFCS Corporation)) writes:

> On our 9000/7xx machines running HPUX 08.07 using the stock X11R4 as
> well as the X11R5 stuff (from iworks) we have noticed that the
> ~/.Xdefaults file seems to be ignored.

  Are you using VUE as your window manager? VUE uses xrdb to load
~/.vue/<host>:0/<home_or_current>/vue.resources. Roll in your .Xdefaults
entries into that file, or do "xrdb -merge ~/.Xdefaults" after you log in,
and see if it works.

  -- Henrique (martins@hpl.hp.com)
Newsgroups: comp.sys.hp
From: root@lysator.liu.se (Peter Eriksson)
Subject: HP7933, HP7935, HP7935+"Cache Memory"
Organization: Lysator Academic Computer Society, Linkoping University, Sweden
Date: Wed, 11 Nov 1992 15:54:17 GMT

What is the difference between the HP 7933, the HP7935 and
a HP7935 with a sticker "CACHE Memory"?

We have a HP9000s3?? (looks like an upgraded hp9k300, it has a 68020 and 4MB
of RAM) running HP-UX 8.0 that usually has problem finding the system which
is located on drive 0 (a 7935). Once it has found it everything works just fine
so I suspect there is something wring with that drive. We also have four other
7935 (some with "CACHE MEMORY" stickers and some without).

Would it be possible to put a booting program + kernel on the other drives
(but still have the root file system on drive 0)?

/Peter


-- 
Peter Eriksson                                              pen@lysator.liu.se
Lysator Academic Computer Society                 ...!uunet!lysator.liu.se!pen
University of Linkoping, Sweden                I'm still bored. Flame me again.
Newsgroups: comp.sys.hp
From: rjn@FC.HP.COM (Bob Niland)
Subject: Re: CDROM connection to diskless node.
Date: Tue, 10 Nov 1992 18:16:07 GMT
Distribution: usa
Reply-To: rjn@FC.HP.COM
Organization: Hewlett-Packard/WSY Ft.Collins,CO,USA
X-Newsreader: TIN [version 1.1.8 PL6]

Kalpit Desai P265 (kdesai@brtph490.NoSubdomain.NoDomain) wrote:

> I have a HP 9000/425t (HPUX 8.0) (diskless) connected on the local net to
> a file server.  I attempted to connect a CDROM to my node.  Unfortunately
> my machine barfs stating that it can only connect the CDROM to a root
> server and not my diskless node.  Can someone help me and tell me what I
> am doing wrong.

You are not doing anything wrong.  Cnodes only support local mounting of
filesystem types "hfs" and "nfs".  "cdfs" can only be mounted on rootservers
and stand-alone nodes.  There is no workaround available from HP, and I have
no idea when this limitation will be lifted.

> Is there any software that I can use to enable me to connect the CDROM
> to my machine rather than the root server.

Young Minds, Inc.  has a package called "PFS" (Portable File System), that
primarily provides RockRidge (Posix fs semantics on top of ISO 9660) support
on various hosts.  It also provides local-mount, case-folding and file-
version-suppression for ISO 9600 CDs on HP systems.  We loaned them a Series
400 machine recently, but I don't know if they have ported PFS to it, or if
they are selling a PFS/400 yet.  You might call and ask them.

Young Minds, Inc.
1910 Orange Tree Lane
Suite 300
Redlands, CA 92374
(714) 335-1350
Director of Sales:
Jacqueline Gillooly


Regards,                                              Hewlett-Packard
Bob Niland      Internet: rjn@FC.HP.COM               3404 East Harmony Road
                CompuServe:  71044,2124               Ft Collins CO 80525-9599
Newsgroups: comp.sys.hp
From: rjn@FC.HP.COM (Bob Niland)
Subject: Re: Running HP-IB disks on slow HP-IB Interface
Date: Thu, 5 Nov 1992 20:02:50 GMT
Reply-To: rjn@FC.HP.COM
Organization: Hewlett-Packard/WSY Ft.Collins,CO,USA
X-Newsreader: TIN [version 1.1.8 PL6]

Pat Allen (alpa@hp850.mbari.org) wrote:

> Does anybody out there have any experience running disks off the low speed
> HP-IB interface? What kind of problems might I run into? This is not a
> performance sensitive application and there is nothing else connected to the
> HP-IB chain.

As long as the HP-IB port has "interrupt on PPOLL response", you will
experience some minor degradation on serial access to large files, but
otherwise won't notice much slowdown.  All Series 300 and 400 standard-speed
HP-IB ports have int-on-PPOLL except for the Model 320 built-in and the
plug-in 98624A (not the 98625A/B).

Regards,                                              Hewlett-Packard
Bob Niland      Internet: rjn@FC.HP.COM               3404 East Harmony Road
                CompuServe:  71044,2124               Ft Collins CO 80525-9599

This article represents only the opinion[s] of its author, and is not an
official or unofficial position of, or statement by, the Hewlett-Packard
Company.  The text is provided for informational purposes only.  It is
supplied without warranty of any kind.
Newsgroups: comp.sys.hp
From: tml@tik.vtt.fi (Tor Lillqvist)
Newsgroups: comp.sys.hp
Subject: Re: CAP/AUFS on HP730
Date: 7 Nov 92 10:57:02
Organization: Technical Research Centre of Finland, Laboratory for Information
	Processing (VTT/TIK)
NNTP-Posting-Host: tik.vtt.fi
In-reply-to: bennett@areaplg2.corp.mot.com's message of Fri, 6 Nov 1992 23:50:06 GMT

Yes, I have run CAP on the hp9000, both on the model 822 and 750.
Previously I used KIP encapsulation, now uab. I didn't have any
problems like the one you described. What patchlevel of CAP are you
using? If I remember correctly, I have used levels 60, 100, and now
the latest, 126.
--
Tor Lillqvist,
working, but not speaking, for the Technical Research Centre of Finland,
Laboratory for Information Processing (VTT/TIK).
From: tml@tik.vtt.fi (Tor Lillqvist)
Newsgroups: comp.sys.hp
Subject: Re: Writing to argv[] for display in 'ps'
Date: 9 Nov 92 14:08:55
Organization: Technical Research Centre of Finland, Laboratory for Information
	Processing (VTT/TIK)
NNTP-Posting-Host: tiuhti.tik.vtt.fi
In-reply-to: dsiebert@icaen.uiowa.edu's message of Mon, 9 Nov 1992 10:11:45 GMT

In article <1992Nov9.101145.10528@icaen.uiowa.edu> dsiebert@icaen.uiowa.edu (Doug Siebert) writes:

   How can I write to the argv[] strings in a program so that the
   altered strings show up in 'ps'?

In HP-UX you can't do it by clobbering the argv strings, but with the
undocumented pstat syscall.  This code is from sendmail 5.65c. Modify
to your taste (especially remove the " (sendmail)").

/*
**  SETPROCTITLE -- set process title for ps
**
**	Parameters:
**		fmt -- a printf style format string.
**		a, b, c -- possible parameters to fmt.
**
**	Returns:
**		none.
**
**	Side Effects:
**		Clobbers argv of our main procedure so ps(1) will
**		display the title.
*/

/*VARARGS1*/
void
#ifdef __STDC__
setproctitle(const char *fmt, ...)
#else /* !__STDC__ */
setproctitle(fmt, va_alist)
	const char *fmt;
va_dcl
#endif /* __STDC__ */
{
#if defined(SETPROCTITLE) && !defined(SYSV)
	va_list	args;
	register char *p;
	register int i;
#if defined(__hpux) && defined(PSTAT_SETCMD)
	union pstun un;
#else
	extern char **Argv;
	extern char *LastArgv;
#endif
	char buf[MAXLINE];

# ifdef __STDC__
	va_start(args, fmt);
# else /* !__STDC__ */
	va_start(args);
# endif /* __STDC__ */
	(void) vsprintf(buf, fmt, args);
	va_end(args);

#if defined(__hpux) && defined(PSTAT_SETCMD)
	(void) sprintf(buf + strlen(buf), " (sendmail)");
	un.pst_command = buf;
	pstat(PSTAT_SETCMD, un, strlen(buf), 0, 0);
#else
	/* make ps print "(sendmail)" */
	p = Argv[0];
	*p++ = '-';

	i = strlen(buf);
	if (i > LastArgv - p - 2)
	{
		i = LastArgv - p - 2;
		buf[i] = '\0';
	}
	(void) strcpy(p, buf);
	p += i;
	while (p < LastArgv)
		*p++ = ' ';
#endif
#endif /* SETPROCTITLE && !SYSV */
}
--
Tor Lillqvist,
working, but not speaking, for the Technical Research Centre of Finland,
Laboratory for Information Processing (VTT/TIK).
From: stroyan@hpfcso.FC.HP.COM (Mike Stroyan)
Newsgroups: comp.sys.hp
Subject: Re: VUE, HPTerms and core files
Date: 5 Nov 92 18:50:24 GMT
Organization: Hewlett-Packard, Fort Collins, CO, USA

In comp.sys.hp, sullivan@interex.UUCP (John Sullivan) writes:

> I have created quite a collection of core files and would like some info
> on where to look for info on reading them.  I create them by running HPTERM.
> I have a 705 with 8.07.  I usually use VUE.  A sample follows:

> The response center was stuck  on this one so I hope I
> can figure it out with some help!  Do I use XDB?  ADB?  Do I need anything
> else?  Which manual would I need to order?  Can I do this myself?

There is a good chance that patch PHSS_1660 will correct the problem.

Debugging without a symbol table is very difficult.

Mike Stroyan, mike_stroyan@fc.hp.com
Xref: sparky comp.sys.hp:12900 comp.unix.admin:6184 comp.unix.wizards:4668
From: abooth@cmsa.gmr.com (Alice Booth CT/90)
Newsgroups: comp.sys.hp,comp.unix.admin,comp.unix.wizards
Subject: Re: Help!  Need to restore without backup
Date: 13 Nov 92 19:40:36 GMT
Reply-To: abooth@cmsa.gmr.com
Followup-To: comp.sys.hp
Distribution: usa
Organization: Sun Microsystems

Please mail any helpful responses to 
  abooth@cmsa.gmr.com

Thanks.


Newsgroups: comp.sys.hp
From: gcagle@dracula.mentorg.com (Greg Cagle)
Subject: Re: New HP Workstations (audio)
Date: Fri, 13 Nov 1992 15:11:23 GMT
Organization: Mentor Graphics
Keywords: 
Followup-To: 

Hmmm. I was under the impression that all the new boxes have integrated
16-bit audio.

-- Greg
---------------------------------------------------------------------------
Greg Cagle                                      Mentor Graphics Corporation
greg_cagle@mentorg.com                         Platform Technology Division
(503)685-1570                                  Member of the Cultural Elite
---------------------------------------------------------------------------
Newsgroups: comp.sys.hp
From: jeff@dsndata.uucp (Jeff Minnig)
Subject: multiple tape files on 9144
Organization: Design Data
Distribution: comp
Date: Thu, 12 Nov 1992 15:16:41 GMT


I have an application that needs to write multiple tape files to cs80
cartridge tapes on a 9144 tape drive.

the tapes need to look like this:

file
eof
file
eof
file
eof
...


Does anyone have suggestions on how to accomplish this?

It's easy to do on DAT.  My application has to support both DAT
and cartridge tape drives...

Thanks in advance

-jeff-


--

----------------------------------------------------------------------
	I said it, not the people I work for.
----------------------------------------------------------------------
Jeff Minnig                     | (402) 476-8278
Design Data			|
1033 'O' St.  Suite 324         | {hpfcla,sparky}!dsndata!jeff
Lincoln NE 68508                | 
----------------------------------------------------------------------
	Home is where your keyboard is.
----------------------------------------------------------------------

Newsgroups: comp.sys.hp
From: bpja@codex.com.au (Brett Adam)
Subject: Re: HP/UX 8.x and RPC/XDR - SOLVED!
Reply-To: bpja@codex.com.au
Organization: Codex Software Development Pty Ltd
Date: Thu, 12 Nov 92 10:06:39 GMT

In article <1992Nov12.073003.1352@codex.oz.au> bpja@codex.com.au (Brett Adam)  
writes:
> I'm now almost 100% convinced that the RPC implementation under HP/UX is  
flaky  
> with regards to memory allocation/deallocation.
> 


Thank god for the net!

Despite calls to HP support to try and answer this one, the necessary insight  
finally came from Darren Smith somewhere deep within HP via this forum.

The truth, it seems, is that all rpc memory allocation and deallocation use  
routines _rpc_malloc() and _rpc_free() which are NOT compatible with free() or  
realloc().

Now that I know what's going on, I can workaround the implementation ...

Thanks to all who helped.

Regards,

-- 
-------------------------------------------------------------------
Brett Adam                                      
Xedoc Software Development Pty. Ltd.           Melbourne, Australia
Phone    :                                           +61 3 696 2490