home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 2 BBS
/
02-BBS.zip
/
geo250.zip
/
REPORT.BUG
< prev
next >
Wrap
Text File
|
1995-10-08
|
5KB
|
119 lines
______________________________________________________________________
HOW TO REPORT BUGS OR PROBLEMS WITH GOLDED
______________________________________________________________________
┌─────────────────────────────────────────────────────────────────┐
│ PLEASE READ THIS DOCUMENT UNTIL YOU GET ALL THE WAY TO THE END! │
└─────────────────────────────────────────────────────────────────┘
In order to maximize my time to handle as many bugs and feature
additions as possible, it is very important that these instructions
are followed. I can NOT afford to take the time to go hunting for lose
files that people send, or chasing people who do not give me a
complete archive as per this document - if you can't send me what I
need, a lot of effort, yours and mine, may be wasted without results.
When sending me bug reports, I will need the following data from you:
* A README.1ST file describing the problem in as much detail as you
can give. Preferrably including a step-by-step description of how
to reproduce the problem on your setup.
* The version of GoldED that you are using, including main version
(X.YY), Alpha/Beta/Gamma number (Ammdd, BetaN, etc) and platform
(DOS, 386 or OS/2). Whether or not you have applied any patches to
the EXE file(s).
* Complete copies of your GOLDED.CFG, GOLDAREA.CFG, GOLDRAND.CFG and
all files included from these. If the problem is related to
keyboard, language or help system, also the GOLDKEYS.CFG,
GOLDLANG.CFG or GOLDHELP.CFG files. If the problem is related to
character translation, I need copies of the relevant .CHS or .ESC
files.
* The GOLDAREA.INC file and a file with the redirected screen output
of GoldED when you run it with the parameters -FF -VV -W. The -W
parameter tells GoldED to make the GOLDAREA.INC file, which dumps
the complete area configuration known by GoldED.
* A copy of the batch or cmd file (if any) you use to run GoldED.
* Your setting of the GOLDED and GEDCMD environment variables.
* If there are problems with GoldNODE, I need a screen dump of the
output when GoldNODE stops. Your setting of the GOLDNODE
environment variable. If GoldNODE reads a different configuration
file than GOLDED.CFG, I need a copy of the different configuration
file.
* If there are problems with nodelists and/or nodelist indexes, I
need to known the program name and version of the nodelist
compiler you used. Try other nodelist compilers and tell me what,
if any, difference it made. For problems with "othernet"
nodelists, I may need copies of the nodelists.
* If there are problems with another programs configuration (using
the AREAFILE keyword), I need the relevant configuration files
from the other program, and the name and version number of it.
* If there are problems with a particular message or a set of
messagebase files, I need a copy of the message or messagebase
files.
* If there are problems with QWK or SOUP packets, I need copies of
the packets.
* A description of your hardware, installed and available memory,
operating environment (DOS, OS/2), any memory managers, special
TSR's etc.
* A copy of your GoldED logfile, or relevant cuts from it.
* If GoldED (2.50.A0715 or later) locks up, try running with the
debug parameter -X. This enables function tracking in the
statusline and may tell me approximately where in the program the
lockup occurred. Let me know what the statusline says in this
situation.
I can not stress enough the need for this archive to be complete, nor
can I stress enough the need for INPUT files to work with. Output
files does not me much good, since they do not let me trace GoldED in
operation while running your configs and your input files.
Double check: Do you have all of the above files ready to go?
Good. Place them into an archive, named uniquely for you. Do NOT call
it "bugs.zip" or some such, as I can not identify it that way. Do NOT
send your files "loose" (ie, not in a package), as OTHER PEOPLE may be
doing it too, and I don't want to waste time sorting through my
inbound.
If sending via email or file attach, I can handle most major archive
formats.
You may now send your archive to me a variety of different ways:
File attach to 2:236/77 (MODEM) or 2:236/1077 (ISDN).
Email uuencoded to odinn@ibm.net or odinn@winboss.dk.
Upload on my BBS in the GoldED file area.
Sorry, I have no FTP site for this purpose.
You can also send the data on a diskette, but please don't.
Please don't send the archive to any reg.site unless they say that
they are ready to accept them. The reg.sites are not geared to, or can
afford to, forward the archives to me.
Thank you for reading this far. With your help, we will all appreciate
the increased productivity, which will translate to sooner bug fixes
and enhancements.
Odinn Sorensen, 24. september 1995.
PS: Thanks to Jason Fesler, author of GIGO, for inspiration for this
document.
______________________________________________________________________