Changeset 6553 for trunk/doc/Readme.Odinbug
- Timestamp:
- Aug 16, 2001, 11:34:57 PM (24 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/Readme.Odinbug
r6516 r6553 1 Odin Bug Report Tool Version 0.2.1 1 Odin Bug Report Tool Version 0.3.0 2 ================================== 2 3 3 4 0. DISCLAIMER 4 5 5 OdinBug is free software. It is not guaranteed to fulfill any 6 particular purpose. Use it at your own risk. 6 OdinBug is free, but copyrighted software. It is not guaranteed 7 to fulfill any particular purpose. Use it at your own risk. It may 8 be included with every application that comes with Odin files 7 9 8 10 1. INTRODUCTION … … 25 27 in ReportingBugs.TXT which is part of every Odin build. 26 28 27 Some of the information is gathered from CONFIG.SYS and SYSLEVEL files28 and also from the odin32_?.log files. And some information has to be29 filled in manually (only the minor part).29 Some of the information is gathered from CONFIG.SYS, SYSLEVEL files, 30 the WarpIN database, from ODIN.INI and also from the odin32_?.log files. 31 And some information has to be filled in manually (only the minor part). 30 32 31 33 It also scans the odin_?.log file to find the exception information and … … 38 40 As OdinBug.EXE is written in VX-REXX it needs the VROBJ.DLL runtime. 39 41 40 VROBJ.DLL can be found in the directory x:\IMAGES (x=CD-ROM drive) of your 41 original Warp 4 CD-ROM and have to copy it into d:\OS2\DLL (d=bootdrive), 42 or somewhere else in your LIBPATH. 42 VROBJ.DLL can be found in the directory x:\IMAGES (x=CD-ROM drive) of 43 your original Warp 4 CD-ROM and has to be copied into into d:\OS2\DLL 44 (d=bootdrive), or somewhere else in your LIBPATH. 45 46 There is also a VROBJ.WPI package at the following location: 47 48 http://groups.yahoo.com/group/odinusers/files/vrobj.wpi 49 50 This package can be installed the usual way using WarpIN. 43 51 44 52 Put OdinBug.EXE in a directory in your path. … … 48 56 itself has reasonable default values. 49 57 50 Call it after you experienced a trap in a Win32 program and 51 after youhave created a log file.58 Call it after you experienced a trap in a Win32 program and after you 59 have created a log file. 52 60 53 61 Every field can be changed manually, but using the "Search"-buttons should 54 62 be the preferred method. 55 63 56 When everything is complete press "Create report" button. The program checks57 for empty fields, and if everything is filled out creates a report.64 When everything is complete press "Create report" button. The program 65 checks for empty fields, and if everything is filled out creates a report. 58 66 59 Pressing "EMail report" starts Netscape Messenger (or any other email program; 60 see OdinBug.CFG) with the appropriate email address and copies the newly 61 created report into the clipboard, so it can be pasted into the email. 67 Pressing "EMail report" starts Netscape Messenger (or any other email 68 program; see OdinBug.CFG) with the appropriate email address and copies 69 the newly created report into the clipboard, so it can be pasted into 70 the email. 62 71 63 72 4. BUG REPORTS AND FEATURE REQUEST FOR THIS PROGRAM 64 73 65 Just email me and tell me what you think or what you want! I will try to66 realize it.74 Just email me and tell me what you think or what you want! 75 I will try to realize it. 67 76 68 77 5. AUTHOR: … … 70 79 Herwig Bauernfeind, 10.08.2001 71 80 EMail: herwig.bauernfeind@aon.at 72 73
Note:
See TracChangeset
for help on using the changeset viewer.