TNT DOS-Extender Fatal Errors
Copyright (c) 1995, Phar Lap Software, Inc.
This file may not be redistributed.


Fatal Error TNT.10013:  Insufficient conventional memory for data 
buffers.

Description:	There is insufficient conventional memory available 
for the needs of TNT DOS-Extender.  A memory requirements summary is 
also printed showing how much memory is needed.  Use the -DEBUG 3 switch 
to get more detailed memory allocation data. 


Fatal Error TNT.10028:  Not a protected-mode program:  filename.

Description:	Not an EXP or PE file, or the file has been corrupted.


Fatal error TNT.10030:  386|VMM:  Couldn't reopen 386|VMM swap file 
after flushing it.

Description:	On a multitasking system, too many file handles are in 
use at once.  Reduce the number of simultaneously running programs, or 
don't use the -FLUSHSWAP switch to flush the swap file, and use the 
25C3h form of the EXEC call rather than 4Bh to avoid flushing the swap 
file on an EXEC. 


Fatal error TNT.10031:  386|VMM:  Page fault handler was reentered.

Description:	A hardware interrupt handler or a critical error 
handler caused a page fault, or you are running at privilege level zero 
(-UNPRIVILEGED) and the stack memory is not locked.  Make sure all 
memory used by hardware interrupt handlers (code, data, and stack) is 
locked. 


Fatal error TNT.10032:  386|VMM:  Bad page table entry in pg flt hndlr 
1st err val = linadr, 2nd = pg tbl entry, 3rd = pg tbl info.

Description:	If you installed your own page replacement handlers, 
they have a bug.  Otherwise, call Phar Lap technical support at (617) 
661-1510. 


Fatal error TNT.10033:  386|VMM:  Page replacement routine selected an 
invalid page:  1st err val = linadr, 2nd = pg tbl entry, 3rd = pg tbl 
info.

Description:	If you install your own page replacement handlers, 
they have a bug.  Otherwise, call Phar Lap technical support at (617) 
661-1510. 


Fatal error TNT.10034:  386|VMM:  Error reading .EXE file, or data file 
mapped in virtual memory.

Description:	Check to see if the file got renamed or deleted.  The 
user may have deleted the file if your program has the capability to run 
a DOS shell to let the user run any DOS command. 


Fatal error TNT.10035:  386|VMM:  Error reading swap file.

Description:	Check to see if the file got renamed or deleted.  The 
user may have deleted the file if your program has the capability to run 
a DOS shell to let the user run any DOS command. 


Fatal error TNT.10036:  386|VMM:  Page table entry not present in pg 
fault hndlr.

Description:	If you installed your own page replacement handlers, 
they have a bug.  Otherwise, call Phar Lap technical support at (617) 
661-1510. 


Fatal error TNT.10037:  386|VMM:  Error writing swap file.

Description:	Check to see if the file got renamed or deleted.  The 
user may have deleted the file if your program has the capability to run 
a DOS shell to let the user run any DOS command. 


Fatal error TNT.10038:  386|VMM:  Out of space for swap file.

Description:	There is no more disk space available on the swap 
device.  Use the -SWAPDIR switch to select a different swap device, or 
use -SWAPCHK FORCE to make sure this error cannot happen, or write an 
out-of-swap-space handler in your program. 


Fatal error TNT.10039:  386|VMM:  stack pointer in unmapped pages.

Description:	Your program changed the ESP register to an unmapped 
memory address.


Fatal error TNT.10049:  Ran out of stack buffers.

Description:	Use the -NISTACK switch to increase the number of 
allocated stack buffers, or don't nest mode switches more than three 
levels deep. 


Fatal error TNT.10050:  Attempted block move (INT 15h func 87h) to 
memory owned by TNT DOS-Extender: 1st error value = block base, 2nd 
error value = word len of block.

Description:	A program (such as a disk cache driver or a RAM disk 
driver) installed in your CONFIG.SYS or AUTOEXEC.BAT files is attempting 
to modify extended memory it does not own.  Remove the buggy program. 


Fatal error TNT.10051:  Ran out of machine state structs.

Description:	You are nesting mode switches too many levels deep.  
Re-architect your program to do less nested mode switching. 


Fatal error TNT.10052:  Couldn't reopen 386|VMM page log file after 
flushing it.

