{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "IO SYS", "size": 40470, "date": "1993-02-10", "time": "5:59" }, { "name": "MSDOS SYS", "size": 38138, "date": "1993-02-10", "time": "5:59" }, { "name": "ANSI SY_", "size": 6260, "date": "1993-02-10", "time": "5:59" }, { "name": "ATTRIB EXE", "size": 11165, "date": "1993-02-10", "time": "5:59" }, { "name": "AUTOEXEC BAT", "size": 36, "date": "1993-02-10", "time": "5:59" }, { "name": "CHKDSK EXE", "size": 12908, "date": "1993-02-10", "time": "5:59" }, { "name": "COMMAND COM", "size": 52925, "date": "1993-02-10", "time": "5:59" }, { "name": "CONFIG SYS", "size": 13, "date": "1993-02-10", "time": "5:59" }, { "name": "COUNTRY SYS", "size": 17066, "date": "1993-02-10", "time": "5:59" }, { "name": "DBLSPACE BIN", "size": 50284, "date": "1993-02-10", "time": "5:59" }, { "name": "DEBUG EXE", "size": 15715, "date": "1993-02-10", "time": "5:59" }, { "name": "DOSSETUP INI", "size": 3808, "date": "1993-02-10", "time": "5:59" }, { "name": "EDIT COM", "size": 413, "date": "1993-02-10", "time": "5:59" }, { "name": "EXPAND EXE", "size": 16129, "date": "1993-02-10", "time": "5:59" }, { "name": "FDISK EXE", "size": 29333, "date": "1993-02-10", "time": "5:59" }, { "name": "FORMAT COM", "size": 22717, "date": "1993-02-10", "time": "5:59" }, { "name": "KEYB COM", "size": 14983, "date": "1993-02-10", "time": "5:59" }, { "name": "KEYBOARD SYS", "size": 34694, "date": "1993-02-10", "time": "5:59" }, { "name": "MORE COM", "size": 2546, "date": "1993-02-10", "time": "5:59" }, { "name": "MSD EXE", "size": 158470, "date": "1993-02-10", "time": "5:59" }, { "name": "NETWORKS TXT", "size": 20594, "date": "1993-02-10", "time": "5:59" }, { "name": "NLSFUNC EXE", "size": 7036, "date": "1993-02-10", "time": "5:59" }, { "name": "PACKING LST", "size": 7057, "date": "1993-02-10", "time": "5:59" }, { "name": "QBASIC EXE", "size": 194309, "date": "1993-02-10", "time": "5:59" }, { "name": "README TXT", "size": 59333, "date": "1993-02-10", "time": "5:59" }, { "name": "RESTORE EX_", "size": 23328, "date": "1993-02-10", "time": "5:59" }, { "name": "SETUP EXE", "size": 71459, "date": "1993-02-10", "time": "5:59" }, { "name": "SETUP MSG", "size": 1290, "date": "1993-02-10", "time": "5:59" }, { "name": "SYS COM", "size": 9379, "date": "1993-02-10", "time": "5:59" }, { "name": "UNFORMAT COM", "size": 12738, "date": "1993-02-10", "time": "5:59" } ] } ], "volume": "DISK 1" }, "2": { "dirs": [ { "path": "/", "files": [ { "name": "8514 VI_", "size": 6421, "date": "1993-02-10", "time": "5:59" }, { "name": "APPEND EX_", "size": 7462, "date": "1993-02-10", "time": "5:59" }, { "name": "CGA GR_", "size": 1617, "date": "1993-02-10", "time": "5:59" }, { "name": "CGA IN_", "size": 2775, "date": "1993-02-10", "time": "5:59" }, { "name": "CGA VI_", "size": 6131, "date": "1993-02-10", "time": "5:59" }, { "name": "CHOICE COM", "size": 1754, "date": "1993-02-10", "time": "5:59" }, { "name": "DEFRAG EXE", "size": 75017, "date": "1993-02-10", "time": "5:59" }, { "name": "DEFRAG HL_", "size": 4284, "date": "1993-02-10", "time": "5:59" }, { "name": "DELTREE EX_", "size": 6899, "date": "1993-02-10", "time": "5:59" }, { "name": "DISKCOMP CO_", "size": 6657, "date": "1993-02-10", "time": "5:59" }, { "name": "DISKCOPY CO_", "size": 7382, "date": "1993-02-10", "time": "5:59" }, { "name": "DISPLAY SY_", "size": 9796, "date": "1993-02-10", "time": "5:59" }, { "name": "DOSHELP HL_", "size": 2492, "date": "1993-02-10", "time": "5:59" }, { "name": "DOSKEY CO_", "size": 4217, "date": "1993-02-10", "time": "5:59" }, { "name": "DOSSHELL CO_", "size": 1907, "date": "1993-02-10", "time": "5:59" }, { "name": "DOSSHELL EX_", "size": 142511, "date": "1993-02-10", "time": "5:59" }, { "name": "DOSSWAP EX_", "size": 13498, "date": "1993-02-10", "time": "5:59" }, { "name": "DRIVER SY_", "size": 4027, "date": "1993-02-10", "time": "5:59" }, { "name": "EDIT HL_", "size": 15709, "date": "1993-02-10", "time": "5:59" }, { "name": "EGA CP_", "size": 18186, "date": "1993-02-10", "time": "5:59" }, { "name": "EGA GR_", "size": 2466, "date": "1993-02-10", "time": "5:59" }, { "name": "EGA IN_", "size": 2776, "date": "1993-02-10", "time": "5:59" }, { "name": "EGA SY_", "size": 3684, "date": "1993-02-10", "time": "5:59" }, { "name": "EGA VI_", "size": 6160, "date": "1993-02-10", "time": "5:59" }, { "name": "EGAMONO GR_", "size": 2318, "date": "1993-02-10", "time": "5:59" }, { "name": "FASTHELP EX_", "size": 7539, "date": "1993-02-10", "time": "5:59" }, { "name": "FASTOPEN EX_", "size": 7783, "date": "1993-02-10", "time": "5:59" }, { "name": "FC EX_", "size": 12065, "date": "1993-02-10", "time": "5:59" }, { "name": "FIND EX_", "size": 4877, "date": "1993-02-10", "time": "5:59" }, { "name": "GRAPHICS CO_", "size": 11327, "date": "1993-02-10", "time": "5:59" }, { "name": "GRAPHICS PR_", "size": 3883, "date": "1993-02-10", "time": "5:59" }, { "name": "HELP COM", "size": 413, "date": "1993-02-10", "time": "5:59" }, { "name": "HELP HL_", "size": 263852, "date": "1993-02-10", "time": "5:59" }, { "name": "HERC GR_", "size": 1636, "date": "1993-02-10", "time": "5:59" }, { "name": "HERC VI_", "size": 6271, "date": "1993-02-10", "time": "5:59" }, { "name": "HIMEM SY_", "size": 8493, "date": "1993-02-10", "time": "5:59" }, { "name": "LABEL EX_", "size": 6176, "date": "1993-02-10", "time": "5:59" }, { "name": "LOADFIX CO_", "size": 649, "date": "1993-02-10", "time": "5:59" }, { "name": "MEM EX_", "size": 19147, "date": "1993-02-10", "time": "5:59" }, { "name": "MODE CO_", "size": 14849, "date": "1993-02-10", "time": "5:59" }, { "name": "MONO GR_", "size": 296, "date": "1993-02-10", "time": "5:59" }, { "name": "MONO IN_", "size": 2451, "date": "1993-02-10", "time": "5:59" }, { "name": "MOVE EX_", "size": 11323, "date": "1993-02-10", "time": "5:59" }, { "name": "POWER EX_", "size": 5549, "date": "1993-02-10", "time": "5:59" }, { "name": "PRINT EX_", "size": 9614, "date": "1993-02-10", "time": "5:59" }, { "name": "QBASIC HL_", "size": 113096, "date": "1993-02-10", "time": "5:59" }, { "name": "RAMDRIVE SY_", "size": 3282, "date": "1993-02-10", "time": "5:59" }, { "name": "REPLACE EX_", "size": 12800, "date": "1993-02-10", "time": "5:59" }, { "name": "SETVER EX_", "size": 6635, "date": "1993-02-10", "time": "5:59" }, { "name": "SHARE EX_", "size": 8116, "date": "1993-02-10", "time": "5:59" }, { "name": "SMARTDRV EX_", "size": 13791, "date": "1993-02-10", "time": "5:59" }, { "name": "SMARTMON EX_", "size": 13747, "date": "1993-02-10", "time": "5:59" }, { "name": "SMARTMON HL_", "size": 7319, "date": "1993-02-10", "time": "5:59" }, { "name": "SORT EX_", "size": 4355, "date": "1993-02-10", "time": "5:59" }, { "name": "SUBST EX_", "size": 12710, "date": "1993-02-10", "time": "5:59" }, { "name": "TREE CO_", "size": 4753, "date": "1993-02-10", "time": "5:59" }, { "name": "VGA GR_", "size": 3198, "date": "1993-02-10", "time": "5:59" }, { "name": "VGA VI_", "size": 6355, "date": "1993-02-10", "time": "5:59" }, { "name": "VGAMONO GR_", "size": 3214, "date": "1993-02-10", "time": "5:59" }, { "name": "WINA20 38_", "size": 2661, "date": "1993-02-10", "time": "5:59" }, { "name": "XCOPY EX_", "size": 10368, "date": "1993-02-10", "time": "5:59" } ] } ], "volume": "DISK 2" }, "3": { "dirs": [ { "path": "/", "files": [ { "name": "AV GR_", "size": 503, "date": "1993-02-10", "time": "5:59" }, { "name": "BK GR_", "size": 394, "date": "1993-02-10", "time": "5:59" }, { "name": "BKAV GR_", "size": 777, "date": "1993-02-10", "time": "5:59" }, { "name": "BKUD GR_", "size": 687, "date": "1993-02-10", "time": "5:59" }, { "name": "BKUDAV GR_", "size": 1071, "date": "1993-02-10", "time": "5:59" }, { "name": "CHKSTATE SY_", "size": 16770, "date": "1993-02-10", "time": "5:59" }, { "name": "MEMMAKER HL_", "size": 5980, "date": "1993-02-10", "time": "5:59" }, { "name": "MEMMAKER IN_", "size": 794, "date": "1993-02-10", "time": "5:59" }, { "name": "MSBACKDB OVL", "size": 63306, "date": "1993-02-10", "time": "5:59" }, { "name": "MSBACKDR OVL", "size": 67530, "date": "1993-02-10", "time": "5:59" }, { "name": "MSBACKFB OVL", "size": 68730, "date": "1993-02-10", "time": "5:59" }, { "name": "MSBACKFR OVL", "size": 73114, "date": "1993-02-10", "time": "5:59" }, { "name": "MSBACKUP EX_", "size": 2487, "date": "1993-02-10", "time": "5:59" }, { "name": "MSBACKUP HL_", "size": 112396, "date": "1993-02-10", "time": "5:59" }, { "name": "MSBACKUP OVL", "size": 133952, "date": "1993-02-10", "time": "5:59" }, { "name": "MSBCONFG HL_", "size": 18549, "date": "1993-02-10", "time": "5:59" }, { "name": "MSBCONFG OVL", "size": 47210, "date": "1993-02-10", "time": "5:59" }, { "name": "MWBACKF DL_", "size": 6956, "date": "1993-02-10", "time": "5:59" }, { "name": "MWBACKR DL_", "size": 30248, "date": "1993-02-10", "time": "5:59" }, { "name": "MWBACKUP EX_", "size": 160121, "date": "1993-02-10", "time": "5:59" }, { "name": "MWBACKUP HL_", "size": 141281, "date": "1993-02-10", "time": "5:59" }, { "name": "MWGRAFIC DL_", "size": 18094, "date": "1993-02-10", "time": "5:59" }, { "name": "MWUNDEL EX_", "size": 65900, "date": "1993-02-10", "time": "5:59" }, { "name": "MWUNDEL HL_", "size": 17458, "date": "1993-02-10", "time": "5:59" }, { "name": "UD GR_", "size": 402, "date": "1993-02-10", "time": "5:59" }, { "name": "UDAV GR_", "size": 798, "date": "1993-02-10", "time": "5:59" }, { "name": "UNDELETE EXE", "size": 26420, "date": "1993-02-10", "time": "5:59" }, { "name": "VFINTD 38_", "size": 1289, "date": "1993-02-10", "time": "5:59" }, { "name": "WNTOOLS GR_", "size": 1071, "date": "1993-02-10", "time": "5:59" } ] } ], "volume": "DISK 3" }, "4": { "dirs": [ { "path": "/", "files": [ { "name": "DBLSPACE EX_", "size": 170104, "date": "1993-02-10", "time": "5:59" }, { "name": "DBLSPACE HL_", "size": 22194, "date": "1993-02-10", "time": "5:59" }, { "name": "DBLSPACE IN_", "size": 1049, "date": "1993-02-10", "time": "5:59" }, { "name": "DBLSPACE SYS", "size": 339, "date": "1993-02-10", "time": "5:59" }, { "name": "DBLWIN HL_", "size": 4205, "date": "1993-02-10", "time": "5:59" }, { "name": "DOSSHELL HL_", "size": 48773, "date": "1993-02-10", "time": "5:59" }, { "name": "EMM386 EX_", "size": 48725, "date": "1993-02-10", "time": "5:59" }, { "name": "INTERLNK EX_", "size": 10652, "date": "1993-02-10", "time": "5:59" }, { "name": "INTERSVR EX_", "size": 26343, "date": "1993-02-10", "time": "5:59" }, { "name": "MEMMAKER EXE", "size": 118628, "date": "1993-02-10", "time": "5:59" }, { "name": "MONOUMB 38_", "size": 950, "date": "1993-02-10", "time": "5:59" }, { "name": "MSAV EXE", "size": 172198, "date": "1993-02-10", "time": "5:59" }, { "name": "MSAV HL_", "size": 12230, "date": "1993-02-10", "time": "5:59" }, { "name": "MSAVHELP OV_", "size": 17796, "date": "1993-02-10", "time": "5:59" }, { "name": "MSAVIRUS LS_", "size": 11473, "date": "1993-02-10", "time": "5:59" }, { "name": "MSCDEX EXE", "size": 25377, "date": "1993-02-10", "time": "5:59" }, { "name": "MSTOOLS DL_", "size": 8376, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAV EX_", "size": 65629, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAV HL_", "size": 16844, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAVABSI DL_", "size": 23085, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAVDLG DL_", "size": 10232, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAVDOSL DL_", "size": 19702, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAVDRVL DL_", "size": 4219, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAVMGR DL_", "size": 9569, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAVSCAN DL_", "size": 70797, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAVSOS DL_", "size": 3983, "date": "1993-02-10", "time": "5:59" }, { "name": "MWAVTSR EX_", "size": 8445, "date": "1993-02-10", "time": "5:59" }, { "name": "SIZER EX_", "size": 4136, "date": "1993-02-10", "time": "5:59" }, { "name": "VSAFE CO_", "size": 33046, "date": "1993-02-10", "time": "5:59" } ] } ], "volume": "DISK 4" }, "5": { "dirs": [ { "path": "/", "files": [ { "name": "PRINTER SYS", "size": 18804, "date": "1993-02-10", "time": "5:59" }, { "name": "4201 CPI", "size": 6404, "date": "1993-02-10", "time": "5:59" }, { "name": "4208 CPI", "size": 720, "date": "1993-02-10", "time": "5:59" }, { "name": "5202 CPI", "size": 395, "date": "1993-02-10", "time": "5:59" }, { "name": "LCD CPI", "size": 10753, "date": "1993-02-10", "time": "5:59" }, { "name": "ADOS CFG", "size": 61, "date": "1993-02-10", "time": "5:59" }, { "name": "ADOS COM", "size": 31086, "date": "1993-02-10", "time": "5:59" }, { "name": "ADOS OVL", "size": 92154, "date": "1993-02-10", "time": "5:59" }, { "name": "ADOS TXT", "size": 100994, "date": "1993-02-10", "time": "5:59" }, { "name": "DVORAK SYS", "size": 2441, "date": "1993-02-10", "time": "5:59" }, { "name": "DVORAK TXT", "size": 8542, "date": "1993-02-10", "time": "5:59" }, { "name": "FAKEMOUS COM", "size": 307, "date": "1993-02-10", "time": "5:59" }, { "name": "README TXT", "size": 26235, "date": "1993-02-10", "time": "5:59" }, { "name": "DBLBOOT BAT", "size": 1965, "date": "1993-02-10", "time": "5:59" }, { "name": "DBLBOOT INI", "size": 91, "date": "1993-02-10", "time": "5:59" }, { "name": "ASSIGN COM", "size": 6399, "date": "1993-02-10", "time": "5:59" }, { "name": "BACKUP EXE", "size": 35146, "date": "1993-02-10", "time": "5:59" }, { "name": "COMP EXE", "size": 13084, "date": "1993-02-10", "time": "5:59" }, { "name": "CV COM", "size": 716, "date": "1993-02-10", "time": "5:59" }, { "name": "EDLIN EXE", "size": 12626, "date": "1993-02-10", "time": "5:59" }, { "name": "EXE2BIN EXE", "size": 8424, "date": "1993-02-10", "time": "5:59" }, { "name": "GRAFTABL COM", "size": 11205, "date": "1993-02-10", "time": "5:59" }, { "name": "JOIN EXE", "size": 16576, "date": "1993-02-10", "time": "5:59" }, { "name": "MIRROR COM", "size": 18201, "date": "1993-02-10", "time": "5:59" }, { "name": "MSHERC COM", "size": 6934, "date": "1993-02-10", "time": "5:59" }, { "name": "PRINTFIX COM", "size": 236, "date": "1993-02-10", "time": "5:59" }, { "name": "GORILLA BAS", "size": 29434, "date": "1993-02-10", "time": "5:59" }, { "name": "REMLINE BAS", "size": 12314, "date": "1993-02-10", "time": "5:59" }, { "name": "NIBBLES BAS", "size": 24103, "date": "1993-02-10", "time": "5:59" }, { "name": "MONEY BAS", "size": 46225, "date": "1993-02-10", "time": "5:59" }, { "name": "MESSAGES TX_", "size": 64577, "date": "1993-02-10", "time": "5:59" } ] } ], "volume": "DISK 5" } }, "desc_file": "README.TXT", "desc_text": "\r\nREADME.TXT\r\n\r\nNOTES ON MS-DOS 6\r\n===========================\r\n\r\nThis file provides important information not included in the\r\nMicrosoft MS-DOS User's Guide or in MS-DOS Help.\r\n\r\nThe following are the major sections of the README.TXT file:\r\n\r\n1. Setup\r\n2. MemMaker and Memory Management\r\n3. Windows\r\n4. Hardware Compatibility with MS-DOS 6\r\n5. Microsoft Programs\r\n6. Third-Party Programs\r\n7. DoubleSpace\r\n8. Resource Kit\r\n\r\nIf the subject you need information on doesn't appear in the\r\nREADME.TXT file, you may find it in one of the following text \r\nfiles included with MS-DOS:\r\n\r\n* NETWORKS.TXT, which describes how to update your network software\r\n to work with MS-DOS 6.\r\n\r\n* CONNECT.TXT, which contains additional notes about Workgroup\r\n Connection.\r\n\r\n* MAIL.TXT, which desribes how to use Microsoft Mail.\r\n\r\nIf you have questions about procedures or commands mentioned\r\nin any of the text files, you will probably find answers in the\r\nMicrosoft MS-DOS User's Guide or, if you have installed MS-DOS 6, \r\nin MS-DOS Help.\r\n\r\nLook through the following table of contents to find the specific\r\ntopic you are looking for. If you are using the MS-DOS Editor to \r\nview this file, you can use the Find command on the Search\r\nmenu to go to the topic you want to read.\r\n\r\n\r\n\r\nThe following topics are discussed in this file:\r\n\r\n1. Notes on Setup\r\n 1.1 You deleted files from the directory that Setup needs\r\n to install the optional programs\r\n 1.2 You need to install MS-DOS manually\r\n2. MemMaker and Memory Management\r\n 2.1 Intel Expanded-Memory Driver (EMM.SYS)\r\n 2.2 When you run Windows, MS-DOS indicates that your \r\n display driver uses the monochrome address range\r\n 2.3 MemMaker does not restart after the \"MemMaker will now\r\n restart your computer to test the new memory configuration\"\r\n screen\r\n 2.4 Running MemMaker with a system that has a batch program called\r\n from the AUTOEXEC.BAT file\r\n 2.5 Undoing MemMaker changes on a system with disk-compression\r\n 2.6 Running MemMaker on a computer with PC-NFS\r\n 2.7 Your computer has an Adaptec controller card, and MemMaker\r\n won't work correctly\r\n 2.8 386MAX (5.11 or Earlier)\r\n 2.9 Optimizing the Order of Programs in CONFIG.SYS and AUTOEXEC.BAT\r\n3. Windows\r\n 3.1 \"Cannot run Windows in standard mode\" Message\r\n 3.2 Your computer uses a Windows 3.0 permanent swap file\r\n4. Hardware Compatibility with MS-DOS 6\r\n 4.1 Compaq EXTDISK.SYS Driver\r\n 4.2 Hardcard\r\n 4.3 Inboard 386/PC\r\n 4.4 Olivetti and AT&T System with a CGA Video Board\r\n 4.5 Toshiba\r\n5. Microsoft Programs\r\n 5.1 Running Backup for MS-DOS under Windows\r\n 5.2 Defrag\r\n 5.3 Microsoft CD-ROM Extensions\r\n6. Third-party Programs\r\n 6.1 Above Board 286 and Above Board Plus Installation\r\n Programs\r\n 6.2 After Dark for DOS (AD-DOS)\r\n 6.3 AutoCAD release 10\r\n 6.4 CodeView\r\n 6.5 Defragment programs\r\n 6.6 Fastback\r\n 6.7 GeoWorks\r\n 6.8 6.6 Lotus 1-2-3 version 3.x with MS-DOS Shell Task Swapper\r\n 6.9 Norton Desktop for Windows 2.0\r\n 6.10 PC Tools\r\n 6.11 PC-Kwik Disk Accelerator\r\n 6.12 Soft-ICE\r\n 6.13 Task Swapper and Asynchronous I/O\r\n 6.14 Ventura Publisher\r\n7. DoubleSpace\r\n 7.1 Installing DoubleSpace If You Use Stacker\r\n 7.2 Installing DoubleSpace If You Use Another Disk-Compression Program\r\n 7.3 Installing DoubleSpace Manually\r\n 7.4 DoubleSpace Setup indicates that your computer is running an\r\n incompatible disk-caching program\r\n 7.5 Your computer runs out of disk space while compressing\r\n a drive\r\n 7.6 Your compressed drive runs out of disk space\r\n 7.7 Your uncompressed drive runs out of disk space \r\n 7.8 DoubleSpace did not compress all of your files because\r\n the drive ran out of disk space\r\n 7.9 DoubleSpace could not convert a Stacker drive because \r\n there was not enough free space\r\n 7.10 DoubleSpace Cannot Convert a Stacker Drive Because\r\n There is Not Enough Free Memory\r\n 7.11 Removing DoubleSpace From Your Computer \r\n 7.12 Your Workgroup Connection persistent drives conflict with your\r\n DoubleSpace drives\r\n 7.13 DoubleSpace and Windows Permanent Swap Files\r\n 7.14 Using Stacker Floppy Disks with DoubleSpace\r\n 7.15 If EXTDISK.SYS displays a warning about drive letters\r\n 7.16 Novell Networks and DoubleSpace\r\n 7.17 Using the DBLSPACE.INI File\r\n 7.18 You Receive the Message \"A CVF is Damaged\" When You Start \r\n Your Computer\r\n 7.19 You Need a Special Device Driver to Use Your Compressed \r\n Startup Drive\r\n 7.20 Defragmenting Uncompressed Drives After Changing File Attributes \r\n 7.21 Files DoubleSpace Cannot Compress\r\n 7.22 DoubleSpace and Microsoft Mail 3.0 .MMF Files\r\n 7.23 Defragmenter Runs Out Of Memory While You Are Compressing a Drive \r\n 7.24 Free Space Requirements for Converting a Stacker Drive \r\n8. MS-DOS Supplemental Disk\r\n\r\n1. NOTES ON SETUP\r\n================\r\n\r\n1.1 You deleted files from the directory that Setup needs\r\n to install the optional programs\r\n---------------------------------------------------------\r\nIf you typed \"setup /e\" at the command prompt, Setup displayed\r\nthe \"Setup did not find the files it needs in the directory\r\nspecified\" message, and you think you deleted the files from\r\nyour hard disk, carry out the following procedure.\r\n\r\n1. Reinstall MS-DOS 6 again.\r\n\r\n2. After Setup is finished, type the following at the command\r\n prompt:\r\n\r\n setup /e\r\n\r\n1.2 You need to install MS-DOS manually\r\n---------------------------------------\r\nIf you need to install MS-DOS manually, carry out the following procedure:\r\n\r\n1. Insert Setup Disk 1 in drive, and restart your computer by pressing\r\n CTRL+ALT+DEL.\r\n\r\n2. After the first screen appears, exit Setup by pressing F3 twice.\r\n\r\n3. To transfer your system files, type the following at the command\r\n prompt:\r\n\r\n sys a: c:\r\n\r\n4. Create a directory on your hard drive for containing your MS-DOS 6 \r\n files.\r\n\r\n5. Copy all the decompressed files on Setup Disk 1 to your MS-DOS\r\n directory.\r\n\r\n6. Use the EXPAND command to decompress the rest of files on your Setup\r\n disks and copy them to your MS-DOS directgory. You must expand the\r\n compressed files one at a time. For example, to decompress the EGA.SY_ \r\n file and copy it to the DOS directory, type the following at the command \r\n prompt:\r\n\r\n a:expand ega.sy_ c:\\dos\\ega.sys \r\n \r\n For more information about the EXPAND command and the location and\r\n extensions of specific files, see the PACKING.LST file on the Setup\r\n disks.\r\n \r\n7. Create startup files in the root of drive C. For more information about\r\n creating your startup files, see the chapter \"Configuring Your System\"\r\n of the Microsoft MS-DOS 6 User's Guide.\r\n\r\n8. Restart your computer by pressing CTRL+ALT+DEL.\r\n \r\n\r\n2. MEMMAKER AND MEMORY MANAGEMENT\r\n=================================\r\n\r\n2.1 Intel Expanded-Memory Driver (EMM.SYS)\r\n------------------------------------------\r\nIf you use Intel's EMM.SYS driver with Aboveboard, use\r\nEMM.SYS version 4.0 revision D or later . If you have an\r\nearlier version, contact Intel for a free upgrade.\r\n\r\n2.2 When you run Windows, MS-DOS indicates that your display \r\n driver uses the monochrome address range\r\n------------------------------------------------------------\r\nIf your computer uses a Windows 3.0 display driver, you need\r\nto modify your SYSTEM.INI file to make the driver compatible\r\nwith the MS-DOS 6 EMM386 memory manager. Carry out the \r\nfollowing procedure:\r\n\r\n1. Open your SYSTEM.INI file by using any text editor.\r\n\r\n2. Find the [386enh] section.\r\n\r\n3. Add a DEVICE= line for the MONOUMB.386 file. For example, if\r\n DOS is your MS-DOS directory, add the following line:\r\n\r\n DEVICE=C:\\DOS\\MONOUMB.386\r\n\r\n4. Save the file.\r\n\r\n5. Restart your computer by pressing CTRL+ALT+DEL.\r\n\r\n6. Run Windows again.\r\n\r\n2.3 MemMaker does not restart after the \"MemMaker will now restart\r\n your computer to test the new memory configuration\" screen\r\n------------------------------------------------------------------\r\nIf your AUTOEXEC.BAT file contains a command (other than the CALL\r\ncommand) that starts a batch program, MemMaker might not restart \r\nafter it displays this screen. If this happens carry out the \r\nfollowing procedure.\r\n\r\n* Type the following at the command prompt:\r\n\r\n find /i \"memmaker\" autoexec.bat >t.bat\r\n\r\n Then type the following at the command prompt:\r\n\r\n t.bat\r\n\r\n MemMaker should restart normally.\r\n\r\n\r\n2.4 Running MemMaker with a system that has a batch program called\r\n from the AUTOEXEC.BAT file\r\n------------------------------------------------------------------\r\nMemMaker does not optimize programs loaded in a batch\r\nprogram called from your AUTOEXEC.BAT file. If any of those \r\nprograms are loaded high, change their command lines to load them\r\nin conventional memory before you run MemMaker.\r\n\r\n2.5 Undoing MemMaker changes on a system with disk-compression \r\n--------------------------------------------------------------\r\nWhen you undo MemMaker changes on a system with third-party \r\ndisk-compression software, you might receive a message instructing \r\nyou to run MemMaker with the /SESSION switch. Ignore this message. \r\nInstead, copy the AUTOEXEC.BAT and CONFIG.SYS files from your host \r\n(uncompressed drive) to your compressed drive. Then restart your \r\ncomputer by pressing CTRL+ALT+DEL.\r\n\r\n2.6 Running MemMaker on a computer with PC-NFS\r\n----------------------------------------------\r\nIf you use PC-NFS network software, carry out the following procedure\r\nbefore you run MemMaker:\r\n\r\n1. Open your MEMMAKER.INF file using any text editor. This file is\r\n in the directory that contains your MS-DOS files.\r\n\r\n2. Add the following line to the file:\r\n\r\n *NET\r\n\r\n3. Save the file, and then run MemMaker.\r\n\r\n2.7 Your computer has an Adaptec controller card, and MemMaker\r\n won't work correctly\r\n-------------------------------------------------------------------\r\nIf MemMaker stop running when you try to optimize your computer's\r\nmemory configuration, and you use the ADAPTEC.SYS driver with your \r\nAdaptec controller card, your computer is probably incompatible \r\nwith MemMaker. Carry out the following procedure to restore your\r\nsystem:\r\n\r\n1. Restart your computer by pressing CTRL+ALT+DEL.\r\n\r\n2. The following text is displayed on your screen:\r\n\r\n Starting MS-DOS...\r\n\r\n While the text is on your screen, press and release the F8 key. \r\n \r\n3. Carry out all the commands in your CONFIG.SYS file by pressing\r\n Y each time your are prompted except when you are prompted for\r\n the EMM386.EXE command. When you are prompted for this command,\r\n press N to bypass it.\r\n\r\n4. When you prompted for your AUTOEXEC.BAT file, press Y to process \r\n it.\r\n\r\n5. Open your CONFIG.SYS by using any text editor. Move the command\r\n for the ADAPTEC.SYS driver so that it appears before the commands\r\n for your HIMEM.SYS and EMM386.EXE files.\r\n\r\n6. Save the file, and then restart your computer by pressing \r\n CTRL+ALT+DEL.\r\n\r\n2.8 386MAX (5.11 or Earlier)\r\n----------------------------\r\nIf you have used the SETVER command to report a different\r\nversion number to a program you are loading into the upper\r\nmemory area with 386LOAD.COM or MAXHI.COM, also use the\r\nSETVER command to report that number to 386LOAD.COM or\r\nMAXHI.COM. For information about the SETVER command, type\r\nHELP SETVER at the command prompt after you have installed\r\nMS-DOS 6.\r\n\r\nThe new version number is reported to all programs loaded by\r\n386LOAD.COM and MAXHI.COM.\r\n\r\nMAXHI.COM programs supplied with versions of 386MAX earlier\r\nthan 5.0 are incompatible with MS-DOS 6.\r\n\r\n\r\n2.9 Optimizing the Order of Programs in CONFIG.SYS and AUTOEXEC.BAT\r\n-------------------------------------------------------------------\r\nIn the \"Making More Memory Available\" chapter of the MS-DOS 6 User's\r\nGuide, the section \"Fine-Tuning Your Memory Configuration\" explains\r\nhow to free additional memory after running MemMaker. The procedure\r\n\"To optimize the order of device drivers and memory-resident programs\"\r\nexplains that you can optimize memory by sorting device drivers \r\nand memory-residents by their MaxSize values.\r\n\r\nTo optimize your system further, follow the steps in that procedure, \r\nbut instead sort the programs by the difference between each program's \r\nMaxSize and FinalSize values. In general, a program with a large difference\r\nbetween its MaxSize and FinalSize values should be loaded before a \r\nprogram with little or no difference between those values.\r\n\r\n\r\n3. WINDOWS\r\n==========\r\n\r\n3.1 \"Cannot run Windows in standard mode\" Message\r\n-------------------------------------------------\r\nIf you have a DEVICE=EMM386.EXE command that includes the\r\nRAM or NOEMS switch in your CONFIG.SYS file, you cannot run\r\nWindows 3.0 in standard mode. Either remove the RAM or NOEMS\r\nswitch or run Windows in real or enhanced mode. (If you\r\nremove RAM or NOEMS, you won't be able to load programs and\r\ndevice drivers into the upper memory area. If you include\r\nRAM or NOEMS, you won't be able to run Windows in standard\r\nmode.)\r\n\r\nNOTE: Using EMM386 may reduce the amount of extended memory\r\navailable to Windows and cause Windows to try to start in\r\nstandard mode. To prevent this, reduce the amount of\r\nextended memory that other device drivers use. For example,\r\nif you are using SMARTDrive, try setting the MinCacheSize\r\nparameter to 0.\r\n\r\n\r\n3.2 Your computer uses a Windows 3.0 permanent swap file \r\n--------------------------------------------------------\r\nIf your computer uses a Windows 3.0 permanent swap file, you\r\nneed to run the SPATCH.BAT program to make the swap file\r\ncompatible with MS-DOS 6. To do so, carry out the following\r\nprocedure:\r\n\r\n1. Make sure the SPATCH.BAT program is on your hard disk. If it\r\n isn't, copy it from the Setup disks. For the location of the\r\n file on the Setup disk, view the PACKING.LST file on Setup Disk\r\n 1.\r\n\r\n2. Type the following at the command prompt:\r\n\r\n spatch [drive]:[path]swapfile.exe\r\n\r\n For the drive and path parameters, specify the location of\r\n your SWAPFILE.EXE file.\r\n\r\n3. Follow the instructions on your screen.\r\n\r\n The program modifies the SWAPFILE.EXE for use with MS-DOS 6\r\n and saves a backup copy as SWAPFILE.SAV. After you have confirmed\r\n the file works correctly, you can delete the SWAPFILE.SAV file.\r\n\r\n\r\n4. HARDWARE COMPATIBILITY WITH MS-DOS \r\n=====================================\r\n\r\n4.1 Compaq EXTDISK.SYS Driver\r\n-----------------------------\r\nCompaq EXTDISK.SYS driver version 3.00 or later is\r\ncompatible with MS-DOS 6. If you have version less\r\nthan 3.00, contact your vendor for an upgrade.\r\n\r\n4.2 Hardcard\r\n------------\r\na) Hardcard II\r\n\r\n If you can't use Plus Development Hardcard II or Hardcard\r\n II XL when running EMM386.EXE, specify the exclude (x=)\r\n switch to prevent EMM386 from conflicting with the card's\r\n BIOS address.\r\n \r\n See your Hardcard II manual to determine which address\r\n space to exclude. Type HELP EMM386.EXE at the command\r\n prompt for more information about the exclude switch.\r\n \r\nb) Hardcard 40 or Passport\r\n \r\n If you are using Hardcard 40 or a Passport removable\r\n disk, and you have a DEVICE command for PLUSDRV.SYS in\r\n your CONFIG.SYS file, carry out the following procedure\r\n before upgrading to MS-DOS 6:\r\n \r\n 1. Disable or remove the DEVICE command for PLUSDRV.SYS\r\n command line in your CONFIG.SYS file.\r\n 2. Run MS-DOS 6 Setup.\r\n 3. Reenable or return the DEVICE command for PLUSDRV.SYS\r\n in your CONFIG.SYS file. Make it the last line in the\r\n file.\r\n\r\n4.3 Inboard 386/PC\r\n-------------------\r\nThe Inboard 386/PC is incompatible with the EMM386 memory\r\nmanager that comes with MS-DOS 6. Do not load EMM386 in your\r\nCONFIG.SYS file and do not run MemMaker.\r\n\r\n4.4 Olivetti and AT&T Systems with a CGA Video Board\r\n----------------------------------------------------\r\nAn Olivetti or AT&T system with a CGA video board may not scroll\r\ncorrectly. Add the /S switch to the DEVICE=ANSI.SYS command\r\nin your CONFIG.SYS file.\r\n\r\n4.5 Toshiba\r\n-------------------\r\nToshiba T3100SX computer's suspend/resume feature is\r\nincompatible with EMM386.EXE. Either disable the feature or\r\ndo not use EMM386.EXE.\r\n\r\nIf you used the MS-DOS 5.0 version of EMM386 before you ran\r\nSetup, and you use the Power Management function, you should not use \r\nthe new version of EMM386. Instead, you should use the old version,\r\nwhich was saved as EMM38650.EXE in your DOS directory.\r\n\r\n5. MICROSOFT PROGRAMS\r\n\r\n5.1 Running Backup for MS-DOS under Windows\r\n-------------------------------------------\r\nIt is recommended that you don't run Backup for MS-DOS under Windows.\r\nHowever, if you do, and if your system is not configured correctly, Backup \r\nmay display the following symptoms:\r\n\r\no Backup appears to stop running--for example, the clock moves, but\r\n there is no disk activity.\r\n\r\no Backup reports problems while testing the second floppy disk during\r\n the compatibility test. For example, it might displays a \"Diskette\r\n not properly seated\" message or it might ask for Disk 1 repeatedly.\r\n\r\no Windows displays a message that DMA buffer size needs to be increased.\r\n\r\no Backup quits unexpectedly.\r\n\r\nYou can correctly configure your system by carrying out the following procedure.\r\n\r\n1. Open your CONFIG.SYS and make it sure contains the following command\r\n lines:\r\n\r\n FILES=30\r\n BUFFERS=30\r\n STACKS-9,256\r\n\r\n2. Open your SYSTEM.INI file by choosing the Run command from Program\r\n Manager, typing SYSEDIT, and selecting the SYSTEM.INI file.\r\n\r\n3. Locate the [386enh] section.\r\n\r\n4. Add the following line to the section:\r\n\r\n DMABufferSize=32\r\n\r\n5. When you run Backup, make sure that you specify with the Settings \r\n command from the Control menu that Backup run with the Exclusive \r\n and Full Screen options. (If you're running Backup full screen, \r\n press ALT+SPACEBAR to choose the Control menu.)\r\n\r\n5.2 Defrag\r\n----------\r\nIf you run Defrag and MS-DOS still displays out-of-memory messages after\r\nyou have followed the procedures in \"An MS-DOS program displays\r\nan out-of-memory message\" in the chapter \"Diagnosing and Solving\r\nProblems\" of the Microsoft MS-DOS User's Guide, your computer\r\nmight have too many files for Defrag to reorganize the files on\r\nyour hard disk. For Defrag to work correctly, you might need to \r\ndelete some files or move them to a floppy disk or a network drive.\r\n\r\n\r\n5.3 Microsoft CD-ROM Extensions\r\n-------------------------------\r\nUse the MSCDEX.EXE file that comes wtih MS-DOS 6.\r\n\r\nIf you load MSCDEX.EXE with a batch file or program,\r\nmake sure it loads the MSCDEX.EXE file that comes with \r\nMS-DOS 6. The MS-DOS Setup program copies the file\r\nto the directory that contains your MS-DOS files.\r\n\r\n\r\n6. THIRD-PARTY PROGRAMS\r\n=======================\r\n\r\n6.1 Above Board 286 and Above Board Plus Installation\r\n Programs\r\n-----------------------------------------------------\r\n\r\nCAUTION: The Intel Above Board installation program that\r\n shipped before May 1989 tests extended memory in a\r\n way that can corrupt extended memory.\r\n\r\nBefore using an Above Board installation program prior to\r\nMay 1989, make sure you haven't loaded software such as\r\nSMARTDrive or RAMDrive that uses extended memory. After the\r\nAbove Board has been installed, other software using\r\nextended memory is unaffected.\r\n\r\n6.2 After Dark for DOS (AD-DOS)\r\n-------------------------------\r\nIf you run After Dark for DOS (AD-DOS) at the same time you \r\nare running programs that use DPMI, you may have problems with \r\nMS-DOS--for example, your system may halt suddenly or you may \r\nreceive \"packed-file corrupt\" messages. Examples of programs\r\nthat use DPMI are Microsoft MASM61, C7, and FoxPro25.\r\n\r\n6.3 AutoCAD release 10\r\n---------------------\r\nTo run AutoCAD release 10 for MS-DOS, contact Autodesk for a\r\npatch file. No patch is needed for AutoCAD386.\r\n\r\n6.4 CodeView\r\n-----------\r\nCAUTION: Using versions 3.0 to 3.13 of the CodeView CV.EXE\r\nfile may cause data loss if your system has a 80386 memory\r\nmanager (such as EMM386.EXE) and device drivers or programs\r\nthat use extended memory. To determine which version you\r\nhave, type CV.EXE at the command prompt.\r\n\r\nThis problem has been fixed in CodeView version 3.14. Call\r\nMicrosoft C Support to get this version.\r\n\r\n6.5 Defragment programs\r\n-----------------------\r\nThird-party defragmentation programs, such as PC Tools COMPRESS or \r\nNorton SpeedDisk, are currently incompatible with DoubleSpace\r\ndrives. Do not use them. When running MS-DOS 6, use the \r\nDEFRAG command from the command prompt or the Defragment command \r\nfrom DoubleSpace. These commands are fully integrated with MS-DOS 6.\r\n\r\n\r\n6.6 Fastback\r\n-------------\r\nTo ensure that you don't lose data, if you have a version \r\nof Fifth Generation Systems Fastback earlier than 3.0, you \r\nmust use the LOADFIX command before running Fastback or the \r\nFastback installation program. Type the following:\r\n\r\nLOADFIX FB.EXE\r\n\r\nor\r\n\r\nLOADFIX FBINSTAL.EXE\r\n\r\nFor information about the LOADFIX command, type HELP LOADFIX\r\nat the command prompt.\r\n\r\n6.7 GeoWorks\r\n-------------\r\nTo install GeoWorks version 1.2 on MS-DOS 6, you must use the\r\nSETVER command to change the MS-DOS version for the GeoWorks \r\nsetup program. Carry out the following procedure:\r\n\r\n1. Before you run GeoWorks Setup, type the following at the \r\n command prompt:\r\n\r\n setver setup.exe 5.00\r\n\r\n2. Restart your computer by pressing CTRL+ALT+DEL.\r\n\r\n3. Run the GeoWorks setup program.\r\n\r\n4. After you have installed GeoWorks, type the following at \r\n the command prompt:\r\n \r\n setver setup.exe /delete\r\n \r\n5. Restart your computer by pressing CTRL+ALT+DEL.\r\n\r\nIf you have a version of GeoWorks (PC/GEOS) earlier than\r\n1.2, use the SETVER command to report version number 4.01 to\r\nthe GEOS.EXE file. Type the following:\r\n\r\nSETVER GEOS.EXE 4.01\r\n\r\nDo not run the installation program for GeoWorks Ensemble\r\nwhen MS-DOS Shell Task Swapper is active.\r\n\r\nUse the Exclusive Tasking option when running GeoWorks\r\nEnsemble with Windows.\r\n\r\n\r\n6.8 Lotus 1-2-3 version 3.x with MS-DOS Shell Task Swapper\r\n-----------------------------------------------------------\r\nIf you use Lotus 1-2-3 version 3.x with the Task Swapper\r\nin MS-DOS Shell, do not specify the NOVCPI switch with the\r\nEMM386.EXE command in your CONFIG.SYS file.\r\n\r\n6.9 Norton Desktop for Windows 2.0\r\n----------------------------------\r\nSetup modifies Norton Desktop for Windows by adding a\r\nsecond Tools menu which contains Backup and Antivirus commands\r\n(if you installed these Windows programs), as well as a \r\nDoubleSpace Info command. \r\n\r\nIf you installed the Anti-Virus, Backup, and Undelete \r\nfor Windows, you can add to Norton Desktop a Microsoft \r\nTools group containing the programs' icons. Carry out Procedure 1 \r\nif you have a group open and want to add to it the\r\nMicrosoft Tools group. Carry out Procedure 2 if you don't have a \r\ngroup open.\r\n\r\nProcedure 1 To add the Microsoft Tools Group if the group window\r\n is open:\r\n\r\n* Drag the file C:\\DOS\\WNTOOLS.GRP and drop it on the group window.\r\n\r\nProcedure 2 To add the Microsoft Tools Group if the the group window\\\r\n is not open:\r\n\r\n1. Select the group into which you want the Microsoft Tools group to\r\n go--for example, the Main or Quick Access group.\r\n\r\n2. From Norton Desktop for Windows, choose New from the File menu.\r\n\r\n3. In the New dialog box, select Group as the Type.\r\n\r\n4. In the Group File Name box, type the path to the WNTOOLS.GRP file. \r\n This file is in the directory that contains your MS-DOS files. For\r\n example, if this directory is C:\\DOS, type the following:\r\n\r\n C:\\DOS\\WNTOOLS.GRP\r\n\r\n5. Choose OK.\r\n\r\n6.10 PC Tools\r\n------------\r\nThe FORMAT command of PC Tools version 7.1 conflicts with\r\nMS-DOS 6. You should use the FORMAT.EXE command that comes \r\nwith MS-DOS 6.\r\n\r\nThe COMPRESS command of PC Tools version 6.0 is incompatible\r\nwith DoubleSpace. Do not use it. When running MS-DOS 6, use the \r\nDEFRAG command from the command prompt or the Defragment command \r\nfrom DoubleSpace. These commands are fully integrated with MS-DOS 6.\r\n\r\n6.11 PC-Kwik Disk Accelerator\r\n-----------------------------\r\nDo not load versions of Multisoft PC-Kwik Disk Accelerator\r\nearlier than 2.0 into the upper memory area.\r\n\r\n6.12 Soft-ICE\r\n-------------\r\nWhen using Nu-Mega Soft-ICE, load it before loading other\r\ndrivers. Otherwise, you may lose data stored in extended\r\nmemory by drivers such as SMARTDrive.\r\n\r\nIn addition, when running Soft-ICE and SMARTDrive, do not\r\npress CTRL+ALT+DEL until you are sure that your computer's\r\nsoftware has finished writing to disk. Otherwise, you might\r\nlose data.\r\n\r\n6.13 Task Swapper and Asynchronous I/O\r\n--------------------------------------\r\nSome programs that perform asynchronous communications are\r\nincompatible with MS-DOS Shell Task Swapper. Terminal-\r\nemulation software (such as SmartCom and Procomm Plus) and\r\nserver/client software (such as Laplink and Blast) are\r\nasynchronous communications programs. If you can't use an\r\nasynchronous program with Task Swapper, contact your vendor\r\nfor more information, or disable Task Swapper.\r\n\r\n6.14 Ventura Publisher\r\n----------------------\r\nIf you can't start a version of Ventura Publisher, make sure your \r\nVentura Publisher directory is within the first 70 characters of \r\nthe PATH command in your AUTOEXEC.BAT file.\r\n\r\n\r\n7. DOUBLESPACE \r\n==============\r\n \r\n7.1 Installing DoubleSpace If You Use Stacker\r\n---------------------------------------------\r\nIf you use Stacker disk-compression software, you can install \r\nDoubleSpace and automatically convert your compressed drives \r\nto DoubleSpace format.\r\n\r\nNote: If your version of Stacker is 1.1 or you compressed your drive\r\nwith a 4K cluster size, you cannot automatically convert your Stacker\r\ndrive; you must convert it manually, as described in the procedure\r\n\"Installing DoubleSpace Manually.\"\r\n\r\nTo install DoubleSpace, carry out the folllowing procedure.\r\n\r\n1. Type the following at the command prompt:\r\n\r\n dblspace\r\n\r\n2. Follow the instructions on your screen. DoubleSpace Setup will\r\n prompt you to convert your Stacker drives.\r\n\r\n3. After DoubleSpace Setup converts your Stacker drives, DoubleSpace\r\n informs you that there are some Stacker files you might want to \r\n delete from your uncompressed drive. The following are files and\r\n directories you can delete:\r\n\r\n CONFIG.*\r\n AUTOEXEC.STC\r\n STACKER.LOG\r\n COMMAND.COM\r\n Your Stacker directory and all its files\r\n Your Windows, MS-DOS, and OLD_DOS.x directories, if any, and all\r\n their files\r\n\r\n NOTE:\r\n You can use the DELTREE command to delete directories and all \r\n their commands.\r\n\r\n7.2 Installing DoubleSpace If You Use Another Disk-Compression Program\r\n----------------------------------------------------------------------\r\nIf your computer uses Stacker disk-compression software, see\r\nsection 7.1.\r\n\r\nIf your computer uses XtraDrive disk compression, use its \r\nuninstallation program to remove the compression, and then\r\ninstall DoubleSpace.\r\n\r\nIf your computer uses another disk-compression program,\r\nyou can install DoubleSpace manually by following the procedure\r\nin the following section.\r\n\r\n7.3 Installing DoubleSpace Manually\r\n-----------------------------------\r\nTo convert your disk-compression software to DoubleSpace manually:\r\n\r\n1. Install MS-DOS 6 if you haven't already done so.\r\n\r\n2. Use Microsoft Backup to back up the files on your hard disk.\r\n\r\n3. Insert Setup Disk 1 in drive A, and restart your computer\r\n by pressing CTRL+ALT+DEL. When the first screen appears, press\r\n F3 twice to exit Setup.\r\n\r\n Or, create a startup disk by inserting Setup Disk in drive B,\r\n and typing B:SETUP /F. When prompted, choose to install \r\n MS-DOS to the floppy disk in drive A. After Setup is finished, \r\n restart your computer by inserting the startup disk in drive A \r\n and pressing CTRL+ALT+DEL.\r\n\r\n4. Use the format command to format the drive that contains the \r\n file that stores all of your compressed files. If you don't know\r\n where this file is located, see your disk-compression\r\n documentation.\r\n \r\n If you are reformatting drive C, include the /S switch to transfer \r\n your system files, as in the following example:\r\n\r\n format c: /s\r\n\r\n NOTE\r\n If you don't format drive C, remove from your CONFIG.SYS and\r\n AUTOEXEC.BAT files any commands that were used by your disk-\r\n compression software.\r\n\r\n5. If you formatted drive C, make sure Setup Disk 1 is in drive A \r\n or B, and type A:SETUP or B:SETUP at the command prompt.\r\n\r\n Follow the instructions on your screen.\r\n\r\n6. Install DoubleSpace by typing DBLSPACE at the command prompt. \r\n Follow the instructions on your screen. \r\n\r\n For more information about DoubleSpace, see the chapter \r\n \"Freeing Disk Space\" of the Microsoft MS-DOS User's Guide.\r\n\r\n7. Restore the files you backed up.\r\n\r\n\r\n7.4 DoubleSpace Setup indicates that your computer is running an\r\n incompatible disk-caching program\r\n---------------------------------------------------------------- \r\nIf DoubleSpace Setup displays a message indicating your computer\r\nis running an incompatible disk-caching program, carry out the\r\nfollowing procedure to install DoubleSpace:\r\n\r\n1. Open your CONFIG.SYS file by typing EDIT C:\\CONFIG.SYS\r\n at the command prompt.\r\n\r\n2. Delete the line that contains the device command that loads\r\n your disk-caching program.\r\n\r\n3. Make sure you have a line for the MS-DOS 6 SMARTDRV program. \r\n For example, if C:\\DOS is your MS-DOS directory, add the \r\n following line:\r\n\r\n C:\\DOS\\SMARTDRV.EXE /DOUBLE_BUFFER\r\n\r\n4. Save the file.\r\n\r\n5. Open your AUTOEXEC.BAT file.\r\n\r\n6. Make sure you have a line for the MS-DOS 6 SMARTDRV program. \r\n For example, if DOS is your MS-DOS directory, add the \r\n following line:\r\n\r\n C:\\DOS\\SMARTDRV.EXE /L\r\n\r\n7. Save the file, and restart your computer by pressing\r\n CTRL+ALT+DEL.\r\n\r\n8. Run DoubleSpace again.\r\n \r\n7.5 You attempt to mount a compressed floppy disk, and MS-DOS\r\n displays an error message\r\n-------------------------------------------------------------\r\nIf you have not installed DoubleSpace on your hard disk, and you\r\nattempt to mount a compressed floppy disk, MS-DOS displays \r\nthe following message:\r\n\r\n There are no more drive letters reserved \r\n for DoubleSpace to use. To add more drive letters, \r\n choose the Options command from the Tools menu.\r\n\r\nYou must load DBLSPACE.BIN and create a DBLSPACE.INI file to mount\r\ncompressed floppy disks if you have not installed DoubleSpace on your\r\nhard disk.\r\n\r\nTo correct this problem:\r\n\r\n1. Create a C:\\DBLSPACE.INI file by using any text editor. \r\n DBLSPACE.INI should contain the following two lines:\r\n\r\n MaxRemovableDrives=2\r\n LastDrive=F\r\n\r\n Note: LastDrive= must be set to one letter higher than your last\r\n logical drive letter. For example, if your last drive is E:, \r\n use LastDrive=F in your DBLSPACE.INI file.\r\n\r\n2. Copy DBLSPACE.BIN from your MS-DOS directory to the root directory of\r\n your startup drive. For example, type the following at the command\r\n prompt:\r\n\r\n copy c:\\dos\\dblspace.bin c:\\\r\n\r\n3. Restart the computer.\r\n\r\n4. You can now mount the compressed disk in your floppy drive. For\r\n example, if the disk is in drive A:, type the following at the\r\n command prompt:\r\n\r\n dblspace /mount a:\r\n \r\n\r\n7.6 Your compressed drive runs out of disk space\r\n------------------------------------------------\r\n\r\nIf your compressed drive runs out of free disk space, you can\r\nuse the following techniques to free some space on that drive:\r\n\r\n * Specify a higher estimated compression ratio for that drive.\r\n * Enlarge that drive.\r\n * Carry out the DEFRAG command on that drive.\r\n\r\nThe rest of this section explains each technique.\r\n\r\n\r\nSpecifying A Higher Estimated Compression Ratio\r\n\r\nIf a compressed drive's estimated compression ratio is too small, \r\nMS-DOS might report that there is no more free space on that drive,\r\nwhen some space is in fact available. (Raising the estimated compression\r\nratio is most effective if the files you are trying to store are highly \r\ncompressible. It will have no effect if the drive really is out of space.)\r\n\r\nTo specify a larger estimated compression ratio:\r\n\r\n1. Start the DoubleSpace program by typing DBLSPACE at the command\r\n prompt.\r\n \r\n2. Select the compressed drive you want to change, and then choose \r\n the Change Ratio command from the Drive menu. \r\n \r\n DoubleSpace displays the Change Compression Ratio dialog box. \r\n\r\n3. Specify a larger compression ratio, and then choose OK. For more \r\n information, choose the Help button.\r\n\r\nYou can also change the estimated compression ratio from the command prompt. \r\nFor more information, type HELP DBLSPACE /RATIO at the command prompt.\r\n\r\n\r\nEnlarging a Compressed Drive \r\n\r\nYou can enlarge a compressed drive to make more space available on it.\r\nEnlarging a compressed drive uses free space on the uncompressed drive\r\n(the host drive). \r\n\r\nTo enlarge the compressed drive:\r\n\r\n1. Start the DoubleSpace program by typing DBLSPACE at the command prompt.\r\n\r\n2. Select the compressed drive you want to enlarge, and then choose\r\n the Change Size command from the Drive menu.\r\n\r\n DoubleSpace displays the Change Size dialog box. The New Free Space\r\n line shows how much free space the compressed and uncompressed drives \r\n will have if you choose OK. \r\n \r\n3. Specify a smaller number for the New Free Space on the uncompressed \r\n drive. Notice that as you change this number, DoubleSpace adjusts\r\n the New Free Space amount for the compressed drive. When the New Free \r\n Space amount for both drives appears the way you want, choose OK. \r\n\r\n DoubleSpace enlarges the drive.\r\n\r\n\r\nCarrying Out the DEFRAG Command on the Compressed Drive\r\n\r\nSometimes, you can free additional space on a compressed drive by\r\ncarrying out the DEFRAG command on it. Although defragmenting files \r\ndoes not free space on an uncompressed drive, it can sometimes free \r\nspace on a compressed drive.\r\n\r\nTo carry out the DEFRAG command on the compressed drive:\r\n\r\n1. Start the Defrag program by typing DEFRAG at the command prompt.\r\n \r\n2. When the Defrag program starts, select the compressed drive, and \r\n then choose OK. \r\n\r\n3. Choose the Optimization Method command from the Optimize menu.\r\n Defrag displays the Select Optimization Method dialog.\r\n\r\n4. Select Full Optimization, and then choose OK.\r\n\r\n5. Choose the Begin Optimization command from the Optimize menu. \r\n Defrag optimizes the compressed drive. (This process optimizes the\r\n way the compressed drives' compressed volume file is stored on\r\n your hard disk.)\r\n \r\n When Defrag finishes optimizing, it starts DoubleSpace to defragment \r\n the way files are stored on the compressed drive. During this \r\n extra optimization step, DoubleSpace frees as much space on\r\n the drive as possible.\r\n\r\n6. To quit the Defrag program, Choose Exit from the Optimize menu.\r\n\r\n\r\n7.7 Your uncompressed drive runs out of disk space\r\n--------------------------------------------------\r\n\r\nIf your uncompressed drive (host drive) runs out of free disk space, you \r\ncan enlarge it by reducing the size of any compressed drives that are\r\nstored on that uncompressed drive. Of course, this will reduce the \r\namount of free space on the compressed drive(s).\r\n\r\nTo enlarge the uncompressed drive (host drive):\r\n\r\n1. Start the DoubleSpace program by typing DBLSPACE at the command prompt.\r\n\r\n2. Select the compressed drive whose size you want to reduce, and then\r\n choose the Change Size command from the Drive menu. (You need to select\r\n a compressed drive that is stored on the uncompressed drive that's\r\n out of space. To find out which compressed drives are stored\r\n on that uncompressed drive, type DBLSPACE /LIST at the command prompt.)\r\n\r\n DoubleSpace displays the Change Size dialog box. The New Free Space\r\n line shows how much free space the compressed and uncompressed drives \r\n will have if you choose OK. \r\n \r\n3. Specify a larger number for the New Free Space on the uncompressed \r\n drive. Notice that as you change this number, DoubleSpace adjusts\r\n the New Free Space amount for the compressed drive. When the New Free \r\n Space amount for both drives appears the way you want, choose OK. \r\n\r\n DoubleSpace reduces the size of the compressed drive, which makes\r\n more free space available on the corresponding uncompressed drive. \r\n\r\n\r\n7.8 DoubleSpace did not compress all of your files because\r\n the drive ran out of disk space\r\n----------------------------------------------------------\r\nIf DoubleSpace indicates that it could not compress some\r\nof your files because there was not enough disk space, carry\r\nout the following procedure.\r\n\r\n1. Type DBLSPACE at the command prompt.\r\n\r\n2. To determine which drive is your uncompressed drive, choose\r\n Info from the Drive menu. Then choose Exit from the Drive\r\n menu.\r\n\r\n3. Back up to floppy disks the files that were left uncompressed\r\n on the uncompressed drive.\r\n\r\n4. Delete the files that were left uncompressed on the uncompressed\r\n drive.\r\n\r\n5. Type DBLSPACE at the command prompt.\r\n\r\n6. Choose Change Size from the Drive menu.\r\n\r\n7. To increase the size of your compressed drive, decrease the size\r\n of your uncompressed drive. Choose OK.\r\n\r\n7. Choose Exit from the Drive menu, and copy the backed-up files\r\n to your compressed drive. If you run out of space again, repeat\r\n steps 5 through 7 until the compressed drive is large enough.\r\n\r\n\r\n7.9 DoubleSpace could not convert a Stacker drive because \r\n there was not enough free space\r\n---------------------------------------------------------\r\nDoubleSpace indicates how much free space needs to be free\r\non your startup or uncompressed drive. Make a note of this\r\namount. Then carry out the following procedure:\r\n\r\n1. Type the following at the command prompt:\r\n\r\n chkdsk drive:\r\n\r\n For the drive parameter, type the drive letter of your\r\n uncompressed drive. A line similar to the following should\r\n appear on your screen:\r\n\r\n 20386 bytes available on disk\r\n\r\n2. Delete unnecessary files or move files to another drive until \r\n you have enough free disk space. You might want to back up\r\n the files before you delete them.\r\n\r\n IMPORTANT\r\n Do not delete your COMMAND.COM, AUTOEXEC.BAT, or CONFIG.SYS\r\n files, your hidden Stacker or system files, or STACKER.COM \r\n and SSWAP.COM files in your Stacker directory. If you cannot \r\n delete enough unnecessary files, use the SDEFRAG /G command to\r\n make more uncompressed space available. Or contact your disk-\r\n compression software vendor.\r\n\r\n3. Run DoubleSpace again.\r\n\r\n\r\n7.10 DoubleSpace Cannot Convert a Stacker Drive Because\r\n There is Not Enough Free Memory\r\n-------------------------------------------------------\r\nIf DoubleSpace displays a message that it cannot convert\r\nStacker because there is not enough free memory, carry out\r\nthe procedures in \"An MS-DOS-based program displays an\r\nout-of-memory message\" in the chapter \"Diagnosing and Solving\r\nProblems\" of the Microsoft MS-DOS 6 User's Guide. \r\n\r\nIMPORTANT\r\nIn procedure 2, make sure not to bypass any commands that\r\nenable access to your Stacker drives. For example, don't\r\nbypass the DEVICE commands that load the STACKER.COM and \r\nSSWAP.COM commands.\r\n\r\n\r\n7.11 Removing DoubleSpace From Your Computer\r\n--------------------------------------------\r\nThere is no method for automatically removing DoubleSpace.\r\nYou can only remove it manually. To do so, carry out the \r\nfollowing procedure:\r\n\r\n1. Back up the files on the compressed drive. If you're using\r\n a backup program on the compressed drive, make sure the \r\n program files are on another drive or are on a floppy disk.\r\n \r\n2. Type DBLSPACE at the command prompt.\r\n\r\n3. Choose the Info command from the Drive menu. Note on which\r\n uncompressed drive the compressed drive is stored.\r\n\r\n4. Copy the COMMAND.COM file from your compressed drive to the root of \r\n your uncompressed drive.\r\n\r\n5. To delete your DoubleSpace files, make your uncompressed drive current,\r\n and then type the following at the command prompt:\r\n \r\n deltree dblspace.*\r\n\r\n6. Restart your computer by pressing CTRL+ALT+DEL at the command\r\n prompt.\r\n\r\n7. Restore your backed-up files.\r\n \r\n After restoring your files, you may want to delete the command in\r\n your CONFIG.SYS that loads the DBLDPACE.SYS driver.\r\n\r\n\r\n7.12 Your Workgroup Connection persistent drives conflict with your\r\n DoubleSpace drives\r\n-------------------------------------------------------------------\r\nIf you did not load your network before running DoubleSpace Setup,\r\nyou might have a conflict between your Workgroup Connection \r\npersistent drives and your DoubleSpace drives. Symptoms of this\r\nproblem are:\r\n\r\n* You cannot get access to the uncompressed drive that contains\r\n your compressed drive. Instead, what should be the uncompressed\r\n drive is a network drive.\r\n\r\n* When you type DBLSPACE at the command prompt, DoubleSpace displays\r\n the \"A network drive has been connected using drive letter X\"\r\n message.\r\n\r\nTo remedy this problem, carry out the following procedure:\r\n\r\n1. Type the following at the command prompt:\r\n\r\n net use /p:clear\r\n\r\n2. Restart your computer by pressing CTRL+ALT+DEL.\r\n\r\n You will need to reestablish your network connections. Make sure\r\n not to use the drive letter of your uncompressed drive.\r\n \r\n\r\n7.13 DoubleSpace and Windows Permanent Swap Files\r\n-------------------------------------------------\r\nWhen you install DoubleSpace, it checks for the existence of a Windows\r\npermanent swap file. If DoubleSpace finds a permanent swap file, \r\nit moves the file to your uncompressed drive.\r\n\r\nIf you install Windows after installing DoubleSpace, or if you use \r\nControl Panel to change the location of your permanent swap file, your\r\nswap file might end up being located on a compressed drive. (When you \r\nspecify a drive for your permanent swap file, Windows allows you to\r\nchoose a compressed drive.)\r\n\r\nIf your Windows permanent swap file is located on a compressed drive, then \r\nWindows displays the message \"The permanent swap file is corrupt\" when it\r\nstarts. \r\n\r\nTo solve this problem: \r\n\r\n1. At the \"Permanent swap file is corrupt\" screen, type Y in response \r\n to the question \"Do you want to delete this swap file?\", and \r\n then press ENTER. \r\n\r\n2. After Windows starts, open Control Panel, and then double-click the 386\r\n Enhanced icon.\r\n\r\n3. Choose the Virtual Memory button.\r\n\r\n Windows displays a dialog box saying that a corrupt swap file was found,\r\n and asks if you want to set the file's length to zero.\r\n\r\n4. Choose the Yes button. Windows displays another Virtual Memory dialog box.\r\n\r\n5. Choose the Change button. Windows displays swap-file settings.\r\n\r\n6. In the Drive list box, select a drive that is not compressed. In the\r\n Type list box, select \"Permanent.\"\r\n\r\n If your uncompressed drive does not have enough free space to create a \r\n permanent swap file, create a temporary swap file on either your \r\n compressed or uncompressed drives. (For information about freeing \r\n space on your uncompressed drive, see the topic \"Your uncompressed \r\n drive is out of disk space\" later in this file.)\r\n\r\n When you have finished specifying swap-file settings, choose OK twice.\r\n Windows displays a dialog box asking if you want to restart Windows now.\r\n \r\n7. Choose the Restart Windows button. \r\n\r\n\r\n7.14 Using Stacker Floppy Disks with DoubleSpace\r\n------------------------------------------------\r\nIf you have floppy disks that were compressed by using Stacker,\r\nyou must convert them to DoubleSpace format in order to use them\r\nwith DoubleSpace.\r\n\r\nWhen DoubleSpace Setup converts your Stacker drives to DoubleSpace \r\nformat, it also converts any compressed floppy disks or other\r\nremovable media that are currently mounted. After you have completed \r\nDoubleSpace Setup, you can convert other floppy disks and removable \r\nmedia from Stacker to DoubleSpace format by using the Convert Stacker \r\ncommand.\r\n\r\nIf a compressed floppy disk contains at least .9 MB of free space, you can \r\nconvert it to DoubleSpace format by choosing the Convert Stacker option \r\nfrom the Tools menu in DoubleSpace, or by typing DBLSPACE /CONVSTAC \r\nat the MS-DOS command prompt.\r\n\r\nIf a floppy disk contains less than .9 MB of free space, you can convert it\r\nto DoubleSpace format manually.\r\n\r\nTo manually convert a Stacker compressed floppy disk to DoubleSpace:\r\n\r\n1. Make sure the STACKER.COM file is on your hard drive. If it isn't,\r\n copy it to your hard drive from your Stacker disk.\r\n\r\n2. Open your CONFIG.SYS file by using any text editor, and add a \r\n DEVICE command for your STACKER.COM file. At the end of the command\r\n line add a \"@\" character. For example, the command line should look\r\n like the following:\r\n\r\n c:\\stacker\\stacker.com @\r\n\r\n3. Remove disks from all floppy disk drives, and restart your computer \r\n by pressing CTRL+ALT+DEL.\r\n\r\n4. Insert the Stacker floppy into a floppy disk drive. Then use the \r\n STACKER command to mount the floppy disk. For example, if the floppy\r\n disk is in drive A, and the STACKER.COM file is in your STACKER\r\n directory, type the following at the command prompt:\r\n\r\n c:\\stacker\\stacker a:\r\n\r\n5. Move files from the floppy disk to another drive until you have \r\n enough free space on the floppy disk.\r\n\r\n6. Remove the DEVICE command for STACKER.COM from your\r\n CONFIG.SYS file.\r\n\r\n7. Remove disks from all floppy disk drives, and restart your computer \r\n by pressing CTRL+ALT+DEL.\r\n\r\n8. Run DoubleSpace again, and choose to convert the Stacker floppy\r\n disk.\r\n\r\n\r\n7.15 If EXTDISK.SYS displays a warning about drive letters\r\n----------------------------------------------------------\r\nIf you use DoubleSpace and your CONFIG.SYS file loads the EXTDISK.SYS \r\ndevice driver, EXTDISK.SYS displays the following message when it loads:\r\n\r\n WARNING: EXTDISK.SYS is not the first device driver to assign drive \r\n letters. Physical hard drive letters will not be contiguous.\r\n\r\nThe EXTDISK.SYS driver still works properly. It displays this message\r\nbecause it expects to be the first module to assign drive letters,\r\nbut since DBLSPACE.BIN loads before the CONFIG.SYS file and assigns\r\nsome drive letters, EXTDISK.SYS is no longer first. (EXTDISK.SYS \r\ndisplays the message regardless of when the DBLSPACE.SYS device \r\ndriver is loaded in the CONFIG.SYS file.)\r\n\r\n\r\n7.16 Novell Networks and DoubleSpace\r\n------------------------------------\r\nWhen you load netx.com, it establishes a network drive \r\nconnection using the drive letter that follows the drive \r\nletter specified with the LASTDRIVE command in your \r\nCONFIG.SYS file. This also applies to any of the following \r\nfiles:\r\n\r\nNET5.COM\r\nBNETX.COM\r\nBNETX.EXE\r\nXMSNET5.EXE\r\nXMSNETX.EXE\r\nEMSNET5.EXE\r\nEMSNETX.EXE\r\n\r\nIf you don't specify a LASTDRIVE command, MS-DOS uses \"E\"\r\nas its default, and your network software uses \"F\" when it \r\nestablishes a network connection.\r\n\r\nBy default, DoubleSpace reserves four drive letters between the\r\nlocal compressed drive and the host drive for the Compressed \r\nVolume File (CVF). These drive letters are reserved for future use\r\nby such items as a RAMDRIVE, a CD-ROM drive, or a second hard \r\ndrive. Thus, a drive letter conflict can arise when you compress \r\nyour local drive.\r\n\r\nFor example, if you have one logical partition C on your hard drive,\r\nand you compress drive C, DoubleSpace reserves drive letters\r\n\"D\" through \"G\" for future use and \"H\" for the drive hosting\r\nthe CVF. If you had not specified a LASTDRIVE command, your \r\nnetwork software would use the drive letter following the\r\nhost drive--in this case \"I\". In your AUTOEXEC.BAT file or in the \r\nbatch file you use to log on to the nework, any commands that \r\nassume the network drive has a different drive letter will cause \r\nproblems.\r\n\r\nThere are two ways of avoiding drive conflicts:\r\n\r\n* When you install DoubleSpace, run it in Custom mode. Then specify\r\n for your host drive a letter that won't conflict with the letter\r\n your network software uses. For example, if your network drive is\r\n currently \"F,\" you could use \"E\" for your host drive when you\r\n install DoubleSpace.\r\n\r\n* Change the drive references in your AUTOEXEC.BAT file or batch file you\r\n use to log on to the network. Make sure the references match\r\n what your network software will default to after you have installed\r\n DoubleSpace. Also, if you log in manually, use a drive letter that \r\n follows the drive letter DoubleSpace uses for the host drive.\r\n\r\n\r\n7.17 Using the DBLSPACE.INI File\r\n--------------------------------\r\nThe DBLSPACE.INI file is a text file with the Read-Only and Hidden \r\nattributes. DoubleSpace stores this file in the root directory of your \r\nstartup drive. The DBLSPACE.INI file contains variables that DoubleSpace \r\nuses when your computer starts. Although it is possible to change these \r\nvariables yourself, you should do so only if you understand what they do \r\nand what the results might be. Before changing the DBLSPACE.INI file, \r\nyou should make a backup copy of the file.\r\n\r\nThe DBLSPACE.INI file can contain one or more of the following variables:\r\n\r\nMaxRemovableDrives=n\r\n Specifies how many additional drives DoubleSpace should \r\n allocate memory for when your computer starts. DoubleSpace \r\n allocates 96 bytes of memory for each additional drive.\r\n The MaxRemovableDrives variable determines how many additional\r\n compressed drives you can create or mount without restarting \r\n your computer.\r\n\r\nFirstDrive=X\r\n Set by DoubleSpace each time it modifies the DBLSPACE.INI file.\r\n Do not change the FirstDrive variable yourself.\r\n\r\nLastDrive=Y\r\n Specifies the highest drive letter available for use by\r\n DoubleSpace. (If another program uses one of the drive \r\n letters specified for DoubleSpace, the highest drive letter \r\n available to DoubleSpace will be higher than the LastDrive \r\n variable.)\r\n\r\nMaxFileFragments=n\r\n Set by DoubleSpace to specify the degree of fragmentation to \r\n allow in all mounted compressed volume files. Do not change\r\n the MaxFileFragments variable yourself.\r\n\r\nActivateDrive=X,Yn\r\n Specifies a compressed volume file that DoubleSpace should \r\n mount automatically when your computer starts. The\r\n ActivateDrive variable requires the following parameters:\r\n\r\n X The drive letter to assign to the newly mounted\r\n compressed drive.\r\n\r\n Y The drive letter of the HOTLINK(\"host drive\", hlHOST).\r\n\r\n n The number of the HOTLINK(\"compressed volume file\",hlCVF).\r\n To determine the CVF number, examine its filename extension.\r\n If the CVF filename is DBLSPACE.000, set n to 0; if the \r\n CVF filename is DBLSPACE.001, set n to 1; and so on.\r\n \r\n The DBLSPACE.INI file can contain than one ActivateDrive variable.\r\n\r\n\r\n7.18 You Receive the Message \"A CVF is Damaged\" When You Start Your Computer\r\n----------------------------------------------------------------------------\r\nA CVF is a compressed volume file -- a special file that contains a \r\ncompressed drive. A CVF is located on an uncompressed drive. DoubleSpace \r\nassociates the CVF with a drive letter and makes the CVF's contents \r\naccessible. This is called \"mounting\" the CVF. You can then use the \r\nfiles that the CVF contains. \r\n\r\nOne or more CVFs have been damaged if you receive the following \r\nmessage when you start your computer: \r\n \r\n A CVF is damaged. For more information, see the DoubleSpace section of\r\n the README.TXT file. To continue, press ENTER.\r\n\r\nTo correct this problem:\r\n\r\n1. At the command prompt, change to your compressed drive and then run \r\n Chkdsk to fix errors on that drive. For example, if your compressed\r\n drive is drive C, you would type the following:\r\n\r\n c:\r\n chkdsk /f\r\n\r\n2. The Chkdsk program checks for logical errors in the file allocation tables\r\n and directory structure of the current drive, and reports any problems it\r\n finds. When Chkdsk is finished, DoubleSpace checks the validity of the CVF's internal\r\n structure, and reports any problems it found. Both Chkdsk and DoubleSpace\r\n also fix as many problems as possible.\r\n\r\n3. If Chkdsk found any cross-linked files, it displays a message like the\r\n following:\r\n \r\n FILENAME.XXX is cross linked on allocation unit 123.\r\n\r\n To fix this problem, copy the specified file or directory by using the\r\n COPY command, and then delete the original file. Some of the information\r\n in a cross-linked file or directory might be lost.\r\n\r\n4. If you have more than one compressed drive, repeat steps 1 through\r\n 3 for each compressed drive.\r\n\r\n5. Restart your computer by pressing CTRL+ALT+DEL.\r\n\r\n\r\n7.19 You Need a Special Device Driver to Use Your Compressed Startup Drive\r\n--------------------------------------------------------------------------\r\nIf your startup hard disk drive requires an installable device driver, \r\nyou can compress it by using DoubleSpace. However, you must take a few \r\nextra steps to configure the drive before and after installing DoubleSpace. \r\nIf you install DoubleSpace and then restart your computer without following \r\nthese steps, DoubleSpace will be unable to provide access to your startup \r\ndrive. (This is because MS-DOS loads DBLSPACE.BIN, the portion of MS-DOS \r\nthat provides access to compressed drives, before carrying out the commands \r\nin your CONFIG.SYS file.)\r\n\r\nTo compress a startup hard disk that requires a device driver:\r\n\r\n1. Install DoubleSpace by typing DBLSPACE at the command prompt, and choose \r\n Express Setup. (If you choose Custom Setup, have DoubleSpace compress \r\n existing drive C.) When DoubleSpace Setup completes, it lists information \r\n about two drives: drive C (your newly compressed startup drive) and \r\n an uncompressed drive (for example, drive H). Note the drive letter \r\n of the uncompressed drive. \r\n\r\n2. Quit DoubleSpace Setup.\r\n \r\n3. Change to the uncompressed drive that DoubleSpace Setup listed (for \r\n example, drive H).\r\n\r\n4. Type the following at the command prompt:\r\n\r\n dir /a\r\n\r\n The root directory should contain at least the following files:\r\n\r\n IO.SYS\r\n MSDOS.SYS\r\n COMMAND.COM\r\n DBLSPACE.BIN\r\n DBLSPACE.000\r\n \r\n5. Change to drive C and open your AUTOEXEC.BAT file. For example, to \r\n change to drive C and open the AUTOEXEC.BAT file by using MS-DOS \r\n Editor, you would type the following commands at the command prompt:\r\n\r\n c:\r\n edit c:\\autoexec.bat\r\n\r\n6. Add the following command to the beginning of your AUTOEXEC.BAT file:\r\n\r\n dblspace /mount\r\n\r\n Save your changes and quit the text editor.\r\n\r\n7. Use the COPY command to copy the following files from your compressed \r\n drive to the root directory of the uncompressed drive:\r\n\r\n * DBLSPACE.EXE (located in the directory that contains your MS-DOS files)\r\n * CONFIG.SYS (located in the root directory)\r\n * AUTOEXEC.BAT (located in the root directory)\r\n * Any device drivers loaded by commands in your CONFIG.SYS file\r\n\r\nPrograms started by commands in your AUTOEXEC.BAT file can remain on \r\nthe compressed drive.\r\n\r\n\r\n\r\n7.20 Defragmenting Uncompressed Drives After Changing File Attributes \r\n---------------------------------------------------------------------\r\nYou can safely defragment both your compressed or uncompressed drives, \r\nusing MS-DOS Defragmenter or another defragmentation program, as long \r\nas you do not change the file attributes of your compressed volume files. \r\n\r\nCaution: Do not change a CVF's file attributes and then defragment the\r\n drive containing that CVF. The file attributes of a compressed \r\n volume file must be Read-Only, Hidden and System. If you change \r\n the CVF's attributes and then defragment the uncompressed drive \r\n while that CVF is still mounted, you might lose all the files \r\n on that compressed drive.\r\n\r\n\r\n7.21 Files DoubleSpace Cannot Compress\r\n--------------------------------------\r\nSome files (such as .ZIP files) are already compressed. DoubleSpace \r\nmight not be able to compress such files any further.\r\n\r\nEncrypted data files, such as the Microsoft Mail 3.0 .MMF file, are\r\nnot compressible and will be stored in uncompressed form, even if\r\nyou store such files on a compressed drive.\r\n\r\n\r\n7.22 DoubleSpace and Microsoft Mail 3.0 .MMF Files\r\n--------------------------------------------------\r\nIf you use Microsoft Mail 3.0, you might want to make sure your mail \r\n(.MMF) file is located on an uncompressed drive. Mail works properly \r\nif the .MMF file is located on a compressed drive; however, your system \r\nmight run faster if the file is located on an uncompressed drive.\r\n\r\nMicrosoft Mail normally stores the .MMF file in encrypted, compressed\r\nform. Because DoubleSpace cannot compress such a file, there is no \r\nadvantage in storing the .MMF file on a compressed drive.\r\n\r\nIf your uncompressed drive does not have enough space to accommodate \r\nyour .MMF file, you can reduce the size of your compressed drive. \r\nTo do this, follow the procedure in section 7.xx, \"Your uncompressed \r\ndrive is out of disk space.\"\r\n\r\n\r\n7.23 Defragmenter Runs Out Of Memory While You Are Compressing a Drive \r\n----------------------------------------------------------------------\r\nIf the Defragmenter runs out of memory while you are compressing a drive,\r\nexit DoubleSpace, and then carry out the procedures in \"An MS-DOS-based\r\nprogram displays an out-of-memory message\" in the chapter \"Diagnosing\r\nand Solving Problems\" of the Microsoft MS-DOS 6 User's Guide.\r\n\r\nIf the Defragmenter still runs out of memory after you have tried\r\nthese procedures, your computer might have too many files for the\r\nDefragmenter to reorganize the files on your hard disk. For the \r\nprogram to work correctly, you might need to delete some files or \r\nmove them to a floppy disk or a network drive.\r\n\r\n7.24 Free Space Requirements for Converting a Stacker Drive \r\n------------------------------------------------------------\r\nTo convert a Stacker drive to DoubleSpace format, the drive must\r\ncontain some free space. To convert your startup hard disk, the\r\ndrive must contain at least 1.7 MB of free space. To convert other\r\nhard drives and floppy disks, the drive or disk must contain at\r\nleast 1.0 MB of free space.\r\n\r\n\r\n8. Resource Kit\r\n-------------------\r\nThe MS-DOS 6 Resource Kit contains a command reference which is\r\na printed version of MS-DOS Help. The Resource Kit also includes \r\nthe MS-DOS 6 Supplemental Disk. The disk contains all the commands that were \r\nincluded with MS-DOS 5.0 but not MS-DOS 6. In addition, the disk contains \r\nAccessDOS, which provides movemovent- or hearing-disabled users with \r\nbetter access to computers that run MS-DOS.\r\n\r\nTo obtain the Resource Kit, send in the coupon at the back of the \r\nMicrosoft MS-DOS User's Guide, and then send it in. Other methods for \r\nobtaining the Supplemental Disk are described in \"AccessDOS\" in \"Appendix B\" \r\nof the Microsoft MS-DOS User's Guide." }