DOCUMENT:Q100941 21-NOV-1999 [msdos] TITLE :How Setup Determines Where to Place SETVER.EXE in CONFIG.SYS PRODUCT :Microsoft Disk Operating System PROD/VER:MS-DOS:6.0,6.2,6.21,6.22 OPER/SYS: KEYWORDS: ====================================================================== ------------------------------------------------------------------------------- The information in this article applies to: - Microsoft MS-DOS operating system versions 6.0, 6.2, 6.21, 6.22 ------------------------------------------------------------------------------- SUMMARY ======= In most cases, MS-DOS Upgrade Setup places SETVER.EXE on the first line of the CONFIG.SYS file. However, if you are loading ASPI4DOS.SYS, Setup places the command for SETVER.EXE after the command for ASPI4DOS.SYS. MORE INFORMATION ================ If you have a DEVICEHIGH command for SETVER.EXE in your CONFIG.SYS file before you run Setup, Setup removes that command and adds the following one to the top of the file: DEVICE=C:\DOS\SETVER.EXE If you are loading ASPI4DOS.SYS, the above line is added after the command for ASPI4DOS. In either case, SETVER is loaded into conventional memory. To optimize your memory configuration after installing MS-DOS 6, run MemMaker. Additional query words: 6.22 6.00 6.20 ====================================================================== Keywords : Technology : kbMSDOSSearch kbMSDOS621 kbMSDOS622 kbMSDOS620 kbMSDOS600 Version : MS-DOS:6.0,6.2,6.21,6.22 ============================================================================= THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY. Copyright Microsoft Corporation 1999.