home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
os2pdp.zip
/
README
< prev
next >
Wrap
Text File
|
1994-04-18
|
10KB
|
294 lines
15 April 1994
Problem Determination Package for OS/2* 2.1 (V 0.2)
THIS PACKAGE IS DESIGNED TO BE USED WITH THE OS/2 2.1 PRODUCT. YOU MUST
BE A CURRENT LICENSEE OF OS/2 2.1 IN ORDER TO USE THIS PACKAGE. THIS
CODE IS GOVERNED BY THE TERMS AND CONDITIONS OF THE OS/2 PROGRAM LICENSE
AGREEMENT.
This package contains a set of OS/2 2.1 programs and APIs that are
useful for problem determination; both for program development and for
defect resolution.
SUPPORTED FEATURES
------------------
For Traps/Hangs
---------------
o System Dump to Diskette
o System Dump to Hard File
o Process Dump
o Trap Dump
For Debugging
-------------
o System Trace (TRACE)
o Error Logging
For Analysis
------------
o Trace Formatter (TRACEFMT)
o Dump Formatter (PMDF)
o Error Log Formatter (SYSLOG)
INSTALLATION INSTRUCTIONS
-------------------------
Note: you should first "de-install" any previous versions that you
may have installed.
1. Open the object that contains the OS2PDP installation code. For
example, open the object labeled "Drive A".
2. Open the object labeled "PDPInst.Cmd".
A folder called Problem Determination will be created on the
desktop.
3. If you have OS/2 2.1 GA or S3, you may experience a flashing effect
on your PMDF output screen which causes performance degradation.
This effect is corrected on the latest release of OS/2 2.1 MR1/SP.
If you don't have the OS/2 MR1/SP release, then you may wish to use
the version of PMMLE.DLL included in this package (located in the
PMDF directory). To install this new DLL: 1) boot with the OS/2
installation diskettes and copy the new PMMLE.DLL to the \OS2\DLL
directory, or, 2) copy the new PMMLE.DLL to the root of your boot
drive (e.g. c:\).
4. A new version of the CONFIG.SYS file is created under the file name
CONFIG.PDP. It contains your original CONFIG.SYS statements plus
these additional statements, providing that they were not already
in the file:
TraceBuf=63
Trace=ON
TrapDump=OFF,A:
DumpProcess=c: (where c: is your boot drive)
SuppressPopUps=c: (where c: is your boot drive)
Device=ipath\DDINFO.SYS (where ipath is the installation path)
Please replace the existing CONFIG.SYS file or add similar statements
statements prior to re-booting your system.
For Your Information
--------------------
a. The install program creates a new version of the following
files, but first saves the originals in *.PDP:
\OS2DUMP
\OS2\SYSLOG.EXE
\OS2\SYSLOGPM.EXE
\OS2\DLL\SYSLOG.DLL
\OS2\HELP\SYSLOGH.HLP
\OS2\TRACE.EXE
\OS2\TRACEFMT.EXE
\OS2\DLL\TRACEFMT.DLL
\OS2\HELP\TRACEFMT.HLP
b. If you are running OS/2 S3 video, have applied the service
pack (2.1) or have applied the manufacturing refresh (2.11),
the install program creates a new version of the following
files, but first saves the originals in *.PDP:
\OS2\SYSTEM\TRACE\SYSTEM.TDF
\OS2\SYSTEM\TRACE\SYSTEM.TFF
\OS2\SYSTEM\TRACE\SYSTEMD.TDF
\OS2\SYSTEM\TRACE\SYSTEMD.TFF
DE-INSTALLATION INSTRUCTIONS
----------------------------
1. Execute the "De-install" object in the "Problem Determination"
folder.
Note: the folder itself will not de-install if you have added
files to any of the paths within the PDP installation path or
if you have the path open in a window.
Note: the program does not touch the \OS2\DLL\PMMLE.DLL file,
the \CONFIG.SYS file, or the \PDPRun.Log.
2. If you choose to delete the Problem Determination package manually:
a. Copy the following hidden files on your boot drive then erase
the *.PDP files:
Copy \OS2DUMP.PDP to \OS2DUMP (hidden)
Copy \OS2\SYSLOG.PDP to \OS2\SYSLOG.EXE
Copy \OS2\SYSLOGPM.PDP to \OS2\SYSLOGPM.EXE
Copy \OS2\DLL\SYSLOG.PDP to \OS2\DLL\SYSLOG.EXE
Copy \OS2\HELP\SYSLOGH.PDP to \OS2\HELP\SYSLOGH.HLP
Copy \OS2\TRACE.PDP to \OS2\TRACE.EXE
Copy \OS2\TRACEFMT.PDP to \OS2\TRACEFMT.EXE
Copy \OS2\DLL\TRACEFMT.PDP to \OS2\DLL\TRACEFMT.DLL
Copy \OS2\HELP\TRACEFMT.PDP to \OS2\HELP\TRACEFMT.HLP
b. Erase the following files on your boot drive:
\OS2\SYSTEM\TRACE\TRC000A.TFF
\PDPKill.CMD
\PDPRun.Log
COMPATIBILITY
-------------
o 2.1 GA (debug, retail, HSTRICT)
o 2.1 S3 Video (debug, retail, HSTRICT)
o 2.1 Service Pack (debug, retail, HSTRICT)
2.11 Manufacturing Refresh (debug, retail, HSTRICT)
o 2.1 for Windows (debug, retail, HSTRICT)
FUNCTIONAL RESTRICTIONS
-----------------------
1. If you install a new version of OS/2, you must re-install OS2PDP.
2. Trace on/off icons in the Trace Options folder turn on/off all
trace points. Execute Trace from the command line to set
specific trace points.
3. Popup suppression and PDUMP fail for S3 video if you send the dump
to a HPFS partition.
4. This package does not support the 2.0 dump formatters for GA,
Preload, Preload Backup, Service Pack, or Service Pack 2.
5. Stand-Alone Dump Restrictions:
Prompts and Messages
--------------------
a. Certain Video adapters do not switch properly into text mode from
Super VGA or XGA mode. Thus if a dump is initiated when in
graphics mode, no prompts will display.
Video adapters with problem: Diamond Viper VLB
8514 on a PS/2 Model 80
XGA2 on a PS/2 Model 56/57
NOTE: The dump is taking place. On dump to diskette, the beeps
will indicate when it is time to insert a diskette. When the
system beeps 3 times, please insert diskette #1 to update
the dump statistics.
NOTE: To ensure that you know how to take a dump, initiate a trial
dump while in OS/2 full screen. The video adapter is already
in text mode and will display all prompts.
OEM Systems
-----------
a. On many OEM systems such as Ambra, Value Point, and NCR, the dump
will begin to beep when accessing memory above 16 meg. The
beeping has no effect on the dump itself, which completes
successfully.
Systems with SCSI adapters
--------------------------
a. On OEM systems with SCSI adapters such as Future Domain, the dump
to hardfile may fail due to a problem with the SCSI adapter.
Depending on the circumstances that have required a memory dump,
if the SCSI adapter was very active at the time of the failure, it
may not have been allowed to complete its processing. The dump is
unable to access the hardfile in this situation.
Miscellaneous
-------------
a. If there is a BAD sector on the disk, the dump to hardfile will
fail.
b. The dump to hardfile has no error recovery.
c. Dumping on 295 (two processors) is not supported.
HOW TO REPORT PROBLEMS
----------------------
The package will be periodically refreshed. If the package you
are using is not the latest level, try to run on the latest package and
see whether the problem is still there. To report a problem use the
following form as a template, filling in whatever is applicable, and
return the completed form to Barry Bryan at address:
* E-MAIL USIB1L8T at IBMMAIL
* CompuServe** barryb@vnet.ibm.com
* IBM Internal Users BRYAN at BCRVM1
* PRODIGY** barryb@vnet.ibm.com
* Fax (407)443-7785
* U.S. Mail IBM Corporation, 1430
1000 NW 51st Street
Boca Raton, FL 33431
-------------------OS2PDP Problem Report (OS2PDP-0.2)-------------------
OS/2 Version____________________________________________________________
System Brand and Model__________________________________________________
Processor and Speed_____________________________________________________
System Memory Size______________________________________________________
Bus Type________________________________________________________________
Hard Disk Size and Type_________________________________________________
Video Adapter Brand, Model, and Chip Set________________________________
________________________________________________________________________
Problem Description_____________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
-----------------End OS2PDP Problem Report (OS2PDP-0.2)-----------------
TRADEMARKS
----------
The following terms, denoted by an asterisk (*) in this file, are
trademarks or registered trademarks of IBM Corporation in the United
States and/or other countries:
IBM
OS/2
The following terms, denoted by an asterisk (**) in this file, are
trademarks or registered trademarks of other companies as follows:
Trademark Owner
------------------- ----------------------------------------------------
CompuServe CompuServe
PRODIGY Prodigy Services Co.
IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING
WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH
RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS
DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS.
THIS PACKAGE IS COPYRIGHTED BY INTERNATIONAL BUSINESS MACHINES
CORPORATION. ALL APPROPRIATE RESTRICTIONS APPLY.
(End of Document)