OSWAWN95 - WINDOWS 95 COEXISTING WITH OS/2 WARP 11/14/96 ======================================================================= Windows 95 Coexisting with OS/2 Warp ======================================================================= Please Read Entire Document for Full Explanation of Procedures -------------------------------------------------------------- DESCRIPTION This document describes things you should do (or NOT do) when installing Windows 95 to make the coexistence of Windows 95 and OS/2 Warp smooth. RESOLUTION It's best not to install Windows 95 over Windows 3.1. ---------------------------------------------------- During the Windows 95 installation, select a directory other than the Windows 3.1 directory if you want WIN-OS/2 support in the OS/2 Warp for Windows version. The OS/2 Warp Fullpack versions of WIN-OS/2 support are not affected by the Windows 95 installation. Windows 95 will copy over Windows 3.1 files, and they are not recoverable unless you have diskettes or make an archive during the installation. If you installed Windows 95 over Windows 3.1... ----------------------------------------------- There is a simple solution if you have the OS/2 Warp for Windows versions. If you have Windows 3.1 diskettes, you can install Windows 3.1 in a separate subdirectory. Then use Dual Boot or Boot Manager to start OS/2 and run Selective Install. Choose to reinstall the WIN-OS/2 support and point to the new Windows 3.1 subdirectory. What happens when I start WIN-OS/2 after installing Windows 95 over Windows 3.1? -------------------------------------------------------------------- When you try to start any WIN-OS/2 session that points to Windows 95 code, you will receive a SYS3175 error. What happens if I try to start a Windows 95 32-bit application from WIN-OS/2? ------------------------------------------------------------------- If you migrate any Windows 95 mini-applications or other applications to your WIN-OS/2 environment, you get an Unexpected DOS Error: 23. Click on OK to bypass the information message. You cannot run 32-bit Windows 95 applications under OS/2 Warp or Windows 3.1. How do I migrate 16-bit Windows applications that have been installed from Windows 95? --------------------------------------------------------------------- To ensure a stable application environment, Windows applications should be reinstalled under OS/2 Warp in the same directory they were installed in under Windows 95 (to save space). The Windows 95 installation says Boot Manager will no longer be usable. Is that true? ----------------------------------------------------------------------- During the Windows 95 installation, some "information messages" appear if Dual Boot or Boot Manager is present on the system. Always press Continue to bypass these errors. There are no bad effects from having OS/2 in the same partition as Windows 95. Boot Manager is no longer the ACTIVE partition, but can be made active by doing the following: 1. Start FDISK from any prompt. 2. Change the 1 MB non-DOS partition (Boot Manager) to active. 3. Save the settings. 4. Shut down and restart the system. You should now get the Boot Manager menu. How does Dual Boot work with Windows 95? ------------------------------------------- If you start the Windows 95 installation from DOS on a Dual Boot system, you should not have any problems with Dual Boot between Windows 95 and OS/2. To start OS/2 do the following: 1. Exit to a DOS prompt from Windows 95. 2. Type C:\OS2\BOOT /OS2 and press Enter. 3. Answer Y to continue. How do I get back to my original DOS setup once I've installed Windows 95? -------------------------------------------------------------- To get back to the DOS CONFIG.SYS system files that you started with before the Windows 95 installation, do the following: 1. Shut down Windows 95 and restart it. 2. During startup, as soon as you see "Starting Windows 95...," press F8 to get the Windows 95 recovery screen. 3. Select the last option on the list, Previous Version of MS-DOS. 4. You are now using the same DOS CONFIG.SYS that you started with. ______________________________________________________________________ IBM disclaims all warranties, whether express or implied, including without limitation, warranties of fitness and merchantability with respect to the information in this document. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright (c) 1994, 1995 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.