Win-OS/2 Tricks
Jump to navigation
Jump to search
Win-OS2 or Win-OS/2 is the common name of the Windows 3.1 embedded sessions that OS/2 can run. Here are some tips and tricks about.
Backup Important Configuration Files
There are some files that are important to backup if you are going to tweak your Win-OS/2 sessions. Backup the win.ini, system.ini, config.sys and autoexec.bat files.
Autoexec.bat
It is important to check your Autoexec.bat if you have problems booting the Win-OS/2 sessions. Here is a sample of a default/standard Autoexec.bat that comes in ArcaOS:
@ECHO OFF ECHO. PROMPT $i$p$g REM SET DELDIR=C:\DELETE,512;S:\DELETE,512;T:\DELETE,512;Z:\DELETE,512; SET WIN3DIR=C:\OS2\MDOS\WINOS2 PATH=C:\OS2;C:\OS2\MDOS;C:\;C:\OS2\MDOS\WINOS2;C:\sys\MDOS\BIN;C:\TCPIP\DOS\BIN; LOADHIGH APPEND C:\OS2;C:\OS2\SYSTEM SET TMP=C:\var\temp LOADHIGH C:\sys\MDOS\BIN\2GBFIX.COM >NUL LOADHIGH DOSKEY FINDFILE=DIR /A /S /B $* LOADHIGH MOUSE DOSKEY EDIT=QBASIC/EDITOR $* SET DIRCMD=/A SET TEMP=C:\OS2\MDOS\WINOS2\TEMP SET ETC=C:\TCPIP\DOS\ETC
Boot Log
You can generate a boot log file when you run Win-OS/2 by running:
win /b
It will generate a BOOTLOG.TXT file with some log about the booting process.
For example:
[boot] LoadStart = system.drv LoadSuccess = system.drv LoadStart = keyboard.drv LoadSuccess = keyboard.drv LoadStart = mouse.drv LoadSuccess = mouse.drv LoadStart = ifgdi2vm.drv LoadSuccess = ifgdi2vm.drv LoadStart = SOUND.DRV .....