pub/facslog2.2/buglist

Known problems in FACSLOG2.2

1.      The LOG program will interrupt printing if the spooler is active
	on CONSORT 32 systems.  Do *not* log out while printing is
	taking place.  If you use a "buffer box", you might consider not
	using the spooler (remove the line from the #46:AUTOSTART file.)

2.      Programs aborting because of errors will usually issue a
	message, but Master Page may come back up too fast for it to be
	readable.  If a program is aborting when you attempt to run it, 
	quit Master Page (from the "BD" menu) and press "X" and supply
	it's name to run it again.  HFS users will have to supply the
	complete path, e.g.  #11:/APP/LOG/LOG.  Include the period at
	the end of the program name.  When the program aborts, error
	messages should remain on the screen.  After reading them, press
	"X" and enter "MASTER" to re-start Master Page.

3.      Recovery systems for HFS may not need to use the "What" command,
	as described in section 4.3.2 of the manual.  Test your system
	to see if you really need it.

4.	Master Page sometimes sends one or two carriage returns when
	starting programs.  This seems to occur when starting the first
	program from Master Page after booting the computer.

	If LOG is run *before* Master Page (as it is if you configure
	AUTOSTART to run LOG automatically) AND the *first* user
	logs-out before running any other programs, one of these
	carriage returns will answer the "Press enter..."  prompt that
	holds the information in OPENING.TEXT on the screen until the
	user has read it; thus, the *second* user of the system will not
	see the OPENING.TEXT info.

	For those utilities that begin with date entries (EDITLOG or
	PRINTLOG), this has the effect of entering the current month and
	day to begin a search.  Just continue on with the other entries,
	then enter "DATE" to re-enter (and correct) the erroneous
	fields, if necessary.

5.	If you configure AUTOSTART to run LOG automatically, you should
	have the following lines as the last lines in your file:

	QX#11:/APP/LOG/LOG.
	XMASTER
					<== this line is blank

	If you use an OPENING.TEXT file, LOG will wait for a carriage
	return after displaying it; however, when LOG is called by the
	AUTOSTART file, the *next* carriage return comes after the command
	to execute Master Page.  Therefore, the OPENING.TEXT info is cleared
	from the screen, but Master Page doesn't start.  Change these lines
	to the following if you use OPENING.TEXT:

	QX#11:/APP/LOG/LOG.
					<== blank line
	XMASTER
					<== blank line

	The extra blank line provides the carriage return that was previously
	provided by the "XMASTER" command, and Master Page will start 
	automatically as it should; unfortunately, the first user will not
	be able to read the OPENING.TEXT info, since a carriage return comes
	immediately after he logs in.

ITEMS 4 & 5 ABOVE will be fixed with a revision to the LOG program, coming
soon (I hope).

