HDTenEightyP/NetNews huggingface dataset:
From: muegel@rtsg.mot.com (Michael S. Muegel)
Subject: Re: send_alarm for X?
Organization: Corporate Computer Services & Support, Motorola, Inc.
Distribution: na
Date: Tue, 1 Sep 1992 05:36:04 GMT

Previously, gordonb@mcil.comm.mot.com (Gordon Berkley) wrote:
>Now that I am using X, however, I don't *SEE* my DM window, so I don't
>get my alarms.
>
>Is there a similar function/utility available for X?

Get the Project Athena Zephyr system. From the zephyr manual page:

     Zephyr is a notice transport and delivery system developed at MIT
     which runs under 4.3BSD Unix.

     A Notice Transport and Delivery system is a method of getting small
     quantities of time sensitive information efficiently from one client
     (or server) on a network to another.  The object is to accomplish this
     with the highest possible fan-out (i.e., client to server ratio) while
     maintaining both network and server performance.  Zephyr is a multi-
     cast notice transport and delivery system based upon an authenticated
     datagram protocol.  Localized Zephyr servers provide routing, queueing
     and dispatching services to clients which communicate with them via
     the Zephyr Client Library.  Two special purpose Zephyr clients, the
     WindowGram client and the HostManager client provide user and client
     host communication support.

many clients sit on top of the basic transport system. Zwrite is one of them.
It gives you stuff you are used to in alarms. Nice thing about Zephyr,
though, is that it works on many different UNIX platforms. Zwrite
can work both with X stations and ASCII terminals.

I think I got the source somewhere at mit. Archie could probably say
for sure.

-Mike

-- 
-Michael S. Muegel <mmuegel@mot.com>
UNIX Applications Startup Group
Corporate Computer Services and Support
Motorola, Inc.
Newsgroups: comp.sys.apollo
From: roeber@vxcrna.cern.ch
Subject: traceroute?
Organization: CERN -- European Organization for Nuclear Research
Date: Mon, 31 Aug 1992 12:44:02 GMT

Has anybody ported "traceroute" to Domain?  The standard BSD code
on the net requires kernel mods to get the special info.
Theoretically, this should be much easier (and safer) on Apollos,
since IP is done in a user-level daemon.  Getting the tcpd docs,
though, might be a toughie.

If it hasn't been ported, and if I can get the needed info (that's 
a hint, HP), I'll do it.

Thanks!
Frederick.

-- 
Frederick G. M. Roeber | CERN -- European Center for Nuclear Research
e-mail: roeber@cern.ch or roeber@caltech.edu | work: +41 22 767 31 80
r-mail: CERN/PPE, 1211 Geneva 23, Switzerland | home: +33 50 42 19 44
From: mannex@inference.com (Russ Mannex)
Newsgroups: comp.sys.apollo
Subject: Mailtool?
Date: 28 Aug 92 00:15:33 GMT
Distribution: world
Organization: The Internet

A mail tool for X Windows is all I ask for. One that actually compiles
OK. Does ANYONE have something like this?

************************************************************************
*   Russell Mannex (x140)            "Geometry is God Himself"         *
*   Technical Support                                                  *
*   Inference Corporation                -Johannes Kepler              *
*   (800) 322-5590 - U.S.                                              *
*   1-(310) 322-5530 - Earth                                           *
*   mannex@inference.com - Internet                                    *
*                                                                      *
* *- Views expressed are independent of those held by Roger Carasso -* *
************************************************************************
From: eng271@aberdeen.ac.uk
Newsgroups: comp.sys.apollo
Subject: Colour maps on DN4500 (again??)
Date: 4 Sep 92 14:57:48 GMT
Distribution: world
Organization: The Internet

Hello.

I posted a message earlier in the week, but haven't had any replies - don't even know if it got posted.
The problem is below:


We have a DN4500 running SR10.3 (no patches) which has an 8 plane 19 inch colour monitor.

The command "lcm" was typed in at one of the pads and this changed the colour map.
The question is, how do I get it back to "normal".

I have tried:

