home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Frostbyte's 1980s DOS Shareware Collection
/
floppyshareware.zip
/
floppyshareware
/
XDISK330.ZIP
/
XDISK.MSG
< prev
next >
Wrap
Text File
|
1992-01-01
|
17KB
|
462 lines
xDISK
Copyright (c) 1989-1992, FM de Monasterio
Licensed Material - All rights reserved
XDISK.EXE MESSAGES
Initialization Error Messages
*****************************
1. "Bad CRC (code corrupted) ─ Execution cancelled"
A failure of the 32-bit cyclical redundancy check was encountered when the
program was executed.
2. "Cannot execute 286+ code ─ Execution cancelled"
286+ program versions cannot be executed in 8088, 8086 or (most) 80186 CPU
machines.
3. "Cannot execute 386+ code ─ Execution cancelled"
386+ program versions cannot be executed in 8088, 8086, 80186 or 80286 CPU
machines.
4. "Needs DOS 2.10 or higher ─ Execution cancelled"
DOS version equal to or greater than MS-DOS 2.10 (or compatible operating
system) is required for proper execution.
5. "Needs EMS 3.00 or higher ─ Execution cancelled"
An extended-memory manager version equal to or greater than version 3.0 of
the extended memory specification (EMS) of Lotus/Intel/Microsoft is needed
for proper execution.
6. "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.
7. "Not enough memory to preserve screen contents"
"Continue? [Yn] "
An additional 4500 bytes of memory are needed to preserve the contents of
the current screen (text mode only). Press <Enter> or <Y> if you want to
start the display, or <Esc> or <N> to cancel execution.
----------------
Data Input Messages
*******************
8. "Invalid switch '/Xx' ─ Execution aborted"
An invalid switch designator (X) or switch parameter (x) was selected.
Execution is cancelled.
9. "Drive 'd:' is not an xDISK RAM-disk"
The selected drive <d:> is not a RAM disk created by XDISK.SYS. Execution
is cancelled.
10. "'d:' is an invalid/unassigned drive designator code"
The selected drive <d:> does not exist or DOS does not consider it a valid
drive designator. Execution is cancelled.
11. "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).
12. "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.
13. "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.
----------------
Driver Update Messages
**********************
14. "Driver parameter(s) updated"
The program was successfully executed, and the (selected disk) XDISK.SYS
driver parameters specified by the requested switches were updated.
15. "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.
16. "XDISK.SYS malfunction ─ [Driver error 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
17. "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)
18. "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[+].
19. "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.
20. "Resizing of drive 'd:' failed ─ [Driver 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).
21. "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: ?'
----------------
Command-line Loading Messages
*****************************
22. "Loaded xDISK drive d:"
"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 <d:> for the
new drive, the decimal length of the resident code, and the hexadecimal
memory address (offset 0000 of segment <hhhh>) where such code starts.
23. "Unrecognized or invalid DOS version"
The program requires MS-DOS version 2.x through 5.x for proper execution
of the command-line loading or the unloading of the device driver. These
services are not available under the DOS compatibility box of OS2.
24. "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.
25. "Undocumented DOS 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.
26. "A critical error ocurred accessing the file"
"Check drive hardware or 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.
27. "Specified file has zero length"
28. "Specified file was not found"
29. "Specified path was not found"
30. "DOS denies access to the file"
31. "Insufficient memory to load driver"
32. "Specified file is too big to load"
These messages are displayed when the corresponding error is triggered
when accessing the driver file.
33. "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.
34. "Loading of driver failed [code ??h]"
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.
35. "Driver initialization failed [code ??h]"
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
36. "Device driver failed the installation"
This message is displayed when the initialization service of the device
driver fails the installation of the driver either by requesting a zero
length resident (DOS 3.3 or higher) or by specifying a zero unit number
(block devices only).
37. "Last available drive [d:] is already 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.
38. "Last available drive [d:] is already assigned"
"LASTDRIVE has been increased to X - Try again"
See above. The program has increased the LASTDRIVE value to LASTDRIVE+1
(X) so that the xDISK driver will be loaded if you repeat the execution.
----------------
Command-line Unloading Messages
*******************************
39. "Drive d: uninstalled"
The specified xDISK drive was successfully removed from memory.
40. "Failed to find an xDISK gateway for drive d:"
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 map utility.
41. "XMS manager (XMM) is not installed"
Failed to determine the presence of a driver compatible with the Extended
Memory Specification (XMS) version 2.0, and the unloading of a UMB-loaded
driver was aborted.
42. "Failed to release program environment [Error ??h]"
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.
43. "Failed to release lower memory block [Error ??h]"
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.
44. "Failed to release allocated EMS block [Error ??h]"
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.
45. "Failed to release upper memory block [Error ??h]"
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.
46. "Failed to release memory control block [Error ??h]"
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.
----------------
XDISK.SYS MESSAGES
1. "CRC failure: Code is corrupted" - See above.
2. "This CPU cannot execute 286 code" - See above.
3. "This CPU cannot execute 386 code" - See above.
4. "Needs DOS version 2.1 or higher" - See above.
5. "Failed to detect presence of an EMS 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. "Expanded memory allocation error [EMS code XXh]"
7. "Expanded memory page frame error [EMS code XXh]"
8. "Expanded memory EMM status error [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
9. "Failed to detect presence of an XMS driver"
"Install in lower conventional memory? [Yn] "
xDISK failed to determine presence of an extended memory manager (XMM)
compatible with XMS version 2+. Press <Enter> or <Y> to load in lower
conventional memory, or <Esc> or <N> to cancel the installation of the
xDISK driver.
10. "Upper memory allocation error [XMS code xxh]"
"Install in lower conventional memory? [Yn] "
The XMS manager encountered an error in allocating memory for the upper
memory selfloading of the driver. Press <Enter> or <Y> to load in lower
conventional memory, or <Esc> or <N> to cancel the installation of this
xDISK driver. 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.
11. "Upper memory allocation error [DOS code xxh]"
"Install in lower conventional memory? [Yn] "
MS-DOS 5.0 encountered an error in allocating a UMB for the upper-memory
memory self-loading or the XMS manager is not present. Press <Enter> or
<Y> to load in conventional memory, or <Esc> or <N> to cancel the driver
installation. Several (hexadecimal) error codes may be displayed:
07h - Memory control blocks destroyed.
08h - Not enough memory.
12. "Unable 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.
13. "Invalid drive -- Increase <LASTDRIVE> value in CONFIG.SYS"
The number of block device drivers already installed during the booting of
the operating system has reached its maximum. This limit may be increased
by changing the value of the LASTDRIVE= command in the CONFIG.SYS file, or
by adding such command if not present. See XDISK.DOC.
14. "<Esc> 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.
15. "DOS allocation strategy not restored"
"System halted -- Reboot processor..."
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.) If this error occurs, the driver enters into a dynamic
halt until the CPU is rebooted.
----------------
┌─────────────────────────────────────────────────────────────┐
│ Trademarked names are the property of the respective owners │
└─────────────────────────────────────────────────────────────┘
[END]