RE: [WinMac] NT/Mac print problems

Dan Schwartz(expresso[at]snip.net)
Mon, 17 Aug 1998 12:13:00 -0400

        Hello, Roger!

        I'll reply inline for clarity...

At 10:08 AM 8/17/98 -0500, Roger Chartier replied to me:
>> Roger:
>>
>> There are several ways to hook up your LocalTalk printer. Depending
>>on how
>>your LAN is set up, and how many Macs and PC's you have will determine the
>>best way.
>>
>> 1) If you have Macs, and only use NT for a server/spooler, print
>>directly
>>to the LW360 by "hanging" the printer off of a Mac and use the LaserWriter
>>Bridge Control Panel. Don't try this trick on a Mac running anything lower
>>than System 7.5.5, due to the "sticky cursor" syndrome;
>
>This means that the a Mac always has to be on and not always I have control
>over this. If the person sitting at the computer restarts it that means
>the the whole network can't print. We are integrating into an NT
>environment and the localtalk bridge would not allow the other NT machines
>to print.

        Just instruct the operator of that Mac to not turn it off. A "hard-on" Mac,
i.e. one with a hard power switch such as a Quadra 610 or PowerMac 6100, is
ideal for this duty. If it crashes, it will quickly be rebooted.

>
>>
>> 2) Or, you can use a hardware Ethernet -> LocalTalk bridge. But
>>again, this
>>is limited to using the printer with Macs;
>>
>
>$400 for the localtalk bridge hardware and this still won't allow the other
>NT machines to print
>

        You can pick these up used for about $50 now.

        Also, please reread item #3 below, using the hot port switching built into
the LaserWriter 360.

>
>> 3) Use a dual connection to the LW360 with hot port switching: The
>>Macs
>>will directly print to the LW360 into the LocalTalk port (preferably
>>connected to the ethernet LAN with either methods 1 or 2, above); and the NT
>>spooler would connect via the parallel port, handling spooled print jobs
>>from the PC's and *spooled jobs* from the Macs.
>
>We would also like to use the NT machine as a file server. This NT machine
>is not going to be used by anyone sitting at it as it has no head. This
>makes it a great file server as I don't have to worry about anyone turning
>it off and causing other trouble. We also have file sharing between the
>macs and we really want to use the ethernet.

        To avoid headaches, you'll want to disable NT's Print Server for Macintosh
service; or if you DO decide to enable it allow the Macs to also print
directly, bypassing the spooler.

        To allow Mac client bypassing, the AppleTalk printer needs to be "released"
from the Spooler.

 -------

        FROM NT4's HELP:
        ~~~~~~~~~~~~~~~~

AppleTalk Port Configuration

Capturing an AppleTalk printing device means that Macintosh users send their
print jobs through the computer running Windows NT Server. Releasing a
captured printing device means that the Macintosh users who print to it
directly will not get the benefit of spooling on the computer running
Windows NT Server. Also, print jobs sent to a released printing device are
not under the control of the system administrator.

For a printing device to be seen by both PC and Macintosh clients, it must
be shared and captured. (Share a printer through the Printer Properties
dialog box, available from Print Manager.) Macintosh users will see the name
you designate in the Share Name option in the Printer Properties dialog box.

If you share a printer but do not capture it, Macintosh users will see the
printing device by both names -- the AppleTalk name and the name you
designated in the Printer Properties dialog box.

If you do not share a printing device and do not capture it, Macintosh users
will see it by its original AppleTalk name.

You can release or recapture the printing device by clearing or selecting
the one option, as appropriate, in the AppleTalk Port Configuration dialog
box.

 -------

>
>> Lastly, make sure you change the 4 MB 72 pin SIMM in the LW360 to a
>>16 MB
>>SIMM. The SIMM can only be 4 or 16 MB (single-sided), and must be 2k row
>>refresh Fast Page Mode, 70 nSec or faster (preferably 60 nSec). I haven't
>>tried EDO in an LW360, though: It probably should work, but I can't
>>guarantee it.
>
>why does the printer need more RAM. I can printer the exact same documents
>directly to the printer over localtalk and it works fine. The printer
>should react the same if it is connected to a mac or a PC.

        The printer will run much faster with more RAM, because it comes stock
from the factory with only 7 MB. The reason is that the page buffer (frame
buffer) will not need to be compressed as it is RIP'd by the printer's CPU.
This will also allow for a bigger input buffer, again speeding up print
jobs. [Just be sure to update the PPD's on all the clients to reflect the
additional RAM!]

>
>>
>>At 08:56 AM 8/17/98 -0500, Roger wrote:
>>>
>>>
>>>Could you send me details of the print drivers you are using on the NT
>>>machine and on the macs. Are these printer connected to the NT machines
>>>directly or have they been captured from the network. The Select 360 does
>>>not do 10T. I believe all the printer you listed off have 10T. These
>>>printer are not on the networks. That is what my goal is
>>>
>>>
>>>Roger...
>>

 -----------------------------------------------------------------

        <mailto:expresso@snip.net>

                Webmaster for <http://www.faulknerstudios.com>

 -----------------------------------------------------------------

* Windows-MacOS Cooperation List *
* FAQ: <http://www.darryl.com/winmacfaq/> *
* Archives: <http://www.darryl.com/winmac/> *
* Subscribe: <mailto:winmac-on@xerxes.frit.utexas.edu> *
* Subscribe Digest: <mailto:winmac-digest@xerxes.frit.utexas.edu> *
* Unsubscribe: <mailto:winmac-off@xerxes.frit.utexas.edu> *

This archive was generated by hypermail 2.0b2 on Mon Aug 17 1998 - 09:21:27 PDT