lcm                         this leaves it in this new different colour scheme.
lcm -p /sys/dm/color_map    again, leaves it in this new scheme
lcm -r                      (wrong hardware)
lcm -rgb444                 (not found)
lcm -rgb332                 changes it to an even worse colour scheme
lcm -p /sys/node_data/etc/dm_display/color_map.rgb         screen goes black
lcm -p /sys/node_data/etc/dm_display/color_map.rgb332      as -rgb332 option
lcm -x                      no (obvious) effect

I've also copied the /sys/node_data/etc/dm_display tree across from another node, but it makes no
difference. Rebooting the machine makes no difference either.

Booting the machine diskless of a DN2500 still doesn't 'put things right', it still keeps its new
colour scheme. This seems to imply that it isn't anything stored on disk, so where could it be
stored? The monitor from a 4 plane coulr machine also shows the new colour scheme on the DN4500.
It can't be a hardware fault surely?

(I went through 'ex config' and the monitor is set correctly. It doesn't seem to make any difference
changing it to the 4 plane monitor anyway.)

Please tell me if you know how to fix this, or what is wrong.
Thanks,

Jon Penny, Dept of Eng, Univ of Aberdeen.
(j.r.penny@aberdeen.ac.uk)

Newsgroups: comp.sys.apollo,comp.sys.hp
From: gordon@maxwell.uwaterloo.ca (Gordon R. Strachan)
Subject: Re: Strange packaging technique
Organization: University of Waterloo
Date: Thu, 3 Sep 1992 01:27:16 GMT

In article <1992Sep2.234048.18002@u.washington.edu> davidb@zeus.ce.washington.edu (David W. Barts) writes:
>
>In the HP400s to HP433s upgrade kit (A2043), we have three boxes:  a
>motherboard box, an EISA adapter card box, and an accessory kit box.
>
>The accessory kit box contains two plastic SIMM card guides, a
>metal backplane cover, and three machine screws.  These are packed in
>-- you guessed it -- a specially-made piece of anti-static bubble
>wrap marked "CAUTION:  Contents subject to damage by static
>electricity.  DO NOT OPEN except at approved static-free workstations."
>
>Do HP sites have a number of very large Tesla coils that generate
>sparks powerful to melt or vaporize these parts?  Are they plagued
>by numerous lightning strikes?  That anti-static bubble wrap must
>be pretty strong stuff if it can resist a lightning strike!
>
>:-) :-) :-)

Heh heh...

The one I always like is the packing lists that list everything in the box
including the packing list itself!  It even has its own HP part number.  HP
paper work, you gotta love it! :-)

Gordon

PS
Does anybody still have that old "story" about ordering lunch in the HP
cafateria?  It was around about 2 years and I lost my copy.


Newsgroups: comp.sys.apollo
From: muegel@rtsg.mot.com (Michael S. Muegel)
Subject: Re: Mailtool?
Organization: Corporate Computer Services & Support, Motorola, Inc.
Date: Sat, 29 Aug 1992 21:05:16 GMT

Previously, vds7789@aw2.fsl.ca.boeing.com (Vincent D. Skahan) wrote:
>mannex@inference.com (Russ Mannex) writes:
>
>>A mail tool for X Windows is all I ask for. One that actually compiles
>>OK. Does ANYONE have something like this?
>
>try 'elm' or 'pine' in an xterm
>or try 'xmh'

Add xmail to the list. It looks very much like the SunOS Mailtool (if you
like such a beast).

-Mike

-- 
-Michael S. Muegel <mmuegel@mot.com>
UNIX Applications Startup Group
Corporate Computer Services and Support
Motorola, Inc.
From: micki@netcom.com (Michelle Stone)
Newsgroups: comp.sys.apollo
Subject: Apollo DN3000 for sale
Date: 29 Aug 92 18:01:08 GMT
Distribution: ba
Organization: Netcom - Online Communication Services  (408 241-9760 guest)


