HDTenEightyP/NetNews huggingface dataset:
Newsgroups: comp.sys.hp

NetIPC <-> BSD Sockets communication does not require MPE/iX 4.0 -- and
I see that a previous responder has already covered this.  I'll just add
than BSD Sockets for MPE/iX becomes available on 4.0 -- this is probably
why someone thought you needed the 4.0 operating system.  Of course, if
you get BSD Sockets for MPE/iX, the NetIPC <-> BSD Sockets question is
moot.  If you haven't already done any development (and are willing to
live with the restriction of not operating on OS versions prior to 4.0), 
I'd go with the pure sockets implementation.  If you already have NetIPC
code running on MPE/iX, the NetIPC <-> sockets interface isn't too
difficult (although I've never actually implemented it, I have written 
both Sockets and NetIPC servers, and they're pretty similar).

Mike Yawn
CSY VAB Consulting Group
speaking for myself only; standard disclaimers apply.
From: fgg@gemini.gsfc.nasa.gov (Frank G. Gomez)
Newsgroups: comp.sys.hp
Subject: SCSI woes
Date: 28 Jul 92 21:31:59 GMT
Organization: NASA GSFC CDP VLBI

System: HP 9000/730  at 8.07

What does it mean when these messages start appearing in
/usr/adm/messages ? :

bus 1, ASC 4, ASC Q 0, sense key 2, ASL 14,
  sense key specific bytes: 0 0 0
SCSI: soft->hard error; lun 0, target 0, bus 1
SCSI: sense key, lun 0, target 0, bus 1: Not Ready
SCSI: sense key, lun 0, target 0, bus 1: Drive Not Ready

I can no longer communicate at all with the Differential
SCSI drive that this message is talking about, although another
drive in the same box is working fine.  Power supplies appeared
to be ok.  HP 'Response' did not give me much of one.

Using mount gives:
   mount: /dev/dsk/c41d0s0 No such device or address
Using fsck gives:
   could not read superblock of /dev/dsk/c41d0s0: I/O error
Using dd gives:
  dd: cannot open /dev/dsk/c41d0s0

The drive configuration (special file, SCSI address in back)
was not changed in any way, and was working before.

Ideas ?  Sympathy ?  Laughter ?

Thanks,
Frank G. Gomez  (Oh, the drive is an HP 97560)
From: ghsu@critical.nswc.navy.mil
Newsgroups: comp.sys.hp
Subject: reconfigure keyborad of HP700
Keywords: keyboard
Date: 22 Jul 92 15:15:07 GMT
Organization: Naval Surface Warfare Center

Hi, I recently switch from Sun to HP workstations.   I am having a
toughest time adjusting to the keyboard.   It is esspecially
troublesome since I virtually use GNU Emacs a lot.   As I remembered,
this was a widely discussed subject in this news group.    I would
like to draw from your wisdom and get some advice on the best way to
reconfigure the keyboard.   I can do the simple things such as stty
in csh and swap keys in Emacs to exchange bksp and del keys.   But I
want to know how one can disable that cap lock key next to the control
key?  Or, better yet, make the cap lock also function as a control
key?   Please send your reply by mail.   The volumn for the group is
too big for me to follow.   Thanks.

BTW, this should be a FAQ for this group.   Is there a FAQ somewhere?


-- 
Guan-Hsong Hsu                   Email: ghsu@critical.nswc.navy.mil
Nonlinear Dynamics Group
Mathematics and Information Sciences Branch (R44)
NSWC DD/WO, Silver Spring, MD 20903-5000
Newsgroups: comp.sys.hp
From: karsten@asl.uni-bielefeld.de (Karsten Quast)
Subject: I need X11-tools 
Date: Tue, 21 Jul 92 18:13:15 GMT
Organization: Universitaet Bielefeld, ASL.

Does anybody know where to find X11-tools for the hp720?
I would be very grateful to hear about them.

Many thanks in advance!

Karsten
From: rdg@hpfcso.FC.HP.COM (Rob Gardner)
Date: Fri, 31 Jul 1992 18:51:06 GMT
Subject: Re: Parallel port compatibility problems?
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.sys.hp



>                           Minor number format: 0xSEF001.

Just to answer the question in advance, the SEF in the minor number
will *always* be 206on the 720/730, ie, minor number format is
0x20600m, where m is the mode.


Rob
Newsgroups: comp.sys.hp
From: zaphod@ctrg.rri.uwo.ca (Lance R. Bailey)
Subject: Re: REXEC of shell script; how to get profile env?
Reply-To: zaphod@ctrg.rri.uwo.ca
Organization: University of Western Ontario
Distribution: na
Date: Tue, 21 Jul 1992 20:12:27 GMT

In article <BrpL0r.Hqy@spock.dis.cccd.edu> markb@spock.dis.cccd.edu (Mark  
Bixby) writes:
>I'm running HPUX 8.02 on a 9000/817 machine.  I am executing a shell script
>via the rexec facility.  How can I establish a normal "login"-type environment
>for my script? 

this was covered in "Wizard's Grabbag" of the most recent unixworld.

--
Lance R. Bailey  System/Network Manager         Robarts Research Institute
     NeXT/email: zaphod@ctrg.rri.uwo.ca    box: Clinical Trials Resources Group
            fax: +1 519 663 3789                P.O. Box 5015, 100 Perth Dr.
            vox: +1 519 663 3787 x4108          London, Canada N6A 5K8
Cats Hate it: when they get caught.
From: smr@iti.org (S.Riehm)
Newsgroups: comp.sys.hp
Subject: vuewm - EXIT_SESSION action question
Date: 23 Jul 92 15:41:33 GMT
Distribution: comp

I have got quite a lot of programs which I run in the background while
I am logged in, but which I don't really need to run while I am not,
so to be nice to other users of my machine, and at the same time
without increasing the number of things I need to do to log out, I
would like to put some commands in a file which would be run by vue
when I quit my session. Something like the .logout would be nice, but
obviously with many windows, I can log out many times while still
being logged in, so .login is no good. I have been thinking along the
lines of changing the EXIT_SESSION definition, to run a script or
something, but it appears to be map'ed to VUE_EXIT_SESSION, which is
defined to run EXIT_SESSION (!?). ( doesn't that mean that vue exits a
session by getting confused?? )

Does anyone have any suggestions??

thanks in advance

-----------------------------------------------------------------
Stephen Riehm				   smr@pki-nbg.philips.de
not in any way talking on behalf of:
Philips Kommunikations Industrie	  Phone: +49 911 526 2975
8500 Nuremberg, Germany			    Fax: +49 911 526 2095
I come from the land down under, where women glow and men blunder
PS: I know my From: line is wrong.. but I don't know WHY!
Newsgroups: comp.sys.hp
From: us048503@mmm.serc.3m.com (Art H. Hurst)
Subject: Re: Help with LaserJet+Postscript on HP-UX
Organization: 3M Company
Distribution: usa
Date: Thu, 23 Jul 92 13:06:17 GMT

In article <l6rnokINN8gf@sipi.usc.edu> weber@sipi.usc.edu (Allan G. Weber) writes:
>Can somebody give me some advice on getting a HP LaserJet IIID with an HP
>Postscript cartridge to work off an HP 425S (HP-UX 7.05) via an RS-232
>connection?  If the Postscript cartridge is not installed it works fine by
>specifying the "laserjet" printer model when setting it up with lpadmin.
>However, with the Postscript cartridge installed I guess it no longer acts
>enough like a LaserJet to work.  I tried specifying the "dumb" model hoping it
>would just pass the data to the printer but nothing ever came out.  None of the
>HPUX documentation mentions anything about Postscript, and none of the LaserJet
>documentation mentions HP-UX so I'm a bit lost.

	We are using a IIIP w/cartridge. One must 'toggle' between
	normal and PS modes via the following sequence--
	hit 'on-line' to take unit offline -- on-line light should go
	out. Next hold '+/-' key down and depress 'Alt' & 'Reset'
	simultaneously. The unit should switch from PCL to PS modes and
	vice versa. One thing that is not obvious is that by adding the
	cartridge, your default printer parameters change! Check the
	booklet that came with the cartridge.

-- 
Art Hurst                                         Email: ahhurst@mmm.com
3M Company                                        Phone: (805)388-4170
Digital Storage Products Division                 FAX:   (805)388-4804
Camarillo CA 93012
From: jdevlin@pollux.usc.edu (Joseph T. Devlin)
Newsgroups: comp.sys.hp
Subject: The newfs command
Date: 24 Jul 1992 13:16:07 -0700
Organization: University of Southern California, Los Angeles, CA
Distribution: na
NNTP-Posting-Host: pollux.usc.edu

  Ok, got the disktab entry to work - as far as I can tell - but
now when I try to add the new filesystem I get the following:

> /etc/newfs -v /dev/rdsk/1s0 FUJ_M2266S-512
/etc/mkfs -L /dev/rdsk/1s0 1053846 127 18 4096 1024 16 10 60 2048
cylinder group too large (16 cylinders); max: 10 cylinders per group

But when I checked the man on newfs I found the default cylinder group
size is 16.  Furthermore, the man for mkfs says that this number only
has to be in the 1-32 range.  Any experience with this kind of problem?
Thanks much!

							- Joe

*************************************************************************
Joseph Devlin                      * email: jdevlin@pollux.usc.edu
University of Southern California  *
Department of Computer science     * "The axon does not think.
Los Angeles, CA 90089              *  It just ax."  George Bishop
*************************************************************************
From: xm9@sdcc12.ucsd.edu (richard g. adair)
Newsgroups: comp.sys.hp
Subject: Re: HP's Disk Array Implementation
Summary: E Pluribus Unun
Keywords: disk striping
Date: 23 Jul 92 15:58:16 GMT
Organization: Arete Associates, San Diego

In article <67870141@hpcupt1.cup.hp.com> dhepner@hpcupt1.cup.hp.com (Dan Hepner) writes:
>From: xm9@sdcc12.ucsd.edu (richard g. adair)
>
>>Ona related topic, does anybody have experience with striped disks,
>>either as file system space or disk swap?  Are there any gotchas?
>>I'm thinking of adding two 1.6GB drives as user and file system
>>swap, creating one 3GB disk.  Does this work reliably?
>It wouldn't work for for filesystems if your filesystem size was 
>limited to 2GB.  It wouldn't work for swap if swap was unable
>to handle > 2BG disk partitions.
>What do you hope to gain?

I hope to gain space for large file collections.  Right now, we have
our files spread across several disks, and all those soft links are
hard to maintain properly.  Talk about spaghetti linking! :-)  Also,
faster file access is always important for such large files.  Am I
heading into a trap for the unwary?

