Answering msg from David Roper to All,
on Friday March 22 1996 at 12:04
 DR> Maybe someone will know the answer to this:  I use PB32 on C: drive at
 DR> home and C: drive at work.  Compile times for a 200k source code are
 DR> 15 seconds and 130 seconds... on the two machines.  The 15 seconds is
 DR> on a 486/25 CPU and the 130 seconds at work is on a Pentium 90.  Go
 DR> figure, I said to myself. Doing some sleuthing, I find if I don't
 DR> attach my Netware 3.12 using VLM's, CAPTURE, etc., then my compile
 DR> time is a blistering 13 seconds on my Pentium 90.  Is there some way
 DR> to tell PB32 NOT to look at the fact that I am "ON" the network so
 DR> that I can get the 13 second compile times without having to re-boot
 DR> or/and do a "dual boot" thingy?  Dave N, Bob Z, any hidden switches?
Hello David,
This is only a guess and could be entirely wrong, but it's possible that PB 
uses temporary files, perhaps in the directory in your "TEMP=" environment 
variable.
When you're logged onto the network type "SET" and see if TEMP= is present, 
and if so, is it pointing to a network drive?
When you're not connected to the network, where does TEMP= (if it's there) 
point to?
Try pointing TEMP= to a local drive when logged onto the network.
FWIW the compiler that I wrote uses temporary files, and it runs like a *dog* 
over a Novell network, at least 3-4 times slower. This may very well be the 
same sort of problem.
Cheers.
---
---------------