Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    POINTS    |    Point usage discussion and systems suppo    |    3,070 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 1,037 of 3,070    |
|    Martin Foster to August Abolins    |
|    oxp: locks up    |
|    12 May 19 11:48:39    |
      MSGID: 2:250/1.1 71af528f       CHRS: IBMPC 2       TZUTC: 0100       REPLY: 2:221/1.58@fidonet d8504fd8       Hello August!              ## 11.05.19 at 18:08:00, August Abolins wrote to Martin Foster:              [snip]        AA>>> Any experience in this matter, and how to fix?               MF>> Have a look in "DEBUGLOG.TXT" and see if there's anything in there which        MF>> might give a clue. Also, see if there's an "errors.txt" file and if so,        MF>> that may give a clue.               AA> I'll repost what I shared with you in netmail for the benefit of any        AA> prospective users:               AA> "Apparently DEBUGLOG.txt gets overwritten each time OXP starts. So, the        AA> contents of the old file (which may have been useful), was gone when I        AA> killed the OXP process and relaunched the program.              Yes, it does get overwritten.               AA> It might be better to launch OXP from a batch file and saving the        AA> DEBUGLOG.TXT from the last session to DEBUGLOG.001 etc.. and maybe even        AA> keep copies for 10 sessions or so, before starting the program."              Hey, that's a good idea but please be aware that it can get *very* big, is       full of techno-babble and a lot of the content is in German.               AA> Anyway.. I am back in business with OXP after taking care of what I        AA> "think" was the problem. |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca