Conference bulova::decw_jan-89_to_nov-90

    Why would the SDC kit of VMS and DECwindows for the VAXstation 3100
    be considered so 'hush-hush'?
    
    I seems to me that with the FT versions being dragged all over creation
    in the road shows and AWSMM kits, VMS would be desperate to
    get SDC SW on view?
                                     
    -fjp

    It's probably mentioned elsewhere in here, but you'll need VWS 4.0A
    (note the A) to use with the PVAX.  The patch to VWS 4.0 corrects
    a problem with the mouse not working on the PVAX.  (I know this
    is a DECwindows conference, and we *all* should be using DECwindows,
    but since .0 mentioned VWS, I thought I would too...)
    
    Todd

Who ever said the release was Hush hush?  

-- Nestor

    If I'm interested in having the PVAX boot in as a satellite to a
    cluster, is it okay to install this new version of VMS on an 8550,
    8800, etc. bootnode?  Do I have to re-install DECwindows SDC?
    
    Thanks,
    
    	 	== ken miller ==

    
    VWS 4.0a is not yet available as there was a slight 'snag'.  I believe
    it is being put together this week.
    
    VWS 4.0 *will* work on the VS3100 *but* it will occasionally fail
    to start the mouse (the turn around time on the pVAX is too fast
    for the mouse when responding to the power-up sequence).
    
    If you have questions regarding the availability of V4.0a, please
    contact Larry (UTAH::) Villandry or Jeff (VWSENG::) Friedrichs.
    
    _Fred

re: -2

Yes, you can. I have upgraded a V5.1 machine without a problem.

As far as hush-hush:

	The memo states an internal release. It still hasn't come out of SDC
	yet. Therefor it should not be given to customers, unless through
	official channels (which all software should come through anyway).

	Anyway, the memo is a boilerplate form we used during Field test
	releases.

    I think the wording of the memo is a little supprising
    
>          They should not be distributed or shown to non-Digital
                                             ^^^^^
                                             |||||
>          employees without the express written consent of VMS prod-
>          uct management.
    
    Digital offices all around the world have demo PVAXen running
    FT-versions of the software. They are shown to customers
    constantly (without nodisclosure, because the product was
    announced in January).  Now when SDC-kit is available from
    the network does this really mean that the SDC-kit cannot
    be installed on these Digital owned demo systems and that we should continue
    showing the FT-software?? Sounds a little strange?. Please
    note that i am not talking of giving the software to customers.
    (just using it in demonstrations).
    
    		Pekka

re:   .6

That's great news...I will upgrade, thanks.

Regards,

                   == ken miller ==

DLOACT""::SYS$KITS:[PVAX.SDC]

I get a "must set STARTUP_P1 to MIN" error on the install, but when I
do this, I no longer see the the disk that contains the savesets.  And I don't
have enough space on the system disk to put them there!

What can I do?

Thanks,

                 == ken miller --

After the "MIN" boot, mount the disk with the kits.  You can refer to
your SYSTARTUP_V5.COM for the exact command.

Dick

STARTUP_P1 set to "MIN" means you don't get the device configured,
so you don't *have* a device to  mount!

The VMS Development folks helped me through it (thanks Ward!).

Basically, I needed to do the following after rebooting with STARTUP_P1 
set to "MIN":

$mc sysgen autoconfig all /sel=(dk,pk)/log
$moun/sys ...
$@vmsinstal ...

Thanks for the feedback

Regards,

               == ken miller ==

    This may not be the best place to put this, but...
    
    Anyone who has one of the VAXstation 3100 units that was a "seed"
    unit with a TK50 drive will have a problem with the tape drive after
    upgrading to the SDC kit.
    
    My TK50 became unusable (except for standalone backup) with V5.1-TB0
    and now will not even come up online under V5.1-B.  An ANALYZE/ERROR
    shows that there is an unsupported hardware/firmware revision. My
    unit shows:
    
    	CNTRLR HW REV	05 
    					HARDWARE REVISION = 5. 
    	CNTRLR FW REV	29 		
    					FIRMWARE REVISION = 41. 
    
    The CSC in Atlanta says that the system will require a
    "seed upgrade" that Field Service will have available next week
    (somewhere around Wednesday). 
    
    Get your systems on contract and log a call with your friendly In-house
    Field Service people (but not before next Wednesday - 3/1/89).

    	- Dave    

re: .12

Sorry about that.  It's been awhile since I did this sort of stuff and I forgot
about the auto config all.

Dick

    I've just pulled the VMS 5.1B/DECwindows kit over and installed
    on our PVAX. Everything seems fine until the system is shut down.
    It looks as though the DECwindows doesn't want to shut down 'cos
    the "arrow head" can still be mouse-controlled after system has
    gone "standalone". The console prompt >>> doesn't seem to appear
    and the halt button need to be pressed.
    
    What seems to be the problem. I've tried a few times and it's the
    same. I was told that this problem was propagated from the earlier
    release of DEcwindows.
    
    Appreciate any advise.
    
    /Mike

This is fixed in V5.2, it would seem.  The standard workaround is to either
run SHUTDOWN from a detached process or to run it from a session logged in
as SYSTEM.

				Steve

       
       
       	Or use the "DCL command" option in FileView.
       
       							mike