How about the Kodak Digital Science 8560 PS? I've been having some problems with it (some offensive postscript commands being sent to it are locking up the network interface on it):
Filter_status: job type 'POSTSCRIPT' at 12:44:10.752 Filter_status: transferring 57209 bytes at 12:44:10.753 Filter_status: 35 percent done at 12:44:10.753 Filter_status: 71 percent done at 12:44:10.849 Filter_status: 100 percent done at 12:44:10.850 Filter_status: sent job file at 12:44:10.850 Filter_status: getting end using 'ps' at 12:44:10.850 Filter_status: error = 'undefined' at 12:44:19.244 Filter_status: Error: undefined; OffendingCommand: ^D^D^D at 12:44:19.244 Filter_status: using model 'postscript' at 12:44:31.847 Filter_status: pagecount using 'ps script' at 12:44:31.860 Filter_status: setting up printer at 12:44:31.860 Filter_status: getting sync using 'ps' at 12:44:31.861 Filter_status: sync done at 12:44:32.362 Filter_status: pagecounter 24804 after 1 attempts at 12:44:32.562 Filter_status: pagecounter 24804 at 12:44:32.562 Filter_status: sending job file at 12:44:32.563 Filter_status: starting transfer at 12:44:32.563 Filter_status: initial job type 'POSTSCRIPT' at 12:44:32.564 Filter_status: decoded job type 'POSTSCRIPT' at 12:44:32.564 Filter_status: job type 'POSTSCRIPT' at 12:44:32.564 Filter_status: transferring 57209 bytes at 12:44:32.565 Filter_status: 35 percent done at 12:44:32.581 Filter_status: 71 percent done at 12:44:32.584 Filter_status: 100 percent done at 12:44:33.484 Filter_status: sent job file at 12:44:33.484 Filter_status: getting end using 'ps' at 12:44:33.484 Filter_status: error = 'undefined' at 12:44:40.636 Filter_status: Error: undefined; OffendingCommand: ^D^D^D at 12:44:40.636 Filter_status: using model 'postscript' at 13:35:00.772 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:36:17.319 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:37:34.638 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:38:51.978 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:40:09.339 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:41:26.692 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:42:44.088 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:44:01.426 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:45:18.763 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:46:36.112 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:47:53.418 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:49:10.729 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:50:28.060 Filter_status: connect to '130.219.217.178 port 9100' failed - Connection timed out at 13:51:45.382 ...any ideas? ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent. | IST/ACS - New Jersey Medical School - C630 ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
