Q. Dear Mr. Know-It-All,
I'm a programmer in a mid-size company with offices in several states,
and we have one very large OS/2 application that runs on a lot of desks.
I recently made some modifications to it, and now we get one or two calls a
day that the app has given a SYS3175 or sometimes a complete Trap.
I need some kind of a utility that can be run to capture exactly what's
on the screen when this happens, because the users don't write down the
information even though we keep asking them.
Do you know of such a utility?
A.
You don't need any utility.
The information is stored in a history file named POPUPLOG.OS2.
For Warp 4, the file is in the OS/2 drive's root directory.
For Warp 3, you'll unfortunately need to add SUPPRESSPOPUPS=x to the
CONFIG.SYS file on each machine, where "x" is the drive letter of the
root directory you want POPUPLOG.OS2 to appear in (example:
SUPPRESSPOPUPS=D).
If you've kept a record of everyone who's reported the problem,
contact them and ask them to forward this file to you.
If you have a method for accessing that file from every machine on your
network (some users may be getting the error but not reporting it), check
each machine for these errors.
Mr. Know-It-All lives in Southern California.
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 1998 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG is a trademark of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
