Filter
Top Products
86
Note:
The contents of the latest version of E: WINDOWS LOCAL may be released as SDK. If this is
the case, use the files in SDK instead of those stored in E: WINDOWS LOCAL.
5.2.2 Application Installation
For this terminal it is recommended to initiate the application program at the same time
MS-Windows is started. This can be achieved by modifying the shell line included in the “boot”
section of system.ini. The default setup script of this shell line is "shell=progman.exe", which is for
initiating the program manager. If "progman.exe" is replaced by the application program name to be
initiated at boot up, the application program, rather than "progman.exe", will be initiated at the same
time MS-Windows is started.
Create the D: WINDOWS directory.
Copy the entire contents of E: WINDOWS LOCAL onto the created directory.
To edit “system.ini” on a personal computer copy D: WINDOWS SYSTEM.INI onto the
ATA or SRAM card.
Open “system.ini” with the editor and insert the application program name to be initiated in the
shell line of the “boot” section.
Create the CONFIG.SYS and AUTOEXEC.BAT files. Remember to add "D: WINDOWS;
E: WINDOWS" to the existing path. Then specify “win.com” to boot MS-Windows at the end
of the AUTOEXEC.BAT file.
Copy the created CONFIG.SYS and AUTOEXEC.BAT files onto D: , and copy the edited
“system.ini” and application program onto D: WINDOWS.
The above procedures complete application installation of MS-Windows. The application program
will be automatically initiated if the terminal is re-started by pressing the RESET switch.
Note:
The contents of the latest version of E: WINDOWS LOCAL may be released as SDK. If this is
the case, use the files in SDK instead of those stored in E: WINDOWS LOCAL.