DP>The most recent one is a constant series of Access Violations (as reported by
DP>Turbo Debugger GX) in the strangest places. For instance:

This may not translate to your situation, but I have an assembly
language program I wrote a while back that worked beautifully under v2.0
and v2.1 but gave me access violations under WARP.  It took me days to
figure out that I had apparently given a second thread a marginally
sized stack that was sufficient for earlier versions, but had a stack
overrun under WARP.  When I increased the size of the stack
sufficiently, the problems went away.
___
 * MR/2 2.0 #99 * Internet: bob.liles{at}tpl-bbs.com   RIME: ->7

--- QScan v1.131b / 01-0169