me32.ini - Where does it go, how do I know it's being processed ??
Question posed as:-
> 1) Am I right in assuming that for NT the file me32.ini goes > into %windir%, i.e. into c:
Yes, this is where the other .ini files are.
> 2) How do I know me32.ini is being processed? Creating one, > as described in the readme.txt file doesn't seem to have > any visible effect.
From within the editor, if you show the variable $MEPATH(5), then it should echo the paths that you have defined in the me32.ini file.
esc-x describe-variable $MEPATH
See: me32.ini(8), Installation Information, Setting Up A User Profile.
> 3) What does the "fontfile" statement do ?
For releases after May 1999 then the fontfile statement may be omitted as typically Lucida Console or Courier New is used. If you want to use the fixed OEM fonts then fontfile should be defined as app860.fon (or local language equivalent), this forces the font to be loaded as a resource, prior to use.
Copyright (c) 1998-2006 JASSPA
Last Modified: 2006/08/24
Generated On: 2006/10/07