Tools for utilizing MS-DOS environment variables in Windows 95

HOW TO USE
----------
This software is intended for use under the following circumstances:

1. When you're required to set environment variables in a Windows NT
   Logon Script. (Especially for a Windows 95 machine!)

2. You use environment variables in the command line of programs, or
   alternate drive mappings between identical servers for load balancing
   network traffic.

3. For any other reason you need to disable the link tracking feature
   of a shortcut. [See SHORTCUT.EXE below!]

The logon script processor for Windows NT logon scripts does not support
setting environment variables in Windows 95.  WINSET.EXE is a Win32
console application that overcomes this limitation!  When called from a
batch file (including an NT Logon script) it sets an environment variable
in Window's global environment.  Please note that WINSET.EXE does not set
an environment variable in the batch file's environment, only Window's
global environment.  The syntax for WINSET.EXE is the same as the SET
command in DOS, with one exception.  It won't list all the environment
variables set.


A convenient way to view Window's global environment variables is to
start an MS-DOS Prompt (duplicating the global environment variables)
then use the SET command.


C:\WINDOWS>WINSET /?
Sets or removes Windows master environment variables.

WINSET [variable=[string]]

  variable  Specifies the environment-variable name.
  string    Specifies a series of characters to assign to the variable.




SHORTCUT.EXE
============

Network clients often have shortcuts to programs that reside on network
servers.  Although shortcut files support the use of variables in the
working directory, they do not support them in a command line. Therefore,
this cannot be used for load balancing between servers.  Another method
employed by network administrators is to alternately drive mappings to
different servers that are mirrors of each other.  Because shortcut files
track the links to the original network resource, this method is also
defeated.

SHORTCUT.EXE permits this method by disabling the "link tracking" feature
of Shortcut files.  Running shortcut.exe with the -s switch on a target
shortcut file will prevent the shortcut from finding the original server
associated with the drive letter.

Example:
           shortcut -c -s -n myshortcut.lnk

 This example will disable the link tracking feature of myshortcut.lnk ;
 Where myshortcut.lnk is the long name of the shortcut file.

 For further documentation of shortcut.exe execute the command
 "shortcut.exe -?". 

 Do not use shortcut.exe to dump extended characters.  [?]



C:\WINDOWS>SHORTCUT -?

shortcut: [-? -h -f -c -r -s] [[-t] target [[-n] name]] [-d working directory]
        [-a Arguments] [-i Iconfile] [-x Icon index] [-u {all|[natdix]}]

  -? -h        This help
  -f           Force overwrite of an existing short cut
  -c           Change existing shortcut
  -s           Make shortcut non tracking (Stupid)
  -r           Resolve broken shortcut
  -t target    Specifies the target of the shortcut
  -n name      Specifies the file name of the shortcut file
  -d directory Specifies the directory name to start the application in
  -a arguments Specifies the arguments passed when the shortcut is used
  -i iconfile  Specifiles the file the icon is in
  -x index     Specifies the index into the icon file
  -u [spec]    Dumps the contents of a shortcut. 'all' is the same as 'natdix'
               but the letters of 'natdix' can be specified to display specific
               fields in the shortcut (repeats allowed, and order followed)


EOF.