[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

3559.0. "DECwindows V3 Internal Field Test Announcement" by STAR::BROUILLETTE () Wed Oct 31 1990 15:18

    
          DIGITAL       INTEROFFICE MEMORANDUM


          TO:      @WSPROJECT                DATE: Oct 31, 1990
                                             FROM: Bill Matthews and
                                                   Janis Horn
                                             DEPT: VMS
                                             EXT:  381-1530,0704
                                             LOC:  ZK03-4/W23
                                             ENET: DECWIN::BMATTHEWS,
						   JARETH::HORN


          SUBJECT: VMS DECwindows V3 Internal Field Test Baselevel


          AVAILABILITY

          The Internal Field Test Baselevel of VMS DECwindows V3 is now
	  available for your use. Note that this baselevel kit and all related
          documentation and project information are COMPANY CONFIDENTIAL.
	  They should not be distributed or shown to non-Digital employees 
	  without the express written consent of VMS product management.

	  You should expect that this DECwindows baselevel will
	  be less stable than the DECwindows software provided with
	  VMS V5.3, V5.3-1 and V5.4.  

	  THE DECWINDOWS V3 IFT KIT IS NOT YET PRODUCTION QUALITY SOFTWARE.

	  While we are running the internal field test baselevel on our
	  development cluster, many of the components are entirely new;
	  minimal testing has been done to date.

	  This baselevel contains almost all of the V3 functionality. Future
	  baselevels will continue to add quality and usability improvements.

                                    NOTE

             To run this software you must be running VMS V5.4 or later
	     software. Upgrading to this version of VMS is required to
	     have the correct base system support for DECwindows V3.


          KIT LOCATION

          The Internal Field Test software savesets are available in the
	  directory:

               BULOVA::DECW$PUBLIC:[V3]		OR

	  Andy Leslie has agreed to be a European distribution site for 
	  the internal field test baselevel.  Andy is in Newbury, England. 
	  Kit location:

		KIKAHA::DISK$UNICORN:[DECWINDOWSV3]

          The savesets should be installed using the standard VMSINSTAL 
	  procedure. There is no need to run a separate VMS update
	  kit or to use DECWDELETE.

          During the DECwindows installation, you will be prompted
          to select which of the savesets and components of the kit
          you want to install.

          To copy all the savesets to your own system for local 
          installation, use a variation of the following command:

               $ COPY BULOVA::DECW$PUBLIC:[V3]*.* destination-directory

          Once again, remember to be sure to reboot your systems after
          completing the installation of DECwindows. 

	  LICENSING

	  DECwindows V3 includes MOTIF from OSF.   You must have a license
	  PAK to run DECwindows V3.  During the installation of DECwindows 
	  you will be asked if you have obtained a license.  If you already 
	  have a PAK for the DECwindows Developer Kit on VMS  for OSF/Motif 
	  V1.0 or V1.1, (the OSF/Motif layered product kit that Digital ships 
	  today) you do not need to obtain another one.  To obtain a PAK: 

	       - At your terminal type    VTX PAK
	       - You will then be asked for some information.
	       - At the next menu, select option 4 - Royalty product PAKS
	       - You will then be asked for the node on which this will reside.
	       - At the next menu, select the product named "DW-DEC-KIT-OSF-V"
	       - After this you will be asked for some additional information 
	         and will be told how to save the PAK.

          DOCUMENTATION

	  All of the documentation for DECwindows V3 is not yet complete.
 	  As additional pieces become available they will be placed in 	  
	  BULOVA::DECW$PUBLIC:[V3.DOCS]. Please check that directory for
	  the most current documentation.

	  DECwindows V3 includes MOTIF from OSF. The OSF documentation for
	  MOTIF can be found at CLT::DECW_LIBRARY:[MOTIF.V1-1].

	  Programming Guide (contains widget, WM and UIL info) 27,431 blocks
	  Style Guide 					       27,761 blocks
	  Toolkit Ref (in two files) 		   (combined)  15,507 blocks 
	  OSF Release Notes 					  767 blocks

	  The DECwindows V3 project and business plans can be obtained from
	  BULOVA::DECW$PUBLIC:[V3.PLANS]. These documents describe the content
	  of the DECwindows V3 product.

          In summary, DECwindows V3 incorporates OSF/MOTIF V1.1 into DECwindows.
          XUI applications will continue to run unchanged. Most of the bundled
	  DECwindows applications have been converted to MOTIF and the MOTIF 
	  window manager is started by default under DECwindows V3. DECwindows 
	  V3 also incorporates the MEMEX HyperInformation technology. The 
	  DECwindows applications MAIL, CARDFILER, BOOKREADER, and CALENDAR have 
	  added MEMEX support. DECwindows V3 moves from MIT R3 to MIT R4
          compliance for the X11 Window system. The X11 server includes
          windowing performance optimizations, backing store support, and
          reduced memory usage.


          QAR SYSTEM

          A QAR system has been set up on TRIFID to allow you to report 
	  problems you have with VMS DECwindows. Please be sure
          to enter VMS-specific DECwindows QARs in the internal database
	  on TRIFID.

	  We have a new QAR database for DECwindows V3. Please start
	  using the DECW-V3-INTERNAL database. The DECWINDOWS-IFT 
	  database should only be used for V1 and V2 problems.
                
          For internal access to the DECW-V3-INTERNAL database you may
          use the QAR account:

               Name: QAR_INTERNAL
               Password: QAR

          When you enter a QAR, please be sure to explicitly state
          the name of the field test (or intermediate baselevel) you
          are running, the release of the VMS operating system you
          are running it on, and the type of workstation you are using 
	  (e.g., VAXstation 2000/GPX).


          CONFIDENTIALITY

          Once again remember, this project, baselevel kit, and
          documentation are highly COMPANY CONFIDENTIAL. Do not discuss
          the contents of the field test or any of the specifications
          with people outside the company.
    
T.RTitleUserPersonal
Name
DateLines
3559.1other distribution sites?DECWIN::BROUILLETTEWed Oct 31 1990 16:536
    
    If you copy the kits and would like to offer your node as an
    additional distribution site, please post the location as a reply to
    this note.
    
    Thanks
3559.2DECW$STARTXTERMINAL.COM problem DECwindows IFT V3HANNAH::CHOUWed Oct 31 1990 17:1219
There is a problem in DECW$STARTXTERMINAL.COM under DECwindows V3 IFT. This
problem is corrected with the LAT/Master which is also in field test now.

The symptom of the problem is the VT1000 can not find the 75DPI fonts.

The DECW$DEVICE.COM has changed for DECwindows V3, the 75DPI directory is 
missing, the old DECW$STARTXTERMINAL.COM file can no longer load 75DPI 
DECW$FONT on DECWwindows V3 and we get only 100 DPI fonts.

To fix this problem, do the following:

$ COPY DECW$STARTXTERMINAL.COM SYS$COMMON:[SMRMGR]:
$ DEASSIGN/EXE/TABLE=DECW$LOGICAL_NAMES DECW$XTERMINAL_FONT
$ @SYS$MANAGER:DECW$STARTUP XTERMINAL

**note** the DECW$STARTXTERMINAL.COM file in the next reply works with the 
old LTDRIVER on V5.3 through V5.4-1.

Hal Chou
3559.3 New DECW$STARTXTERMINAL.COM HANNAH::CHOUWed Oct 31 1990 17:18166
$ !
$ ! DECW$STARTXTERMINAL.COM - Start up the DECwindows Terminal support environment
$ !
$ !****************************************************************************
$ !*									      *
$ !*  COPYRIGHT (c) 1989 BY						      *
$ !*  DIGITAL EQUIPMENT CORPORATION, MAYNARD, MASSACHUSETTS.		      *
$ !*  ALL RIGHTS RESERVED.						      *
$ !* 									      *
$ !*  THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED   *
$ !*  ONLY IN  ACCORDANCE WITH  THE  TERMS  OF  SUCH  LICENSE  AND WITH THE   *
$ !*  INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR  ANY  OTHER   *
$ !*  COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY   *
$ !*  OTHER PERSON.  NO TITLE TO AND OWNERSHIP OF  THE  SOFTWARE IS  HEREBY   *
$ !*  TRANSFERRED.							      *
$ !* 									      *
$ !*  THE INFORMATION IN THIS SOFTWARE IS  SUBJECT TO CHANGE WITHOUT NOTICE   *
$ !*  AND  SHOULD  NOT  BE  CONSTRUED AS  A COMMITMENT BY DIGITAL EQUIPMENT   *
$ !*  CORPORATION.							      *
$ !* 									      *
$ !*  DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE  OR  RELIABILITY OF ITS   *
$ !*  SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.		      *
$ !* 									      *
$ !*									      *
$ !****************************************************************************
$ !
$ ! This command file sets up the environment needed for support of DECwindows
$ ! Terminals.  It should be run at system startup time.
$ !
$ ! It is not advisable to edit this procedure as it may be replaced in
$ ! future software updates.  Instead, you should perform any site-specific
$ ! commands in your SYSTARTUP file.
$ !
$ ! p1 = 
$ ! p2 = 
$ ! p3 = 
$ ! p4 = 
$ !
$
$ !
$ ! If we aren't doing workstation setup, then don't do this.
$ !
$ if f$trnlnm("DECW$IGNORE_WORKSTATION") then exit
$
$ !
$ ! Check to make sure that DECwindows Terminal support is to be installed
$ !
$ if f$trnlnm("DECW$INSTALL_XTERMINAL") .nes ""
$then
$ if .not f$trnlnm("DECW$INSTALL_XTERMINAL") then exit
$else
$ exit
$! if decw$device .nes "NONE" then exit
$endif
$ !
$ !This command file work with the old LTDRIVER only.
$ !
$ ! Define logical names for font directories
$ !
$! @sys$manager:decw$logicals decw$xterminal_table decw$define_xterminal False
$
$ ! If DECW$DEVICE.COM failed to define the font directories, do it here.
$
$ decw$xterminalfont =      "DECW$SYSCOMMON:[SYSFONT.DECW.*]"
$
$ on error then goto xterminal_done
$
$ !
$ ! Load class driver
$ !
$ sysgen := $sysgen
$ IF .NOT. F$GETDVI("_XT0:","EXISTS") -
	THEN SYSGEN CONNECT xt0/NOADAPTER/DRIVER=xtdriver
$
$ !
$ ! Install LAT transport
$ !
$ if f$file("sys$share:decw$transport_lat.exe","known") -
	then install replace sys$share:decw$transport_lat
$ if .not. f$file("sys$share:decw$transport_lat.exe","known") -
	then install create sys$share:decw$transport_lat/open/share/header
$
$ !
$ ! Install DECnet access
$ !
$ decnet_access_name = "decw$dwt_decnet"
$
$ if f$file("sys$system:''decnet_access_name'.exe","known") -
	then install replace sys$system:'decnet_access_name'
$ if .not. f$file("sys$system:''decnet_access_name'.exe","known") -
	then install create sys$system:'decnet_access_name'/priv=SYSNAM
$
$ !
$ ! Clean up old log and data files and then start up the font daemon
$ !
$
$ font_daemon_proc = "DECW$FD"
$ font_daemon_name = "decw$dwt_font_daemon"
$
$ IF F$SEARCH("sys$manager:''font_daemon_name'_output.log;-1") .NES. "" -
	THEN PURGE/NOLOG sys$manager:'font_daemon_name'_output.log
$ IF F$SEARCH("sys$manager:''font_daemon_name'_error.log;-1") .NES. "" -
	THEN PURGE/NOLOG sys$manager:'font_daemon_name'_error.log
$
$ ! Stop running Font Daemon, if any
$
$ context = ""
$kill_fd_loop:
$ pid = f$pid(context)
$ if pid .eqs "" then goto kill_fd_done
$ if f$getjpi(pid,"PRCNAM") .nes font_daemon_proc then goto kill_fd_loop
$ stop /ident='pid'
$ wait 0:0:10
$kill_fd_done:
$
$ IF F$TRNLNM("''font_daemon_name'_dump") .NES. ""
$ THEN
$	dump = "/DUMP"
$ ELSE
$	dump = "/NODUMP"
$ ENDIF
$
$ wsdef = 500
$ if F$TRNLNM("''font_daemon_name'_wsdef") .NES. "" -
	THEN wsdef = F$TRNLM("''font_daemon_name'_wsdef")
$
$ wsquota = 1300
$ IF F$TRNLNM("''font_daemon_name'_wsquota") .NES. "" -
	THEN wsquota = F$TRNLM("''font_daemon_name'_wsquota")
$
$ wsextent = 4000
$ IF F$TRNLNM("''font_daemon_name'_wsextent") .NES. "" -
	THEN wsextent = F$TRNLM("''font_daemon_name'_wsextent")
$
$ page_file = 25000
$ IF F$TRNLNM("''font_daemon_name'_page_file") .NES. "" -
	THEN page_file = F$TRNLM("''font_daemon_name'_page_file")
$
$
$ if f$trnlnm("DECW$XTERMINAL_FONT") .eqs "" then -
  decw$define decw$xterminal_font 'decw$xterminalfont' 
$
$ RUN /DETACHED sys$system:'font_daemon_name' -
	/INPUT=		nl: -
	/OUTPUT=	sys$manager:'font_daemon_name'_output.log -
	/ERROR=		sys$manager:'font_daemon_name'_error.log -
	/PROCESS_NAME= 	"''font_daemon_proc'" -
	/PRIVILEGES=	(noall,cmkrnl,tmpmbx,netmbx) -
	/IO_BUF= 	60 -
	/IO_DIR= 	100 -
	/FILE= 		92 -
	/AST_LIM= 	100 -
	/BUFFER= 	50000 -
     	/PAGE_FILE= 	'page_file' -
	/WORKING_SET= 	'wsdef' -
	/MAXIMUM_WORKING_SET= 'wsquota' -
	/EXTENT= 	'wsextent' -
	/TIME_LIMIT= 	0 -
	/TIME_LIMIT= 	0 -
	/NOSWAP		-
	'dump'
$
$xterminal_done:
$ if .not $status then -
  write sys$output "DECW$XTERMINAL startup failed, continuing..."
$ EXIT 1
3559.4Installation in SYS$SPECIFIC?RAGS::SIEBOLDSentenced to PRISM again!Thu Nov 01 1990 15:336
Does the kit allow me to install it in SYS$SPECIFIC so other cluster
members are not effected? Or do I have to take the kit apart ?

Thanks 
	Thomas
3559.5LESLIE::LESLIEAndy LeslieThu Nov 01 1990 17:056
    You'll have to take the kit apart.
    
    I wouldn't recommend it, but you know what you're doing, Thomas :-)
    
    
    /andy/
