Category : Miscellaneous Language Source Code
Archive   : SCOPE1.ZIP
Filename : SCOPE.DOC

 
Output of file : SCOPE.DOC contained in archive : SCOPE1.ZIP



















The CodeScope Reference Manual
Version 1.00








CodeCrafters
Post Office Box 1317
Londonderry, NH 03053-1317
CIS 73647,1011

























Copyright (C) 1988 by CodeCrafters.
All rights to The CodeScope are reserved by CodeCrafters.


The CodeScope is a User Supported software product which
represents many, many hours of hard work and dedication.
"User Supported" means if you use this product on a regular
basis, you should become a registered user. The amount of
time and effort spent to support and enhance this product is
directly proportional to the number of its registered users.
User Supported software is distributed in its original,
unmodified form, without charge, via computer users group
software libraries, electronic bulletin boards and
friend-to-friend sharing. This unique distribution method
greatly reduces the cost of software marketing, resulting in
a reasonably priced product to the end user. User Supported
software is protected by copyright law to the same extent as
traditionally marketed software products, it is NOT public
domain software.

Fees for various user registration types are shown below, and
please remember, only YOU can make User Supported software
work !!!

Individual User (1 CPU) ..................... $25
Institutional User (1-10 CPUs) .............. $50
Institutional User (11-50 CPUs) ............. $100
Institutional User (Over 50 CPUs) ........... $200

As major revisions or bug fixes are made available, all
individual users are notified by mail and all institutional
users will receive one (1) diskette containing the new
version of the software. Updates to individual users, and
additional copies to institutional users, are available for a
$5 diskette and shipping fee.

Complete program source code for The CodeScope is available
to registered users when a signed and dated "The CodeScope
Source Code License Agreement" is included with your
registration fee.

The latest version of all CodeCrafters products are always
available, in executable form only, via the IBM Software
Forum of the CompuServe Information Service. ("GO IBMSW",
keyword "CODECRAFTERS")

All questions, problems, suggestions and/or comments
concerning The CodeScope should be sent to:


CodeCrafters
Post Office Box 1317
Londonderry, NH 03053-1317
CIS 73647,1011


CodeCrafters is a member of The Association of Shareware
Professionals (ASP) and subscribes to its guidelines for
product marketing and support.





The CodeScope User Registration Form


Name: ___________________________________________________

Company: ___________________________________________________

Street: ___________________________________________________

City: ___________________________________________________

State: ______________________________ Zip ________________

************************************************************

Registration: ___ Individual User (1 CPU) ............. $25

___ Institutional User (1-10 CPUs) ...... $50

___ Institutional User (11-50 CPUs) ..... $100

___ Institutional User (Over 50 CPUs) ... $200

************************************************************

Product Update Contact (Institutional Users ONLY)

Name: ___________________________________________________

Company: ___________________________________________________

Street: ___________________________________________________

City: ___________________________________________________

State: ______________________________ Zip ________________

************************************************************

Do you wish to receive The CodeScope source code ? ___

Have you enclosed a SIGNED and DATED License Agreement ? ___

ABSOLUTELY NO SOURCE CODE WILL BE SHIPPED WITHOUT A SIGNED
AND DATED SOURCE CODE LICENSE AGREEMENT. NO EXCEPTIONS !!!

************************************************************

Comments: __________________________________________________

____________________________________________________________


CodeCrafters
Post Office Box 1317
Londonderry, NH 03053-1317
CIS 73647,1011



The CodeScope Source Code License Agreement


CodeCrafters grants ___________________________________ a
nonexclusive, nontransferable license to use The CodeScope
source code for personal, non-commercial use subject to the
terms and conditions of this Agreement.

1. You may NOT transfer, assign or sublicense The CodeScope
source code without the prior written consent of
CodeCrafters.

2. You may incorporate portions of The CodeScope source code
into any product of your creation provided that product is
significantly different from The CodeScope.

