Re: Appletalk printing problem update

[shack@crash.cts.com (Randy Shackelford)]

In article <3hg8o5$ejr@cello.gina.calstate.edu>,
Greg R. Achenbach <lacoss@cello.gina.calstate.edu> wrote:

>If I cold boot, printing from GS/OS programs happens just like it should. 
>AppleWorks also works OK.  If I start up ProTerm and then go back to
>GS/OS, then printing gets EXTREMELY slow.  It takes about 10 minutes to
>print one page with one word on it, and AppleWorks won't print at all. 
>The thermometer fills up, but nothing comes out the printer.  I don't even
>need to actually do anything in Proterm.  Just starting it up and quitting
>immediately causes the problem.  When attempting to print, the "Establishing 
>Communication" 
>message comes on the screen for about 3 minutes.  Then the "Positioning 
>Printhead" message comes on for about 2 minutes before the printhead is 
>actually positioned, followed by another 2 minutes of the same message.  
>Then the "Pages left to print: 1" message comes on for a few minutes.  
>Then the word will print, followed by another few minutes of that 
>message.  And finally it is done and I get control of the computer back.  
>During this whole process, nothing will interrupt it.  Not escape, nor 
>command-period, nor anything except a powerdown will cancel printing.  A 
>warm boot sometimes gets things back to normal, but to be sure I do a 
>power down and then back up to reboot.  Then things are fine again until 
>proterm is started next.  Does anybody have any idea what is going on?

A really long time ago someone posted a patch for Proterm supplied by Greg S
to cure a problem concerning Appletalk. I used it since my machine went weird
every time I quit Proterm before the patch. I have no problems quitting and
I can print to my Appletalk IW and Laserwriter just as pretty as you please.
I can even print to them inside Proterm. So I'd say you need to try the patch.
It's buried in some junk files on my hard disk so it'd take some work for me
to dig it up. It's a one byte patch.
--
Randy Shackelford                                Huh huh, that was cool.
shack@crash.cts.com