6/27 KMC Current Problems with Laser1+ Upgrade

1. Doc doesn't tell you minimum s/w revision to load on. The software
doesn't function under 102.117; users should be told to load patches to
102.187, and make sure customers receive the released patch kit with the
laser1+ upgrade.

Also, what new 'Tiger revision should this upgrade patch up to?

2. Doc has user re-compile the 'Tiger files. This generates several
screens of warning messages, and requires user intervention.  Three
options:

  a) Doc should list the expected (normal) outputs and what the user
  should type, or
  
  b) Engineering should re-compile the .LISP files (if needed?) and make a
  new tape (does it have to include all the Tiger files?), or
  
  c) Engineering should certify that the s/w does not need to be
  recompiled, and revise the documentation, or

  d) Engineering should fix the software *or the doc* to not cause the
     warnings.

Option 'a' would be acceptable on a pre-release basis, but I don't feel
this software should go out as is; option 'd' is the only real solution.

Fortunately, it appears that the s/w does not need to be recompiled.
The doc could say to simply (make-system 'tiger) after cold-booting and
before loading site files.  Mike Phillips will test this procedure.

3. Doc gives incorrect procedure for updating site files; needs

   a) before cold boot,

	(make-system 'site :compile :no-reload-system-declaration)
	(update-site-configuration-info) 

      ...and how to verify new site info; and

   b) after cold boot,	(update-site-configuration-info)

4. My first attempts at producing screen dumps were frustrating; they
were not being output, and I thought the printer was hung.

The "flashing ready light" indicator is not documented in the HP manual,
but apparently it means the printer is buffering and processing the
screen dump.  It turns out the user must wait 4-8 minutes for a screen
dump.  The "normal" procedure for getting the printer to dump the last
page of a printout is to force a form feed; but with a screen dump, it
causes the problems I was seeing with incorrect output.  ***This must be
documented for the user! ***

5. Our experience in Andover (including Dave Riddell) is that dumping
several screen dumps causes the printer to wedge.  Has Engineering
tested this product? ...under what loads?  Is the following work-around
documented for users anywhere?

	(tiger:reset-tiger)			;empty the queue
	(si:free-sdu-serial-b)			;un-wedge port b
						;(And resubmit request)