Conference bulova::decw_jan-89_to_nov-90

    OCALA::MCLEMAN$ cop FIZBUZ""::FIZBUZ$USER:[SAUNDERS.DECW$BANNER]BANNER002.A *
    %COPY-E-OPENIN, error opening
    FIZBUZ""::FIZBUZ$USER:[SAUNDERS.DECW$BANNER]BANNER002.A; as input
    -RMS-E-FND, ACP file or directory lookup failed
    -SYSTEM-F-INVLOGIN, login information invalid at remote node

My IS people bit me again, but its fixed now, although I cant promise for 
how long, until someone changes the object info yet again.

Thanks

	Jim

I need some feedback from people using Banner in a VMS 5.3 cluster environment. 
I particular I need to know if the majority of people are seeing Misc Events 
display in the NI monitor window. On our cluster we are seeing ~ 10 Misc Events 
per second, and there is a question now as to weather it is Banner who is 
giving bad stats, or if we really do have a problem with our network. 

So anybody else seeing high Misc Event counts, and more important anybody
in a cluster environment not seeing Misc Events recorded. 

Thanks for your help,

	Jim

    I'll take a look. 
    
    
    			Pete 
    
    PS banner doesn't work on screen 1 of a two-headed monster.
    

RE:.-1
I have no idea what "Misc Events" are, if you send me the source I will
tell you what the Cells mean. 

Steve Mayhew
	(PEDRIVER maintianer)

    If you have problems accessing the kit via FIZBUZ::, you can access it
    via PAMPAM:: same device/directory. At the moment I'm having trouble
    with my network, and getting invalide login on a very regular basis.
    
    Jim

Any chance  of  getting  a version which works properly on screen 1 of a two
headed  system?  I have found that if I disable the toy then banner seems to
work after producing a number of error messages.  If I leave the toy enabled
then it generates continuous error messages which fill up my disk!

Graham

Fizbuz now is alive and kicking again, so hopefully you have acess to the 
kits again.

re .-1 I'm working on that now, I think I've fixed it, I should have a new kit 
together in a couple of days, for people who want the dual head support.

Jim

Well I fixed all the problems with Multi-headed workstations, this is the same 
kit as the in .0, so if you dont have a multi-headed workstation, there is no
point in copying this kit.

	FIZBUZ::FIZBUZ$USER:[SAUNDERS.DECW$BANNER]BANNER003.A

Jim

So now everybody has got Banner 02 up and running, anybody got any feedback on
the displays, generally, or anything they see missing, which they think would
be usefull?

Jim

    I like the SYSTEM display especially. Good work and all that stuff...

I really like it.  Only problem is that all the neato features keep
increasing real-estate costs on the screen... :-)

Chad

Yes I realize this, real-estate space is an interesting problem, the system 
display completly replaces the monitor display, so through customization you
can select the items which best fit you needs, thus making best use of the 
real-astate space you want to use. But if anybody has better ideas, on how to 
display the present information, (In graphical terms), using the 
least amount of real-estate space as possible I would be very interested in 
hearing them.

Jim

    SOmewhere can you show the boot time? Say in the Processes window next
    to the node name.

    re .10:
    
    Here's something that bugs me. On the process display, there is the
    line that says how many network, interactive, etc. processes there are.
    It would be very nice if it didn't mention a class of processes that
    is zero. I rarely have any outswapped processes, but often this will
    bump other things (like the net processes) out of the window. I don't
    mind being told that I do have outswapped processes, but I don't think
    that it's important to know there's none.
    
    	Jon

There seem to be some off by one errors in saving the sizes and/or positions of
some of the windows.  Specifically, I've noticed this on the Processes window
and the System window.

Wook

If you resize the hanoi window too much, it crashes with an access violation.

On my system, the box doesn't rotate, it bounces around in a disturbing
pattern.

Why are Hanoi, Globe, and Box mutually exclusive?  I'd be happier with
enabling and disabling them as separate windows.

I have Banner installed with the necessary privs, yet, when I try to start it
up automatically from the Session Manager, it draws the windows (the CPU graph
and the Page IO window) and then crashes when it tries to update them the first
time.

Currently, I have to run it as a detached process, also started from the Session
Manager.  Here it shows different behaviour - it starts up fine, but doesn't
update for quite a while.  I can kick it off by suspending and then resuming
the process, or I can wait, and it starts up by itself eventually.

And one I just noticed right now - if I double-click on the icon (no active
icons), it pops the main banner window, but I have to iconize and de-iconize
completely to get it to pop all windows.

Also, if anyone knows how I persuade the Banner message window to display
broadcast messages when started from the session manager, I'd love to know.

