How To Enable Legacy Dos Application To Use Hebrew Fonts Under Command Line

When you start legacy application that use dos/command line environment�under Windows XP/2000/2003, the�fonts characters seems
un-comprehendible instead of Hebrew fonts.

Legacy application that use dos/command line environment�with Hebrew fonts may require additional fonts that are
missing from the default installation of Windows XP/2000/2003.�
�
Further information can be obtain from:
�
�
Limitations of Windows 2000 Support for Languages
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q254256
�

There few option to configure Hebrew font support under Windows XP/2000/2003. The actual implementation depend
�
�on the dos application requirements.
�
Warning: Methods A,B,D,E aren't supported by Microsoft and�you may implement them�on your on risk.�
������������� �Also, there is no guaranty that any method will work with every dos application, you can only use it with "trial and error".
�
Method A -�Run Application in Full Screen:
�
�
1.�Obtain "LOADHEB.COM" or "VGA-HEB.EXE" files.
�
2. Create a batch file script in installation directory of the DOS application and add to it the
�����
����� following lines:
�
�
���� "MODE CON LINES=25"
�
���� "LOADHEB (or VGA-HEB)"
�
��� �"The EXE/COM file name that launch the DOS application"
�
�
3. Run the batch file that you created in step 2.
�
�
Method B: Run Application in�"Windows" Screen:
�
�
1. Obtain a copy of "APP862.FON" (You can find it on Hebrew Enabled version of Windows 98/ME).
�
� Note: To use the files above, you will need to obtain Windows 98/ME/2000 Pro/XP license.
�
2. Install "APP862.FON" into the "Fonts" icon�from the Windows "Control Panel".
�
3.��Backup the original "SYSTEM.INI" file of your system.
�
4. Change "woafont=dosapp.FON" line under "SYSTEM.INI" file to "woafont=APP862.FON"
�
5. Reboot the computer.
�
6. Configure the DOS window to use the following font settings:
�
������� "Raster fonts"
�
������� "Size = 10 X 18"
�
7.�Launch the dos application after the reboot.
�
�
Method�C -�Using Microsoft AppLocale Utility:
�
�
Please review Microsoft reference to AppLocale Utility:
�
http://www.microsoft.com/globaldev/tools/apploc.mspx
�
�
Method�D -�Using 3party tools:
�
�
Consider to obtain 3party tool that can add Hebrew support to Windows command prompt.
�
�
Method�E -�Upgrade the DOS application:
�
�
Contact the software manufacture support, and obtain Windows version of the DOS application.

Configurable Language and Cultural Settings
http://www.microsoft.com/globaldev/reference/localetable.mspx
�
The Microsoft AppLocale Utility
http://www.microsoft.com/globaldev/tools/apploc.mspx

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.