Description:	On a multitasking system, too many file handles are in 
use at once.  Reduce the number of simultaneously running programs, or 
don't use the -FLUSHSWAP switch to flush the page log file, and use the 
25C3h form of the EXEC call rather than 4Bh to avoid flushing the page 
log file on an EXEC. 


Fatal error TNT.10057:  Data too large for buffer for INT 21h, func num 
shown as err value.

Description:	Use a higher value for the -MINIBUF switch to allocate 
a larger data buffer for DOS system calls.


Fatal error TNT.10093:  Unable to allocate hardwired LDT descriptors 
from DPMI host.

Description:	Another Extended DOS program that requrires the use of 
the first 16 LDT descriptors is running in the same DOS box.  Quit from 
the other program before running your application.


Fatal error TNT.11000:  No executable file on command line

Description:	Your command line does not contain the name of an .EXE 
file.  Specify an .EXE file for TNT DOS-Extender to load.


Fatal error TNT.11010:  DOS-Extended applications nested too deeply

Description:	TNT DOS-Extender is limited to the number of times 
that a protected-mode application spawns a real-mode application, which 
in turn spawns another protected-mode application.  By default, the 
limit is 5 nested protected-mode applications and 5 nested real-mode 
applications.  Since it is unusual for 10 nested spawns to be done in a 
program, this error is most likely due to an outdated GOTNT.EXE being 
bound to an application, or to an infinite loop in an application.  To 
update GOTNT.EXE, simply run REBIND on the .EXE file.


Fatal error TNT.11020:  Unhandled exception occurred: <exception>

where exception is one of:  Divide by zero exception
	Single-step interrupt
	Parity error
	Breakpoint interrupt
	Overflow interrupt
	Bounds exception
	Invalid opcode exception
	Coproc not present exception
	Double fault exception
	Coprocessor segment overrun
	Invalid TSS exception
	Segment not present fault
	Stack fault
	General protection fault
	Page fault

Description:	The most common exception is a General protection 
violation (GP fault). If your program receives a GP fault, it violated 
the rules of protected mode. There is a bug in your program, OR you're 
using a piece of code which must be modified before it can be run in 
protected mode, OR you have unintentionally included real-mode code (for 
example, real-mode libraries) in the program.  

In addition to the CPU register dump, TNT DOS-Extender displays the 
process ID (ProcessId), thread ID (ThreadId), and exception error code.  
For GP faults, the error code generally bears some resemblance to an 
invalid selector that caused the fault (for example, an attempt to move 
the number B800h into ES will generate ERRORCODE=B800).

Correct the bug that caused the exception, and try again. If you need to 
catch the exception, rather than terminate the program with this 
message, use the structured exception handling mechanism.


Fatal error TNT.11030:  LOADDLL filename list too long

Description:	The TNT DOS-Extender -LOADDLL switch takes a list of 
one or more dynamic link libraries (DLLs) to be loaded before running 
the protected-mode .EXE file. For example: TNT -LOADDLL PHOO,BAR HELLO. 
Up to 512 bytes can be used to list DLL names. You have exceeded this 
maximum.  Specify fewer DLLs.


Fatal error TNT.11040:  Cannot load DLL; MS-DOS error number <number>

Description:	TNT DOS-Extender cannot load your program due to a DOS 
error.  Verify that the DLL and .EXE files have been built properly and 
that the DLL is on the PATH, and try again.


Fatal error TNT.11060:  Cannot start program; real-mode multitasking not 
supported

Description:	You are attempting to execute more than one real-mode 
program concurrently.  Do not attempt to run more than one real-mode 
program at a time.


Fatal error TNT.11070:  Stub is out of date

Description:	The files REBIND.EXE, TNT.EXE, and GOTNT.EXE must all 
have the same version number.  The version of GOTNT you have does not 
match the other two files.  Rebind your program with the version of 
GOTNT that matches your REBIND.EXE and TNT.EXE files.


Fatal error TNT.11080:  <functionname> function called but not 
implemented

Description:	You have called a Win32 API function which has not yet 
been implemented.  Try to  find a workaround that does not use the 
unimplemented function, or write your own replacement function and 
install it with SetProcAddress().


Fatal error TNT.11170:  Cannot load <filename> at <hexaddress>: no 
fixups

