home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
validat1.zip
/
README.DOC
< prev
next >
Wrap
Text File
|
1994-04-21
|
5KB
|
124 lines
Validator for OS/2
README File
Release Notes for the
Version 1.0 Developer Connection Beta
OS/2 2.x Series
Copyright (c) Prominare Inc., 1992, 1993, 1994
This document contains release notes for Version 1.0 of the
Validator for OS/2.
====================== < Contents > ========================
This file has 7 parts:
Part Content
---- -------
1 Documentation
2 Feedback
3 Header Usage
4 OS/2 2.0, 2.1 and 2.11
5 ViewPort Considerations
6 Compiler Differences
7 Problem Determination
=================== < Documentation > =======================
Hard copy documentation is not provided with this beta.
Online documentation is provided through the installation and
is found within the Validator folder. The PostScript
versions of the documentation are provided on the CD-ROM
but not copied your to system.
Two files are provided in the PostScript format: ParmErrs.PS
and Validatr.PS. If you have a PostScript compatible printer,
you only need to copy the files to the printer through an
OS/2 command prompt like the following from the CD-ROM:
copy \devtools\valbeta\*.ps lpt1:
====================== < Feedback > =========================
Validator is based on the released documentation for OS/2.
There may situations where you existing usage of an OS/2 API
works but is failed by the validation routines. If you feel
that this is incorrect, please post a note within the
Developer Connection area of the OSDF2 Forum on CompuServe.
Please make sure you denote the API and the parameter AND
how you are using it. This will allow for a response to
your note to be made indicating whether or not the usage is
correct and what the resolution will be.
==================== < Header Usage > =======================
It is extremely important that you use the method of
including the OS/2 API's through the os2.h, os2me.h and
penpm.h and INCL_* mechanism. The validation headers depend
on this mechanism to be able to properly redefine the API's
in certain cases.
Some of the samples as provided with the various toolkits,
like MMPM/2, ignore this mechanism and will include the
individual header files even though the toolkit documentation
recommends not doing this.
If you use a similar method, you may encounter compiler
errors where the compiler indicates an error in redefining
a function.
=============== < OS/2 2.0, 2.1 and 2.11 > ==================
The software has been tested on both OS/2 Version 2.0,
OS/2 Version 2.1 and OS/2 Version 2.11. The newer OS/2
Version 2.1 calls have been added to allow these calls to be
monitored as well. The calls have been placed within a
separate set of DLL's to ensure that you can still run the
software on OS/2 Version 2.0 systems.
=============== < ViewPort Considerations > ================
Before you start your application that has been enabled for
ViewPort support, ViewPort MUST be started otherwise
you will receive a message stating that the link between
the Validator DLL and ViewPort was not made.
================ < Compiler Differences > ==================
There are differences in how the various compilers generate
code that calls OS/2 functions. The compilers are
supposed to to place the number of parameters that have been
placed on the stack for the call in the AL register. The
only compilers that appear to be doing this are the IBM
C Set/2 and C Set++ compilers. The Borland compiler does
not do this.
Therefore, you must specify during the installation which
compiler you are using. If you are using the IBM compilers,
you should select the IBM compilers radio button otherwise
select the Borland radio button. This means the feature of
determining if there are too many or few parameters being
passed to the OS/2 API will only occur with the IBM
compilers.
================ < Problem Determination > =================
If a problem occurs within an application utilizing the
Validator or ViewPort that causes a memory protection
violation, a message will be displayed showing the memory
address where the violation occurred. Further information
will be found within the directory where the Validator files
were installed within specific files associated with each
application:
Application Exception File
---------------------------------------------
Application Validatr.XCP
ViewPort ViewPort.XCP
=============================================
When a memory protection violation does occurr, please
post a note within the Developer Connection area of the
OSDF2 Forum on CompuServe with the information produced
in one of the files to allow the support personnel to
help you solve the problem.