|
|
DataMuseum.dkPresents historical artifacts from the history of: CP/M |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about CP/M Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - download
Length: 5376 (0x1500)
Types: TextFile
Names: »READ.ME«
└─⟦d482c3728⟧ Bits:30005987 Turbo Pascal v2.00A (Jet80)
└─⟦this⟧ »READ.ME«
.HE
.L-
*****************************************************************
* *
* Print this document in the following way: *
* *
* 1. Exit Turbo Pascal *
* 2. Activate the TLIST program *
* 3. Answer READ.ME and press <RETURN> *
* 4. Press <RETURN> to question about Options. *
* *
* *
* If you want to change the left margin use the directive: *
* .PO (Page Offset E.g. .PO8) (the dot must be in column one). *
* *
* You may also use the .PL directive to set Page Length *
* *
*****************************************************************
.L+
.PO8
.PL66
Addendum to TURBO REFERENCE MANUAL
Z80 CP/M-80 8-bit Version
April 1984
(C) Copyright 1983, 1984 Borland International Inc.
.HEAddendum to the TURBO Pascal Reference Manual page: # ØFirst printing November 1983
.PA▶8a◀
.FO Continued....
-----------------------------------------------------------------
GETTING STARTED RIGHT NOW
-----------------------------------------------------------------
1. Make a copy of the distribution disk to a fresh disk.
2. Start TINST from your copy and select your terminal.
3. Exit TINST and type: TURBO
4. Type O for Options then C for Com file and Q for Quit.
5. Type Y for Yes
6. Type M for Main file and answer: MC
7. Type R for Run
Th▶e5◀ compile▶f2◀ wil▶ec◀ no▶f7◀ compil▶e5◀ th▶e5◀ fil▶e5◀ MC.PA▶d3◀ an▶e4◀ mak▶e5◀ the
file MC.COM which will be executed immediately.
If you run out of space on your disk, you may delete the
TINST*.* files since they are only needed to install TURBO.
.pa▶8a◀
-----------------------------------------------------------------
FILES ON THE DISTRIBUTION DISK
-----------------------------------------------------------------
----------------------------------------------------------------
! THE FILE YOU MUST HAVE TO DEVELOP AND COMPILE PROGRAMS !
----------------------------------------------------------------
! TURBO.COM Compiler and Editor !
----------------------------------------------------------------
----------------------------------------------------------------
! OPTIONAL FILES WHEN DEVELOPING PROGRAMS !
----------------------------------------------------------------
! TURBOMSG.OVR Error messages (You may omit this file) !
! TURBO.OV▶d2◀ eXecut▶e5◀ comman▶e4◀ (Yo▶f5◀ ma▶f9◀ omi▶f4◀ thi▶f3◀ file) !
! TLIST.COM Program lister !
----------------------------------------------------------------
----------------------------------------------------------------
! FILES YOU ONLY NEED WHEN YOU INSTALL TURBO !
----------------------------------------------------------------
! TINST.COM Installation program !
! TINSTMSG.OVR Message file for TINST !
! TINST.DTA Terminal definitions for TINST !
---------------------------------------------------------------
Onc▶e5◀ yo▶f5◀ hav▶e5◀ installe▶e4◀ TURB▶cf◀ t▶ef◀ you▶f2◀ satisfaction▶ac◀ yo▶f5◀ ma▶f9◀
delete these files from your working copy of TURBO Pascal.
I▶e6◀▶a0◀ yo▶f5◀ hav▶e5◀ installe▶e4◀ ne▶f7◀ terminal▶f3◀ the▶ee◀ yo▶f5◀ shoul▶e4◀ firs▶f4◀ mak▶e5◀ ▶e1◀
cop▶f9◀ o▶e6◀ TINST.DT▶c1◀ t▶ef◀ sav▶e5◀ you▶f2◀ corrections.
.PA
---------------------------------------------------------------
! RUN-TIME ERRORS IN OVERLAYS !
---------------------------------------------------------------
Run-time errors occurring in overlays are found as usual, and an
address is issued by the error handling system. This address,
however, is an address within the overlay area, and there is no
way of knowing which overlay subprogram was actually active when
the error occurred.
Run-time errors in overlays can therefore not always be readily
found with the Options menu's 'Find Run-Time Error' facility.
What 'Find Run-Time Error' will point out is the first occurence
of code at the specified address. This, of course, may be the
place of the error, but the error may as well occur in a subsequent
subprogram within the same overlay group.
This is not a serious limitation, however, as the type of error
and the way it occurs most often will indicate to you in which
subprogram the error happened. The way to locate the error
precisely is then to place the suspected subprogram as the first
subprogram of the overlay group. The 'Find Run-Time Error' will
then work.
THE BEST THING TO DO IS TO NOT PLACE SUBPROGRAMS IN OVERLAYS UNTIL
THEY HAVE BEEN FULLY DEBUGGED!«eof»