Retro video games delivered to your door every month!
Click above to get retro games delivered to your door ever month! Blinker 5.10 Online Reference - <b> 1109: unable to open file <filename></b> [<<Previous Entry] [^^Up^^] [Next Entry>>] [Menu] [About The Guide]
 1109: unable to open file <filename>
 This message indicates that Blinker was unable to find the specified file in
 the current directory where it was expected to be, so the full directory
 path for the file should be specified. If no file extension is specified for
 script files, Blinker assumes an extension of .LNK.

 If the file has been specified in the link script with a FILE command then
 check that the OBJ environment variable points to the correct location for
 the file (FILEs have a default extension of .OBJ). If it has been specified
 with a LIBRARY or SEARCH command then check the LIB environment variable
 (LIBs or SEARCHes have a default extension of .LIB).

 If the file is one of the Blinker protected mode .OBJ or .LIB files e.g.
 BLXxxxnn.LIB look in the OBJ or LIB subdirectory of the Blinker directory.
 If the file does not exist but there are a similarly named files with
 different extensions, then run the Blinker utility BLIBLD.EXE from the main
 Blinker directory. This should create the required .OBJ and .LIB files.

 This error can also occur when Blinker is attempting to create a swap file
 and the TEMP environment variable points to an invalid directory. When
 running on a network, it is also possible that another user deleted the file
 or that you do not have network access rights to the file.

Online resources provided by: --- NG 2 HTML conversion by Dave Pearson