Category : Utilities for DOS and Windows Machines
Archive   : XDISK340.ZIP
Filename : XDISK.MSG

 
Output of file : XDISK.MSG contained in archive : XDISK340.ZIP

º ºÉÍ»É͹ÉÍ»ÌÍ ÉÍ»
º ºº ºº ºÉ͹º Ìͼ
ÈͼÌͼÈͼÈͼÈͼÈͼ

xDISK
Revision 3.40.1

Copyright (c) 1989-1992, FM de Monasterio
Licensed Material - All rights reserved


XDISK.SYS MESSAGES
******************


1. "Abort - Program code is corrupted (CRC failure)"
-------------------------------------------------
The program performs a full integrity test (32-bit cyclical redundancy
check) prior to installation. The message is displayed if a CRC error
is encountered, indicating corruption of the program code.


2. "Abort - This program requires a ?86-CPU machine"
-------------------------------------------------
The 80x86 (Intel-compatible) CPU used by the machine is not compatible
with the CPU-type release of the xDISK version: the 286 release cannot
be used in 8088, 8086, and most 80186 CPUs, and the 386 release cannot
be used in 8088, 8086 80186, and 80286 CPUs.


3. "Abort - This program requires MS-DOS 3 or higher"
--------------------------------------------------
A DOS version fully compatible with MS-DOS 3.x (or higher) is required
for proper program execution.


4. "Abort - EMS manager not installed (INT 67h)"
---------------------------------------------
The presence of a expanded memory manager (EMM), compatible with the
Lotus/Intel/Microsoft expanded memory specification (EMS) revision 3
or higher, could not be ascertained and the installation was failed.


5. "Abort - Expanded memory failure [EMS code xxh]"
------------------------------------------------
The EMS manager encountered an error in allocating expanded memory for
the driver, in setting up the EMS page frame, or the EMS manager (EMM)
itself malfunctioned. Several (hexadecimal) error codes are possible,
but those more likely to be found are listed below:

80h: EMM internal error (manager corrupted)
81h: EMS hardware error
82h: EMM is busy
85h: Handles are exhausted
86h: Error in saving or restoring mapping context
87h: Requested more pages than physically available
88h: Requested more pages than currently available


6. "Error - XMS manager not installed (INT 2Fh)"
"Install in conventional memory? [Yn]"
---------------------------------------------
The presence of an extended memory manager (XMM), compatible with the
Lotus/Intel/Microsoft/AST extended memory specification (XMS) version
2.x or later, could not be ascertained. The user is given the option
to install xDISK in conventional memory or to abort the installation:
Press or key to install, or key to cancel.


7. "Unable to find UMB above requested limit"
------------------------------------------
A free UMB was not available above the upper-memory limit specified via
switch /Ln; xDISK was installed at a lower UMB whose value is displayed
in the installation message.


8. "Error - UMB allocation failed [XMS code xxh]"
"Install in conventional memory? [Yn]"
----------------------------------------------
The XMM encountered an error during UMB allocation. Press or
key to install xDISK in conventional memory, and or key
to cancel the installation. Several (hexadecimal) error codes may be
displayed:

80h - Function is not implemented.
8Eh - General driver error occurred.
8Fh - Unrecoverable driver error occurred.
A9h - Parity error was detected
B0h - Smaller UMB is available.
B1h - No UMBs are available.
B2h - UMB segment number is invalid.


9. "Error - UMB allocation failed [DOS code xxh]"
"Install in conventional memory? [Yn]"
----------------------------------------------
MS-DOS or PC-DOS 5.x encountered an error during UMB allocation. Press
or key to install xDISK in conventional memory and or
key to cancel the installation. Two (hexadecimal) error codes may
be displayed:

07h - Memory control blocks destroyed.
08h - Not enough memory.