3. This license is granted by CodeCrafters on an "as is"
basis. CodeCrafters makes no warranties either express or
implied as to the accuracy, reliability or merchantability
for any particular use of The CodeScope source code.

4. This Agreement shall be construed according to the laws
of the State of New Hampshire and contains the entire
agreement of the parties. No representations, promises,
agreements or understandings, written or oral, not contained
herein shall be valid or binding unless presented in writing
and signed by the party to be charged.



___________________________ ___________________________
Signature of Licensee President

___________________________
Address of Licensee CodeCrafters
Post Office Box 1317
___________________________ Londonderry, NH 03053-1317


___________________________ ___________________________
Date Date



















Table Of Contents


1.0 What Is The CodeScope ? . . . . . . . . . . . . . . . 1

2.0 Getting Started . . . . . . . . . . . . . . . . . . . 2

3.0 CSM - The CodeScope Monitor . . . . . . . . . . . . . 3

4.0 CSA - The CodeScope Analyzer . . . . . . . . . . . . 5

5.0 CSC - The CodeScope Converter . . . . . . . . . . . . 9

6.0 Interactive CSA Operation . . . . . . . . . . . . . . 11

7.0 Special Usage Notes . . . . . . . . . . . . . . . . . 12

7.1 Analyzing Turbo Pascal Programs . . . . . . . . . 12

7.2 Analyzing Assembler Programs . . . . . . . . . . 12

7.3 Resident Software and CSM . . . . . . . . . . . . 12

8.0 Error Messages . . . . . . . . . . . . . . . . . . . 13


































The CodeScope - Version 1.00 Page 1

1.0 What Is The CodeScope ?

The CodeScope is a symbolic program execution profiler
designed to enable the identification of heavily used or slow
portions of a program, or to gain a better understanding of
where a program spends its time. Some of the features
provided by The CodeScope are:

* Adjustable execution sampling rates from 11 to 99
milliseconds.

* Dynamic control of execution sampling via "hot keys".

* "Full System" or "Program Only" execution sampling.

* Three execution analysis reports, including two
histograms.

* Support for character, extended ASCII and ANSI color
graphics histograms.

* Full support for PUBLIC symbols and source code line
numbers, via MAP file from DOS LINK and other Linkage
Editors.

The CodeScope requires an IBM PC/XT/AT/PS or compatible with
at least 128K of available memory running MS(PC)-DOS Version
2.10 or later. For owners of less than 100% IBM compatibles,
The CodeScope requires hardware timer, keyboard and speaker
interfaces which are compatible with the IBM PC/XT/AT/PS.




























The CodeScope - Version 1.00 Page 2

2.0 Getting Started

The CodeScope consists of three (3) files. "CSM.COM", The
CodeScope Monitor, which records execution samples of your
program, "CSA.COM", The CodeScope Analyzer, which analyzes
the execution samples to create reports detailing your
programs activity and "CSC.COM", The CodeScope Converter,
which converts symbol files from other Linkage Editors to the
format used by "CSA.COM". Three additional files are
provided for those users utilizing Microsoft Windows.
"CSM.PIF", "CSA.PIF" and "CSC.PIF" are the Program
Information Files for use with "CSM.COM", "CSA.COM" and
"CSC.COM", respectively.

The files "SIEVE.C", "SIEVE.COM", "SIEVE.CSM" and "SIEVE.MAP"
are provided as samples. All figures in this manual were
created using actual data from this sample program.

The most convenient method of executing The CodeScope is to
place all program files on the default drive or within the
DOS search path. The Program Information Files, if required,
should be placed in the same directory as the program files
or within the Microsoft Windows PIF directory.

The CodeScope supports both popular switch characters, "/"
for DOS enthusiasts and "-" for UNIX enthusiasts. Both
switch characters are functionally equivalent. For the
purposes of this manual, the "/" character will be used.






























The CodeScope - Version 1.00 Page 3

3.0 CSM - The CodeScope Monitor

