On Tue, 22 Apr 2014, Joe Delahaye wrote to Daryl Stout:

 DS>  I am considering Argus. Marc Lewis came into the system remotely, 
 DS> and noted I may have a CORRUPT EXE with IREX for Windows. You 
 DS> could NEVER get the system to save the entry "accept connects from 
 DS> unlisted systems". While you could do it in the same 
 DS> session...when you exited REXCFGW, and reloaded it, the paramenter 
 DS> was back to "NO".

 JD> Why not simply put in new exe? Pretty sure you can still download
 JD> Rex from various sources, and get an exe that is not corrupt.

or just delete the existing one and pull a new copy out of the original
archive... back in the early 90s, some of us saw problems with trying to
overwrite corrupted executables with a new copy... no clue as to why but
deleting the original and then replacing it with a new copy worked every
time...

it is also possible that the config is corrupted... IIRC, some folks
maintain a backup copy of the config so they can replace it when they have
problems from it becoming corrupted...

if all else fails, one might also use a binary editor on the config and
change the necessary item to the desired value... of course, this will only
work if one knows where the value is in the binary config, knows what the
desired value should be and the system doesn't calculate some sort of
checksum to ensure the config is not altered outside of the config
program...

)\/(ark

One of the great tragedies of life is the murder of a beautiful theory by a
gang of brutal facts. --Benjamin Franklin

--- FMail/Win32 1.60