Description:	The file was linked with no fixups, and TNT DOS-
Extender could not load the file at the specified base address.  Relink 
the file with fixups, and try loading again.


Fatal error TNT.11210:  Cannot load program : unknown error code 
<number>

Description:	TNT DOS-Extender cannot load your protected-mode 
executable because it encountered an unknown error.  The number 
specified in the message is a Windows NT error code.  Please consult the 
Microsoft documentation for more information.


Fatal error TNT.11230:  TNT initialization failed

Description:	This message usually follows another, more 
descriptive, message describing the cause of the initialization failure.  
The most common reason for failing is insufficient memory.  Correct the 
problem identified in the previous message and try again.


Fatal error TNT.11250:  Command line error : environment variables 
nested too deeply at <envvar>

Description:	Environment variables optionally used by TNT DOS-
Extender can themselves contain references to other environment 
variables, using the %envvar syntax. However, there is a limit of four 
nested environment variables.  Most likely, you have an infinite loop.  
Don't nest more than four environment variables.


Fatal error TNT.11260:  Command line error : command files nested too 
deeply

Description:	TNT DOS-Extender command files can themselves contain 
references to other command files, using the @cmdfile and @@cmdfile 
syntax.  However, there is a limit of four nested command files.  Most 
likely, you have an infinite loop.  Don't use so many nested command 
files.


Fatal error TNT.11270:  Command line error : unknown command switch 
<switch>

Description:	An illegal switch has been specified on the TNT DOS-
Extender command line, in an environment variable, or in a command file.  
Fix the TNT DOS-Extender switch.


Fatal error TNT.11280:  Command line error : extra command line argument 
<argument>

Description:	The command line contains more arguments than are 
expected by the program.  Remove the extra argument.


Fatal error TNT.11290:  Command line error : cannot open command file 
<filename>

Description:	TNT DOS-Extender was unable to open the named command 
file. Typical reasons include an incorrect file name, a nonexistent 
file, or a directory that is inaccessible.  Correct the spelling of the 
file name. The default extension for command files is .CMD.


Fatal error TNT.11300:  Command line error : cannot read command file 
<filename>

Description:	TNT DOS-Extender was unable to read the command file.  
Make sure the command file is accessible, and try again.


Fatal error TNT.11310:  Command line error : command too long <command>

Description:	The specified command line contains more than 511 
characters.  Break the command into multiple lines.


Fatal error TNT.11320:  Command line error : invalid number <number>

Description:	One of the TNT DOS-Extender command-line switches was 
expecting a numeric value, but a non-numeric value was specified.  Check 
the value, and try again.


Fatal error TNT.11330:  Command line error : invalid filename <filename>

Description:	The command file named with the @cmdfile syntax is not 
a valid filename.  Check the filename, and try again.


Fatal error TNT.11340:  Command line error : missing value for 
<argument>

Description:	The named TNT DOS-Extender switch expects an argument, 
but none has been supplied.  Consult Chapter 4 of this manual for 
arguments expected by TNT DOS-Extender switches.  Supply the missing 
value, and try again.


Fatal error TNT.11350:  Cannot load program : file not found

Description:	TNT DOS-Extender cannot find an .EXE file with the 
specified name.  Check your DOS PATH, and/or the spelling of the file 
name, and try again.


Fatal error TNT.11360:  Cannot load program : directory not found

Description:	TNT DOS-Extender cannot find the named subdirectory.  
Check your spelling, and/or make sure the subdirectory really exists, 
and try again.


Fatal error TNT.11370:  Cannot load program : too many open files

Description:	TNT DOS-Extender cannot load your protected-mode 
program because there aren't enough free DOS file handles.  Either 
increase the number of DOS file handles by increasing the FILES= count 
in CONFIG.SYS, or close some files.


Fatal error TNT.11380:  Cannot load program : access denied to file

Description:	TNT DOS-Extender cannot load your protected-mode 
executable because the file cannot be accessed.  Most likely, this is 
because the file resides on a network server, and you don't have access 
rights to the file.  Get your network/system administrator to give you 
access rights to the file, or try a different file.


Fatal error TNT.11390:  Cannot load program : out of memory

Description:	TNT DOS-Extender cannot load your protected-mode 
executable because all conventional and extended memory is exhausted.  
Remove some TSRs, or install more memory.