Tony Burzio
Arete Associates
San Diego, CA
From: mhr@hpuerca.atl.hp.com (Mike Reaser)
Newsgroups: comp.sys.hp
Subject: Re: Problem with C++ or the loader
Date: 31 Jul 92 15:27:58 GMT
Organization: a stone mountain of Kudzu

> I am trying to link a c++ code I am getting the following message:

> ld: initialized data space not big enough for COMM declaration of gain

> Where gain is a variable in one of the objects. An executable is
> generated but it is sometimes aborted for no apparan reason.

> Aharon Friedman (aharon@bnl.gov)

The identifier "gain" has been declared more than once among all the 
object files involved in the link process, and "gain" was declared with
a different type and/or size each time it was defined.

Look at the source code involved in producing the object files used in
the "offending" link -- you should find the multiple, inconsistent
declarations for "gain".

=======================================================================
Mike Reaser                           I barely speak for me, I _sure_
Hewlett-Packard                          don't speak for HP.....
N. Amer. Response Center - Atlanta    
=======================================================================
From: sanner@track.physics.usfca.edu (David Sanner)
Newsgroups: comp.sys.hp
Subject: Postcript to HP LaserJet 500-C ?
Date: 25 Jul 92 22:34:33 GMT
Distribution: na
Organization: University of San Francisco

