Xref: utzoo comp.windows.ms:11763 comp.sys.novell:1252 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!ub!dakwala From: dakwala@acsu.buffalo.edu (Nikhil Dakwala) Newsgroups: comp.windows.ms,comp.sys.novell Subject: Re: Windows on diskless workstations Message-ID: <72261@eerie.acsu.Buffalo.EDU> Date: 22 Apr 91 12:09:38 GMT References: <8621@crash.cts.com> <1991Apr17.130557.14349@hubcap.clemson.edu> <1991Apr18.015949.26790@npd.Novell.COM> <1991Apr20.034704.28236@netcom.COM> <1991Apr21.164528.12434@pbs.org> Sender: news@acsu.Buffalo.EDU Followup-To: comp.windows.ms Organization: State University of New York at Buffalo/Comp Sci Lines: 37 Nntp-Posting-Host: sybil.cs.buffalo.edu In article <1991Apr21.164528.12434@pbs.org> rfutscher@pbs.org writes: > > >> >>Only catch is this. You can't tell Windows not to use a swap file. And if it >>comes down to using a network workstation's resources for swapping, this is >>the preferred order..... 1) Local Hard Drive.. 2) Local RAM Drive.. ........ > > >"If you are useing a Novell network, do not set the temporary swap file >to a net drive. Unlike other network vendors, Novell does not license >Microsoft"s MSNet Redirector module. Because Novell is not MSNet >Redictor compatible, thr root directory of a Novell network drive >is also the root directory of the server. What this means is that >if more than one user tries to run windows in 386 enhanced mode >with their temporary swap file set to the same Novell drive, their >systems will hang because the swap files will try to be the same >name on the root directory of the server." > >Robert Futscher rfutscher@pbs.org Besides that, using a network drive to store the temporary swap files, can easily create storage problems during run-time, because these files occupy lots of space.. These files are deleted too, but then they won't be deleted long enough for the file server to purge them automatically to create more space, this might eventually crash the network. Nikhil Dakwala