Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!unmvax!deimos.cis.ksu.edu!rutgers!njin!limonce From: limonce@pilot.njin.net (Tom Limoncelli) Newsgroups: comp.sys.amiga Subject: 1.4 suggestion (FileForbid) (was: Re: A BIG apology and, hopef...) Message-ID: Date: 10 May 89 23:37:54 GMT References: <14870@louie.udel.EDU> <17069@usc.edu> <18129@cup.portal.com> <15007@louie.udel.EDU> Distribution: na Organization: NJ InterCampus Network, New Brunswick, N.J. Lines: 17 How about at least serializing LoadSeg? I mean, just don't permit two to happen at the same time on the same volume. The net has had a number of screwy suggestions for stopping disk thrashing (not so much FilePermit(), but others) I always thought this would be a little simpler. Basically, LoadSeg could check and if someone else is LoadSeg'ing on a volume, wait it's turn. It wouldn't be the end of thrashing, but it would reduce it in a number of places. Once I got my hard drive I found myself starting up many applications at the same time for some reason and often I see a lot of thrashing due to that. Tom -- Tom Limoncelli -- tlimonce@drunivac.Bitnet -- limonce@pilot.njin.net Drew University -- Box 1060, Madison, NJ -- 201-408-5389 Standard Disclaimer: I am not the mouth-piece of Drew University