In order to analyze a programs performance, it is necessary
to execute the program under the control of the program
monitor, CSM. The format of the CSM command is depicted in
Figure 3.1.

+-----------------------------------------------------------+
| |
| CSM [d:][path]filename.ext |
| |
| [/D] |
| |
| [/P] |
| |
| [/Rn] |
| |
+- Figure 3.1: CSM Command Format --------------------------+

The operands which may appear with the CSM command are:

[d:][path]filename[.ext]

Provides the file specification of the program to be
monitored. Be sure to include the COM or EXE file
extension.

/D

Indicates execution sampling is to be initially disabled
when the program is given control. CSM allows dynamic
control of execution sampling. By means of a "hot key",
sampling can be enabled or disabled from the keyboard
while the program runs. To disable sampling, hold down
Ctrl and press the Left Shift key. CSM will respond
with a low frequency beep indicating sampling is
disabled. To enable sampling, again hold down Ctrl and
press the Right Shift key. A high frequency beep
indicates sampling is enabled. Execution sampling may
be disabled and enabled as often as desired with this
feature. By default, execution sampling is enabled.

/P

Indicates "Program Only", rather than "Full System",
execution sampling is to be used. "Full System"
execution sampling will include samples from all of
memory, including DOS, any TSR programs and ROM BIOS.
By default, "Full System" execution sampling is used.

/Rn

Provides the execution sampling rate, ranging from 1 to
9, to be used during program monitoring. Sampling can
occur as fast as 91 times per second (every 11 ms) and
as slow as 11 times per seconds (every 99 ms). The
available sampling rates are depicted in Figure 3.2.

The CodeScope - Version 1.00 Page 4

+------------------------------------------------------+
| |
| Value Rate Sample/Sec Maximum Time |
| ----- ----- ---------- ------------ |
| 1 11 ms 90.9 2 Min 45 Sec |
| 2 22 ms 45.5 5 Min 30 Sec |
| 3 33 ms 30.3 9 Min 15 Sec |
| 4 44 ms 22.7 11 Min 00 Sec |
| 5 55 ms 18.2 13 Min 45 Sec |
| 6 66 ms 15.1 16 Min 30 Sec |
| 7 77 ms 13.0 19 Min 15 Sec |
| 8 88 ms 11.4 21 Min 00 Sec |
| 9 99 ms 10.1 24 Min 45 Sec |
| |
+- Figure 3.2: CSM Sampling Rates ---------------------+

The Maximum Time column shows how long execution samples
can be gathered before the data buffer is exhausted, at
which time all subsequent samples are discarded. By
default, samples are recorded every 55 ms.

For example, a sample CSM session to monitor the SIEVE
benchmark is depicted in Figure 3.3.

+-----------------------------------------------------------+
| |
| C> CSM SIEVE.COM /R1 |
| |
| CSM - The CodeScope Monitor - Version 1.00 |
| Copyright (C) 1988 by CodeCrafters. All rights reserved. |
| |
| Enter command arguments: |
| > SIEVE _ |
| |
| Execution begins ... |
| |
| 25 iterations = 4.34 seconds |
| |
| ... Execution completed. |
| |
| |
| C> |
| |
+- Figure 3.3: Sample CSM Session --------------------------+

A disk file by the name "SIEVE.CSM" is created in the current
directory which contains the execution sample data gathered
during this CSM session. This file will be used as input to
The CodeScope Analyzer described later in this manual.

CSM can monitor all types of programs EXCEPT one, which is
any program that intercepts the External Timer interrupt (INT
08H). Attempting to monitor this type of program should not
result in a system crash, but may cause the DOS system clock
to lose or gain time. Since most time dependant programs use
the Timer Tick interrupt (INT 1CH) to mark time, this
restriction should not create any problems.

The CodeScope - Version 1.00 Page 5

4.0 CSA - The CodeScope Analyzer

Once a program has been monitored with CSM, the execution
sample data gathered must be processed by the program
analyzer, CSA. The format of the CSA command is depicted in
Figure 4.1.