10. "HALT - Allocation strategy not restored [DOS code xxh]"
" Reboot the machine..."
--------------------------------------------------------
During high memory selfloading under MS-DOS 5 control of UMB allocation,
DOS did not restore its block allocation strategy to the default setting
of 'first-fit low-memory only.' (Consequently, subsequent programs would
be allocated in upper memory only, and the operation of the system could
be compromised.) xDISK halts the machine if the error were to occur, so
you can reboot the machine with a system diskette in drive A: and remove
the line in CONFIG.SYS installing XDISK.SYS. (Please contact the vendor
if this message is displayed.)


11. "Abort - Invalid drive unit in DOS request"
-------------------------------------------
MS-DOS passed an invalid drive unit code to the driver to be installed.
The display of this message indicates a serious corruption of the chain
of drivers of MS-DOS. If this message is displayed, remove the line in
CONFIG.SYS installing XDISK.SYS, coldboot (power off and then power on)
the machine, and contact the vendor.



XDISK.EXE MESSAGES
******************

1. "Not enough memory to preserve screen contents"
"Continue? [Yn] "
-----------------------------------------------
An additional 4400 bytes of memory, beyond the length of the program, are
required to save the screen contents (text mode only) if the Usage/Status
and Help panels are to be displayed. This message is displayed when such
free memory is not available. Press or key to continue with-
out preserving screen contents, or or to cancel the display.

If this message is displayed, the state of the mouse driver, if installed,

cannot be saved prior to the reset of this driver. If this message is not
displayed, a maximum of 2 KB might be allocated (if available) to save the
driver state.


2. "Invalid switch /Xx in command line"
------------------------------------
Invalid switch character(s) /X(x) found during parsing of the DOS command
line; the program continues the parsing of command switches.


3. "Invalid character entered in password string [X]"
"Use lower-case alphanumeric (a-z 0-9) characters"
--------------------------------------------------
An invalid character (i.e., neither a-z nor 0-9) was entered as part of
the requested password. Execution is cancelled.


4. "Drive X: is not an xDISK RAM-disk"
-----------------------------------
The selected drive unit is not a RAM disk created by xDISK.


5. "X: is an invalid/unassigned drive [code xxh]"
----------------------------------------------
The selected drive unit does not exist or DOS does not consider X:
a valid drive designator.


6. "Abort - Program code is corrupted (CRC failure)"
7. "Abort - This program requires a ?86-CPU machine"
8. "Abort - This program requires MS-DOS 3 or higher"
9. "Abort - EMS manager not installed (INT 67h)"
--------------------------------------------------
See above.


10. "Abort - Unknown video card/bad CRT controller"
------------------------------------------------
The video adapter type could not be determined, or the video controller
chip was found to be incompatible.


11. "Abort - EMS manager malfunction [code xxh]"
--------------------------------------------
The EMM encountered an error in (re)allocating or freeing an EMS block.
Several error codes are possible (see above).


12. "Abort - Invalid address for EMS frame segment"
------------------------------------------------
The xDISK driver for the requested unit returned an invalid address for
the EMS page frame.


13. "Data in drive X: will be lost upon resizing Ä Continue? [yN]"
---------------------------------------------------------------
Displayed (if switch /NQ or /ND is not specified in the DOS command line)
before any resizing operation that will destroy disk contents.


14. "Adjusting ñnnn KB; data should be preserved - Continue? [yN]"
--------------------------------------------------------------
Displayed (if switch /NQ or /ND is not specified in the DOS command line)
in response to the selection of switch /DXñ. The user is asked to confirm
the resizing (which should be able to preserve the contents of the disk).
Press or to continue or or to cancel the resizing.


15. "Disk formatting needed - Use switch /DB or /DE"
------------------------------------------------
A collapsed disk needs to be uncollapsed with switch /DB[n][!] or /DE[!]
only. See XDISK.DOC.


16. "Drive X: is write protected - Use switch /TW-"
-----------------------------------------------
The status of the (selected disk) XDISK.SYS driver was previously set to
write protected (Read-Only) with switch /TW+; the status must be changed
with switch /TW- (Read/Write) before the disk can be resized.


