Description of Stub Files and How They May Enlarge EXE (62908)

SUMMARY

The stub files provided with Microsoft Basic Professional Development System (PDS) versions 7.00 and 7.10 for MS-DOS should be used only under specific circumstances. If used incorrectly, linking with the stub files may actually increase the size of the executable file.

For more information about when to link with stub files, the effects of each of the stub files, and when linking each stub file may increase or decrease the size of a program, please see the following article in the Microsoft Knowledge Base:

62459 (Complete) Stub File Description and How They May Enlarge EXE

MORE INFORMATION

Please see the above-mentioned article for more specific information about when to use the following Basic PDS 7.00 and 7.10 stub files:

NOCGA.OBJ, NOEGA.OBJ, NOOGA.OBJ, NOHERC.OBJ NOVGA.OBJ NOGRAPH.OBJ
NOCOM.OBJ, NOLPT.OBJ
SMALLERR.OBJ
87.LIB
NOEVENT.OBJ
NOEMS.OBJ
OVLDOS21.OBJ
NOFLTIN.OBJ
NOEDIT.OBJ
TSCNIONR.OBJ
TSCNIOFR.OBJ
TSCNIONP.OBJ
TSCNIOFP.OBJ
NOTRNEMR.LIB
NOTRNEMP.LIB
NOISAM.OBJ

Most stub files are useful only when you are compiling for use with BCL7nxxx.LIB (compiling with BC /O) or making a customized run-time module. When you compile for use with the default BRT7nxxx.EXE run-time module, the support for Basic language features is already built into the run-time module and cannot be stubbed out without rebuilding (customizing) the run-time module itself. (Two exceptions to this are NOEMS.OBJ and OVLDOS21.OBJ, which affect overlay support in the Basic compiled executable .EXE program and don't affect the run-time module.)