Apart from the above, I love what Banner does for me.  I keep it simple, and
it's very useful.

Thanks,
-- Paul.

re .-2

	Banner just asks for the X,Y co-ordinates of the window when it needs to
save the sizes etc. I've seen many problems here, where the widget structures do 
no seem to have valid X,Y possitions some times. Mostly when you do a re-size, 
from the top left corner. There is unfortunatly not much I can do if I get 
returned wrong co-ordinates I just dont know it.

re .-1

	The hanoi toy works in replay mode, it recusivly works out the solution,
storing all the moves in memory, and replays the moves. What you are actually 
seeing is not an ACCVIO but an error, out of VM, and Banner exits. You can 
increase your page file quota, but the standard size, normally allows you to get up to
~7 Disks, if you create a window that allows more, you are likely to run out
of VM. I cant recover from this, because the VM allocation routines are now 
dead, and I need them in other parts of Banner.

	The problem with the cube, has only come about because of performance 
inhancements in the server. I need to put some XSync's in! Before with uVax II's
the server could never process all the line drawing the cube generated, so 
everything worked O.K, but now on the bigger machines the server can keep up, 
and seems to optimize away some of the lines I'm drawing thus defeating the 
object of the cube. 

	I could make all the toy display allowable at the same time, but as the 
cube/hanoi can each take every second of free CPU, running them both on the same
machine, just wouldn't work, they would look pritty bad, but maybe I'll allow 
them to be active at the same time anyway. 

For all the other comments, thanks a lot, I'll see what I can do to fix them
in the next version, which will probably be when I need to produce a kit to 
support a new VMS version. 

Jim

All your problems are revolving around the Auto-start feature. To be quite 
honest, you cant really start Banner via this mechanism. If you do, you can 
never have message trapping, because banner is running as a detached process
and cannot find a terminal device to trap broadcasts from. This is also why you 
see this long pause, when you run banner detached. Banner waits for upto 
~3 minutes to see if its parent creates a device it can trap messages via, 
after that it gives up, and forgets about message trapping. Also banner 
requires a lot of priv's so to run it detached from auto-start, banner must
be an installed image, with these priv's otherwise it exits the moment its 
displays are painted. Hence the problems your seeing. 

Now what can you do :-

	1. Install Banner with the priv's it needs, and accept the fact you 
cant have message trapping! Then you can use the Auto-start feature to start
Banner. 

	2. Use DECW$LOGIN.COM, and spawn Banner as a sub process of the 
session manager. Now everything will work just fine, as long as you turn on 
priv's before the spawn, or install banner with the correct priv's.

Sorry about this, but I still have not found a good way of trapping broadcaste
messages, that would allow Banner to be a detached process. 

Jim

Jim,
	Thanks for setting me right on the Message window - I guess I can live
without it!

On the Autostart problem, now that I know about the pause on startup, it doesn't
bother me, but I still think I should be able to Autostart Banner.

The image is installed with CMKRNL, SYSNAM, PRMMBX, ALTPRI, WORLD, and SYSPRV
privs, and if I use a command like MC DECW$BANNER for Autostart, it will fail.

If I use a RUN/DET/AUTH/IN=X.COM/OUT=NL:/ERR=NL: SYS$SYSTEM:LOGINOUT then
everything works.  I'd rather not have to create two processes every time I want
to start up Banner (one for autostart and another for Banner), so any ideas on
this would be appreciated.

Thanks in advance,
-- Paul.

P.S. I also want to know how to set the process name on an Autostarted
application, but I think that deserves a new topic.

I really dont know, I just tried it myself, and I get the same problem, it
does not seem to be concerned with priv's. And I dont know where the session 
manager puts the log of auto-started apps? I wonder if it is the output to 
sys$output that banner makes, which is causing the problem. Does anyone 
know how to get a log of what happened to the application, once it is started 
by the session manager?

Jim

    RE: .21

    I routinely start BANNER from autostart.  I found that I have to have a
    .DAT file for it that specifies no broadcast message window though, or
    else it dies.  This was documented a few replies back though, and I
    don't miss the broadcast message window.  BANNER pops right up with
    no delays.

    I do however, do it a little differently, which might account for why
    it works for me.  It also solves your process name problem.  Instead
    of running an application directly from the autostart menu, I specify
    a DCL command file with the application name as a parameter.  This
    command file sets up a process name based on the application name,
    and then runs the application.  Send me mail if you want a copy of it.

                 Dave

    I autostart BANNER with "RUN SYS$SYSTEM:DECW$BANNER" with no
    problems.  I don't use the message window.  BANNER starts immediately.
    
    				-John

