MSGID: 2:221/1.58@fidonet d8c85b1b   
   REPLY: 2:310/31.3@fidonet d8ca157d   
   PID: OpenXP/5.0.38 (Win32)   
   CHRS: ASCII 1   
   Hello Martin!   
      
   ** 26.05.19 - 13:44, Martin Foster wrote to August Abolins:   
      
    MF>I generated a new one with 'crashexport' this morning:   
      
    MF>---------- 8< ----------   
    MF>; Generated by CrashExport 1.0   
    MF>; Sun May 26 09:17:29 2019   
    MF>---------- 8< ----------   
      
    MF>However, by pure chance, I noticed that the file had UNIX line   
    MF>endings. Huh!?   
      
   That should be a big clue.  You have to think "DOS" for this, especially     
   the text files that you can edit manually.   
      
      
    MF>I changed the line endings to DOS, popped the file in my SemPoint   
    MF>directory and configured SemPoint to use the AREAS.BBS file but it   
    MF>GPF'd on me again. I then removed everything from the file apart from   
    MF>the last two lines and this time, SemPoint didn't GPF on me. However,   
    MF>I still don't have an area list but I know something's changed because   
    MF>AREE.CFG is a bit bigger than it was before and the date/time stamps   
    MF>have changed.   
      
   You can also take a look inside and see if the text strings that you     
   expect are there.  There will be a lot of control chars inbetween the pure     
   text, but if you look at the file with WordPad for example, the control     
   chars with be little blocks or spaces that don't interfere with reading     
   the text.   
      
      
    AA>> If you are only needing one area (for test and evaluation purposes), why   
    AA>> not Configure the area manually.   
   -------- [Snip] ---------   
    AA>> Hope this helps.   
      
    MF>Yes it does thanks because I now have an area list containing the one   
    MF>area and I can read the messages.   
      
   Another thing to watch out for when configuring SEM, stick to max 8 chars     
   for directory names and 8.3 max for file names.   SEM predates WinXP a     
   little bit.   
      
   I ran into this problem when I was pointing SEM to my Apoint-created JAM     
   areas directly, not realizing that some of the path/dir names in Apoint     
   were long.   
      
   I now have a JAM base for FIDOTEST that I can read and write to without     
   the system crashing on me.  (Now I just need to add the tosser and binkd     
   to take it to the next level).   
      
      
    AA>> [BTW..  I still haven't received my Fastecho reg key  :(  ]   
    MF>Can't imagine why, perhaps you should give Tobias a gentle nudge?   
      
   I think it still "works" without the key, right?  Meanwhile, I'll see what     
   CrashMail can do.  I've received a lot of encouragement to use CrashMail     
   over FE or FM.   
      
      
     ../|ug   
      
   --- OpenXP 5.0.38   
    * Origin: o,,,,o§ø`ø§o,,,,o§ø`ø§o,,,,o (2:221/1.58)   
   SEEN-BY: 1/123 15/2 154/10 203/0 221/1 6 360 226/17 229/354 426 1014   
   SEEN-BY: 240/5832 249/206 317 400 280/464 5003 292/854 310/31 317/3   
   SEEN-BY: 322/757 342/200 393/68 396/45 423/120 712/848 770/1 2452/250   
   PATH: 221/1 280/464 229/426