% 4 n è ° o ï DV▓╚!2DUf}ò╝┘÷╢╤éö╔π├Φ║╠~Éσ ç¢┬╫¥┐ç¥ ª╛/ P ┌ ≡ ` | + B ═ Σ j â H!f!╬!≡!\"u"Θ"#$1$╛$ß$$%5%î%ú%0&P&╞&╪&g'Ç'(%())|)£) * *+ +t+è+▐+²+ü,ÿ,---╩-α-R.j.Ω.ⁿ.//E/Ñ/╕/═0Γ0B1_1ô2╢223I3Æ3¿3╦3π3*4E4╛4╥45-5ƒ5╗566╟6╒6v7ï7╠7▐7Q8b8╥8Φ8A9W9ï9ƒ9: :;1;ö;⌐;±;< =1= >.>╩>τ>?'?Ñ?╩?;@M@┤@╫@ªA═AB'BoBéB√BCïC⌐C≤C DéDÿDE E E+E+E<E∩EFòFªFGGZG⌡GHHæHIIsIàIJ!J╤JΣJôK«K¬L╗L▌M≡MlOO²PQéQòQ¥R»RΣS÷S TUeVxV┴V╘VX*XpYëY1ZGZk[à[Æ\⌐\ε]^X_m_``ε`a4bFbc+c∩c cFe]e┼eΓeaf~f+gBgöh[0001] System Error. This is an unanticipated system error. Please describe the events leading to this error and the error number in a letter addressed to RJSwantek. Until a fix is sent to you, try a different approach to what causes the error.[002] Could not find input file. The file name you specified to be disassembled or define labels does not exist. You may have misspelled the name or omitted the disk name (ex: a:) or path name (ex: \asm). Also, if the file is not an .EXE or a .COM file, the extension must be specified.[003] First memory boundary >= second. The second memory range, as specified, is less than or equal to the first. (ex: 100 < 10) If the range is right, swap the values.[004] Bad Label. A blank label just will not do. If you just want a comment here, use the F5 function key with the cursor at the right of the screen.[005] Bad second boundary. The boundary specified was a bad hex number (ex: 2as or 3w4), a bad decimal number (ex: fff or 10000000), or greater than fffffh for memory, or 9999 for subroutines.[006] Bad first boundary. The boundary specified was a bad hex number (ex: 3w4 or 2ag), a bad decimal number (ex: fff or 10000000), or greater than fffffh for memory, or 9999 for subroutines.[007] Terminated by Cntl-Break. The previous operation was prematurely stopped because you pressed the Control and Break keys.[008] Bad switch. One of the switches is invalid. Switches may be upper or lower case, with or without spaces in between (ex: /g/c). To get a list of valid flags, refer to the User Guide. Switches in interactive mode are not valid for batch mode. Preface line with '@' sign to enter batch mode (ex: dd @sample).[009] No file to save. You've got to have a file loaded before you can save it or add labels to it with the 'DSM Load' command. Use the 'LOAD' command to load a file.[010] Could not open output file. The output file.ASM or .OSM could not be opened. This is usually due to a bad file name (non-MSDOS). Other possibilities are a full disk, a non-existent disk, or other disk problems. If the disk is full, try deleting unnecessary files. Or try another disk.[011] Label Defined. The label at this address has already been defined. Use the 'DELETE' or 'MODIFY' command to change this label.[012] No Label. There is no label at this address to delete or modify.[013] Invalid Start Address. The program starting address must be specified in the form: SEGMENT:OFFSET. (examples: 600:0, e000:8000.)[014] File not loaded. You're not going to see much until you use the 'LOAD' command to load a file for disassembly.[015] Bad subroutine number. The subroutine number you specified is out of the range of possible subroutines in the program you are disassembling. Check the prompt for a valid range of subroutines (ex: (1-12)).[016] Bad address. The address you specified was either not hexadecimal (ex: 123g) or greater than 0fffffh.[017] Outside program. The subroutine you're searching for falls outside the range of the program you are disassembling. This can happen if you are disassembling a range of memory or the program is calling the BIOS, driver or operating system directly. Refer to the address next to the 'call' statement for this subroutine's address (ex: call s1 ;>>xref<00123><<).[018] Bad string. The string you specified did not follow the format: 'text'/xxxx, where text is specified between single quote marks, and the xxxx's represent an even number of hex characters. Other valid formats are: 'text' and xxxx alone. Also, patches may not be longer than 16 bytes.[019] No matches. There are no matches for this string from here to the bottom of the program you are disassembling. The search starts at the screen you are looking at. To search the whole file, use the mouse or press the 'SHIFT-HOME' keys to position the display at the top of the file.[020] Quicksand memory. The memory range you have chosen to disassemble is constantly changing. This range may be a stack or buffer region. Dis■Doc makes its label and data block calculations when you first load a memory range. These calculations are now worthless. Try printing this listing to disk.[021] System file missing or corrupted. (See dderror subroutine.)[022] INT/AH buffer overflow. The DD program capacity for new interrupt and out/in comments has been reached. Try to eliminate unnecessary lines (ex: an interrupt that doesn't occur in the program being disassembled). [023] Hit Another Boundary. The 'MODIFY' command will not move a data block boundary over its other boundary or over the boundary of another data block. Use the 'REMOVE' command to delete a data block.[024] Bad Comment. Why bother if you're not going to have a comment?[025] User label overflow. The labels generated by this program exceeds the storage capacity of Dis■Doc. If you are loading memory, try a smaller range. If you are loading a huge file, try doing a PARTIAL load using the command in the Load Window.[026] Printing stopped by Cntl-Break. Printing or file creation has been prematurely stopped because you pressed the Control and Break keys. If you were creating a file, it still exists, although the file ends at the point you stopped printing.[027] Bad address. The address you specified was either not hexadecimal (ex: 123g) or out of the range of the program you are disassembling. Check the prompt for the valid range (ex: 100-234d).[028] Bad address. The address you specified was not hexadecimal (ex: 123g) or greater than 0fffffh.[029] Could not write LBL file to disk. The saved label array (with the extension LBL) could not be saved to the disk due to a full disk or disk write errors. [030] Printer error. The printer is not selected or off.[031] Internal error. This error indicates that a portion of the DD program or it's files has been corrupted. Try copying the original files from the master DD disk. Also try changing the way you entered the command.[032] ASM or OSM file write error. Check disk to make sure there's enough room on the output disk & try again. Huge programs generate huge listings. If you just want to see a part of the file, use the 'RANGE' command when printing.[033] Bad tab setting. Tabs may be set from 0 for no tabs to 8 for each tab to represent 8 spaces. This should match the tab setting on your editor.[034] Version Mismatch. The current LBL file does not match this version of Dis■Doc. You must recreate the LBL file for this version.[035] LBL file mismatch. The saved label file (LBL) does not match the program you are disassembling. If the program to be disassembled has been changed, continue with the next prompt. If they should match, press the Escape key for the next prompt, and locate the difficulty. A common cause of this error are programs with the same name but different extensions (ex: ansi.exe and ansi.sys).[036] Bad interrupt or ah number. The interrupt or 'ah' subfunction number specified was either an invalid hex number (ex: 2eg) or greater than hex value 0ff (ex: fff).[037] Bad port number. The port number specified was either an invalid hex number (ex: 23g) or greater than hex value 3ff (ex:400).[038] Patch Outside Program. The address of a patch was not within the boundaries of the program. Check each patch against the program header to insure they are within the program range and try again.[039] Multiple Patches. The address of this patch is the same as a previous patch. If this isn't a mistake, consolidate the two patches into one and try again.[040] Too Many Patches. The number and size of patches entered exceeds the DD program limits. Try to consolidate patches or eliminate unnecessary patches.[041] No block to delete. The address specified as the start of a data block to delete was invalid. No data block starts at that address. Refer to the listing to obtain the valid address of the block you wish to delete.[042] Could Not Open NEW File. The .NEW patched file could not be opened. Make sure there is a disk with enough room and try again.[043] Could Not Write to NEW File. The .NEW patched file could not be written to. Make sure there is a disk with enough room and try again.[044] File Must Be Saved. The LBL file must be saved before you can load a DSM file. Use the 'KEEP' command to save the work to this file.[045] No more data blocks. There are no more data blocks to modify from here to the top/bottom of the program. Modification starts at this screen. To modify from the start of the program, use the 'SHIFT-HOME' keys to position the program at the start. Use the 'SHIFT-END' keys to start at the bottom.[046] Bad Overlay Number. The overlay number you specified was either not a valid decimal number or was greater than the actual number of overlays in this program.[047] No patch to delete or modify. Use the Edit window to list the addresses of all valid patches.[048] No patches. You can't do much with this command until you've created some patches in this file.[049] Bad patch number. The patch number you specified was either not a valid decimal number (ex: 1f) or not within the range specified by the prompt (ex: 1- 6).[050] Could not read input file. While creating the patched file, DD could not read the original program file to patch. Check to insure it's there.[051] DOS Failure. The DOS shell could not be loaded for lack of memory. Try getting out of Dis■Doc and typing EXIT. You may have more than one shell running.[052] Bad Segment Number. The segment value you specified was either not a valid hexadecimal number (ex: 0012s) or was greater than 0ffffh in magnitude.[053] Multiple Segment Definitions. Two segment value and ranges cannot occur at the same address. If you want them to occur at the same address, use the next highest address. (Ex: if a segment range already starts at address 02f4h, use address 02f5h.)[054] Too Many Segments. The number of segments entered exceeds the DD program limit. Try to consolidate segment values.[055] No Defined Segment Ranges. There are no current segment ranges in this program to delete or list. Use the 'ADD' to add a segment range.[056] Not 80386. The 'FS' and 'GS' extra segment registers are for use with programs written for the 80386 instruction set only. Choose another segment register or re-load this program and select 'd' or 'e' when choosing the instruction set to use.[057] No Segment There. There was no segment definition at the address you specified, try another address.[058] No More Patches. There are no more patches in this file. 'SHIFT-HOME' the screen and start again.[059] Use EXE UNPACKER Utility. The disassembly of this packed file will be much more accurate if it is first unpacked using the EXE UNPACKER by RJSwantek, Inc.[060] Bad Segment Name. We're looking here for one of the following names: ES, CS, SS, DS, GS, or FS. Pick one of these names and try again.[061] Incompatible Selection. The area of the screen selected can not be processed by the selected function key, as in the case of trying to convert a header region into data or code.[062] Label Redefined. The label chosen matches a previous label. To allow correct assembly of the final listing, pick another label.[063] DSM Syntax Errors. Syntax errors have occurred in the DSM file. Correct the errors and try again. (The original label file has been re-loaded.)[064] INT 3 Fixed. The definition for interrupt 3 is fixed. Sorry.[065] Bad Port Number. The port number on this line cannot be read. Use the command windows to change this comment.[066] Syntax Error. Colons (':') and semi-colons (;) are not allowed in labels or comments. 'Main' is a reserved label. Labels cannot be broken by a space (eg. 'lab el'). Labels cannot have non-alphanumeric characters other than @, ?, _, and $. Labels cannot begin with a decimal number (0-9).[067] Could Not Save. An error occurred while saving your initial conditions. Check for disk space, bad disk, etc.[068] Bad Partial Parameters. One of the parameters was an illegal hex number, or, when taken together, the parameters exceeded the range of the file to be disassembled. The "Start_file_byte_offset" plus "number_of_bytes" should not exceed the file size. Also the start program address plus number of bytes should not exceed 16#fffff.[069] Warning--Effective Next Load. This is just a friendly reminder that this option just not take effect until the next complete load of a file or memory.[070] Bad Search Label. The cursor is either not on a valid label to GOTO or cross reference.[071] No More Returns. The GOTO return stack is empty.[072] Invalid Data Type. The data type specified was not one of these: DB, DW, DD, ASC, DUP.[073] Bad Segment Location. Segments can only occur between processes. If you want a segment at this address, create a process label here first. [074] Already There. The address you want to GOTO is currently on the screen.[075] CS Segment Value Too Big. The CS segment value times 16 should not exceed the program address it's going to. (CS*10h < program address.)[076] More Than One Address. Segment/Offset/Constant formatting can only be done one at a time. [077] Data Type Too Big. The data type you attempted to put here will not fit before the next label. (EX: Putting a DD data type at address 205h will not fit if there's a label at address 206h.)[078] No More. From here to the top or bottom of the listing, there is no more cross reference to this address, 16 bit words used in a command or questionable source lines.[079] No More UNDO's. There are no more addresses on the stack which may be undone.[080] Parse Error. The definition command line either did not have enough arguments or the arguments were not separated be commas.[081] Bad String. The specified string was either too long for this argument or was not enclosed by single quotes ('comment').[082] Bad DSM Command. The DSM command was not one of the following: PRO, INI, DAT, COD, COM, LAB, SEG, DEC.[083] Bad Output Name. The name specified in the /F switch was illegal.[084] Bad Data Type. This argument should be one of the following: DB, DW, DD, DS, with an optional ,DUP at the end of the line.[085] Bad Patch. The specified patch was not in the proper format of 'text'/000000, where the text or hex values are optional. Or the patch was longer than the maximum of 24 bytes long. Or if a patch byte is to be a single quote mark, it was not specified as ''.[086] DSM File Read Error. DS had difficulty reading the DSM file. Try copying the DSM file to another disk and try again.[087] Bad Label Type. This argument should be one of the following: JUMP, DATA, PROC, SEG.[088] Bad Comment Definition. The command argument should be one of the following: INTR, PORT, FULL, or HALF. If interrupt, the first two arguments should be the interrupt number followed by the function. Both should be below 255. If port, the first argument should be 0-3ffh.[089] Bad Offset Declaration Definition. The command argument should be one of the following: CONST, OFFSET, or SEGMENT. If OFFSET, it should be followed by the segment register to pair the offset with: ES, DS, CS, SS, or NX to use the next 16 bit word.[090] Bad Initialization Argument(s). The INITIALIZE command should be followed by an equal sign (=) and then one or all of the following separated by commas: L&C, D&C, DEC, SEG, and/or PAT.[091] Two Boundries Required. Two boundries are required for this switch.[092] No Default. When using the /R switch for disassembling memory, no deafault values are allowed. Each boundry must be specified in full.[093] First Boundry > Second Boundry. The first boundry should be less than the second boundry. If the boundries are correct, just swap the values.[094] No Filename. A file name was missing from the batch mode command line. (What are we going to disassemble today?)[095] Warning--EXE within COM file. This COM file unpacks into an EXE file. For a clearer disassembly, use the UNPACK utility on the Master Diskette to convert this file into it's EXE equivalent. OR-- continue to get a COM/EXE file format.[096] Can't delete 1st seg declaration. The first segment declaration can be renamed but not deleted.[097] Non-color Terminal. This function is for color terminals only, such as CGA, EGA and VGA.[098] Non-hex Byte. This byte was either non-hex or greater than 0ffh. An example of a color byte entry would be '70' for black-on-white.[099] Foreground = Background. The color byte you entered would result in a non-readable display. Example: '11' would result in blue on blue.[100] Could Not Open LBL File. DD could not find the named LBL file. DD will create one from scratch.[101] Illegal Operand. The selected operand could not be converted to a LABEL[INDEX] operand (ex: d01234 cannot be converted to d01234[di]).[102] Illegal Operand. The selected operand could not be converted to a [INDEX+CONSTANT] operand (ex: d01234 cannot be converted to [di+12].[103] Unused.[104] Unused.<1> Load Window. This window loads and disassembles a file or memory. All automatic labeling and separation of code and data occurs here. A definition file may also be loaded with this window.<2> Format Window. This window formats the disassembled listing into a variety of formats including: all upper case, program outline, no retf/n opcodes, and more.<3> Edit Window. This window allows you to edit code and data blocks, labels, segment definitions. Direct screen editing can be accomplished with function key group F1 to F5.<4> Search Window. This window allows you to search the disassembled listing for strings, subroutines, addresses, and more. You may also use function keys F7 through F10.<5> Output Window. This window creates source files or printer listings of the disassembled program. You may also use function key F6.<6> Patch Window. This window patches disassembled programs. First the listing is patched. Then a final patched program is output.<7> DOS Command. This command brings up a DOS shell to do file commands. Type 'EXIT' to return to Dis■Doc.<8> Keep Command. This command saves the labels created by loading a file or memory, making future reference to that file or memory much faster to load.<9> Quit Command. This command ends Dis■Doc. If changes have been made to the currently loaded file or memory and they have not been saved, Dis■Doc gives you the opportunity to save it here.<10> Group F1-F10. The function keys F1 to F10 provide a faster access to some command windows and allow listing text to be directly selected. Press F1 to get more help on each function key.<11> Disk or Memory Choice. 'COMPLETE' will load files from the hard disk or floppies. 'PARTIAL' will load parts of files when the file is too large. 'RANGE' will load a range of RAM memory. 'BIOS' will load this system's BIOS. 'DSM' will load a DSM file of label definitions.<12> Edit Window. Add, modify or delete program labels and/or comments. Add a data block over a code block or vice versa. Also press F1 for a more interactive labeling method. REPROCESS will reprocess all labels after a section of data is converted to code (example: jmp 9034 is converted to jmp m02315).<13> Format Window. You have a choice of listing formats. 'EVERYTHING' will display everything. 'CODE' or 'DATA' for just those. 'OUTLINE' shows subroutines, interrupts, and ports commands. 'KILL RETN/F' will toggle the RETF/N opcodes to RET. 'BYTES' will display code bytes in lieu of comments. 'ADDRESSES' provide three addressing modes. 'PROCESSOR' will increment the current processor up one.<14> Search Window. 'TEXT' finds a string within the listing. 'BINARY' moves the listing to a binary string in the program image. 'CODE BOUNDARY' finds the next code/data boundary and gives you the ability to change that boundary in byte increments. 'ORIGIN' finds the start of program execution. 'WORD' finds the next 16 bit word used in an opcode. 'QUESTIONS' helps locate possible trouble areas.<15> Next Window. Use 'NEXT' to find the next occurrence of this string. Use PG UP/ PG DN keys to scroll the disassembled listing.<16> Output Window. 'COMPLETE' creates a full .ASM file of this program (or press F6 with no selection). 'PARTIAL' outputs a range of file (or select something with the function keys and press F6). 'EVERYTHING' and 'RANGE' are the same except they produce listings on the printer.<17> Block Window. 'NEXT'/'PREVIOUS' will locate the next/previous code/data boundary. 'UP' will move this boundary up one byte and display the result for fine-tuning this boundary. 'DOWN' will move this boundary down one byte. 'REMOVE' will delete this data block. 'XRESTORE' will restore the previously removed data block.<18> Patch Window. 'ADD' adds a patch to this program. 'DELETE' takes it away. 'MODIFY' allows you to change the patch or its location. 'FIND' positions the display over the patch to find. 'LIST' lists all the patches in this program. 'PROGRAM' creates a new patched program file.<19> Processor Window. Choose the processor for which the program to be disassembled has been written. If it's a MS-DOS program, choose 'a'. If you are dumping the BIOS from an IBM AT, choose 'b'. If you are dumping the BIOS from a 386 machine, choose 'c'. If unsure, select 'a', then use the 'PR' command to increment the legal processor instruction set.<20> Option Window. The settings for the starting program segment and color are set here.<21> Option Window. 'PROGRAM SEG' will determine where Dis■Doc starts the next program it disassembles. Keep this at the same value to get consistent labels. 'NORMAL' sets the color of the majority of screens. 'LISTING' sets the color of display listings and 00% windows. 'ERROR' and 'HELP' sets the colors for these types of messages.<22> Edit Label Window. 'JUMP/DATA' will create a label in column 1. 'PROCESS' will create a 'PROC/ENDP' label set. 'SEGMENT' will start a new segment definition. 'FULL' will create a full line comment. 'VALUE' allows you to tell Dis■Doc what the value of the various segment registers (DS, ES,...) are so that labels will be addressed correctly.<23> Edit Comment Window. 'INTR/PORT' will cause the new comment to appear with every occurrence of this interrupt or port. 'PARTIAL' will create a comment just for this line of the listing.<24> Edit Data Window. 'LABEL' will create a data label. 'BYTE' thru 'ASC II' will change the format of the selected data. 'SEG/OFF' will toggle the selected word from constant to segment declaration to offset. 'REPEAT' will cause Dis■Doc to try to display the bytes following the selected byte in 'dup' format.<25> Edit Constant Window. Change this value to a constant, OFFSET label, or SEG label. If converting to a SEG or OFFSET, Dis■Doc will create a label if it does not already exist [OFFSET label = DS seg [in code] or CS seg [in data] * 10h + constant value]. [SEG label = constant value * 10h].<26> Moving the Cursor. In addition to the arrow keys, the cursor can also be moved with the TAB key (thru four columns), SHIFT-TAB keys (backwards TAB), HOME key (to the top of the window), CNTL-HOME (top of listing), CNTL-LEFT ARROW (left of window), CNTL-RIGHT ARROW (right of window), END (end of window), and CNTL-END keys (end of listing).<27> Using the Mouse. The mouse can be used to select commands (by putting the mouse cursor on the command and pressing the left button), scroll the screen (by putting the mouse cursor on the left side of the window and pressing the left or right button) or move the keyboard cursor (by moving the mouse cursor within the window and pressing the left button).<28> Cross Reference. Use 'Previous' or 'Next' to find the previous or next cross reference to this address. Use PG UP/ PG DN keys to scroll the disassembled listing.<29> Offset in Code. An offset label address is calculated based on: SEGMENT*16 + OFFSET. The OFFSET is the word constant here. The SEGMENT used is specified through this window. DS will use the current DS value, CS the CS value, etc.<30> Offset in Data. An offset label address is calculated based on: SEGMENT*16 + OFFSET. The OFFSET is the word constant here. The SEGMENT used is specified through this window. DS will use the current DS value, CS the CS value, etc. 'NEXT' will use the word constant following the offset constant, as in a FAR jump table.<31> Word in Code. Use 'Previous' or 'Next' to find the previous or next 16 bit word in code, to insure that all OFFSET and SEGMENT declarations have been made. Use PG UP/ PG DN keys to scroll the disassembled listing.<32> Label in Wrong Block. The highlighted line contains either a data label within a code block or code label in data block. Use 'Invert' to invert the line to check if this should really be a data line or a code line.<33> LEA Opcode. The LEA opcode is unique in that the assembler can use a segment override when calculating the offset, but that override does not appear in the binary image. Use '-segment-' to override the default of DS. The Absolute command allow you to convert d00012[di] to [di+12]. The Relative command restores the d00012[di] operand.<34> LEA Opcode Search. LEA opcodes are the runtime version of 'mov ax,offset label'. Here you can set the segment override.<35> 16 Bit Indexed Operands. Indexed 16 bit operands can be displayed as d00012[di] or [di+12]. Selecting the Absolute command performs this conversion.<36> 16 Bit Indexed Operands. Indexed 16 bit operands can be displayed as d00012[di] or [di+12]. Selecting the Absolute command performs this conversion. Selecting Relative converts the operand back.<37> Questionable Line. This Search mode looks for questionable source lines, such as: illegal opcodes ("???"), code labels (m,s,b,c,o prefixes) in a data block, data labels (d,k prefixes) in code blocks, and code labels within a code line (s123 EQU $+1//jmp m01234). The last two questionable source lines however are perfectly legal in self-modifying code.
