Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month!
X-Hacker.org- Blinker 5.10 Online Reference - <b> setting up the environment</b> http://www.X-Hacker.org [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 Setting up the environment
------------------------------------------------------------------------------
 The PATH environment variable

 The PATH environment variable should be set to include the directory in
 which the files BLINKER.COM, BLINKER.DLL and BLINKER.EXE are installed. The
 installation program automatically updates the PATH environment variable to
 point to the BIN subdirectory of the Blinker installation directory.

 If you copy or move the Blinker files to a new directory, make sure you
 adjust the PATH accordingly, and make sure you copy or move all the above
 three files together, and keep them all in the same directory.
 Blinker can use the following environment variables at link time to locate
 object modules and libraries:

 The OBJ environment variable

 In the event that the .OBJ files specified in the link file are not in the
 current directory, and no path has been specified in the FILE command, the
 OBJ environment variable may be set to a list of paths which Blinker should
 use to find the required .OBJ files. It is often useful to point the OBJ
 environment variable to the directory containing any .OBJ files always
 required by your compiler, or to a directory containing third party
 libraries and .OBJ files (or both places).

 The LIB environment variable

 The LIB environment variable may be set to a list of paths to inform Blinker
 where to find the .LIB files specified in the script file if they are not in
 the current directory. Blinker also uses this variable to locate script
 files if they cannot be found in the current directory.

 The TMP or TEMP environment variable

 The TMP or TEMP environment variable may be set to a path to inform Blinker
 where to place temporary files at link time if there is not enough memory
 to complete the link. The Blinker DOS extender also uses these variables to
 determine where to place its virtual memory swap file if there is
 insufficient program memory at run time.

 For more details on these environment variables, and for a description of
 the use of the BLINKER environment variable to control the program at
 runtime, see the section in Chapter 2 on environment variables.

Online resources provided by: http://www.X-Hacker.org --- NG 2 HTML conversion by Dave Pearson