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

Conference abbott::teamlinks_windows

Title:TeamLinks for Windows
Notice:Kit and ECO locations: See replies to note 8.o note 8.
Moderator:ORION::chayna.zko.dec.com::tamara::eppesAN
Created:Mon Aug 28 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2238
Total number of notes:9650

2040.0. "DEFAULTS.INI and v2.7" by KERNEL::BURDENI () Mon Mar 10 1997 06:55

    I have a customer upgrading to v2.7 of Teamlinks, and he is getting the
    same problems with DEFAULTS.INI as mentioned in many previous notes
    (872 and 907 particularly).  The transport selection option
    SetupTransports=5 gets overridden, and DECnet is used. (3) 
    
    Previous notes have suggested that this is fixed in v2.5 by a new
    version of TLINSTAL.EXE, can anyone tell me if this was supposed to
    have been fixed in v2.7, or if it is still a known problem ?
    
    I have been looking at the CheckEnvironments=0 option as a way of
    overriding this feature, though I feel sure it will work, I am not sure 
    what the implications of this are for other installation elements.  Is
    there any information about this option and its effects.
    
    All comments appreciated.
    
    Ivan.
T.RTitleUserPersonal
Name		DateLines
2040.1MANANA::PRINCIPIOMon Mar 10 1997 09:5417
>    I have a customer upgrading to v2.7 of Teamlinks, and he is getting the
>    same problems with DEFAULTS.INI as mentioned in many previous notes
>    (872 and 907 particularly).  The transport selection option
>    SetupTransports=5 gets overridden, and DECnet is used. (3) 

This is not the same problem.  The problem described in those notes
deals specifically with the DisplayDialogs setting in DEFAULTS.INI
and that has been fixed in V2.7

If you are upgrading from V2.5 to V2.7 then users already have
a transport chosen and you have startup configurations with that
transport.  These startup configurations must be changed.  I don't
think this can be done during the installation.

.....helen
2040.2Checkenvironments optionKERNEL::BURDENIMon Mar 10 1997 10:337
    Please forgive me for re-iterating a point, but does that mean that the
    DEFAULTS.INI cannot be used during an upgrade to change the Transport
    selection.  If that is the case what happens when you use the
    Checkenvironments option.
    
    Many Thanks 
    Ivan
2040.3Well yes and noMANANA::PRINCIPIOMon Mar 10 1997 13:2428
>    Please forgive me for re-iterating a point, but does that mean that the
>    DEFAULTS.INI cannot be used during an upgrade to change the Transport
>    selection.  If that is the case what happens when you use the
>    Checkenvironments option.

Well, your default transport will be updated in your win.ini.  The
CheckEnvironments variable just tells the install to not bother
checking to make sure the proper software to make sure that chosen
transport will work is installed or not.  

The problem however is the first time you install TeamLinks and choose a
transport it creates the users startup configurations.  Subsequent
installations do not modify the startup configurations.  They are only 
modified if the user changes them.  They also include a transport.  These 
will still be set as they were regardless of what transport is chosen during 
an upgrade installation.  

So, although the install will update the Default XTI Transport in
the win.ini file, it will only be used if the user chooses Cancel
in the Startup Configurations dialog when they startup TeamLinks.
Otherwise if they choose one of the startup configruations listed
in that dialog or if they autoconnect, it will still be using
whatever transport those startup configurations are set to use.

......helen
2040.4ThanksKERNEL::BURDENITue Mar 11 1997 04:274
    Thanks for the extra info,  I just wanted to make sure I was clear on
    what was going on before I try to explain it to someone else.
    
    Ivan.
2040.5How complicated ?KERNEL::BURDENITue Mar 11 1997 04:3612
    Sorry, is it me or was that designed to confuse me, 
    Does CheckEnvironments have any effect on elements other than the
    transport ??
    
    >Well, your default transport will be updated in your win.ini.  The
    >CheckEnvironments variable just tells the install to not bother
    >checking to make sure the proper software to make sure that chosen
    >transport will work is installed or not.
    
    Thanks in advance.
    Ivan
2040.6XANADU::PRINCIPIOTue Mar 11 1997 08:2621
>    Sorry, is it me or was that designed to confuse me, 
>    Does CheckEnvironments have any effect on elements other than the
>    transport ??
>    
>    >Well, your default transport will be updated in your win.ini.  The
>    >CheckEnvironments variable just tells the install to not bother
>    >checking to make sure the proper software to make sure that chosen
>    >transport will work is installed or not.
    
Ivan,

Sorry about that.  I wasn't trying to confuse you.  I answered in
the context of the transport since that's what you were asking.
If you set CheckEnvironments off, it will take as much info from
the defaults.ini rather than checking the existing install or whether
or not various things are installed on the system.  It applies to
more than just the transport.  

.....helen