Fatal error TNT.11400:  Cannot load program : invalid drive

Description:	TNT DOS-Extender cannot load the specified file 
because the drive letter is invalid.  Specify a valid DOS drive letter.


Fatal error TNT.11410:  Cannot load program : entry point not found in 
DLL

Description:	When attempting to load your program, TNT DOS-Extender 
could not resolve one of the imports found in the file.  Correct the 
problem in the .EXE or .DLL file.


Fatal error TNT.11420:  Cannot load program : invalid or corrupted .EXE 
file

Description:	TNT DOS-Extender cannot load the specified file 
because it is not a valid .EXE file.  For example, typing TNT HELLO.C 
instead of TNT HELLO.EXE will result in this error message.  Check the 
file with the MAPEXE utility, specify a different file, or relink the 
file.


Fatal error TNT.11430:  Cannot load program : DLL not found

Description:	Your protected-mode executable cannot be loaded by 
TNT DOS-Extender because it depends, directly or indirectly, upon a 
dynamic link library (DLL) which TNT DOS-Extender cannot find.  Make 
sure that the TNT DOS-Extender DLLs are in the same directory as TNT.EXE 
(e.g., \TNT\BIN), on the DOS PATH, in the same directory as your 
protected-mode executable, or in the current directory.


Fatal error TNT.11440:  Cannot load program : DLL attach routine failed

Description:	The auto-initialization routine of a DLL (dynamic link 
library) returned 0, indicating an error in DLL initialization.  
Determine why the DLL initialization failed, and try again.


Fatal error TNT.11450:  Unimplemented function <function> called at 
<address> access denied to file

Description:	You have called a Win32 API function which has not yet 
been implemented.  Try to  find a workaround that does not use the 
unimplemented function, or write your own replacement function and 
install it with SetProcAddress().


Fatal error TNT.11460:  A coprocessor error has occurred under Windows 
and cannot be handled because the PHARLAP.386 device driver is not 
installed in SYSTEM.INI.  Program terminated.

Description:	The PHARLAP.386 device driver is not installed in 
SYSTEM.INI.  You should install the PHARLAP.386 device driver in 
SYSTEM.INI.  See section 3.1 for more information.


Fatal error TNT.11490:  Could not grow stack on demand - out of memory

Description:	When TNT DOS-Extender starts your program, it 
allocates  an initial stack of size commitsize.  As your program 
executes, TNT automatically grows the stack as needed to a maximum of 
reservesize.  This error message will appear if TNT DOS-Extender cannot 
find more memory for the stack.
	With 386|LINK, these two sizes are always identical, and are set 
with the -STACK switch.  This error will therefore never occur in a 
program built with 386|LINK.
	With Microsoft LINK, however, these values can be different.  Use 
the -stack:reservesize,commitsize switch to increase the stack size of 
your program.  See Section 5.7, "Running out of Stack Space".


Fatal error TNT.12020	Error returned by attach routine for DLL dllname 
while loading pgm exename.

Description:	The initialization code for the dllname DLL failed.  
Determine why the initialization failed and try again.


Fatal error TNT.12030	File filename not found while loading program 
exename.

Description:	One of the files required by your program could not be 
found.  Check your DOS PATH and/or the spelling of the file name, and 
try again.


Fatal error TNT.12040	Insufficient memory to load program exename.

Description:	TNT ran out of memory (both extended and conventional) 
during initialization.  Remove some installed TSRs, buy more memory, or 
use 386|VMM.


Fatal error TNT.12050	Bad file format in file filename while loading 
program exename.

Description:	TNT cannot load the file filename, because it is not a 
valid .EXE file.  Check the file with the MAPEXE utility, specify a 
different file, or relink the file.


Fatal error TNT.12060	File seek error in file filename while loading 
program exename.

Description:	A DOS file seek error occurred while reading data from 
file filename.  Either the file is corrupted or DOS is unable to access 
the file due to network or other problems.


Fatal error TNT.12070	File read error in file filename while loading 
program exename.

Description:	A DOS file read error occurred while reading data from 
file filename.  Either the file is corrupted or DOS is unable to access 
the file due to network or other problems.


Fatal error TNT.12080	Insufficient memory to initialize DosStyle 
loader