OK, I can live with that.  Since the message window is unusable from Autostart,
and I don't intend to use Banner in any other fashion, I guess I can disable the
message window without suffering too much hardship!  :-)

Re: .23

Thanks for the offer Dave.  I was rapidly coming to the conclusion that that
was how I'd have to exercise any control over the created process.  For the
moment I think I'll let it ride as it is, and see if anything changes in future
versions of DECwindows.

Thanks for the help everyone,

-- Paul.

P.S.  Dave, the folks in ELKTRA::DW_EXAMPLES might like to see your command
procedure.  Just an idea...

Jim, I can maybe shed a little light on the problem. The message
window crash also occurs if you try to run BANNER out of Fileview.
Only Fileview is kind enough to display SYS$OUTPUT for you. I got
the following:

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000003                00000000
        Name   = 0000044C                000E0000
                 7FF39B7E                7FF39AC8
                 03C00000                7FF39AA4
                                         80121AF3
                                         7FF39B7C
                                         00000003
                                         7FFEDC1C
                                         00000005
                                         7FF39B24

        Register dump

        R0 = 80306D20  R1 = 7FF39B7C  R2 = 00000003  R3 = 7FFEDC1C
        R4 = 80267670  R5 = 00000001  R6 = 00000000  R7 = 00000001
        R8 = 00000001  R9 = 00000000  R10= 0060000E  R11= 0060000C
        AP = 7FF39A38  FP = 7FF399F8  SP = 7FF39A6C  PC = 7FF39B7E
        PSL= 03C00000

