+‚00‚016‚02k‚03­‚*3΂04`‚05œ‚*5¿‚06 ‚*6&‚07É‚*7÷‚08ú‚*8*‚09E‚*9x‚0A*‚*AV‚0B‚*B'‚0C³‚*CÛ‚0Dš ‚*DË ‚0Eä ‚*E" ‚0F ‚*FG ƒ010˜ ƒ*10Ç ƒ011* ƒ*11g ƒ012ó ƒ013 ƒ*13gƒ0143ƒ*14eƒ015‡ƒ*15³ƒ016؃*16ûƒ017rƒ*17¤ƒ018@ƒ023ƒ*23³ƒ024΃*24ƒ025½ƒ*25Úƒ029Zƒ*29qƒ02A²ƒ02Bîƒ02Cƒ02F>ƒ030nƒ031–ƒ032¹ƒ035ãƒ040ƒ0415ƒ042Oƒ043}ƒ044·ƒ045ȃ046äƒ047 ƒ*475ƒ048tƒ049ƒ04C¼ƒ04DÖƒ04Eñƒ04Fƒ050>ƒ051\ƒ052yƒ053—ƒ054­ƒ*54åƒ055èƒ056ƒ057_ƒ*57¢ƒ058uƒ*58¢ƒ059ƒ*59ƒ05BŸƒ05C¼ƒ05Eöƒ*5Eƒ05F‹ƒ060у*60ìƒ061j ƒ*61™ ƒ062ä ƒ*62!ƒ06E6!ƒ*6Ex!ƒ06F"ƒ*6FH"ƒ070Ø"ƒ*70#ƒ071O#ƒ072†#ƒ073Æ#ƒ*73é#ƒ074ö$ƒ*74%%ƒ075&ƒ*75J&ƒ076T'ƒ*76€'ƒ077¿(ƒ*77î(ƒ078š)ƒ*78Ô)ƒ088¹*ƒ089è*ƒ08A+ƒ08B&+ƒ*8BE+ƒ08C¤,ƒ08D¼,ƒ08Eû,ƒ08F-ƒ090=-ƒ0A0Z-ƒ0A1v-ƒ0A2”-ƒ0A3¯-ƒ0A4×-ƒ0A5ô-ƒ*A5,.ƒ0A6ä.ƒ0A7/ƒ*A7[/ƒ0A8ß/ƒ0A90ƒ0B1P0ƒ0B40ƒ0B5–0ƒ0B6©0ƒ0B7Í0ƒ*B7ô0ƒ0B8«2ƒ0B9Õ2ƒ0BA 3ƒ0BBp3ƒ0BCš3ƒ0BDÙ3ƒ0BE!4ƒ0C4d4ƒ0C5Š4ƒ0C6©4ƒ*C6É4ƒ0C85ƒ0C9E5ƒ0CA„5ƒ0CBÆ5ƒ0CDå5ƒ0CE"6ƒ0CF^6ƒ0D0Š6ƒ0D1©6ƒ0D2È6ƒ0D3ç6ƒ0D47ƒ0D5%7ƒ0D6Z7ƒ0D77ƒ0D8¦7ƒ0D9»7ƒ0DAã7ƒ0DB8ƒ0DC38ƒ0DD\8ƒ0DEw8ƒ0DFŽ8ƒ0E0Ì8ƒ*E0ç8ƒ0E129ƒ*E1^9ƒ0E2²9ƒ*E2Ö9ƒ0E3™:ƒ0E4À:ƒ0E5ï:ƒ0F8;ƒ0F9";„0200[;„*200;„0201F<„0214l<„0220†<„0221Â<„0222ù<4Type definition record with unrecognizable format. 3Array's lower bound is unknown - zero is assumed. @Symbol is not an array or has fewer dimensions than specified. Array index is out of bounds. The array index specified in the symbolic request was larger than the maximum dimension defined for the array in the original source program. :Referenced array expects a single character array index. !Address of module is not known. HThe module referenced contains no debug information and the address of the module can not be determined. DB86 can not provide symbolic support without symbolic information in the module being loaded. Be sure that the DEBUG option is being used when compiling and assembling or symbolic information will not be generated. Unknown module specified. ¡A module name was specified that could not be found. Be sure the name is spelled correctly or check the list of program modules with the DIR MODULE command. ,No line information was loaded for module. There was no line information in the module. DB86 can not provide source support without line information in the module being loaded. Be sure that the DEBUG option is being used when compiling and assembling or line information will not be generated. .No symbol information was loaded for module. There was no symbolic information in the module. DB86 can not provide source or symbolic support without symbolic information in the module being loaded. Be sure that the DEBUG option is being used when compiling and assembling or symbolic information will not be generated. 1Cannot determine module for specified location. °Could not find the specified location in any known module. Either the specified location is outside of the program or in a module for which there is no symbol information. *Cannot determine current default module. ¯Could not find current location in any known module. Either the current execution point is outside of the program or in a module for which there is no symbol information. Symbol currently not active. ŠThe symbol is stack resident and is only available when the current execution point is in the procedure in which the symbol is defined. &Symbol not known in current context. ½The debugger cannot find and identify the symbol as either a keyword or program symbol. This message can occur if a debugger key word or program symbol does not exist or is misspelled. /No symbol information was loaded for program. There is no symbolic information in the loaded program. DB86 can not provide source or symbolic support without symbol information in the loaded program. Be sure that the DEBUG option is being used when compiling and assembling or symbol information will not be generated. <Symbol reference of unsupported type, displayed as a word. ùDB86 does not know the type of the symbol being referenced. This may be because no type information exists in the program or DB86 does not support the symbolic type being referenced. By default The contents of the symbol is display as a WORD. (Symbol is not known to be a structure. OThe symbol was specified as a structure and was found not to be a structure. -Symbol is not a known structure field name. aThe symbol was specified as part of a structure and was not found to be part of the structure. ;Cannot determine offset of field from start of structure. ŠThe debugger was unable to determine the size of one of the preceding structure fields, hence the requested field cannot be referenced. +Nested symbolic references not permitted. ESymbol isn't a pointer variable or its dereference type is unknown. ÊOnly symbols that are defined as pointers and that have an additionally defined type may be dereferenced. Only C and PASCAL allow this, PL/M does not and hence PL/M pointer may not be dereferenced. 0Specified line is not an executable statement. The specified line does not exist in the loaded program. Lines that exist may always be found by using the DIR LINE command. Disappearing line numbers may occur if compiling with any optimize level higher than 0 because some lines may be eliminated during the optimization process. *Specified line does not exist in module. #The specified line does not exist in the referenced module. Lines that exist may always be found by using the DIR LINE command. Disappearing line numbers may occur if compiling with any optimize level higher than 0 because some lines may be eliminated during the optimization process. !Cannot evaluate line reference. uThe segment part of line reference pointer not known. It may be that no symbol information was loaded for module. 0Specified type is incompatible with directory. šSpecified type cannot be used with the specified (or default) directory. For example, DIR PUBLIC LINE is contradictory, as there are no public lines. ?Cannot perform symbol table request. No user program loaded. 0Breakpoint is already defined at this address. In order to define another breakpoint address to this address the existing break must be removed. Position the address into the view window where you may use the F9 key to toggle the breakpoint off. Setting SCOPE to this address will position the break into the view window. 0Maximum number of temp breaks already defined. »DB86 limits the number of temp breaks that may be defined to 10. Either some of the existing temp breaks must be removed or the breakpoint must be assigned to a break of another type. Execution cannot proceed. ~Either you have not loaded a program or else your program has Exited. In either instance execution is not allowed to occur. Workspace exceeded. ?There is no DOS memory remaining for the debugger to utilize. :The name is either undefined or not of the correct type. The name is undefined. 4The name is already defined with a different type. .Illegal type specified in DIR DEBUG command. &The named object is not a literally. !Illegal assignment to register. (String too long to perform assignment. Overlay name does not exist. 0Attempt to PUT or APPEND a local debug object. I/O error on PUT file. ,This command is not currently implemented. 8This command not allowed inside of a compound command. Invalid type. Invalid type conversion. $String longer than 254 characters. )String too long for numeric conversion. =Strings of length >1 may not be used in numeric conversion. Illegal type in output. +Unmatched double quotes in format string. Invalid format string. Output buffer overflow. *Invalid floating point value for output. Invalid expression for MTYPE. Invalid boolean operation. Invalid string operation. Invalid pointer operation. Unknown operation. 6Attempt to assign value to code instead of variable. An attempt was made to assign an expression to a location associated with user code (eg, :main.proc1 = 5, where proc1 is a procedure in module main). Direct assignments may only be made to variables or with mtype operators (eg, BYTE .:main.proc1 = 5). 3Attempt to assign illegal value to BASE variable. @Cannot use editor if debugger was invoked with SUBMIT control. ANot in a procedure or in a procedure with no debug information. ÑIn order for the calling procedure to be identified (and the CALLS command to function properly), the current execution point must be in a procedure, or in a procedure for which there is debug information. +The debugger has overflowed its 86 stack. cThe sequence of operations performed by the debugger caused DB86 to overflow its run-time stack. UDI Exception. „The operation performed generated a DB86 run-time exception. Operations such as divide-by-zero are known to cause this exception. Illegal extended integer. 8Attempt to assign illegal value to INPUTMODE variable. %Error occurred during shell escape. lEither there is insufficient DOS memory available or COMMAND.COM is not visible in the current directory. DThe number specified in the HELP E must be a decimal number. Illegal File Extension. |The specified file extension is not valid for DOS. Extensions are restricted to no more than three characters in length. -Maximum number of file extensions exceeded. IThe maximum number of list file extensions that may be specified is 10. Illegal file name in SETMOD. 0The filename used is not a valid DOS filename. @No data segment information. Program may execute incorrectly. ‹The load module did not provide any information about the data segment. Therefore, execution of the program may have unexpected results. ANo stack segment information. Program may execute incorrectly. ŽThe load module did not provide any information about the stack segment. Therefore, execution of the program may have unexpected results. EProgram cannot be loaded. Start address needs fixing up by linker. .Program start address needs fixup by linker. 5The 8087 Emulator was not found in the load module. >Missing CH8087 option when loading a program with real math. !Bad object record in load file. The loader encountered a record while loading the program that was not recognized. This can be caused by loading a file that is not an object file (for example a source file), an object file that is not in OMF-86 form, or an object file that has been corrupted. -Load file contains absolute load addresses. ÷The load file contains a module which has been fixed in memory. Possibly the file has been run through LOC86 which creates an absolute program. The debugger will only load relocatable (LTL) programs linked with LINK86 using the BIND control. *Load file contains unresolved externals. The program being loaded was found to have unresolved referenced to symbols and the program load has been aborted. Be sure all program modules have been properly linked together and that no unresolved symbol warnings are issued during the final program link. *Accessed Symbol not in resident overlay. =The symbol being accessed is defined in an overlay that is not currently resident in the user program overlay area. The value returned will not be correct as it represents a value that exists in another overlay. Correct reverences may only be made when the overlay in which the symbol is defined is in memory. -Memory segment request failure during load. ªMore memory is needed to load program than is available. More memory may be obtained by eliminating programs that are resident in memory before the debugger is used. 8Load module contained no starting address information. ãThe load module did not provide any information about the starting address. The load has been aborted and execution of the program is not possible. Be sure that a main module has been created and linked into the program. -Divide by zero (operation yields 0 result). Invalid type for arithmetic. Invalid integer operation. Real math is not available. ]In order to use real math (including any operations or reference to real numbers), you must have an 8087 math coprocessor or have the 8087 emulator linked into the program under debug. This error may be detected if references to 8087 libraries were encountered in the loaded program but neither the 87 emulator or math chip was found by DB86. Invalid real number. =Attempted real comparison with NAN, +infinity or -infinity. Invalid real operation. %Invalid extended integer operation. Illegal numeric constant. Attempt to INCLUDE :CI:. I/O error on INCLUDE file. I/O error on LIST file. &I/O error while loading object file. Could not open load file. 6Error while attempting to open virtual symbol table. ¶The virtual symbol table uses :WORK: for the disk-resident portion of the virtual symbol table. Ensure that the device for :WORK: is ready and that DB86 has access rights to it. 9Error while attempting to seek in virtual symbol table. :Error while attempting to write to virtual symbol table. ‚The disk device used for the virtual symbol table cannot be written to. The most common cause of this problem is a full device. 7Error while attempting to close virtual symbol table. 6Error while attempting to read virtual symbol table. /First address is greater than second address. Illegal mnemonic. Illegal number. "Unrecognized 8086/8087 mnemonic. %Illegal use of indirect addressing. µThe correct forms of indirect addressing are: [BX] + offset [BP] + offset [DI] + offset [SI] + offset [BP] [DI] + offset [BP] [SI] + offset [BX] [DI] + offset [BX] [SI] + offset The symbolic reference (of the form :MODULE.SYMBOL.SYMBOL.etc) and the '+ offset' are optional. (Illegal single line assembler operand. 4Single line assembler syntax error. See HELP ASM. cMemory pointer (eg. BYTE, WORD, etc) without memory operand (eg. number or symbolic reference). (Too few operands for this instruction. =Illegal operands, both operands appear to reference memory. FThe types of the operand(s) do not match the mnemonic or each other. AOne byte relative jump is out of range. Range is -128 to +127. $Bad minor number in 8087 function. Expression stack underflow. BASE must be 2T, 10T or 16T. =The value was detected during the use of the BASE variable. ;Invalid line number record found in virtual symbol table. =Anomaly in symbol information in Virtual Symbol Table file. @Invalid type information record found in virtual symbol table. Invalid symbol record type. ;Attempt to reference non-existent type definition record. :Attempt to seek beyond end of Virtual Symbol Table file. *Unknown size of integer in EVAL command. Fatal Memory Manager Error. Fatal Memory Manager Error. Fatal Memory Manager Error. Fatal Memory Manager Error. Fatal Memory Manager Error. 3Attempt to seek past end of debugger memory file. 3Attempt to read past end of debugger memory file. Fatal System Error. Bad minor number. &Attempt to execute bad postfix code. !Anomaly in mode of PUT command. +Anomaly in type of PUT or APPEND command. 'Attempt to access undefined register. Register name too long. Fatal System Error. <An illegal operand type was detected on the runtime stack. Operand size too large. IAn operand whose size is illegally large was detected on runtime stack. *Unsupported reference to a debug object. RAn unsupported debug object was detected during an attempt to access its value. "Unsupported variable assignment. ÁThe attempted assignment operation is invalid. Potential causes: - Assigning a value to a variable whose type is unknown; (Use a memory template command to perform the assignment) %Bad debug object scope encountered. -Error in Help/Error message file directory. Illegal operand. Illegal syntax in CRT file. 7Insufficient memory for Virtual Symbol Table buffers. 2The cause of execution break is unknown to DB86. µExecution was broken in a manner that DB86 cannot determine. It was not via a known breakpoint or a control-c. Most likely caused by placing an interrupt at the given address. $This breakpoint is already active. No program was loaded. :Unknown 86 instruction at specified address during STEP. 5Attempt to restore data where no breakpoint occurs. +Anomaly in active breakpoint information.