17. "Drive X: is resize protected - Use switch /TR-"
------------------------------------------------
The status of the (selected disk) XDISK.SYS driver was previously set to
resize protected via switch /TR+; the status must be changed with switch
/TR- before the disk can be resized.


18. "Warning - Switching to RAM-disk of fixed size"
-----------------------------------------------
The file system overhead sectors for an "elastic" disk formatting request
via switch /DB[n] are too large for proper functioning, so xDISK modified
the disk to an "inelastic" one. (Although neither switch /DB[n]! nor /DE!
was selected, switch /DX+ or /DX- requests will not be honored.)


19. "Warning - The RAM-disk root directory is full"
-----------------------------------------------
All of the root directory entries of the RAM-disk are used, and new files
cannot be created in the root directory. Either delete one root entry to
create a subdirectory to create new files (preserving the remainig files)
or resize with a larger /DRn value (destroying disk contents).


20. "Warning - Drive contains nnn open file(s)..."
----------------------------------------------
A data-destroying resize switch was selected and the disk contains
open files that should be closed by DOS before resizing to preserve file
handles.


21. "Abort - xDISK driver is corrupted or not loaded"
-------------------------------------------------
XDISK.EXE was unable to locate the resident XDISK.SYS driver code via the
communication interface of interrupt 2Fh, subfunction 0DDh (see XDISK.DOC
revision 3.40.00 or higher).


22. "Abort - Wrong unit data returned by XDISK.SYS"
-----------------------------------------------
A sanity check of the xDISK communication interface (see above) failed to
yield the expected return, indicating memory corruption or malfunctioning
of the driver(s).


23. "Error - Malfunction of xDISK driver [code xxh]"
------------------------------------------------
The (selected disk) XDISK.SYS driver has passed back to XDISK.EXE an error
code indicating a driver malfunction. 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


24. "Abort - Unable to access XDISK.SYS [code xxh]"
-----------------------------------------------
Unless switch /DA+ has been selected, XDISK.EXE communicates with XDISK.
SYS 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. The codes 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)


25. "Abort - Cannot shrink/expand DOS-unlinked disks"
-------------------------------------------------
A disk resizing request was specified for a unit that has been unlinked
from the DOS chain of drivers via switch /TL-. Relink the driver first
via switch /TL+ and then reissue the resize request.


26. "Abort - Disk resizing parameters out-of-range"
"Increase /DB or reduce /DR, /DS, or /CS value"
-----------------------------------------------
The EMS buffer size for the RAM-disk (specified with switch /DBn) is too
small to account for the sector size (/DSn), root directory size (/DRn),
and/or cluster size (/CSn).


27. "Error - Temporary file access failed [code xxh]"
-------------------------------------------------
To implement some of the "elastic" disk features, xDISK makes use of DOS
services to create and then erase a temporary file in the root directory
of the RAM-disk. If an error occurs when using these services, the free
space algorithm of switch /DX- will not be valid.


28. "Error - Resizing of drive X: failed [code xxh]"
------------------------------------------------
Requested resizing could not be accomplished. The (selected disk) XDISK
.SYS driver passes a hexadecimal error code reflecting the nature of the
error.


29. "Abort - DOS cannot access the RAM-disk"
----------------------------------------
DOS is unable to access the disk to measure its free space.


30. "Abort - Inelastic RAM-disks have a fixed size"
-----------------------------------------------
Switch /DX+ or /DX- (data-safe "elastic-disk" resizing) was requested for
a disk formatted by means of switch /DB[n]! or /DE! ("inelastic" disks).


31. "Abort - Maximal expansion is already achieved"
32. "Abort - Disk expansion may damage FAT entries"
-----------------------------------------------
Switch /DX+ was selected for an "elastic" RAM-disk whose size cannot be
expanded further if the integrity of disk contents is to be preserved.