Description:	TNT ran out of memory (both extended and conventional) 
during initialization.  Remove some installed TSRs, buy more memory, or 
use 386|VMM.


Fatal error TNT.12090	Function funcname not exported by DLL dllname 
while loading program exename.

Description:	Your program, exename, uses funcname which is supposed 
to be exported by dllname.  Make sure you have specified the right DLL.



TNT DOS-Extender Errors;


Error TNT.20001:  Invalid baud rate specified with -BAUD switch.

Description:	Valid baud rates are 110, 150, 300, 600, 1200, 2400, 
4800, or 9600.  If you need a different baud rate, use the DOS MODE 
command to set the port parameters and don't use the -BAUD switch.


Error TNT.20002:  Channel initialization for I/O redirection failed. 

Description:	Check to make sure you're using the correct serial 
port.  Use -COM1 for port 1 and -COM2 for port 2.  Try using the DOS 
MODE command to set the port parameters and not using the -BAUD switch.

Error TNT.20003:  Serial channel does not exist _ I/O redirection 
failed.

Description:	Use -COM1 for serial port 1, -COM2 for serial port 2. 


Error TNT.20004:  No .EXE file specified.

Description:	Enter the name of your .EXE file on the command line. 


Error TNT.20005:  System does not have an 80386 or later processor.

Description:	Do not run TNT DOS-Extender on 8086- or 286-based PCs. 


Error TNT.20006:  QEMM must be on to run under DESQview.

Description:	Install QEMM-386 in your CONFIG.SYS file. 


Error TNT.20007:  MS-DOS version 3.0 or later required.

Description:	Do not run TNT DOS-Extender under versions of MS-DOS 
prior to 3.0. 


Error TNT.20009:  The 80386 chip on this system does not always obtain 
correct results for 32-bit multiply instructions.  If you are sure your 
program does not use any 32-bit MUL instructions, you can force the 
program to run with the -NOMUL command line switch.

Description:	Some Intel 80386 chips have a chip errata that can 
cause erroneous results from a 32-bit MUL instruction.  Either get a new 
chip, or make sure your program doesn't use the MUL instruction. 


Error TNT.20010:  The 80386 chip in your system was manufactured prior 
to step B1 of the chip.  Chip steps prior to B0 have a bug that makes 
them unable to switch from protected mode back to real mode.  If you are 
sure that the 80386 chip in your system is step B0, then use the -B0 
switch on the command line to force this program to run.  If you use the 
-B0 switch with a chip earlier than step B0, it will crash your system!

Description:	TNT DOS-Extender can run on B0 stepping 80386 chips, 
but not A steppings.  If you know your computer has a B0 chip step, use 
the -B0 switch to tell TNT DOS-Extender it's OK to run. 


Error TNT.20011:  Couldn't obtain HW interrupt vectors from EMS 
emulator.

Description:	The EMS emulator in your CONFIG.SYS file doesn't 
correctly implement the VCPI interface.  Remove it or use QEMM-386 or 
386MAX instead. 


Error TNT.20012:  Bad value for -HWIVEC or -INTMAP switch.

Description:	The -HWIVEC and -INTMAP switches must be a multiple of 
8, must be between 30h and F8h, and must not conflict with the -PRIVEC 
switch (default value 80h). 


Error TNT.20013:  Illegal switch values:  -MINIBUF n, -MAXIBUF n. 
Illegal switch values:  -EXTLOW n, -EXTHIGH n.

Description:	The -MINIBUF and -MAXIBUF switches must be between 1 
and 64, and -MAXIBUF must be >= -MINIBUF.  The -EXTLOW switch must be >= 
1 MB (100000h). 


Error TNT.20014:  -NISTACK must be between 6 and n

Description:	The -NISTACK switch cannot be less than 6 or greater 
than the upper bound specified in the error message. 

Error TNT.20015:  A maximum of 63 K may be alloc'd with -NISTACK and 
-ISTKSIZE.

Description:	The product of the -NISTACK and -ISTKSIZE switch 
values cannot be greater than 63. 


Error TNT.20016:  -CALLBUFS must be < = 64 KB.

Description:	The -CALLBUFS switch value cannot be greater than 64. 


Error TNT.20018:  -NOPAGE cannot be used with -OFFSET or -REALBREAK.

