Path: utzoo!utgpu!attcan!uunet!tank!mimsy!dftsrv!ames!mailrus!sharkey!cfctech!rphroy!edsews!rel!bob
From: bob@rel.eds.com (Bob Leffler)
Newsgroups: comp.dcom.lans
Subject: Re: WordPerfect net blues
Summary: lan printing
Keywords: control keys, EOF
Message-ID: <1152@rel.eds.com>
Date: 12 Jan 89 12:16:16 GMT
References: <11000005@uxh.cso.uiuc.edu> <1924@cfctech.UUCP>
Distribution: all
Organization: Electronic Data Systems, Troy, MI
Lines: 30

In article <1924@cfctech.UUCP>, norm@cfctech.UUCP (Norm Meluch) writes:
> In article <11000005@uxh.cso.uiuc.edu> fleming@uxh.cso.uiuc.edu writes:
> >	I have a problem with my networks (PC LAN and Token Ring)
> >	being able to properly handle WordPerfect when it prints
> 	Ctrl-Alt-PrtScrn
> 
> 	Any people at AT&T and or MS that can enlighten me/us as to why we
>   need to do this?


The problem is really with the application not the network.  An older technique
used by most vendors, is to keep all files open at all times on a PC to
increase preformance.  This was fine on a single user, single tasking
operating system.

The problem that you find on Lans, that since the file isn't closed, it isn't
released to the print queue.  Your Ctrl-Alt-PrtScrn sequence forces this to
occur.

The easiest way to get this feature in your favorite application, is to
mandate LAN compatability in all your applications.  For obvious reasons,
Microsoft was one of the first vendors to make their product LAN compatable
with most NETBIOS and MSNET compatable LANs.



-- 
Bob Leffler - EDS, GM Truck & Bus Account (313)456-5375
bob@rel.eds.com or {uunet!edsews, rutgers, umix}!rel!bob
Opinions expressed may not be those of my employer.