Does anyone know where I can get a converter to go from 

PostScript -> HP LaserJet 500-C color printer ?

			Thanks,

-- 
                                      David Sanner  (sanner@physics.usfca.edu)
                                      U of S.F.    Physics Research Laboratory
                                      S.F., CA 94117      (415) 666-2962
From: acmeyer@hpfcso.FC.HP.COM (Alan C. Meyer)
Date: Fri, 24 Jul 1992 19:10:02 GMT
Subject: Re: Inhibiting core dumps on HP7xx
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.sys.hp

In comp.sys.hp, elwin@gamma.phys.clemson.edu (Lawrence E. Brown) writes:

> I'm very tired of frequent dumps of 10-40Meg core files every
> time I have a floating exception somewhere in my code (mostly
> Fortran some C).  Is there any way to prevent core dumps in
> HPUX8.0x on an HP700 series machine? 

Here is some information if you are using a Fortran main program.  By
default, trapping for floating point exceptions are not enabled.  For
example,

	X = 0.0
	Y = 1 / X
	PRINT *, Y

will print +INF and execution would continue.  A floating point trap
can be enabled with various methods:

	* Compile your Fortran main with +T (this will enable other
	  traps beyond floating point exception).  If an FPE occurs,
	  you would see a procedure traceback, and no core file
	  created.  For example, the above program would produce:

		PROGRAM ABORTED :  IEEE divide by zero
		PROCEDURE TRACEBACK:
		( 0)  0x00001e80   main__ + 0x70

	* Directly call HP-UX signal handling routines to enable
	  various signals.

	* Several other methods that will be available at "a future
	  release".