33. "Abort - Maximum shrinkage is already achieved"
34. "Abort - Disk shrinkage may damage FAT entries"
-----------------------------------------------
Switch /DX- was selected for an "elastic" RAM-disk whose size cannot be
shrinked further if the integrity of disk contents is to be preserved.


35. "Abort - Disk has less than 16 KB of free space"
------------------------------------------------
Switch /DX- was requested for a RAM-disk having less than 16 KB of unused
space, so that shrinking would not free an EMS page (16 KB each).


36. "Abort - Cannot shrink fragmented/unpacked disk"
------------------------------------------------
Switch /DX- was selected for an "elastic" RAM-disk in which the free disk
space is not packed toward the end of the disk, i.e. there are free-space
gaps between used sectors. Run first a disk packing utility, providing a
full compression of used sectors, and then reissue the xDISK command.


37. "Error - Out-of-range shrinkage algorithm data"
------------------------------------------------
A sanity check of the shrinkage algorithm of an "elastic" disk for which
switch /DX- was selected returned an invalid value. Because data safety
cannot be insured, the shrinkage request is voided.



Command-line Loading/Unloading Messages
***************************************

38. "Loaded xDISK drive X:"
"Resident code length (decimal): nnn bytes"
"Loaded at (hexadecimal) address hhhh:0000"
-------------------------------------------
The specified driver was successfully loaded from the DOS command-line.
The messages provides information on the letter designator for the
new drive, the decimal length of the resident code, and the hexadecimal
memory address (offset 0000 of segment ) where such code starts.


39. "Error - Unrecognized or invalid DOS version"
---------------------------------------------
A DOS version compatible with MS-DOS 3.x or 4.x is required for command
line loading or unloading of a xDISK device driver. Neither service is
available under the DOS compatibility box of OS/2, MS-DOS or IBM PC-DOS
5.x, COMPAQ DOS 4.x or higher, and DR-DOS 5.x or higher.


40. "Error - Failed to find the NUL driver"
---------------------------------------
The program was unable to find the start of the DOS drivers chain. This
may occur if DOS has been corrupted, or an incompatible operating system
system is being used. You should reboot immediately if you receive this
message.


51. "Error - Undocumented function 32h is not supported"
----------------------------------------------------
This message indicates the the DOS version being used does not support a
necessary DOS undocumented function in question, and alternative methods
to obtain undocumented DOS data have failed or are not available.


52. "Error - Critical failure upon accessing file"
"Check drive hardware and SHARE access rights"
----------------------------------------------
This message is displayed whenever a DOS critical error (interrupt 24h)
is triggered by an attempt to open the driver file. For diskette-based
operations, an empty diskette drive or opened drive bay can trigger the
error. For nonremovable disk-based systems, a file-sharing error (i.e.
SHARE.EXE is loaded and the file has already been opened with a sharing
mode incompatible with read access request) can also trigger the error.


53. "Abort - Specified file has zero length"
54. "Abort - Specified file was not found"
55. "Abort - Specified path was not found"
56. "Abort - DOS denies access to the file"
57. "Abort - Insufficient memory to load driver"
58. "Abort - Specified file is too big to load"
--------------------------------------------
These messages are displayed when the corresponding error is triggered
when accessing the driver file.


59. "Abort - Driver file is not an xDISK driver"
--------------------------------------------
This message indicates that the specified driver file does not contain
the proper data to identify it as XDISK.SYS.


60. "Error - Loading of driver failed [code xxh]"
---------------------------------------------
This generic error message is displayed when an error is encountered in
loading the driver file as an overlay. The (hexadecimal) error code is
in the range between 01h and 58h, and is determined by DOS.


61. "Error - Driver initialization failed [code xxh]"
-------------------------------------------------
This generic error message is displayed when an error is encountered in
the initialization of the driver by xDISK. The (hexadecimal) error code
is one of the following:

