Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!XEROX.COM!Wilson.ES_AE
From: Wilson.ES_AE@XEROX.COM
Newsgroups: comp.laser-printers
Subject: LJ IIISi "Clock"
Message-ID: <9105132000.AA02283@crayola.cs.UMD.EDU>
Date: 8 May 91 18:15:11 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 32
Approved: laser-lovers@brillig.umd.edu


There is a new operator in the Si System Dictionary called 'realtime'

Use it instead of 'usertime'

usertime does not increment while the "Interpreter" is waiting for data from
the I/O Board.  Furthermore, comment lines never quite make it to the
Interpreter.

This is the PS Level II implementation of usertime.  Without changing your
spooler, you could send an 'exitserver' file down every time you powered up
which replaced usertime with realtime.  To wit, (an untried example):

%Oh, how we yearn for the old usertime
%
%Copyright (C) 1991 Xerox Corporation.
%
systemdict /realtime known {
   serverdict begin 0 exitserver
   userdict begin
      /usertime /realtime load def
      end
   (Control-D Follows) print flush
   } if    %Control-D within {}if hardly ever works, but just in case

However, this won't work for some PS files which circumvent userdict, AND, now
that the cat's out of the bag, some of your clients could bugger up realtime to
return real short durations.  The solution is to change the exitserver
password, but then some legitimate users will have a problem.  For example,
LzrPrep has an exitserver command.

Rick