Conference bulova::decw_jan-89_to_nov-90

    re .0
    
    Quick question - What is the easiest way to set the icon name. By
    default now, it seems to be using the decw$banner.exe pathname as the icon
    title name.
    
    
    							Thanks
    							-mike-

I dont know, this kit is based on Motif code, and I've still got some minor 
problems like Icon names, and Resize etc. I think there is a resource you can 
throw into the resource file which will patch the Icon name, but I'm not sure 
what its called.

Alternatly turn of banner borders, then you wont have an Icon any longer. Also
mean you will use less display area, and youcan use the 'Goto minimum' option
on the banner menu, to shrink banner to an Icon display.


Sorry

	Jim

I have some problems with the new version. I'd appreciate any help or pinters.

a) How can I get Banner's background color to change? I tried to but
	DECW$BANNER.background into the resource file which is in
	SYS$LOGIN. I tried both the '.' and the '*'. I also tried
	upper and lower case beginning letter for background. It all
	the time comes up in the color my icon box is set too.

	Changing the font family by the way works. That means the resource
	file in my directory is being looked at.

b) When I run banner from my account it works fine. But if I start via
	the session manager with the following file:

	$set proc/priv=(cmkrnl,world,sysprv,sysnam,prmmbx,altpri)
	$run sys$system:decw$banner

	Banner comes up (windows appear), but then,puuff, everything goes
	away without leaving a trace.

	Any ideas what I could do wrong?

I appreciate any ideas!

Thanks
	THomas

    re -1
    
    a) I think the DECW$BANNER resource name isnt working any longer in the 
    resource file, looks likethe application class name is getting set some
    other name. Try adding lines of the for *forground, *background to the 
    resource file to see if this has the desired affect.
    
    b) Do you have message window selected as active? I suspect it is the
    problem where if banner fails to find a mailbox to catch broadcaste 
    messages from, it blows away. I thought I  had caught that problem,
    but this sounds similar. Try turning message trapping off, and then see
    if the problem goes away. Alternatly spawn it from DECW$LOGIN.COM, 
    and not from auto-start, where Banner will find the session manager
    mailbox, and can still trap broadcatse messages. 
    
    Jim

- The color problem has been solved by removing a *background in DECW$SM_COLOR.DAT.
	Of course this has impact on other applications too, but the default
	color I like better now. There was no way to tell BANNER to use a
	different color.

- My DECW$BANNER.EXE has image version of T0.05. Is this what should be in
	BANNER006.A? That's where I got it from. I am little confused, because
	I expected to ses T0.06!

- Banner also stays alive now after I removed the message display in the setup.

- But when I clicked on SETUP the setup window appeared AND in my login window
	the following messages appeared:

		X error event from server: BadMatch - parameter mismatch
		...major opcode: 42 (X_SetInputFocus)

	Then I deselected the message window and clicked on apply and then OK.
	The stuff was saved (I heared the disk! ;-)) and a window appeared
	saying 'Setting saved' (or similar). In this window I clicked on
	OK. Then the window manager told me that it was confused!

- I am also running with the large fonts. This results in the fact that in the
	setup window some things write over one another and that some are not
	settable because of that, like the batch and print things.

Thomas

>- The color problem has been solved by removing a *background in DECW$SM_COLOR.DAT.
>	Of course this has impact on other applications too, but the default
>	color I like better now. There was no way to tell BANNER to use a
>	different color.

This is probably a resource naming problem, I'll have to take a look and 
see why colors in banner's resource files arnt overiding the defaults any 
longer.

>- My DECW$BANNER.EXE has image version of T0.05. Is this what should be in
>	BANNER006.A? That's where I got it from. I am little confused, because
>	I expected to ses T0.06!

My fault I forgot to to change the link ident when I built the kit. It is 
really a T0.6 image.

>- Banner also stays alive now after I removed the message display in the setup.

Look like I'll have to take another look at this problem, I thought I had got 
it this time.

>- But when I clicked on SETUP the setup window appeared AND in my login window
>	the following messages appeared:
>
>		X error event from server: BadMatch - parameter mismatch
>		...major opcode: 42 (X_SetInputFocus)
>
>	Then I deselected the message window and clicked on apply and then OK.
>	The stuff was saved (I heared the disk! ;-)) and a window appeared
>	saying 'Setting saved' (or similar). In this window I clicked on
>	OK. Then the window manager told me that it was confused!

Yes I've seen this, its due to banner trying to force input focus on the setup
window, for when you are running in borderless mode, it seem to cause this 
error, when you have window borders turned on. Its not important, everything
is still working O.K.