Description:	Stop using conflicting switches. 


Error TNT.20019:  -MINSWFSIZE cannot be greater than -MAXSWFSIZE.

Description:	Adjust the values appropriately. 


Error TNT.20020:  -VSCAN value must be between n and m.

Description:	Adjust the value as specified. 


Error TNT.20021:  Can't use 386|VMM with -NOPAGE or real-mode pgm.

Description:	Stop using -NOPAGE.  You may want to use -ERRATA17 
with 386|VMM if your application uses the 387 coprocessor. 


Error TNT.20022:  -SWAPCHK ON used, but unable to get info on swap 
device: X.

Description:	The MS-DOS Get Disk Space call (36h) returns an error 
for the device on which the swap file is located.  If it's a network 
device, check to see if the network software has a bug.  386|VMM must be 
able to get the free disk space in order to run with the -SWAPCHK ON 
switch setting. 


Error TNT.20023:  EMS emulator returned error on 'get physical address' 
call.

Description:	The EMS emulator in your CONFIG.SYS file doesn't 
correctly implement the VCPI interface.  Remove it or use QEMM-386 or 
386MAX instead. 


Error TNT.20024:  Can't alloc system conventional mem buffer for GDT and 
LDT.

Description:	There is insufficient conventional memory available 
for the needs of TNT DOS-Extender.  A memory requirements summary is 
also printed showing how much memory is needed.  Use the -DEBUG 3 switch 
to get more detailed memory allocation data. 


Error TNT.20025:  Relative paths not permitted with -SWAPDIR.

Description:	Specify an absolute path. 


Error TNT.20029:  Bad value for -PRIVEC switch.

Description:	The -PRIVEC switch value must be between 30h and FFh, 
and must not conflict with -HWIVEC, -INTMAP, or vectors used for 
hardware interrupts (normally 70h-77h). 


Error TNT.20030:  Can't use -A20 with XMS driver or VCPI (EMS emulator)

Description:	Stop using the -A20 switch. 


Error TNT.20031:  Reg CR0 has bad value for real mode:  value

Description:	Call Phar Lap technical support at (617) 661-1510. 


Error TNT.20033:  Can't enable address line 20.

Description:	There's a hardware problem with your PC.  Call Phar 
Lap technical support at (617) 661-1510. 


Error TNT.20034:  Unable to turn off program using virtual 8086 mode. 
Turn it off manually or take it out of CONFIG.SYS.

Description:	If the program using V86 mode is an EMS emulator that 
doesn't support VCPI, replace it with QEMM-386 or 386MAX. 


Error TNT.20035:  The 386 chip is currently executing in virtual 8086 
mode under the control of another program.  You must turn off this other 
program in order to use TNT DOS-Extender to run in protected mode.

Description:	If the program using V86 mode is an EMS emulator that 
doesn't support VCPI, replace it with QEMM-386 or 386MAX. 


Error TNT.20036:  EMS emulator reports VCPI but doesn't use V86 mode.

Description:	The EMS emulator in your CONFIG.SYS file doesn't 
correctly implement the VCPI interface.  Remove it or use QEMM-386 or 
386MAX instead. 


Error TNT.20037:  Cannot use -NOPAGE under V86 mode environment.

Description:	Stop using -NOPAGE, or remove the EMS emulator or 
other program that is running in V86 mode. 


Error TNT.20038:  You must use version 6.0 or later of REBIND to bind 
your program.

Description:	Use the copy of REBIND that came with your bindable 
TNT DOS-Extender. 


Error TNT.20039:  Bindable 386|VMM driver can only run if bound with 
REBIND.

Description:	Use the copy of REBIND that came with your bindable 
TNT DOS-Extender. 


Error TNT.20040:  Development 386|VMM driver cannot be bound with 
REBIND.

Description:	Use the -VMFILE switch to load the development version 
of 386|VMM. 


Error TNT.20041:  Not a Phar Lap 386|VMM file:  filename.

Description:	The file selected with the -VMFILE switch has been 
corrupted, or is not 386|VMM from Phar Lap Software. 


Error TNT.20042:  Incompatible version of 386|VMM file.

Description:	Use the same version number of 386|VMM as TNT DOS-
Extender.  You can obtain the version numbers from the distribution 
disks, or by using the -BANNER switch. 


