ID:W3 Windows 3.0 with DESQview and QEMM-386 Quarterdeck Technical Note by Stan Young WINDOWS 3.0 If you are planning to run Windows 3.0 with our DESQview, DESQview 386 and/or QEMM-386 products, Quarterdeck recommends that you upgrade to the versions of these products which specifically support Windows 3.0. These versions are: DESQview 2.3 (or above) DESQview 386 2.3 (or above) QEMM-386 5.1 (or above) Upgrade notices will be going out to registered users of Quarterdeck products starting 8/28/90. RUNNING WINDOWS 3.0 WITH EARLIER VERSIONS It is possible to run Windows 3.0 with earlier version of Quarterdeck products only in Real mode, not in Standard or Enhanced modes. If you are running with a version of QEMM-386 prior to 5.1, you must be sure to use the RAM parameter and also make the following additions to the Windows SYSTEM.INI file, after the line which reads "[386Enh]": [386Enh] DualDisplay=True EMMExclude=E000-EFFF These changes to the SYSTEM.INI file prevent Windows 3.0 from disrupting the high memory management of QEMM-386. These changes can be retained when you upgrade to QEMM-386 v5.1, but they are not required with the upgrade. If you are running Windows 3.0 in DESQview 386 versions prior to 2.3, it must run full-screen and not virtualized, due to mouse and video problems. Even if you are planning to run Window 3.0 ONLY in Real mode, an upgrade to the current versions of DESQview and QEMM-386 is recommended. DESQview v2.3 AND ABOVE WITH WINDOWS 3.0 ON A 286 On 80286 machines, Windows 3.0 requires a special loader program to operate in Standard mode inside DESQview 2.3 and above. The loader (W3-LOAD.COM) is provided on the DESQview disk and is invoked when you run Windows 3.0 from the "MS Windows 3 Std." selection which is added to your Open Window menu by Add a Program. The loader is not required when running in DESQview 386. It is included only for consistency with what is shipped in the standard DESQview package. To run Windows 3.0 in Standard mode on a 286, you must have a minimum of 1MB of real extended memory. If all of your memory currently is configured as expanded, you may have to reconfigure some as extended. Most Windows applications, even those which specifically support Windows 3.0 can run in Real mode, so unless you have applications which require Standard mode, you may wish to leave your memory configured as expanded memory. DESQview 386 v2.3 AND ABOVE WITH WINDOWS 3.0 DESQview 386 2.3 and above support Windows 3.0, both in Real mode and Standard mode. This support is completely automatic, requiring no special loaders or parameters as long as QEMM-386 v5.10 or above is used as the memory manager. Real Mode Support: Install the "MS Windows 3 Real" selection from Add a Program. Running in Real mode, Windows 3.0 runs like any other large graphics program. Windows in this mode can be run in a small window and in the background. Standard Mode Support: Install the "MS Windows 3 Std." selection from Add a Program. Running in Standard mode, Windows 3.0 will run in the foreground. However, since it writes directly to the screen in protected mode, the screen cannot be virtualized. Therefore, the "MS Windows 3 Std." installation defaults to run full-screen only and only in foreground. 386 Enhanced Mode: Windows 3.0 386 Enhanced mode is not supported inside DESQview 386. This should not be a major restriction, since currently anticipated Windows 3.0 applications are expected to support either Real or Standard mode. One of the primary features of 386 Enhanced mode is multitasking support for standard DOS applications. This can be obtained by running your DOS applications in their own DESQview windows. 386 Enhanced mode is supported by QEMM-386 when running outside of DESQview 386. USING QEMM-386 VERSION 5.1 QEMM-386 v5.1 can support Windows 3.0 in all of its possible modes of operation: Real, Standard and 386 Enhanced. Giving Windows 3.0 the "type" of memory it needs: To give Windows 3.0 the kind of memory it needs for ANY mode of operation, simply install QEMM-386 using the defaults. No special parameters to QEMM-386 are needed for this support and there is no need to use Microsoft's HIRAM.SYS driver or reserve any extended memory for the use of Windows 3.0. QEMM concurrently supports both the EMS standard (the one Windows uses in Real mode) and the XMS standard (the one Windows uses in Standard and Enhanced modes). QEMM-386 automatically detects the type of memory being requested and provides it. Installation Note: If you will be running Windows 3.0, be sure to use the QEMM-386 "RAM" parameter. This parameter will automatically be installed when you run the OPTIMIZE program, or if you answer "Yes" to the question "Fill All High Memory with RAM?" during the QEMM-386 Install procedure. QEMM-386 by default provides memory management in the monochrome video area (B000-B7FF), when it is not in use by a video adapter. If you use the RAM parameter, QEMM-386 fills these addresses with RAM so that resident programs, drivers and some of DOS overhead can be loaded into high memory. However, if you don't use the RAM parameter, Windows 3.0 seems to become confused by QEMM-386's memory management in this area and may refuse to start up in 386 Enhanced mode. If you will be running Windows 3.0 and for some reason don't want to use the RAM parameter, you should exclude QEMM-386's use of this area by using, X=B000-B7FF as a parameter to the QEMM386.SYS driver. Fine-Tuning: Users who want to make the most efficient use of their memory may want to consider making some changes from the defaults. The procedure for making these modifications varies slightly, depending on whether you have installed QEMM-386 first, or Windows 3.0 first. When QEMM-386 is installed before Windows 3.0: If you install Windows 3.0 after installing QEMM-386, the Windows Setup program's default, makes two changes to your CONFIG.SYS file which you may wish to modify. Windows Setup inserts the driver HIMEM.SYS before the QEMM386.SYS driver. When QEMM-386 loads, it can allocate all of the memory that is controlled by the HIMEM.SYS driver, so the presence of HIMEM.SYS is not a big problem. However HIMEM.SYS takes 2.8K of conventional memory which QEMM-386 cannot reclaim. Since QEMM-386 provides all the features of HIMEM.SYS, you may want to avoid loading HIMEM.SYS altogether. You can do this by selecting "Let you review & edit changes before modifications are made" from Windows Setup when you get to the menu which offers this option. Just edit out the line which contains the HIMEM.SYS driver from the "Proposed CONFIG.SYS file." Or, you can remove the line from your CONFIG.SYS file at a later time using a text editor. Windows Setup inserts the driver SMARTDRV.SYS after QEMM386.SYS. This is Microsoft's disk caching software. It will operate correctly as loaded, however its default size tends to be rather large. If you are running programs which use expanded memory, outside of Windows, you may want to remove the driver or modify its size. (See "SMARTDRV.TEC", our technical note on SMARTDrive) When Windows 3.0 is installed before QEMM-386: If Windows 3.0 is already installed when you install QEMM-386, the Windows Setup program may have made some changes to your CONFIG.SYS file which you may want to modify. Windows Setup installs a driver called HIMEM.SYS. The QEMM-386 installation procedure puts the QEMM386.SYS driver before the HIMEM.SYS driver. When the system boots, the HIMEM.SYS driver sees that an extended memory manager (QEMM-386) is already installed and does not load itself. This is fine since the QEMM386.SYS driver provides all the features of HIMEM.SYS. Also, since HIMEM.SYS fails to load, it will not be taking any memory. However, it will beep and produce a message, saying "Error: An Extended Memory Manager is already installed." To get rid of this error message, remove the line which loads the HIMEM.SYS driver from your CONFIG.SYS file using a text editor. Windows Setup inserts the driver SMARTDRV.SYS after QEMM386.SYS. This is Microsoft's disk caching software. It operates correctly as loaded, however its default size tends to be rather large. If you are running programs which use expanded memory, outside of Windows, you may want to remove the driver or modify its size. (See "SMARTDRV.TEC", our technical note on SMARTDrive) RUNNING MANIFEST IN WINDOWS 3.0 Quarterdeck Manifest can be run within Windows 3.0 as you would any standard DOS application. You can use the default Windows PIF with the following changes: Change "Memory Requirements: KB Required" to 200. Select COM1 and COM2, so that the communications ports can be seen. When running Manifest in Windows 3.0 in 386 Enhanced mode, the "QEMM 386" entry will not occur even if you are running QEMM-386 before Windows. This is because QEMM-386 completely disables itself when Windows 3.0 is running in Enhanced mode. You will see the entry if you are running Windows in either Real or Standard modes. ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD? 3Important Notice: Starting with QEMM-386 version 5.1,3 3the name of the QEMM-386 driver (.SYS) file was 3 3changed from: 3 3 3 3 QEMM.SYS to QEMM386.SYS 3 3 3 3This prevents the Windows 3.0 installation from 3 3incorrectly reporting that QEMM.SYS is incompatible. 3 3So as you read the DESQview 386 or QEMM-386 manual, 3 3remember that QEMM.SYS is now QEMM386.SYS. 3 @DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDY Copyright (C) 1990 by Quarterdeck Office Systems * * * E N D O F F I L E * * *