Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!rutgers!gatech!emory!joe
From: joe@mathcs.emory.edu (Joe Christy)
Newsgroups: comp.sys.next
Subject: printer woes
Keywords: np_serial_cmd, printer status
Message-ID: <4188@emory.mathcs.emory.edu>
Date: 1 Jul 89 16:23:22 GMT
Organization: Math & Computer Science, Emory University, Atlanta, GA
Lines: 25



	Since the problem I'm having seems to be chronic, I thought I'd
post to the net and see if it was idiosyncratic as well.
	Last night my machine rebooted itself, irritatingly aborting the
auto backup script which happened to be running at the time. A
perusal of the system messages revealed the following:
	Jun 30 21:43:49 suzette vmunix: np0: serial command parity error
	Jul 1 02:39:07 suzette vmunix: panic: (Cpu 0) np_serial_cmd: can't
	flush printer status
	... and then the reboot.
This is happening with annoying consistency [about once a day]. Does
anyone else have this problem? My theory is that this might be caused by
my habit of leaving the Printer app running constantly with the Test...
window open [so as to catch "toner low" messages].
	By the way, has anyone discovered a more graceful way to discover
when the printer thinks [erroneously] that the toner is low, or to
convince it that the toner is only low when the toner is actually low?

	On an unrelated topic, is there a way to get the Workspace to open
a Terminal window as console when it launches, similar to the way that
it opens various apps in the dock on launch? I find it annoying to
have to periodically Edit /private/adm/messages to look at the console
messages. I know about Terminal -Console YES & from a command line, but
what like to do this automatically.