Apollo DN300 workstation for sale.  19" color monitor, tape drive, floppy
170 Mb hard disk.  $500 cash.  408 736 3911
 
 
I also have some memory cards and other spare parts if anyone is interested.
From: mishkin@apollo.HP.COM (Nathaniel Mishkin)
Newsgroups: comp.sys.apollo
Subject: Re: NCS: problems compiling in ANSI C
Keywords: NCS
Date: 27 Aug 92 19:04:16 GMT
Organization: Hewlett-Packard Company - Distributed Object Computing Program / East

In article <1992Aug26.102340.23358@ghost.dsi.unimi.it>, giachino@ghost.dsi.unimi.it (luca giachino) writes:
>You normally include these files in the manager sources,
>where you actually insert the bodies of the server functions.
>You might be in the need of rendering those functions invisible
>to the other sources, defining them as static. In this way
>the linker doesn't complain when you define different managers
>for the same interface.
>
>But the ANSI C compiler does complain issuing a warning because
>these static functions appear defined with two different prototypes:
>in the include file as simple "#extern type function(type arg, ...)", 
>and in the manager source as "static type function(type arg, ...)".
>
>Is anybody able to tell me a way for avoiding those annoing warnings?

This isn't an ideal solution, but I think it's a reasonable workaround:
use the NIDL compiler "-m" switch and name your static manager routines
something other than what's in the .idl file.  E.g.,

    foo.idl:

        interface foo
        {
            some_op(
                /* parameters */
            );

            some_other_op(
                /* parameters */
            );
        }

    server.c:

        #include "foo.h"

        static my_some_op(/* parameters */)
        {
            /* manager routine body */
        }

        static my_some_other_op(/* parameters */)
        {
            /* manager routine body */
        }

        static foo_vN$epv_t my_foo_epv = {
            my_some_op,
            my_some_other_op
        };

        main()
        {
            ...
            rpc_$register_mgr(&uuid_$nil, &foo_vN$if_spec, 
                              foo_vN$server_epv,
                              (rpc_$mgr_epv_t) &my_foo_epv, &status);
            ...
        }

You can read the documentation for more info on the "-m" switch and
rpc_$register_mgr() call.

-- 
                    -- Nat Mishkin
                       Distributed Object Computing Program / East
                       Hewlett-Packard Company
                       mishkin@apollo.hp.com
Newsgroups: comp.sys.apollo
From: szabo_p@maths.su.oz.au (Paul Szabo)
Subject: Idle nodes? (was Re: automatic screen turn-off)
Reply-To: szabo_p@maths.su.oz.au (Paul Szabo)
Organization: Mathematics, University of Sydney
Date: Tue, 1 Sep 1992 04:14:00 GMT

Is there a way to find out how long an Apollo node (i.e. the interactive
user logged on the display) has been idle? It might be sufficient to find
out whether the screen has been blanked out or not (with due regard to the
setting of scrto). Does anyone know the trick?

In article <BtuqtL.Jor@apollo.hp.com> ganek@apollo.hp.com (Dan Ganek)
writes:
> Under the DM and Xapollo the following events will unblank the
> screen: (I don't know about Xdomain)
> 1) Keyboard/mouse input
> 2) Window reconfiguration, i.e. create, delete, move, resize, etc. 
>    (Graphical output to a window will NOT unblank the screen.)
> 3) Program call to gpr_$video_ctl();

I cannot find any documentation on the gpr_$video_ctl call. (Not that I
would need it at the moment.)

Thanks in advance,

Paul Szabo - System Manager   //        School of Mathematics and Statistics
szabo_p@maths.su.oz.au        //   University of Sydney, NSW 2006, Australia
From: thompson@PAN.SSEC.HONEYWELL.COM ((jt) John Thompson)
Newsgroups: comp.sys.apollo
Subject: re: Printing under 10.4
Date: 3 Sep 92 14:19:04 GMT
Organization: The Internet



> Hello, I are having a great deal of difficulty getting printing to
> work under 10.4.  The problem appears to be either with prmgr or
> with NCS services.
> 
> /sys/hardcopy/prmgr -c config_file -e
> 
> gives the following:
> (prmgr) Can't reach glbd - no matching entry available (network computing system/locating broker)
> (and tries again every so-often...)

