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

Conference utrop1::linkworks_v3

Title:LinkWorks V3.0 Notes Conference
Notice:LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:tacklr.apd.dec.com::TACK_Lm::TACK_L
Created:Tue Jun 28 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:8338

2231.0. "Help with LNX.UPD in 32-bit Client" by TROOA::TROTTI (VAX..more than just a vacuum cleaner) Tue May 13 1997 19:14

    I am using the 32 bit Linkworks client on NT 3.51 / Win 95 / NT 4.0
    and I am curious about the use of the LNX.UPD file.  
    
    If I include lines such as:
    
    environ.ini[Environment]HOSTOPXM=142.43.32.12
    
    it will modify The following Registry entry:
    HKEY_CURRENT_USER
       SOFTWARE
    	  DIGITALEQUIPMENT
              LINKWORKS
                ENVIRON
                  ENVIRONMENT
                      HOSTOPXM
    
    Now, how would I modify something in HKEY_LOCAL_MACHINE or if possible
    other locations in the Registry.
    
    Thanks,
    
    Mike Trotti
    Bank of Montreal Team
T.RTitleUserPersonal
Name		DateLines
2231.1UTROP1::PETERS_MWed May 14 1997 18:525
    You cannot change other entries in the registry. Of course, the lnx.upd
    file is only to change LinkWorks client entries. lnx.upd allows you to
    change all entries.
    
    Martin
2231.2It works with 16-bit Applications.TROOA::TROTTIVAX..more than just a vacuum cleanerThu May 15 1997 17:0510
    The 16-bit version seems to allow you to change any ".INI" file so why
    can't it change Registry Entries for other products.
    
    Also, there are Linkworks client entries in Hkey_Local_Machine. So at the
    very least it would be nice to change these entries as well.
    
    Thanks,
    
    Mike Trotti
    Bank of Montreal Team