Code Error Code Error
00 Write protect violation 08 Sector not found
01 Unknown unit 09 Out of paper
02 Device not ready 0A Write fault
03 Unknown command 0B Read fault
04 CRC error 0C General failure
05 Bad request structure length 0D Reserved
06 Seek error 0E Reserved
07 Unknown media 0F Invalid disk change


62. "Abort - xDISK driver failed the installation"
----------------------------------------------
This message is displayed when the initialization service of the device
driver fails the installation.


63. "Error - Last available drive [X:] is assigned"
"and LASTDRIVE cannot be increased any further"
-----------------------------------------------
DOS assigns the first available drive letter to a disk within the default
range A: through E: or (for DOS 3.x or higher) the range A: through Z: if
the command 'LASTDRIVE=Z' has been given. The message indicates that the
maximum range has already attained so that the xDISK device driver cannot
be loaded. This also applies to Novell's NetWare drives.


64. "Abort - Last available drive [X:] is assigned"
"LASTDRIVE has been increased to Y - Try again"
-----------------------------------------------
See above. The program has increased the LASTDRIVE value to LASTDRIVE+1
(Y) so that the xDISK driver will be loaded if you repeat the execution.


65. "Drive X: uninstalled"
----------------------
The specified xDISK drive was successfully removed from memory.


66. "Error - XMS manager (XMM) is not installed"
--------------------------------------------
The presence of an extended memory manager (XMM), compatible with the
Lotus/Intel/Microsoft/AST extended memory specification (XMS) version
2.x or later, could not be ascertained.


67. "Error - Driver not loaded from the command line"
-------------------------------------------------
The request to uninstall an xDISK drive specified an xDISK RAM-disk not
loaded from the DOS command line.


68. "Error - Device is not an xDISK driver"
---------------------------------------
The request to uninstall an xDISK drive specified a non-xDISK drive.


69. "Warning - Failed to find an xDISK gateway for drive X:"
--------------------------------------------------------
The request to uninstall an xDISK drive specified an xDISK RAM-disk not
installed from the command line or an invalid drive letter. Retype the
request correctly or check the installed gateway names (i.e., XDISK_d:)
with a memory mapping utility.


70. "Warning - Failed to release program environment [code xxh]"
------------------------------------------------------------
The program was unable to release the DOS environment block of the driver
(lower memory loading) or its gateway (upper memory loading). The failure
is harmless to the operation of the program.


71. "Warning - Failed to release lower memory block [code xxh]"
-----------------------------------------------------------
xDISK was unable to release the lower-memory block containing the driver
(LMB loading) or its DOS gateway to the upper memory (UMB loading). This
failure is harmless to the unlinking of the xDISK driver from the chain,
but the allocated memory block is unavailable to the conventional memory
pool for further use.


72. "Warning - Failed to release allocated EMS block [code xxh]"
------------------------------------------------------------
xDISK was unable to release the expanded memory block that was allocated
by the the driver during its initialization. This failure is harmless to
the unlinking of the driver from the DOS driver chain, but the allocated
block is unavailable to the EMS memory pool for further use.


73. "Warning - Failed to release upper memory block [code xxh]"
-----------------------------------------------------------
xDISK was unable to release the upper-memory block containing the driver
(UMB load). This failure is harmless to the unlinking of the driver from
the driver chain, but the allocated block is unavailable to the XMS pool
for further use.


74. "Warning - Failed to release memory control block [code xxh]"
-------------------------------------------------------------
In rebuilding the chain of memory, the program was not able to release a
memory control block allocated by a resident program installed after the
driver was loaded. The failure is harmless to the unlinking of the xDISK
driver from the driver chain, but the allocated memory is unavailable to
the memory pool for further use.

----------------

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ Trademarked names are the property of the respective owners ³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
[END]


  3 Responses to “Category : Utilities for DOS and Windows Machines
Archive   : XDISK340.ZIP
Filename : XDISK.MSG

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/