If my memory hasn't suffered a parity error, the 10.4 print mgr has a bug.  
Use the 10.3 manager.  The 10.4 print server does not have a problem.

You _might_ also be having problems with the default family that glbd belongs
to.  At 10.3 and ealier, the default family when you created a glbd was DDS.
At 10.4, it was changed to be IP by default.  This is the protocol used when
talking, and is not the same as the 'listen' switch (glbd will always listen
on it's 'family' protocol, and will listen on all (IP / DDS) other active 
protocols unless limited by the '-li' switch).

It seems to me that '/etc/ncs/glbd -create -from dds://ten_three_node' should
have gotten a glbd that belonged to the DDS family, but it _appears_ that I
got it talking on the IP family, since that's the problem I had w/ my first 
10.4 node....


-- jt --
John Thompson
Design Services Engineer / Sys-Admin
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

If you're not part of the solution, you're part of the precipitate.
*************************************************************************
* This e-mail correspondence is a work of fiction.  Any similarity      *
* between the views presented and actual views, personal or corporate,  *
* living, dead, or still to be conceived, is pure coincidence.          *
*************************************************************************

Newsgroups: comp.sys.apollo
From: bush@cae.prds.cdx.mot.com (Michael Bush)
Subject: Re: Nameserver blues
Organization: none
Date: Mon, 31 Aug 1992 19:39:25 GMT

L58@vm.urz.uni-heidelberg.de (Dieter Menszner) writes:

>I am setting up  /etc/named on our Apollo ring with partial success:
> 
>But this doesn't work for me. I think that e.g. ftp should look in
>resolv.conf for the nameserver but it always falls back to
>/etc/hosts. Is ftp and friends broken ?
>

Make sure that you have the nmconfig stub file in the etc/daemons
directory on all of the nodes which have a resolv.conf file.
Also make sure that /etc/nmconfig exists on each node.  It is this file
which causes the node to query the nameserver instead of looking in
/etc/hosts.  You can also switch this dynamically, which is good
if your nameserver goes down and you want people to temporarily
use the host file: /etc/nmconfig -h hostent_bind tells it to use the
nameserver and /etc/nmconfig -h hostent_ascii makes it use the host
file for ftp, telnet, etc.

Mike 
-- 
Mike Bush
Motorola Codex - Mansfield, MA
bush@cae.prds.cdx.mot.com
Xref: sparky comp.sys.apollo:3444 comp.sys.hp:10018
From: smv@apollo.hp.com (Steve Valentine)
Newsgroups: comp.sys.apollo,comp.sys.hp
Subject: Re: Strange packaging technique
Date: 3 Sep 92 17:53:22 GMT
Article-I.D.: apollo.Bu0KCz.9vx
Organization: Hewlett-Packard Corporation, Chelmsford, MA

In article <BtzApG.1o1@watserv1.uwaterloo.ca> gordon@maxwell.uwaterloo.ca (Gordon R. Strachan) writes:
>The one I always like is the packing lists that list everything in the box
>including the packing list itself!  It even has its own HP part number.  HP
>paper work, you gotta love it! :-)

I recently received several boxes of HP-UX manuals.
The packing lists that came with each weren't self-referential,
and didn't list the bubble wrap and/or plastic peanuts enclosed,
but they did list the boxes!

	Component Part			Description
	9211-6313		CARTON, CORRUGATED, SHIPPING
	...

Recycling note:
	This box also makes a good cheap monitor stand. :-)
-- 
Steve Valentine - smv@apollo.hp.com
Hewlett-Packard Company, Apollo Systems Division, Chelmsford, MA
Hermits have no peer pressure. -Steven Wright
Newsgroups: comp.sys.apollo
From: alek@spatial.com (Alek O. Komarnitsky)
Subject: Re: New DN3000 Owner Seeks Help
Organization: Spatial Technology, Inc. (Boulder, Colorado)
Date: Sun, 30 Aug 1992 03:22:49 GMT

