Path: utzoo!attcan!uunet!mcvax!ukc!warwick!bsrdp
From: bsrdp@warwick.ac.uk (Hylton Boothroyd)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: UNCLE causes my PRINT.COM spooler to hang up
Summary: Might be TSR-like nature of PRINT.COM
Keywords: UNCLE
Message-ID: <1249@sol.warwick.ac.uk>
Date: 4 Jan 89 14:35:45 GMT
References: <945@lzfmd.att.com> <12785@bellcore.bellcore.com>
Organization: Warwick Business School
Lines: 25

In article <12785@bellcore.bellcore.com> thf@wind.UUCP (Theodore
Feyler) writes:
>In article <945@lzfmd.att.com> fgg@lzfmd.att.com (F.G.GECK) writes:
> >I tried using UNCLE and it seems to work ok but I discoverred
> >that if UNCLE is invoked then the PRINT.COM (spooler) command
> >does not work.
> >Has anyone seen this problem or know what is happening here?
>I have been using UNCLE religously and have not experienced any problems
>with print.com.

I don't use UNCLE, but 18 months ago I discovered that some standard
MSDOS 3.20 calls are (or behave like) TSR's,  and can therefore leave
holes in the memory allocation under some conditions - most
particularly if first called during a nested application.  The
hang/crash is not always immediate - it is more likely to wait until
you finish one application and start another.

Since then I've always included

        print /d:PRN/b:4096>nul

in my AUTOEXEC.BAT file to ensure PRINT.COM is loaded and used.  I seem
to remember APPEND.COM is another such offender.

---