+-----------------------------------------------------------+
| |
| CSA [d:][path]filename[.ext] |
| |
| [/G{A|C|X}] |
| |
| [/I] |
| |
| [/Lnn.n] |
| |
| [/M[[d:][path]filename[.ext]] |
| |
| [/O[[d:][path]filename[.ext]] |
| |
| [/R[D][E][S]] |
| |
| [/S{A|N|P}] |
| |
| [/Zname] |
| |
+- Figure 4.1: CSA Command Format --------------------------+

The operands which may appear with the CSA command are:

[d:][path]filename[.ext]

Provides the file specification of the execution sample
data created by CSM.

/G{A|C|X}

Selects (A)NSI color, ASCII (C)haracter or e(X)tended
ASCII character graphics for analysis histograms. The
ANSI.SYS device driver or equivilent is required for
ASNI color graphics. By default, extended ASCII
character graphics are used.

/I

Indicates "Interactive Analysis" mode is to be used.
CSA will take a fair amount of time to process a
large execution sample file. This is of little concern
when producing a single set of reports, but can become
an inconvenience when performing iterative analysis.
Interactive analysis mode allows repeated report
creating and iterative analysis. The Interactive
Analysis Mode is described later in this manual.




The CodeScope - Version 1.00 Page 6

/Lnn.n

Provides the lower percentage limit for analysis
histograms. All items below this percentage value are
grouped in the histogram item "Below Limit %". By
default, the minimum percentage value is 1.0.

/M[[d:][path]filename[.ext]]

Provides the file specification of the DOS LINK MAP file
to be used for PUBLIC Symbols and source code line
numbers. Symbols allow easy identification of the
procedure and function names used when writing the
program. Line numbers take that a step further by
breaking functions down into individual source lines.
Both PUBLIC symbols and line number data must be created
by a language compiler for them to be available. LINK
must also be directed to create a MAP file using the
"/M" and "/LI" switches. Two 2 "built-in" symbols
(FDISK BIOS and ROM BIOS) are provided to identify these
critical components of program execution. By default,
the CSA file with the same filename portion as the
execution sample file is used, if one exists, otherwise
the MAP file with the same filename is used. A
different MAP may be specified, or the MAP file may be
bypassed entirely by using "/M" without a file
specification.

/O[[d:][path]filename[.ext]]

Provides the file specification for the output reports
and histograms. By default, the output is produced to
the standard output device.

/R[D][E][S]

Selects (D)OS Function Analysis, (E)xecution Analysis
and/or Execution (S)tatistics reports be produced. By
default, all reports are produced.

/S{A|N|P}

Selects (A)ddress, (N)ame or (P)ercentage sequence for
histogram items. By default, histogram items are shown
in Address sequence.

/Zname

Provides the Function or Segment name to be "zoomed-in".
The entire name need not be typed, just enough to be
uniquely identify it, and the comparison is NOT case
sensitive. To zoom-in one of the "built-in" symbols,
use only the first word of the name.

For example, a sample CSA session to analyze the SIEVE
benchmark is depicted in Figure 4.2.


The CodeScope - Version 1.00 Page 7

+-----------------------------------------------------------+
| |
| C> CSA SIEVE |
| |
| CSA - The CodeScope Analyzer - Version 1.00 |
| Copyright (C) 1988 by CodeCrafters. All rights reserved. |
| |
| Processing SIEVE.MAP ... |
| |
| Processing SIEVE.CSM ... |
| |
| |
| EXECUTION STATISTICS |
| |
| Program Name : SIEVE.COM |
| Command Line : |
| Return Code : 0000 |
| Elapsed Time : 00:00:04.51 |
| Total Samples : 413 at 11ms intervals |
| DOS Functions : 16 |
| CSM Options : /R1 |
| Symbol File : SIEVE.MAP |
| |
| |
| EXECUTION ANALYSIS |
| |
| Symbol/Address Cnt Pct 0% 10% 20% 30% 40% 100 |
| +--------------+-----+-----+|++++|++++|++++|++++|+++\\++| |
| |1816:0000-FFFF| 6| 1.5|| . . . . // | |
| |main | 351| 85.0||***********************\\ | |
| |memset | 44| 10.7||***** . . . // | |
| |Below Limit % | 12| 2.9||* . . . . \\ | |
| +--------------+-----+-----++-----------------------//--+ |
| Totals ....... 413 100.0 (Percentage of ... |
| |
| |
| DOS FUNCTION ANALYSIS |
| |
| Function Name Cnt Pct 0% 10% 20% 30% 40% 100 |
| +--------------+-----+-----+|++++|++++|++++|++++|+++//++| |
| |Get Sys Time | 2| 12.5||****** . . . \\ | |
| |Get Version | 2| 12.5||****** . . . // | |
| |Close File | 5| 31.3||*************** . \\ | |
| |Write File | 1| 6.3||*** . . . . // | |
| |IOCTL | 1| 6.3||*** . . . . \\ | |
| |Alloc Memory | 1| 6.3||*** . . . . // | |
| |Release Memory| 1| 6.3||*** . . . . \\ | |
| |SETBLOCK | 2| 12.5||****** . . . // | |
| |Exit Process | 1| 6.3||*** . . . . \\ | |
| +--------------+-----+-----++-----------------------//--+ |
| Totals ....... 16 100.0 (Percentage of ... |
| |
| |
| C> |
| |
+- Figure 4.2: Sample CSA Session --------------------------+


The CodeScope - Version 1.00 Page 8

Unfortunately, this sample does not do justice to the actual
output since extended ASCII graphics characters could not be
used in this manual for greatest printer compatibility. The
extended ASCII graphics are quite impressive, especially when
combined with the ANSI color option and the ANSI.SYS device
driver or equivilent.




















































The CodeScope - Version 1.00 Page 9

5.0 CSC - The CodeScope Converter

To get the maximum benefit from CSA, PUBLIC symbols and
source code line numbers should be used. CSA can directly
process the MAP file created by LINK to extract the required
information. However, CSA cannot directly process similar
files created by other Linkage Editors, this is the job of
the symbol file converter, CSC. Currently, CSC supports
conversion of both EXE files and SYMTABLE data created by
PLINK86 (Phoenix Software Associates) and related utilities.
CSC may also be used to convert a MAP file created by LINK
into the raw PUBLIC symbol and source code line number data
to conserve disk space. The format of the CSC command is
depicted in Figure 5.1.

+-----------------------------------------------------------+
| |
| CSC [d:][path]filename[.ext] |
| |
| [/D] |
| |
| [/P] |
| |
| [/S] |
| |
+- Figure 5.1: CSC Command Format --------------------------+

The operands which may appear with the CSC command are:

[d:][path]filename[.ext]

Provides the file specification of the symbol file to be
converted. If the extension portion is omitted, MAP is
assumed for LINK files, EXE for PLINK86 files and SYM
for PLINK86 SYMTABLE output.

/D

Indicates a DOS LINK MAP file is to be converted. By
default, the input file is assumed to be a MAP file
created by LINK.

/P

Indicates a PLINK86 EXE file is to be converted. Be
sure to specify the "SYMTABLE" option to PLINK86.

/S

Indicates PLINK86 SYMTABLE data is to be converted. Be
sure to redirect the output of the SYMTABLE utility to a
file prior to executing CSC when this option is used.
This option is provided in case the PLINK86 EXE file
conversion fails due to an "Unknown symbol type" error.

For example, a sample CSC session to convert a PLINK86 EXE
file is depicted in Figure 5.2.

The CodeScope - Version 1.00 Page 10

+-----------------------------------------------------------+
| |
| C> CSC SIEVE /P |
| |
| CSC - The CodeScope Converter - Version 1.00 |
| Copyright (C) 1988 by CodeCrafters. All rights reserved. |
| |
| Converting SIEVE.EXE ... |
| |
| ... Conversion completed. |
| |
| |
| C> |
| |
+- Figure 5.2: Sample CSC Session --------------------------+

A disk file by the name "SIEVE.CSA" is created in the current
directory which contains the PUBLIC symbols and source code
line numbers for use by CSA.

CodeCrafters will make every effort to support other Linkage
Editors in order to make The CodeScope a more valuable
product. Please provide us with a copy of the EXE file and
corresponding symbol file created by the Linkage Editor. If
at all possible, also provide a MAP file created by LINK for
the same EXE file for reference. When support has been
added for the Linkage Editor, a free update will be sent
along with the return of all submitted materials. Any other
information which will assist us in providing this support
would be greatly appreciated.




























The CodeScope - Version 1.00 Page 11

6.0 Interactive CSA Operation

For ease of use when performing iterative analysis, CSA
provides an interactive mode during which CSA prompts for
options. Each time Return is pressed, CSA will evaluate the
options entered to produce the desired report(s), and prompt
for more options. Any CSA command line option may be
specified, with or without the leading "/", except /I or /M.
The only option which is automatically reset after each
iteration is /Z. When the desired output has been obtained,
respond to the prompt with EXIT and press Return.

For example, a sample interactive CSA session to analyze the
SIEVE benchmark is depicted in Figure 6.1.

+-----------------------------------------------------------+
| |
| C> CSA SIEVE /I |
| |
| CSA - The CodeScope Analyzer - Version 1.00 |
| Copyright (C) 1988 by CodeCrafters. All rights reserved. |
| |
| Processing SIEVE.MAP ... |
| |
| Processing SIEVE.CSM ... |
| |
| Enter options or 'EXIT': /RE |
| |
| EXECUTION ANALYSIS |
| |
| Symbol/Address Cnt Pct 0% 10% 20% 30% 40% 100 |
| +--------------+-----+-----+|++++|++++|++++|++++|+++\\++| |
| |1816:0000-FFFF| 6| 1.5|| . . . . // | |
| |main | 351| 85.0||***********************\\ | |
| |memset | 44| 10.7||***** . . . // | |
| |Below Limit % | 12| 2.9||* . . . . \\ | |
| +--------------+-----+-----++-----------------------//--+ |
| Totals ....... 413 100.0 (Percentage of ... |
| |
| Enter options or 'EXIT': /ZMAIN |
| |
| EXECUTION ANALYSIS OF main |
| |
| Line No/Offset Cnt Pct 0% 10% 20% 30% 40% 100 |
| +--------------+-----+-----+|++++|++++|++++|++++|+++\\++| |
| |Line 22 | 204| 58.1||***********************// | |
| |Line 23 | 147| 41.9||******************** \\ | |
| +--------------+-----+-----++-----------------------//--+ |
| Totals ....... 351 100.0 (Percentage of ... |
| |
| Enter options or 'EXIT': EXIT |
| |
| |
| C> |
| |
+- Figure 6.1: Sample Interactive CSA Session --------------+


The CodeScope - Version 1.00 Page 12

7.0 Special Usage Notes

7.1 Analyzing Turbo Pascal Programs (Version 3.0 and Older)

Turbo Pascal (Version 3.0 and older) does not provide any
form of PUBLIC symbol or line number information normally
found in the MAP file created by LINK. To analyze a Turbo
Pascal program at source code level, create an enlarged
EXECUTION ANALYSIS histogram of the program segment with the
/Z command line switch or interactive option. This histogram
shows the programs execution at 16 byte intervals. The Turbo
Pascal "Find run-time error" option may then be used to
locate which source code line(s) relate to each histogram
item. Turbo Pascal will only find run-time errors within the
source program, so if the error cannot be found, it is not
within the source program.


7.2 Analyzing Assembler Programs

In order to obtain the full benefit of CSAs use of PUBLIC
symbols, be sure to declare all procedures and labels within
the program as "PUBLIC" and direct LINK to create a MAP file
with the "/M" switch. This will allow CSA to show the same
procedure and label names which were used on the EXECUTION
ANALYSIS histogram. These PUBLIC declarations may be removed
after completing final performance tuning.


7.3 Resident Software and CSM

If any type of system hang should be encountered when using
CSM to monitor a program, try removing all resident software
being used and then attempt the monitoring session again. If
this fails to resolve the problem, be sure the program being
monitored correctly restores any interrupt vectors which it
intercepts. Also, be sure at least 16 bytes of stack space
is available for CSM during a monitor session. Most system
hangs when using CSM are caused by resident software,
improper clean-up by the program being monitored or stack
corruption due to insufficient stack size.


















The CodeScope - Version 1.00 Page 13

8.0 Error Messages

CSM, CSA and CSC display messages when errors are detected.
Most messages indicate fatal errors, from which CSM, CSA and
CSC cannot recover. Some fatal errors are considered
non-fatal when using the interactive analysis mode of CSA.
The following is a summary of those messages along with their
explanations:


File Not Found

The file specified for the program to be monitored could
not be found.


Input file does not contain symbol data

The file specified for PLINK86 EXE conversion was not
created by PLINK86 OR was created without the SYMTABLE
option.


Input file is not a valid EXE file

The file specified for PLINK86 EXE conversion does not
have a valid EXE header signature.


Insufficient disk space

The execution sample file could not be created due to a
lack of disk space.


Insufficient memory

The program to be monitored requires more memory than is
currently available.


Invalid CSM file format

The file specified for the execution sample file did not
contain a valid CSM file header.


Invalid CSM file specification

An invalid file specification was specified for the
execution sample file.


Invalid MAP file specification

An invalid file specification was specified for the /M
command line switch.

The CodeScope - Version 1.00 Page 14

Invalid input file specification

An invalid file specification was specified for the
Linkage Editor symbol file.


Invalid /G option

A value other than "A", "C" or "X" was specified for the
/G command line switch or interactive option.


Invalid /L option

A non-numeric value or a numeric value less than "00.0"
or greater than "99.9" was specified for the /L command
line switch or interactive option.


Invalid /R option

A value other than "D", "E" or "S" was specified for the
/R command line switch or interactive option.


Invalid /S option

A value other than "A", "N" or "P" was specified for the
/S command line switch or interactive option.


Invalid /Z option

No routine or segment name was specified for the /Z
command line switch or interactive option.


Invalid file specification

An invalid file specification was specified for the
program to be monitored.


Invalid option

An unknown command line switch or interactive option was
encountered.


Out of memory

An attempt to allocate dynamic memory failed.


Path not found

The path of the file specified for the program to be

The CodeScope - Version 1.00 Page 15

monitored could not be found.


Premature end of CSM file

The file specified for the execution sample file did not
contain all the data indicated by the file header.


Unable to create CSA file

The file implied by the Linkage Editor symbol file could
not be created.


Unable to create output file

The file specified with the /O command line switch or
interactive option could not be created.


Unable to create work file

The work file required by PLINK86 EXE and SYMTABLE
conversion could not be created.


Unable to open CSM file

The file specified for the execution sample file count
not be found.


Unable to open MAP file

The file specified with the /M command line switch could
not be found.


Unable to open input file

The file specified for the Linkage Editor symbol file
could not be found.


Unable to reopen work file

The work file used by PLINK86 EXE and SYMTABLE
conversion could not be reopened.


Unknown symbol type at offset


An unknown PLINK86 symbol type was encountered during
PLINK86 EXE conversion. Please notify CodeCrafters and
provide a copy of the EXE file so PLINK86 support may
remain current.




  3 Responses to “Category : Miscellaneous Language Source Code
Archive   : SCOPE1.ZIP
Filename : SCOPE.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/