>- I am also running with the large fonts. This results in the fact that in the
>	setup window some things write over one another and that some are not
>	settable because of that, like the batch and print things.

Nothing I can do to help you here, if you have set resources which change all
the font sizes, then the setup window is going to get disturbed, due to 
the fact it is using exact pixel positioning, and not attachments. I will recode
the UIL file, when I get a change to use widget attachment, and not pixel 
possitioning.

Jim

	I've tried to install Banner006 last week, but had no success.

	Below is an extract of the installation logfile. First it gave some
	linking warnings and after the installation the earlier reported stack
	dump followed. My colleague did the installation today as well without
	any problems on his station.

	I also modified DECW$Banner.dat and purged files (as mentioned in some
	replies), but still it failed.

	What have I done wrong?


HLEUS1_Eddy >set process/priv=all
   9-AUG-1990 15:45:17
HLEUS1_Eddy >@sys$update:vmsinstal

	VAX/VMS Software Product Installation Procedure V5.3

%VMSINSTAL-W-NOTSYSTEM, You are not logged in to the SYSTEM account.
* Do you want to continue anyway [NO]? YES
* Are you satisfied with the backup of your system disk [YES]? 
* Where will the distribution volumes be mounted: hlis07::

Enter the products to be processed from the first distribution volume set.
* Products: banner
* Enter installation options you wish to use (none): 
The following products will be processed:
  BANNER V0.6
	Beginning installation of BANNER V0.6 at 15:46

%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, 9 undefined symbols:
%LINK-I-UDFSYM, 	DDTM$AR_PERFORMANCE_CELLS 
%LINK-I-UDFSYM, 	PMS$GL_CWPS_BYTES_IN 
%LINK-I-UDFSYM, 	PMS$GL_CWPS_BYTES_OUT 
%LINK-I-UDFSYM, 	PMS$GL_CWPS_GETJPI_IN 
%LINK-I-UDFSYM, 	PMS$GL_CWPS_GETJPI_OUT 
%LINK-I-UDFSYM, 	PMS$GL_CWPS_MSGS_IN 
%LINK-I-UDFSYM, 	PMS$GL_CWPS_MSGS_OUT 
%LINK-I-UDFSYM, 	PMS$GL_CWPS_PCNTRL_IN 
%LINK-I-UDFSYM, 	PMS$GL_CWPS_PCNTRL_OUT 

%LINK-W-USEUNDEF, undefined symbol DDTM$AR_PERFORMANCE_CELLS referenced
 in psect $CODE offset %X00000057
 in module BANNERTP file HLEUS1$DKA300:[SYS0.SYSUPD.BANNER006]BANNER.OLB;1
%LINK-W-USEUNDEF, undefined symbol DDTM$AR_PERFORMANCE_CELLS referenced
 in psect $CODE offset %X0000056A
 in module BANNERTP file HLEUS1$DKA300:[SYS0.SYSUPD.BANNER006]BANNER.OLB;1
			___///___
%LINK-W-USEUNDEF, undefined symbol PMS$GL_CWPS_MSGS_IN referenced
%LINK-W-USEUNDEF, undefined symbol PMS$GL_CWPS_MSGS_IN referenced
%LINK-W-USEUNDEF, undefined symbol PMS$GL_CWPS_MSGS_OUT referenced
%LINK-W-USEUNDEF, undefined symbol PMS$GL_CWPS_BYTES_IN referenced
%LINK-W-USEUNDEF, undefined symbol PMS$GL_CWPS_BYTES_OUT referenced
%LINK-W-USEUNDEF, undefined symbol PMS$GL_CWPS_GETJPI_IN referenced
%LINK-W-USEUNDEF, undefined symbol PMS$GL_CWPS_GETJPI_OUT referenced
%LINK-W-USEUNDEF, undefined symbol PMS$GL_CWPS_PCNTRL_IN referenced
%LINK-W-USEUNDEF, undefined symbol PMS$GL_CWPS_PCNTRL_OUT referenced
%BANNER-I-HLB1,  Building the DECwindows Banner help file.

%LIBRAR-S-INSERTED, module OVERVIEW inserted in 
		HLEUS1$DKA300:[SYS0.SYSUPD.BANNER006]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.6 completed at 15:52

Enter the products to be processed from the next distribution volume set.
* Products: 
	VMSINSTAL procedure done at 15:54

HLEUS1_Eddy >log
  EDDY         logged out at  9-AUG-1990 15:55:14.42

