Diagnosing "String space corrupt" & "Far heap corrupt" Errors (99079)

SUMMARY

The errors "String space corrupt" and "Far heap corrupt" occur when Basic detects that its memory areas are damaged. Possible causes are:

• incorrectly using the POKE or BLOAD statements
• calling C or assembly language routines or third party libraries that modify Basic's memory incorrectly
• incompatible terminate-and-stay-resident (TSR) programs or device drivers

To help narrow down the point in your program where memory becomes corrupt, you can add certain statements to cause Basic to check memory consistency.

The following functions and statements cause Basic to check its memory:

   FRE(-1)
   FRE(A$)
   FRE("")
   STACK
   REDIM
				

In the interpreter environment, you can place one of these functions in a debug watch expression, causing Visual Basic to invoke the function automatically after every statement.