OS/2 Professional/OS2PRO194.ISO/os2/info/faq/os2_20/os2help/win002.fax

Text File | 1992-09-17 | 5.8 KB | 117 lines

WINOS2 INSTALLATION AND MIGRATION TROUBLE SHOOTING GUIDE
--------------------------------------------------------

See also:  OS/2 2.0 Online Help

           OS/2 2.0 Manuals - Installation Guide
                              Using the Operating System
                              Migrating to the OS/2 Workplace Shell
                              Adobe Type Manager for WIN-OS2

           OS/2 Readme File  ('README' file in root directory)


Problem: Either Full Screen or Seamless WINOS2 fails to start.  Normally
         a Fatal Error 0x0401 appears very quickly.  Typing WINOS2 from
         a full screen DOS session can verify this problem.

Answer:  This problem is caused by one or more of the drivers,sys or font
         files listed in the Windows SYSTEM.INI or WIN.INI file not loading
         correctly. This could happen if one of these files is not present,
         or if the driver does not fully load when Windows starts up.  To
         correct this problem, the user can try reinstalling WINOS2
         by doing a selective install of OS2.  Another more time
         consuming solution is to copy the SYSTEM.INI file in the WINOS2
         directory to a printer and verify that each of the drivers or
         system files actually exists.

         This error also occurs on systems with XGA or 8514 video boards
         and monitors when trying to use large fonts.  Use small fonts
         instead.  Modify the lines in SYSTEM.INI to:

                    fonts.fon=xgasys.fon
                    fixedfon.fon=xgafix.fon
                    oemfonts.fon=xgaoem.fon


Problem: Microsoft Windows 3.1 and Windows 3.1 Applications do not work.

Answer:  Microsoft Windows 3.1 and any Windows 3.1 applications
         that will only run with Windows Version 3.1, cannot run
         under OS/2 2.0 WINOS2 3.0 compatibility mode.  Windows 3.10
         specific applications do not run either under a
         OS/2 2.0 Dos Session or a OS/2-2.0 VMB(Booted Dos Session).
         Windows Version 3.1 may be available under a future version
         of OS/2-2.0, but the release date of this is unknown at this time.

         If you installed OS/2-2.0 using dual boot, Microsoft Windows 3.1
         will still run under native DOS.

Problem: ATM (Adobe Type Manager) fonts not available using
         Windows Applications.

Answer:  Using a Full Screen WINOS2 session, select the ATM ICON
         in the OS2/Main Folder of the Program Manager and install ATM
         fonts.  The 17 standard ATM fonts are on Printer Driver Disk #5.

Problem: Windows applications cannot be run seamlessly from the desktop.

Answer:  Migrate Windows applications using the Migrate Utility in the
         System Set-up Folder. From the OS/2 desktop select the OS/2-2.0
         System Icon, System Set-up folder, then Migrate Applications.

Problem: Windows applications started from user-created OS2 2.0 program
         objects do not have the correct DOS Settings.

Answer:  If you migrated your Windows applications, DOS Settings are
         automatically set for you using the list of applications in
         the \OS2\INSTALL\DATABASE.TXT file.  If you created your own
         program object for a Windows or DOS application, your DOS
         Settings may be incorrect.  Look through the DATABASE text
         file for your application and required DOS Settings.  If your
         DOS Settings for the application are correct, see the next item.

Problem: Windows applications not starting or running correctly.

Answer:  Many Windows applications require private application INI files
         or specific WIN.INI setting to run.  The least complicated way
         to have INI files set up correctly is to reinstall your Windows
         application over the old installation using a Full Screen WINOS2
         session.  This will correctly update WIN.INI and any appliction
         INI file correctly.

         A quicker but more complex and dangerous way, that may work with
         some, but not all Windows applications experiencing problems, is
         to copy the old application INI file from the old directory to
         the new \OS2\MDOS\WINOS2 directory.  Type DIR *.INI in your old
         Windows directory to see files names that should be copied to
         \OS2\MDOS\WINOS2.  Do not copy WIN.INI or SYSTEM.INI, you will
         prevent WINOS2 Windows from working and lose other WINOS2
         functionality.  Any application that does not work at this
         point should be reinstalled.

         Additionally, for information purposes. If OS/2-2.0 was installed
         on top of DOS/WINDOWS 3.0, the WIN.INI in the \OS2\MDOS\WINOS2
         directory will reflect the older WIN.INI file if the user
         selected to migrate his Windows 3.0 settings to WINOS2.
         If OS/2-2.0 was installed on top of a DOS/WINDOWS 3.1, the
         WINOS2 WIN.INI file will be a base WIN.INI file without any
         of the settings in the older Windows 3.1 WIN.INI file.

Problem: Windows application gives "Cannot Load File" error message.

Answer:  Some applications use DLLs (Dynamic Link Libraries) that are
         shipped with the application.  If the DLLs are in a directory
         other than the Windows directory, make sure that the DLL is in
         the path statement that is in the AUTOEXEC.BAT file.



-------------------------------------------------------------------------------
Thank you for calling the OS/2 2.0 Support Line.  Regarding the problem
reported to the Support Line, we feel that this information may assist
you in resoloving your problem.  If you still require assistance, please
call 1-800-237-5511, and reference your customer number and problem (PMR)
number.  Your Problem Record Number (PMR) should appear on the cover
page of this faxed document.