Boston 2

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

/ Boston 2 / boston-2.iso / DOS / HILFEN / SYSTEM / RAMDISK3 / XDISK.DOC < prev next >

Wrap

Text File | 1993-12-01 | 38KB | 807 lines

┌─────────────────────────────────────────────────────────────┐ │ Trademarked names are the property of the respective owners │ └─────────────────────────────────────────────────────────────┘ Copyright (c) 1989, 1990, 1991, F.M. de Monasterio Licensed Material - All rights reserved xDISK version 3.00 ------------------ SUMMARY xDISK generates RAM disks in expanded memory and permits to vary the amount of memory allocated to the disk(s) without rebooting the computer when used with expanded memory conforming to the LIM 3.0+ specification (EMS). If DOS version 3.xx or higher is used, the RAM disk can be collapsed completely to free all of its EMS to another process (with DOS 2.10, the disk can be made as small as 16 kbyte [an EMS page]). Also, the RAM disk can be expanded to use all of the available EMS or any intermediate size multiple of 16 kbyte, sector size and number of root directory entries can be changed, and it can be made to show visual clues of its activity. Security features include making the disk a Read-Only or Read-Write device, locking/unlocking DOS access to the disk, and the enforcing of user-defined password checks before the implementation of any command to the disk. Requires DOS 2.1 or later and expanded memory conforming to the LIM EMS 3.0 or later. It is available in 086+, 286+, and 386+ CPU-type versions. ---------------- 1. GENERAL INFORMATION xDISK is a virtual-device driver system to generate (and modify) RAM disks in expanded memory conforming to Lotus/Intel/Microsoft specification version 3.0 or higher. Disk parameters can be modified without having to reboot the CPU, although the data on the disk are lost during any disk resizing. This system consists of two programs: (1) XDISK.SYS, a block device driver to be installed via CONFIG.SYS, after an EMS manager has been installed, and (2) XDISK.EXE, a utility to communicate with the device driver via DOS and, thus, to permit changing of one or more parameters of the specified xDISK RAM disk. The XDISK.SYS and XDISK.EXE files of a given version are matched and will not work with those of other versions of the program. Requires MS DOS/IBM-PC DOS version 2.1 or later, and an EMM complying with the EMS LIM 3+ specification. The 286 version of the program requires an 80286 CPU or higher; it is smaller and faster than the 086 version (any 80x86 CPU). The 386 version requires an 80386 CPU or higher; it is faster than the 286 and 086 versions. xDISK RAM disks are compatible with the CHKDSK utility of DOS as well as with other disk utilities (such as NDD) that sometimes encounter difficulties with other resizable RAM disks. Starting with version 2.50, the boot sector of the xDISK RAM disks complies with the DOS 4.0x format. 1.1 RAM DISK IDENTIFICATION & DOS VERSION DOS assigns the first available drive letter to a RAM disk within the default range A to E or, for DOS ≥3.00, the range A to Z if the command <LASTDRIVE=Z> is included in CONFIG.SYS. Such a letter is shown by XDISK.SYS when using DOS ≥3.00, but it is not shown when using an earlier DOS version. xDISK disks can be identified by the volume label and time of creation, as well as by the OEM identification in the boot sector, all of which are determined by the version | of xDISK. When executed in a CPU i286 or higher, the date of creation of the | RAM disk is the current date in the CMOS chip; for an 8088/8086 CPU, the date | of creation is that of the assembly of the xDISK version. 1.2 DIRECT DRIVER COMMUNICATION Starting with version 2.52, the device header of each XDISK.SYS installed has the string: [-1]xDISK[0]unit:[0]<d>[-1] where the start and ending delimiter bytes [-1] contain the hexadecimal value of 0FFh, the null separator bytes [0] contain 0, and the drive designator <d> is the upper-case letter assigned to this RAM disk (DOS ≥ 3.0) or a null byte (DOS < 3). The identifying string is used to locate the driver for direct communications between XDISK.EXE and XDISK.SYS. Note that when this string does not contain a designator letter (as when using DOS 2.10), switches /A, /P, /R, and /V can only be assigned to the first XDISK.SYS driver found in memory. | When XDISK.EXE is executed, the program searches memory for the corresponding | identifying string. When the correct drive is not specified or the driver has | been installed in upper-conventional memory, the search may extend as high as | the initial 1 Mb of memory (see below). ---------------- 2.0 COMMAND SYNTAX A. XDISK.SYS must be installed via the CONFIG.SYS file on the boot disk after the LIM-3+ EMS manager has been installed (the filename of such an EMS driver varies with the manufacturer, but its code must include the string EMMXXXX0): Device=[d:][\path\]XDISK.SYS [/B][/C][/D][/E][/L][/S] where <d:> and <\path\>, when specified, are the drive and path specification for the XDISK.SYS file. See below for an explanation of the switches. B. After the xDISK driver has been loaded and the RAM disk created, XDISK.EXE allows for modification of the RAM disk parameters from the DOS command line: XDISK [x:] [/A][/B][/C][/D][/E][/N][/P][/Q][/R][/S][/V][[/]?] x This is the drive designator letter, followed by <:>, that identifies the xDISK drive. The use of letters for non-xDISK drives and for non-existing drives generates separate error messages (IOctl error 1 and F). Defaults: Null drive, no colon or x=<ASCII 21-40> = Current drive letter. ---------------- 2.1 SWITCHES The switches are not case sensitive and most must be preceded by a slash [/]. If the RAM disk is being resized (i.e., /Bn/Sn/Dn/C/E), non-resizing switches must be specified AFTER the resizing switch(es). NOTE: When xDISK is invoked without any switch (or when the switches are not preceded by slashes [and thus are ignored]), the status of the xDISK drive is displayed on the DOS command line. Except during the XDISK.SYS installation, such a null-switch call does not change any RAM disk parameters. During xDISK installation, however, default values for switches /B, /D, and /S are used if the corresponding switch is not specified. ---------------------------------------------------------------------------- Asterisks mark switches available only in registered copies of xDISK ---------------------------------------------------------------------------- * A± Open [+] and close [-] the DOS-mediated access to the specified RAM disk. Defaults: /A = /A+. ------- Bn Disk size in kilobytes, where <n> is in the range between 16 and 32768 in 16-kbyte steps; when <n> is not a 16-kbyte multiple, size is increased to the nearest larger multiple available. Unless switch /Q or /N is enabled, this resizing change necessitates confirmation by the user. Defaults: In the CONFIG.SYS file, null switch or null <n> = /B64. In the command line of DOS, /B = /B64; null switch is ignored. ------- * C Collapses the RAM disk to a size of 0 kb (DOS ≥3.0) or 16 kb (DOS <3.0). Unless switch /Q or /N is enabled, collapse necessitates confirmation by the user; a 0-kb collapse does not change the existing /D and /S values, but a 16-kb collapse also sets /D=4 and /S=128. If a 0-kb collapse has occurred, a DOS-mediated request to the disk will trigger an error message of the following type for DOS 3.XX: Not ready error reading drive E Abort, Retry, Fail? whereas for DOS 4.0X some disk-access commands will trigger this message (e.g. 'CHKDSK E:'): Invalid drive specification Invalid media type and others this message (e.g. 'DIR E:'): Not ready reading drive E Abort, Retry, Fail? Answer the "Abort, Retry, Fail?" by pressing <A> to quit the DOS critical error handler and return to the DOS prompt. The "not ready" error message is a remainder that the RAM disk exists, but is collapsed. The 0-kbyte collapse can be restored only by using switch /B or /E; other switches do not change the disk size. The following EMS measurements were obtained as described by the headers: Upon booting with /B16/S128/D4: 2800 kbytes total EMS 576 kbytes used by process 0 16 kbytes used by process 1 <- 768 kbytes used by process 2 1440 kbytes free Upon collapsing disk with /C: 2800 kbytes total EMS 576 kbytes used by process 0 768 kbytes used by process 2 1456 kbytes free Upon expanding disk with /E: 2800 kbytes total EMS 576 kbytes used by process 0 1456 kbytes used by process 1 <- 768 kbytes used by process 2 0 kbytes free ------- Dn Number of allowed entries (files) in the root directory, where <n> is in the range between 4 and 512. If the minimum value of 4 entries has been selected, the number of entries is increased to 8 or 16 when a sector of size 256 or of 512 bytes is also selected. Unless switches /Q or /N are enabled, this resizing change necessitates confirmation by the user. | NOTE | If a sufficient number of entries is not available, commands to write to | the disk will trigger critical error messages of a 'File Creation Error' | To decrease this possibility, expanding the disk to the maximum EMS size | via switch /E changes the number of root directory entries to 512. If a | smaller number of entries is needed, follow switch /E with /Dn. Defaults: In the CONFIG.SYS file, null switch or null <n> = /D64. In the command line of DOS, /D = /D64; null switch is ignored. ------- * E Expands the disk to the maximum available EMS size. If switch /Dn is not | also specified, it sets the directory entries to /D512. Unless switch /Q or /N is enabled, this expansion necessitates confirmation by the user. ------- * Ln Instructs the program to load its resident in high memory between 640 kb | and 1,024 kb, i.e. below the 1 Mb boundary of conventional RAM but above | the memory area normally controlled by DOS. The switch requires that an | extended memory manager (XMM) supporting the services of the XMS 2.00 is | installed and that a free upper memory block (UMB) of a little less than | 2 kb is available. The XMM must support functions 10h (Allocate UMB) and | 11h (Free UMB). | | Unlike the high-memory loading provided by 386 memory managers, the size | of the free UMB is that of the resident, and not that of the entire code | of XDISK.SYS; a few additional bytes are used by XMS when allocating the | UMB. (See High Memory Installation section.) | | A low high-memory limit for the UMB can optionally be specified via <n>, | a hexadecimal number between A000 (640 kb) and FFFF (1,024 kb), so as to | avoid specific areas of upper memory with a slow access time. UMB access | times are provided by some memory managers, e.g., QEMM386 (Quarterdeck), | 386MAX (Qualitas), but not by others, e.g., HIMEM.SYS (Microsoft). More | detailed UMB-access timings are provided by the utility TIMEM.EXE, which | is enclosed in this software release of xDISK (see also TIMEM.DOC). | | Defaults: Lower-memory installation, if any errors are found during the | UMB loading. High-memory installation below requested lower limit if no | UMB is available above such limit. ------- * N Nulls the displaying of disk status, user confirmation request, and error messages; errors can still be detected within a batch file with the ERROR LEVEL command. Because the disk status display is generated by the driver via BIOS calls, the messages cannot be redirected by DOS; use of switch N produces the same result as a redirection to the NUL device. The RAM disk configuration parameters are preserved. ------- * Px± Demand password before implementing changes; password consists of 1 to 15 lower-case, pure alphanumeric characters followed by <Enter>. Use /Px to (re)define a password, where <x> is 1 to 15 alphanumeric lower-case [0-9, a-z] characters followed by a space; use /P- to disable and /P+ to enable the password requirement. Defaults: /P = /P+. | Pressing <Esc> or <Break> during password testing returns the user to the | DOS command line. The typing of an incorrect character during the testing | vitiates prior accepted (correct) characters, and the entire password has | to be retyped. Note that warmbooting via <Ctrl-ALt-Del> is not suppressed | during password testing (rebooting destroys the RAM disk data). | | The password is useful in situations when more than one user has acces to | the RAM disk (i.e., a server) and, after copying the common-access files, | the disk is made Read-Only to protect its contents. ------- Q Quiet resizing. Disables the default prompt for user's confirmation prior to disk resize/format operations that destroy all data on the RAM disk. ------- * R± Make the disk a Read-Only [+] or Read-Write [-] device; the current write status is indicated by [RO] or [RW] icons in the configuration message. A Read-Only status does not allow for file changes or resizing of the disk. RAM disk configuration parameters are preserved. Defaults: /R = /R+. ------- Sn Sector size in bytes, where <n> is 128, 256, or 512. Select a small value if storing small files; large values will reduce reading and writing time if storing larger files. Unless switch /Q or /N is enabled, this resizing change necessitates confirmation by the user. Defaults: In the CONFIG.SYS file, null switch or null <n> = /S256. In the command line of DOS, /S = /S256; null switch is ignored. ------- * V± Turn ON [+] or OFF [-] the display of a "" on the top-left corner of the screen whenever xDISK is active due to a DOS request. The disk parameters are preserved. If the display is on, the icon "" is displayed along with the drive status in answer to the switch /? or <d:>? (see below). ------- ? When preceded by a valid xDISK designator, ? or /? displays the status of the RAM disk. In the absence of a drive designator, ? displays the syntax help panel, while /? attempts to display the status of the default drive. It is the only switch that preserves a Read-Only status for the RAM disk. ---------------- 2.2 COMMENTS Comments may be added in the command after the desired switches. The comments (which may be useful in batch files) must be preceded by a semicolon (;), and are ignored by xDISK. NOTE: Do not use DOS redirection (<>) and pipe (|) characters in comments, as DOS will attempt to implement the implied redirection/pipe request. ---------------- 3.0 DOS ERRORLEVEL XDISK.EXE passes to DOS execution status values that can be tested in batch files via the ERRORLEVEL command; the following are values for version 2.52 or later: Value Condition ----- -------------------------------------- 255 Cyclical Redundancy Check failure 254 286 version executed in non-286+ machine 16 Invalid expanded memory manager/version 8 Unknown or invalid switch request 4 DOS access to driver has been closed 2 Invalid character is password string 1 Resize attempt of Read-Only disk 0 Succesful execution ---------------- 4. DRIVER INSTALLATION XDISK.SYS must be installed via CONFIG.SYS. In the registered licensed copy, the installation of XDISK.SYS can be skipped by pressing the <Esc> key before the initialization of the driver is completed, e.g., before the xDISK message is displayed. Such a keypress interrupts the installation until the following abort query in answered by pressing <Y> for 'YES' or <N> for 'NO': XDISK.SYS: <Esc> pressed ─ Abort installation? [yn] The avoidance of installation produces no memory penalty in DOS versions 3.30 or higher, and uses 80 bytes (286+ or 386+ version) of conventional memory in earlier DOS versions. | When XDISK.EXE is executed and the corresponding driver identification string | found, the memory segment of the (selected disk) xDISK driver is displayed in | the Help Status panel preceded by the initials UMB if the driver is installed | upper conventional memory. The memory segment of a lower-memory installation | is displayed only when the <F10>+<Alt> keys are pressed simultaneously. -------- 4.1 INSTALLATION ERRORS The following errors fail the installation of the driver: A. Invalid CRC - Driver has been corrupted | B. Invalid CPU type - Needs i286/i386 or higher C. Invalid DOS version - Needs 2.1 or later D. Failure to detect presence of an EMM driver E. Expanded memory allocation error (LIM code) F. Expanded memory EMM status error (LIM code) G. Expanded memory page frame error (LIM code) | See below for an explanation of driver error messages (section 6). -------- 4.2 HIGH-DOS MEMORY INSTALLATION DIRECT UMB LOADING | Starting with version 3.00, xDISK can load itself directly in high memory | (RAM addresses between 640 kb and 1,024 kb) via switch /L. Such a loading | is mediated by an XMS manager (XMM) version 2.0, such as the driver HIMEM | .SYS (Microsoft), which must be installed prior to the loading. Some 386- | memory managers (386MAX version 4.09, and QEMM version 5.11, for example) | provide XMS support as well. All XMMs require DOS version 3.0 or later. | | For the loading to be successful, an upper memory block (UMB) of the size | of the resident part of XDISK.SYS (about 2 kb) plus an additional 48-byte | block used by the XMM must be available. | | Switch /Ln, where A000 ≤ n ≤ FFFF (hexadecimal), allows the specification | of a lower high-memory bound for the UMB, to avoid high-memory areas with | a very slow access time. | | Hence, compared to the high-memory installation provided by some (but not | all) memory managers, direct UMB loading has two major advantages: (1) it | does not need an initial free block of high memory the size of the entire | program, as opposed to the resident size, to be available, and (2) allows | some user control on the selection of the high-memory block. -------- LOADING VIA 386-MEMORY MANAGERS The XDISK.SYS driver can also be loaded into high memory via 386-specific memory managers, provided that there is enough high-memory for the entire size of the driver plus any additional memory that may be required by the loading utility. 4.3 HIGH-DOS MEMORY UPDATING Updating the xDISK driver is accomplished either via DOS-mediated requests to the driver or via a direct updating of the driver by XDISK.EXE (without the intervention of high-DOS memory utilities). ---------------- | 5. MESSAGES of XDISK.EXE | | | 5.1 "Bad CRC: Code corrupted ─ Execution cancelled" | A failure of the 32-bit cyclical redundancy check was encountered when the | program was executed. | | -------- | | 5.2a "Cannot execute 286 code ─ Execution cancelled" | 286+ program versions cannot be executed in 8088, 8086 or (most) 80186 CPU | machines. | | -------- | | 5.2b "Cannot execute 386 code ─ Execution cancelled" | 386+ program versions cannot be executed in 8088, 8086, 80186 or 80286 CPU | machines. | | -------- | | 5.3 "Needs DOS 2.10 or later ─ Execution cancelled" | An MS-DOS/IBM-PC DOS version equal to or greater than 2.10 is required for | proper execution. | | -------- | | 5.4 "Needs LIM EMS 3.00 or higher ─ Execution cancelled" | An extended-memory manager version equal to or greater than version 3.0 of | the Lotus/Intel/Microsoft extended memory specification (EMS) is needed for | proper execution. | | -------- | | 5.5 "Unknown video card/Incompatible CRT controller" | The type of video adapter could not be determined, or the video controller | chip was found to be incompatible. Execution is cancelled. | | -------- | | | 5.6 "Driver parameter(s) updated" | The program was successfully executed, and the (selected disk) XDISK.SYS | driver parameters specified by the requested switches were updated. | | -------- | | 5.7 "Invalid switch '/Xx' ─ Execution aborted" | An invalid switch designator (X) or switch parameter (x) was selected. | Execution is cancelled. | | -------- | | 5.8 "Drive 'd:' is not an xDISK RAM disk" | The selected drive <d:> is not a RAM disk created by XDISK.SYS. Execution | is cancelled. | | -------- | | 5.9 "'d:' is an invalid drive designator" | The selected drive <d:> does not exist or DOS does not consider it a valid | disk drive designator. Execution is cancelled. | | -------- | | 5.10 "Device driver XDISK.SYS is corrupted or not loaded" | XDISK.EXE was unable to find the resident code signature of an XDISK RAM | disk driver. Execution is cancelled. | | -------- | | 5.11 "XDISK.SYS malfunction ─ [Error XXh]" | The (selected disk) XDISK.SYS driver has passed back to XDISK.EXE an error | code indicating a driver malfunction (xx). The following hexadecimal codes | may be passed: | | Code 00h: Write-protect violation | Code 01h: Unknown unit | Code 02h: Drive Not Ready | Code 03h: Unknown Command | Code 08h: Sector Not Found | | -------- | | 5.12 "Unable to access XDISK.SYS ─ [IOctl error XXh]" | XDISK.EXE communicates with the XDISK.SYS driver via IOCTL (Input/Output | Control) DOS function calls. The message is displayed if DOS encounters | any error during the IOCTL call; a number of hexadecimal error codes are | possible, but those more likely to be found are listed below: | | Code 01h: Invalid Function Code (a non-xDISK drive was selected) | Code 0Fh: Invalid Disk Drive (a non-existing drive was selected) | Code 05h: Access denied (drive corrupted) | Code 0Dh: Data invalid (drive corrupted) | | -------- | | 5.13 "DOS access to XDISK.SYS is closed ─ Use switch /A" | Access to the (selected disk) XDISK.SYS driver was previously closed via | switch /A-; access can be restored via switch /A[+]. | | -------- | | 5.14 "Cannot resize RAM disk with Read-Only status - Use switch /R" | The status of the (selected disk) XDISK.SYS driver was previously set to | Read-Only via switch /R[+]; the status must be changed to Read-Write via | switch /R- before the disk can be resized. | | -------- | | 5.15 "Resizing of drive 'd:' failed ─ [xDISK error XXh]" | Requested resizing could not be accomplished. The (selected disk) XDISK | .SYS driver passes a hexadecimal error code reflecting the nature of the | error (see 6.1). | | -------- | | 5.16 "Data in drive 'd:' will be lost upon resizing ─ Continue? [yN] " | This prompt is displayed before any disk resizing operation if switch /N | or /Q (see above). | | -------- | | 5.17 "DOS unable to access xDISK drive" | This message is displayed when the (selected disk) XDISK.SYS driver was | made inactive (/A-) and the status of the disk is requested by entering | 'XDISK d: ?' | | -------- | | 5.18 "xDISK drive(s) installed ─ d:, d:,..., d:" | This message, listing the xDISK drives installed, is displayed when the | global status of the XDISK.SYS driver is requested by entering 'XDISK ?' | | -------- | | 5.19 "Invalid character in password string: x" | "Use lower case alphanumeric (a-z 0-9) characters only" | An invalid character (i.e., neither a-z nor 0-9) was entered as part of | the requested password. Execution is cancelled. | | -------- | | 5.20 "Password assigned to first xDISK driver installed" | This message is displayed only when running xDISK under a DOS version less | than 3.00, and a password to access xDISK was specified. ---------------- | 6. MESSAGES of XDISK.SYS | | 6.1 "CRC failure: Code is corrupted" | See message 5.1 above. | | -------- | | 6.2a "This CPU cannot execute 286 code" | See message 5.2a above. | | -------- | | 6.2b "This CPU cannot execute 386 code" | See message 5.2b above. | | -------- | | 6.3 "Needs DOS version 2.1 or higher" | See message 5.3 above. | | -------- | | 6.4 "Failed to detect presence of an EMM driver" | "Installation aborted" | xDISK failed to determine presence of an expanded memory manager (EMM) | compatible with the LIM EMS version 2.0, and failed the installation. | | -------- | | 6.5 "Expanded memory allocation error [EMS code XXh]" | 6.6 "Expanded memory page frame error [EMS code XXh]" | 6.7 "Expanded memory EMM status error [EMS code XXh]" | The EMS manager encountered an error in allocating expanded memory for | the xDISK driver (6.5), in setting up the page frame (6.6), or the EMS | manager (EMM) itself malfunctioned (6.7). A number of hexadecimal EMS | error codes are possible, but those more likely to be found are listed | below: | | Code 80h: EMM internal error (manager corrupted) | Code 81h: EMS hardware error | Code 82h: EMM is busy | Code 85h: Handles are exhausted | Code 86h: Error in saving or restoring mapping context | Code 87h: Requested more pages than physically available | Code 88h: Requested more pages than currently available | | -------- | | 6.8 "Error in allocating upper memory block [XMS code xxh]" | "Install in lower conventional memory? [Yn] " | The XMS manager encountered an error in allocating a UMB for the upper- | memory self-loading, or the XMS manager is not present. The following | hexadecimal error codes may be displayed: | | Code 80h: Function was not implmented | Code 8Eh: General driver error (also XMM not present) | Code 8Fh: Unrecoverable driver error occurred | Code A9h: Parity error was detected | Code B0h: Smaller UMB is available | Code B1h: No UMBs are available | Code B2h: UMB segment number is invalid | | -------- | | 6.9 "XMM failed to allocate UMB above requested limit" | An free upper-memory block was not available above the lower high-memory | limit specified by switch /Ln; xDISK installed the driver at a lower UMB | whose value is displayed in the installation message. | | -------- | | 6.10 "<Esc> was pressed ─ Cancel installation? [Yn] " | The <Esc> key was pressed during the installation of an XDISK.SYS driver | before it could be completed. Press <Enter> or <Y> if you want to abort | the installation, or <N> to continue installing the driver. ------------------------------------------------------------------------------ SINGLE USER (BBS-DISTRIBUTED) LICENSE AGREEMENT REGISTRATION These programs and the documentations (the "Software") are the copyrighted property of FM de Monasterio (the "author"), who provides the Software and licenses its use. Neither the title to nor ownership of this Software are transferred to you by such a license, and both are retained by the author. All rights are reserved. The Software is user-supported; the enclosed release, although lacking the options marked by asterisks, is a fully usable program. You may test this release for (in)compatibilities with your system, but after the testing is completed you are requested to order a registered release of this Software from the address below. Alternatively, to continue use of this unregistered copy, send to the same address a US$5.00 check marked "For Deposit Only," and payable to "PATIENT CARE FUND, CHILDREN'S HOSPITAL" of Washington, DC. Unregistered users who donate to this fund may legally keep such a copy under the injunctions and limitations described below. A form needed for the registration or upgrade of this Software is provided in the file XDISK.REG. Refer all inquiries about the Software to: FM de Monasterio P.O. Box 219 Cabin John, MD 20818-0219 LICENSE Upon registration you receive a non-exclusive, non-transferable license to use the Software. Two types of license are available: Single User License: Upon registration/upgrade you are granted a nontransferable license to use the Software in a single computer at a time. You may transfer the Software physically to another computer provided that the Software is then not used on more than one computer at any time. This particular Software may NOT be installed on a network server under this license. Site/10-Computer License: Upon registration/upgrade you are granted a nontransferable license to use the Software in a single site or a set of sites provided that the Software is not used in more than ten computers at any time and that such computers are located exclusively within the registered site(s). Installation of the Software in a network server requires a site license. Special licenses at are available for sites with a larger number of computers (see xDISK.REG). UPGRADES Within the same major version: Registered Software users can upgrade free of charge within the same major version (e.g., 2.00 through 2.99). Outside the same major version: Registered users can upgrade for half the the license fee for a different version of the Software. To upgrade send a self-addressed stamped diskette mailer with the original 360 kb diskette to the address above, along with the upgrade form. SUPPORT Limited technical support is provided to registered users. If you discover a problem, please try to replicate it under the same conditions and, then, in the absence of other resident programs. (Changes in the order residents are installed sometimes solve conflicts.) If the problem can be replicated please write at the address above providing: - Your name and address. - Program version number (see the Syntax/Help panel). - Computer model and configuration, and hardware used. - A sufficiently detailed description of the problem. - A list of resident and nonresident programs in use, and their sequence of loading into memory. Messages may be left c/o Sysop at: The DC Information Exchange BBS ~~~ 202-433-6639, Sysop: Bill Walsh (2400+ baud). INJUNCTIONS You may distribute this Software via magnetic and/or electronic means, but you are specifically prohibited from: - Charging fees or asking donations in exchange of or payment for copies of the Software. - Distributing this Software with commercial products without the written permission from the author. - Distributing this Software via a for-profit organization or group, either alone or with other Software. The unauthorized copying, decompiling or disassembling of this Software is prohibited; any other use of this Software is prohibited without a written permission in advance from the author. LIMITED WARRANTY The author-copyright owner warrants for a period of thirty (30) days from the date of delivery that, under normal use and without any modification, the programs substantially conform to the accompanying specifications and that the documentation is substantially complete and contains information the author deems necessary to use the programs. If, during the thirty-day period, a demonstrable defect in the programs, magnetic medium upon which they are distributed, or documentation should appear, you may return this Software for repair or replacement, at the author's option. If the defect cannot be repaired, or the Software replaced with functionally equivalent software, within sixty (60) days of the author's receipt of the defective software, then you shall be entitled to a full refund of the license fee, but not of the mailing/handling costs described in the registration form. All other warranties of any kind, either express or implied,including but not limited to the implied warranties of merchantability and fitness for for as a particular purpose, are expressly excluded. The author cannot and does not warrant that any function contained in the programs will meet your requirements, or that the operation will be error free. The entire risk as to the Software performance or quality, or both, is solely with the user, and not with the author. LIMITATION OF REMEDIES You assume responsibility for the selection of the program to achieve your intended results, and for the installation, use, and results obtained from the Software. The author makes no warranty, either implied or expressed, including with- out limitation any warranty with respect to this Software documented here, its quality, performance, or fitness for a particular purpose. In no event shall the author be liable to you for damages, whether direct or indirect, incidental, special, or consequential arising out the use of or any defect in the Software, even if the author has been advised of the possibility of such damages, or for any claim by any other party. The author's entire liability, and your exclusive remedy shall be: (1) the replacement of an original Software diskette not meeting the above Limited Warranty and which is returned to the author along with proof of purchase, or (2), if the author is unable to deliver a replacement diskette which is free of defects, you may terminate the License Agreement by returning this Software and the corresponding license fee will be returned. GENERAL By using the Software, you acknowledge (1) to have read and understood all parts of this document and (2) to have agreed with and accepted all of its provisions without any reservation. ------------------------------------------------------------------------------ [END]