In article <f5fn66m.hbo@netcom.com> hbo@netcom.com (Howard Owen) writes:
>    I bought the machine Michelle advertised here, a DN3000 running Domain 10.2
>
>   Thanks for your attention. I swear I'm one of the good guys. I'll let
>you talk to my mother if you don't beleive me. 8)
Ahh, but you have fallen to the "dark side" by buying an Apollo!  ;-)

Alek Komarnitsky                                      303-449-0649
Software Tools Manager, Spatial Technology, Inc.      2425 55th Street, Bldg A
alek@spatial.com                                      Boulder, CO 80301-5704

P.S. T-3 days until padded van comes to pick up our 12 leased Apollo's and sends
     'em back to HP (replaced with 710's and X-terms; massive improvement! )
From: billy@mana.oz.au (Jeff Coleman)
Newsgroups: comp.sys.apollo
Subject: Specs on a couple of Apollo monitors (Horiz/Vert) ?
Date: Sun, 30 Aug 1992 12:47:15 GMT
Distribution: world
Organization: Private.
X-Newsreader: Arn V1.00 beta rel2

I am wondering if anyone can provide me with some Horizontal and Vertical
scan rates for a couple of monitors i have.

007284 15inc colour. (off DN3000).
       19inc colour  (off DN560).

Has anyone hooked up either of these monitors to any other type of computer?

As a side issue does anyone know if its possible to configure a dn560 to 
output to the 15inc mentioned above..i have connected the 2 together but the
output is still at 19inc and tends to wrap around on a 15inc (doesn't sound
too crash hot - doesn't look it either.)

thanx in advance

Jeff.


  +-------------------------------++-------------------------------------+
  |          Jeff Coleman         ||           billy@mana.oz.au          | 
  |      Canberra, Australia      ||       billy@mana.pub.uu.oz.au       |
  |                               ||..!uunet!munnari.oz!eyrie!mana!billy |
  +-------------------------------++-------------------------------------+
  |    A Silent Member of APANA   || AMIGA - Where Multitasking isn't an |
  |    I represent myself ONLY.   ||              afterthought :-)       |
  +-------------------------------++-------------------------------------+
Xref: sparky comp.sys.apollo:3451 comp.sys.hp:10021
From: snow@netcom.com (Tim Szeliga)
Newsgroups: comp.sys.apollo,comp.sys.hp
Subject: Re: Strange packaging technique
Date: 3 Sep 92 19:09:33 GMT
Organization: Netcom - Online Communication Services  (408 241-9760 guest)


A few years ago, we got a disk drive in a big packing case. To lodge
the drive securely in the box, there was a heavy 20 inch length of 1.5"x1.5"
hardwood.  Stenciled on the side (you're getting ahead of me here),
was the phrase (you guessed it) "HP P/N 19511-80014".  
  Many's been the time when an object (or person) required delicate
adjustment and received a wallop from "the HP Part Number".

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Tim Szeliga	 Org:National Weather Service / Hydrologic Remote Sensing
Voice: (612) 725-3259  			NOHRSC BBS:  (612) 725-3230  (8N1)
UUCP:	apple!netcomsv!frost!tim		Internet: snow@netcom.com
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
From: philip@cel.cummins.com (Philip D. Pokorny)
Newsgroups: comp.sys.apollo
Subject: Re: SCSI on 5500
Date: 3 Sep 92 14:17:34 GMT
Organization: The Internet

David Krowitz says:
> The WD7000 controller supports two ESDI disks, a floppy, and SCSI tape
> drives ... no SCSI disks. This is entirely a software limitation.
> HP decided not to supply the SCSI disk driver for the DN3500/4500/5500
> series.
Perhaps those new SWT guys taking over development of
Domain/OS will look into making the drivers available.  They
really want to prove they are going to do good things for the
Domain/OS customers and SCSI support on DN machines is certainly
high on the list of Frequently Asked Questions... 
Unfortunately, I don't think it was raised at the Engineering
directions at InterWORKS...

Sincerely,
Philip D. Pokorny
philip@cel.cummins.com
:)
From: ccount@boltzmann.mit.edu (Dr. Craig A. Counterman)
Newsgroups: comp.sys.apollo
Subject: Dead power supply (?) on DN10000
Date: 31 Aug 92 16:12:10 GMT
Organization: Electronic Materials Research Group, Cambridge Mass.

