MEMORY PROBLEM

[ANDREW GLASS]

 Barbara:

 Let me butt in here:

 I strongly doubt your problem is with XyWrite per se. You can quit Xy and
 reload until the cows come home without effecting the memory threshold.

 It's much more likely that with each quit sequence users are reloading a TSR
 that is perhaps associated with your network driver. You could check for
 this by running any number of [free] ram-map utilities which are designed
 to show you the current usage condition of your memory. Should you find a
 given TSR produces an incremental sequence, you will have found the culprit.

 You might also see what happens when you shell to DOS. Is the memory stable
 or does it also decrease? Usually, if you inadvertantly create DOS memory
 "holes," XyWrite will have trouble reading overlays and crash.

 - Andy