01 Sep 15 09:33, you wrote to me:

 ml>> run "RAMGR /U" to use the user editor and look at the
records to see
 ml>> if they contain proper data... you might want to copy your RA data
 ml>> files to a safe place before using RAMGR or editing any records...

 MA> Yeah, I thought so too. I can not figure out which is the software
 MA> that can be modified.It may be the AMU 3.20?

i don't have any idea... it is possible that it is an external door
rewriting the EXITINFO.BBS file which RA reimports when returning from the
external door... back in the day, i wrote utilities to split the
EXITINFO.BBS file into the old format and the new data in another file...
that allowed old doors to work and update the file which was then merged
back together before returning to RA so that corruption did not happen like
this...

the main things to look for are

  1. what version of RA are you running?
  2. do your external doors and tools specifically recognize that RA version.

if they do not explicitly state that they work with your version of RA,
stop using them, fix the user file errors, and then try them one at the
time to see if the corruption returns... i've dropped most all of my
external tools other than the ones i wrote myself and compiled with the
proper structures for the RA i'm running... especially doors and utils that
update the user record information...

)\/(ark

... Before eating take a little time to thank the food. -Arapaho saying
---