errors.gml

开放源码的编译器open watcom 1.6.0版的源代码

.*
.note 1003 "can't lock extender kernel in memory"
.np
DOS/4G couldn't lock the kernel in physical memory, probably because
of a memory shortage.
.*
.note 1004 "syntax is DOS4G <executable.xxx>"
.np
You must specify a program name.
.*
.note 1005 "not enough memory for dispatcher data"
.np
There is not enough memory for DOS/4G to manage user-installed
interrupt handlers properly.  Free some memory for the DOS/4G
application.
.*
.note 1007 "can't find file <program> to load"
.np
DOS/4G could not open the specified program.  Probably the file
didn't exist.  It is possible that DOS ran out of file handles, or
that a network or similar utility has prohibited read access to the
program.  Make sure that the file name was spelled correctly.
.*
.note 1008 "can't load executable format for file <filename> [<error code>]"
.np
DOS/4G did not recognize the specified file as a valid executable
file.  DOS/4G can load linear executables (LE and LX) and EXPs (BW).
The error code is for Tenberry Software's use.
.*
.note 1009 "program <filename> is not bound"
.np
This message does not occur in DOS/4G, only DOS/4GW Professional; the
latter requires that the DOS extender be bound to the program file.
The error signals an attempt to load
.*
.note 1010 "can't initialize loader <loader> [<error code>]"
.np
DOS/4G could not initialize the named loader, probably because of a
resource shortage.  Try making more memory available.  If that doesn't
work, please contact Tenberry Technical Support.  The error code is for
Tenberry Software' use.
.*
.note 1011 "VMM initialization error [<error code>]"
.np
DOS/4G could not initialize the Virtual Memory Manager, probably
because of a resource shortage.  Try making more memory available. If
that doesn't work, please contact Tenberry Technical Support.  The error code
is for Tenberry Software' use.
.*
.note 1012 "<filename> is not a WATCOM program"
.np
This message does not occur in DOS/4G, only DOS/4GW and DOS/4GW
Professional.  Those extenders only support WATCOM 32-bit compilers.
.*
.note 1013 "int 31h initialization error"
.np
DOS/4G was unable to initialize the code that handles Interrupt 31h,
probably because of an internal error.  Please call Tenberry Technical
Support.
.*
.note 1100 "assertion \"<statement>\" failed (<file>:<line>)"
.np
DOS/4G internal error.  Please contact Tenberry Technical Support.
.*
.note 1200 "invalid EXP executable format"
.np
DOS/4G tried to load an EXP, but couldn't.  The executable file is
probably corrupted.
.*
.note 1201 "program must be built -AUTO for DPMI"
.np
Under DPMI, DOS/4G can only load EXPs that have been linked with the
GLU -AUTO or -DPMI switch.
.*
.note 1202 "can't allocate memory for GDT"
.np
There is not enough memory available for DOS/4G to build a Global
Descriptor Table.  Make more memory available.
.*
.note 1203 "premature EOF"
.np
DOS/4G tried to load an EXP but couldn't.  The file is probably
corrupted.
.*
.note 1204 "not enough memory to load program"
.np
There is not enough memory available for DOS/4G to load your program.
Make more memory available.
.*
.note 1301 "invalid linear executable format"
.np
DOS/4G cannot recognize the program file as a LINEXE format.  Make
sure that you specified the correct file name.
.*
.note 1304 "file I/O seek error"
.np
DOS/4G was unable to seek to a file location that should exist.  This
usually indicates truncated program files or problems with the
storage device from which your program loads.  Run CHKDSK or a
similar utility to begin determining possible causes.
.*
.note 1305 "file I/O read error"
.np
DOS/4G was unable to read a file location that should contain program
data.  This usually indicates truncated program files or problems
with the storage device from which your program loads.  Run CHKDSK or
a similar utility to begin determining possible causes.
.*
.note 1307 "not enough memory"
.np
As it attempted to load your program, DOS/4G ran out of memory.  Make
more memory available, or enable VMM.
.*
.note 1308 "can't load requested program"
.note 1309 "can't load requested program"
.note 1311 "can't load requested program"
.note 1312 "can't load requested program"
.np
DOS/4G cannot load your program for some reason.  Contact Tenberry Technical
Support.
.*
.note 1313 "can't resolve external references"
.np
DOS/4G was unable to resolve all references to DLLs for the requested
program, or the program contained unsupported fixup types.  Use EXEHDR
or a similar LINEXE dump utility to see what references your program
makes and what special fixup records might be present.
.*
.note 1314 "not enough lockable memory"
.np
As it attempted to load your program, DOS/4G encountered a refusal to
lock a virtual memory region.  Some memory must be locked in order to
handle demand-load page faults.  Make more physical memory available.
.*
.note 1315 "can't load requested program"
.note 1316 "can't load requested program"
.np
DOS/4G cannot load your program for some reason.  Contact Tenberry Technical
Support.
.*
.note 1317 "program has no stack"
.np
DOS/4G reports this error when you try to run a program with no
stack.  Rebuild your program, building in a stack.
.*
.note 2000 "deinitializing twice"
.np
DOS/4G internal error.  Please contact Tenberry Technical Support.
.*
.note 2001 "exception <exception_number> (<exception_description>) at
<selector:offset>"
.np
Your program has generated an exception.  For information about
interpreting this message, see the file COMMON.DOC.
.*
.note 2002 "transfer stack overflow at <selector:offset>"
.np
Your program has overflowed the DOS/4G transfer stack.  For
information about interpreting this message, see the file COMMON.DOC.
.*
.note 2300 " can't find <DLL>.<ordinal> - referenced from <module>"
.np
DOS/4G could not find the ordinal listed in the specified DLL, or it
could not find the DLL at all.  Correct or remove the reference, and
make sure that DOS/4G can find the DLL.
.np
DOS/4G looks for DLLs in the following directories:
.begbull
.bull
The directory specified by the Libpath32 configuration option
(which defaults to the directory of the main application file).
.bull
The directory or directories specified by the LIBPATH32
environment variable.
.bull
Directories specified in the PATH.
.endbull
.note 2301 "can't find <DLL>.<name> - referenced from <module>"
.np
DOS/4G could not find the entry point named in the specified module.
Correct or remove the reference, and make sure that DOS/4G can find
the DLL.
.note 2302 "DLL modules not supported"
.np
This DOS/4GW Professional error message arises when an application
references or tries to explicitly load a DLL.  DOS/4GW Professional
does not support DLLs.
.*
.note 2303 "internal LINEXE object limit reached"
.np
DOS/4G currently handles a maximum of 128 LINEXE objects, including
all .DLL and .EXE files.  Most .EXE or .DLL files use only three or
four objects.  If possible, reduce the number of objects, or contact
Tenberry Technical Support.
.*
.note 2500 "can't connect to extender kernel"
.np
DOS/4G internal error.  Please contact Tenberry Technical Support.
.*
.note 2503 "not enough disk space for swapping - <count> byes required"
.np
VMM was unable to create a swap file of the required size.  Increase
the amount of disk space available.
.*
.note 2504 "can't create swap file \<filename>\""
.np
VMM was unable to create the swap file.  This could be because the
swap file is specified for a nonexistent drive or on a drive that is
read-only.  Set the SWAPNAME parameter to change the location of
the swap file.
.*
.note 2505 "not enough memory for <table>"
.np
VMM was unable to get sufficient extended memory for internal tables.
Make more memory available.  If <table> is page buffer, make more DOS
memory available.
.*
.note 2506 "not enough physical memory (minmem)"
.np
There is less physical memory available than the amount specified by
the MINMEM parameter.  Make more memory available.
.*
.note 2511 "swap out error [<error code>]"
.np
Unknown disk error.  The error code is for Tenberry Software' use.
.*
.note 2512 "swap in error [<error code>]"
.np
Unknown disk error.  The error code is for Tenberry Software' use.
.*
.note 2514 "can't open trace file"
.np
VMM could not open the VMM.TRC file in the current directory for
writing.  If the directory already has a VMM.TRC file, delete it.  If
not, there may not be enough memory on the drive for the trace file,
or DOS may not have any more file handles.
.*
.note 2520 "can't hook int 31h"
.np
DOS/4G internal error.  Please contact Tenberry Technical Support.
.*
.note 2523 "page fault on non-present mapped page"
.np
Your program references memory that has been mapped to a nonexistent
physical device, using DPMI function 508h.  Make sure the device is
present, or remove the reference.
.*
.note 2524 "page fault on uncommitted page"
.np
Your program references memory reserved with a call to DPMI function
.note 504h, but never committed (using a DPMI 507h or 508h call).  Commit
the memory before you reference it.
.*
.note 3301 "unhandled EMPTYFWD, GATE16, or unknown relocation"
.note 3302 "unhandled ALIAS16 reference to unaliased object"
.note 3304 "unhandled or unknown relocation"
.np
If your program was built for another platform that supports the
LINEXE format, it may contain a construct that DOS/4G does not
currently support, such as a call gate.  This message may also occur
if your program has a problem mixing 16- and 32-bit code.  A linker
error is another likely cause.
.endnote