Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!gatech!usenet.ins.cwru.edu!usenet!trier
From: trier@usenet.INS.CWRU.Edu (Stephen C. Trier)
Newsgroups: comp.os.msdos.programmer
Subject: Re: Borland's VROOM & Networks
Message-ID: <1991May29.222808.29430@usenet.ins.cwru.edu>
Date: 29 May 91 22:28:08 GMT
References: <675397058.3@sunbrk.FidoNet>
Sender: news@usenet.ins.cwru.edu
Reply-To: trier@po.CWRU.Edu
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 19
Nntp-Posting-Host: usenet.ins.cwru.edu

"Note that VROOMM applications and network file servers do not mix."
Now, that's good documentation, isn't it?

Anyway, if I turn off the flame thrower, I'll give you my guesses:
1) Any kind of swapping will be slow off of a file server.  2) Setting
a VROOMM application (or a Microsoft C overlaid application) execute-
only on a Novell server will render it inoperable.  This means that
file server copy protection will kill any VROOMM application.  3) If
they mean a non-dedicated server, perhaps VROOMM isn't compatible with
the funny disk access techniques such a server has to use.

Does the Borland integrated environment run off of your file server?
It uses VROOMM, so if it works, yours should work, too.

-- 
Stephen Trier                        Work: trier@ins.cwru.edu
Case Western Reserve University      Home: sct@seldon.clv.oh.us
Information Network Services