Liren Large Software Subsidy 16

home *** CD-ROM | disk | FTP | other *** search

/ Liren Large Software Subsidy 16 / 16.iso / t / t103 / 1.ddi / ONLINE.HLP < prev next >

Wrap

Text File | 1988-10-28 | 27.9 KB | 487 lines

DISK MANAGER HELP INFORMATION, REVISION 1.0 #----------------------------------------------------------------------- # HELP FOR THE DISK MANAGER MAIN MENU #MSG01 The CONFIGURATION MENU is generally the first option taken from here. This menu will allow you to be certain that DISK MANAGER is completely aware of the size of the hard disk(s) on your computer. The INITIALIZATION MENU performs all initialization, or "low-level-format" functions on your hard disk(s). This initialization process is required prior to any partitioning or preparation options. The PARTITIONING MENU allows you to arrange the size/location of the various "partitions" on your hard disk(s). The partitions then become the various logical drives (C:, D:, etc.) on your system. This menu also allows you to proceed to the PREPARATION MENU, where these partitions are readied for DOS. SELECT DRIVE will allow you to select either physical disk, if you have two. #----------------------------------------------------------------------- # HELP FOR THE INITIALIZATION MENU #MSG02 All hard disks require a "low-level-format" to be written on them before they become useable for storing data. DISK MANAGER allows you to create that "low-level-format" through a process called INITIALIZATION. Generally, you will first want to use the DEFECT-LIST MANAGEMENT menu to identify to DISK MANAGER all tracks on your hard disk(s) which contain flaws. Then, you will want to use the INITIALIZATION function to actually perform the initialization. NOTE THAT THE INITIALIZATION PROCESS DESTROYS ANY DATA ON THE HARD DISK ! The VERIFY option is available to test the integrity of the low level format. #----------------------------------------------------------------------- # CONFIRMATION OF THE DEFECT-LIST PRIOR TO INITIALIZATION #MSG03 DISK MANAGER uses the defect-list to determine whether any given track should be initialized as defective or not. The currently displayed defect list should be an accurate replica of the defect-information supplied with the disk drive. Otherwise, DISK MANAGER will only mark as defective those tracks which have such serious defects that they cannot be properly initialized at all. This can possibly cause some defective areas to be used for data storage, with the risk of loss of data at some later point in time. IF THE DEFECT-LIST IS NOT ACCURATE, DO NOT CONTINUE WITH THE INITIALIZATION PROCESS UNTIL THE DEFECT-MANAGEMENT MENU IS USED TO CORRECT THE DEFECT-LIST. #----------------------------------------------------------------------- # HELP FOR CHOOSING WHETHER TO INIT/VERIFY TRACKS, PARTS, OR DISKS #MSG04 INITIALIZATION and VERIFICATION functions can be performed on any of the following categories: (D)isk--usually used on a new installation in order to subject the ENTIRE disk to the verification or initialization process. (P)artition--usually used when the integrity of a single partition is in question, or if a desired partition is to have a different interleave value than other areas on the disk. (T)rack--single track initialization/verification can be used as a diagnostic procedure if you have troubles installing a disk. (i.e. if you are unable to initialize, then verify cylinder 0, head 0, you have a very basic problem with the disk subsystem.) #----------------------------------------------------------------------- # HELP FOR THE DEFECT-LIST MANAGEMENT MENU #MSG05 The GET and WRITE options allow saving/retrieving the DEFECT-LIST to/from your DISK MANAGER diskette. The files used are named FLAW1.MAP and FLAW2.MAP, and can also be copied to a printer to produce a paper-list of defects. The CLEAR, ADD, and DELETE options are used to manipulate the DISK MANAGER DEFECT-LIST so it agrees with the DEFECT-LIST which accompanied your disk drive from its manufacturer. This list may have been on a separate sheet of paper, or it may be physically attached to the disk drive itself. The SCAN option can be used to create a DEFECT-LIST which lists all tracks that cannot be successfully verified. This test will not itself destroy any data, however, THE HARD DISK MUST BE INITIALIZED PRIOR TO USING THE SCAN OPTION. #----------------------------------------------------------------------- # DOES THE PARTITION TABLE NEED MODIFICATION? #MSG06 A new disk installation will have NO VALID PARTITION TABLE, and you must respond "Yes" to this prompt to create a NEW PARTITION TABLE. If you have already established a partition table, but wish to change the type, select as boot, or otherwise rearrange the partition assignments, you will also want to respond "Yes". If you wish to leave the current PARTITION TABLE as it is, you may respond "No" to this prompt, and you will continue into the PREPARATION MENU. #----------------------------------------------------------------------- # HELP FOR THE PREPARATION MENU #MSG07 Preparation of a partition is equivalent to the DOS "FORMAT" process. This MUST be performed on all partitions of type DOS, WRITE-READ, or READ-ONLY, or DOS will not be able to store files on them. The legitimacy of the "PREPARATION" can be CHECKED with the (C) option. Also, the text in the partition table under NAME-VER column will indicate "UNPREPARED" if the preparation has not been performed. #----------------------------------------------------------------------- # DO YOU WISH TO USE THE DEFAULT PARTITION TABLE ? #MSG08 Disk Manager can assign a DEFAULT PARTITION TABLE for you. The default partition table will divide the disk into approximately 10 MB partitions. If you choose to NOT use the default partition assignments, DISK MANAGER will allow you to assign partitions interactively. Generally, most installations require 1 type DOS partition on the first disk. This partition must be smaller than 33.5 MB total size, and will usually be the BOOT partition. If you have a NONSTANDARD disk drive, this partition will use ONLY those heads which are specified by the SETUP size of your disk. Therefore, if you have a NONSTANDARD disk with a number of heads different than the SETUP size, you will want to make the DOS partition very small (the DISK MANAGER default will be large enough to hold all your DOS files, etc.) to minimize unused disk space. #----------------------------------------------------------------------- # HELP FOR THE PARTITIONING MENU #MSG09 NEW PARTITION TABLE is used to create the table itself. This must be performed at least once on a new installation. The table may then have new assignments allocated, deleted, changed in type, or boot-selection performed. ALLOCATE will create a new partition assignment. DELETE will delete any partition assignment. SELECT will cause any partition (1-4) to be selected for subsequent boot-up. CHANGE is generally used to change partitions from WRITE-READ to READ-ONLY status. #----------------------------------------------------------------------- # CONFIRMATION OF WRITING CONFIGURATION INFO TO THE DISK #MSG10 If you change miscellaneous parameters, add a disk drive, or otherwise alter the disk subsystem configuration, you must WRITE the new configuration information to the disk. The new configuration will then be recognized by DISK MANAGER on subsequent re-boots. If this is a new installation, please remember that the configuration information cannot be written to the disk by DISK MANAGER until the disk is initialized. Further, remember that the configuration information is automatically written by DISK MANAGER any time an initialization is performed on cylinder 0, head 0. #----------------------------------------------------------------------- # HELP FOR THE CONFIGURATION MENU #MSG11 The Configuration Menu is used to help you identify the actual disk parameter information to ensure that DISK MANAGER installs your disk correctly. Your configuration is STANDARD if all disks have parameters that are correctly displayed on the upper half of the configuration screen. If you have any disks which have other parameters, you will need to either re-configure the switches on your controller card (XT), re-run the computer SETUP process (AT), or use the NONSTANDARD option of this menu to allow DISK MANAGER to correctly utilize your hard disk(s). #----------------------------------------------------------------------- # ENTER MODEL-CODE FOR YOUR DISK DRIVE #MSG12 DISK MANAGER-SEAGATE provides CONFIGURATION DATA for many SEAGATE hard disks. The mechanism below should be used to inform DISK MANAGER which hard disk(s) you are using. If your disk drive is in fact a STANDARD disk (one that is DIRECTLY supported by the BIOS of your particular computer) then you may inform DISK MANAGER that the drive in question is STANDARD by just striking "Return". If your disk drive is a SEAGATE hard disk from the table below, respond with the MODEL CODE associated with the model of your drive, then strike "Return". #----------------------------------------------------------------------- # DO YOU WISH TO PRESERVE EXISTING PARTITION DATA ? #MSG13 You have asked DISK MANAGER to create a NEW PARTITION TABLE in the DISK MANAGER format. DISK MANAGER has noticed that you currently DO have a valid partition table, and is giving you the option of transferring the partition information from that table to the new one about to be created. Respond "Yes" to this prompt if you wish to save the existing partition data. Respond "No" if you have no need to transfer that data to the new partition table. #----------------------------------------------------------------------- # DO YOU WISH TO WRITE THE ABOVE PARTITION TABLE TO THE DISK? #MSG14 If you are confident that any changes that have been made to the partition table are desirable, respond "yes" to this prompt. If you have altered partition table entries which specified partitions that contain any valuable data, that data will be LOST ! If this is the case, you should respond "NO" to this prompt, and back-up your valuable data before altering the partition table. THE NEW PARTITION TABLE WILL BECOME EFFECTIVE AFTER YOU WRITE IT TO THE DISK AND THEN RE-BOOT YOUR SYSTEM. #----------------------------------------------------------------------- # SPECIFYING INTERLEAVE DURING INITIALIZATION #MSG15 INTERLEAVE is a term which refers to the ORDER in which physical sectors on the disk are used. Generally, the DISK MANAGER default value takes into consideration the controller-type and the computer-type being used. Therefore, most applications should use this. If you have unique hardware or software considerations, and have insight into an INTERLEAVE value which may give better performance, you may enter the interleave value here. TERMINOLOGY DIFFERS AMONG THE DISK-DRIVE COMMUNITY. DISK MANAGER USES THE INTERLEAVE OF 1 (ONE) TO INDICATE A NONINTERLEAVED FORMAT, INTERLEAVE OF 2 (TWO) TO INDICATE EVERY-OTHER-SECTOR, ETC. #----------------------------------------------------------------------- # ENTER NUMBER OF CYLINDERS FOR A PARTITION #MSG16 The number of cylinders occupied by a partition determines its ultimate storage capacity. The bottom line of the screen indicates the number of kilobytes (1000 kilobytes = 1 megabyte) each cylinder can store. Remember, the DOS format has some associated overhead, so the resulting logical drive will have slightly smaller useable data storage space. The DISK MANAGER default for DOS-type partitions will be about 850 kbytes. The DISK MANAGER default for WRITE-READ/READ-ONLY partitions will be as large as possible without exceeding the 33.5 MB limit. To produce a partition which is as large as possible, just type in a large number, such as 9999. #----------------------------------------------------------------------- # DO YOU WANT TO PLACE A SYSTEM ON THIS PARTITION? #MSG17 You will want to place a system on the partition if you ever expect to boot your system from the partition. Therefore, the DOS partition (on the first disk if you have two) will generally have a system placed on it. You will be asked by DISK MANAGER (at the appropriate time) to put your system diskette into the disk drive and continue. DISK MANAGER will then copy the vital system files from that diskette to the partition being prepared. If you don't wish to ever boot from the partition, there is no need to place a system on it. #----------------------------------------------------------------------- # ENTER 1-11 CHARACTER VOLUME LABEL #MSG18 A volume label is an optional 11-character "LABEL" that you can specify (optionally) for each logical drive. This "LABEL" will appear on directory listings of the drive, as well as "CHKDSK" listings, etc. It is strictly a convenience feature, but many users find it useful to specify a meaningful "LABEL" for each drive. #----------------------------------------------------------------------- # DO YOU WISH TO PRESERVE EXISTING FLAW-MAP ENTRIES? #MSG19 If you do not "preserve" the existing entries, the DEFECT-LIST will be completely cleared prior to performing the SCAN. ONLY unreadable tracks which were encountered during the SCAN process will be left in the list when the SCAN completes. If the existing DEFECT-LIST was exactly the same when the disk was first initialized with DISK MANAGER, all defective tracks should already be initialized as defective, and therefore will be detected as defective during the execution of SCAN. If you have entries in the DEFECT-LIST which are in addition to those used to initialize the disk, you may wish to "preserve" them in the list by responding "Yes" to this prompt. ******* PLEASE NOTE THAT SCAN IS A PASSIVE READ PROCESS, AND THE ******* ******* DISK MUST BE INITIALIZED BEFORE SCANNING IS MEANINGFUL. ******* #----------------------------------------------------------------------- # SPECIFYING A BOOT PARTITION #MSG20 Enter the number of the partition that you wish to have BOOT-up when the system boots from hard disk. #----------------------------------------------------------------------- # SPECIFYING A PARTITION'S TYPE #MSG21 DOS partitions are necessary to boot the operating system. They must be less than 33.5 MB in size, and cannot utilize the extra disk space of NONSTANDARD disk drives. NOTE that if you have a NONSTANDARD disk with a head-count different from that of the SETUP disk type (see CONFIGURATION MENU), then the DOS partition should be as small as possible to minimize wasted disk space. WRITE-READ partitions cannot be booted directly, but can use the full capacity of NONSTANDARD drives, and can be larger than 33.5 MB in size. READ-ONLY partitions are similar to WRITE-READ, but files can NOT be added, deleted, or altered from DOS-- they are "WRITE-PROTECTED". OTHER partition types can be specified if you know the "SYSTEM-TYPE" value for that particular system. Most systems, however, provide their own utility program ("FDISK", etc.) for allocating partitions for that system. #----------------------------------------------------------------------- # CHANGING A PARTITION'S TYPE #MSG22 The DISK MANAGER change-type function is generally used to change the status of a WRITE-READ partition to READ-ONLY, after the associated logical drive has been filled with data files which need to be write-protected. Also, if it becomes necessary to change a file(s) on a READ-ONLY partition, this option will be used to change it back to a WRITE-READ partition. THE NEW PARTITION STATUS WILL BE IN EFFECT AFTER YOU RE-BOOT. #----------------------------------------------------------------------- # SPECIFYING THE TYPE OF DISK DRIVE BEING USED #MSG23 If this disk drive is a STANDARD disk drive, you may just strike "Enter" at this prompt. The system will then use the drive parameters as defined by your computer's disk subsystem BIOS. Alternatively, DISK MANAGER has the capability of dealing with drives as specified below, even though your computer's disk subsystem BIOS may not normally be able to support them. If you are using one of these "NONSTANDARD" drives, use the mechanism below to specify which drive you are using. #----------------------------------------------------------------------- # DO YOU WISH TO MODIFY THE DRIVE PARAMETERS ? #MSG24 If your disk drive is a different model than the options presented to you earlier, or if you have a unique hardware requirement, you may modify the disk-drive parameter table, below, to reflect your desired changes. In most cases, however, DISK MANAGER will default all parameters to values appropriate for your hardware configuration. #----------------------------------------------------------------------- # IS THE DISPLAYED CMOS INFORMATION CORRECT? #MSG25 DISK MANAGER has detected a condition where NO hard disks are responding. This can be caused by hardware problems (cables, jumpers being defective or incorrectly installed), or by incorrect information in the system CMOS configuration memory (PC-AT type computers only). If you wish to change the CMOS configuration memory, you may respond "Yes" to this prompt and be given an opportunity to reconfigure the CMOS. Otherwise, you may respond "No" to terminate DISK MANAGER and determine the reason that NO hard disks are responding. REMEMBER --ONLY DISKS WHICH ARE ATTACHED TO THE TRUE IBM-PC-AT COMPATIBLE CONTROLLER CARD SHOULD BE ACCOUNTED FOR IN THE CMOS CONFIGURATION MEMORY. #----------------------------------------------------------------------- # WHICH DISK DO YOU WANT TO INSTALL? #MSG26 DISK MANAGER has detected the presence of more than 1 physical hard disk on this computer system. Please respond with the number of the hard disk drive which you wish to run DISK MANAGER on. If you wish to use DISK MANAGER to install more than 1 disk drive, you must run DISK MANAGER once on each drive. If you have additional drives which DISK MANAGER does not detect, please inspect your cables, jumpers, etc. Also, be sure that your CMOS configuration memory correctly describes the number of PC-AT compatible drives attached to the native PC-AT controller card (PC-AT type machines only). #----------------------------------------------------------------------- # CHOOSE ONE OF THE DEFAULT PARTITIONING MODES #MSG27 DISK MANAGER offers 3 automatic partitioning algorithms, as follows: (OTHER PARTITIONING ALGORITHMS ARE POSSIBLE WITH DISK MANAGER MANUAL MODE) A) As much of the entire physical disk as possible is made into 1 LARGE PARTITION. This will be larger than the DOS 33.5 MB limit on large drives. B) Partitions of EXACTLY THE 33.5 MB DOS LIMIT will be assigned. There may be a "leftover" partition as well. C) Enough EQUALLY SIZED partitions will be created such that the DOS 33.5 MB limit will not be exceeded. ("PARTITIONS" then become accessible from DOS as unique drive-letters.) NOTE THAT 1 UNDER 33.5 MB PARTITION IS REQUIRED ON DRIVE 1 FOR BOOT CAPABILITY! #----------------------------------------------------------------------- # HOW MANY HARD DISKS ARE ATTACHED TO THE AT-COMPATIBLE CARD? #MSG28 Respond with the number of PHYSICAL hard disks (0,1,or 2) connected to this system's AT- compatible controller card. DO NOT count any hard disks which are attached to various other types of controller cards. The information you supply here will be used to set the CMOS configuration data within your computer system. REMEMBER --ONLY DISKS WHICH ARE ATTACHED TO THE TRUE IBM-PC-AT COMPATIBLE CONTROLLER CARD SHOULD BE ACCOUNTED FOR IN THE CMOS CONFIGURATION MEMORY. #----------------------------------------------------------------------- # DO YOU WISH TO ENTER THE BAD-TRACK MAP FOR THIS DRIVE? #MSG29 Most disk drives come with a manufacturer-supplied list of defective tracks. DISK MANAGER will ensure that these areas are correctly de-allocated if you enter them. If not, some of the more severe defective tracks may be detected by DISK MANAGER, but the less severe defects may go undetected. Since these less severe defects may cause trouble after installation, we recommend that you take the time to enter them now. DISK MANAGER also provides a mechanism to allow you to (W)rite this defect list on diskette. Therefore, once they are entered, if you should ever need to re-create the list to re-install at a later date, etc., the tedious task of re-entering them can be avoided by (G)etting them off the diskette again. NOTE that the diskette file FLAWX.MAP (X= drive number) contains the saved information, and can be edited or printed if needed. #----------------------------------------------------------------------- # ONLY 1 DRIVE DETECTED, IS THIS CORRECT? #MSG30 If there is currently only 1 hard disk on the system, then you may respond "Yes" to this prompt. The drive 1 installation process will then proceed. If you have more than 1 disk drive on your computer then you should respond "No" to this prompt, and determine why DISK MANAGER is only detecting 1 drive. DISK MANAGER will assist in making that determination wherever possible. If you respond "No", and you are on a PC-AT type computer you will proceed to a facility that allows you to manipulate the CMOS configuration data kept within your computer. #----------------------------------------------------------------------- # IS THE SHOWN CMOS DISK DRIVE CONFIGURATION DATA NEED TO BE CHANGED? #MSG31 DISK MANAGER has detected only 1 hard disk which responds. If multiple hard disks are installed but not responding, this can be caused by hardware problems (cables, jumpers being defective or incorrectly installed, etc.), or by incorrect information in the system CMOS configuration memory. If you wish to change the CMOS configuration memory, you may respond "Yes" to this prompt and be given an opportunity to reconfigure the CMOS. Otherwise, you may respond "No" to terminate DISK MANAGER and determine the reason that other hard disks are not responding. REMEMBER --ONLY DISKS WHICH ARE ATTACHED TO THE TRUE IBM-PC-AT COMPATIBLE CONTROLLER CARD SHOULD BE ACCOUNTED FOR IN THE CMOS CONFIGURATION MEMORY. #----------------------------------------------------------------------- # WARNING EXPLANATION FOR SETUP-TYPE INCONSISTENCY (NON-FATAL) #MSG32 DISK MANAGER has detected a situation in which the drive type (which was specified during the computer's SETUP process) is NOT IDEAL for use with the specified DISK DRIVE MODEL. Specifically, there is a type in your system BIOS which is compatible with this drive and has a head count which is closer to the drive's actual head count. If you respond "Yes", DISK MANAGER will automatically re-configure your CMOS configuration memory for this other type. You may respond "No" to proceed with the installation using the type currently selected. #----------------------------------------------------------------------- # WARNING EXPLANATION FOR SETUP-TYPE INCONSISTENCY (FATAL) #MSG33 DISK MANAGER has detected a situation in which the drive type (which was specified during the computer's SETUP process) is NOT COMPATIBLE with the attached drive. If you respond "Yes", DISK MANAGER will automatically re-configure your CMOS configuration memory for a compatible type, then continue with installation. You may respond "No" to abort the installation process. We would then recommend re-running the computer's SETUP process to choose a drive type which is SMALLER OR EQUAL to the size of your disk in BOTH the head- and cylinder- counts. ALSO, if your drive has 9 or more heads, the chosen type must have WRITE PRECOMPENSATION turned off, or an "08" for the control byte. #----------------------------------------------------------------------- # CHOOSING ROOT DIRECTORY SIZES #MSG34 DISK MANAGER allows customization of the size of your ROOT DIRECTORY. This size can be designated when preparing the partition, and, once established, it cannot be changed without repreparing the partition and destroying all the data in that partition. The default value shown in the prompt is that which the operating system now in use would have utilized for a partition of this size. You may accept that default, or, if you wish, choose an alternate root-directory size. SINCE SOME APPLICATIONS DEPEND UPON GIVEN ROOT-DIR. SIZES, THE USER ASSUMES ALL RESPONSIBILITY FOR INCOMPATIBILITY IF VALUES OTHER THAN THE DEFAULT ARE USED. #-------------------------------------------------------------------------- # CHOOSING CLUSTER SIZES #MSG35 DISK MANAGER allows customization of the CLUSTER-SIZE. The CLUSTER-SIZE is the fundamental "allocation unit" DOS will use when creating files. ALL FILES will consume useable disk space in multiples of this CLUSTER-SIZE. Therefore, if you anticipate using SMALL files, the efficiency of disk space utilization will generally be better if a smaller CLUSTER-SIZE is chosen. Alternatively, larger CLUSTER-SIZES frequently result in better performance for larger files. The maximum and minimum permissible values are displayed in the prompt. The default value shown in the prompt is that which the operating system now in use would have utilized for a partition of this size. SINCE SOME APPLICATIONS DEPEND UPON GIVEN CLUSTER-SIZES, THE USER ASSUMES ALL RESPONSIBILITY FOR INCOMPATIBILITY IF VALUES OTHER THAN THE DEFAULT ARE USED. #----------------------------------------------------------------------- # WARNING EXPLANATION FOR SETUP-TYPE INCONSISTENCY (CONFIG MENU) #MSG36 DISK MANAGER has detected a situation in which the drive type (which was specified during the computer's SETUP process(AT) or by setting controller card switches/straps (XT)) is NOT COMPATIBLE with the attached drive. Generally, a situation like this will eventually lead to one or both of the following symptoms. 1) 1790 DISK ERROR when booting the computer 2) An inability to successfully prepare any DOS partitions We recommend re-running the computer's SETUP process to choose a drive type which is SMALLER OR EQUAL to the size of your disk in BOTH the head- and cylinder- counts. ALSO, if your disk over 8 heads, the chosen type must have WRITE PRECOMPENSATION turned off, or (AT ONLY) an "08" for the control byte. #----------------------------------------------------------------------- # DO YOU WISH TO START OVER WITH THE ORIGINAL PARTITION TABLE? #MSG37 DISK MANAGER has detected an aspect of the partition table that is not legitimate for this operating system. The bottom line on the screen should help identify what the problem is. You may start over with the partition table you had prior to entering this menu by responding "Yes". Or, you may go back to this menu and further modify the partition table to alleviate the problem by responding "No". Also, the following switches (useable ONLY on the DM command line) may be useful in altering DISK MANAGER's partition table legitimacy checks: /z -- Allows consistency with ZENITH MS-DOS partitioning rules. /w -- Allows consistency with WYSE-DOS partitioning rules. #----------------------------------------------------------------------- # WE HAVE A SWITCH-PROBLEM ON OUR HANDS #MSG38 DISK MANAGER has detected a condition where BOTH of your disk drives are configured to be the same drive-type. Since you specified that they are to be configured as having DISSIMILAR drive-parameters, DISK MANAGER is unable to cause the controller card to correctly support both drives. The condition can be cured by re-strapping the controller card such that DIFFERENT entries are selected for each of the two drives. DISK MANAGER will then be able to correctly install either or both of them as NONSTANDARD drives and correctly cause the controller card to recognize their respective drive-parameters.