Dos Error 5313
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 to visit from the selection below. Results 1 to 9 of 9 Thread: Problem face Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 04-28-06,02:00 #1 prosiyam View Profile View Forum Posts Registered User Join Date Apr 2006 Posts 6 Unanswered: Problem face Dear All Dbforums members, I am new members of this forum. I want to place here two problems. I am used a shipping software which developed by CA-Clipper language and this software running under Novellnetware v-6. Our all workstations is running under Windows XP with SP2 By using this software when we add or update some datas, its randomly quited from the programme and and shows below two error messages. 1. "Unrecoverable error 5313: Out of space for VM swap file" 2. "Unrecoverable error 416: Read error on overlay file" Somebody could help me what does it mean the above two error and how could we solve this error message by ourselvs. Awaiting the wonderful reply from someone, who basically well known the clipper languages. Thanks in advance for nice co-operation in this regards. Sharif Reply With Quote 04-28-06,04:03 #2 healdem View Profile View Forum Posts Jaded Developer Join Date Nov 2004 Location out on a limb Posts 13,692 Provided Answers: 59 Hi Prosiyam, and welcome to the forum I moved your thread to the section that will be more appropriate for Clipper questions I'd rather be riding on the Tiger 800 or the Norton Reply With Quote 04-28-06,08:49 #3 Pat Phelan View Profile View Forum Posts Visit Homepage Resident Curmudgeon Join Date Feb 2004 Location In front of the computer Posts 15,579 Provided Answers: 54 It has been years since I've used Clipper, but these are problems that I remember! The first error you've mentioned, "Unrecoverable error 5313: Out of space for VM swap file" is caused by not enough disk space wherever the workstation's temp files are stored. Be sure that a TEMP environment variable is set, and that the drive that it points to has at least a few megabytes of free space. If you are running from Windows 2000 or
to corruption of the VM (Virtual Memory) system by bad memory chips or conflicting software drivers. The error message could be interpreted as "the table (index) that manages blocks of virtual memory has gone bad". Investigations are ongoing. Action: Try using: SET CLIPPER=//BADCACHE 5211 SWAPFILE creation error The virtual memory (VM) subsystem is unable to create a swap file on disk. See Also: Error 5311, "The Runtime Environment" chapter of the Programming and Utilities Guide. 5302 Conventional memory exhausted This is an "out of memory" message that indicates that the CA-Clipper application no longer has sufficient conventional memory (below http://www.dbforums.com/showthread.php?1216122-Problem-face 640K) available to continue. Specifically, this error occurs when the virtual memory system attempts and fails to bring a VM segment into conventional memory that had been swapped out to disk or expanded memory. Action: Make more conventional memory available to the VM system. This can be done in several ways: 1) Increase the amount of conventional memory available before running the application -- remove TSRs, make use of 386 http://www.ghservices.com/gregh/clipper/ie52f.htm memory manager, etc. 2) Use a third-party linker that can dynamically overlay C and assembly-language code. C and ASM are not automatically overlaid by RTlink and therefore sit in conventional memory throughout the execution of the application. 3) Ensure that any C or ASM code in use is making use of the virtual memory system if it is doing dynamic memory allocation. Any memory allocated using the Fixed Memory Allocator functions _xalloc() and _xgrab() reduces the amount of conventional memory available if it is not immediately freed. See Also: "VM API" chapter of the Technical Reference Guide. 5304 Conventional Memory Exhausted This is an "out of memory" message that indicates that the CA-Clipper application no longer has sufficient conventional memory available to continue. Specifically, this error occurs when a function attempts to allocate conventional memory and fails. This error can be received as a result of the failure of _xgrab() in Extend System functions. Action: See action for 5302. 5305 VM Swap Space Exhausted There is insufficient room in the VM swap area in real memory to load virtualized data. This only occurs in the undocumented internal function _vmTwo(). The CA-Clipper runtime issues calls to the _vmTwo() function when it must obtain two de-referenced virtual memo
VM memory [5108] too many spawned programs [5110] VM loader error [5111] VM disk error Startup and Runtime Messages [5004] can't allocate special seg [5005] can't allocate VM info [5010] memory free http://www.itlnet.net/programming/program/Reference/c53g02c/ngf499.html [5011] execute prog failure [5251] insufficient memory [5253] can't allocate VM tables [5254] insufficient DOS memory [5255] VM memory allocation error [5257] can't create swap file: