Windows for WorkGroup3.11 英文版

SETUP.TXT ========= This file contains information about problems that may occur while running Windows for Workgroups Setup and describes problems that can occur when using terminate-and-stay-resident (TSR) programs or drivers with Windows for Workgroups or Setup. If you are using a TSR or if you encounter problems setting up Windows for Workgroups, read this document BEFORE running Setup again. General Setup Notes ==================== This section includes notes on specific system configurations that may prevent Setup from installing Windows for Workgroups successfully. A solution to each problem is provided. If you are using a hardware or software product listed here, follow the proposed recommendations before running Setup. Network Cards -------------- If you are using one of the following network cards, you must run Setup with the /i option: Novell/Anthem NE1500 Novell/Anthem NE2100 Advanced Micro Devices (AMD) AM2100 Microdyne EXOS 105 At the MS-DOS prompt, type the following: setup /i MS-DOS Screen Savers --------------------- If you are using an MS-DOS screen saver, you should turn it off before running Setup. These screen savers can cause problems when running Setup. COMPAQ Computer with MS-DOS Version 5.0 and EGA or VGA --------------------------------------------------------- If you are using the upgrade version of Microsoft MS-DOS 5.0, check your CONFIG.SYS file to make sure the following drivers (if present) appear in this order: HIMEM.SYS EMM386.EXE ANSI.SYS Note: If you are using the COMPAQ version of MS-DOS 5.0, HIMEM.EXE is used in place of HIMEM.SYS and CEMM.EXE is used in place of EMM386.EXE. If ANSI.SYS is loaded before HIMEM.SYS or EMM386.EXE (or if you are using COMPAQ MS-DOS 5.0 before HIMEM.EXE or CEMM.EXE), Setup may restart your system before Windows for Workgroups is installed. Also, if you are using the DOS=HIGH,UMB command line to load MS-DOS into upper memory, loading EMM386.EXE (or CEMM.EXE) before loading ANSI.SYS will create the maximum amount of upper memory space on a COMPAQ computer. AT&T Safari Computer -------------------- If you have an AT&T Safari computer, you cannot maintain two versions of Windows (version 3.0 and version 3.1) on your system. You must upgrade over version 3.0. If you set up Windows for Workgroups version 3.1 in its own directory, it will not use the special drivers required to run on the Safari computer. Displays That May Require Driver Updates with Windows for Workgroups -------------------------------------------------------------------- Certain third-party display drivers designed for Windows version 3.0 can cause problems with Windows for Workgroups version 3.1. The most serious problem is a system failure while running Windows for Workgroups Setup. If you encounter this problem, run Custom Setup, and then select one of the standard display types, such as VGA, that is provided with Windows for Workgroups. With other Windows version 3.0 display drivers, Windows for Workgroups may be set up successfully but TrueType fonts may not appear correctly on your screen. An updated driver may be available in the Windows Driver Library (WDL) or from your display vendor or manufacturer. For information about obtaining the WDL, see the "Getting Started" book. Windows version 3.0 drivers for the following display adapters may cause problems: - ATI Graphics Ultra and Vantage NOTE: These adapters are 8514/a-compatible and run well with the 8514/a driver provided with Windows for Workgroups. - DGIS display adapters (Direct Graphics Interface Standard) from Graphic Software Systems, including the following: NEC MultiSynch Graphics Engine (MGE) Zenith Z-649 HP IGC-10, IGC-20 GSS 1000 Series NOTE: Some DGIS-based adapters are TIGA-compatible and run well when used with the appropriate TIGACD.EXE MS-DOS driver and with the TIGA driver provided with Windows for Workgroups. - HP Ultra VGA (versions earlier than 1.4 only) - IBM Image Adapter/A - Matrox MG Series/M-WIN Series - Palettized VGA 640x480, 16-color (provided with Windows Multimedia Extensions version 1.0) - Radius SVGA MultiView - RGDI (Renaissance Graphics Device Interface) display adapters from Appian, Inc., including the following: Appian Rendition II, IIe, II/XE, and III Appian GV1024 Decpc 433 - S3 adapters, including the following: Orchid Fahrenheit 1280 STB WIND/X Diamond Stealth VRAM Using Stacker ------------- If you are using Stacker to compress your hard disk, there are certain steps you need to take before setting up Windows for Workgroups. * If you want to use a swap file with Windows for Workgroups, you must set up the swap file on the uncompressed drive. When setting up Stacker, you can leave at least 1 megabyte (MB) of disk space uncompressed for storing system files. To leave enough space for the swap file, it is recommended that the amount of uncompressed disk space equal at least twice the amount of system memory. For example, if your system has 4 MB of memory, you should leave at least 8 MB of disk space uncompressed. If Stacker is already set up on your system and there is not enough uncompressed disk space for a swap file, you can run the STAC utility provided with Stacker to increase the amount of uncompressed disk space. For more information, see your Stacker documentation. * If you are using Stacker version 2.0 or later, Windows for Workgroups Setup modifies your CONFIG.SYS and AUTOEXEC.BAT files. When Setup finishes making the modifications, it displays a message at the end of the Windows portion of Setup, notifying you of the modifications. If you have used Stacker to swap your startup drive, when you restart your system, Stacker will ask whether you want to update to the new version of the CONFIG.SYS or AUTOEXEC.BAT file. It is recommended that you update. If you are using a version of Stacker earlier than 2.0, you may need to modify your CONFIG.SYS and AUTOEXEC.BAT files yourself. For more information, see the following topic, "Modifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself." * For best performance, do not use SMARTDrive to cache the compressed drive. You only need to cache the uncompressed drive. You can include options on the SMARTDRV.EXE line of the CONFIG.SYS file to specify which drives to cache. For example, if the Stacker swap utility swaps drives C and D so that C is compressed and D is uncompressed, you would include the following line in your AUTOEXEC.BAT file: c:\windows\smartdrv.exe c- d+ For more information about swap files and using SMARTDrive, see Chapter 11, "Managing Memory and Performance," in the "Microsoft Windows for Workgroups User's Guide." Modifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself --------------------------------------------------------- When you set up Windows for Workgroups, Setup usually places the HIMEM.SYS, SMARTDRV.EXE, and EMM386.EXE files in the Windows directory. If the Windows directory is on a disk that is not available when you start your computer, such as a removable or nonlocal disk, or if Setup detects one of the following conditions, Setup does not modify the CONFIG.SYS or AUTOEXEC.BAT file: - Your boot drive has been modified by a disk-compression utility. - Your CONFIG.SYS file contains references to block device drivers. - There is not enough available space on your hard disk to copy the files. - The files are already installed on your system and Setup cannot overwrite them (they are read-only). Instead, Setup writes propose