3559.6HKOVC::TERENCEFrom Middlesex, UWOThu Nov 01 1990 20:015
    Do I really need a PAK to install V3 IFT?

    -Terry

3559.7KIKAHA::LESLIEAndy LeslieFri Nov 02 1990 06:051
    Yes.
3559.8Central Mass (SHR) kit locationGOTIT::harleyEat at Ralphs and live forever!Fri Nov 02 1990 10:116
I've placed a copy if the kits (no space for docs) in:

	MPGS::VMS$Kits:<DECW.V3>
(DFS)	.Eng.Stor_Sys.SHRISG.MPGS_VMS$Kits <DECW.V3>

/harley
3559.9PRAVDA::JACKSONYou run your mouth, I&#039;ll run my business brotherFri Nov 02 1990 11:168
Mill Kit location


DECnet			HARBOR::DISK$KITS:[DECW_V3]*.*;*
DFS			.MLO.S.WRKSTN_BPM.DFS.HARBOR_KITS directory [DECW_V3]


-bill
3559.10Correction to the DW V3.0 PAK nameJARETH::HORNTue Nov 06 1990 18:508
    There is an error in the directions given to pull the DW V3.0 PAK from 
    VTX.  The PAK name is incorrect.  The corrected PAK name is 
    DW-DEV-KIT-OSF-V.
    
    As there are only 4 royalty bearing PAKs in VTX anyway, and 2 are
    Ultrix products, I don't think this will confuse too many people!
    
    Janis