Looks from the list of undefined symbols that your running a VMS version which is 
less than V5.3? I forgot to put the code into the kitinstal that checked the VMS
version, but for the BANNER006 kit it must be V5.3 or later.

Sorry

	Jim

re .5

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

re .8
>                    -< BANNER006 is for VMS V5.3 or later >-
>

Eddy is sitting next to me and his 3100 sure is running VMS 5.3 as is 
mine...

... I have to admit that he's been playing around with VMS tailor a 
little lately, perhaps he was a bit to over enthousiast ;-)

But while I've been tailoring as well banner runs perfectly on my 
system, so what could be so essential ??

regards,

_Floris_


PS please help the guy, he sits there all day looking jealous at my 
   system running banner...

  Re: 8    This looks very familiar to me....  

VAX/VMS V5.3  on node HLEUS1  15-AUG-1990 20:16:02.77   Uptime  0 02:34:25
  Pid    Process Name    State  Pri      I/O       CPU       Page flts Ph.Mem
00000041 SWAPPER         HIB     16        0   0 00:00:02.87         0      0   
00000045 ERRFMT          HIB      8      125   0 00:00:00.39        81    117   
00000046 OPCOM           HIB      8       31   0 00:00:00.67       208     79   
00000047 AUDIT_SERVER    HIB     10       26   0 00:00:00.46      1304    152   
00000048 JOB_CONTROL     HIB      9      100   0 00:00:00.35       127    271   
				---//--
00000055 EDDY_SM4        LEF      6      273   0 00:00:32.16      3794   4071   
00000057 EDDY_SM6        HIB      5      102   0 00:00:00.97       954    396   
00000058 DECW$TE_1       LEF      7    16907   0 00:03:51.84      4430   3155   
00000059 DECico          CUR      4    13074   0 00:23:29.61     30025    300   
0000005A VWSLat          LEF      6    83667   0 00:01:18.59       801    899  S


	As Floris already mentioned I might miss something I'll need to get
	banner running but the question is: What!!

	Eddy	:-o 

 (PS Re: 10
	Don't inform the whole world will you......  :-p )

	

    Do you have a kit for Ultrix (RISC and VAX) or where I could find
    one?

    Thanks,

    Hemant.

re .12 I'm very sorry to tell you that BANNER is very definiatly VMS ONLY. Even
though it is written in C, and X11, it unfortuiantly use about 50+ VMS system
services getting the stats that are display for VMS/VAX. I have never investigated 
just how much of that information is available on ULTRIX systems, but my 
gut feeling is not very much. There was someone actually looking at porting some 
of it, I dont know how many displays they got working, maybe if they still
read this conference they might like to comment?

Sorry
	Jim

re .9 - .11

	I'm afraid I really dont know what you have done to your VMS system. The
undefined symbols are the VAX performance cells which are in SYS.EXE. The 
particular ones you listed came into existance in VMS V5.3, but were not there
in VMS V5.2. This can mean that either your SYS.EXE or SYS.STB is not what it
is ment to be. I'm afraid there isn't much more I can say, you have to find why 
your 'V5.3' doesnt have the symbols on SYS.STB that banner needs to get the 
performance info on the system. 

Sorry 

	Jim

	Re: -14

	Maybe you're right. I'll check with Floris to see if there are any
	differences (SYS.EXE and SYS.STD are exactly the same as on the
	system Floris is using).

	Perhaps I can TAILOR them BACK !! (Can I??)

	I'll keep you informed.

	Regards Eddy

	PS (Floris, what about tomorrow morning 08:30 sharp???)

I've looked through  this note and 1609 and I cannot find what I am looking for
so pointers please if I have missed something.

I am running BANNER006 and it is basically working OK (except for the various
problems mentioned elsewhere) but when I try to use the alarm I get some
strange happenings.

1) The alarm setup sliders are backwards. The start off at 12:00 but the
minutes slider is hard right and increases the minute value as it slides left.
Ditto the hour slider which starts at 12 in the middle.

2) Editing the alarm message works OK but the DELETE key deletes the character
to the right and not the left (I noticed this with other systems when I played
with using MOTIF and I thought that something was incorrectly set in my
installation. However I am now using DECwindows and this still happens but only
in BANNER)

3) When the alarm goes off, the message displayed is not what I typed in but
"Banner Alarm Message"

Thanks

Don Mackay

re .-1

	Yes the Text entry problems are due to Motif, dont forget Banner006
