{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "IBMBIO COM", "size": 24474, "date": "1993-07-09", "time": "1:02" }, { "name": "IBMDOS COM", "size": 39239, "date": "1993-07-09", "time": "1:02" }, { "name": "COMMAND COM", "size": 50440, "date": "1993-07-09", "time": "1:02" }, { "name": "DOSUTILS", "dir": true, "date": "1993-07-09", "time": "1:02" }, { "name": "TECHSUPT", "dir": true, "date": "1993-07-09", "time": "1:02" }, { "name": "INTL", "dir": true, "date": "1993-07-09", "time": "1:02" }, { "name": "AUTOEXEC BAT", "size": 90, "date": "1993-07-09", "time": "1:02" }, { "name": "CHECK EXE", "size": 45028, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG SYS", "size": 24, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG EXE", "size": 18880, "date": "1993-07-09", "time": "1:02" }, { "name": "CREATE COM", "size": 1042, "date": "1993-07-09", "time": "1:02" }, { "name": "DISK1HLP TXT", "size": 1229, "date": "1993-07-09", "time": "1:02" }, { "name": "ED EXE", "size": 18971, "date": "1993-07-09", "time": "1:02" }, { "name": "FILELIST TXT", "size": 6090, "date": "1993-07-09", "time": "1:02" }, { "name": "README TXT", "size": 45420, "date": "1993-07-09", "time": "1:02" }, { "name": "REMOVDRV COM", "size": 1043, "date": "1993-07-09", "time": "1:02" }, { "name": "REPORT EXE", "size": 45454, "date": "1993-07-09", "time": "1:02" }, { "name": "SATTRIB EXE", "size": 9820, "date": "1993-07-09", "time": "1:02" }, { "name": "SCREXEC EXE", "size": 87952, "date": "1993-07-09", "time": "1:02" }, { "name": "SCREXEC2 EXE", "size": 64896, "date": "1993-07-09", "time": "1:02" }, { "name": "SDEFRAG COM", "size": 1042, "date": "1993-07-09", "time": "1:02" }, { "name": "SDEFRAG2 EXE", "size": 95395, "date": "1993-07-09", "time": "1:02" }, { "name": "SDIR EXE", "size": 27972, "date": "1993-07-09", "time": "1:02" }, { "name": "SETUP SAF", "size": 229033, "date": "1993-07-09", "time": "1:02" }, { "name": "SETUP EXE", "size": 41028, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER LBL", "size": 164, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER CFG", "size": 4, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER EXE", "size": 30251, "date": "1993-07-09", "time": "1:02" }, { "name": "SWAPMAP EXE", "size": 20143, "date": "1993-07-09", "time": "1:02" }, { "name": "UNSTACK COM", "size": 1042, "date": "1993-07-09", "time": "1:02" }, { "name": "UNSTACK2 EXE", "size": 46842, "date": "1993-07-09", "time": "1:02" }, { "name": "SERIAL NO", "size": 11, "date": "1993-12-02", "time": "19:25" } ] }, { "path": "/DOSUTILS", "files": [ { "name": "SSWAP CFG", "size": 410, "date": "1993-07-09", "time": "1:02" }, { "name": "SSWAP COM", "size": 57824, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER COM", "size": 43727, "date": "1993-07-09", "time": "1:02" } ] }, { "path": "/TECHSUPT", "files": [ { "name": "DDEBUG EXE", "size": 895, "date": "1993-07-09", "time": "1:02" }, { "name": "REPAIR EXE", "size": 13286, "date": "1993-07-09", "time": "1:02" }, { "name": "SAVEHDR EXE", "size": 5080, "date": "1993-07-09", "time": "1:02" }, { "name": "SFIXCTL3 EXE", "size": 13763, "date": "1993-07-09", "time": "1:02" } ] }, { "path": "/INTL", "files": [ { "name": "AUTOEXEC SP", "size": 108, "date": "1993-07-09", "time": "1:02" }, { "name": "AUTOEXEC UK", "size": 108, "date": "1993-07-09", "time": "1:02" }, { "name": "AUTOEXEC JA", "size": 90, "date": "1993-07-09", "time": "1:02" }, { "name": "AUTOEXEC ENG", "size": 90, "date": "1993-07-09", "time": "1:02" }, { "name": "AUTOEXEC FR", "size": 108, "date": "1993-07-09", "time": "1:02" }, { "name": "AUTOEXEC GR", "size": 108, "date": "1993-07-09", "time": "1:02" }, { "name": "AUTOEXEC IT", "size": 108, "date": "1993-07-09", "time": "1:02" }, { "name": "AUTOEXEC NL", "size": 108, "date": "1993-07-09", "time": "1:02" }, { "name": "AUTOEXEC PO", "size": 108, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG ENG", "size": 24, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG UK", "size": 57, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG JA", "size": 57, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG PO", "size": 57, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG FR", "size": 57, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG GR", "size": 57, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG IT", "size": 57, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG NL", "size": 57, "date": "1993-07-09", "time": "1:02" }, { "name": "CONFIG SP", "size": 57, "date": "1993-07-09", "time": "1:02" }, { "name": "COUNTRY SYS", "size": 10752, "date": "1993-07-09", "time": "1:02" }, { "name": "KEYB COM", "size": 34591, "date": "1993-07-09", "time": "1:02" }, { "name": "LANGUAGE BAT", "size": 1799, "date": "1993-07-09", "time": "1:02" } ] } ], "volume": "SO_1_OF_2" }, "2": { "dirs": [ { "path": "/", "files": [ { "name": "DOSUTILS", "dir": true, "date": "1993-07-09", "time": "1:02" }, { "name": "BOOT COM", "size": 48652, "date": "1993-07-09", "time": "1:02" }, { "name": "FATMGR EXE", "size": 53456, "date": "1993-07-09", "time": "1:02" }, { "name": "MIDINST EXE", "size": 48655, "date": "1993-07-09", "time": "1:02" }, { "name": "POSTINST EXE", "size": 51216, "date": "1993-07-09", "time": "1:02" }, { "name": "POSTUP EXE", "size": 44046, "date": "1993-07-09", "time": "1:02" }, { "name": "PREPINST EXE", "size": 17392, "date": "1993-07-09", "time": "1:02" }, { "name": "PREPUP EXE", "size": 16432, "date": "1993-07-09", "time": "1:02" }, { "name": "SSWAP2 SYS", "size": 5962, "date": "1993-07-09", "time": "1:02" }, { "name": "STACBOOT EXE", "size": 14184, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER CFG", "size": 4, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER LBL", "size": 164, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER SYS", "size": 53396, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKERI SYS", "size": 53346, "date": "1993-07-09", "time": "1:02" }, { "name": "SYNC2 CFG", "size": 778, "date": "1993-07-09", "time": "1:02" }, { "name": "SYNC2 EXE", "size": 60941, "date": "1993-07-09", "time": "1:02" }, { "name": "SYNC2 ORG", "size": 183, "date": "1993-07-09", "time": "1:02" } ] }, { "path": "/DOSUTILS", "files": [ { "name": "@6FB4 ADF", "size": 1388, "date": "1993-07-09", "time": "1:02" }, { "name": "SDIAG_AT EXE", "size": 9070, "date": "1993-07-09", "time": "1:02" }, { "name": "SDIAG_MC EXE", "size": 9048, "date": "1993-07-09", "time": "1:02" }, { "name": "SDIAG_XT EXE", "size": 9974, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER AT", "size": 31828, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER MC", "size": 30564, "date": "1993-07-09", "time": "1:02" }, { "name": "STACKER XT", "size": 31380, "date": "1993-07-09", "time": "1:02" } ] } ], "volume": "SO_2_OF_2" } }, "desc_file": "README.TXT", "desc_text": " Stacker for OS/2 & DOS - Late Breaking News\r\n\r\nThis document contains important information that is not included in the\r\nStacker for OS/2 & DOS User's Guide or in the Help.\r\n\r\nIf you're going to use MS-DOS 6.0 and Stacker 3.1 in conjunction with\r\nStacker for OS/2 & DOS, please be sure to read section 3, particularly\r\nsection 3.4.\r\n\r\nIf you're going to install OS/2 on a Stacker drive, please be sure to read\r\nsection 11.\r\n\r\nIf you're using any special or unique hardware or software with your system,\r\nsee the Help provided in SETUP. To get help in these situations:\r\n\r\n1. From any SETUP screen, press F1.\r\n2. Press ENTER to choose the Index.\r\n3. Press TAB to select Hardware Considerations or Software Considerations\r\n and press ENTER.\r\n\r\n\r\nContents\r\n\r\nThis document contains late-breaking information on the following topics:\r\n\r\n1.0 Changes to Stacker for OS/2 & DOS User's Guide\r\n\r\n 1.1 Which CONFIG.SYS files are updated by UNSTACK\r\n\r\n 1.2 Order of diskette insertion when installing OS/2 2.1\r\n\r\n 1.3 Rebooting directly from POSTINST and POSTUP\r\n\r\n 1.4 Instructions for keeping SWAPPER.DAT uncompressed\r\n\r\n2.0 Non-compression of SWAPPER.DAT\r\n\r\n3.0 Using Stacker for OS/2 & DOS with other Stacker software\r\n\r\n 3.1 Installing Stacker 3.x after Stacker for OS/2 & DOS\r\n\r\n 3.2 Protecting EAs by using the Stacker for OS/2 & DOS utilities\r\n\r\n 3.3 CHECK /WP path\r\n\r\n 3.4 Operation with Stacker 3.1 under MS-DOS 6.0\r\n\r\n 3.4.1 Installing Stacker for OS/2 & DOS after Stacker 3.1\r\n\r\n 3.4.2 Installing Stacker 3.1 after Stacker for OS/2 & DOS\r\n\r\n 3.4.3 Accessing converted DoubleSpace drives under OS/2\r\n\r\n 3.4.4 Accessing new Stacker drives under MS-DOS 6.0\r\n\r\n 3.4.5 Error messages when booting MS-DOS 6.0\r\n\r\n 3.4.6 CONFIG.SYS on Disk 1 not updated by SETUP\r\n\r\n 3.4.7 Error messages after UNSTACK on Dual Boot systems\r\n\r\n 3.4.8 Running PREPINST and PREPUP\r\n\r\n4.0 Rebuilding your OS/2 desktop\r\n\r\n5.0 Creating more Stacker drives after installation\r\n\r\n6.0 Installing without creating any Stacker drives\r\n\r\n7.0 For users of Dual Boot systems\r\n\r\n 7.1 Safe rebooting from OS/2 to DOS\r\n\r\n 7.2 Safe rebooting from DOS to OS/2\r\n\r\n 7.3 Location of Stacker and IBM versions of BOOT.COM\r\n\r\n 7.4 If you're using a Dual Boot system with Stacker 2.0 or 3.0\r\n\r\n8.0 Making space for UNSTACK\r\n\r\n9.0 Damaged drives: AutoProtect and AutoRecovery\r\n\r\n 9.1 If a Stacker drive is write-protected under OS/2\r\n\r\n10.0 Formatting a Stacker drive as HPFS: don't try this!\r\n\r\n11.0 Installing OS/2 on an existing Stacker drive\r\n\r\n 11.1 Simplified procedure for OS/2 2.1 may be available\r\n\r\n 11.2 Slight change to procedure in Appendix B for OS/2 2.1\r\n\r\n 11.3 Installing OS/2 from a CD-ROM\r\n\r\n 11.4 Files won't migrate from other Stacker drives\r\n\r\n 11.5 OS/2 error message in POSTINST\r\n\r\n 11.6 Temporary video corruption after running MIDINST\r\n\r\n12.0 CONFIG notes\r\n\r\n 12.1 CONFIG with optical disks\r\n\r\n 12.2 Handling of special switches in DOS CONFIG.SYS\r\n\r\n13.0 Lost extended attribute message on CONFIG.SYS\r\n\r\n14.0 Files not found at OS/2 startup\r\n\r\n15.0 HPFS boot drives\r\n\r\n16.0 Changing where Stacker for OS/2 & DOS is installed\r\n\r\n17.0 Avoiding the SUBST command\r\n\r\n18.0 SDEFRAG notes\r\n\r\n 18.1 Lowers fragmentation even if you don't tell it to defragment\r\n\r\n 18.2 Error 136\r\n\r\n19.0 The DONT_DEL.ME file\r\n\r\n 19.1 CHECK and CHKDSK error messages related to DONT_DEL.ME\r\n\r\n20.0 Creating large Stacker drives\r\n\r\n 20.1 Two Stacker drives created when one is requested\r\n\r\n 20.2 SETUP running out of memory\r\n\r\n21.0 For users of systems with OS/2 pre-installed\r\n\r\n 21.1 Unscrambling the OS/2 logo screen\r\n\r\n22.0 Running DOS from a disk or disk image within OS/2\r\n\r\n23.0 GammaTech utilities\r\n\r\n24.0 Customizing Stacker for international use\r\n\r\n25.0 Determining free space requirements\r\n\r\n----------------------------------------------------------------------------\r\n\r\n1.0 Changes to Stacker for OS/2 & DOS User's Guide\r\n\r\n1.1 Which CONFIG.SYS files are updated by UNSTACK\r\n\r\nThe User's Guide states (on page 93) that UNSTACK updates only one OS/2\r\nCONFIG.SYS file. Actually, when UNSTACK removes a Stacker drive it updates\r\nall the OS/2 and DOS CONFIG.SYS files it can find. It can't, however, update\r\na CONFIG.SYS file that's on an HPFS partition or on a hidden partition.\r\n\r\n1.2 Order of diskette insertion when installing OS/2 2.1\r\n\r\nDue to a late-breaking change in the installation process for OS/2 2.1,\r\nstep 10 at the bottom of page 154 in the Stacker for OS/2 & DOS User's\r\nGuide should be changed to:\r\n\r\n 10 After you have inserted several diskettes, insert the Installation\r\n Diskette again when OS/2 asks for it. If you're installing OS/2 2.1,\r\n also reinsert Diskette 1 when OS/2 asks for it.\r\n\r\n1.3 Rebooting directly from POSTINST and POSTUP\r\n\r\nThe POSTINST and POSTUP utilities both have been modified to prompt you to\r\npress Ctrl-Alt-Del to reboot when they have completed their processing.\r\nAccordingly, step 18 on page 156 and step 9 on page 160 of the User's Guide\r\ncan be omitted.\r\n\r\n1.4 Instructions for keeping SWAPPER.DAT uncompressed\r\n\r\nThe directions in Appendix E of the User's Guide for telling OS/2 to use an\r\nuncompressed drive for SWAPPER.DAT no longer apply, since this is now done\r\nautomatically, as described in the next section.\r\n\r\n2.0 Non-compression of SWAPPER.DAT\r\n\r\nThe OS/2 swap file SWAPPER.DAT cannot be kept on a Stacker drive in this\r\nversion of Stacker for OS/2 & DOS. If SWAPPER.DAT is on a Stacker drive,\r\nSYNC2.EXE will detect this when it runs at startup and will alter the\r\nSWAPPATH directive in the OS/2 CONFIG.SYS to make sure that on subsequent\r\nreboots SWAPPER.DAT will be on an uncompressed drive.\r\n\r\nWhen SYNC2 has to move SWAPPER.DAT, it always tries to move it to the\r\nuncompressed drive corresponding to the OS/2 boot drive. If there is not\r\nenough uncompressed space on that drive, SYNC2 suggests making more free\r\nspace available by running SDEFRAG /GP. If you have more free space on a\r\ndifferent uncompressed drive, you may wish to edit CONFIG.SYS so that the\r\nSWAPPATH directive instead points to the uncompressed drive with more free\r\nspace.\r\n\r\nAs mentioned above in section 1.4 of this file, the directions in Appendix E\r\nof the User's Guide for telling OS/2 to use an uncompressed drive for\r\nSWAPPER.DAT no longer apply, since this is done automatically.\r\n\r\nAfter SYNC2 changes the SWAPPATH away from a Stacker drive, be sure to delete\r\nthe unused SWAPPER.DAT file from the Stacker drive so that it won't be taking\r\nup space. It's normally in the directory \\OS2\\SYSTEM, although the SWAPPATH\r\ndirective in CONFIG.SYS can cause it to be placed in a different directory.\r\n\r\n3.0 Using Stacker for OS/2 & DOS with other Stacker software\r\n\r\nThis section provides some additional information you need to be aware of\r\nif you'll be using Stacker for OS/2 & DOS along with other Stacker software.\r\nIt supplements Appendix C of the Stacker for OS/2 & DOS User's Guide. Please\r\nbe sure to read that appendix as well if this section applies to you.\r\n\r\nIf you're using MS-DOS 6.0 and will be using Stacker 3.1 in conjunction with\r\nStacker for OS/2 & DOS, please pay particular attention to section 3.4 below.\r\n\r\nIf you're already using a DOS version of Stacker and have created a Dual Boot\r\nsystem by installing OS/2 in the C drive's uncompressed free space, please\r\nsee section 7.4 of this file.\r\n\r\nStacker 3.x is used in this section whenever information applies to both\r\nStacker 3.0 and Stacker 3.1.\r\n\r\n3.1 Installing Stacker 3.x after Stacker for OS/2 & DOS\r\n\r\nIf you install Stacker 3.x after Stacker for OS/2 & DOS, when you run the\r\nStacker 3.x SETUP program, choose Custom Setup, not Express Setup, and do not\r\nlet it compress any drives that you'll want to access under OS/2. Otherwise,\r\nyou risk losing the extended attributes (such as OS/2 desktop icons) of files\r\non those drives. It's best to just let the Stacker 3.x SETUP install the\r\nStacker 3.x files. To do this, run the Stacker 3.x SETUP, choose Custom\r\nSetup, let it copy the Stacker files to the hard drive, and then choose Exit\r\nwhen it asks you to select a drive to compress.\r\n\r\nUse the Stacker for OS/2 & DOS SETUP, as described in the next section of\r\nthis file, to create new Stacker drives.\r\n\r\n3.2 Protecting EAs by using the Stacker for OS/2 & DOS utilities\r\n\r\nIf you have Stacker 3.x on your system in addition to Stacker for OS/2 & DOS,\r\nplease be sure that after you've installed Stacker 3.x you use the Stacker\r\nfor OS/2 & DOS versions of the following utilities:\r\n\r\n SETUP\r\n UNSTACK\r\n REMOVDRV\r\n\r\nIt's particularly important to observe this rule with SETUP and UNSTACK so\r\nthat the extended attributes (for example, OS/2 desktop icons) of the files\r\nare preserved. In addition, the Stacker for OS/2 & DOS versions of the\r\nutilities listed above update OS/2 CONFIG.SYS files, not just the DOS one,\r\nto reflect the addition or removal of Stacker drives.\r\n\r\nIf you let the Stacker for OS/2 & DOS SETUP modify your AUTOEXEC.BAT, this\r\nnormally will cause the Stacker for OS/2 & DOS versions of the utilities to\r\nbe executed instead of the Stacker 3.x versions when you're using DOS. For\r\nexample, typing UNSTACK C: runs the Stacker for OS/2 & DOS version of\r\nUNSTACK, not the Stacker 3.x version.\r\n\r\nIf you don't let SETUP modify your AUTOEXEC.BAT, or if you've installed\r\nStacker 3.x in a directory with a name other than \\STACKER, you should edit\r\nyour DOS AUTOEXEC.BAT file and make sure the Stacker for OS/2 & DOS directory\r\nprecedes the Stacker 3.x directory in the PATH command.\r\n\r\n3.3 CHECK /WP path\r\n\r\nIf you're already running a DOS version of Stacker, you should change the\r\npath on the CHECK /WP command in your DOS AUTOEXEC.BAT to the one where\r\nStacker for OS/2 & DOS is installed. For example, if it now says\r\nC:\\STACKER\\CHECK /WP and you installed Stacker for OS/2 & DOS in\r\nD:\\STACKER\\OS2, change the command to D:\\STACKER\\OS2\\CHECK /WP. (An OS/2\r\nAUTOEXEC.BAT file does not need a CHECK /WP command. If you have a Dual Boot\r\nsystem, then while you're running OS/2 your DOS AUTOEXEC.BAT is stored as\r\n\\OS2\\SYSTEM\\AUTOEXEC.DOS, not \\AUTOEXEC.BAT.)\r\n\r\n3.4 Operation with Stacker 3.1 under MS-DOS 6.0\r\n\r\nStacker for OS/2 & DOS is basically compatible with Stacker 3.1 when running\r\nunder MS-DOS 6.0. This section provides some information you should be aware\r\nof if you're using that combination.\r\n\r\n3.4.1 Installing Stacker for OS/2 & DOS after Stacker 3.1\r\n\r\nIf Stacker 3.1 is already installed, the Stacker for OS/2 & DOS SETUP will\r\noverwrite the Stacker 3.1 files if you let it install to the same path with\r\n\"\\OS2\" appended. For example, if Stacker 3.1 is installed in C:\\STACKER and\r\nyou install Stacker for OS/2 & DOS to C:\\STACKER\\OS2, then you'll lose the\r\nStacker 3.1 files in C:\\STACKER. You can work around this problem in either\r\nof the following two ways:\r\n\r\n(i) Before running the Stacker for OS/2 & DOS SETUP, copy the file\r\n \\DOSUTILS\\SSWAP.COM from Stacker for OS/2 & DOS Disk 1 to the directory\r\n in which Stacker 3.1 is installed. (This will inhibit SETUP from\r\n overwriting the Stacker 3.1 files.)\r\n(ii) Reinstall Stacker 3.1 after Stacker for OS/2 & DOS, making sure not to\r\n compress any drives with the Stacker 3.1 SETUP.\r\n(iii) Install Stacker for OS/2 & DOS to a different path or drive. For\r\n example, if Stacker 3.1 is installed in C:\\STACKER, you might install\r\n Stacker for OS/2 & DOS in D:\\STACKER\\OS2 or C:\\STAC\\OS2 instead of\r\n C:\\STACKER\\OS2.\r\n\r\nAlso, the Stacker for OS/2 & DOS SETUP may insert STACKER.COM and SSWAP.COM\r\nlines in your DOS CONFIG.SYS that will cause error messages to display when\r\nyou boot DOS. You can use a text editor to remove those lines from the\r\nCONFIG.SYS file if you wish. This subject is also covered in section 3.4.5\r\nbelow.\r\n\r\nFinally, you should make sure that the path specified in the CHECK /WP line\r\nnear the top of your DOS AUTOEXEC.BAT file is the path where Stacker for OS/2\r\n& DOS is installed, as described above in section 3.3 of this file.\r\n\r\n3.4.2 Installing Stacker 3.1 after Stacker for OS/2 & DOS\r\n\r\nIf you install Stacker 3.1 in the parent of the directory where Stacker for\r\nOS/2 & DOS is installed, the DOS-specific Stacker for OS/2 & DOS files, in\r\nparticular STACKER.COM and SSWAP.COM, will be overwritten. This doesn't do\r\nany harm, however.\r\n\r\nAfter installing Stacker 3.1, you should make sure that the path specified in\r\nthe CHECK /WP line near the top of your DOS AUTOEXEC.BAT file is the path\r\nwhere Stacker for OS/2 & DOS is installed, as described above in section 3.3\r\nof this file.\r\n\r\n3.4.3 Accessing converted DoubleSpace drives under OS/2\r\n\r\nWhen you convert a DoubleSpace drive using Stacker 3.1, one more step is\r\nrequired before you can access it under OS/2. You must run SDEFRAG d: /R\r\n(where d: is the drive letter of the converted drive), using the Stacker 3.1\r\nSDEFRAG, to recompress the data. Until then, the drive can't be accessed\r\nunder OS/2 or when you boot from Stacker for OS/2 & DOS Disk 1.\r\n\r\nWhen you run SDEFRAG for this purpose, you need to specify the directory in\r\nwhich Stacker 3.1 is installed to make sure the correct version of SDEFRAG is\r\nrun. That's because, as described above, the Stacker for OS/2 & DOS directory\r\nprobably precedes the Stacker 3.1 directory in your PATH command, and only\r\nthe Stacker 3.1 SDEFRAG program can recompress the converted drive. The\r\nStacker for OS/2 & DOS version of SDEFRAG will display an error message if\r\nyou try to use it on such a drive.\r\n\r\nMost commonly, Stacker 3.1 will be installed in C:\\STACKER, in which case\r\nyou would type C:\\STACKER\\SDEFRAG d: /R (where d: is the drive letter of the\r\nconverted drive) and press Enter.\r\n\r\n3.4.4 Accessing new Stacker drives under MS-DOS 6.0\r\n\r\nAfter you use the Stacker for OS/2 & DOS SETUP to create a Stacker drive,\r\nwhich is the way to ensure the files' extended attributes are preserved, \r\nyou need to run the Stacker 3.1 CONFIG program to make sure that drive\r\ncan be accessed under MS-DOS 6.0.\r\n\r\nWhen you run CONFIG for this purpose, you need to specify the directory in\r\nwhich Stacker 3.1 is installed to make sure the correct version of CONFIG is\r\nrun. Most commonly, Stacker 3.1 will be installed in C:\\STACKER, in which\r\ncase you would type C:\\STACKER\\CONFIG and press Enter.\r\n\r\n3.4.5 Error messages when booting MS-DOS 6.0\r\n\r\nThe Stacker for OS/2 & DOS SETUP and CONFIG commands may insert STACKER.COM\r\nand SSWAP.COM lines in your DOS CONFIG.SYS file. This will cause error\r\nmessages to display when you boot MS-DOS 6.0, but will otherwise do no harm.\r\nYou can use a text editor to remove those lines from the CONFIG.SYS file if\r\nyou wish.\r\n\r\n3.4.6 CONFIG.SYS on Disk 1 not updated by SETUP\r\n\r\nWhen you boot from Stacker for OS/2 & DOS Disk 1 and run SETUP, the\r\nCONFIG.SYS file on that disk may not be updated if Stacker 3.1 is on your\r\nsystem. If you find that when you boot Disk 1 you can't access some or all\r\nof your Stacker drives, run CONFIG, accept the CONFIG.SYS changes it offers\r\nto make, and reboot with Disk 1.\r\n\r\n3.4.7 Error messages after UNSTACK on Dual Boot systems\r\n\r\nOn a Dual Boot system, UNSTACK may not update the OS/2 CONFIG.SYS file; when\r\nyou reboot OS/2 you will get a message that the drive you removed cannot be\r\nmounted. Running CONFIG under OS/2 will make the necessary update to the\r\nCONFIG.SYS file.\r\n\r\n3.4.8 Running PREPINST and PREPUP\r\n\r\nPREPINST and PREPUP should be run by booting from Stacker for OS/2 & DOS Disk\r\n1 if Stacker 3.1 is on your system. Otherwise, they may complain that the\r\ndrive on which you want to install or update OS/2 isn't swapped, even though\r\nit is.\r\n\r\n4.0 Rebuilding your OS/2 desktop\r\n\r\nIf you use Alt+F1 while rebooting to rebuild the desktop on a compressed OS/2\r\nboot drive, you won't be able to boot OS/2 from that drive subsequently. To\r\navoid this problem, enter these commands before using Alt+F1:\r\n\r\n COPY d:\\OS2\\INSTALL\\CONFIG.SYS d:\\OS2\\INSTALL\\CONFIG.SAV\r\n COPY d:\\CONFIG.SYS d:\\OS2\\INSTALL\\CONFIG.SYS\r\n\r\nwhere d: is the compressed OS/2 boot drive.\r\n\r\nAs a result of the first COPY command above, the original CONFIG.SYS that\r\nOS/2 saved in the OS2\\INSTALL directory will still be there, but under the\r\nname CONFIG.SAV.\r\n\r\n5.0 Creating more Stacker drives after installation\r\n\r\nIf you run SETUP from Stacker for OS/2 & DOS Disk 1, it will assume that you\r\nwant to reinstall the Stacker files to the hard drive. To avoid this when\r\nyou've already done the installation and only want to create additional\r\nStacker drives, run SETUP from the directory where you installed it on the\r\nhard drive. If you've booted from Disk 1, the easiest way to do this if you\r\ndon't remember the installation path is to enter the command\r\n\r\n TYPE INSTPATH.TXT\r\n\r\nwhich will show you the path where Stacker for OS/2 & DOS was installed (for\r\nexample, C:\\STACKER\\OS2\\) and run SETUP from there (for example, type\r\nC:\\STACKER\\OS2\\SETUP and press Enter).\r\n\r\nThis is potentially more complicated if you have HPFS drives on your system,\r\nas the drive letter given in INSTPATH.TXT is the OS/2 drive letter, and the\r\nDOS drive letter may be lower. For example, let's say you installed Stacker\r\nfor OS/2 & DOS in E:\\STACKER\\OS2 and INSTPATH.TXT will say E:\\STACKER\\OS2\\. \r\nHowever, if your D drive is an HPFS drive, then the drive that's called E:\r\nwhen you're in OS/2 or in SETUP is called D: under DOS because DOS skips over\r\nthe HPFS drive, so you would run SETUP by typing D:\\STACKER\\OS2\\SETUP instead\r\nof E:\\STACKER\\OS2\\SETUP. (Within SETUP, all drives are referred to by their\r\nOS/2 drive letters.)\r\n\r\n6.0 Installing without creating any Stacker drives\r\n\r\nHere's the cleanest way to install Stacker for OS/2 & DOS without creating\r\nany new Stacker drives. Run SETUP and select Custom installation (as opposed\r\nto Express). If a version of Stacker isn't already present on your system,\r\nyou'll be prompted for the directory in which to copy the Stacker files.\r\nAfter SETUP has copied the files, you'll be asked whether you want the PATH\r\ncommand in your AUTOEXEC.BAT updated (recommended answer: yes) and then\r\nyou'll see a screen with buttons labeled Restart, Don't Restart, and Exit.\r\nSelect Exit at this point. (It would work to exit from SETUP at any time\r\nafter the files have been copied, but this way you don't spend any more time\r\nin SETUP than you have to.)\r\n\r\n7.0 For users of Dual Boot systems\r\n\r\nThis section contains important information for users of Dual Boot systems;\r\nthat is, systems where both DOS and OS/2 boot from the C drive. Stacker for\r\nOS/2 & DOS installs its own version of BOOT.COM, as the one that comes with\r\nOS/2 doesn't work if the C drive is a Stacker drive.\r\n\r\n7.1 Safe rebooting from OS/2 to DOS\r\n\r\nOn Dual Boot systems, before entering BOOT /DOS to reboot into DOS you must\r\nmake sure to shut down all applications. This is true of the IBM BOOT.COM as\r\nwell as the Stacker for OS/2 & DOS BOOT.COM.\r\n\r\n7.2 Safe rebooting from DOS to OS/2\r\n\r\nIf you use a disk cache utility under DOS that performs \"lazy writes\" (that\r\nis, it doesn't write data to the disk right away), be sure to flush or\r\ndisable the cache before running the BOOT /OS2 command. One symptom of\r\nneeding to do this is that the computer reboots back into DOS instead of\r\nbooting OS/2.\r\n\r\n7.3 Location of Stacker and IBM versions of BOOT.COM\r\n\r\nOn your OS/2 boot drive, SETUP renames \\OS2\\BOOT.COM to OS2BOOT.COM and\r\ncopies the Stacker for OS/2 & DOS version of BOOT.COM into the \\OS2\r\ndirectory. If you have more than one OS/2 boot drive, SETUP asks you which\r\none you want to have CONFIG.SYS updated on, and this is the one on which\r\n\\OS2\\BOOT.COM is updated.\r\n\r\nIf you compress that OS/2 boot drive, neither \\OS2\\BOOT.COM nor\r\n\\OS2\\OS2BOOT.COM is kept on the uncompressed drive. However, the Stacker\r\nfor OS/2 & DOS version of BOOT.COM is kept on the uncompressed drive, in the\r\ndirectory where Stacker for OS/2 & DOS is installed (typically \\STACKER\\OS2).\r\n\r\n7.4 If you're using a Dual Boot system with Stacker 2.0 or 3.0\r\n\r\nA number of users of Stacker 2.0 or Stacker 3.0 for Windows and DOS who\r\ncouldn't wait for Stacker for OS/2 & DOS have set up Dual Boot systems on\r\nwhich the C drive is a Stacker drive. They've done this by installing OS/2 in\r\nthe C drive's uncompressed space. On such a system, rebooting from DOS to\r\nOS/2 would normally be a problem because the physical C drive is swapped with\r\na different drive, which throws off IBM's BOOT.COM. However, these ingenious\r\nfolks have solved this problem by rerunning SSWAP.COM before BOOT /OS2 (for\r\nexample, if C: is swapped with E:, they would enter SSWAP C: E:). That way,\r\nC: is what the IBM BOOT.COM expects it to be, namely the physical C drive.\r\n\r\nIf you're not one of these users, you can ignore the rest of this section.\r\n\r\nIf you are one of these users, your preferred course of action is to run\r\nUNSTACK on your existing C drive, then install Stacker for OS/2 & DOS and\r\nturn the whole drive, including OS/2, into a new Stacker drive. That way,\r\nyou'll be able to see all your data under both OS/2 and DOS. If you're\r\ncurrently using Stacker 2.0, in which case you don't have UNSTACK, you can\r\nuse the Stacker for OS/2 & DOS UNSTACK as follows:\r\n\r\n1. Boot with the Stacker for OS/2 & DOS Disk 1 in the A drive\r\n2. Update A:\\CONFIG.SYS by running CONFIG.\r\n3. Reboot with Disk 1 still in the A drive.\r\n4. Run UNSTACK to remove Stacker drive C.\r\n\r\nAfter you've run UNSTACK, you can run the Stacker for OS/2 & DOS SETUP.\r\n\r\nIf for some reason you don't run UNSTACK before the Stacker for OS/2 & DOS\r\nSETUP, you need to be aware of two issues:\r\n\r\n1. If you run SETUP with the Stacker drive C mounted and swapped (the way\r\nyou normally run your system), SETUP will not modify the OS/2 CONFIG.SYS and\r\nAUTOEXEC.BAT files, which are stashed away as C:\\OS2\\SYSTEM\\CONFIG.OS2 and\r\nC:\\OS2\\SYSTEM\\AUTOEXEC.OS2 when you're running DOS. The next time you reboot\r\nto OS/2, you'll need to do two things:\r\n(i) Run CONFIG to update your OS/2 CONFIG.SYS\r\n(ii) Edit the OS/2 AUTOEXEC.BAT to put the Stacker for OS/2 & DOS path (which\r\n is C:\\STACKER\\OS2 if you accepted the default) in the PATH command.\r\n\r\n2. If you run SETUP without the Stacker drive C mounted, it will not install\r\nStacker for OS/2 & DOS on the C drive. However, if you have another drive\r\nthat isn't compressed, you can install Stacker for OS/2 & DOS there. In that\r\ncase, SETUP will update your OS/2 CONFIG.SYS and AUTOEXEC.BAT files, unlike\r\nthe preceding case.\r\n\r\n8.0 Making space for UNSTACK\r\n\r\nUNSTACK may tell you that you must make more space on the uncompressed drive.\r\nIf you're unstacking an OS/2 boot drive, the easiest way to make lots of\r\nspace may be to delete the SWAPPER.DAT file, which normally will be in the\r\n\\OS2\\SYSTEM directory on the uncompressed drive. (If you're not sure which\r\ndrive is the uncompressed one, run SWAPMAP. For example, if you're about to\r\nunstack drive D, look for the drive that SWAPMAP says was drive D at boot\r\ntime.)\r\n\r\nIf you decide to make more space by deleting other files, it's best to boot\r\nOS/2 and delete the files, so that the extended attributes of files you\r\ndelete aren't left dangling. Then run CHECK (in a DOS session) and the OS/2\r\nCHKDSK to make sure the Stacker drive is clean, and reboot into DOS. If CHECK\r\nreported any errors, run CHECK /F, and finally run UNSTACK again.\r\n\r\n9.0 Damaged drives: AutoProtect and AutoRecovery\r\n\r\nThe AutoProtect(TM) feature mentioned on the Stacker for OS/2 & DOS box is\r\nthe feature that if a Stacker drive is seriously damaged it is automatically\r\nwrite protected at startup, under both OS/2 and DOS, to prevent any further\r\nloss of data. The AutoRecovery(TM) feature mentioned on the box is the\r\nautomatic repair of such damaged drives under DOS.\r\n\r\nDamaged Stacker drives that have been write protected are automatically\r\nrepaired when you boot DOS, assuming the CHECK /WP command that SETUP puts\r\nin your DOS AUTOEXEC.BAT is still present.\r\n\r\n9.1 If a Stacker drive is write-protected under OS/2\r\n\r\nWhen OS/2 is starting up, if the Stacker driver (STACKER.SYS) write-protects\r\na damaged Stacker drive it displays a message to that effect and asks you to\r\npress a key to continue. At this point, you should let OS/2 finish booting\r\n(if it will), then shut down OS/2 and boot DOS. Assuming your DOS\r\nAUTOEXEC.BAT has the CHECK /WP command in it, your drive will automatically\r\nbe repaired at that point; this is the AutoRecovery feature. Otherwise, run\r\nCHECK d: /F (where d: is the drive letter of the damaged drive) to repair it.\r\n\r\n10.0 Formatting a Stacker drive as HPFS: don't try this!\r\n\r\nIf you try to reformat a Stacker drive as an HPFS drive, the format operation\r\nmay \"succeed\" but the Stacker drive will be rendered useless. Of course, all\r\nthe data on the drive will be lost, as in any formatting operation.\r\n\r\n11.0 Installing OS/2 on an existing Stacker drive\r\n\r\nPlease read this section before installing OS/2 on an existing Stacker drive.\r\n\r\n11.1 Simplified procedure for OS/2 2.1 may be available\r\n\r\nIf you're installing OS/2 2.1 and you have a modem, check Stac's BBS or\r\nthe Stacker CompuServe forum. We expect to be posting software soon in\r\nboth places that allow OS/2 2.1 to be installed on a Stacker drive with\r\nconsiderably fewer steps than the method given in Appendix B of the User's\r\nGuide. Consult the HOW TO REACH US brochure in your Stacker for OS/2 & DOS\r\npackage for information on Stac's BBS and the CompuServe forum.\r\n\r\n11.2 Slight change to procedure in Appendix B for OS/2 2.1\r\n\r\nIf you're installing OS/2 2.1 on a Stacker drive using the method in Appendix\r\nB of the User's Guide, pretend that step 10 at the bottom of page 154 says:\r\n\r\n 10 After you have inserted several diskettes, insert the Installation\r\n Diskette again when OS/2 asks for it. If you're installing OS/2 2.1,\r\n also reinsert Diskette 1 when OS/2 asks for it.\r\n\r\n11.3 Installing OS/2 from a CD-ROM\r\n\r\nIf you're installing OS/2 from a CD-ROM, the instructions in Appendix B of\r\nthe User's Guide for installing on a Stacker drive still apply. Where the\r\ninstructions refer to the OS/2 Installation Diskette and OS/2 Diskette 1,\r\nuse the two diskettes that came with the CD-ROM.\r\n\r\n11.4 Files won't migrate from other Stacker drives\r\n\r\nDuring OS/2 installation, \"Migrate Applications\" and \"Configure WIN-OS/2\r\nDesktop\" will not find files on any Stacker drive other than the drive on\r\nwhich you're installing OS/2.\r\n\r\n11.5 OS/2 error message in POSTINST\r\n\r\nIf you get an error message from OS/2 while running POSTINST to reinstall\r\nOS/2 on a Stacker drive, select \"Return error code to application.\"\r\n\r\nThis error occurs when POSTINST tries to replace the OS/2 BOOT.COM with the\r\nStacker for OS/2 & DOS version, if that replacement has already been done.\r\nNo harm is done by this error.\r\n\r\n11.6 Temporary video corruption after running MIDINST\r\n\r\nWhile installing OS/2 on a Stacker drive using PREPINST, MIDINST, and\r\nPOSTINST, you may see some video corruption. Specifically, when OS/2 is\r\nrebooting from the target drive after you run MIDINST, the OS/2 rings may\r\nappear out of sync and there may be a series of vertical lines near the top\r\nof the screen. This goes away in a few seconds and is harmless.\r\n\r\n12.0 CONFIG notes\r\n\r\nThis section provides some further information on the CONFIG command.\r\n\r\n12.1 CONFIG with optical disks\r\n\r\nIf you run CONFIG in a DOS session under OS/2 with an optical drive mounted\r\nthat has no disk in it, OS/2 will display a SYS0039 error, saying the drive\r\nis not ready. If this happens, select \"Return error code to application\" and\r\nCONFIG will continue normally.\r\n\r\n12.2 Handling of special switches in DOS CONFIG.SYS\r\n\r\nWhen you run CONFIG under DOS, the Stacker lines that it offers to insert in\r\nin your DOS CONFIG.SYS are strictly \"vanilla.\" STACKER.COM switches that\r\ndon't start with a slash (such as @ and *) are not preserved, nor are\r\nspecial driver loading directives such as DEVICEHIGH. Also, SSWAP.COM lines\r\ninserted by CONFIG use the /SYNC switch, not /SYNC+.\r\n\r\nIf you press Y to accept the changes CONFIG suggests, the old lines are left\r\nin the CONFIG.SYS (with a REM in front so they're ignored), so they're right\r\nthere to refer to if you decide to edit the file to restore any of the\r\nprevious switches or directives.\r\n\r\n13.0 Lost extended attribute message on CONFIG.SYS\r\n\r\nThe OS/2 CHKDSK may give you a \"lost extended attribute\" message after you\r\nrun SETUP, UNSTACK, or REMOVDRV if your OS/2 CONFIG.SYS had an extended\r\nattribute. Those programs do not preserve the extended attribute of\r\nCONFIG.SYS. By default, CONFIG.SYS has no extended attribute; when it\r\ndoes have one, it's generally just a file type whose loss does no harm.\r\n\r\n14.0 Files not found at OS/2 startup\r\n\r\nInstallation of some OS/2 software packages may insert DEVICE= lines at the\r\ntop of the OS/2 CONFIG.SYS file, before the STACKER.SYS and SSWAP2.SYS lines.\r\nThe next time you reboot OS/2, these new drivers may display error messages\r\nsaying they can't find certain files; the reason is that those files are on a\r\nStacker drive which, because the Stacker driver hasn't been loaded yet, can't\r\nbe accessed yet.\r\n\r\nThe solution is to edit the OS/2 CONFIG.SYS and move the Stacker-related\r\nlines (the ones that mention STACKER.SYS, SSWAP2.SYS, FATMGR.EXE, and\r\nSYNC2.EXE) to the top of CONFIG.SYS, making sure to keep them in their\r\noriginal order.\r\n\r\n15.0 HPFS boot drives\r\n\r\nIf you have an OS/2 boot drive formatted as an HPFS drive, the CONFIG.SYS and\r\nAUTOEXEC.BAT files on that drive will not be updated by SETUP, UNSTACK, and\r\nREMOVDRV, since these programs run under DOS and therefore cannot access HPFS\r\ndrives. To bring this drive up to date, boot from it and run CONFIG to update\r\nthe CONFIG.SYS file. You may also wish to use a text editor to insert the\r\npath where you've installed Stacker for OS/2 & DOS in the AUTOEXEC.BAT file's\r\nPATH statement, so that the Stacker utilities will be directly available. For\r\nexample, if you've installed Stacker for OS/2 & DOS in C:\\STACKER\\OS2, you\r\nwould change the PATH statement from \r\n\r\n PATH D:\\OS2;D:\\OS2\\MDOS\r\n\r\nto\r\n\r\n PATH D:\\OS2;D:\\OS2\\MDOS;c:\\stacker\\os2\r\n \r\n16.0 Changing where Stacker for OS/2 & DOS is installed\r\n\r\nAfter you've installed Stacker for OS/2 & DOS, it's inadvisable to try to\r\nmove it to a different directory or to give the directory that it's in a new\r\nname (for example, to install in \\STACKER\\OS2 and then by renaming\r\ndirectories change it to \\ST\\O2). If you absolutely must change the path\r\nof the Stacker files, you need to replace the old Stacker path with the new\r\none every time it occurs in the following files:\r\n\r\n(i) All OS/2 and DOS CONFIG.SYS files containing Stacker commands. This\r\n includes the CONFIG.SYS on the second diskette in the set of Stacker-\r\n aware OS/2 boot diskettes you made with STACBOOT. It also includes\r\n C:\\OS2\\SYSTEM\\CONFIG.DOS on a Dual Boot system where you're currently\r\n running OS/2.\r\n\r\n(ii) All OS/2 and DOS AUTOEXEC.BAT files. This includes\r\n C:\\OS2\\SYSTEM\\AUTOEXEC.DOS on a Dual Boot system where you're currently\r\n running OS/2.\r\n\r\n(iii) \\OS2\\SYSTEM\\CONFIG.OS2 and \\OS2\\SYSTEM\\AUTOEXEC.OS2 on a Dual Boot\r\n system where you're currently running DOS.\r\n\r\n(iv) INSTPATH.TXT on Stacker for OS/2 & DOS Disk 1 and Disk 2 and in the\r\n directory to which you've moved Stacker.\r\n\r\nIf you have HPFS drives on your system, the path may be different under DOS\r\nthan it is under OS/2 because DOS skips over HPFS drives. The DOS CONFIG.SYS\r\nand AUTOEXEC.BAT files (including CONFIG.DOS and AUTOEXEC.DOS) should use \r\nthe DOS drive letter. The OS/2 CONFIG.SYS and AUTOEXEC.BAT files (including\r\nCONFIG.OS2 and AUTOEXEC.OS2), plus all the INSTPATH.TXT files, should use the\r\nOS/2 drive letter.\r\n\r\n17.0 Avoiding the SUBST command\r\n\r\nAvoid using SUBST to assign a new drive letter to a directory on a Stacker\r\ndrive. If you must do this, it is advisable to remove the mounted drive\r\nbefore running any Stacker utilities, such as CHECK. If x: is the drive\r\nletter of the mounted drive, SUBST x: /D will remove it.\r\n\r\n18.0 SDEFRAG notes\r\n\r\nThis section provides some further information on the SDEFRAG command.\r\n\r\n18.1 Lowers fragmentation even if you don't tell it to defragment\r\n\r\nSDEFRAG performs certain kinds of cleanup even if you decline to actually\r\ndefragment the drive, so it and the other utilities that report on the\r\nfragmentation level (CHECK and REPORT) may display a lower number than\r\nbefore.\r\n\r\n18.2 Error 136\r\n\r\nIf you run SDEFRAG /GP to change the physical size of a Stacker drive and\r\nget a message that says SIZE CHANGE ERROR 136, create a new subdirectory in\r\nthe root directory of the Stacker drive that alphabetically precedes all\r\nthe others (e.g., \\aaaaa), copy some files into it, and rerun SDEFRAG /GP.\r\n\r\n19.0 The DONT_DEL.ME file\r\n\r\nUnder OS/2, the root directory of every Stacker drive contains a hidden file\r\ncalled DONT_DEL.ME. Its size is continuously monitored and adjusted as\r\nnecessary by FATMGR.EXE to ensure that the drive never runs out of physical\r\nspace while OS/2 thinks it still has logical free space (free clusters) left.\r\n\r\nEven if DONT_DEL.ME is huge, it's not using up any physical space on your\r\nStacker drive -- it's just making sure OS/2 won't try to write data to the\r\ndrive when there isn't enough room. Deleting it won't let you fit more data\r\non the drive, and FATMGR will just create it again in a few seconds anyway.\r\nHence the name DONT_DEL.ME!\r\n\r\nWhen a Stacker drive is almost full, FATMGR increases the size of DONT_DEL.ME\r\nmore aggressively due to the greater risk of running out of space. This\r\neffectively limits the capacity of small (less than 5 megabyte) Stacker\r\ndrives, since they're treated as almost full from the outset.\r\n\r\nDONT_DEL.ME is automatically deleted when OS/2 shuts down, and also when\r\nDOS boots up (the latter is courtesy of the CHECK /WP line in the DOS\r\nAUTOEXEC.BAT). A different method is used under DOS for managing the free\r\nspace, so it's not appropriate to have DONT_DEL.ME present under DOS.\r\n\r\n19.1 CHECK and CHKDSK error messages related to DONT_DEL.ME\r\n\r\nYou may see CHECK and CHKDSK report errors such as \"File length error\" on the\r\nDONT_DEL.ME file. These are generally harmless and are due to the file not\r\nhaving been closed since the last time its length changed. There would be a\r\nsubstantial performance impact if FATMGR closed DONT_DEL.ME each time the\r\nfile length changed.\r\n\r\nIf you run CHKDSK /F on a Stacker drive under OS/2, CHKDSK may report that it\r\ncannot access the drive because it is locked or in use by another process.\r\nThis may be because DONT_DEL.ME is open. Wait 10 to 20 seconds and try\r\nrunning CHKDSK again; if no other programs are writing or deleting files on\r\nthat drive, FATMGR will close DONT_DEL.ME in the meanwhile and CHKDSK /F\r\nshould proceed.\r\n\r\n20.0 Creating large Stacker drives\r\n\r\nThis section covers some situations you may run into when creating large\r\nStacker drives, i.e., larger than 512 megabytes.\r\n \r\n20.1 Two Stacker drives created when one is requested\r\n\r\nWhen you compress a large drive, you may find that you end up with two\r\nStacker drives instead of just one. The reason is that we avoid using 16K\r\nclusters (the units in which space is allocated to files) if we can use 8K\r\nones, and avoid using 32K ones if we can use 16K. Smaller clusters can allow\r\nmore data to be stored on a drive, but they limit the size of the drive; 8K\r\nclusters allow up to a 512 megabyte drive, and 16K clusters allow up to a 1\r\ngigabyte drive. When you compress an entire drive, the existing data on the\r\ndrive always goes onto a single drive, regardless of the cluster size that\r\nrequires.\r\n\r\nYou can enforce a given cluster size when creating a new Stacker drive by\r\ngoing into SETUP's Advanced Options (during a Custom Setup) and selecting\r\nthat cluster size.\r\n\r\n20.2 SETUP running out of memory\r\n\r\nIf you attempt to create a Stacker drive with 16K or 32K clusters by\r\ncompressing a drive that has 32K clusters and has extended attributes on\r\nit, you will probably get an \"insufficient memory\" error message and the\r\nStacker drive will not be created. The workaround is to remove enough data\r\nfrom the drive you wish to compress so that it has less than 1,024,000,000\r\nbytes of data on it, and rerun SETUP to compress the drive. SETUP will now\r\ncreate two Stacker drives with 16K clusters, as described above in section\r\n20.1.\r\n\r\n21.0 For users of systems with OS/2 pre-installed\r\n\r\nIf your system was preloaded with OS/2, then it probably didn't come with\r\nOS/2 installation diskettes. In that case, you need to make your own OS/2\r\nutility diskettes and use copies of those diskettes whenever the Stacker for\r\nOS/2 & DOS User's Guide asks you to use copies of the OS/2 installation\r\ndiskettes. With at least some systems, the procedure for making the utility\r\ndiskettes is documented in a manual called \"Using the Welcome Folder,\" in a\r\nsection called \"Creating Utility Diskettes.\"\r\n\r\nThe procedure for creating utility diskettes results in three diskettes,\r\nwhich are supposed to be labeled Utility Diskette 1, 2, and 3. Use Utility\r\nDiskette 1 whenever the Stacker for OS/2 & DOS User's Guide tells you to use\r\nthe OS/2 Installation Diskette, and use Utility Diskette 2 whenever the\r\nUser's Guide tells you to use OS/2 Diskette 1.\r\n\r\nYou'll need copies of the first two Utility Diskettes in order to run\r\nSTACBOOT, which will turn them into \"Stacker-aware\" OS/2 boot diskettes that\r\ncan be used to repair errors on drives that might otherwise be locked if you\r\nbooted in the usual way.\r\n\r\n21.1 Unscrambling the OS/2 logo screen\r\n\r\nIf your system was preloaded with OS/2, then you may get garbage on your\r\nscreen early in the process of booting of OS/2 if you've compressed the OS/2\r\nboot drive. This doesn't affect the operation of OS/2 or Stacker, but you can\r\nuse this command to clean up the screen:\r\n\r\n XCOPY od:\\OS2\\INSTALL\\PRELOAD\\WELCOME.RGB ud:\\OS2\\INSTALL\\PRELOAD\\\r\n\r\nwhere od: is the compressed OS/2 boot drive and ud: is the corresponding\r\nuncompressed drive. You can determine the latter by running SWAPMAP in a DOS\r\nsession under OS/2. For example, if C: is the compressed OS/2 boot drive,\r\nSWAPMAP might display the following (among other information):\r\n\r\n Drive C: was drive E: at boot time\r\n Drive E: was drive C: at boot time\r\n\r\nThis tells you that the uncompressed drive is E:. You would then enter\r\n\r\n XCOPY C:\\OS2\\INSTALL\\PRELOAD\\WELCOME.RGB E:\\OS2\\INSTALL\\PRELOAD\\\r\n\r\n22.0 Running DOS from a disk or disk image within OS/2\r\n\r\nThe information in this section applies to running a specific version of DOS\r\nfrom within OS/2. For example, you can start up an MS-DOS 4.0 session by\r\ninserting an MS-DOS 4.0 boot diskette in the A drive and double-clicking on\r\nthe \"DOS from Drive A:\" icon in the Command Prompts folder. In general, you\r\ncan start up such a DOS session from a diskette, from a hard drive (normally\r\nC:), or from a disk image created by VMDISK.\r\n\r\nThis section does not apply to regular DOS Window or DOS Full-screen sessions\r\nwithin OS/2, nor does it apply to rebooting from OS/2 to DOS on a Dual Boot\r\nsystem via the BOOT /DOS command or the Dual Boot icon.\r\n\r\nWhen running a specific version of DOS within OS/2, you can access all the\r\nStacker drives in that session that you can normally access in OS/2, provided\r\nthe CONFIG.SYS used by that session contains a DEVICE=FSFILTER.SYS line.\r\nOS/2's on-line help contains further information on FSFILTER.SYS.\r\n\r\nThe results are unpredictable if you run DOS in this manner from a disk or\r\ndisk image that itself mounts Stacker drives or runs Stacker utilities. You\r\nshould make sure the disk's CONFIG.SYS doesn't load STACKER.COM or SSWAP.COM\r\nand that its AUTOEXEC.BAT doesn't run CHECK, before booting DOS from it\r\nwithin OS/2.\r\n\r\n23.0 GammaTech utilities\r\n\r\nA trap 000E with possible data corruption may occur if you try to run the\r\nGammaTech Analyze, Sector-Edit, or Sentry utilities on a Stacker drive. The\r\nutilities themselves may be stored a Stacker drive, but you should not tell\r\nthem to operate on a Stacker drive.\r\n\r\n24.0 Customizing Stacker for international use\r\n\r\nBy default, Stacker uses a standard United States keyboard and conventions\r\nfor date, time, and characters. You can tell Stacker that you use a different\r\nkeyboard layout and request country-specific conventions for date, time, and\r\ncharacters if necessary. The \\INTL directory on Stacker for OS/2 & DOS Disk 1\r\nincludes new files for use in these countries:\r\n\r\n Code Country\r\n FR France\r\n GR Germany\r\n IT Italy\r\n JA Japan\r\n NL Netherlands\r\n PO Portugal\r\n SP Spain\r\n UK United Kingdom\r\n ENG To revert to the standard English version after changing it\r\n\r\nBEFORE RUNNING SETUP FOR THE FIRST TIME:\r\n\r\nModify Stacker for OS/2 & DOS to suit your computer following these steps:\r\n\r\n1. Start your computer as usual.\r\n\r\n2. Get to a DOS command line; a DOS session within OS/2 is fine.\r\n\r\n3. Insert Stacker for OS/2 & DOS Disk 1 into drive A.\r\n\r\n4. Type A:\\INTL\\LANGUAGE code where code is one of the choices in the table\r\n above (for example, A:\\INTL\\LANGUAGE GR for Germany) and press ENTER.\r\n\r\n5. Restart your computer using this disk to run SETUP.\r\n\r\nWhenever your computer restarts into DOS from this disk, it will use the\r\nappropriate keyboard and country settings.\r\n\r\nThe LANGUAGE batch file runs the KEYB and COUNTRY commands to make your\r\ncomputer respond appropriately. KEYB specifies the keyboard layout in use,\r\nwhile COUNTRY determines the appropriate date, time, currency, character\r\nsort, and filename validity for the computer.\r\n\r\nUsing any keyboard other than the standard United States English layout uses\r\na bit more memory. If you find that you run out of memory after customizing\r\nit for your language, use A:\\INTL\\LANGUAGE ENG to restore it to the default\r\nsettings. You'll be able to use it, but the keyboard and displayed values\r\nwill be in their default state.\r\n\r\n25.0 Determining free space requirements \r\n\r\nCurrently Setup allows you to compress an entire drive as long as you have at\r\nleast 1% plus 45K free, or compress free space if you have at least 100K\r\nfree. However, if you are trying to compress a drive that has particularly\r\nlarge clusters, you may receive an error message indicating that Setup cannot\r\ncontinue because the disk is full. If this happens to you, you can use the\r\nfollowing procedure to determine the free space requirements.\r\n\r\n1. Determine the Number of Sub-Directories using the CHKDSK command.\r\n This is the \"Number of Directories\" (not the bytes).\r\n Write that number here._________________________________\r\n2. Determine Stacker's Working Drive Size using the CHKDSK command.\r\n This is the \"Bytes Total Disk Space.\"\r\n Write the number of bytes here._________________________\r\n3. Determine the amount of data you have on your disk using the CHKDSK\r\n command. This is:\r\n Bytes determined in #2 _____________________________\r\n - \"Bytes Available on Disk\"_____________________________\r\n = _____________________________\r\n4. Determine the STACVOL cluster size on your drive in bytes using the\r\n following table. Locate your drive size (the number of bytes determined\r\n in #2) in the first column. Locate your data size (the number of bytes\r\n determined in #3) underneath the Data Size heading. The cluster size for\r\n your drive is displayed in the column beneath the range in which your\r\n data size falls.\r\n Write the number of bytes here.________________________\r\n\r\n Drive Size | Data Size\r\n |0 - 1,023,999,999 |1,024,000,000 - 2,147,483,648\r\n | STACVOL Cluster Size\r\n----------------------------------------------------------------------------\r\n 0 - 460,799,999| 8,192 | N/A\r\n460,800,000 - 921,599,999| 16,384 | N/A\r\n921,600,000 - 2,147,483,648| 16,384 | 32,768\r\n----------------------------------------------------------------------------\r\n\r\n5. Multiply the number from #1 by the number of bytes from #4.\r\n Write that value here.________________________\r\n6. Multiply .006 by the number of bytes from #2.\r\n Write that value here.________________________\r\n7. Add the two values calculated in #5 and #6. This is the free space\r\n requirement for compressing the drive.\r\n Write that value here.________________________\r\n8. Remove data from your drive until the amount of free space you have on\r\n your disk (see #3) is at least this size." }