3559.11QUARK::LIONELFree advice is worth every centWed Nov 07 1990 09:234
    How can we find out how much our cost center will be charged for
    the PAK?  There's no clue in the VTX PAK system.
    
    			Steve
3559.12RTL::GRASSSteve GrassWed Nov 07 1990 14:396
Steve,

The charge does *not* come out of your cost center.  DEC will be charged
$40 per license.

				steve
3559.13PSW::WINALSKICareful with that VAX, EugeneWed Nov 07 1990 14:544
Why, then, does the PAK system ask for a cost center number before it will issue
you the PAK?

--PSW
3559.14Really? Then maybe someone should tell the VTX PAK folks...QUARK::LIONELFree advice is worth every centWed Nov 07 1990 16:0314
The following text is displayed by the VTX PAK menu for royalty PAKs.  Note
that it explicitly says there will be a cost-center cross charge.  Is the
text wrong or are we actually being charged?


   The following Digital software product(s) are bound by a royalty agreement
   with a third party, and use PAKs as the tracking mechanism for Digital to
   fulfill its obligation for the usage of these product(s) internally. Each
   PAK issued from the following list results in a cost center cross charge for
   the royalty payment, and a royalty payment from DIGITAL to a third party.
   For more information contact the Royalty Administration Organization.


				Steve
3559.15And the answer is - $14QUARK::LIONELFree advice is worth every centMon Nov 12 1990 11:497
I asked my cost center manager whether or not we were being charged for
the Motif PAKs.  The question eventually got routed to our financial planner
(I think) who said that "Royalty Administration" told her that the cost
centers were indeed being charged for each Motif PAK, but that the fee was
$14, not $40, per CPU.  This is a one-time only charge for each system.

			Steve
3559.16R2ME2::GRASSSteve GrassMon Nov 12 1990 13:013
Sorry 'bout that.  I guess I was given the wrong information.

				steve
3559.17Area 37 Kit Source - Both Kits & DocumentationAITPLB::PBRIGGSPete Briggs - AITC (IDLB5-1/E9 [291-8674])Thu Nov 15 1990 11:3614
The complete kit and documentation are available on:

	midevl::kits$disk:[DECWINDOWS.V3.KIT]

			and

	midevl::kits$disk:[DECWINDOWS.V3.DOC]

respectively.

The DFS access point for the disk is:

	.eng.ai.aiis.DISK$MIDEVL_FT$1