Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!mit-eddie!uw-beaver!Teknowledge.COM!plim
From: plim@Teknowledge.COM (Pean Lim)
Newsgroups: comp.windows.ms
Subject: Re: APPLETLK.DLL in Windows 2.11
Message-ID: <2084@alfred.Teknowledge.COM>
Date: 14 Feb 90 18:58:43 GMT
References: <2016@alfred.Teknowledge.COM> <23578@siemens.siemens.com>
Organization: CIMFLEX Teknowledge Inc., Palo Alto CA
Lines: 26
In-reply-to: jrv@demon.siemens.com's message of 13 Feb 90 14:42:42 GMT

In article <23578@siemens.siemens.com> jrv@demon.siemens.com (James R Vallino) writes:

>   I run Windows/286 on my machine with a TOPS "AppleTalk compatible" card and
>   the TOPS network software.  With the netprint software resident you do not
>   need to print to a file.  I setup the Postscript printer to be connected to
>   LPT1:  in the control panel.  The TOPS resident program traps the calls to
>   the printer interrupt (INT 17) and routes the output over the
>   network.  This works not only for Windows but for any program
>   which generates Postscript output and does not write directly to
>   the printer hardware port.

Like James, we use TOPS NetPrint (ours is ver 2.00) to print directly
from Windows apps.  While this setup works, it (i) requires purchase
of third-party memory resident software (NetPrint), and (ii) is
flakey--ocassionally Windows seizes up while printing.

There may be a newer version of NetPrint that solves this problem.
Also, perhaps APPLETLK.DLL does no better--I don't yet have the
experience (direct or shared) to say, but for now it holds out the
hope that it is better integrated with Windows than NetPrint.
Expriences to share, anyone?

-- Pean Lim

INTERNET:  plim@Teknowledge.COM
  USENET:  {uunet|ucbvax|sun|decwrl}!Teknowledge.COM!plim