home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
sniff16.zip
/
READ.ME
Wrap
Text File
|
1993-10-27
|
5KB
|
138 lines
Installing and Using The 16-Bit Sniffer Utility
===================
Evaluation Revision 0.5, September 30, 1993
1) DevCon will install, in your hard drive,
the 16-Bit Sniffer Utility.For simplicity,
assume that you wish to install the 16-Bit
Sniffer Utility in the D:\SNIFF16 directory.
2) The SNIFF16 directory structure will be as follows:
. ─┐ Your current working directory
│ (by example: D:\SNIFF16)
│
├─── BIN Sniff16 executable and message file
│ README file
│
├─── TESTAPP Test application directory
│
│
└─┬─ EPM OS/2 Enhanced Editor binaries
│
├──── DLL OS/2 Enhanced Editor dynamic link libraries
│
│
└──── HELP OS/2 Enhanced Editor help
3) Your OS/2 CONFIG.SYS has to be updated as follows:
a) Set up the OS/2 Enhanced Editor path in the following
format:
> SET EPMPATH=xxxx\EPM
where "xxxx" refers to the base directory you've
selected. For example, if you used the 'D:\SNIFF16'
directory to install the 16-Bit Sniffer Utility as
illustrated, the statement would be:
SET EPMPATH=D:\SNIFF16\EPM
b) Update your PATH statement to indicate that executable
files reside in the BIN and EPM directories. The format
is:
> SET PATH=C:\OS2;C:\OS2\SYSTEM;xxxx\BIN;xxxx\EPM;
where "xxxx" refers to the base installation directory
you've selected. The 'xxxx'\BIN and 'xxxx'\EPM directories
are to be appended to your existing PATH. For example:
SET PATH=C:\OS2;C:\OS2\SYSTEM;D:\SNIFF16\BIN;D:\SNIFF16\EPM;
c) Update your LIBPATH statement to reference the OS/2
Enhanced Editor's DLLs. The following form is used:
> LIBPATH=C:\OS2\DLL;C:\OS2\MDOS;C:\;xxxx\EPM\DLL;
For example:
LIBPATH=C:\OS2\DLL;C:\OS2\MDOS;C:\;D:\SNIFF16\EPM\DLL;
d) Update your DPATH statement to find the SNIFF.MSG
file on you hard disk. DPATH uses the form:
> SET DPATH=C:\OS2;C:\OS2\SYSTEM;xxxx\BIN;
For example:
SET DPATH=C:\OS2;C:\OS2\SYSTEM;D:\SNIFF16\BIN;
e) Update your HELP environment variable in CONFIG.SYS
to reference the OS/2 Enhanced Editor help file.
The HELP variable uses the form:
> SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;xxxx\EPM\HELP;
For example:
SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;D:\SNIFF16\EPM\HELP;
f) You may wish to insert a SNIFF16PATH line in CONFIG.SYS
which points to the path that SNIFF16 will search for
executable files (.exe), dynamic link libraries (.dll),
and source (.c) files. For example:
> SET SNIFF16PATH=D:\DEV\DLL;D:\DEV\CSOURCE;D:\DEV;C:\MYDLLS;
4) Once you've updated your CONFIG.SYS file, reboot OS/2 to
recognize the changes to CONFIG.SYS.
To test the installation of SNIFF16, change to the TESTAPP
directory under the installation directory you've chosen.
For example:
D:
CD \SNIFF16\TESTAPP
Type:
SNIFF16 -e WORMS.EXE
to SNIFF the WORMS application and bring up EPM to
guide you to each 16-bit call that SNIFF16 detected. Use
the ALT-N key to move to the next 16-bit call, ALT-P to
move to the previous 16-bit call, ALT-F1 while on the
line of any 16-bit call to bring up a message box which
may give an explanation of the potential problem, and
ALT-F4 to exit EPM.
Source code has been included for the WORMS application,
which comes from the OS/2 2.1 Toolkit. The Makefile
from the Toolkit has been modified to include symbolic
debug information in the executable, and is included
in the TESTAPP directory. To use SNIFF16's EPM editor
interface, it is necessary to include DEBUG information
in the application executable. You may refer to the
WORMS makefile for the compiler and linker options used
to build the sample application.
Please refer to the READ.ME file that was installed in the
BIN directory (under the 16-Bit Sniffer Utility directory
you've chosen) for additional details and options for the
tool.