BG>> I have been using 1.45 for so long that I wonder if it's worth
 BG>> moving to 1.46.

 PQ> The only true bug I've seen with 1.46 is in using its
 PQ> FeSetup.Exe; I found that it just would not accept the "[" &
 PQ> "]" chars when describing directory paths which can be
 PQ> extracted from DOS environment variables.  Keep your
 PQ> FeSetup.Exe from the 1.45 release, at least.  I use DOS envars
 PQ> extensively and had to FREQ a 1.45 archive from a feller in
 PQ> Canada (I think) via the POTS to fix my config at some
 PQ> particular time.

oh yes! there is/was that bug... i resorted to hexediting the config file
IIRC when i was using/testing those... i had forgotten all about that
one... in my case, i did what i found obvious... i put !'s for the [ and ]
and since it was only a couple of paths that i was doing this on, i only
had one or two places to hexedit...

i guess it should be mentioned that one should be careful when using an
older FESETUP due to new capabilities/settings that may get
overwritten/lost with new config files...

)\/(ark