MSHELP.DLL must be located in the path set by LIBPATH in your CONFIG.SYS
file in order to use Help in PWB under OS/2.
NMK Utility
-----------
The NMK utility (NMK.COM) should not be used within PWB. To get help on
NMK, type QH NMK from the command line.
ILINK and BIND Utilities
------------------------
Documentation for the ILINK and BIND utilities is included online for
compatibility with Microsoft C. These utilities are not included with
Microsoft BASIC and are not supported by BASIC.
I/O within LPRINT, PRINT #, PRINT # USING, WRITE, and WRITE USING
-----------------------------------------------------------------
If you use any of these output statements with an argument that is,
itself, an input/output statement, the output will go to the
console screen rather than the expected file or device. To avoid this
problem, use a variable to get input, and use that variable as the
argument to the statement that will perform the output. In the following
example output will always go to the screen:
OPEN "Test1.dat" FOR INPUT AS #1
OPEN "Test2.dat" FOR OUTPUT as #2
PRINT #2, INPUT$(10, #1)
The following rewritten example will send output to the proper place:
OPEN "Test1.dat" FOR INPUT AS #1
OPEN "Test2.dat" FOR OUTPUT AS #1
TEXT$ = INPUT$(10, #1)
PRINT #2, TEXT$
Output is also sent to the screen if you use an argument that is a
user-defined function that also performs input/output. You must not
use user-defined functions that perform I/O as arguments to any of the
preceding output statements.
Debugging Custom Run-Time Modules with CodeView
------------------------------------------------
You can debug custom run-time modules with CodeView only in protected mode
(CVP.EXE). To do this you must prepare the run-time module as follows:
1. Compile the source files using the CodeView options (/Zi or /Zd).
2. Set the LINK environment variable to include the /CO (CodeView) option.
3. Run the BUILDRTM utility to create the custom run-time module.
After you run BUILDRTM, you should set the LINK environment variable back to
its original setting.
References to Version Numbers in Filenames
------------------------------------------
The references to the filenames for the BASIC run-time libraries and run-
time modules in the "BASIC Language Reference" and "Programmer's Guide"
include the 7.0 version number, e.g. BRT70ENR.LIB. Change these to include
the 7.1 version number, e.g. BRT71ENR.LIB.
=======================================================================
Part 2: Notes for "Microsoft BASIC Language Reference"