Internal Error #773,

  (#112934) User indicated that the error would occur with a bunch of junk
  on the screen -- which indicated to him that it may be some sort of "memory
  trashed" error.  The only reports of this error are very sketchy.  This same
  user later indicated that the program involves a large chunk of Microsoft
  C 5.1 code called from Clipper 5.0.

  (#112958) One user said that after getting an internal error 416, and
  executing the program with //info, he got 773.

  (#116899) BJ Walsh [71121,3013] found that this error was caused by his   ~
  attempts to free pointers from C that didn't belong to his program.