is built against a very early Motif version, when I get 1.1 up on my machine
I'll rebuild it, and hopefully be able to iron out a lot of the problems 
that currently exist. 

	The rest sound like basic bugs, probably braught around by the port to 
motif that I never noticed, I'll take a look at them, and try to work out 
whats going on. 

Thanks for the info,

	Jim

Hi There -

    I just recently installed T0.6 of Banner and I like the new features
which have been added (at least added since my earlier version of banner) -
cluster and queues.  Thank you very much for creating this utility.  I'm
currently running Banner on V5.4-4G1 and running DECwindows.

I've observed some strange behaviour:

1) I start up Banner and everything looks fine.  After about 1 minute it starts
   using the CPU (well at least the CPU chart shows 100% utilization and the
   Processes chart show banner using 85-95% of the CPU).  Checking with monitor,
   Banner is really using that much CPU (as opposed to just showing that the
   CPU is busy when it isn't).

2) With the BATCH QUEUE window.  It will come up fine.  When I go into setup
   options and change something (Printer queue attributes) and then apply the
   change, the BATCH QUEUE window clears and just shows one of the queues and
   none of the processes in any of the queues.

3) With the PRINTER QUEUE window, I will select and give the filter of `*' or
   `*PS40*' and then select apply.  No window appears.

4) When I deselect the TP window, the TP options gray out to reflect that it
   isn't selected.  I then close the options window and then reopen it.  The
   TP options are no longer grayed out even though they aren't selected.

5) Now that I've been running it awhile, I get a few error messages while its
   running.  They are:

	X error event received from server:  BadMatch - parameter mismatch
	  Failed request major op code 42 (X_SetInputFocus)
	  Failed request minor op code 0 (if applicable)
	  ResourceID 0xf00096 in failed request (if applicable)
	  Serial number of failed request 25157
	  Current serial number in output stream 25306
	%NONAME-E-NOMSG, Message number 02DB822A
	X Toolkit Warning: Window Manager is confused
	X error event received from server:  BadMatch - parameter mismatch
	  Failed request major op code 42 (X_SetInputFocus)
	  Failed request minor op code 0 (if applicable)
	  ResourceID 0xf0012a in failed request (if applicable)
	  Serial number of failed request 43741
	  Current serial number in output stream 43917
	%NONAME-E-NOMSG, Message number 02DB822A
	X error event received from server:  BadMatch - parameter mismatch
	  Failed request major op code 42 (X_SetInputFocus)
	  Failed request minor op code 0 (if applicable)
	  ResourceID 0xf0017f in failed request (if applicable)
	  Serial number of failed request 49169
	  Current serial number in output stream 49346
	%NONAME-E-NOMSG, Message number 02DB822A


I hope this helps.  If you need any more information, I'll try to supply if
I can.  If you are in or near ZKO (Nashua), I can show the behaviour listed.

Thanks for making this utility available.

Ike

Hello again -

    Some more observations to augment my previous note (.18).


1) The error message described in #5 only occur when the setup window is being
   opened.

2) If I have both printer and Batch queue windows open, go into the setup
   options, deselect printer, and then select ok, the BATCH window goes and
   the printer window remains.

I'll report anything else I see.  Thanks in advance for any info you can provide
as workarounds or ideas.

Great stuff,
    ike

Hello again -

   Well, Banner has been running most of today and it hasn't been hogging the
CPU as I described in note .18.  I believe this is becuase I have both the
printer and the batch queues windows open at the time.  The printer queue
window is empty and so I just tuck it behind the windows.

   Is anyone else noticing these actions?  Or am I just the lucky one?

   Thanks,
      Ike

Re .-18

Well 006 had a lot of changes, and it looks like it got quit a lot of bugs at the
same time. Ah well I'm going to have some fun fixing this lot :-{

.1 Really dont know why it should do this, if you can reproduce it I would be 
   very greatful, because I have never seen banner hogg CPU time like that, 
   But that would be very dangerous if there is a bug of that sort, since banner
   is elivating its priority to 14, it can eat a machine under such circumstance.

.2 .3 Looks like the buttons (and maybe the queue names) are inversed, eg:
      print queue is batch queue and visa versa. You probable ned to turn on the
      print queue to get the bacth queue etc. 

.4  Looks like a little bug in the set sensitive code, I'll take a look at it.

5.  Yes this is a bug, which is concerened with the setup window, it only happens
    when you are running in 'with boarders' mode, its doesnt have any effect on the 
    operation of banner.

Jim

Hello again -

    (probably getting sick of seeing my stuff here :-)

    I've had banner running for 5 days now( Banner started at decw$login.com).
