Thanks for the heads-up on the "6.2" vs. "6.3". I believe that is now fixed in the latest build, available directly from
ate-6.3.1544.7-web.exe , or via the Help > Check For Updates. (This update also contains the latest ASHNET2.DLL 2.3.208 which addresses the SSH/All-Users conflicts you posted previously.)
I'm not so sure about the default colors though. Those are stored in the default.ash file, which you can see in Notepad. The line of interest is:
which means that the default fcolor is #2, the bcolor is #0. The last -0 relates to the reduced intensity background color but probably isn't relevant here.
The installer contains two copies of this file, one called default.ash, and one called default.new. The default.ash file is only installed if it doesn't already exist, so we don't overwrite your existing one when updating.
Things get a bit more complicated from here, because when you use the File > Save menu to save updated settings, there is a hierarchy of possible saved locations, with the default one being relevant only to the Current User and the current profile (%APPDATA%\ATE\configname.ash).
Once you save updated settings in one of the location farther up (or down, depending on your perspective) in the hierarchy, that file will be used in instead of the %MIAME%\default.ash.
My guess is that when fooling around with the all-users vs current-user issue, you inadvertently switched to a saved copy of your settings. (The File > Save dialog also shows where the current settings were loaded from.)
The other thing to note is that the "normal" case is for the application startup to set the foreground and background palette indices, using TAB(-2,x) and TAB(-3,x), or
.XY -2 x and
.XY -3 x and that will override whatever default was initially set. (The theory here is that the application should control which palette indices are being used, but each user could theoretically override the meaning/color of each palette index.) So if it is important to use that the color scheme be set to FG 6, BG 0, then it would probably be a good idea to establish that in the startup command, rather than have to worry about all the possible ways that users can mess with it on the client side.
That said, it isn't our intent that 6.3 changes anything in this area, so if you can point to where the 6.3 installer is somehow changing your existing color scheme, I'd like to fix it.