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

Conference ucrow::desktop_acms

Title:DECtp Desktop for ACMS
Moderator:UCROW::GIBSON
Created:Mon Sep 24 1990
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:859
Total number of notes:3034

848.0. "Do we have the correct kit to resolve problems?" by CSC32::D_BUTLER () Mon Apr 21 1997 19:59

Hi,
	Following is a list of the save set delivered to Pacificare by
the local support office specialist. They are trying to resolve a problem
with using 32 bit Visual Basic and Desktop ACMS. Is this the correct kit
and content. They say that they are still experiencing problems.
This also refers back to notes 840 and 844.
    
    Dave
    CSC LST team

-------------------------------------------------------------------------------
ACMSDI_ALPHA_ECO01022.A;1                    945/945     11-APR-1997 15:09:50.00
ACMSDI_VAX6_ECO01022.A;1                     504/504     11-APR-1997 15:07:59.00
-------------------------------------------------------------------------------

Subject: 
        List of saveset for ACMSDI v2.2 EC01
  Date: 
        Mon, 21 Apr 1997 15:40:54 -0700 (PDT)
  From: 
        Scott Flatland <[email protected]


          BU/LIST ACMSDI_ALPHA_ECO01022.A;1/SAVE    
          Listing of save set(s)
          
          Save set:          ACMSDI_ALPHA_ECO01022.A
          Written by:        GIBSON      
          UIC:               [000030,000027]
          Date:              21-OCT-1996 09:12:22.74
          Command:           BACKUP/EXCL=*.A *.* 
          ACMSDI_ALPHA_ECO01022.A;/SAV
          Operating system:  OpenVMS VAX version V6.2
          BACKUP version:    V6.2
          CPU ID register:   13000202
          Node name:         _EYEORE::
          Written on:        _$2$DIA1:
          Block size:        32256
          Group size:        10
          Buffer count:      51
          
          [ACMSDI_DEV.BLD_V22.ECO1.AXP]ACMSDI$FORMS_MANAGER_SHR.EXE;1
                                                                     46  
          21-OCT-1996 08:57
          [ACMSDI_DEV.BLD_V22.ECO1.AXP]ACMSDI$MSG.EXE;1              20  
          21-OCT-1996 08:52
          [ACMSDI_DEV.BLD_V22.ECO1.AXP]ACMSDI$SERVER.EXE;1            8  
          21-OCT-1996 08:57
          [ACMSDI_DEV.BLD_V22.ECO1.AXP]ACMSDI$SERVER_SHR.EXE;1      632  
          21-OCT-1996 08:57
          [ACMSDI_DEV.BLD_V22.ECO1.AXP]ACMSDI$TSS_SHR.EXE;1          48  
          21-OCT-1996 08:57
          [ACMSDI_DEV.BLD_V22.ECO1.AXP]ACMSDI022_ECO1.RELEASE_NOTES;1
                                                                      5  
          16-SEP-1996 14:44
          [ACMSDI_DEV.BLD_V22.ECO1.AXP]ACMSDI_ECO_ALPHA.KIT;1         2  
          18-JUL-1996 17:36
          [ACMSDI_DEV.BLD_V22.ECO1.AXP]ACMSDI_ECO_LEVEL.DAT;1         1  
          16-JUL-1996 10:06
          [ACMSDI_DEV.BLD_V22.ECO1.AXP]KITINSTAL.COM;1               24  
          30-AUG-1996 13:35
          
          Total of 9 files, 786 blocks
          End of save set
T.RTitleUserPersonal
Name
DateLines
848.1UCROW::GIBSONTue Apr 22 1997 18:5026
    It looks like they have the V2.2 ECO 1 kit for Alpha and VAX with VMS
    6.n. That is correct to allow them to run V2.2 clients. Installing
    those ECO kits after installing the V2.2 kits, should set up the server
    side OK. Those ECO kits do not include the client code, they fix bugs on 
    the server side. So they would not in and of themselves help remove the
    client DLL error messages, the server update is needed to allow the
    V2.2 clients to be used. In the same public directory tree [.v22.eco1]
    there are  directories that have the corresponding ECO1 client kits, so
    your customer needs those also to override the client code shipped on
    the V2.2 SSB kit.
    
    At that point the server and client should be running V2.2 plus ECO1
    and it would be good to do some testing to see that everything other
    than the VB4 32 bit client is working as expected just to establish 
    the new operating environment.
    
    Then they will also need the [.v22.vb4] files in order to use VB in 32 bit
    mode which I think is where the earlier notes were trying to get to.
    
    If the DLL error messages are still occuring, it might indicate that
    the files on the PC are not as expected, and NT is finding the wrong 
    DLLs in its search path. Let us know where in the above process the
    customer is and what exactly are the error indications that they are
    now getting and the dates/sizes of the acmsdi DLLs on the system.
    
    Tom