Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!hsdndev!rutgers!gatech!prism!gt3791a
From: gt3791a@prism.gatech.EDU (JOHNSON)
Newsgroups: comp.os.msdos.programmer
Subject: Borland's VROOM & Networks
Summary: Where are the problems?
Message-ID: <29850@hydra.gatech.EDU>
Date: 25 May 91 09:42:38 GMT
Organization: Georgia Institute of Technology
Lines: 23

I've been using Borland C++ for some time now, and recently I have been
working on some memory intensive applications to be run on networks (i.e.
Novell).  In the manuals for C++, there are one or two mentionings of
some sort of incompatibility between networks and the VROOM overlay
manager.  However, there is limited explaination - no more than "Note that
VROOM applications and network file servers do not mix."  (This can be
found in a caption at the beginning of the section on Overlays.)

What is the nature of the conflict?  Can VROOM applications be run on
workstations utilizing local drives instead of network drives (despite
operating in the network's shell)?

My suspicion is that the problem arises out of Borland using some slight-of-
disk writing techniques that are incompatible with network drives.  However,
I suspect there may also be problems with respect to memory management while
operating under a shell.  Nevertheless, I can't afford to crash a system
trying to find out...  Any help and comments would be appreciated.

						M. Johnson

Georgia Institute of Technology, Atlanta Georgia, 30332
uucp:	  ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt3791a
Internet: gt3791a@prism.gatech.edu