A few months ago I asked here about a 'suicidal' DN10000.  It
would randomly turn itself off....  The replys I got all agreed that
the symptoms were those of a power supply needing replacement.

Well, I tried to prepare for the loss of the DN10000, and hoped it
would hold up till the end of the year.

It stayed up for nearly two months (with only software problems
causing a reboot), and then last week we had a power failure.  It came
back from that OK, but about three hours later it turned itself off.
It came back for only a few minutes before going off again.  And now
it powers down a few seconds after being turned on.

I looked at the LEDs people told me about in replys to my earlier
post.  They indicate "VNR under voltage."

So, any way I can repair this myself or at least resurrect it for a
few more months?  Any ideas which component failed, and sources for
this independent of Apollo?  Any companies with used or repaired
Apollo parts?

Thanks for any ideas, it would be nice to get this running long enough
for a graceful transition.

Craig
From: thompson@PAN.SSEC.HONEYWELL.COM ((jt) John Thompson)
Newsgroups: comp.sys.apollo
Subject: re: SCSI disks on 5500?
Date: 27 Aug 92 21:18:59 GMT
Distribution: world
Organization: The Internet



> I've read the faq, but it doesn't make the answer to this question entirely
> clear.  Can I connect an external SCSI disk to a DN5500 with a WD7000
> controller?  If so, is there any limitation on the size (eg 1.2GB)?  Is the
> process for involing etc.. the same as for a 425t?

OK -- let's make it clear then.

You can not hook up any SCSI disk drives to a WD7000 controller.  In fact, you 
can't use SCSI drives on any Apollo machine except the DN2500 (the 9000/4xx is
an HP/Apollo box).

You CAN hook up up to 2 ESDI drives to a WD7000 controller.  There are only 
three (?) drives that are supported, though -- the Maxtor 8760E (697MB), the
Maxtor 4380E (329MB FastActuator) and the Micropolis(?) 170MB drive.  The 
controller can apparently figure out what's on the other end, and act 
appropriately, so there aren't jumpers for the drive type itself.  I think I've
heard that you can add different drive types as your two drives (e.g. a 697MB and
a 329MB drive).  

You CAN install up to 2 WD7000 controllers in your system (DN3500/DN4500/DN5500).
The SCSI bus _must_ be disabled on the second controller.

You CAN install a SCSI cartridge drive or floppy, but only if you do not have a
non-SCSI one in place.  If you have a non-SCSI tape/floppy, you must disable the 
SCSI bus.

If the SCSI bus is enabled, you CAN add up to 7 SCSI devices total of CD-ROMS,
4mm drives, 8mm drives, and 9-track drives.  I'm not sure whether the 4mm drives
are explicitly supported, but I'm almost certain that I read somewhere that they 
work.  I've read that SCSI device 0 is reserved for the cartridge/floppy drive, 
but that might have changed.

The 8mm tape drives must be SCSI ids 1,2,3, or 4.  These correspond to devices
rmts8, 9, 10, and 11 (12-14 for non-rewinding devices).  Although wbak is not
officially supported on 8mm drives, it works fine at 10.3+ (and at 10.2?).  Use
m0 for SCSI id 1, m1 for SCSI id 2, etc.  There is a long pause before it starts
writing the tape with wbak.  The tar and omniback packages work just fine (as do
lots of other vendors' backup packages, I'm sure).


Clearer?

-- jt --
John Thompson
Design Services Engineer / Sys-Admin
Honeywell, SSEC
Plymouth, MN  55441
thompson@pan.ssec.honeywell.com

What do I know?  I'm just a Token Administrator.
*************************************************************************
* This e-mail correspondence is a work of fiction.  Any similarity      *
* between the views presented and actual views, personal or corporate,  *
* living, dead, or still to be conceived, is pure coincidence.          *
*************************************************************************