Error TNT.20043:  Invalid configuration block in 386|VMM file.

Description:	The file selected with the -VMFILE switch has been 
corrupted, or is not 386|VMM from Phar Lap Software. 


Error TNT.20044:  Couldn't init page table from EMS emulator.

Description:	The EMS emulator in your CONFIG.SYS file doesn't 
correctly implement the VCPI interface.  Remove it or use QEMM-386 or 
386MAX instead. 


Error TNT.20045:  Can't open .EXE file:  filename.

Description:	Check the spelling of the filename, and check to see 
if it is in a directory on the environment PATH. 


Error TNT.20046:  Couldn't get free mem size from EMS emulator.

Description:	The EMS emulator in your CONFIG.SYS file has a bug.  
Remove it or use QEMM-386 or 386MAX. 


Error TNT.20047:  Can't read in header for .EXE file:  filename.

Description:	The file has been corrupted, or is not an .EXE file. 


Error TNT.20048:  -GDTENT or -LDTENT value too large.

Description:	The -GDTENT and -LDTENT switch values must be <= 8192. 


Error TNT.20049:  Can't allocate conventional memory for 386|VMM.

Description:	There is insufficient conventional memory available 
for the needs of TNT DOS-Extender.  A memory requirements summary is 
also printed showing how much memory is needed.  Use the -DEBUG 3 switch 
to get more detailed memory allocation data. 

Error TNT.20055:  Can't open 386|VMM file:  filename.

Description:	Check the spelling of the file name, and whether it is 
in a directory on the environment PATH. 


Error TNT.20056:  Can't read 386|VMM file:  filename.

Description:	The file is corrupted. 


Error TNT.20058:  Can't create VM swap file of size n in directory 
dirname.

Description:	There is insufficient swap space on the selected swap 
device.  Use the -SWAPDIR switch to select a different swap device. 


Error TNT.20070:  Can't create -PAGELOG file:  filename.

Description:	A DOS error occurred attempting to create the file 
specified with the -PAGELOG switch.  Check the spelling of the file name 
and path. 


Error TNT.20072:  -VSLEN value must be >= n.

Description:	The -VSLEN switch value must be larger than the number 
shown in the error message. 


Error TNT.20073:  The -HWIVEC and -INTMAP switches can't both be used.

Description:	Remove one of the switches. 


Error TNT.20074:  Can't use -REALBREAK under this version of DPMI.

Description:	The DPMI host doesn't support -REALBREAK.  Stop using 
-REALBREAK, or run your program only under DPMI hosts supporting 
-REALBREAK.  Under Windows 3.x, install the PHARLAP.386 VxD.  Under 
OS/2, update to OS/2 2.1 or later.


Error TNT.20084:  There is already a DOS extender running in this 
virtual machine, and Windows 3.0 only allows one extender in a VM

Description:	There is already a DOS-extended program running in the 
virtual machine.  Run your TNT DOS-Extender program in another virtual 
machine or wait until the first program finishes.


Error TNT.21010:  Invalid pointer passed to free or realloc

Description:	A call with a bad pointer was made to LocalReAlloc(), 
LocalFree(), GlobalReAlloc(), or GlobalFree().  Fix the bug that caused 
the invalid pointer.


Error TNT.21060:  Unsupported INT 21H (AX = hex) issued at CS:EIP = 
hex1:hex2 - terminating process (PID = hex3)

Description:	You have used an unsupported INT 21 call in your 
NtStyle program.  Use an equivalent Win32 API call.  See section 5.14.1 
for a list of INT 21h calls that are not supported for NtStyle programs.


Error TNT.40025:  Processor exception occurred <exception number>

Description:	<exception number> is an Intel exception number.  
Refer to the Intel documentation for more information.
TNT DOS-Extender Warnings 
Warning TNT.31000:  -NOHAND used, exception handler not installed

Description:	You have used the -NOHAND switch.  The exception 
handlers listed were not installed by TNT DOS-Extender.


Warning TNT.31010:  -NOHAND used, interrupt handler not installed:

Description:	You have used the -NOHAND switch.  The interrupt 
handlers listed were not installed by TNT DOS-Extender.


Warning TNT.31020:  Out of file handles. Increase value of FILES= 
statement in CONFIG.SYS

Description:	All the available file handles are in use.