Alan Meyer
Colorado Language Lab
acmeyer@fc.hp.com

"These are my own opinions ..."
From: rdg@hpfcso.FC.HP.COM (Rob Gardner)
Date: Fri, 31 Jul 1992 20:01:50 GMT
Subject: Re: device driver for 720
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.sys.hp

> > 2) A "id" is required. There is no specification of what the id looks like,
> > how to create it, set it. Again please direct me to info on how to create
> > the device driver id.
> 
> The id is read from the eisa card (at offset 0xC80 in its I/O space)
> and passed into your attach routine (first argument). Is this what
> you're talking about? Or are you asking how to create the id to be
> programmed into the card? There might be some algorithm, but I think
> it's also OK to choose a random 32-bit integer, since the chances
> of collision with another vendor's id are small.


Ah, I found the correct answer in the EISA specification. There is an
algorithm for constructing ID's, so I wrote the attached summary. DON'T
use a random ID as I suggested before.

Rob


Explanation of EISA ID's.
-------------------------

Construct a 7 character ID as follows: MMMPPPR

MMM is a 3 character manufacturer code, consisting of only [A-Z]
PPP is a 3 digit hex product identifier
R is a 1 digit hex revision number.

For example, HWP123A might be an ID. This is the ID that you specify
in your EISA config file in the ID statement. For example:

	BOARD
	  ID = "HWP123A"
	  NAME = "Example"
	etc.

This 7 character ID is "compressed" into a 32-bit integer which is
found at offset 0xC80 in the I/O space of the EISA card. The
compression happens like this:

Take the least significant 5 bits of the ASCII value of each character
in the manufacturer code, and form a 16 bit number by concatenating them
and putting a 0 bit in the high bit:
    0[5-bits-from-1st-char][5-bits-from-2nd-char][5-bits-from-3rd-char]

Now put the high byte of this 16-bit number into 0xC80, and put the
low byte into 0xC81.

Put the high two bytes of the product identifier into 0xC82. Put
the low byte of the product and the revision digit into 0xC83.

For example, using the  ID "HWP123A" we would get:
	H = ascii 0x48 = 0100 1000
	W = ascii 0x57 = 0101 0111
	P = ascii 0x50 = 0101 0000

Taking the 5 bit chunks, we get:
	0 01000 10111 10000 ===> 0x22f0
So 0xC80 would get 0x22, and 0xC81 would get 0xf0.

Handling the product id and rev code, 0xC82 would get 0x12, and 0xC83
would get 0x3A.

The entire 32 bit ID, after appropriate byte swapping would be
0x22f0123A. This is the value you should define in your driver to
compare with the ID read from the card. For instance:

#define MY_ID 0x22f0123A

my_attach(id, isc)
int id;
struct isc_table_type *isc;
{
	if (id == MY_ID) {
		/* it's my card */
		...
	}
	return((*my_saved_attach)(id, isc));
}
Newsgroups: comp.sys.hp
From: seligman@CS.Stanford.EDU (Scott Seligman)
Subject: Re: /usr/adm/diag ?
Organization: Stanford University
Distribution: usa
Date: Sun, 26 Jul 1992 01:46:53 GMT

