Trailing-Edge
-
PDP-10 Archives
-
BB-F493Z-DD_1986
-
10,7/galaxy.bwr
There are 12 other files named galaxy.bwr in the archive. Click here to see a list.
GALAXY.BWR
Beware file for GALAXY Version 5.1
February 1986
COPYRIGHT (c) DIGITAL EQUIPMENT CORPORATION 1986. ALL RIGHTS
RESERVED.
THIS SOFTWARE IS FURNISHED UNDER A LICENSE AND MAY BE USED AND COPIED
ONLY IN ACCORDANCE WITH THE TERMS OF SUCH LICENSE AND WITH THE
INCLUSION OF THE ABOVE COPYRIGHT NOTICE. THIS SOFTWARE OR ANY OTHER
COPIES THEREOF MAY NOT BE PROVIDED OR OTHERWISE MADE AVAILABLE TO ANY
OTHER PERSON. NO TITLE TO AND OWNERSHIP OF THE SOFTWARE IS HEREBY
TRANSFERRED.
THE INFORMATION IN THIS SOFTWARE IS SUBJECT TO CHANGE WITHOUT NOTICE
AND SHOULD NOT BE CONSTRUED AS A COMMITMENT BY DIGITAL EQUIPMENT
CORPORATION.
DIGITAL ASSUMES NO RESPONSIBILITY FOR THE USE OR RELIABILITY OF ITS
SOFTWARE ON EQUIPMENT WHICH IS NOT SUPPLIED BY DIGITAL.
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 2
1.0 GALAXY VERSION 5.1
This Beware File accompanies the new GALAXY Version 5.1 software that
is being distributed with TOPS-10 Version 7.03.
It is provided to warn site managers and installers of the critical
differences between GALAXY Versions 4.1 and 5.1. "Critical
differences" are those that affect or destroy user jobs and requests,
batch control files, the functionality of programs, or that require
operational changes. In addition, this file provides instructions for
the installation of GALAXY 5.1 on a running TOPS-10 Version 7.03 and
GALAXY Version 4.1 system. Therefore, you should read this file
thoroughly before installing GALAXY 5.1 on your system.
2.0 NEW FEATURES AND FUNCTIONALITY
GALAXY 5.1 replaces GALAXY Version 4.1 on TOPS-10, and provides many
features and enhancements that are intended to optimize the efficiency
of DECsystem-10 site operations and management. Some of the
enhancements are:
o A more efficient and easier to use tape and disk catalog
handler.
o Enhancements to the OPR program which will allow the operator
to conduct most duties within the OPR environment. These
enhancements include:
- Allowing access to all priviledged monitor commands such
as the ATTACH/DETACH device, SET BATMIN/BATMAX commands.
- Being able to reconfigure the hardware system without
having to run the CONFIG program.
- Being able to set and display parameters for the Ethernet
Local Area Transport network.
- Being able to set the CI network online or offline on
individual CPUs.
- Allow access to the CATALOG daemon to insert and delete
tape or structure entries into the system structure list
file more easily.
o New QUASAR functionality includes:
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 3
- Support for deadlock avoidance in allocating resources.
- [SYSTEM]INFO functionality in allocating and reporting
system PIDS. This change effectively makes the SYSINF
program obsolete.
o LPTSPL will be able to handle the dynamic loading of fonts
into an LN01 laser printer without user intervention, other
than to specify the font name.
o Event queue and time of day take files will be handled
through QUASAR and the OPR/ORION programs, thus eliminating
the need for the OPSER program.
o A new multi-threaded FAL which will be controllable through
the OPR program and will allow the operator to start and stop
FAL streams as he would any other device stream.
3.0 INSTALLING GALAXY VERSION 5.1
The GALAXY Version 5.1 software is distributed on the CUSP tape. In
order to install it, be sure first that it is possible to fallback to
GALAXY Version 4.1 if it is desirable to do so. In order to do this,
shutdown all spoolers in the GALAXY 4.1 system. Once this is done,
the GALAXY 4.1 system should be copied from SYS: to a secondary disk
area, along with the QUASAR master queue file QSRMS1.QSR. If the
redundant queue file option was chosen in the GALGEN dialogue,
QSRMS2.QSR must also be moved to the secondary disk area. Since the
master queue file format is changed between GALAXY 4.1 and GALAXY 5.1,
the master queue file(s) must be deleted from SYS: or QUASAR will
crash upon startup. This will mean the loss of all queued jobs on the
system, and the site should be prepared for it.
3.1 Installing The CATLOG Program
The CATLOG program is the only reader and writer of STRLST.SYS. When
it is run for the first time, it looks up the the existing STRLST.SYS
file (file format 0) and converts it to a new format (file format 1)
under the same name. Therefore, before running CATLOG, be sure to
make a backup copy of the old STRLST.SYS file for drop back purposes.
CATLOG will not do this for you.
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 4
3.2 Restoring The GALAXY System
Once fallback is ensured, follow these instructions in order to
restore the GALAXY system from tape.
1. Mount the "CUSP" tape as per the instructions in the "TOPS-10
Monitor installation Guide" instructions.
2. Using BACKUP, restore GALAXY .EXE files to SYS:[1,4] using
the commands:
/TAPE TAPE:
/REWIND
/NOINTERCHANGE
/RESTORE SYS:[1,4]*.*=DSKB:[10,7,GALAXY,*]*.EXE
This will restore all the executable files for running
GALAXY.
3. GALAXY Version 5.1 also needs the new CATLOG cusp. To
restore this as well, type to BACKUP:
/REWIND
/RESTORE SYS:[1,4]=DSKB:CATLOG.EXE[10,7,CATLOG]
4. Edit your site's SYSJOB.INI file to reflect the fact that
CATLOG must start with GALAXY.
You will also want to update the GALAXY related REL and UNV files if
you have any site specific cusps which use GLXLIB. In order to do
this, copy any old REL and UNV files on the system library areas to a
secondary disk area and, type to BACKUP:
/REWIND
/RESTORE REL:[5,11]=DSKB:[10,7,GALAXY,GLXLIB] -
#GLXLIB.REL,GLXINI.REL
/REWIND
/RESTORE UNV:[5,17]=DSKB:[10,7,GALAXY,*]*.UNV
The GALAXY files on SYS:[1,4] reflect a system built with all defaults
specified through the GALGEN dialogue. If you wish to build a
customized system, GALAXY.DOC contains which options are available for
modifications. GALAXY.DOC also contains a list of the components
which are required for a complete GALAXY system.
NOTE
Previous releases of GALAXY have placed
all GALAXY files on one area on the CUSP
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 5
tape. GALAXY Version 5.1 comes
unbundled with each major component in
its own [10,7,GALAXY,*] SFD. The
distributed GALAXY.CTL file which we
stress should be used only as a guide
for site specific builds, assumes that
all files are in the same SFD. This is
because we have found that internally
this is the best way to build GALAXY,
but it is best to maitain the sources
separately.
4.0 GALAXY AND TOPS-10 VERSION 7.03
Although GALAXY Version 5.1 is meant to run under TOPS-10 Version 7.03
it is distributed on the tape with 7.02 fallback code enabled. Once
your site has permanently migrated to TOPS-10 7.03, you may wish to
disable this code. To do this, GALAXY must be rebuilt. Use the
following steps:
1. Follow instructions in GALAXY.DOC to restore all GALAXY
sources to the area [10,7].
2. Edit GALAXY.CTL to answer "NO" to the question "Is 7.02
fallback code to be included?"
Note that "NO" is the default.
3. SUBMIT GALAXY.CTL and wait for completion.
4. Upon completion, copy the new system to SYS:[1,4].
GALAXY is now built with the fallback code disabled.
NOTE
If you are building your customized
GALAXY 5.1 system, your old GALAXY.CTL
file will not work, since the format of
the GALGEN dialogue has changed.
Digital recommends that the new
GALAXY.CTL, distributed on the "CUSP"
tape in the DSKB:[10,7,GALAXY] SFD, be
used as a base for site specific
configurations. The customer is
encouraged to edit this file to reflect
his particular desired options.
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 6
4.1 INTERDEPENDENCIES
4.1.1 GALAXY/SYSINF/MONITOR - The interdependencies between GALAXY
Version 5.1, the SYSINF program and the TOPS-10 monitor, may be
summerized as follows:
In order to allow fallback to 7.02, the fallback option must ALWAYS be
specified in the GALGEN dialog. Once done, either SYSINF V3B(322)
must be run (via SYSJOB.INI) to allow QUASAR to talk to CATLOG, or the
7.02 monitor must be rebuilt with an additional system PID, index 16,
so that CATLOG may start up without need of SYSINF when running 7.02.
SYSINF V3B(322) is the only version of SYSINF which should be run in
association with GALAXY Version 5.1, or (if necessary,) TOPS-10
Version 7.03. Any other version of SYSINF will not work with TOPS-10
7.03. SYSINF V3B(322) will check whether TOPS-10 Version 7.03 is
running and will defer to QUASAR for all functions if so. QUASAR will
defer to SYSINF if it detects that it is running under TOPS-10 Version
7.02. This is necessary because of QUASAR's dependency on TOPS-10
Version 7.03 running.
For those customers who wish to retain SYSINF for some reason, it can
still be found on the customer supported tape in the save-set
"CUSTOMER SUP CUSPS."
In addition, there are two PCOs which must be applied to 7.02 in order
to run with GALAXY version 5.1.
1. PCO 10-702-197 corrects problems in IPCSER with the QUEUE.
UUO.
2. PCO 10-702-200 causes the monitor's LPT device drivers to
correctly set the printer class.
These two PCOs are listed in the appendix of this beware file for the
benefit of those customers which may not have received the autopatch
tapes where they are distributed before they receive 7.03.
4.1.2 LPTSPL/ANF10/MONITOR - LPTSPL now takes the printer class
returned by the monitor seriously. Remote stations are assumed to
have LP05 class printers if the monitor returns an unknown printer
class, but customers are encouraged to build their configurations with
the correct printers specified. This will prevent possible future
conflicts if any changes must be made to the LP05 printer driver which
is incompatible with the customer's actual printer.
Local printers will be handled by the installation of PCO 10-702-200,
which is described in the previous section.
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 7
5.0 RESTRICTIONS
During the course of field testing a problem with deadlock avoidance
was discovered, which we were unable to fix in time for the release of
5.1. The problem manifests itself in this manner: If two users place
a MOUNT request for a structure that is not currently online, only the
first user will have his request satisfied when the operator mounts
the structure. This problem exists only at those sites which will run
with deadlock avoidance turned on. The QAR which reported the problem
has been converted into a high priority SPR and will be dealt with as
quickly as possible. Until it can be resolved however, it must remain
a temporary restriction.
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 8
Appendix
Required PCOs for 7.02
[BEGIN PCO 10-702-197]
[SYMPTOM]
Can't send useful information to ACTDAE via QUEUE. UUO. Have to
use regular IPCF (with all its associated headaches) instead.
[DIAGNOSIS]
Monitor was being too helpful in protecting QUASAR from users, no
matter how much it got in the way of other components, or how little
QUASAR needed the protection.
Immediate mode arguments mistakenly don't allow more than one
word in the sub-block.
[CURE]
Remove the restriction on the range of block codes from IPCSER.
Fix sub-block handling to deal correctly with immediate-mode
blocks.
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 9
[FILCOM]
File 1) BLKK:IPCSER.MAC[7,7022] created: 1039 04-Jan-84
File 2) SIXT:IPCSER.MAC[30,5653,ACCT] created: 1630 22-Nov-85
1)40 HLRE P1,T1
1) TRNE P1,1 ;MUST BE AN ODD NUMBER OF ARGUME
NTS
1) CAIGE P1,5 ;MUST BE AT LEAST ONE REAL ARGUM
ENT
**** ;At GLXINF+1L
2)40 HLRZ P1,T1
2) CAIGE P1,5 ;MUST BE AT LEAST ONE REAL ARGUM
ENT
**************
1)40 HRRES T1
1) JUMPE T1,QUEILF
1) CAIL T1,.GTQFT##-.GTQFC##
1) CAILE T1,QUTBLN##
1) JRST QUEILF
1) HRRZ T1,.GTQFT##(T1)
1) SKIPN (T1)
1) JRST QUECNR ;COMPONENT NOT RUNNING
**** ;At GLXINF+14L
2)40 HRRES T1 ;GET FUNCTION CODE
2) JUMPE T1,QUEILF ;ZERO IS ILLEGAL
2) CAML T1,[.GTQFT##-.GTQFC##] ;CUSTOMER FUNCTION?
2) CAILE T1,QUTBLN## ;DEC FUNCTION?
2) JRST QUEILF ;NO TO EITHER
2) HRRZ T1,.GTQFT##(T1) ;GET ADDRESS OF ASSOCIATED PID
2) JUMPE T1,QUEILF ;ILLEGAL FUNCTION IF NO MATCHING
PID
2) SKIPN (T1) ;DOES IT EXIST?
2) JRST QUECNR ;COMPONENT NOT RUNNING
**************
1)40 MOVEI P2,-3(P1)
1) LSH P2,-1 ;ARGUMENTS ARE WORD PAIRS
1) MOVEI P3,QUESDL ;5 WORDS OF GALAXY HEADER, 2 WOR
D FUNCTION BLOCK
**** ;At GLXINF+48L
2)41 MOVEI P2,-3(P1) ;COUNT OF ARGUMENT WORDS
2) MOVEI P3,QUESDL ;5 WORDS OF GALAXY HEADER, 2 WOR
D FUNCTION BLOCK
**************
1)41 SKIPGE T1 ;IF IMMEDIATE,
1) MOVEI T2,1 ;IMMEDIATE MESSAGES ARE TWO WORD
S LONG
1) ADDI P3,1(T2) ;LENGTH OF THE DATA BLOCK + 1 FO
R THE HEADER WORD
1) JRST GLXIN1
1) ;HERE TO ALLOCATE THE CORE TO BUILD THE MESSAGE
**** ;At GLXIN1+3L
2)41 ADDI P3,1(T2) ;LENGTH OF DATA BLOCK + 1 FOR HE
ADER WORD
2) JRST GLXIN1 ;LOOP BACK
2)42 ;HERE TO ALLOCATE THE CORE TO BUILD THE MESSAGE
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 10
**************
1)41 MOVEI T2,-3(P1) ;ARGUMENT COUNT
1) LSH T2,-1 ;TWO WORDS PER ARGUMENT
1) ADDI T2,QUEIGL ;FOUR ARGUMENTS INTERNALLY GENER
ATED
1) MOVEM T2,QUEARC(T1)
1) MOVE T2,[QUEFCL,,.WTUFC] ;FUNCTION BLOCK
**** ;At GLXIN2+22L
2)42 MOVEI T2,QUEIGL ;SET INITIAL ARGUMENT COUNT TO
2) MOVEM T2,QUEARC(T1) ; THE NUMBER OF INTERNAL BLOCKS
GENERATED
2) MOVE T2,[QUEFCL,,.WTUFC] ;FUNCTION BLOCK
**************
1)42 GLXIN3: MOVEI P2,-3(P1) ;NUMBER OF ARGUMENTS TO COPY
1) LSH P2,-1 ;ARGUMENTS ARE WORD PAIRS
1) MOVEI P1,QUESDL(T1) ;WHERE TO STORE ARGUMENTS
**** ;At GLXIN3
2)43 GLXIN3: MOVEI P2,-3(P1) ;NUMBER OF ARGUMENT WORDS
2) MOVEI P1,QUESDL(T1) ;WHERE TO STORE ARGUMENTS
**************
1)42 LDB T3,[POINT 9,T1,17] ;LENGTH OF THE DATA BLOCK
1) SKIPGE T1 ;IMMEDIATE ARGUMENT?
1) MOVEI T3,1 ;YES, LENGTH IS 1
1) LDB T4,[POINT 12,T1,35] ;FUNCTION
1) HRLI T4,1(T3) ;LENGTH,,FUNCTION
**** ;At GLXIN4+2L
2)43 HLRZ T3,P3 ;GET MESSAGE ADDRESS
2) AOS QUEARC(T3) ;COUNT THE BLOCK ABOUT TO BE ADD
ED
2) LDB T3,[POINT 9,T1,17] ;LENGTH OF THE DATA BLOCK
2) HRRZ T4,T1 ;FUNCTION
2) HRLI T4,1(T3) ;LENGTH,,FUNCTION
**************
1)42 MOVE T4,T2 ;ASSUME AN IMMEDIATE ARGUMENT
1) JUMPL T1,GLXIN6 ;GO IF IT IS
1) GLXIN5: EXCTUX <MOVE T4,(T2)> ;GET DATA
1) AOS T2 ;NEXT WORD OF DATA
1) GLXIN6: MOVEM T4,(P1) ;STORE DATA IN THE MESSAGE
1) SOSLE T3 ;MOVED ALL DATA ITEMS?
**** ;At GLXIN4+9L
2)43 GLXIN5: EXCTUX <MOVE T4,(T2)> ;GET DATA
2) MOVEM T4,(P1) ;STORE DATA IN THE MESSAGE
2) HRRI T2,1(T2) ;ADVANCE ARGUMENT POINTER
2) SOSLE T3 ;MOVED ALL DATA ITEMS?
**************
1)44 PUSH P,T1
1) PUSHJ P,GETWR1##
1) JRST NXTAD2 ;QUEADC, BUT POP T1 AND CALL OFF
STACK FIRST.
1) ;IMMEDIATE?
1) SKIPL T2,(P) ;BIT ZERO ON INDICATES IMMEDIATE
ARGUMENT
1) JRST NXTAR1 ;NOPE - PRETEND WE HAVE @T1
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 11
1) TDNE T2,[377776,,770000]
1) JRST NXTIAL ;SPURIOUS BITS ON - QUEIAL
1) MOVE T2,T1 ;ARGUMENT IS NOW IN T2
1) JRST TPOPJ1## ;RESOLVED
1) NXTAR1: TDNN T2,[777000,,770000]
1) TLNE T1,(17777B12) ;ALLOW ONLY @(17)777777
1) JRST NXTIAL ;SPURIOUS BITS ARE ON, QUEIAL
1) HLRZS T2 ;NUMBER OF WORDS OF ARGUMENT IS
IN LEFT HALF
1) CAIGE T2,1
1) JRST NXTIAL ;LESS THAN ONE WORD OF ARGUMENT,
QUEIAL
1) PUSH P,M
**** ;At NXTARG+3L
2)45 TLNN T1,777 ;WORD COUNT SPECIFIED?
2) TLO T1,1 ;NO--DEFAULT TO ONE
2) HLRZ T2,T1 ;NUMBER OF WORDS OF ARGUMENT IS
IN LEFT HALF
2) ANDI T2,777 ;STRIP OFF ANY FLAGS THERE MIGHT
BE
2) TLNN T1,377000 ;ANY ILLEGAL BITS TURNED ON?
2) CAIGE T2,1 ;REASONABLE LENGTH?
2) JRST NXTIAL ;ILLEGAL ARGUMENT
2) PUSH P,T1 ;SAVE ON STACK
2) JUMPGE T1,NXTAR1 ;GO FETCH IF NOT IMMEDIATE
2) HRRI M,1(M) ;ADVANCE ARGUMENT POINTER
2) MOVE T1,M ;ADDRESS OF SUB-BLOCK
2) PUSH P,M ;BALANCE STACK
2) JRST NXTAR2 ;RE-JOIN COMMON CODE
2) NXTAR1: PUSHJ P,GETWR1##
2) JRST NXTAD2 ;QUEADC, BUT POP T1 AND CALL OFF
STACK FIRST.
2) TLNE T1,(17777B12) ;ALLOW ONLY @(17)777777
2) JRST NXTIA2 ;SPURIOUS BITS ARE ON, QUEIAL
2) HLRZ T2,(P) ;GET LENGTH OF THIS SUB-BLOCK
2) PUSH P,M
**************
1)44 PUSH P,T1 ;SAVE ADDRESS OF THE DATA BLOCK
1) HRRZS T1,(P) ;ADDRESS OF DATA BLOCK, CLEAR LE
FT HALF BITS
1) HLL T1,-2(P) ;WHERE CHKIC WANTS LENGTH
1) PUSHJ P,CHKIC
1) POP P,T2 ;ADDRESS OF THE DATA BLOCK
1) POP P,M ;RESTORE POINTER TO THE ARGUMENT
LIST
1) JRST TPOPJ1## ;RESTORE ARGUMENT AND RETURN
**** ;At NXTAR1+10L
2)45 NXTAR2: PUSH P,T1 ;SAVE ADDRESS OF THE DATA BLOCK
2) HRRZS T1,(P) ;ADDRESS OF DATA BLOCK, CLEAR LE
FT HALF BITS
2) HLL T1,-2(P) ;WHERE CHKIC WANTS LENGTH
2) TLZ T1,400000 ;IGNORE IMMEDIATE-MODE BIT
2) PUSHJ P,CHKIC
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 12
2) POP P,M ;RESTORE BLOCK ADDRESS
2) EXCH M,(P) ;SAVE AND RESTORE M
2) HLRZ T2,-1(P) ;GET SUB-BLOCK LENGTH PLUS FLAG
2) TRZN T2,400000 ;IMMEDIATE MODE?
2) MOVEI T2,1 ;NO, ONLY ONE WORD USED BY POINT
ER
2) SUBI P2,(T2) ;ACCOUNT FOR ARGS IN UUO BLOCK
2) JUMPL P2,NXTIA2 ;ILLEGAL ARG LIST IF COUNTS DON'
T MATCH
2) ADD T2,M ;POINT PAST CURRENT ARGUMENT
2) HRRI M,-1(T2) ;OFFSET FOR GETWR1
2) POP P,T2 ;ADDRESS OF THE DATA BLOCK
2) JRST TPOPJ1## ;RESTORE ARGUMENT AND RETURN
**************
1)45 NXTIAL: POP P,(P) ;POP T1,
1) POP P,(P) ; AND CALL TO NXTARG
1) PJRST QUEIAL ; AND THEN GIVE AN "ILLEGAL ARG
" ERROR
**** ;At NXTAD2
2)46 NXTIA2: POP P,(P) ;POP T1,
2) NXTIAL: POP P,(P) ; AND CALL TO NXTARG
2) PJRST QUEIAL ; AND THEN GIVE AN "ILLEGAL ARG
" ERROR
**************
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 13
[FILCOM]
File 1) BLKK:UUOSYM.MAC[7,7022] created: 1319 13-Dec-83
File 2) SIXT:UUOSYM.MAC[30,5653,ACCT] created: 1650 22-Nov-85
1)51 QA.TYP==7777B35 ;ARGUMENT TYPE (BITS 18-23 RESER
VED FOR GALAXY INTERNALS)
1) ;ARGUMENT TYPES 4000-7777 RESERV
ED FOR CUSTOMERS
**** ;At top of file +2158L
2)51 QA.TYP==777777B35 ;ARGUMENT TYPE (BITS 18-23 RESER
VED FOR
2) ; GALAXY INTERNALS IN GALAXY FUN
CTIONS)
2) ;ARGUMENT TYPES 4000-7777 RESERV
ED FOR CUSTOMERS
**************
[END OF PCO 10-702 -197]
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 14
[BEGIN PCO 10-702-200]
[SYMPTOM]
GALAXY Version 5 LPTSPL doesn't run under a 7.02 monitor. LPTSPL
claims printers do not exist.
[DIAGNOSIS]
LPT device drivers do not set the printer class in the hardware
characteristics word of the DDB.
[CURE]
Make sure the printer class is setup correctly.
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 15
[FILCOM]
File 1) BLKK:DLPSER.MAC[7,7022] created: 1044 13-Dec-83
File 2) BLKK:DLPSER.MAC[10,56,SPR] created: 0117 15-Jan-86
1)7 DLPREL: MOVSI T1,DEPADV ;GET "DON'T ADVANCE BUFF
ER" BIT
1) ANDCAM T1,DEVADV(F) ;TURN IT OFF IN DDB
**** ;At DLPREL
2)7 DLPREL: MOVEI T1,.HCULP ;LP05 CLASS PRINTER
2) DPB T1,[POINT 7,DEVHCW(F),14] ;SAVE IN DDB
2) MOVSI T1,DEPADV ;GET "DON'T ADVANCE BUFF
ER" BIT
2) ANDCAM T1,DEVADV(F) ;TURN IT OFF IN DDB
**************
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 16
[FILCOM]
File 1) BLKK:LP2SER.MAC[7,7022] created: 1901 26-Sep-83
File 2) BLKK:LP2SER.MAC[10,56,SPR] created: 0137 15-Jan-86
1)21 HLLM T3,DEVHCW(F) ;STORE HARDWARE CHARACTE
RISTICS
**** ;At LPTTYP+17L
2)21 TLO T3,(<.HCULP>B14) ;LP05 CLASS PRINTER
2) HLLM T3,DEVHCW(F) ;STORE HARDWARE CHARACTE
RISTICS
**************
GALAXY.BWR: Beware file for GALAXY Version 5.1 Page 17
[FILCOM]
File 1) BLKK:LPTSER.MAC[7,7022] created: 1901 26-Sep-83
File 2) BLKK:LPTSER.MAC[10,56,SPR] created: 0137 15-Jan-86
1)17 LPTTY1: HLLM T1,DEVHCW(F) ;STORE HARDWARE CHARACTERISTICS
1) DPB T2,[POINT 3,DEVHCW(F),11] ;STORE CONTROLLER TYPE
IN DEVHCW
**** ;At LPTTY1
2)17 LPTTY1: TLO T1,(<.HCULP>B14) ;LP05 CLASS PRINTER
2) HLLM T1,DEVHCW(F) ;STORE HARDWARE CHARACTERISTICS
2) DPB T2,[POINT 3,DEVHCW(F),11] ;STORE CONTROLLER TYPE
IN DEVHCW
**************
[END OF PCO 10-702 -200]