Dos Error Code 2000
Contents |
Links and Website Archived Old Forum Files Links for VC and MASM 128553 Posts in 15254 Topics by 684 Members Latest Member: mottt The MASM Forum Archive 2004 to 2012 Miscellaneous Forums 16 bit DOS Programming "Error 2000: Stack Overflow" running dos error code 9009 DOS application on Windows XP « previous next » Pages: [1] Author Topic: "Error 2000: Stack
Dos Error Code 128
Overflow" running DOS application on Windows XP (Read 7630 times) brookebree Guest "Error 2000: Stack Overflow" running DOS application on Windows XP « on: June dos error code 255 19, 2010, 11:04:44 PM » I"ve used Microsoft masm v6.11 assembler, link v5.60 linker, mapsym v4.0 symbol file generator, and symdeb v4.0 debugger for years on my XP Professional, Service pack-3 computer to write and maintain several 16-bit assembly programs in dos error code 1 the XP DOS command lineenvironment. Recently, a problem started when I install various new windows applications (Itunes, Java updates, Roxio Disk software, etc.) I start getting the error 'Error 2000: Stack overflow' when I run the mapsym.exe program to create the .sym file I use with symdeb to debug my assembly applications.So my masm, link, mapsym and symdeb are the exact same versions I've run for years, nothing has been changed, I've been able to run maysym for years also with no problem
Dos Error Codes List
(Win 95, 98, XP), but my current problem is basically that after I install just about any new windows XP application, mapsym will stop working and report this same error, but I uninstall the application and mapsym will start working again and doesn't display the error. I've tried running mapsym on a couple other XP computers and found out it gets the same stack error on them so it seems to only work on my XP computer (maybe the only one in the world???), and only if I don't install any new windows software (or most windows software, I am able to load some applications with no Ill effects like fileZilla, Bugzilla, Skype, Digital Picture Professional).Codeview is not an option for debug since I run processes that spawn child processes several layers deep which codeview has issues with, I actually used to use codeview years ago for but this and other reasons I switched to symdeb for my debug use as it it much more robust for my app's that use multiple code/data segments & calls to 'c' code. I could use the 'debug' program that comes with the XP OS but can't see public'd code and memory location labels so that is not an option. I've read on the internet about this error being displayed for other DOS programs and I understand it has something to do with the stack in my mapsym program being too small. I also read about an old microsoft program
File not found 03 Path not found 04 Too many open files (no handles left) 05 Access dos error 5 denied 06 Invalid handle 07 Memory control blocks destroyed 08 Insufficient memory dos error 64 09 Invalid memory block address 0A Invalid environment 0B Invalid format 0C Invalid access mode (open mode
Dos Error 4
is invalid) 0D Invalid data 0E Reserved 0F Invalid drive specified 10 Attempt to remove current directory 11 Not same device 12 No more files 13 Attempt to write on http://www.masmforum.com/board/index.php?PHPSESSID=786dd40408172108b65a5a36b09c88c0&topic=14251.0 a write-protected diskette 14 Unknown unit 15 Drive not ready 16 Unknown command 17 CRC error 18 Bad request structure length 19 Seek error 1A Unknown media type 1B Sector not found 1C Printer out of paper 1D Write fault 1E Read fault 1F General failure 20 Sharing violation 21 Lock violation 22 Invalid disk change 23 FCB unavailable http://stanislavs.org/helppc/dos_error_codes.html 24 Sharing buffer overflow 25 Reserved 26 Unable to complete file operation (DOS 4.x) 27-31 Reserved 32 Network request not supported 33 Remote computer not listening 34 Duplicate name on network 35 Network name not found 36 Network busy 37 Network device no longer exists 38 NetBIOS command limit exceeded 39 Network adapter error 3A Incorrect network response 3B Unexpected network error 3C Incompatible remote adapter 3D Print queue full 3E No space for print file 3F Print file deleted 40 Network name deleted 41 Access denied 42 Network device type incorrect 43 Network name not found 44 Network name limit exceeded 45 NetBIOS session limit exceeded 46 Temporarily paused 47 Network request not accepted 48 Print or disk redirection is paused 49-4F Reserved 50 File already exists 51 Reserved 52 Cannot make directory entry 53 Fail on INT 24 54 Too many redirections 55 Duplicate redirection 56 Invalid password 57 Invalid parameter 58 Network device fault 59 Function not supported by network (DOS 4.x) 5A Required system component not installed (DOS 4.x) DOS Err
your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want http://discussions.virtualdr.com/showthread.php?68547-DOS-error-message-list to visit from the selection below. Results 1 to 12 of 12 Thread: DOS error http://www.symantec.com/connect/articles/windows-system-error-codes-exit-codes-description message list Tweet Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode January 13th, 2000,02:20 PM #1 Webwalker View Profile View Forum Posts Visit Homepage Virtual Med Student Join Date Jan 2000 Location sacramento, ca, usa Posts 5 DOS error message list Does anyone dos error know where I can find (electronically) a list of the various DOS errors and runtime errors and what they mean? Reply With Quote January 13th, 2000,02:48 PM #2 DoubleDutch View Profile View Forum Posts Virtual Intern Join Date Dec 1999 Location Netherlands Posts 124 I use oftenhttp:// Français Deutsch 日本語 Español Help Video Screencast Help Windows System Error Codes (exit codes) Description Created: 28 Jan 2009 • Updated: 20 Dec 2010 | 9 comments Language TranslationsMachine TranslationsDeutsch Français Español 简体中文 日本語 Sidd +19 19 Votes Login to vote Tweet Application installation (legacy setup applications or Windows installer applications) sometimes fails without any error message. These tasks will return exit/error codes when log file is generated. The following script will help in getting the Exit/Error code of Application installation else on can get it from log file. Dim oShell, MyApp, i Set oShell = CreateObject("WScript.Shell") MyApp = """C:\MyApplication\Setup.exe"" /Q" i = 0 i = oShell.Run(MyApp, 1 ,True) WScript.Echo "Exit Code is: " & (i) Set oShell = Nothing Note: Use Silent switches according to the application. The table below describes system Exit/Error codes when a task is executed. The description of codes may help in identifying and troublshooting the issues. Code Description 0 The operation completed successfully. 1 Incorrect function. 2 The system cannot find the file specified. 3 The system cannot find the path specified. 4 The system cannot open the file. 5 Access is denied. 6 The handle is invalid. 7 The storage control blocks were destroyed. 8 Not enough storage is available to process this command. 9 The storage control block address is invalid. 10 The environment is incorrect. 11 An attempt was made to load a program with an incorrect format. 12 The access code is invalid. 13 The data is invalid. 14 Not enough storage is available to complete this operation. 15 The system cannot find the drive specified. 16 The directory cannot be removed. 17 The system cannot move the file to a different disk drive. 18 There are no more files. 19 The media is write protected. 20 The system cannot find the device specified. 21 The device is not ready. 22 The device does not recognize the command. 23 Data error (cyclic redundancy check). 24 The program issued a command but the command length is incorrect. 25 The drive cannot locate a specific area or track on the disk. 26 The specified disk or diskette cannot be accessed. 27 The drive cannot find the sector requested. 28 The printer is out of paper. 29 The system cannot write to the specified device