OS/2 Shareware BBS: 8 Other/08-Other.zip/problm.zip/README.TXT

Text File | 1996-01-10 | 8KB | 161 lines

README for OS2INFO.EXE
 This package contains three files:
  INSTALL.EXE Installation program
  OS2INFO.EXE OS/2 Problem Report Generator
  README.TXT This file

This release can be used to submit Defect Reports to IBM.  If using
CompuServe mail, OS/2 Base Operating System defect reports should be mailed
to 76711,610.  Extended Services or LAN Server defect reports should be
mailed to 76711,611.  If using the Internet, OS/2 base Operating system
defects need to be sent to [e-mail] and Extended Services
or LAN Server defects to [e-mail].

NOTE:

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

    IF YOU HAVE PROBLEMS WITH THIS (OS2INFO.EXE) APPLICATION, PLEASE
    REPORT THE PROBLEMS IN COMPUSERVE FORUM OS2SUPPORT, SECTION 23,
    ADDRESSED TO 'THE TEAMIBM NETWORK, 72370,250'.  PLEASE DO NOT POST
    THE PROBLEM REPORT FILE GENERATED BY THIS APPLICATION ON THE CIS
    FORUM.

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

Suggestions, comments and problems regarding OS2INFO.EXE are very welcome.
Please post them in section 23 of OS2SUPPO forum on CompuServe.

To install:

Run the INSTALL.EXE program and follow instructions.  You can install
OS2INFO.EXE into its own directory or anywhere else you wish.  The INSTALL
program will create a directory for you if you wish and a desktop object.

To Use:

If you have a desktop object, double click on it or just invoke it from the
command line by typing OS2INFO.  Fill out the 'Personal Information' first.

The Entitlement number in the Personal information panel is the number
given to you when you purchase a support contract from IBM.  If you do not
have such a number, please enter the 16-digit number from the 'Customer
Service and Support' card that came with the product.  Select 'Environment'
for hardware configuration, IBM LAN server/requestor information and IBM
Communications Manager/2 or Database Manager/2.  Click on the SYSLEVEL
button to run SYSLEVEL.EXE.  A file called SYSLEVEL.TXT will be created in
the current directory.  The syslevel information from this file are
automatically imported into the respective fields.  The hardware is
detected automatically.  If any hardware is not detected or is incorrect,
just type it in or correct the information.  At this time the video
information is not detected automatically.  Please select your video card
from the listed 340 types in the Hardware screen-I.  Also select the
resolution.  If the card you are using is not listed, just type it in.  If
connected to a LAN, fill out the 'Network/LAN' section.  If using
Communications Manager/2 or Database Manager/2, fill out the 'IBM CM/DBM'
section.

Return to the Main Menu when done.

If you had entered any Personal Information incorrectly or wish to correct
it, select 'Edit Personal Information' button.  You can view this
README.TXT file if you select the 'README.TXT' radio button and click on
the View file button.  Click on the 'Generate Problem Report' button to
proceed.

In the Problem Screen, select 'Problem Description'.  Give a one-line
description and a complete and detailed description.  This is absolutely
necessary so that the problem can be properly understood and processed.  If
these fields are empty, the 'Generate Problem Report' button will not be
enabled.

Then select 'Specific Problem' Info.  Choose the section or sections that
appear to apply to the suspected defect.  (WIN Apps are Windows
Applications, Comm/Async is Communication problems using a COM port, such
as a modem, etc.) If nothing appears to fit or it is an OS/2 program, OS/2
memory--not DOS window/fullscreen memory--or performance problem, use
OTHER.  Please make at least ONE selection from the list of buttons.  When
a button is selected, the title text on the button changes from Blue to
Green indicating that it has been processed.  If you do not select any of
the buttons here, the 'Generate Problem Report' button will still be
disabled.

If you have 'SUPPRESSPOPUPS=<drive_letter>' in your CONFIG.SYS, the error
messages and traps are written to a file <drive_letter>:\POPUPLOG.OS2.  If
you select 'Hang/Trap' as the Specific Problem info, you can look at all
the errors in the POPUPLOG.OS2 file and attach the one you need to the
Problem report.  To see the latest error, click on the 'Prev' button on the
panel that comes up when you select 'Import from POPUPLOG.OS2' button.

Pressing 'Generate Problem Report' will ask the frequency of the problem
and offer the ability to include the CONFIG.SYS, STARTUP.CMD, and
AUTOEXEC.BAT or any other file.  Click on the Other button and select the
file you wish to attach.  Only include those that have bearing to the
problem.  If you are not sure which to include, include all.

A file called SEND2IBM.TXT will be created containing the information
entered.  A file SEND2IBM.xxx (where xxx is a number from 000 to 999) will
also be created.  The highest numbered SEND2IBM file is a copy of the
current SEND2IBM.TXT file.  This keeps a history of all reported defects.

Using CompuServe mail, send SEND2IBM.TXT to the corresponding IBM OS/2
defect reporting id.  OS/2 Base Operating System defect reports should be
mailed to 76711,610.  Extended Services or LAN Server defect reports should
be mailed to 76711,611.  If you wish to send the file using the Internet,
please send OS/2 base Operating system defects to [e-mail]
and Extended Services or LAN Server defects to [e-mail].

 Changes:

10/23/95

 -- Added a new field in the Customer screen to enter e-mail address.
 -- Added functionality to detect multiple diskette drives.
 -- Added functionality to view SEND2IBM.TXT from the main screen.
 -- Added functionality to report additional information about the serial
    ports.
 -- Fixed problem with the Token ring information being reported incorrectly
    in some cases.
 -- Fixed the problem that some OEM diskette drives are not being
    detected.
 -- Fixed problem with the features being printed incorrectly.
 -- Fixed problem with the pointer version not being reported in some
    cases.
 -- Fixed problem with the drives information becoming garbled when
    more than 10 logical drives exist.

11/30/95

 -- Created a PM based install program.
 -- Added functionality to run SYSLEVEL and input information into various panels
 -- Added functionality to attach any text file to the SEND2IBM.TXT file.
 -- Added functionality to make changes to the generated SEND2IBM.TXT file and save
    the changes.
 -- Fixed problem with the SUPPRESSPOPUPS= statement in the CONFIG.SYS not being
    detected if it was at the end of the file or in lower case.
 -- Fixed the  POPUPLOG.OS2 view so that the last error recorded is
    displayed first instead of the first error.
 -- Under 'Specific problem info -> install -> installation setup', added an other
    check box for third party setup types.
 -- Changed other controls for CUA conformity.
 -- Changed logo screen behaviour to conform to the logo setting in the
    system settings notebook.
 -- Fixed truncation of text when exported from the problem description MLE.
 -- Added Video Card and Video Resolution list boxes to the Hardware screen
 -- The SEND2IBM.TXT will now indicate which version of OS2INFO created the
    file.

01/10/96

 -- Added problem identifier to SEND2IBM.TXT file for customers sending problem
    reports to departments which do not issue problem identifier numbers.
 -- When problem report is generated, a log file called PROBRPT.LOG is generated
    with the name of the problem report file, problem identifier, date, time and
    description of the problem.
 -- Added button to import text files into problem description MLE.
 -- Added button to TCPIP2 panel to go to TCPIP1 panel.
 -- Added confirmation message box when Exit is selected without generating
    problem report.
 -- The version is now 1.00.