Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!warwick!bsrdp
From: bsrdp@warwick.ac.uk (Hylton Boothroyd)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: documentation printing
Message-ID: <_DS{Y#~@warwick.ac.uk>
Date: 13 Jun 91 21:23:52 GMT
Sender: bsrdp@warwick.uucp (Hylton Boothroyd)
Organization: Warwick Business School
Lines: 19
Nntp-Posting-Host: clover

> > > Is there a good reason for using copy-to-prn rather than 'print'?
> >
> > Print invokes a resident program which will stay in memory thus
> > reserving some of it (unless you use mark-release).
>
> DOS PRINT does more than eats up memory. PRINT allows background
> spooling and printing.

So to make sure I don't make holes in memory, I include
        print /d:PRN /b:16384 > nul
in my AUTOEXEC.BAT, then it is there.  It took me years to discover that
some of my machine crashes were caused by using PRINT after I had pushed
above an application!
---
-- 
Hylton Boothroyd        h.boothroyd@cu.warwick.uk.ac
Warwick Business School Janet: h.boothroyd@uk.ac.warwick.cu
University of Warwick   Darpa: h.boothroyd%cu.warwick.ac.uk@relay-nsfnet.ac.uk
COVENTRY, CV4 7AL       Uucp:  h.boothroyd@warwick.uucp