Instalar.txt: Actualización de Microsoft Windows & MS-DOS 5

IMPORTANTE: Este artículo ha sido traducido por un software de traducción automática de Microsoft (http://support.microsoft.com/gp/mtdetails) en lugar de un traductor humano. Microsoft le ofrece artículos traducidos por un traductor humano y artículos traducidos automáticamente para que tenga acceso en su propio idioma a todos los artículos de nuestra base de conocimientos (Knowledge Base). Sin embargo, los artículos traducidos automáticamente pueden contener errores en el vocabulario, la sintaxis o la gramática, como los que un extranjero podría cometer al hablar el idioma. Microsoft no se hace responsable de cualquier imprecisión, error o daño ocasionado por una mala traducción del contenido o como consecuencia de su utilización por nuestros clientes. Microsoft suele actualizar el software de traducción frecuentemente.

86355
Este artículo se ha archivado. Se ofrece "tal cual" y no se volverá a actualizar.
Resumen
La siguiente información se toma del archivo instalar.txt de actualización de Windows & MS-DOS 5.
Más información
MICROSOFT WINDOWS 3.1 & MS-DOS 5 UPGRADESETUP.TXT===================================================This file provides important information not included in the"Microsoft Getting Started" manual, the "Microsoft MS-DOS User's Guideand Reference," the "Windows User's Guide" or in online Help.Specifically, this file contains information about problems that mightoccur while running the Windows and MS-DOS Setup program and describesproblems that can occur when using terminate-and-stay-resident (TSR)programs or drivers with Windows or the Windows and MS-DOS Setupprogram. If you are using a TSR or if you encounter problems settingup Windows version 3.1, read this document BEFORE running Setup again.For information about other files and documentation, see the "Welcome"section of "Getting Started."Note: Within this document, "Windows Setup" refers to the Windows partof the Windows and MS-DOS Setup program.  You can execute the Windowsonly part of this program by following the instructions below:When this file instructs you to run Windows Setup, do the following:--If this file instructs you to run Setup from the Main Group within  the Windows Program Manager, carry out the procedure as stated.--If you have not installed Microsoft Windows and MS-DOS,  carry out the procedure described in "Getting Started."--If you have installed Microsoft Windows and MS-DOS, and this  file does not instruct you to run Setup from the Main Group,  carry out the following procedure to run Setup for Windows only:  1. Make drive C your current drive.  2. Insert Setup Disk #1 into drive A.  3. Type the following at the command prompt:        a:setup /w  This procedure for running a "Windows only" setup after MS-DOS has  been installed is also described in Appendix A of "Getting Started."General Setup Notes for the Windows portion of Setup=====================================================This section includes notes on specific system configurations that mayprevent Setup from installing Windows successfully. A solution to eachproblem is provided.If you are using a hardware or software product listed here, followthe proposed recommendations before running Setup.MS-DOS Screen Savers---------------------If you are using an MS-DOS screen saver, you should disable it beforerunning Setup. These screen savers can cause problems when runningSetup.AT&T Safari Computer----------------------If you have an AT&T Safari computer, you cannot maintain two versionsof Windows (version 3.0 and version 3.1) on your system. You mustupgrade over version 3.0. If you set up Windows 3.1 in its owndirectory, Windows will not use the special drivers required for it torun on the Safari computer.Using the TIGA Display Driver-------------------------------After successfully setting up Windows, you can increase the amount ofconventional memory available to non-Windows applications when Windowsis running in 386 enhanced mode by loading TIGACD.EXE from theWINSTART.BAT file. The WINSTART.BAT file runs only in 386 enhancedmode. If you want to run Windows in standard mode, you must loadTIGACD.EXE manually. For more information, see the README.WRI onlinedocument.Displays That Are Incompatible with Windows Version 3.1---------------------------------------------------------Certain display adapters can cause problems with Windows version 3.1.The most serious problem is a system failure while running the Windowsand MS-DOS Setup program. If you encounter this problem, run CustomSetup, and then select one of the standard display types, such as VGA,provided with Windows version 3.1.With other display drivers, Windows may be set up successfully butTrueType fonts may not appear correctly on your screen. An updateddriver may be available in the Windows Driver Library or from yourdisplay vendor or manufacturer. For information about obtaining theWindows Driver Library, see "You have special hardware to set up withWindows" in Chapter 3, "Troubleshooting During Setup," in "GettingStarted."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 3.1.- All 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 3.1.- HP Ultra VGA- 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- All 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- All S3 adapters, including the following:      Orchid Fahrenheit 1280      STB WIND/X      Diamond Stealth VRAMUsing Stacker-------------If you are using Stacker to compress your hard disk, there are certainsteps you need to take before setting up Windows.*  Before you run Setup, install MS-DOS 5.0 manually. For   instructions, see section 2.21 of the README.TXT file.*  If you have not set up MS-DOS 5.0, and you want to set up   Windows only on a computer with an older version of Stacker,   your computer might halt on Setup disk 3 while it is analyzing   your system software. If this happens, remove the Setup disk,   restart your computer by pressing CTRL+ALT+DEL, and run   Setup again by typing the following at the command prompt:   a:setup /w /c   Note: Before you run Setup again, make sure all the commands         that load memory-resident programs have been disabled         in your AUTOEXEC.BAT and CONFIG.SYS files. To disable         a command, type "rem" and a space in front of the command         in your CONFIG.SYS and AUTOEXEC.BAT file. Then save the file,         and restart your computer.*  If you want to use a swap file with Windows, 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. For more information about   swap files, see "Working with Windows Swap Files" in Chapter 14,   "Optimizing Windows," in the "Microsoft Windows User's Guide."   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 upgraded from an earlier version of Stacker to   Stacker 2.0 or later, choose the Custom Setup option   when you run Setup. When Setup prompts you, don't choose to let   Setup modify your CONFIG.SYS and AUTOEXEC.BAT files. Modify   these files yourself after Setup is complete by carrying out   the following steps:   * In your AUTOEXEC.BAT, add Windows to your path.   * Copy the HIMEM.SYS and EMM386.EXE files to your     uncompressed drive, unless you use a different memory     manager, such as QEMM-386.   * Add DEVICE commands for HIMEM.SYS and EMM386.EXE to     your CONFIG.SYS file, unless you use a different memory     manager such as QEMM-386. The command lines that load     these drivers should appear before the command that loads     STACKER.COM.   * Make sure a copy of SMARTDRV.EXE is on the     uncompressed drive. In your CONFIG.SYS file, the     SMARTDRV.EXE command line should include the     "/double_buffer" switch and should be the path     of the file at boot time. For example, if SMARTDRV.EXE     is in the root directory at boot time, you would include     the following command in your CONFIG.SYS:     DEVICE=C:\SMARTDRV.EXE /DOUBLE_BUFFER     SMARTDRV.EXE should be loaded before STACKER.COM in the     CONFIG.SYS file.   * In the AUTOEXEC.BAT file, the SMARTDRV.EXE command     line should be the path of the file after disk drives     are swapped. Also, add the /L switch to the SMARTDRV.EXE     command in your AUTOEXEC.BAT file.*  If you are using Stacker version 2.0 or later, but didn't   upgrade from Stacker version 1.1, choose the Express Setup   option when you are prompted. Setup will modify your CONFIG.SYS   and AUTOEXEC.BAT files for you. When Setup is finished making   the modifications, it displays a message at the end   of the Windows portion of Setup that notifies you of the   modifications that have been made. 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. Choose Yes.*  If you are using a version of Stacker earlier than 2.0, you   need to modify your CONFIG.SYS and AUTOEXEC.BAT files   yourself, using the CONFIG.WIN and AUTOEXEC.WIN files that   Setup generates. For information about using these files,   see "Modifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself,"   following this topic.*  After you have set up MS-DOS manually, type the following at   the command prompt to set up Windows:   a:setup /wModifying Your CONFIG.SYS and AUTOEXEC.BAT Files Yourself---------------------------------------------------------When you set up Windows, 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 availablewhen you start your computer, such as a removable or nonlocaldisk, 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).- The path in your AUTOEXEC.BAT is too long.Instead, Setup writes proposed changes to the CONFIG.WIN andAUTOEXEC.WIN or the CONFIG.00x and AUTOEXEC.00x files.In this case, you must either move the HIMEM.SYS, SMARTDRV.EXE,and EMM386.EXE files to a drive that is available when you startyour computer, or use a text editor to modify your CONFIG.SYS orAUTOEXEC.BAT file so that any references to HIMEM.SYS,SMARTDRV.EXE, and EMM386.EXE appear after the DEVICE=command line used to load the drivers for your disk drives. Referto the CONFIG.WIN and AUTOEXEC.WIN or the CONFIG.00x andAUTOEXEC.00x files for the proposed changes.Setting Up XGA on a PS/2 Model 75 or 90----------------------------------------If you have a PS/2 model 75 or 90 with an XGA, theWindows and MS-DOS Setup program will configurethe display adapter for 16-color, 640x480 resolution.Do not change this configuration during Setup.Specifying a different XGA configuration while settingup Windows may cause Setup to fail.After you have successfully installed Windows, you canconfigure your XGA to use a different resolution or 256 colors,if your monitor supports it. For more information on how to dothis, see the topic "IBM XGA" in the README.WRI onlinedocument.If you are using the plasma screen on the PS/2 model 75, useONLY the 640x480, 16-color configuration. If you change thisconfiguration, you will be returned to the MS-DOS prompt whenyou try to start Windows.Correcting the "Out of Environment Space" Error Message-------------------------------------------------------If you receive an "out of environment space" message whenstarting Windows, you can either:*  Increase the size of your environment by adding the SHELL=   command line to your CONFIG.SYS file. See your MS-DOS   documentation for more information about the SHELL command   and modifying your CONFIG.SYS file.*  Move the SET commands in your AUTOEXEC.BAT file   to the beginning of the file so that they run before the   commands that load terminate-and-stay-resident (TSR)   programs or drivers, such as SMARTDrive.If Setup Does Not Detect Your Network--------------------------------------If you have a network installed, you choose Custom Setup,and Setup specifies "No Network" in the System-Informationscreen, Setup is not able to detect your network. For Setup todetect certain networks, the directory that contains thenetwork program files must be included in your path.This is a known problem with these networks: 3Share, 3Open,LAN Manager, and MSNet. If your path does not include thedirectory where the network files are located, you can either:*  Add the directory to the PATH line in your AUTOEXEC.BAT   file.*  Run Custom Setup again and specify the full path for your   network in the System-Information screen.Using Terminate-and-Stay-Resident (TSR) Programs and Driverswith Windows Version 3.1=============================================================The Program Listing section of this document lists severalterminate-and-stay-resident (TSR) programs and drivers thatare known to cause problems when running with Windows version3.1. Some of the problems you may encounter include systemfailures or an incorrect display of information on your screen.In some cases, special steps are provided to solve the problems.While setting up Windows version 3.1, the Windows portion ofSetup searches the AUTOEXEC.BAT and CONFIG.SYS filesfor references to TSR programs and drivers, in addition toscanning memory for TSRs that are currently running. If Setupdetects a TSR that is known to cause problems when runningwith Windows version 3.1, a message appears, asking whetheryou want to continue or quit Setup.If you receive such a message, do the following:1. Locate your TSR in the Program Listing section of this document   and use the information to determine if the situation encountered   prevents Windows Setup from successfully installing Windows 3.1.2. If the situation does not affect Windows Setup, you can continue   setting up Windows 3.1 by following the instructions on your   screen.   If the situation does affect Windows Setup and prevents it from   installing Windows on your computer, follow the instructions   on the screen to quit Setup, and then complete the following   steps.3. Quit the TSR and remove all references to it from your   AUTOEXEC.BAT and CONFIG.SYS files. For more information,   see the documentation for your TSR.4. Restart your computer.5. Run Windows Setup again.After Windows is successfully set up, you may want to restoreyour TSRs.Not all TSRs or drivers included in the Program Listing sectionare detected by Setup. The TSRs and drivers that Setup detectsare in the SETUP.INF file, listed under the names "incomptsr1"and "incomptsr2".Program Listing===============This section describes some problems, discovered during testing, thatyou might encounter while using a TSR with Windows version 3.1. Itdoes not include all possible problems that can occur.386MAX------The documentation for 386MAX recommends against setting the EXTparameter below 64. If you set this parameter to 0, Windows Setup andWindows running in standard mode will fail.See the README.WRI online document for more information about running386MAX with Windows 3.1.386MAX Disk-Cache Utility (QCACHE.EXE)--------------------------------------Do not use this disk-cache utility simultaneously with SMARTDrive.There is no reason to use two disk-cache utilities with Windows. It isrecommended that you use SMARTDrive, which is installed with Windows3.1, instead.All Charge 386 Version 3.1--------------------------ALLEMM4.SYS is a memory manager that causes problems with Setup andWindows 3.1. If you encounter problems running this program withWindows, it is recommended that you use EMM386.EXE and HIMEM.SYS,provided with Windows 3.1, to manage memory instead.Anarkey Version 4.00--------------------With some memory configurations, Anarkey version 4.00 running withWindows 3.1 in 386 enhanced mode may cause unpredictable systemfailures. In rare cases, this program can also corrupt hard-disk data.In addition, Windows 3.1 might not start when this program is running.Do not run Windows 3.1 in 386 enhanced mode when Anarkey version4.00 is running. Version 4.01 may correct these problems. ContactModerne Software for a free upgrade of Anarkey 4.01.Anarkey Version 4.01--------------------If Anarkey version 4.01 is loaded before starting Windows in standardmode, it is not available in any MS-DOS Prompt that you start fromWindows. In this case, it is recommended that you load Anarkey fromeach MS-DOS Prompt, as needed.Do not load Anarkey HIGH before starting Windows in 386 enhanced mode.If you load Anarkey HIGH, your system may fail when you try to startan application.APPEND (MS-DOS)---------------Do not use the APPEND utility with Windows 3.1. It prevents Windowsand Windows applications from creating valid Well-Formed-Path (WFP)names for the files they are using. (A WFP is the complete name of afile, including the drive letter and full path specification, startingfrom the root directory.)ASP Integrity Toolkit Version 3.7---------------------------------This product is a virus-protection program that can cause problemswhen running Windows Setup, including system failure, automaticrestarting of the system, and the inability to use the keyboard. Youshould turn off protection in the toolkit before setting up Windows3.1. For information about how to do this, see your ASP Integritydocumentation.Note: Setting up Windows is considered a system-administration      task. The ASP Integrity Toolkit documentation instructs      you to turn off protection when performing these types      of tasks.ASSIGN.COM----------If you are using this MS-DOS utility to reassign a drive letter,change the drive back to its original letter by typing the followingat the command prompt before you run Setup:assignAutocon Version 2.0e--------------------Autocon enables you to select up to fifty different configurationswhen starting your system. To do this, it modifies the CONFIG.SYSand AUTOEXEC.BAT files, based on information in its database(AUTOCON.DAT), when you restart your system from within AUTOCON.Windows Setup modifies only the first section in the CONFIG.SYSand AUTOEXEC.BAT files. If you want to use specific configurationswith Windows, you must run Autocon and then manually edit theconfigurations in the database that you want to use. You must dothis after setting up Windows. For your changes to take effect,you must restart your system from within Autocon. For moreinformation, see your Autocon documentation.Bootcon Version 1.60--------------------Using Bootcon, you can maintain different system-configurationinformation in your CONFIG.SYS and AUTOEXEC.BAT files. You can thenselect the configuration you want to use from a menu when startingyour system.Windows Setup modifies only the first section in the CONFIG.SYSand AUTOEXEC.BAT files. You must edit the sections of those filesthat contain the configurations you want to use after you set upWindows. For more information, see your Bootcon documentation.BOOT.SYS---------Using BOOT.SYS, you can maintain different system-configurationinformation in your CONFIG.SYS and AUTOEXEC.BAT files. You can thenselect the configuration you want to use from a menu when startingyour system.Windows Setup modifies only the first section in the CONFIG.SYSand AUTOEXEC.BAT files. You must edit the sections of those filesthat contain the configurations you want to use after you setup Windows. For more information, see your BOOT.SYS documentation.Bootsafe--------If you are running Bootsafe, you may experience problems whilerunning Setup. Carry out the following procedure:1    Open your AUTOEXEC.BAT with any text editor.2    Type "REM" and a space in front of the line that loads     Bootsafe. For example, the line might look something like this:     rem c:\cpav\bootsafe3    Save the file, and restart your computer by pressing     CTRL+ALT+DEL.4    Run Setup again.CACHE.EXE Disk-Cache Utility----------------------------Do not use two disk-cache utilities with Windows 3.1. It isrecommended that you use SMARTDrive, provided with Windows 3.1, andremove all references to other disk-cache utilities from yourCONFIG.SYS and AUTOEXEC.BAT files. (If CACHE.EXE is detected, Setupremoves it from the CONFIG.SYS file for you.)CACHE.SYS Disk-Cache Utility----------------------------This disk-cache utility will not work properly with SMARTDrive. It isrecommended that you use SMARTDrive, provided with Windows 3.1, andremove all references to other disk-cache utilities from yourCONFIG.SYS and AUTOEXEC.BAT files. (If CACHE.SYS is detected, Setupremoves it from the CONFIG.SYS file for you.)CED Version 1.0e----------------Using CED with Windows 3.1 may cause problems, including systemfailure. It is recommended that you do not use CED with Windows 3.1.Central Point Anti-Virus Version 1.1 (VSAFE.COM/VSAFE.SYS)----------------------------------------------------------VSAFE.COM/VSAFE.SYS should not be loaded when you set up Windows 3.1.Otherwise, Setup may not run properly. After you set up Windows 3.1,you can load VSAFE.Because Windows uses the disk for memory swapping, you should turn offthe VSAFE write-protection option when running Windows. For moreinformation, see the Central Point Anti-Virus documentation.CMDEDIT.COM Version 2.0 (Date 12-6-91)--------------------------------------If this command-line editor is loaded before starting Windows, it maycause a General Protection Fault when running multiple MS-DOS Promptsin 386 enhanced mode. Also, it cannot be loaded from an MS-DOS Promptwithin Windows when Windows is running in standard mode.Cubit Version 3.01------------------When using Cubit with Windows 3.1, do not compress the Windows SYSTEMdirectory or any file that is loaded from the CONFIG.SYS file.Compressing these files could cause problems.Before upgrading to Windows 3.1, make sure that the earlier version ofWindows is uncompressed on your hard disk. You may recompress thefiles after you have successfully set up Windows 3.1.Data Physician Plus Version 2.0 (VirALERT)------------------------------------------It is recommended that you do not set up Windows while VirALERT isrunning. If you do, VirALERT will display a warning message every fewseconds while Setup is running.After you have set up Windows, you can run VirALERT. Press ALT+V todisplay the VirALERT menu. You can use the commands on this menu todisable and enable VirALERT.DOSCUE.COM Command-Line Editor------------------------------The DOSCUE command-line editor produces unexpected results when usedwith Windows version 3.1. It is recommended that you do not use thiseditor with Windows 3.1.Doubledisk Version 2.5----------------------Windows 3.1 may try to access "phantom" disk drives if you useDoubledisk with Windows 3.1. Phantom drives occur when youuse Doubledisk to create a compressed drive. For example, if youhave drives A, B, and C on your computer and you use Doublediskto create drive F, Windows 3.1 (and MS-DOS) recognize drives Dand E as valid drives, even though they do not actually exist. Youcan use the DRVOFF utility to prevent Windows from recognizingphantom drives. Contact Vertisoft to order a copy of the DRVOFFutility.FASTOPEN (MS-DOS)-----------------FASTOPEN is a RAM resident utility. Problems involving the fileallocation table (FAT) may occur if FASTOPEN is used together withdisk de-fragmenting utilities. In low-memory situations, you may needto remove FASTOPEN for Windows 3.1 to run properly.Flash Disk-Cache Utility (FLASH.EXE)-------------------------------------Do not use this disk-cache utility simultaneously with SMARTDrive.There is no reason to use two disk-cache utilities with Windows. It isrecommended that you use SMARTDrive, which is installed with Windows3.1, instead.Graphics (MS-DOS)-----------------Loading Graphics from an MS-DOS Prompt within Windows can causeunexpected results when printing. The active MS-DOS Prompt will sendits output to the printer. Switching between MS-DOS Prompts may resultin mixed printing jobs.HIMEMSLS.SYS (Software Carousel)If you use the HIMEMSLS.SYS driver with Software Carousel, open yourCONFIG.SYS with any text editor, and delete the command that loads thedriver. Then save the file, restart your system, and run Setup.Setup will install the HIMEM.SYS driver when it installs Windows.Use the HIMEM.SYS driver; do not reinstall the HIMEMSLS.SYS driver.HPEMM386.SYS and HPEMM486.SYS-----------------------------These expanded-memory managers are incompatible with Windows when itis running in 386 enhanced mode. If you plan on running Windows in 386enhanced mode, it is recommended that you use EMM386.EXE to managememory instead.HPMM.SYS - HP Memory Manager----------------------------When HPMM.SYS is running, you cannot set up Windows 3.1 or run it instandard mode. You should remove all references to HPMM.SYS from yourCONFIG.SYS and AUTOEXEC.BAT files before setting up Windows 3.1.Hyperdisk Disk-Cache Utility----------------------------Do not use this disk-cache utility simultaneously with SMARTDrive.There is no reason to use two disk-cache utilities with Windows. It isrecommended that you use SMARTDrive, which is installed with Windows3.1, instead.IBM VDISK.SYS (RAM Disk Utility)--------------------------------VDISK.SYS is incompatible with Windows because it occupies extendedmemory required to run Windows. This utility prevents any XMS-compatible memory manager from loading.IEMM.SYS Memory Manager-----------------------The IEMM.SYS memory manager is incompatible with Windows. It isrecommended that you remove all references to IEMM.SYS from yourCONFIG.SYS and AUTOEXEC.BAT files and use EMM386.EXE, provided withWindows 3.1, to manage memory instead.ICACHE.SYS Disk-Cache Utility-----------------------------Do not use two disk-cache utilities with Windows version 3.1. It isrecommended that you use SMARTDrive, provided with Windows 3.1, andremove all references to other disk-cache utilities from yourCONFIG.SYS and AUTOEXEC.BAT files. (If ICACHE.SYS is detected, Setupremoves it from the CONFIG.SYS file for you.)IBMCACHE.SYS Disk-Cache Utility-------------------------------Do not use two disk-cache utilities with Windows version 3.1. It isrecommended that you use SMARTDrive, provided with Windows 3.1, andremove all references to other disk-cache utilities from yourCONFIG.SYS and AUTOEXEC.BAT files. (If IBMCACHE.SYS is detected, Setupremoves it from the CONFIG.SYS file for you.)Intel Expanded-Memory Emulator (ILIM386.SYS)--------------------------------------------The ILIM386.SYS expanded-memory emulator, provided with the IntelInboard/386 product, is incompatible with Windows 3.1. It isrecommended that you remove all references to this emulator from yourCONFIG.SYS and AUTOEXEC.BAT files before setting up Windows 3.1.JOIN (MS-DOS)-------------Do not add or remove "joined" drives while running Windows 3.1. If youuse the JOIN command before starting Windows 3.1 and do not change thestate of the joined drives from an MS-DOS Prompt within Windows,Windows 3.1 will work properly. It is recommended that you do not usejoined drives at all if you plan on running Windows.KBFLOW TSR by Artisoft----------------------If you load the KBFLOW TSR utility provided by Artisoft beforestarting Windows 3.1, your system may fail when starting or using anMS-DOS Prompt from within Windows.KEYB.COM (MS-DOS)-----------------If you use command-line options to load KEYB.COM, it is recommendedthat you load it before starting Windows. After it is loaded, you canchange the keyboard configuration from an MS-DOS Prompt within Windowsany time. If you do not load KEYB.COM before starting windows, you mayencounter problems using a KEYB command that includes an option in anMS-DOS Prompt. However, you can use the KEYB command without optionsat any time to display code-page information.Lansight Version 2.0--------------------Lansight is a utility that you can use to control and monitor otherworkstations attached to a Novell network. In some cases, version 2.0of Lansight may cause the workstation running Windows 3.1 to fail.Lasertool Control Panel Version 2.2------------------------------------If you load version 2.2 of the Lasertool Control Panel program(PCPANEL.EXE) from Windows 3.1, your system may fail. This programworks properly if you load it before starting Windows.Le Menu Version 1.0-------------------When using Le Menu version 1.0 with Windows 3.1, environmentinformation such as PATH, PROMPT and WINDIR may be lost if you startan MS-DOS Prompt from within Windows. If you want to start Windows 3.1by using a Le Menu menu command, it is recommended that you set upWindows 3.1 as a Batch-File menu command so that COMMAND.COM will loadbefore starting Windows 3.1. For more information, see your Le Menudocumentation.LOCKIT Version 3.3 (PC Vault, Secure It)----------------------------------------Version 3.3 of these programs strips out spaces from the LOAD= commandline in the WIN.INI file. Later versions may correct this problem.Logitech Mouse Software Version 5.0/6.0 (CLICK, LOGIMENU)---------------------------------------------------------If you want to use CLICK and LOGIMENU from an MS-DOS Prompt withinWindows, you must load the TSRs from that MS-DOS Prompt, even if youloaded the TSRs before starting Windows. When you quit Windows, youmust reload the TSRs for them to work properly from the MS-DOS promptoutside of Windows, even if you loaded them from an MS-DOS Promptwithin Windows.Mace Disk-Cache Utility (MCACHE.SYS)------------------------------------This disk-cache utility will not work properly with SMARTDrive. It isrecommended that you use SMARTDrive, provided with Windows 3.1, andremove all references to other disk-cache utilities from yourCONFIG.SYS and AUTOEXEC.BAT files. (If Mace is detected, Setupremoves it from the CONFIG.SYS file for you.)Maximizer Memory Manager (MAXIMIZE.COM)---------------------------------------If you are using the Maximizer memory manager, you may not be able toset up or start Windows. Make sure that you are using only one memorymanager with Windows 3.1. It is recommended that you use HIMEM.SYS andEMM386.EXE, which are installed with Windows 3.1, to manage memoryinstead.MIRROR (MS-DOS)-----------------If MIRROR is loaded from Windows 3.1 by using the Run command instandard mode, you cannot remove it from memory by using the MIRROR /Ucommand. This will cause an error message to appear.NDOSEDIT.COM (Date 1-1-84)--------------------------You may have problems loading this command-line editor. Also, it maycause unexpected results when running with Windows 3.1.NetRoom Memory Manager (RM386.SYS)----------------------------------With some older versions of NetRoom, you may encounter problemssetting up Windows. In this case, contact Helix Software for a newerversion of NetRoom.Newspace Version 1.07---------------------This disk-compression utility is incompatible with Windows 3.1 and maycause several problems.Norton Anti-Virus Version 1.0-----------------------------If you load version 1.0 of Anti-Virus before setting up Windows, Setupmay fail. It is recommended that you contact Symantec for the mostcurrent version of this program.Norton Desktop for Windows (EP.EXE)-----------------------------------If the data-recovery program Erase Protect (EP.EXE) is loaded from theAUTOEXEC.BAT file, you need to disable it when setting up Windows 3.1,especially if you are upgrading over a previous version of Windows.Erase Protect tries to save copies of all deleted files, which cancause you to run out of disk space while running Setup. It isrecommended that you run Erase Protect with a permanent swap file, nota temporary swap file. If you are using a temporary swap file, youneed to exclude files with a .TMP or .SWP extension from eraseprotection.Norton Utilities Version 5.0 (DISKREET, NCACHE)-----------------------------------------------This program is incompatible with Windows 3.1 and may cause yoursystem to fail. It is recommended that you upgrade to the most recentversion of Norton Utilities to correct problems.Norton Utilities Version. 6.01 (NCACHE)---------------------------------------Some versions of NCACHE may prevent you from setting up or startingWindows 3.1. When Windows is running in standard mode, your system mayfail, especially if NCACHE is set up as an EMS cache. Setting upNCACHE as an EMS cache is not recommended. Setting up NCACHE as an XMScache may solve the problem.You may also encounter additional problems using NCACHE. New versionsmay correct these problems. For an updated version of NCACHE, contactSymantec Corporation. In the meantime, you can use SMARTDrive, whichis provided with Windows 3.1.Norton Utilities Version 6.01 (DISKMON)--------------------------------------It is recommended that you do not use DISKMON version 6.01 withWindows 3.1.PCED Version 2.00-----------------Do not load the PCED command-line editor HIGH. Loading it HIGH maycause unexpected results, such as system failures, when Windows isrunning in 386 enhanced mode. If you load this program before startingWindows, it may be unavailable when Windows is running in standardmode.PCKEY.EXE (MultiSoft Keyboard Enhancer and Command-Line Stack)--------------------------------------------------------------PCKEY.EXE may not work properly with Windows 3.1 when you are runningmore than one non-Windows application at a time. It is recommendedthat you unload PCKEY.EXE before starting Windows.PC-Kwik Disk Accelerator------------------------If you use PC-Kwik when Windows is running in 386 enhanced mode, makesure that you are using version 3.55 or later and that PC-Kwik is inextended memory, not expanded memory. To get an upgraded version ofPC-Kwik, contact MultiSoft.PC-Kwik Disk-Cache Utility (PC-KWIK.EXE)----------------------------------------Do not use this disk-cache utility simultaneously with SMARTDrive.There is no reason to use two disk-cache utilities with Windows. It isrecommended that you use SMARTDrive, provided with Windows 3.1,instead.PC-Kwik Version. 1.59 (PCK.EXE, PSKSCRN.EXE, PCKEY.COM)-------------------------------------------------------If version 1.59 of PC-KWIK is loaded before setting up Windows,Setup may fail. PC-KWIK Version 2.0 may correct this problem.PCSXMAEM.SYS Utility--------------------This utility is incompatible with Windows. You should remove allreferences to it from your CONFIG.SYS and AUTOEXEC.BAT files beforesetting up or starting Windows 3.1. PCSXMAEM.SYS is similar toXMAEM.SYS. It has been renamed and slightly modified. It is providedwith current versions of the IBM PC/3270 emulator.PCSX2EMS.SYS-------------Windows will run correctly with PCSX2EMS.SYS if it is loaded on acomputer that has an XMA board installed. Otherwise, this program isincompatible with Windows. PCSX2EMS.SYS is provided with the IBMPC/3270 emulator.PC Tools Deluxe Version 7.1 (DATAMON)------------------------------------If you load PC Tools DATAMON using the \SENTRY+ option, Setup may failif you are low on disk space. Do not use the \SENTRY+ option whenloading DATAMON.Do not load DATAMON after loading SMARTDrive. If DATAMON is loadedafter SMARTDrive, your system may fail. See the PC Tools documentationfor information about how to unload DATAMON.PC Tools Deluxe Version 6.0 (DESKTOP)------------------------------------If you try to start PC Tools from an MS-DOS Prompt within Windows instandard mode, your system may fail. In enhanced mode, your system mayrestart itself. These problems also occur if you use MS-DOS commandsfrom an MS-DOS Prompt within Windows.Version 7.0 of PC Tools may correct these problems.  However, do notload DESKTOP from an MS-DOS Prompt if it was loaded before startingWindows 3.1. If you do, your system may fail when you quit Windows. Itis recommended that you run DESKTOP from its PIF, provided withWindows 3.1.PC Tools Deluxe Version 7.1 (VDEFEND)-------------------------------------Setup may not work properly if VDEFEND is loaded before running Setup.You may load VDEFEND after setting up Windows 3.1.PC Tools Disk-Cache Utility (PC-CACHE.COM)-----------------------------------------Do not use this disk-cache utility simultaneously with SMARTDrive.There is no reason to use two disk-cache utilities with Windows. It isrecommended that you use SMARTDrive, which is installed with Windows3.1, instead.PRINT (MS-DOS)--------------If you are printing several large documents on a network printer andrun Windows Setup from the network, your system may fail while Setupis creating Program Manager groups.Printer Assist Version 4.20---------------------------Printer Assist is a TSR that you can use to share a workstationprinter with other workstations on Netware 286 and 386 systems. SomeWindows applications (such as Microsoft Word for Windows) printextended characters, mixed with correct output when this program isloaded.PYRO! Version 1.0-----------------If this screen saver is loaded before starting Windows 3.1, you maynot be able to restore the Windows 3.1 screen after this screen saverappears.QMAPS Memory Manager Version 5.16---------------------------------If you are using the QMAPS memory manager, you may not be able to setup or start Windows. New versions may correct these problems. For anupdated version of QMAPS, contact Quadtel. In the meantime, you mayuse HIMEM.SYS and EMM386.EXE, provided with Windows 3.1, to managememory instead.RAMTYPE.SYS - AST RAMpage! Boards---------------------------------The RAMTYPE.SYS driver is incompatible with Windows. It is recommendedthat you remove this driver before setting up Windows 3.1. If you loadthe driver from your CONFIG.SYS file, comment out the command line forthe driver as follows:   rem RAMTYPE.SYSWindows 3.1 will run correctly without RAMTYPE.SYS. However, otherdrivers that rely on RAMTYPE.SYS will not load and applications willnot be able to use the expanded memory on your system.After setting up Windows, you can use version 1.2 and later ofRAMTYPE.SYS with Windows. If you are using an earlier version on anIBM PS/2 or micro-channel architecture computer and your RAMpage!board is configured for expanded and extended memory, you need toupgrade your AST RAMTYPE.SYS driver after setting up Windows. You willalso need to remove the "rem" command from your CONFIG.SYS file sothat RAMTYPE.SYS will load properly.Secretdisk II Disk-Cache Utility (FAST512.SYS)----------------------------------------------This disk-cache utility will not work properly with SMARTDrive. It isrecommended that you use SMARTDrive, provided with Windows 3.1, andremove all references to other disk-cache utilities from yourCONFIG.SYS and AUTOEXEC.BAT files. (If this utility is detected, Setupremoves it from the CONFIG.SYS file for you.)SideKick Versions 1.0 and 2.0 and SideKick Plus-----------------------------------------------Miscellaneous problems may occur when running SideKick as a TSR withWindows 3.1. It is recommended that you use a PIF to run SideKick as anon-Windows application, instead of loading it as a TSR.SoftIce Debugger----------------If SoftIce is loaded, Setup will fail when starting the Windowsportion of the program. It is recommended that you unload SoftIcebefore setting up Windows 3.1.SpeedFXR--------This program is incompatible with Windows 3.1 when running as a TSR.It tries to increase the speed of the floppy disk drives, but slowsthem down instead. To get the best results, use the -X option whenloading SpeedFXR. This will prevent SpeedFXR from remaining in memoryand affecting the speed of the floppy disk drives.SUBST (MS-DOS)--------------Do not add or remove "substituted" drives while running Windows 3.1.If you use the SUBST command before starting Windows and do not changethe state of the substituted drives from an MS-DOS Prompt withinWindows, Windows 3.1 will work properly.Super PC-Kwik Disk-Cache Utility (SUPERPCK.EXE)-----------------------------------------------Do not use this disk-cache utility simultaneously with SMARTDrive.There is no reason to use two disk-cache utilities with Windows. It isrecommended that you use SMARTDrive, which is installed with Windows3.1, instead.Trantor T100 Host Adapter Driver (TSCSI.SYS)--------------------------------------------(For SCSI hard disk drives) - If you use the Trantor T100 driver(TSCSI.SYS), you must use version 4.33d or higher. Earlier versionsidentify the SCSI hard disk drive as a removable drive. This may causeproblems when using File Manager, such as a system failure whileformatting the drive and unexpected results when deleting files. Toget an updated driver, contact Trantor Systems, Ltd.UMB PRO Version 1.07--------------------If you are running UMB PRO, you may experience problems runningWindows in standard mode. In some cases, your system may fail. Makesure that you are using only one memory manager with Windows 3.1. Itis recommended that you use HIMEM.SYS and EMM386.EXE, which areinstalled with Windows 3.1, to manage memory instead.Vaccine-------If Vaccine is loaded, Setup fails when trying to modify the CONFIG.SYSand AUTOEXEC.BAT files. You should unload Vaccine before setting upWindows 3.1. You may also encounter problems, such as beeping, whilerunning Windows when Vaccine is loaded.VIREX-PC Version 1.11---------------------If VIREXPC.COM is loaded, Windows Setup and Windows 3.1 will fail whenKRNL386.EXE performs a write operation. Also, the first time Windows3.1 is loaded, you may be returned to the MS-DOS prompt.Virus Prevention Plus Version 5.0---------------------------------If Virus Prevention Plus is loaded, you may not be able tosuccessfully set up Windows 3.1. You may also encounter problems whenrunning Windows 3.1 in 386 enhanced mode. The Keyboard Lock programmay cause Windows to fail.Virusafe Version 4.0--------------------If this program is loaded as a TSR, Setup may fail while settingup Windows 3.1. It is recommended that you load Virusafe by usingthe /C- option. This option turns off the memory-change detectionprovided with Virusafe. Version 4.5 may correct this problem.For more information, see your Virusafe documentation.XGAAIDOS.SYS------------With XGAAIDOS.SYS loaded, Windows 3.1 will fail at the openinglogo if you use the WIN /s option to start Windows in standard mode.XMAEM.SYS---------XMAEM.SYS is a device which causes extended memory to act like XMA.This utility is incompatible with Windows 3.1. It is recommended thatyou remove all references to it from your CONFIG.SYS and AUTOEXEC.BATfiles before setting up or running Windows 3.1. XMAEM.SYS is providedwith IBM DOS version 4.0.XMA2EMS.SYS-----------Windows will run correctly with XMA2EMS.SYS if it is loaded on acomputer that has an XMA board installed. Otherwise, this program isincompatible with Windows. XMA2EMS.SYS is provided with IBM DOSversion 4.0.				
ndw gpf 3.1 3.10 5 5.0 5.00 KBSetup

Advertencia: este artículo se ha traducido automáticamente

Propiedades

Id. de artículo: 86355 - Última revisión: 02/08/2014 16:01:51 - Revisión: 2.1

  • Microsoft Windows 3.1 Standard Edition
  • Microsoft MS-DOS 5.0 Standard Edition
  • kbnosurvey kbarchive kbmt KB86355 KbMtes
Comentarios