Error Message Listing
Messages with first letter A-L
A B C D E F G H I J K L (M-Z)
Select the first letter of the word from the list above to jump to appropriate section of the listing. If the error message you are looking for starts with a digit or symbol, choose the M-Z page.
THIS section gives a brief explanation of error messages that you may encounter. It is very new, and more messages will be added as we develop it. If the message you are looking for is not listed, please email technical support and we do our best to provide you with an explanation, and then add the message here for the benefit of others.
Abort, Retry, Ignore, Fail ? from
Any application
This is produced by the operating kernel, and
indicates that a device (usually a floppy disk drive) is having difficulty
reading or writing data. Check that the disk is seated properly in the drive,
retry a few times (by pressing R) and then if unsuccessful abort the program
(press A). Note that selecting either the "Ignore" or "Fail"
option may corrupt data unless the application program has been specially
written.
Access denied from Any
application
A program is trying to access a file which is
read-only, or a file or directory for which the current user does not have the
required rights.
Attempted FREE of NULL pointer
from Any application
Internal error, please report to your dealer.
Attrib not compatible with version of
REAL/32 from ATTRIB
Use the version of attrib which is supplied on
the installation disks for the version of REAL/32 you are running.
Attribute A,D,H,R or S expected to follow
"-" from XDIR
+ or - must be followed by an attribute. Use the
command-line help or refer to the User Guide for valid formats.
BACKUP file sequence error from RESTORE
You are using the wrong floppy disk. Disks created with BACKUP
are identified by a sequence number, and must be RESTORE'd in the correct order.
Bad arguments from Any
command
The command line arguments were incorrect. Use the
command-line help or refer to the User Guide for valid formats.
Bad or missing command interpreter
from System
startup
The file pointed to by the COMSPEC variable in mconfig.sys was
not a valid command interpreter, or did not exist. COMSPEC should point to a
copy of the command.comfile supplied with REAL/32.
Bad command or parameter from
SID
Get help on the available commands and parameters by entering
? or ??
Bad file name from
SID
The filename specified was not valid. Check that the
characters are legal, and that the file is in the current directory.
Bad format for time from
WAIT
Use the command-line help or refer to the User Guide for valid
formats.
Bad media type from
Any application
This is usually caused by attempting to read a high capacity
disk in a standard drive, or by using a disk which is not formatted for a PC.
BAD OPCODE interrupt from processname
at nnnn:nnnn from Any
application
An application program has crashed. This is frequently caused
by a bad upper-memory configuration.
Bad or missing file from
Any application
The operating system cannot locate the mconfig.sys file.
Bad time selected from
WAIT
Use the command-line help or refer to the User Guide for valid
formats.
Batch file filename missing retry (Y/N)?
from Any
application
The operating system cannot re-open the batch file from which
it was reading instructions. If it was on a floppy then make sure the same disk
is available, check that the batch file has not deleted itself and make sure
that the drive has not been re-mapped by NET, SUBST, etc.
Batch files nested too deep from
Any application
Too many CALL directives are active at the same time.
Bdos error 21 (otherwise known as bdos
error 33) from REAL/32
This error indicates a bad disk - a hardware problem.
Binary reads from a device are not allowed
from COPY
Do not use the /B option when copying to or from a device such
as CON.
Blink will only work on an EGA or VGA screen
from BLINK
BLINK is not needed for an MDA or Hercules card since the
blink status cannot be changed.
Cannot find WINOLDAP.MOD (followed by) Unexpected DOS
ERROR CODE 23 from Windows 3.xx
An attempt has been made to run a Dos application from Windows
which is itself running under REAL/32. Use a REAL/32 dos session instead.
Cannot open a virtual input queue
from COPILOT
COPILOT was unable to access the keyboard of the target DOS
session
Can't open MXdisk queue from
PROFILE
Reboot the machine since if we can't open the MXdisk queue
(controlling access to the disk system) something is seriously wrong.
Cannot access drive from
BACKUP
See "Abort, Retry, Ignore, Fail".
Cannot close from
SID
The file being written cannot be closed. Check that there is
enough room on the disk and that the root directory is not full.
Cannot copy to/from a reserved device from
REPLACE, XCOPY
REPLACE and XCOPY can only be used for moving files on disks,
not to CON etc.
Cannot find any system files (LOADER.SYS)
from Operating
system startup procedure
The multiple-boot loader installed by LOADER can't find
anything to boot.
Cannot find bootlist file - Will now attempt to load
from Standard boot sector from
Operating system startup procedure
The multiple-boot loader cannot find the bootlist. This is the
text file which was specified as the first parameter to the LOADER program.
Cannot find exec file from
Operating system startup procedure
As above, except that the missing file is the code file
specified by LOADER's optional second parameter.
Cannot find VTDAPI.386 driver from
KRNL386
This driver will not load in Windows under REAL/32. Delete it
from the [enh386] section of your system.ini file.
Cannot find Winoldap.mod - execution error status 23
from Rwin (krnl386)
This error message occurs when trying to run a Dos program
under Windows 3.xx on REAL/32. switch to another Dos Session under REAL/32 to
run the application, or use the REAL/32 DosBox utility with Windows.
Cannot load file from
Operating system startup procedure
The volume boot loader has located but is unable to load the
position sensitive ibmbio.ldr file.
Cannot open devicename(device) from
FIND
FIND can only be used on files, not devices.
Cannot uninstall LOADER from hard disk
from LOADER
In order to remove the multiple-boot loader, the original
loader.savfile must be available.
CGA main screen not supported from
Operating system startup procedure
The main screen must be VGA, MDA or Hercules compatible
Command or filename not recognized
from Any command
Check the spelling of the command you have just entered, also
make sure that if it is loaded from a file that the appropriate file is in the
current directory or is in the search path.
COPILOT not available from PHANTOM sessions
from COPILOT
COPILOT is not available from a phantom session, for security
reasons.
Could not create new volume label on destination disk
from BACKUP
The disk may be write-protected, see also "Abort, Retry,
Ignore, Fail".
Could not delete destination disk volume label
from BACKUP
As above.
Could not load FORMAT from
BACKUP
Check that format.comis on the search path, BACKUP uses it to
format a floppy disk if necessary.
Could not update destination disk ... file
from BACKUP
Check that the disk is not corrupt. See also "Abort,
Retry, Ignore, Fail".
Could not update log file from
BACKUP
The log file used by BACKUP is in the root directory of the
system drive by default, check that an existing file is not read-only.
CTS/RTS not supported on ports 5 to 16 of PCC/16i
card. Reconfigure to use DTR/DSR instead from
IMSPCC16
The non-expandable 16-port intelligent card has limited
handshaking capability on ports 5 to 16.
Current path invalid from
FIND
Use the command-line help or refer to the User Guide for valid
formats.
Cyclic copy not allowed from
XCOPY
When using the /S option, ensure that directories in the
source and destination specifications do not overlap.
Data error from
Any application
See "Abort, Retry, Ignore, Fail".
Date is not valid from
BACKUP, RESTORE
Check the format of the date in the /D option, it should
correspond with that used in the country specified by the COUNTRY directive in
mconfig.sys.
Date must also be specified from
BACKUP
A time cannot be specified without a date.
Delete failed from
XDEL
Check the protection level of the file which has failed.
Destination disk is full from
RESTORE
Delete some files or restore the backup disk to a different
drive.
Destination file content lost before copy
from COPY
The + (concatenate) facility has been used to overwrite a file
before it was copied.
Destination must be a valid disk drive
from BACKUP
Valid destinations are fixed and floppy drives, the source and
destination cannot be the same device.
Destination path not found from
BACKUP, RESTORE
Use the command-line help or refer to the User Guide for valid
formats.
Device does not exist: from
PRINTMAP
Use PRINTMAP/A/P to display a list of available auxilliary and
printer devices.
Disk drives or diskette formats are not compatible
from DISKCOMP
The two disks must have the same format. This information is
stored on the disk itself, so sometimes two disks actually have different
formats even if their storage capacities etc. are the same.
Disk full from
Any command
Remove or backup files that are not needed. Alternatively, buy
a larger disk.
Disk read error from
SID
A file could not be read. Check that the disk is not corrupt.
Disk write error from
SID
See "Disk read error".
Divide interrupt from processname at nnnn:nnnn
from System error
An application program has detected a divide-by-zero error.
This is usually caused by a bug in the program, although it may also be caused
by a bad upper-memory configuration. This may arise, for example,
when OPT00025.zap has not been applied when a Zip drive is in use.
DMA transfer error: Use ALIGN option in MCONFIG.SYS
from System error
The operating system has detected that a program has used
Direct Memory Access to write to physical memory that it should not be
accessing. Use the ALIGN option in mconfig.sysor set the program up to use
aligned memory using PIFED.
DOS session must not be your own
from COPILOT
COPILOT does not allow you to COPILOT your own sessions.
Drive not ready from
Any command
See "Abort, Retry, Ignore, Fail".
Ensure the
MsDos version is set to 3.3 or higher from
Rwin (krnl386)
The REAL/32 Dos version number set in SETUP/Dos Session
Defaults should be checked.
Environment error from
SET
The environment space for the current session could not be
located.
Environment full from
SET
The environment space for the current session is full. Either
allocate a larger default size using the ENVSIZE directive in mconfig.sys, or
run command.comwith the /E option. Sometimes running a TSR program limits the
size of the environment.
Error 1: An internal error occurred from Windows NT
Client for Dos
This message has been reported when IFSHLP.SYS was not loaded
as the last line in the mconfig file, either due to it being omitted or when
loading failed. Please check this file is loaded. If it fails to
load, it may be because the REAL/32 systemwide dos version number should be set
to 3.31 (this is set in SETUP/Dos Session Defaults) - if any applications need a
higher Dos version number to be returned to them by the operating system, please
use PIFED. The NT Client must be also set to use the "BASIC"
redirector. This can be done using the NT Client SETUP program, Select
"Change Setup Options" and set "Change ReDir Options" to
"Use the Basic Redirector". The alternative is to use the "Full
Redirector" which may also result in the above error message being seen.
Error loading operating system from
Operating system startup procedure
See "Can't load DOS file"
Error on file ... from
DOSPRINT
A file which DOSPRINT was trying to print cannot be read.
Error reading configuration file
from FILELINK
The default configuration cannot be retrieved.
Error reading file from
Several commands
A file has been opened but cannot be read.
Error reading filelist . . . from
Several commands
A file list (preceded by @ on the command line) cannot be
read.
Error reading from standard input
from SORT
Check that the file or device redirected into the standard
input channel is OK.
Error reading in the DIALIN.DAT file
from IMSTERM
The file may be corrupt, restore from backup.
Error reading Queue from
Menu system
Run RUM to see if any system resources are exhausted, increase
them using SETUP if necessary.
Error reading system area from
FDISK
This implies a hardware failure or a seriously corrupted disk.
Error reading system files from
FORMAT, SYS
The operating system files cannot be copied to the destination
disk.
Error when opening file filenamefor card n
from IMSPCC
The firmware file was found but for some reason could not be
opened.
Error reading system files from
FORMAT, SYS
See "Error reading system files".
Failed to change mode of printer . . .
from MODE
See "Abort, Retry, Ignore, Fail".
Failed to find file filenamefor TCL card at address
ssss from IMSPCC
The driver could not find the firmware file for the card.
Failed to get current path on drive...
from Several
commands
See "Abort, Retry, Ignore, Fail".
File already open from
Several commands
A file is already open, probably by another user.
File not erased from
DEL
The file is read-only or the user does not have delete-access.
File not found from
Several commands
A file is missing or in an inaccessible directory.
File read error for card n from
IMSPCC
The firmware file is corrupt.
File sharing conflict from
Several commands
See "File already open".
File too large for Multiport card
from IMSPCC
The firmware file is expected to be less than 64K bytes in
size. If more, then it is invalid.
Filename too long from
Several commands
A filename comprises a name of up to 8 characters, followed by
an optional extension of up to 3 characters.
FORMAT not allowed on fixed media
from FORMAT,
BACKUP
FORMAT only works on floppy disks. Use FDISK for hard disks.
Format unsuccessful from
FORMAT
The disk is probably unusable.
Hour must be between 0 and 23 from
WAIT
Midnight is 00:00 rather than 24:00.
I/O error . . . from
Any application
See "Abort, Retry, Ignore, Fail".
IBMBIO.COM read error from
Diskette system loader
The operating system files could not be read whilst loading
from a floppy disk.
Illegal characters in label from
LABEL
A disk label may contain only letters and digits.
Illegal combinations of options from
ATTRIB
Use the command-line help or refer to the User Guide for valid
formats.
Illegal drive in Path Specification
from Several
commands
There is a non-existent drive in the search path.
Illegal filename filename from
ATTRIB
The filename contains an invalid character.
Illegal syntax for directory select option
from ATTRIB
Use the command-line help or refer to the User Guide for valid
formats.
Illegal syntax for paging option: /x
from ATTRIB
As above
Illegal syntax for subdirectory search option
from ATTRIB
As above
Illegal x level: x from
ATTRIB
Protection levels are 0 to 3.
IMS Network terminal driver could not start up
from IMSNETIO
Internal error, please report to your supplier.
IMS Network terminal driver incompatible with this
operating system from IMSNETIO
The version of imsnetio.sysbeing loaded is incompatible with
the operating system kernel.
IMS Terminal emulator is already resident
from IMSTERM
The terminal emulator cannot be loaded a second time.
Incorrect card type at address ssss
from IMSPCC
An intelligent card was found where expected, but was not the
correct type for this driver being loaded.
Incorrect day name from
WAIT
Use the command-line help or refer to the User Guide for valid
formats.
Incorrect version of operating system
from Several
commands
Many programs associated with REAL/32 are sensitive to the
version of operating system kernel loaded. Be particularly careful if multiple
operating systems are loaded on the same disk.
Incorrect version of filename.SYS - Use version n.nn
from IMSPCC
An invalid firmware file was found - either the firmware or
the driver needs to be upgraded.
Input redirection already active
from Command line
instructions
The standard input channel can only be redirected once. Be
careful if executing a batch file inside a secondary command interpreter (using
the /C or /K option) which has its input redirected.
Insert SYSTEM diskette in A: then PRESS
Ctrl/Alt/Del... from Operating
system hard disk system loader
This message will be displayed if an operating system cannot
be loaded from a hard or floppy disk.
Install Pterm from original master disk, using install
from Pterm
Use the Install program supplied, rather than copying the
files, and/or make sure the installation diskette is not write protected.
Insufficient memory from
SID
The banked window (TPA) is not large enough to load a file
with the E or R commands.
Internal Error 0001 from a Novell NetWare
ODI connection
Please reduce the Dos version returned by REAL/32 to 3.31
or earlier. Pifed may be used to ensure a higher dos version number is returned
to those applications that need it.
Internal Error 112 from
Command line instructions
The operating system can't create a process descriptor for
your program, or it can't create a network requester process for it. Try running
NETOFF on any DOS sessions which do not need to be attached to the network.
Internal Error 128 from
REAL/32
Internal error 128 is an operating system queue or buffer overflow.
Invalid baud rate from
MODE
Use the command-line help or refer to the User Guide for valid
formats.
Invalid break switch (use ON or OFF)
from BREAK
BREAK takes ON or OFF as its parameter.
Invalid combination of options from
REPLACE, XCOPY
Use the command-line help or refer to the User Guide for valid
formats.
Invalid country code from
COUNTRY
See the description of the COUNTRY directive in the User
Guide.
Invalid date specified from
DATE, TOUCH
See "Date is not valid".
Invalid destination pathname from
REPLACE
Use the command-line help or refer to the User Guide for valid
formats.
Invalid directory specified from
ATTRIB
Use the command-line help or refer to the User Guide for valid
formats.
Invalid drive specified from
ATTRIB
As above
Invalid file specification from
PRINT, ATTRIB
Check that the filename specified is valid and that its path
is a reasonable length.
Invalid hard disk system partition
from Hard disk
system loader
It may be necessary to run FDISK to rebuild the hard disk
partitions. Using FDISK will destroy all the data on that partition of your hard
disk.
Invalid last drive character (use A...Z)
from LASTDRIVE
Drive must be a: to z:.
Invalid lines per inch from
MODE
Valid parameters are 6 or 8.
Invalid line width from
MODE
Valid widths are 80 or 132 characters.
Invalid number of buffers from
BUFFERS
The maximum number is 99.
Invalid number of data bits from
MODE
Either 7 or 8 data bits may be specified.
Invalid number of parameters from
Several commands
Use the command-line help or refer to the User Guide for valid
formats.
Invalid number of stop bits from
MODE
Either 1 or 2 stop bits may be specified.
Invalid option - decimal number expected
from SORT
SORT expects the column number at which the comparison is to
start to be expressed as a decimal number.
Invalid option /x from
ATTRIB
Use the command-line help or refer to the User Guide for valid
formats.
Invalid option ... in parameter ...
from Several
commands
Use the command-line help or refer to the User Guide for valid
formats.
Invalid parity setting from
MODE
Should be Even, None or Odd.
Invalid parameter from
Several commands
Use the command-line help or refer to the User Guide for valid
formats.
Invalid parameter - missing option
from FIND
As above. Make sure that the string to be matched is enclosed
in double quotes"".
Invalid partition table from
Hard disk system loader
See "Invalid hard disk system partition".
Invalid path from
Several commands
Check the format of file names in the command line.
Invalid time specified from
TIME, TOUCH
See "Time is not valid".
Label; labelnot found from
GOSUB, GOTO, SWITCH
The specified label cannot be found in the mconfig.sys file or
in a batch file.
Line too long in file from
FIND
The file being processed is probably not a text file.
Loading conflict from
Several commands
The program being loaded requires a resource which is already
in use, or not supported. This message is usually generated because an
application is requesting a service not provided by the hardware. If a dumb
terminal configurarion is used, for example, then an INT10 call to the bios
video will generate this message because INT10 is not supported by a dumb
terminal.
LOADING FAILED from
IMSPCC
There was an error loading the firmware file onto the
intelligent card.
Log file path not found from
BACKUP
Use the command-line help or refer to the User Guide for valid
formats.
( go to A-Z index )
If the first letter of your message falls in the range M-Z
please click here