Everything looks fine.  No CPU hogging (with both printer and batch queue
windows open).

    The only quirk I've noticed recently (beyond those mentioned in previous
notes) has to do with the message window.  I've started banner early on so the
message comes up when mail is recieved, printer notification, etc.  As the
messages have come through, the banner message window is getting larger!
The text window remains the same size, but the border area below gets
larger about a line at a time.  So after 5 days, the message window is about
1 inch longer than it was when I started.  Very strange...


Thanks again for the utility!
    Ike

Reply from ftsv is as follows:

FTSV Job 2091 (FTSV_2091) finished at 13:30:54
COPY FIZBUZ::FIZBUZ$USER:[SAUNDERS.DECW$BANNER]BANNER006.A $77$DUA9:[DECW]*.*
%SYSTEM-F-CTRLERR, fatal controller error

Kit size is 0... I don't see this often...

Dont know what you had there, the kit looks O.K, this end, 22,000~ blocks, 
and seems to copy O.K, I suggest you try again, and send me the whole FTSV
log if it doesnt come across, we may have a hardware error here which hasnt
show up this side.

Sorry

	Jim

	Hello,
	
	I have the same problem from node COSMO at KBO (Germany)...

	
From:   COSMO::FTSV
To:     JANICH
CC:
Subj:   FTSV Job 171 (FTSV_0171) finished at 13:30:17

COP FIZBUZ::FIZBUZ$USER:[SAUNDERS.DECW$BANNER]BANNER006.A USER2:[NEWPROD.DECWBAN
NER]*.*/NOTIFY=MAIL
%SYSTEM-F-CTRLERR, fatal controller error

[FTSV Version V2.1-001]
          

MAIL>


          

    I am having similar problems here in ZK0. Is the file corrupted ??
    $ copy TLE::FIZBUZ::FIZBUZ$USER:[SAUNDERS.DECW$BANNER]BANNER006.A []
    %COPY-E-READERR, error reading
    TLE::FIZBUZ::FIZBUZ$USER:[SAUNDERS.DECW$BANNER]BA
    NNER006.A;1
    -RMS-F-RER, file read error
    -SYSTEM-F-CTRLERR, fatal controller error
    %COPY-W-NOTCMPLT,
    TLE::FIZBUZ::FIZBUZ$USER:[SAUNDERS.DECW$BANNER]BANNER006.A;1 n
    ot completely copied

Is FIZBUZ$USER an RD connected to an RQDX3?  Is FIZBUZ running either V5.3-1 or
V5.3-2?  If so then it's likely that this problem is caused by a bug in the
driver for the RQDX3 (PUDRIVER).  There is a patch posted in the VMS_FIELD_TESTS
conference on VAXWRK.

stephen

    BANNER006.A is also on VISA::DECW_DISK:[DECW$UTILS]
    
    
    Pierre.

Re .-1  Thanks for the info, thats it, we upgraded to V5.3-1 last week. In the 
mean time, I've put the kit onto another cluster, it can be copied either from
there, or from VISA:: as mentioned in .28 :-

	PAMPAM::LING$DEV:[DECW$BANNER]BANNER006.A

Sorry for this, I didnt know about this bug,

	Jim

�The only quirk I've noticed recently (beyond those mentioned in previous
�notes) has to do with the message window.  I've started banner early on so the
�message comes up when mail is recieved, printer notification, etc.  As the
�messages have come through, the banner message window is getting larger!
�The text window remains the same size, but the border area below gets
�larger about a line at a time.  So after 5 days, the message window is about
�1 inch longer than it was when I started.  Very strange...
    
    
    I see the same problem, though in my case it seems to be growing faster
    that that.  Pretty strange.  Any ideas?
    
    
    -Dave

>    I see the same problem, though in my case it seems to be growing faster
>    that that.  Pretty strange.  Any ideas?

Known toolkit shell widget bug.

-steve-

I assume that this kit is still intended to work with the DEC window manager.

I have installed it on V5.4 of VMS (SSB) and all seems fine except the resources
listed in .9 seem to be ignored.  I added these lines to the 
SYS$LOGIN:DECW$BANNER_node.DAT and restarted BANNER.

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

Any clues?

Brad

RE: .-1
>listed in .9 seem to be ignored.  I added these lines to the 
>SYS$LOGIN:DECW$BANNER_node.DAT and restarted BANNER.

  I had the same problem, but if you read the note carefully you
want to put those resource names in a sepearte file: DECW$BANNER.DAT

				Craig