Conference bulova::decw_jan-89_to_nov-90

There is a typo in this announcement.  The documentation is actually in:

	VMSKITS::DECW$PUBLIC:[DOCUMENTATION.V2_IFT1.POST] and
	VMSKITS::DECW$PUBLIC:[DOCUMENTATION.V2_IFT1.LN03]

not in VMSKITS::DECW$PUBLIC:[DOCUMENTATION.V2_IFT2.xxx] as in .0.

--PSW

    There is another typo in both the basenote and the first reply: the
    nodename is VMSKIT::, not VMSKITS::.
    
    Keith

       For field test only, DECwindows Mail has support for tracing
       user actions and internal state. This is enabled by defining
       the logical DECW$MAIL_TRACE to a file to which to write the log
       (i.e. $DEFINE DECW$MAIL_TRACE SYS$SCRATCH:DECW$MAIL.LOG). We
       ask that you always define this logical during field test, as
       the log will make it much easier to track down any problems.
       When submitting a QAR, please include at least the beginning
       section of the log (through "Startup complete"), and the
       section of the log where the problem occurred. If you do not
       include the entire log in your QAR, please keep a copy of the
       entire log in case we need more information.

Caution - before installing this IFT1 kit, save a copy of the VAX binding
files for DWT (the DECW$DWTDEF and DECW$DWTWIDGETDEF) files for the
various languages.  V2 claims that it has broken these into separate
files and the old files just do an "include" of the new ones, but the new
files are not provided on the kit.  This wouldn't be so bad except that the
old ones WERE changed to include the new ones, so you're stuck with
no definitions.

I have QARed this.

				Steve

    Where can I find 5.2?
    
    

    Re: .5
    
    See note 5 in the VAXWRK::VMS_FIELD_TESTS conference for V5.2
    (actually, still T5.2) kit information.
    
    				Steve

When will the ultrix field test be available????

I think it already is.  That is not to say I know how to get it, however.


Burns

This is the announcement of availability of the Field Test Kit for UWS T2.2
(you can call it ULTRIX DECwindows V2, same thing with different names.)

AVAILABILITY

External Field Test 1 of ULTRIX Workstation Software (UWS V2.2 EFT1)
is now available for your use.  Note that this baselevel and all related 
documentation and project information are COMPANY CONFIDENTIAL.

It is available internally for two audiences of users:

-  those who are now running UWS T2.2-BL3 or T2.2-pre-FT1 and wish 
   to upgrade their system to the latest UWS V2.2 bits slated to ship
   to external Field Test.

-  users of the present UWS V2.1/V3.1 software who wish to upgrade
   their system.  
          
All the information contained here should not be distributed or shown
to non-Digital employees without the express written consent of UWS
product management (Jon Hall  hall on sonora::).



CONTENTS

The software described in this memo and available by the below 
means is not a complete UWS V2.2/ULTRIX-32 V3.1 kit.  Only the UWS V2.2
bits can be obtained in this enet manner.  

This baselevel contains all the basic functions that UWS Engineering 
Development plans to ship in Version 2.2 (and V2.4) of UWS.  

Requirement:  To run this software you must be running 
	      ULTRIX-32 V3.1, SDC version.



KIT LOCATION for ENET installation

These bits were last updated July 8 5PM PDT.  If you retrived bits
prior to this date you will need to re-install this more current version.


EFT1 kits are located on gilroy in the standard place:

	/kits/uwsft1/{max,vax}/kit


The uwsinstall script in  /a13c/uws/kits/ft1  will install the bits
for you if you don't want to grab them.


                              NOTE
             
To run this software you should be running ULTRIX-32 V3.1 SDC version.

If you are not, you will need to edit your /etc/ttys file to use 
login.patch as opposed to login.



DOCUMENTATION
          
The release notes and associated documentation describing EFT1 and its
installation are located in these directories:

       EFT1 Documents*	     ravine:/usr/staff/r0/maler/uws/fieldtest
 	  release notes     
	  other DWs docs
	  

       DPS Documents	     gilroy /a13c/uws/phases/v22/phase2 

       Preliminary SPD       gilroy /a13c/uws/phases/v22/phase2   

       UWS Software Change   gilroy /a13c/uws/phases/v22/phase2  
       Submit forms

(* Installation Notes intended for external FT may not apply to the enet kit)       


INSTALLATION

The UWS V2.2 EFT1 kit files are maintained in setld-format for easy use
by the Ultrix ris and dms utilities.
	
To obtain and install the EFT1 subsets, copy the "uwsinstall" script
from GILROY and run it.  You may also intervene manually on your own 
initiative.
	
"UWS" is used to refer to both the VAX UWS subsets and the RISC UDW subsets.

   INITIAL SETUP

1. Preparation: become the root user with "su" and change your current
   directory to a partition with adequate free disk space. To acquire
   adequate space, you may choose to delete the old subsets prior to EFT1
   installation.  

   On disk space:  the full VAX distribution requires 20 megabytes; the full 
   RISC distribution requires 45mb.  These figures more than double to do
   a standalone installation.  


2. Copy uwsinstall script from gilroy

   Type:

		dcp gilroy::/a13c/uws/kits/ft1/uwsinstall

		chmod u+x uwsinstall


3. Run uwsinstall

   Type:
	./uwsinstall

    and answer the questions.

    You may copy the mandatory subsets, all the subsets, or individually
    chosen subsets. You may also choose to install immediately or defer
    installation to a later time. If you have ris or dms servers and
    clients, you must add the subsets to your own ris or dms configuration.