In article <Jul.22.10.23.00.1992.8293@paul.rutgers.edu> slu@paul.rutgers.edu (shen lu) writes:
> 
>    I noticed that there were a lot of big files in the directory
>    /usr/adm/diag, by name of LOG00**. (Our systems is a HP817S
>    Running HP-UX 8.02. ) . 
>    What are there files? Is there any reason to keep those files?
>    They sum up to a total about 20 megas. 


The same happens on our 705 & 720 systems running 8.07.  Every 30
minutes (exactly) some process wakes up on each machine, and does
something that causes the LOG* files to grow by about 5 kilobytes
each.  This adds up quickly.

DUI / LOGTOOL doesn't give much info.  It shows a zillion repetitions of
something to the effect of "unable to open device file ()" (note the
empty parentheses).

The culprit is one of the following processes.  I'm not sure how to
narrow it down much further.  Note that "cron" is not running anything
at 30 minute intervals.

  swapper init vhand statdaemon unhashdaemon lcsp syncdaemon gcsp MEMLOGP
  syslogd portmap nfsd inetd rpc.lockd snmpd cron ptydaemon DIAGMON DIAGINIT

Our fix was to "chmod -x /usr/diag/bin/DIAGINIT".   :-(


Scott Seligman

Internet:  seligman@CS.Stanford.EDU
UUCP:      {uunet,decwrl,sun}!cs.stanford.edu!seligman
From: stan@dixie.com (Stan Brown)
Newsgroups: comp.sys.hp
Subject: Re: HP remote print server SYSV like or BSD like ?
Date: 24 Jul 92 23:30:39 GMT
Organization: Dixie Communications Public Access.  The Mouth of the South.

paul@eye.com (Paul B. Booth) writes:

>In article <c8dm=4n@dixie.com> stan@dixie.com (Stan Brown) writes:
>>
>>   Is the HP remote print *server* SYSV like or BSD like?  
>>   
>I'm pretty sure this is right.

>The hp-ux print spooler system is SYSV (lp, lpadmin, and lpsched are SYSV),
>_but_ the mechanism used for remote printing across a network is BSD-based
>(rlp and rlpdaemon).  Has to be this way because SYSV (at least the versions
>that hp-ux is based on) has no capability for networked printers; only BSD has
>that.  If you check the man page for the remote spooling daemon (rlpdaemon) and
>client (rlp), you'll find this:

> AUTHOR
>       rlpdaemon was developed by the University of California, Berkeley and
>       HP.

>The confusion is caused because you never really use rlp directly.  HP simply
>has a SYSV printer model, rmodel, which calls rlp for you.  The rlpdaemon just
>listens for these BSD-style requests, massages them a bit and dumps them onto
>the local SYSV based print spool.

>I've successfully gotten Sun's and Apollo (speaking the BSD dialect of
>DomainOS) to print to HP's.  No experience w/ Dell, though.

   Thanks for the consice summary of a confusing (to ma anyway)
   sunject.

   Stan


>-- 
>Paul B. Booth  (paul@eye.com)
>-------------------------------------------------------------------------------
>3D/EYE, Inc., 2359 N. Triphammer Rd., Ithaca, NY  14850    voice: (607)257-1381
>                                                             fax: (607)257-7335
-- 
Stan Brown					    Electric Systems Inc.
Home (404) 299-2225				Atalanta Ga. (USA)
Home (615) 894-5781				Chattoonaga TN (USA)
Work (615) 899-1714				stan@dixie.com
dixie.com = Public Access UNIX in Georgia
From: shankar@sgi.com (Shankar Unni)
Newsgroups: comp.sys.hp
Subject: Re: HP9000/834.. is it a 2 user only machine ?
Date: 28 Jul 92 00:12:06 GMT
Organization: Silicon Graphics, Inc.

In article <1992Jul25.215554.2729@csdvax.csd.unsw.edu.au> u1044737@csdvax.csd.unsw.edu.au writes:

>HP-UX acme A.B7.00 U 9000/834 23506101     
                           ^^^

Hmmm.. A faint memory of the "834", also known as the "635" (or the
infamous "hp9000 series 600") Server.

This was supposed to be a "network" server, which meant a two-user
license (i.e. one serial-port login (usually the console) and one
"network" login (which includes *unlimited* logins over the network).

You *should* be able to log in multiple users, provided they all come
in over the network.  Where are your users trying to log in from?
Serial ports?
--
Shankar Unni				E-Mail:	shankar@sgi.com
Silicon Graphics Inc.			Phone:	+1-415-390-2072
Newsgroups: comp.sys.hp
From: gordon@madmax.uwaterloo.ca (Gordon R. Strachan)
Subject: Re: Xnetlib runtime error
Organization: University of Waterloo
Date: Wed, 22 Jul 1992 14:42:13 GMT

In article <1992Jul20.103102.49370@ccvax.ucd.ie> beamishd@ccvax.ucd.ie writes:
>Hi, I get this error when I try to run xnetlib 3.0 on a hp720 running 8.07.
>Does anyone know if and how I can avoid it ?
>
>Warning: Cannot convert string "" to type Cursor
>X Error of failed requet:  BadPixmap (invalid Pixmap parameter)
>  Major opcode of failed request:  93 (X_CreateCursor)
>  Resource id in failed request:  0x0
>  Serial number of failed request:  150
>  Current serial number in output stream:  152
>
>I've seen other people on the net note this error before but unfortunately
>haven't seen any reply. ( probably dozing and missed it :)) )

I reported this bug back to the xnetlib people.  They managed to get it to
compile on my 730 by putting some ifdef's around their fancy gas guage widget.
I am a bit surprised this patch hasn't made it in to their distribution yet,
when did you download the code?  If the "fix" isn't in the lastest version
then send them some email and ask for it.  If you still can't get it send me
mail and I will send you the code that I have.

Gordon


Newsgroups: comp.sys.hp
From: simon@giaec.cc.monash.edu.au (simon shields)
Subject: Re: adjustable arrays 720's f77
Organization: Monash University, Melb., Australia.
Date: Wed, 29 Jul 1992 00:04:51 GMT

SYSTEM:
HP-UX giaec A.08.07 A 9000/720 2001133857
Thanks Allan

I'll make those changes you recommended and let you know how I go.
You said that dynamic arrays will be available in a future version 

>At 8.07, the S700 compiler does not support this feature.  However, they
>have been implemented and will ship with the next S700 release.

of the s700 operating system, what version will that be ?

QTN: Should the compiler on the 720's know the 
$STANDARD_LEVEL SYSTEM
compiler option ? I tried using it and get ...

I tried the example in the fortran manual HP9000 600, 800 we have
for dynamic arrays .

$STANDARD_LEVEL SYSTEM
      program main
	  i=10
	  call routine (i)
	  end

	  subroutine routine (i)
	  integer dyn_array(i)
	  dyn_array(i)=i
	  end

$STANDARD_LEVEL SYSTEM - is a compiler option page 7-71 
	"indicates Fortran 77 plus additional system dependent features
	added to the language."

i get
using f77 eg.f
eg.f:
Warning on line 1 of eg.f: unknown inline compiler option
   MAIN main:
   routine:
Declaration error on/above line 10 of eg.f;  for dyn_array; adjustable dimension on non-argument

f77: Error.  No assembly.
f77: Errors detected, no link

Are there fortran manuals for the 720's ? We don't have one, all we
have is a fortran manual HP9000 600, 800 series.


Newsgroups: comp.sys.hp
From: floyd@media.mit.edu (Bob Sabiston)
Subject: Starbase hit mode
Summary: has anyone used it on a 720
Keywords: starbase, hit
Organization: MIT Media Laboratory
Date: Thu, 30 Jul 1992 06:28:28 GMT

Has anyone used the Starbase 'hit mode' on a HP720 CRX24, specifically
with 3D graphics?  Basically I just want to know if anyone has used it
successfully to detect 3d polygons.  Does it work in the current 
implentation of starbase? 

Thanks a lot--
From: jovanov@ceg.uiuc.edu (Dan Jovanovic)
Newsgroups: comp.sys.hp
Subject: idraw for HP 9000/7xx series machines
Date: 22 Jul 92 23:40:25 GMT
Organization: University of Illinois at Urbana

Is there an "officially sanctioned" version of idraw for
HP9000/7xx series machines? Any help would ... well ...
help.

Thanks a bunch,

Dan Jovanovic
From: larryt@hpcupt3.cup.hp.com (Larry Thompson)
Date: Thu, 23 Jul 1992 17:29:22 GMT
Subject: Re: BZONE crashes and logs me out
Organization: Hewlett Packard, Cupertino