Hi! Alexey,

On Sat, 04 Mar 06, you wrote to me:

 PQ>> I just checked an old config file's buffer size and can verify
 PQ>> I've had mine set for 512k for almost exactly the last 6 years - 
 PQ>> it's dated 22/3/2000.
 AF> You can set it to 512, but FE will use maximum of 64k. Check out help
 AF> topic on message buffer size.

I know this.  I'm an optimistic pessimist.  That way I'm not disappointed
when things turn to *shit*, and not overjoyed when things run smoothly. 
=B^)

 AF> === Starting Windows Clipboard === It's  recommended  to  use a 
 AF> buffer as large as possible (DOS: max. 64kB, OS/2: max. 512kB), and 
 AF> only to make it smaller if your computer is short on memory.
 AF> === End of Windows Clipboard ===

You just illustrated my point.  I set it for 512, since the dox say
"My only suggestion is to use a buffer as large as possible, reducing
it only in case you notice that your computer is short on memory." 
So, I did!  And haven't noticed any ill effects since.  :)

 AF> FeSetup program is universal for all versions and doesn't check on
 AF> which OS it is running. That's why you can set 512k for DOS version.

Maybe it doesn't 'check on which OS', but it certainly does report it.

By the way, not all FeSetup.Exe programs are equal.  I know of one
significant difference between v1.45 versus v1.46 setups, in that the 1.46
setup will not accept the "$" (the dollar sign, in case of some
codepage problem in your editor) to indicate DOS environment variable
references for directory "path" settings.  I had to FREQ to a
site in central U.S.A. via modem once to get the old 1.45 setup version, to
fix my 1.46 config's paths at the time.

Cheers,
Paul.

--- Radius 4.010/21.01.2005(Final)