[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: The Postscript option and AppleTalk? (Re: parallel card)
- Subject: Re: The Postscript option and AppleTalk? (Re: parallel card)
- From: supertimer@aol.com (Supertimer)
- Date: 1999/10/19
- Newsgroups: comp.sys.apple2
- Organization: AOL http://www.aol.com
- References: <380b91b4.152776381@news>
CUTblakeney@home.com (Jeff Blakeney) wrote:
>supertimer@aol.com (Supertimer) wrote:
>
>>You are correct, but AppleTalk is usually paired with
>>Postscript. Since the printer does all the rendering,
>>the printer's speed is the limiting factor in both parallel
>>and AppleTalk. No Postscript printer that I know of
>>can outrun AppleTalk, so there's really no need for
>>a parallel card on Postscript laser printers that support
>>AppleTalk.
>
>Actually there is a reason to use parallel instead of AppleTalk.
>AppleTalk requires you to install more stuff into GS/OS so you lose
>more hard drive space on your boot drive, boot times are longer, more
>RAM is used after booting and AppleTalk eats a relatively large amount
>of processor time dealing with interrupts.
AFAIK, there's a difference between AppleTalk to a
laser printer and running software off a LocalTalk
network with the IIGS logged onto a Mac. The former
only takes a toll on interrupts when printing to the
printer. The latter is the one that causes problems
since the IIGS is expected to "keep an eye" out
for data from the Mac.
So unless you were using Express to print to parallel
in the background, it does not matter because the
IIGS does not normally do background printing. As
such, taking a toll or not taking a toll on interrupts
during printing does not matter. You can't use the
IIGS at that time one way or the other.
In fact, if you only set up a network printer, you could
delete many of the AppleTalk files on the IIGS setup
if I remember correctly.