<http://schema.org/articleBody>
" Dave, Did you get this worked out? Years and years ago, I worked with a customer who was having a similar problem. We fixed it by changing the paging attributes of Windows. There's a piece of the code in the VI client that relies on an old OS/2 module for memory management. That module allocates memory without using the Windows API. When Windows swaps memory pages to make room for, say, another program to be loaded, the pointers to the memory VI client allocated no longer point to valid locations. The old ..."^^<http://www.w3.org/2001/XMLSchema#string>
<http://archive.midrange.com/midrange-l/201408/msg00340.html>