errors.gml

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

.* (c) Portions Copyright 1990, 1995 by Tenberry Software, Inc.
.*
.chap Error Messages
.*
.np
.ix 'messages' '&dos4gprd'
.ix 'extender messages' '&dos4gprd'
.ix '&dos4gprd' 'extender messages'
:cmt. .begnote $break
:cmt. .note &dos4gnam Fatal error: Syntax -- &dos4gnam <executable.xxx>
:cmt. This message occurs when you execute the &dos4gnam program without
:cmt. giving the name of an executable program on the command line.
:cmt. .note &dos4gnam Fatal error: Can't find file to load -- <filename>
:cmt. This message indicates that &dos4gnam couldn't find the executable
:cmt. file you asked it to execute.
:cmt. This should not happen if the program was spliced with a stub loader.
:cmt. .note &dos4gnam Fatal error: Can't find loader for file[#code#]  -- <filename>
:cmt. This message indicates that &dos4gnam was unable to find a loader that
:cmt. can load an executable of this format.
:cmt. .note &dos4gnam Fatal error: Can't initialize loader[#code#]  -- <loader>
:cmt. This error should not occur -- please call technical support if it
:cmt. does.
:cmt. .note &dos4gnam Fatal error: Loader failed -- <loader>
:cmt. This error should not occur, and may indicate that the executable file
:cmt. has been corrupted in some way.
:cmt. .note &dos4gnam Fatal error: INT31 initialization error
:cmt. This error should not occur -- please call technical support if it
:cmt. does.
:cmt. .note &dos4gnam Fatal error: No INT31 action found
:cmt. This error should not occur -- please call technical support if it
:cmt. does.
:cmt. .note &dos4gnam Fatal error: Can't locate DOS extender
:cmt. This error should not occur -- please call technical support if it
:cmt. does.
:cmt. You may get this error if you change the name of the "&dos4gexe" file
:cmt. to something else.
:cmt. .note &dos4gnam Fatal error: VMM initialization error[#code#]
:cmt. This error should not occur -- please call technical support if it
:cmt. does.
:cmt. .endnote
:cmt. .np
:cmt. The
:cmt. .us #code#
:cmt. mentioned in these error messages will be a decimal or hexadecimal
:cmt. number -- please be prepared to give it to technical support.
.np
:cmt. This excerpt from the DOS/4G manual currently being written lists
:cmt. DOS/4G error messages, with descriptions of the circumstances in which
:cmt. the error is most likely to occur, and suggestions for remedying the
:cmt. problem.
:cmt. .np
:cmt. With a few exceptions, this information applies to DOS/4GW Professional
:cmt. as well.  (Naturally, error messages that pertain to DOS extender
:cmt. features -- like DLLs -- that are not supported in DOS/4GW
:cmt. Professional will not arise with that product.)
The following lists DOS/4G error messages, with descriptions of the
circumstances in which the error is most likely to occur, and
suggestions for remedying the problem.
Some error messages pertaining to features &mdash like DLLs &mdash that
are not supported in &dos4g will not arise with that product.
In the following descriptions, references to DOS/4G, DOS4G, or
DOS4G.EXE may be replaced by &dos4gprd, &dos4gnam, or &dos4gexe should
the error message arise when using &dos4g..
.*
.section Kernel Error Messages
.*
.np
.ix '&dos4gprd' 'kernel error messages'
.ix 'kernel error messages'
.ix 'error messages' 'kernel'
This section describes error messages from the DOS/16M kernel
embedded in DOS/4G.
Kernel error messages may occur because of severe resource shortages,
corruption of DOS4GW.EXE, corruption of memory, operating system
incompatibilities, or internal errors in DOS/4GW.
All of these messages are quite rare.
.begnote $setptnt 2
.*
.note 0. involuntary switch to real mode
.np
The computer was in protected mode but switched to real mode without
going through DOS/16M.  This error most often occurs because of an
unrecoverable stack segment exception (stack overflow), but can also
occur if the Global Descriptor Table or Interrupt Descriptor Table is
corrupted.  Increase the stack size, recompile your program with
stack overflow checking, or look into ways that the descriptor tables
may have been overwritten.
.*
.note 1. not enough extended memory
.*
.note 2. not a DOS/16M executable <filename>
.np
DOS4G.EXE, or a bound DOS/4G application, has probably been corrupted
in some way.  Rebuild or recopy the file.
.*
.note 3. no DOS memory for transparent segment
.*
.note 4. cannot make transparent segment
.*
.note 5. too many transparent segments
.*
.note 6. not enough memory to load program
.np
There is not enough memory to load DOS/4G.  Make more memory
available and try again.
.*
.note 7. no relocation segment
.*
.note 8. cannot open file <filename>
.np
The DOS/16M loader cannot load DOS/4G, probably because DOS has run
out of file units.  Set a larger FILES= entry in CONFIG.SYS, reboot,
and try again.
.*
.note 9. cannot allocate tstack
.np
There is not enough memory to load DOS/4G.  Make more memory
available and try again.
.*
.note 10. cannot allocate memory for GDT
.np
There is not enough memory to load DOS/4G.  Make more memory
available and try again.
.*
.note 11. no passup stack selectors -- GDT too small
.np
This error indicates an internal error in DOS/4G or an
incompatibility with other software.
.*
.note 12. no control program selectors -- GDT too small
.np
This error indicates an internal error in DOS/4G or an
incompatibility with other software.
.*
.note 13. cannot allocate transfer buffer
.np
There is not enough memory to load DOS/4G.  Make more memory
available and try again.
.*
.note 14. premature EOF
.np
DOS4G.EXE, or a bound DOS/4G application, has probably been corrupted
in some way.  Rebuild or recopy the file.
.*
.note 15. protected mode available only with 386 or 486
.np
DOS/4G requires an 80386 (or later) CPU.  It cannot run on an 80286
or earlier CPU.
.*
.note 16. cannot run under OS/2
.*
.note 17. system software does not follow VCPI or DPMI specifications
.np
Some memory resident program has put your 386 or 486 CPU into Virtual
8086 mode.  This is done to provide special memory services to DOS
programs, such as EMS simulation (EMS interface without EMS hardware)
or high memory.  In this mode, it is not possible to switch into
protected mode unless the resident software follows a standard that
DOS/16M supports (DPMI, VCPI, and XMS are the most common).  Contact
the vendor of your memory management software.
.*
.note 18. you must specify an extended memory range (SET DOS16M= )
.np
On some Japanese machines that are not IBM AT-compatible, and have no
protocol for managing extended memory, you must set the DOS16M
environment variable to specify the range of available extended
memory.
.*
.note 19. computer must be AT- or PS/2- compatible
.*
.note 20. unsupported DOS16M switchmode choice
.*
.note 21. requires DOS 3.0 or later
.*
.note 22. cannot free memory
.np
This error probably indicates that memory was corrupted during
execution of your program.
.*
.note 23. no memory for VCPI page table
.np
There is not enough memory to load DOS/4G.  Make more memory
available and try again.
.*
.note 24. VCPI page table address incorrect
.np
This is an internal error.
.*
.note 25. cannot initialize VCPI
.np
This error indicates an incompatibility with other software.  DOS/16M
has detected that VCPI is present, but VCPI returns an error when
DOS/16M tries to initialize the interface.
.*
.note 26. 8042 timeout
.*
.note 27. extended memory is configured but it cannot be allocated
.*
.note 28. memory error, avail loop
.np
This error probably indicates that memory was corrupted during
execution of your program.  Using an invalid or stale alias selector
may cause this error.  Incorrect manipulation of segment descriptors
may also cause it.
.*
.note 29. memory error, out of range
.np
This error probably indicates that memory was corrupted during
execution of your program.  Writing through an invalid or stale alias
selector may cause this error.
.*
.note 30. program must be built -AUTO for DPMI
.*
.note 31. protected mode already in use in this DPMI virtual machine
.*
.note 32. DPMI host error (possibly insufficient memory)
.*
.note 33. DPMI host error (need 64K XMS)
.*
.note 34. DPMI host error (cannot lock stack)
.np
Any of these errors (32, 33, 34) probably indicate insufficient memory
under DPMI.  Under Windows, you might try making more physical memory
available by eliminating or reducing any RAM drives or disk caches.
You might also try editing DEFAULT.PIF so that at least 64KB of XMS
memory is available to non-Windows programs.  Under OS/2, you want to
increase the DPMI_MEMORY_LIMIT in the DOS box settings.
.*
.note 35. General Protection Fault
.np
This message probably indicates an internal error in DOS/4G.  Faults
generated by your program should cause error 2001 instead.
.*
.note 36. The DOS16M.386 virtual device driver was never loaded
.*
.note 37. Unable to reserve selectors for DOS16M.386 Windows driver
.*
.note 38. Cannot use extended memory: HIMEM.SYS not version 2
.np
This error indicates an incompatibility with an old version of
HIMEM.SYS.
.*
.note 39. An obsolete version of DOS16M.386 was loaded
.*
.note 40. not enough available extended memory (XMIN)
.np
This message probably indicates an incompatibility with your memory
manager or its configuration.  Try configuring the memory manager to
provide more extended memory, or change memory managers.
.endnote
.*
.section DOS/4G Errors
.*
.ix '&dos4gprd' 'error messages'
.ix 'error messages' '&dos4gprd'
.begnote $setptnt 4
.*
.note 1000 "can't hook interrupts"
.np
A DPMI host has prevented DOS/4G from loading.  Please contact
Tenberry Technical Support.
.*
.note 1001 "error in interrupt chain"
.np
DOS/4G internal error. Please contact Tenberry Technical Support.