home *** CD-ROM | disk | FTP | other *** search
- Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
- Path: sparky!uunet!paladin.american.edu!auvm!CUNIXB.CC.COLUMBIA.EDU!PJB3
- Message-ID: <CMM.0.90.4.724180108.pjb3@cunixb.cc.columbia.edu>
- Date: Sat, 12 Dec 92 12:08:28 EST
- Sender: Nota Bene List <NOTABENE@TAUNIVM.BITNET>
- From: "Paul J. Bodin" <pjb3@CUNIXB.CC.COLUMBIA.EDU>
- Subject: Re: overflow files
- Comments: To: Nota Bene List <NOTABENE%TAUNIVM.BITNET@CUVMB.CC.COLUMBIA.EDU>
- Newsgroups: bit.listserv.notabene
- In-Reply-To: Your message of Sat, 12 Dec 92 12:00:13 IST
- Lines: 45
-
- j-p takala writes:
-
- > Tim Moore,
- > after your posting I tried again. Shelling out to DOS from
- > NB4 still does create a file "@NBDTA.TMP" in the directory
- > specified in the line "DR=" in NBCUSTOM.SET, which in my case
- > is a ramdrive. I did not check in on a 'real' disk, so I'm free
- > to speculate that this feature may depend on whether the overflow
- > drive is a fast virtual drive or a slower real thing.
-
- There are methods that a programmer may use to determine which kind of
- drive his program is writing to, but NB doesn't seem use any of these
- as far as I can tell except to check whether the volume used is
- removable (in some cases). I don't think the type of drive involved
- is the determining factor here.
-
- I have done some experimenting with this phenomenon. Michael at NBI
- told me that the new NB creates only one overflow file, no matter how
- many editing windows have overflows. NB does its own housekeeping
- internally to keep track of which part of the overflow file belongs to
- which edit window. I have verified this experimentally. No matter
- how many of my windows have overflows there is only one overflow file.
-
- On my system, I have also noted that NB4 creates an @NBDTA.TMP file on
- the overflow drive when (and only when) it shells to DOS, and that
- this temporary file is created in addition to any overflow file that
- may exist. It is created whether or not an overflow file already
- exists, and regardless of the amount of free memory available inside
- NB. On my system it seems always to be the same size--55232 bytes.
-
- One may speculate, then, that this is a temporary file created by NB
- that helps it keep track of its own configuration, and perhaps free
- some memory. Since my configuration is pretty much the same all the
- time, NB would be saving pretty much the same information all the
- time. If this is the case, then logically something about the
- configuration of NB would determine whether it needed to write the
- @NBDTA.TMP file--perhaps the size and nature of printer drivers loaded
- or some such.
-
- Can anybody suggest another explanation?
-
- ___________________________________________________________________________
- Paul J. Bodin Internet: pjb3@cunixb.cc.columbia.edu
- Union Theological Seminary smail: 435-52nd Street
- (718) 439-3549 Brooklyn, NY 11220
-