(I'm running VMS V5.3, BANNER002.A.)

I think you're going to have to go after this with the debugger.
Some hacking of DEBUG logicals may be necessary to get DEBUG to
talk to you out of the Fileview environment.

Hmmm....

	Yep Reserved Operand fault, Thats a new one, Banner used to work fine
under fileview, Ill have to take a look at this, and try to see what has 
caused the problems.

Thanks for the info

	jim

I just installed the 5.3 version of the DECW$BANNER (note 1609) and, when I run 
it from Session Manager, FileView or DCL Command, I get the following stack 
dump.

Other notes refer to old copies of banner data files as being the culprit so I 
renamed every reference to anthing that I could find (*BAN*) in SYS$MANAGER, 
SYS$SYSTEM, SYS$SHARE, SYS$LOGIN, DECW$USER_DEFAULTS (did I get them all?) 
to *_OLD.* (Deleteing is so FINAL), reinstalled BANNER, QUIT and logged back 
in again to no avail. :^(   I even ran in from a loaded-gun-aimed-at-foot (full
privs) account in case it was a priv problem (I didn't think so, but, what the 
heck, privs are cheap)!

Now for our configuration:
	VMS 5.3 (SDC) with the DECWindows that come with it
	Bootnode: Config-5 (Micro-vax II)
	Satellite VS2000  w/ 6mg. (no cracks, please!)

Any thoughts?

--dave--


%SYSTEM-F-OPCDEC, opcode reserved to DIGITAL fault at PC=7FF3377E, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000003                00000000
        Name   = 0000043C                00000000
                 7FF3377E                7FF336C8
                 03C00000                7FF336A4
                                         8014C4F3
                                         00000005
                                         7FF33724
                                         00000001
                                         803C1300
                                         7FFEDFFE

        Register dump

        R0 = 803C1300  R1 = 7FF3377C  R2 = 00000003  R3 = 7FFEDC1C
        R4 = 802BCF80  R5 = 00000001  R6 = 00000000  R7 = 00000001
        R8 = 00000001  R9 = 00000000  R10= 0020000E  R11= 0020000C
        AP = 7FF33644  FP = 7FF33604  SP = 7FF33678  PC = 7FF3377E
        PSL= 03C00000

The RES OP Fault is comming out of SYS$SETAST, when ever the device owned by
the parent process is not in fact a terminal device. Please dont ask me why 
this is happening, because I really dont know why this should be happening. 
At any rate I'll build a new kit, which checks out the device type before
trying to allocate it, in the mean time, if you are going to run banner
from things like VUE, you should first run it in a normal DECTERM, and 
use the SETUP menu, to turn off the message window facility. Remember to 
save these settings, then you should be able to run it from Vue or from
the session managers auto-start facility.

Sorry for this, this is a new bug, and I really dont know why it should be
causing problems with SYS$SETAST, just because the device I'm trying to
allocate like a terminal, is not in fact a terminal.

Jim

Jim,

No need to apologize.  If everything worked the first time, we'd be bored and
would learn nothing!  I tried it from a DECterm (must have been the only
avenue I didn't take) and it worked fine.  Got rid of the message window, saved
and Voila! no more problem when run from session manager.  So far it looks good!

Now to play.......

--dave--

    
    I have a question about the new System display:
    
    What does it mean when the nodename (positioned between the 25% and
    75%) changes from "node" to "node - (P)"?  What causes it?
    
    Thanks in advance,
    
    		- Valerie
    

    There are two status flags that can be displayed here, 'M', and/or 'P', 
    they refer to status information about the NI port (Your eithernet 
    connection), and the IO's that are outstanding on the NI port. 
    
    P - stands for outstanding IO's to the NI port, eg: you have IO's 
    	requested to a remote disk, that have not yet been satisfied. 
    	If it happens a lot, the eithernet is saturated.
    
    M - stands for outstanding IO's to a remote disk that has gone 
    	off-line, normally happens when a satalite crashes.
    
    Jim

Is there some way I can have another process write messages into Banner's
message window? I seem to remember some documentation telling how to do
something like that but I can't seem to be able to find it.  Is there such
an animal?

Thanks,
-Mike

There are two basic ways :-

o	Send a broadcaste to the user owning the Banner process.

o	Open the mailbox created by Banner "BANNER$MAILBOX", and then 
	write your message to the mailbox, and close it afterwards. 

Both of these should work, although I must admit it is a long time since 
anyone has tried doing this. Let me know if you have any problems. 

Jim

For anybody who is interested in playing in the XM world, an XM version of 
Banner is now available. Very little change can be seen, just the style of the 
the dialog box's etc. Note also, that since the XM world is object libraries, 
and not sharable images, the Banner kit is very big, ~20000 blocks. 

This kit also only works effectivly if you are running the XM window manager, 
due to some minor differences between the Xm window manager, and the DEC window
manager. 

The kit can be copied from :-

	FIZBUZ::FIZBUZ$USER:[SAUNDERS.DECW$BANNER]BANNERXM004.A 

Jim

It sure would be great to see the Image Name listed by each process in the 
process display (as an option of course).

e.g. something like

	WESTBROOK	WESTBROOK_SM8	NOTES		20% *****
	SYSTEM		DECW$SERVER_0	DECW$SERVER	18% ****
	WESTBROOK	WESTBROOK_SM5	DECW$MAIL	5%  *
	SYSTEM		VPA_DC		VPA		1%

would really be great, and would alleviate my having to write .com files to
set process names that duplicate the image name anyway.

Can it be done?
Eric

Yes thats not a bad idea, I'll see what I can do to make it an option on the 
process display.

	Jim

    One thing that I would like to see is something like NCP SHOW KNOWN
    LINKS. Often I will see a MAIL_1234, FAL_1234, or NETACP in the CPU
    display and I will pop up terminal window to do a SHOW KNOWN LINKS to
    see who is doing what.  It would be nice if the display were like the
    CPU display, but it will be static for long period times with
    relatively short periods of interest. Hmmm... for network processes (N
    on a SHOW SYSTEM) could more info be displayed in the CPU display
    (NODE::USER) ? I'm just thinking out loud... anybody else have ideas
    about how it could work?
    
    						- Alan

I would love to put in this display, and have hunted for ways to get this info. 
Unfortunatly I came to the conclusion that the only person who knows anything 
about network links is NCP? I do not unfortunalty have the time to go through 
NCP sources and work out where this info is, so if anybody in the know can pass 
me an example piece of code that would be capable of gathering this info, I will
be all to happy to put this  (In one form or another) into banner, since I 
cosider it as one of the big missing items. Unfortunalty unless someone can show 
me how to get this info, I dont see much chance of me being able to incorperate 
this info into banner.


Sorry

	Jim

I think you'll have to talk NICEly .. I may have some code
fragments hanging around

	Grab the code frags out of WHAT. It allows you to do just what
	you want.. (monitor links)

WHAT (VMS V5)            5.4     SUBWAY::WHAT$KIT:WHAT054.A
WHAT sample collector routines   SUBWAY::WHAT$KIT:WHAT_EXAMPLES010.A

						mike

    Keep in mind that it's a short-lived optimization, as network
    management changes completely with Phase V.

.16 reported that window coordinates are not saved correctly;  it was replied
that DECwindows doesn't report the coordinates to BANNER correctly.  I experi-
mented (using xwininfo from an Ultrix client), and found out that you're right!
Whatever mechanism xwininfo uses to get window coordinates lies to it, also.

I've been using the Motif window manager on my server.  This let me easily de-
termine the actual coordinates of the windows arranged the way I like them.
I hand edited these coordinates into DECW$BANNER.DAT and restarted BANNER--it
placed all of the windows correctly _except_ the clock window.  I checked, and
found that the coordinates were specified correctly.

Well, at least it got all the rest of them right--previously _none_ of the four
windows I use came up in the right place.

A nice addition to BANNER would be the addition of overriding resource names for
window positions--that way I could hand-edit the positions in and not have them
change if I decided to modify some other parameter.

My DECW$BANNER.DAT follows:

DECW$BANNER.hanoi:	0
DECW$BANNER.lck_window:	0
DECW$BANNER.cube_y:	735
DECW$BANNER.message_y:	109
DECW$BANNER.bell_volume:	50
DECW$BANNER.disk_2:	XQA%d:6
DECW$BANNER.seconds:	1
DECW$BANNER.font_family_size:	10
DECW$BANNER.cwps_window:	0
DECW$BANNER.cpu_update:	2
DECW$BANNER.digital_clock:	1
DECW$BANNER.cwps_height:	104
DECW$BANNER.process_x:	0
DECW$BANNER.process_update:	0
DECW$BANNER.analog_clock:	1
DECW$BANNER.title:	Banner
DECW$BANNER.cpu:	1
DECW$BANNER.monitor_update:	0
DECW$BANNER.cube_height:	104
DECW$BANNER.dua0:	1
DECW$BANNER.message_width:	852
DECW$BANNER.world:	0
DECW$BANNER.clock_x:	498
DECW$BANNER.icon_on:	0
DECW$BANNER.cpu_x:	685
DECW$BANNER.sysflt:	1
DECW$BANNER.sysrespgfile:	0
DECW$BANNER.freeiocnt:	1
DECW$BANNER.disk_1:	dua1:,dua2:
DECW$BANNER.cpu_y:	735
DECW$BANNER.pe_width:	158
DECW$BANNER.process_y:	735
DECW$BANNER.pe_update:	0
DECW$BANNER.multi_hist:	0
DECW$BANNER.dua1:	1
DECW$BANNER.clock_y:	735
DECW$BANNER.disk_0_name:	System IO
DECW$BANNER.ni_io:	0
DECW$BANNER.pe_height:	104
DECW$BANNER.message_window:	1
DECW$BANNER.hwmrk_update:	180
DECW$BANNER.sys_width:	236
DECW$BANNER.process_width:	247
DECW$BANNER.process_name:	1
DECW$BANNER.sys_update:	0
DECW$BANNER.sys_height:	104
DECW$BANNER.sys_x:	254
DECW$BANNER.freeblkcnt:	0
DECW$BANNER.cpu_width:	164
DECW$BANNER.lck_x:	341
DECW$BANNER.cpu_height:	104
DECW$BANNER.sys_y:	735
DECW$BANNER.message_height:	140
DECW$BANNER.cube_width:	181
DECW$BANNER.base_priority:	0
DECW$BANNER.sys_window:	1
DECW$BANNER.lck_update:	0
DECW$BANNER.clock_width:	179
DECW$BANNER.dua2:	1
DECW$BANNER.mp:	1
DECW$BANNER.process_user:	0
DECW$BANNER.sys_highlight:	75
DECW$BANNER.disk_1_name:	User disks IO
DECW$BANNER.process_pid:	1
DECW$BANNER.message_size:	100000
DECW$BANNER.lck_y:	735
DECW$BANNER.mon_x:	860
DECW$BANNER.cube:	0
DECW$BANNER.lck_width:	163
DECW$BANNER.process_height:	104
DECW$BANNER.mon_y:	735
DECW$BANNER.bars:	1
DECW$BANNER.clock_height:	104
DECW$BANNER.border:	1
DECW$BANNER.cwps_update:	0
DECW$BANNER.fp:	1
DECW$BANNER.process_states:	0
DECW$BANNER.pio:	1
DECW$BANNER.iocnt:	1
DECW$BANNER.disk_2_name:	Decnet
DECW$BANNER.message_hide_timer:	0 00:01:00.00
DECW$BANNER.lck_height:	104
DECW$BANNER.monitor:	1
DECW$BANNER.mon_width:	160
DECW$BANNER.mon_height:	104
DECW$BANNER.cwps_x:	512
DECW$BANNER.process_window:	1
DECW$BANNER.message_init_state:	1
DECW$BANNER.message_x:	104
DECW$BANNER.window_border:	1
DECW$BANNER.cpu_count:	67
DECW$BANNER.bell:	1
DECW$BANNER.font_template:	*-ADOBE-%s-%s-R-Normal-*-*-%s0-*-*-%s-*-*-*
DECW$BANNER.pf:	1
DECW$BANNER.pe_window:	0
DECW$BANNER.disk_0:	SYS$SYSDEVICE:
DECW$BANNER.modes:	1
DECW$BANNER.highlight_colour:	red
DECW$BANNER.pe_x:	856
DECW$BANNER.cwps_y:	735
DECW$BANNER.pe_y:	735
DECW$BANNER.sys_ioratemax:	50
DECW$BANNER.cwps_width:	178
DECW$BANNER.cube_x:	192
DECW$BANNER.sys_faultratemax:	100
DECW$BANNER.font_family_name:	ITC Avant Garde Gothic

An ammendment to .43--the problem seems to be intermittent.  BANNER hasn't fail-
ed to position the clock window properly in a couple of tries.

Hi;

	I have a VAXstation 3100 (VMS 5.3, DECwindows 2.0). I would like to run
BANNER. Is there anyone out there who can point me to BANNER in .EXE format? I
am not terribly familiar with VMS, etc.

	Thanks...

Robi.

    The BANNER kit listed in reply .9 of this note is a VMSINSTALable
    kit, that is, you install it like a VMS layered product.  I would
    suggest that you take this approach, since the BANNER installation
    links the .EXE for your workstation during installation.  BANNER
    is very VMS version dependant, because it needs to get data from
    internal VMS data structures.  These tend to change from one VMS
    version to the next.  Installing the kit won't be any harder than
    copying someone else's .EXE file.  Also, there are more files
    required for DECwindows usage than just the .EXE.  Trying to
    piece them together manually would be difficult.

                  Dave

re: .15

I agree that this is a minor problem.  Could we simply left justify the line 
with the process counts in it, rather than (apparently) centering it?

I run banner with an 80 column DECterm left justified on the screen, and have
the process display next to it, extending off the screen to the right.  I can 
see everything interesting except the end of the summary line.

John

Regarding the 'SYSTEM' display.

    Why do some 'classes' have two thin lines and some one fat line ? For example
    the disks seem to have two lines each. In my case, I have disk0 defined as
    "DFSC%d:15" and I have a line all the way to 100% and a line which reflects
    the traffic across the DFS disks.

    The same question about the 'memory' lines. Why two ? What do they mean ?
    Likewise 'page file'.

Thanks for any explanation you can give

Ross

Ps. On the "PROCESSES" display, why do some bits go to the highlight colour some
    of the time ?

    Why do the banner windows stay on top of the other windows ?
    How do I force them to the BACK ?
    
    Philip Ritz

re .48

	The classes which have two thin lines, are classes that display two
sets of information. For instance, on disks they display the %ulitization on 
the uperhalf, and the physical IO rate on the lower half. Some of the other 
classes dislay thing like, Page IO, and Page file usage, Remote IO, and Physcal
page file IO etc. Memory is physical memory utilization, and modified page 
ultilisation etc. 

	With your DFSC disks, I suspect that you are seeing the utilizated 
space as 100% because the DFSC driver is not returning accurate information
and disk occupancy, although I have never witnessed personally. 

	The highlighted colours on the process display is when items change 
there state, eg: Top CPU user highlights when it changes, the number of 
processes in the particular process states highlight when it changes. And the 
title bar highlights if any of the information in it changes.

re .49

	This is a question of window managers, I supose that you are running without
window title bars, which means the window manager has been told to keep its
hands off the banner windows. As such the window manager does not accept to 
do anything with the windows. Now depending on the window manager you get 
different effects here. If you are using decwindows the windows will always 
be on top, and there is nothing I can do about that at all. If you are using 
motif then the windows will be on top of any that where created before them, 
and below any created after them. In this case it is quite nice, since if 
banner is one of the first things activated when you start a session, its 
windows will stay below all others. In both cases it this an action of the server
and the window manager, and as far as I can see, there is nothing I can do 
to change this behavour. 

Jim

With DFS you will indeed not see a meaningful "percentage used" statistic.
That's because a DFS "device" does NOT correspond to an actual device, but
rather to a part of the file system hierarchy.  In that definition the
notion of "free space" is meaningless.

	paul

    I'm running DECwindows V5.3.  I looked on FIZBUZ and found that
    0.5 is the only version there.  Can that be installed on V5.3? 
    If not, can 0.3 be put back in the directory?
    
    	Thanks!
    		David

    I keep old versions on node CIMTWO::DECW$PUBLIC:[BANNER].  You can
    copy them from there.

              Dave

    Directory CIMTWO::DECW$PUBLIC:[BANNER]

    BANNER001.A;1        1575/1575    28-AUG-1989 11:48:02.00
    BANNER002.A;3        2205/2205    19-OCT-1989 16:32:26.00
    BANNER003.A;2        2268/2268    28-DEC-1989 15:35:52.00

    I'm running BANNER003 on VMS T5.4-4GE and get some strange results. 
    First of all, only about half the windows pop up (lower display
    windows) and I get this error:
    
    %DCL-S-SPAWNED, process DECW$BANNER spawned
    
    Ni access routine rreturned bad status!
    
    This is being run on a satellite in a LAVc.
    
    Mike
    

    Did you perhaps do a VMS upgrade since last installing BANNER?
    Banner should be reinstalled after every VMS upgrade, since it
    links against some internal VMS stuff.

                Dave

re .54

	Use the Setup options to customise which display you want to see, 
this can be accessed via the MB2 popup menu. As for the error message, 
this could be due to the fact that the NI port addresses have changed again, 
something which happens on a regular basis. I'll have to wait until I find a 
4-4ge system, and see if this is true. If this is true, then there is basicly no
NI monitor untill I can find the new offsets.

Sorry

	Jim

    There were no upgrades to VMS since Banner was installed.
    
    -1 sounds like the problem.
    
    Mike

    VMS T5.4-4G1 with full decw programming support: not only are there
    errors in the installation, but it continues and produces a non-usable
    BANNER (the banner windows appear then die; the banner process
    continues).
    
    
            Beginning installation of BANNER V0.5 at 17:19
    
    %VMSINSTAL-I-RESTORE, Restoring product save set A ...
    
    %BANNER-I-DECWBANNER,  Installing DECwindows Banner
    
    * Do you want to purge files replaced by this installation [YES]?
    
    %BANNER-I-LINK1,  Building the DECwindows Banner image.
    
    %LINK-W-NUDFSYMS, 3 undefined symbols:
    %LINK-I-UDFSYM,         DXMCREATEHELP
    %LINK-I-UDFSYM,         DXMHELPWIDGETCLASS
    %LINK-I-UDFSYM,         DXMHELPWIDGETCLASSREC
    %LINK-W-USEUNDEF, undefined symbol DXMHELPWIDGETCLASSREC referenced
            in psect $CODE offset %X00000019
            in module MRMINIT file
    DKB0:[SYS0.SYSUPD.BANNER005]DECW$MOTIF$MRM.OLB;3
    %LINK-W-USEUNDEF, undefined symbol DXMCREATEHELP referenced
            in psect $CODE offset %X0000001F
            in module MRMINIT file
    DKB0:[SYS0.SYSUPD.BANNER005]DECW$MOTIF$MRM.OLB;3
    
    %BANNER-I-HLB1,  Building the DECwindows Banner help file.
    
    %LIBRAR-S-INSERTED, module OVERVIEW inserted in
    DKB0:[SYS0.SYSUPD.BANNER005]DECW
    $BANNER.HLB;1
    
    %BANNER-I-FILES,  Defining target directories for DECwindows banner
    files.
    
    
            The installation of DECwindows Banner has completed. DECwindows
    Banner requires the following privileges to operate correctly.
    
            CMKRNL, WORLD, SYSPRV, SYSNAM, PRMMBX, ALTPRI
    
            If you wish the run DECwindows banner from non-privileged
    accounts,
    the image SYS$SYSTEM:DECW$BANNER.EXE must be installed with the above
    priveleges. Refer to the online help, accesable via the MB2 popup menu,
    for
    further information on DECwindows Banner.
    
            The most efective way of runing DEcwindows Banner is to add the
    following lines to your SYS$LOGIN:DECW$LOGIN.COM
    
            $SET PROC/PRIV=(CMKRNL,WORLD,SYSPRV,SYSNAM,PRMMBX,ALTPRI)
            $SPAWN/NOWAIT/PROC=DECW$BANNER RUN SYS$SYSTEM:DECW$BANNER.EXE
    
            Note: If you have installed the DECW$BANNER.EXE with the
    necessary
    privileges it is not necessary to turn on privileges in the
    DECW$LOGIN.COM
    file.
    
    %VMSINSTAL-I-MOVEFILES, Files will now be moved to their target
    directories...
    
            Installation of BANNER V0.5 completed at 17:22
    
    
            VMSINSTAL procedure done at 17:22
    
                                                                                     

The 005 kit was not for wide distribution, although many people seemed to have 
copied anyway. You should copy the BANNER006 kit off the netwrok, this 
one will work correctly, with the possible exception of the NI monitor on V5.4 
systems.

Jim

>    VMS T5.4-4G1 with full decw programming support: not only are there
>    errors in the installation, but it continues and produces a non-usable
>    BANNER (the banner windows appear then die; the banner process
>    continues).

I'm running the motif window manager, so I don't know if this will work,
but when you run BANNER, if you iconify the main banner window before the
other windows are managed, banner works.  There is a new version, V0.6
which may solve the problem, but you'll have to try it and see.

Wook

    V0.6 does not have this problem any longer, it was caused by a slight 
    missunderstanding between Banner and the window manager, in that 
    Banner unmmaped its root window, because it didnt need it displayed, 
    and the window manager unmapped all the others that were spawned from 
    the root window. As I said, the BANNER006 does not have any of these
    problems any longer. 
    
    	Jim

    I just installed BANNER006 and it appears that the NI errors have gone
    away.  Everything is up and running, which is a lot more than what
    happened before (i.e., nothing). 
    
    One question though, is the full file spec supposed to be in the icon 
    bar at the top in the icon box?
    
    Mike

No its not ment to be there, but I ported Banner over to the Motif toolkit about
2 months ago, and I'm still having problems ironing out some of the more nitty
problems. Banner is done on a free time/good will basis, which means it doesnt get
the attention it deserves. Hopefully one day I will find eneugh time to fix 
the host of nitty problems with the UI under Motif. 

Jim

    no problem, I can fix it myself.
    
    Mike

    Please let the rest of us know how to fix it too!  It's a real pain to
have the banner icon take up so much of the icon box, but I LIKE having the
banner displays up.
						Wayne

    Re: -1 
    
    Wayne, I'm not a DECwindows heavy either, but I can handle some minor
    things.  It looks to me like the icon name "Banner" is properly defined
    in BANNER.C.  I'm not sure why it isn't being displayed.
    
    Mike

>       <<< Note 1609.63 by FIZBUZ::SAUNDERS "A WINDOW in any Language" >>>
>                   -< Some people are just never happy :-} >-
>
>No its not ment to be there, but I ported Banner over to the Motif toolkit about
>2 months ago, and I'm still having problems ironing out some of the more nitty
>problems. Banner is done on a free time/good will basis, which means it doesnt get
>the attention it deserves. Hopefully one day I will find eneugh time to fix 
>the host of nitty problems with the UI under Motif. 
>
>Jim
>

I suspect the problem is that Banner is just letting the title bar string
default, rather than explicitly setting it.  The version of the Intrinsics
used with the current (DECwindows V1, V2, V2.1) XUI toolkit used the
application name passed in the XtInitialize call.  The MIT R3 Intrinsics
(used by the Motif 1.0 toolkit) and the new R4 Intrinsics used in DECwindows
V3 don't use the application name.  If the title isn't explicitly set, you
get the filespec of the application exe (actually I think the window manager
code does some U*ix specific hacking on the filespec to remove everything
preceding the last "/", so it may look different on Ultrix systems).

You need to do something like:

    XtSetArg(arglist[0], XtNtitle, "Banner");
    XtSetValues(Toplevel_Widget, arglist, 1);

The problem seems to come around from the name changes I made to the X resources
files for Banner. Since then now contain the node names of the node running banner
the resource manager nolonger loads the resources for banner. Until I find a fix
here is a workaround. Create a file SYS$LOGIN:DECW$BANNER.DAT and add the following
lines to it. Remove the lines for foreground and banckground if you wish to 
continue using your default window manager colors. 

DECW$BANNER.iconName : Banner
DECW$BANNER*foreground : blue
DECW$BANNER*background : green


This should fix your problems with the icon name, and colors used by banner

jim

    Thanks!  Setting iconName in DECW$BANNER.DAT works.  It's nice to have
room in the icon box again.

					Wayne

	I'm sure this is a pipe dream, but it sure would be nice if you
	could tell Banner to display some of its windows on one display
	and others on another.. I have a two-headed (color and B&W) VS3100
	and some of the banner windows I'd like to see on the B&W monitor
	and some on the color.

	Just a pipe dream?

							mike

    Re .70, i can do it now. Actually, i have three different Banner
    displays (read 3 DECW$BANNER.EXE images) on two heads. It's just the
    matter of defining SYS$LOGIN to include the right subdirectories
    containing the different .DAT files.
    
    --svb

My apoligies if this has been asked already but I didn't see it...

  I upgraded to SSB V5.4 the other day and installed the BANNER006 kit.
When banner was up and running I switched over to ACTIVE ICONS and
restarted banner. I found that each display no longer has an individual
icon box. That in itself is no problem for me but the ability to resize
windows no longer functions!

  It nice to be able to change the font and font size but if the new sizes
make the info bigger than the size of the window I lose infomation due to the
inablility to resize...  Can I do anything to resize windows? Do I need
another window manager to get the resize ability?

  I love Banner and I'm not knocking it but losing the icons & resize seems
like a step backward in some ways...
					Thanks for any help,
					       Craig

BTW I use a 14Mb VS200/GPX with 4-plane...