4. Clean up afterwards.

    Delete the subsets in the current directory unless you have determined
    you will need them later.


         
		    *IMPORTANT INSTALLATION NOTES*
  

Once the subsets have been copied to your machine, there are several
issues to keep in mind.
	Previously existing UWS subsets which are going to be overwritten,
        (in particular, the fonts) should be deleted with "/etc/setld -d".

	If fatal verification errors occur, check the subsets to see if
        they've copied correctly.

	Consult the ULTRIX documentation set for further information 
        on the ris, dms, and setld utilities.


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

         
QAR SYSTEM

Please use the ULTRIX QAR database, UWS_QAR, for reporting quality problems
with this baselevel.
                
This QAR system is set up on GORGE (in ZKO) to allow you to report 
all internal problems you have with UWS software.  Each DRI should already have
an account on this machine.  Or you may use the general account, 

               Name: QAR_INTERNAL
               Password: QAR

Contact the Account manager:  Eileen Horner  decvax::eileen  with any questions.

When you enter a QAR, the system will ask you a series of questions.  Please
be sure to explicitly state you are reporting problems against product
version V2.2 EFT1.  



PROBLEM REPORTS

Unsupported software:  there are a number of software product components 
which continue, as in UWS V2.1, to be unsupported in UWS V2.2.  QARs will not
be honored for these components and will be automatically closed with a
statement of non-support provided. A statement of support is contained both
in the Release Notes and in the preliminary SPD.



INSTALLATION & PROCEDURAL PROBLEMS

Please contact, in this order:  Rich Hyde     415-853-6671  sonora::hyde
				Tom Patterson 415-853-6731  sonora::tp 


     
CONFIDENTIALITY

Once again remember, this project, baselevel kit, and memo are COMPANY
CONFIDENTIAL. Do not discuss the contents of this BL with people
outside the company.

    I copied the Ultrix field test kit but didn't want to install it immediately
    so I exited. Is there anyway the get the uwsinstall script to skip
    the copying of the files and jump straight into the installation.
    It takes quite a while to copy the kits so I would like to avoid 
    that if possible.
    
    I tried just editing out the copying section but it obviously
    sets up some stuff for the setld command because the script
    breathed its last as soon as it attempted setld.
    
    Any help much appreciated,
    
    Joe.
    

If you have all the UWS T2.2  subsets, then this is what you need to do.

 Boot  your system to single-user mode ("b/3" and enter image name "vmunix" for a  VAX or,
 "boot -f rz(0,root fille disk #,0)vmunix" for a PMAX.....always run 'fsck" after single-user boot..
 You can then mount all your file systems with "mount -a".

1.  cd  to the target directory containing the subsets (this directory may be your own creation but
      you have to be root and in single-user mode)

2.  setld -l  <target directory> .....eg.  setld -l /usr/kits/UWS_2.2  ....to copy the files from di
      target destinations on disk.   Use setld -d  to delete the old subsets that are no longer need
      These should be the old and redundant UWS 2..1 subsets.

3.  /etc/doconfig  .....to rebuild your new kernel (please take the defaults to play safe).
     The system will prompt you for the location of the new kernel after it is built..usually in a p
      like /sys/.../SYSTEMNAME/vmunix.   Save your old kernel in / (root), and move the new kernel
     to /.   Reboot your system.....when all is fine, you may delete your old kernel.


BTW:  I tried the FT UWS 2.2 but found it so buggy that I went back to 2.1.   Good luck.


Kris...

    I've upgraded my system to T5.2-1 before installing the DECWFT1020 kit.
    However, the DECW kit complained that the VMS version is not 5.2 or
    later!? Is this a bug in the DECW KITINSTAL?
    
    --svb

    I couldn't find where I read this, but do this first:

    	$ DEFINE/SYSTEM/NOLOG DECW$IGNORE_VERSION TRUE

               Dave

    Re .13, thank you. That does work.
    
    --svb

    Will DECWindow Ver 2.0 work with VMS T5.2-41S ??
    
    

gawd!  upgrade to *at least* V5.2 or T5.2-1 if you want to run ft stuff.  41s
is really old.

The IFT1 kit is obsolete anyway - you'd want the EFT1 kit (announced
somewhere...).

But I agree - update to V5.2.

		Steve

	While on the topic of the different DECW kits! - Could someone clear up
some of my confusion?
	The kits I find on the net are

	DECW052.C-G dated 15 JUNE 1989
and
	DECWFT1020.A-H dated 12 JULY 1989

	The DECW052 kit is located with the VMS052 SSB release, so I presume
this kit is the DECW SSB release. Right or wrong?
	But the DECWFT1020 kit has a newer date? 
	Is there really any differences between the kits? I wish to use one of
these for my VS2000/GPX (an internal system). Would it make any difference in
which one I used? Or are there newer test kits that would be more interesting
to test?
	Thanks if you can help.

The DECW052 savesets provide the version of DECwindows "V1" that is
included in VMS V5.2.  The DECWFT1020 savesets are newer and provide a
field test version of DECwindows "V2" (that will presumably ship with
a future VMS release).

				Steve

       
       
       	And the DECW052 savesets are applied using
       SYS$UPDATE:DECW$TAILOR.EXE. The DECW IFT V2 kits are done using
       SYS$UPDATE:VMSINSTAL.COM
       						mike

Not really...  The general way that the DECW052 savesets get installed is as
part of the regular VMS V5.2 installation (using VMSINSTAL).  Only if you
choose to not install DECwindows initially do you use DECW$TAILOR later.

			Steve

       
       
       	I assumed that he didn't have DECWindows installed already Steve.
       
       							mike