https://gunkies.org/w/api.php?action=feedcontributions&user=Vaxorcist&feedformat=atom
Computer History Wiki - User contributions [en]
2024-03-28T20:50:11Z
User contributions
MediaWiki 1.30.0
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_021_session_start.png&diff=33854
File:VSII-ULT0404 021 session start.png
2024-03-09T15:40:28Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_019_login_screen.png&diff=33853
File:VSII-ULT0404 019 login screen.png
2024-03-09T15:39:08Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_018_final_boot.png&diff=33852
File:VSII-ULT0404 018 final boot.png
2024-03-09T15:38:49Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_017_system_configuration_2.png&diff=33851
File:VSII-ULT0404 017 system configuration 2.png
2024-03-09T15:36:42Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_016_mandatory_software_done.png&diff=33850
File:VSII-ULT0404 016 mandatory software done.png
2024-03-09T15:34:27Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_015_start_mandatory_software.png&diff=33849
File:VSII-ULT0404 015 start mandatory software.png
2024-03-09T15:33:12Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_011_up_to_time_zone.png&diff=33848
File:VSII-ULT0404 011 up to time zone.png
2024-03-09T15:30:38Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_006_root_file_system_reboot.png&diff=33847
File:VSII-ULT0404 006 root file system reboot.png
2024-03-09T15:27:44Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_005_choice_system_disk_confirm.png&diff=33846
File:VSII-ULT0404 005 choice system disk confirm.png
2024-03-09T15:25:20Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=VSV21_Graphic_System&diff=33845
VSV21 Graphic System
2024-03-09T09:37:05Z
<p>Vaxorcist: display resolution values added</p>
<hr />
<div>The '''VSV21 Graphic System''' is a single-module [[DEC card form factor|quad]] size option for the [[QBUS#Variable address size|Q22]] [[QBUS]]. It is a high functionality graphics control module capable of working on the following processors:<br />
<br />
* [[PDP-11/23+]]<br />
* [[PDP-11/53]]<br />
* [[PDP-11/73]]<br />
* [[PDP-11/83]]<br />
* [[MicroVAX II]]<br />
<br />
It is capable of interfacing with:<br />
<br />
* A color [[video display|monitor]], e.g. a [[VR241]]<br />
* An [[LK201]] [[keyboard]]<br />
* A pointing device ([[joystick]], trackball, [[mouse]], tablet)<br />
* A [[serial interface]] (example [[DHV11]])<br />
<br />
The display resolution is settable via switches on the module to one of:<br />
<br />
* 640 x 480<br />
* 640 x 240<br />
* 512 x 512<br />
* 512 x 256<br />
<br />
The VSV21 has got [[operating system]] support from:<br />
* [[RSX-11M-PLUS]]<br />
* [[Micro/RSX]]<br />
* [[MicroVMS]] resp. [[VMS]]<br />
<br />
When the VSV21 is interfaced to the host processor via its serial interface, it can be configured to emulate a basic [[terminal]]. In this configuration the Q22 bus interface is not used, and the VSV21 can be used as the host console terminal.<br />
<br />
The VSV21 is provided with [[VSV11 Graphic System|VSV11]] emulation software which enables it to run applications that have been developed for the [[VS11]] and VSV11 systems. <br />
The VSV21 can emulate a minimum-configuration single-channel VSV11 system. <br />
The VSV11 emulation software supports the following VS11/VSV11 features:<br />
<br />
* [[QIO]] format, identical to the VS11<br />
* Main and auxiliary display lists<br />
* The [[FORTRAN]] Draw package<br />
* Joystick control<br />
<br />
These features allow most VS11/VSV11 applications to run on the VSV21 without modification or recompilation.<br />
<br />
{{semi-stub}}<br />
<br />
==See also==<br />
<br />
* [[VSV11 Graphic System]]<br />
<!--<br />
==Further reading==<br />
--><br />
==External links==<br />
<br />
* [http://mim.stupi.net/manuals/layered/vsv4.pdf VSV21 Version 2.0 User Guide] (AZ-FV70B-TC)<br />
* [http://mim.stupi.net/manuals/layered/vsv5.pdf VSV21 Version 2.0 Programmer's Guide] (AA-FV67B-TC)<br />
* [http://mim.stupi.net/manuals/layered/vsv6.pdf VSV21 Programmer's Guide Addendum] (AD-FV67B-T1)<br />
* [http://mim.stupi.net/manuals/layered/vsv2.pdf VSV21 Version 2.0 Installation Manual] (AZ-FV71B-TC)<br />
* [http://mim.stupi.net/manuals/layered/vsv3.pdf VSV21 Version 2.0 Software Installation Guide] (AA-FV66B-TC)<br />
* [http://www.bitsavers.org/www.computer.museum.uq.edu.au/pdf/EK-VSV21-UM-001%20VSV21%20Peripheral%20Concentrator%20User-Installation%20Guide.pdf VSV21 Peripheral Concentrator User/Installation Guide] (EK-VSV21-UM-00l)<br />
* [http://www.bitsavers.org/www.computer.museum.uq.edu.au/pdf/EK-VSV21-PSG-003%20VSV21%20Version%202.0%20Pocket%20Service%20Guide.pdf VSV21 Version 2.0 Pocket Service Guide] (EK-VSV21-PSG-003)<br />
<br />
[[Category: QBUS Display Controllers]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_004_confirm_choice.png&diff=33844
File:VSII-ULT0404 004 confirm choice.png
2024-03-09T08:24:03Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_002b_standalone_ULTRIX_with_choice.png&diff=33843
File:VSII-ULT0404 002b standalone ULTRIX with choice.png
2024-03-09T08:17:30Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=File:VSII-ULT0404_001b_boot_screen_with_boot_command.png&diff=33842
File:VSII-ULT0404 001b boot screen with boot command.png
2024-03-09T08:12:17Z
<p>Vaxorcist: </p>
<hr />
<div></div>
Vaxorcist
https://gunkies.org/w/index.php?title=VAXstation&diff=33834
VAXstation
2024-03-08T07:43:00Z
<p>Vaxorcist: "VAXstation 5xx" links changed to "VAXstation 500 series"</p>
<hr />
<div>A '''VAXstation''' is a [[VAX]]-based [[workstation]] manufactured by [[Digital Equipment Corporation|DEC]]. The very first product with this name, the [[VAXstation 100]], was not VAX-based; it was a programmable [[graphics]] [[terminal]] which attached to the [[UNIBUS]] on a [[host]] computer.<br />
<br />
Another one, the [[VAXstation 500 series|VAXstation 500]] employed the [[Tektronix]] [[4125 Graphics Terminal]] attached to a [[MicroVAX I]]. When the [[MicroVAX II]] came out the same combination was called [[VAXstation 500 series|VAXstation 520]].<br />
<br />
The rest were all independent computers, based on a variety of internal [[bus]] types, starting with the [[QBUS]]. They were often produced by adding a [[bit-mapped display]] to an existing machine to produce a single-user workstation; later ones used a single [[motherboard]], with the [[display]] support built in. [[Ethernet]] was increasingly used to tie them together.<br />
<br />
==QBUS-based VAXstations==<br />
<br />
* [[VAXstation I]]<br />
* [[VAXstation II]]<br />
* [[VAXstation 500 series]]<br />
* [[VAXstation 3200/3500]]<br />
<br />
==Motherboard-based VAXstations==<br />
<br />
* [[VAXstation 2000]]<br />
* [[VAXstation 3100 series]]<br />
* [[VAXstation 4000 series]]<br />
<br />
==Others==<br />
<br />
* [[VAXstation 3520/3540]] - M-bus<br />
* [[VAXstation 8000]] - [[VAX Bus Interconnect|VAXBI]] bus<br />
<br />
==See also==<br />
<br />
* [[:Category: VAXstation Peripherals|VAXstation Peripherals]]<br />
* [[Netbooting a VAXstation]]<br />
<br />
==External links==<br />
<br />
* [http://www.bitsavers.org/pdf/dec/brochures/DEC-VAXstationFamilyOfWorkstations.pdf Digital's VAXstation Family of Workstations]<br />
<br />
[[Category: DEC Graphics Terminals]]<br />
[[Category: VAXen]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=DEC_acronyms&diff=33820
DEC acronyms
2024-03-06T13:06:37Z
<p>Vaxorcist: UWS - ULTRIX Worksystem Software added</p>
<hr />
<div>'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Acronym<br />
! Meaning<br />
|-<br />
| BR<br />
| [[Bus request line|Bus Request]] ([[UNIBUS]])<br />
|-<br />
| CBOX<br />
| Cache Box<br />
|-<br />
| CFS<br />
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])<br />
|-<br />
| CI<br />
| [[Computer Interconnect]]<br />
|-<br />
| CMI<br />
| [[CPU/Memory Interconnect]]<br />
|-<br />
| CRD<br />
| [[Customer Runnable Diagnostic]]<br />
|-<br />
| CSS<br />
| [[Computer Special Systems]]<br />
|-<br />
| DBN<br />
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]<br />
|-<br />
| DCL<br />
| [[Digital Command Language]]<br />
|-<br />
| DCS<br />
| [[Digital Classified Software]]<br />
|-<br />
| DDC<br />
| [[Digital Diagnostic Center]]<br />
|-<br />
| DSA<br />
| [[Digital Storage Architecture]]<br />
|-<br />
| DSC<br />
| [[Disk Save and Compress]]<br />
|-<br />
| DSDF<br />
| [[DSA Standard Disk Format]]<br />
|-<br />
| DSR<br />
| [[Digital Standard Runoff]]<br />
|-<br />
| DSSI<br />
| [[Digital Storage Systems Interconnect]]<br />
|-<br />
| DUP<br />
| [[Diagnostic and Utility Protocol]]<br />
|-<br />
| EBOX<br />
| Execution Box<br />
|-<br />
| ECO<br />
| ''[[Engineering Change Order]]''<br />
|-<br />
| FRU<br />
| [[Field Replacable Unit]]<br />
|-<br />
| IBOX<br />
| Instruction Box<br />
|-<br />
| GPX<br />
| [[Graphics Processing Extension]]<br />
|-<br />
| GIDIS<br />
| [[General Image Display Instruction Set]]<br />
|-<br />
| JBOX<br />
| Junction Box<br />
|-<br />
| LAD<br />
| Local Area Disk<br />
|-<br />
| LAST<br />
| Local Area System Transport<br />
|-<br />
| LAT<br />
| Local Area Transport<br />
|-<br />
| LAVC<br />
| [[Local Area VAXcluster]]<br />
|-<br />
| LBN<br />
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''<br />
|-<br />
| MDM<br />
| [[MicroVAX Diagnostic Monitor]]<br />
|-<br />
| MBOX<br />
| Memory Box<br />
|-<br />
| MCR<br />
| [[Monitor Console Routine]]<br />
|-<br />
| MDS<br />
| [[Maintenance Documentation Service]]<br />
|-<br />
| MSCP<br />
| [[Mass Storage Control Protocol]]<br />
|-<br />
| ODS-2<br />
| [[On-disk Structure 2]]<br />
|-<br />
| OTS<br />
| [[Object Time System]]<br />
|-<br />
| RBN<br />
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]<br />
|-<br />
| RCT<br />
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]<br />
|-<br />
| RDC<br />
| [[Digital Remote Diagnosis Center]]<br />
|-<br />
| RMS<br />
| [[Record Managment Services]]<br />
|-<br />
| SBB<br />
| [[System Building Block]]<br />
|-<br />
| SBI<br />
| [[Synchronous Backplane Interconnect]]<br />
|-<br />
| SCA<br />
| [[Systems Communication Architecture]]<br />
|-<br />
| SCS<br />
| [[Systems Communication Services]]<br />
|-<br />
| SDA<br />
| [[System Dump Analyzer]]<br />
|-<br />
| SDB<br />
| [[Standard Drive Bus]]<br />
|-<br />
| SDI<br />
| [[Standard Disk Interconnect]]<br />
|-<br />
| SDL<br />
| Structure Definition Language<br />
|-<br />
| STI<br />
| [[Standard Tape Interconnect]]<br />
|-<br />
| UETP<br />
| [[User Environment Test Package]]<br />
|-<br />
| UPI<br />
| [[DEC Unique Product Identifier| Unique Product Identifier]]<br />
|-<br />
| UQSSP<br />
| [[UNIBUS]] [[QBUS]] Storage Systems Port<br />
|-<br />
| UWS<br />
| [[ULTRIX Worksystem Software]]<br />
|-<br />
| VAXBI<br />
| [[VAX Bus Interconnect]]<br />
|-<br />
| VBOX<br />
| Vector Box<br />
|-<br />
| VDS / VAX/DS<br />
| [[VAX Diagnostic Supervisor]]<br />
|-<br />
| VUP<br />
| [[VAX Unit of Performance]]<br />
|-<br />
| VWS<br />
| [[VAX Workstation Software]]<br />
|-<br />
| WCS<br />
| [[Writable Control Store]]<br />
|-<br />
| XBN<br />
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]<br />
|-<br />
| XMI<br />
| [[Extended Memory Interconnect]]<br />
|}<br />
<br />
<br />
[[Category: Digital Equipment Corporation]]<br />
[[Category: DEC Acronyms]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=Template:Nav_VAX&diff=33817
Template:Nav VAX
2024-03-04T21:13:40Z
<p>Vaxorcist: VAXstation 500 series added</p>
<hr />
<div>{{PartiallyCollapsibleNavBox<br />
| templateName = Nav VAX<br />
| title = [[VAX]] Computers and Operating Systems<br />
| body = <b>VAX-11/7xx</b> (including VAX 86x0) - [[VAX-11/780]] • [[VAX-11/785]] • [[VAX-11/750]] • [[VAX-11/730]] • [[VAX 8600]] • [[VAX 8650]]<br />
<br />
<b>VAX 8000 series</b> (excluding VAX 86x0) - [[VAX 82xx/83xx series]] • [[VAX 85x0, 8700, 88xx, and 897x systems|VAX 85x0/8700/88xx series]]<br />
<br />
<b>MicroVAXen</b> (many types also come in [[VAXserver]] and [[VAXstation]] models) - [[MicroVAX I]] • [[MicroVAX II]] <br> [[MicroVAX 2000]] • [[MicroVAX 3100 series|MicroVAX 3100]] • [[MicroVAX 3300/3400]] • [[MicroVAX 3500/3600]] • [[MicroVAX 3800/3900]]<br />
<br />
<b>VAXstation Series</b> - [[VAXstation I]] • [[VAXstation II]] • [[VAXstation 500 series]] • [[VAXstation 3100 series|VAXstation 3100]] • [[VAXstation 3200/3500]] • [[VAXstation 3520/3540]] • [[VAXstation 8000]]<br />
<br />
<b>Late Model VAXen</b> - [[VAX 4000 series]] • [[VAX 6000 series]] • [[VAX 7000 series]] • [[VAX 9000 series]] • [[VAX 10000 series]]<br />
<br />
| cbody =<br />
<br />
<b>Special Purpose VAXen</b> - [[VAXft series]] • [[rtVAX series]] • [[Infoserver series]]<br />
<br />
<b>Clones</b> - [[CM 1700]] • [[TPA-11/580]]<br />
<br />
<b>Operating Systems:</b> [[VMS]] • [[VAXELN]] • [[ULTRIX]] • [[BSD on VAX|BSD UNIX]]<br />
<br />
}}</div>
Vaxorcist
https://gunkies.org/w/index.php?title=VAXstation&diff=33816
VAXstation
2024-03-04T21:11:14Z
<p>Vaxorcist: /* QBUS-based VAXstations */ VAXstation 500 series added</p>
<hr />
<div>A '''VAXstation''' is a [[VAX]]-based [[workstation]] manufactured by [[Digital Equipment Corporation|DEC]]. The very first product with this name, the [[VAXstation 100]], was not VAX-based; it was a programmable [[graphics]] [[terminal]] which attached to the [[UNIBUS]] on a [[host]] computer.<br />
<br />
Another one, the [[VAXstation 500]] employed the [[Tektronix]] [[4125 Graphics Terminal]] attached to a [[MicroVAX I]]. When the [[MicroVAX II]] came out the same combination was called [[VAXstation 520]].<br />
<br />
The rest were all independent computers, based on a variety of internal [[bus]] types, starting with the [[QBUS]]. They were often produced by adding a [[bit-mapped display]] to an existing machine to produce a single-user workstation; later ones used a single [[motherboard]], with the [[display]] support built in. [[Ethernet]] was increasingly used to tie them together.<br />
<br />
==QBUS-based VAXstations==<br />
<br />
* [[VAXstation I]]<br />
* [[VAXstation II]]<br />
* [[VAXstation 500 series]]<br />
* [[VAXstation 3200/3500]]<br />
<br />
==Motherboard-based VAXstations==<br />
<br />
* [[VAXstation 2000]]<br />
* [[VAXstation 3100 series]]<br />
* [[VAXstation 4000 series]]<br />
<br />
==Others==<br />
<br />
* [[VAXstation 3520/3540]] - M-bus<br />
* [[VAXstation 8000]] - [[VAX Bus Interconnect|VAXBI]] bus<br />
<br />
==See also==<br />
<br />
* [[:Category: VAXstation Peripherals|VAXstation Peripherals]]<br />
* [[Netbooting a VAXstation]]<br />
<br />
==External links==<br />
<br />
* [http://www.bitsavers.org/pdf/dec/brochures/DEC-VAXstationFamilyOfWorkstations.pdf Digital's VAXstation Family of Workstations]<br />
<br />
[[Category: DEC Graphics Terminals]]<br />
[[Category: VAXen]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=Talk:System_Module&diff=33806
Talk:System Module
2024-03-03T21:07:51Z
<p>Vaxorcist: /* Two meanings of "System Building Block" (SBB) */</p>
<hr />
<div>== Two meanings of "System Building Block" (SBB) ==<br />
<br />
In 1983 the the term "System Building Block" was reused for basic computer system configurations including the CPU, memory and an operating system license. Not included were system devices, load devices, communications interfaces, console terminal, and application software.<br />
We need a disambiguation page here. [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 08:10, 2 March 2024 (CET)<br />
<br />
: Hmmm. The "Digital Dictionary" doesn't include the later one; maybe that use post-dates that volume? The [https://manx-docs.org/collections/mds-199909/cd3/storage/ba350ugc.pdf StorageWorks Family User's Guide] and [https://manx-docs.org/collections/mds-199909/cd3/storage/ba350cge.pdf StorageWorks Solutions Configuration Guide] both give 'SBB' as an expansion for "StorageWorks building blocks"; the [https://manx-docs.org/collections/mds-199909/cd3/storage/350saug1.pdf BA350-SA Modular Storage Shelf User's Guide] does have the "system building blocks" expansion.<br />
: I did a Web search for [https://www.google.com/search?q=%22System+Building+Block%22+dec "System Building Block" DEC], and almost all the hits were for the earlier meaning.<br />
: Nothing links to [[system building block]] (or any variant capitalization of it), so if we want to put a disambiguation page there, that would be easy. [[User:Jnc|Jnc]] ([[User talk:Jnc|talk]]) 23:29, 2 March 2024 (CET)<br />
<br />
:: Up to 1983 DEC mostly sold "Prepackaged Systems" that contained all components for a runnable system: CPU, Memory, System Device, Load Device, Communication Options.<br />
<br />
:: This scheme was somewhat inflexible, so DEC decided to offer "System Building Blocks" consisting only of CPU and memory starting in 1983; the remaining components could be selected and purchased individually.<br />
<br />
:: At the beginning, the additional elements were rarely called “System Building Blocks” until in the 1990s the simliar name "StorageWorks Building Blocks" (also abbreviated to "SBB") became established for the elements of the “StorageWorks” mass storage series.<br />
<br />
:: The term “System Building Blocks” and in particular the acronym “SBB” was used very frequently in the DEC publications “Systems and Options” and “Price List”.<br />
<br />
:: As of now, there are very few documents of this type available from the 1983/84 era, but the [http://bitsavers.org/pdf/datapro/datapro_reports_70s-90s/DEC/M11-384-40_8303_DEC_VAX-11.pdf DATAPRO report from March 1983] explains on page 3 why DEC changed their attitude towards their former system packaging method:<br />
<br />
::: "In a move designed to further simplify their VAX-11 configurations and provide a unique level of user customization for particular systems, DEC has dropped the concept of packaged systems for the VAX-11 family and now provides VAX System Building Blocks (SBBs). SBBs provide a foundation for building customized system configurations. Each SBB (VAX-11/782, VAX-11/780, or VAX-11/750), begins with a core of components: CPU, two or four megabytes of 64K or 16K ECC MOS memory, cabinetry, and the VAX/VMS operating system license. To this core you must add selections from the system device, load device, communications interface, console terminal, and software menus. SBBs give the customer a considerable amount of ordering flexibility because there are many possible equipment combinations. SBBs are currently available for VAX-11/782, VAX-11/780, and VAX-11/750 systems. VAX-11/730 systems are still offered in packaged system configurations. After ordering one of the models below, the customer must then order one from each of the mass storage, communications, and console terminal menus. Selection from the software menu is optional."<br />
<br />
:: The wording "DEC has dropped the concept of packaged systems" is a little too drastic - DEC did not drop it, Dec slowly phased it out over a lot of years.<br />
<br />
:: More recent documents, especially the [http://bitsavers.org/pdf/dec/catalog/ price lists and system and options catalogs at Bitsavers] use the acronym “SBB” very frequently.<br />
<br />
:: So we've certainly got at least two kinds of "System Building Blocks. <br />
<br />
:: By the way: The amount of main memory allocated to both the Prepackaged Systems and the System Building Blocks was chronically too low, probably in order to keep the price as low as possible. [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 22:07, 3 March 2024 (CET)</div>
Vaxorcist
https://gunkies.org/w/index.php?title=DEC_acronyms&diff=33792
DEC acronyms
2024-03-02T07:11:41Z
<p>Vaxorcist: SBB - System Building Block added</p>
<hr />
<div>'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Acronym<br />
! Meaning<br />
|-<br />
| BR<br />
| [[Bus request line|Bus Request]] ([[UNIBUS]])<br />
|-<br />
| CBOX<br />
| Cache Box<br />
|-<br />
| CFS<br />
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])<br />
|-<br />
| CI<br />
| [[Computer Interconnect]]<br />
|-<br />
| CMI<br />
| [[CPU/Memory Interconnect]]<br />
|-<br />
| CRD<br />
| [[Customer Runnable Diagnostic]]<br />
|-<br />
| CSS<br />
| [[Computer Special Systems]]<br />
|-<br />
| DBN<br />
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]<br />
|-<br />
| DCL<br />
| [[Digital Command Language]]<br />
|-<br />
| DCS<br />
| [[Digital Classified Software]]<br />
|-<br />
| DDC<br />
| [[Digital Diagnostic Center]]<br />
|-<br />
| DSA<br />
| [[Digital Storage Architecture]]<br />
|-<br />
| DSC<br />
| [[Disk Save and Compress]]<br />
|-<br />
| DSDF<br />
| [[DSA Standard Disk Format]]<br />
|-<br />
| DSR<br />
| [[Digital Standard Runoff]]<br />
|-<br />
| DSSI<br />
| [[Digital Storage Systems Interconnect]]<br />
|-<br />
| DUP<br />
| [[Diagnostic and Utility Protocol]]<br />
|-<br />
| EBOX<br />
| Execution Box<br />
|-<br />
| ECO<br />
| ''[[Engineering Change Order]]''<br />
|-<br />
| FRU<br />
| [[Field Replacable Unit]]<br />
|-<br />
| IBOX<br />
| Instruction Box<br />
|-<br />
| GPX<br />
| [[Graphics Processing Extension]]<br />
|-<br />
| GIDIS<br />
| [[General Image Display Instruction Set]]<br />
|-<br />
| JBOX<br />
| Junction Box<br />
|-<br />
| LAD<br />
| Local Area Disk<br />
|-<br />
| LAST<br />
| Local Area System Transport<br />
|-<br />
| LAT<br />
| Local Area Transport<br />
|-<br />
| LAVC<br />
| [[Local Area VAXcluster]]<br />
|-<br />
| LBN<br />
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''<br />
|-<br />
| MDM<br />
| [[MicroVAX Diagnostic Monitor]]<br />
|-<br />
| MBOX<br />
| Memory Box<br />
|-<br />
| MCR<br />
| [[Monitor Console Routine]]<br />
|-<br />
| MDS<br />
| [[Maintenance Documentation Service]]<br />
|-<br />
| MSCP<br />
| [[Mass Storage Control Protocol]]<br />
|-<br />
| ODS-2<br />
| [[On-disk Structure 2]]<br />
|-<br />
| OTS<br />
| [[Object Time System]]<br />
|-<br />
| RBN<br />
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]<br />
|-<br />
| RCT<br />
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]<br />
|-<br />
| RDC<br />
| [[Digital Remote Diagnosis Center]]<br />
|-<br />
| RMS<br />
| [[Record Managment Services]]<br />
|-<br />
| SBB<br />
| [[System Building Block]]<br />
|-<br />
| SBI<br />
| [[Synchronous Backplane Interconnect]]<br />
|-<br />
| SCA<br />
| [[Systems Communication Architecture]]<br />
|-<br />
| SCS<br />
| [[Systems Communication Services]]<br />
|-<br />
| SDA<br />
| [[System Dump Analyzer]]<br />
|-<br />
| SDB<br />
| [[Standard Drive Bus]]<br />
|-<br />
| SDI<br />
| [[Standard Disk Interconnect]]<br />
|-<br />
| SDL<br />
| Structure Definition Language<br />
|-<br />
| STI<br />
| [[Standard Tape Interconnect]]<br />
|-<br />
| UETP<br />
| [[User Environment Test Package]]<br />
|-<br />
| UPI<br />
| [[DEC Unique Product Identifier| Unique Product Identifier]]<br />
|-<br />
| UQSSP<br />
| [[UNIBUS]] [[QBUS]] Storage Systems Port<br />
|-<br />
| VAXBI<br />
| [[VAX Bus Interconnect]]<br />
|-<br />
| VBOX<br />
| Vector Box<br />
|-<br />
| VDS / VAX/DS<br />
| [[VAX Diagnostic Supervisor]]<br />
|-<br />
| VUP<br />
| [[VAX Unit of Performance]]<br />
|-<br />
| VWS<br />
| [[VAX Workstation Software]]<br />
|-<br />
| WCS<br />
| [[Writable Control Store]]<br />
|-<br />
| XBN<br />
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]<br />
|-<br />
| XMI<br />
| [[Extended Memory Interconnect]]<br />
|}<br />
<br />
<br />
[[Category: Digital Equipment Corporation]]<br />
[[Category: DEC Acronyms]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=Talk:System_Module&diff=33791
Talk:System Module
2024-03-02T07:10:57Z
<p>Vaxorcist: Created page with "== Two meanings of "System Building Block" (SBB) == In 1983 the the term "System Building Block" was reused for basic computer system configurations including the CPU, memory..."</p>
<hr />
<div>== Two meanings of "System Building Block" (SBB) ==<br />
In 1983 the the term "System Building Block" was reused for basic computer system configurations including the CPU, memory and an operating system license. Not included were system devices, load devices, communications interfaces, console terminal, and application software.<br />
We need a disambiguation page here. [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 08:10, 2 March 2024 (CET)</div>
Vaxorcist
https://gunkies.org/w/index.php?title=Talk:UNIBUS_priority_plug&diff=33641
Talk:UNIBUS priority plug
2024-02-23T13:13:15Z
<p>Vaxorcist: Help to formulate wanted</p>
<hr />
<div>== Help to formulate wanted ==<br />
From time to time I recognize I'm not a native speaker - I'm not content with my formulation (here : sentence about the bus request) and do not know how to do better. Can you help? [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 14:13, 23 February 2024 (CET)</div>
Vaxorcist
https://gunkies.org/w/index.php?title=UNIBUS_priority_plug&diff=33640
UNIBUS priority plug
2024-02-23T13:08:46Z
<p>Vaxorcist: "BR - Bus Request" added</p>
<hr />
<div>A '''UNIBUS priority plug''' is an insertable plug, physically a [[Dual Inline Package|DIP]], which was inserted into almost all [[UNIBUS]] [[peripheral|devices]] in order to select which daisy-chained [[interrupt]] [[bus grant line]], of the four such available on the UNIBUS (BG4, BG5, BG6, and BG7), the device's [[Bus Arbitration on the Unibus and QBUS|grant-acquiring/passing circuitry]] was connected to. As a secondary purpose, it passed all the other grant lines past the device.<br />
<br />
As part of the configuration of a device being added to a system, it was necessary to ensure that a priority plug for the desired priority level was installed in the device.<br />
<br />
Another name for "priority level" was '''bus request''', usually abbreviated to "'''BR'''"; the manuals usually state e.g. '''BR 5''' for priority level 5.<br />
<br />
Priority plugs were manufactured by [[Digital Equipment Corporation|DEC]] for all four priority levels:<br />
<br />
{| class="wikitable"<br />
! Level !! [[DEC part number]]<br />
|-<br />
| 4 || 54-08776<br />
|-<br />
| 5 || 54-08778<br />
|-<br />
| 6 || 54-08780<br />
|-<br />
| 7 || 54-08782<br />
|}<br />
<br />
Most devices also came with a plug pre-installed at manufacturing time, at a level selected by DEC as likely the most appropriate interrupt priority level for that device; they were rarely changed.<br />
<br />
[[Category: UNIBUS]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=UNIBUS_priority_plug&diff=33637
UNIBUS priority plug
2024-02-23T11:28:01Z
<p>Vaxorcist: Missing part numbers added</p>
<hr />
<div>A '''UNIBUS priority plug''' is an insertable plug, physically a [[Dual Inline Package|DIP]], which was inserted into almost all [[UNIBUS]] [[peripheral|devices]] in order to select which daisy-chained [[interrupt]] [[bus grant line]], of the four such available on the UNIBUS (BG4, BG5, BG6, and BG7), the device's [[Bus Arbitration on the Unibus and QBUS|grant-acquiring/passing circuitry]] was connected to. As a secondary purpose, it passed all the other grant lines past the device.<br />
<br />
As part of the configuration of a device being added to a system, it was necessary to ensure that a priority plug for the desired priority level was installed in the device.<br />
<br />
Priority plugs were manufactured by [[Digital Equipment Corporation|DEC]] for all four priority levels:<br />
<br />
{| class="wikitable"<br />
! Level !! [[DEC part number]]<br />
|-<br />
| 4 || 54-08776<br />
|-<br />
| 5 || 54-08778<br />
|-<br />
| 6 || 54-08780<br />
|-<br />
| 7 || 54-08782<br />
|}<br />
<br />
Most devices also came with a plug pre-installed at manufacturing time, at a level selected by DEC as likely the most appropriate interrupt priority level for that device; they were rarely changed.<br />
<br />
[[Category: UNIBUS]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=DEC_Software-related_Order_Codes&diff=33636
DEC Software-related Order Codes
2024-02-23T11:24:51Z
<p>Vaxorcist: /* 7-Character Format XXXXX-XX */ Some more codes added</p>
<hr />
<div>DEC Software Media, Software License, Software Service, and Software Manual Order Codes <br />
<br />
== 7-Character Format XXXXX-XX ==<br />
<br />
Samples: <br />
*ZYA06-P3 MicroPDP-11 RX33 Formatter Kit<br />
*<br />
<br />
'''1st Letter = Type of Software''':<br />
*Y - [[Computer Special Systems]] Software<br />
*Z - Diagnostics<br />
*Q - System and Application Software<br />
<br />
'''2nd Letter = Processor Identifier''':<br />
*0 - [[MicroVAX]]/[[VAXserver]] 3500 and 3600<br />
*1 - MicroVAX/VAXserver 3500 and 3600/[[VAXstation]] 3200 and 3500<br />
*2 - [[VAX 8700]] and [[VAX 8550]]<br />
*3 - [[MicroVAX 2000]]<br />
*4 - [[VAXstation II]]<br />
*5 - [[VAX 8200]] and [[VAX 8250]]<br />
*6 - [[VAXmate]]<br />
*7 - [[VAX 8300]] and [[VAX 8350]]<br />
*8 - [[VAXstation 2000]]<br />
*9 - [[VAX 8500]] and [[VAX 8530]]<br />
*A - [[Digital Classified Software]], USA<br />
*B - [[Professional 300 Series]]<br />
*C - [[VAX-11/725]] and [[VAX-11/730]]<br />
*D - [[VAX-11/750]]<br />
*E - [[VAX-11/780]], [[VAX-11/782]], and [[VAX-11/785]]<br />
*F - [[PDP-8]], [[WPS-8]], [[DECmate I]]<br />
*G - Digital Classified Software, Internal<br />
*H - [[DECsystem 10]]<br />
*I - Digital Classified Software, GIA<br />
*J - [[PDP-11]] [[UNIBUS]]-based ([[RT-11]], [[ULTRIX-11]])<br />
*K - [[VAX 8600]] and [[VAX 8650]]<br />
*L - All Models<br />
*M - [[VAX 8800]], [[VAX 8974]], and [[VAX 8978]]<br />
*N - [[MicroVAX I]]<br />
*P - PDP-11 ([[RSTS]])<br />
*Q - [[VAXstation I]]<br />
*R - PDP-11 ([[RSX-11M]]/[[RSX-11M-PLUS]])<br />
*S - Software<br />
*T - [[DECsystem 20]]<br />
*U - Digital Classified Software, Europe<br />
*V - [[Rainbow]]<br />
*W - [[DECmate II]]<br />
*X - Cross prod, and/or no support services<br />
*Y - [[MicroPDP-11]] [[QBUS]]-based<br />
*Z - [[MicroVAX II]]<br />
<br />
'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br><br />
:Exception: Digital Classified Software, 2nd letter = A, G, I, U<br />
<br />
'''6th Letter = Product Type''':<br />
*3 - Self-Maintenance Service<br />
*7 - Startup Service Level II<br />
*8 - Basic Service<br />
*9 - DECsupport Service<br />
*A - License and Software Media?<br />
*B - Startup Service Level III<br />
*C - License and Key, no Support<br />
*D - License only<br />
*E - Source License and Distribution<br />
*F - Source Distribution and Listings / Microfiche<br />
*G - Documentation Only (-GZ)<br />
*H - Distribution and Documentation<br />
*I - Installation Service<br />
*N - Source Distribution<br />
*P - No License, Binaries only<br />
*R - No License, Binaries Documentation<br />
*S - DECstart Service<br />
*T - Update<br />
*U - Single-Use License<br />
*W - Warranty Update<br />
<br />
<br />
'''7th Letter = Software Medium''':<br />
*2 - [[RX180]]<br />
*3 - [[RX50]]<br />
*4 - [[RC25]]<br />
*5 - [[TK50]]<br />
*6 - [[TK25]]<br />
*7 - [[RX33]]<br />
*8 - [[CDROM]]<br />
*A - [[Magnetic tape|9-Track Tape 6250 BPI]] / [[LINC tape]]<br />
*B - [[Paper Tape]] / [[RX24]]<br />
*C - [[DECtape]] / [[RX23]]<br />
*D - [[Magnetic tape|9-Track Tape 800 BPI 600ft]]<br />
*E - [[RK03]] / [[RK05]]<br />
*F - [[Magnetic tape|7-Track Tape]]<br />
*G - [[TU58]]<br />
*H - [[RL02]]<br />
*I - [[RX31]]<br />
*J - [[RA60]]<br />
*K - [[RP04]]<br />
*L - [[RP06]]<br />
*M - [[Magnetic tape|9-Track Tape 1600 BPI 2400ft]]<br />
*P - Cassette Tape ([[QIC]], [[DAT]], ...) / [[Magnetic tape|9 Track Magtape 800 BPI 2400ft]]<br />
*Q - [[RL01]]<br />
*R - [[Microfiche]]<br />
*S - [[ROM]]<br />
*T - [[RK06]]<br />
*V - [[RK07]]<br />
*W - Multimedia<br />
*X - [[RX02]]<br />
*Y - [[RX01]]<br />
*Z - No Hardware Dependency / Paper<br />
<br />
== 9-Character Format XX-XXXXX-XX ==<br />
<br />
With the advent of VMS V5 and as new VAX processors were introduced, the Software Products and Services used the new Software Model Number, a 9-character format.<br />
<br />
=== Cluster Licensing ===<br />
<br />
Samples: <br />
*<br />
*<br />
<br />
'''1st and 2nd Letter = Unknown (usually "QL")'''<br />
<br />
'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br />
<br />
'''6th and 7th Letter = CC (Country Code):'''<br />
*A9 - <br />
*GA - Germany<br />
<br />
'''8th and 9th Letter = Cluster License Points:'''<br />
*JB - 10<br />
*JC - 20<br />
*JD - 50<br />
*JE - 100<br />
*JF - 200<br />
*JG - 300<br />
*JH - 400<br />
*JJ - 600<br />
*JK - 900<br />
*JL - 1200<br />
*JM - 1800<br />
*JN - 2400<br />
*JS - 4800<br />
*JV - 9000<br />
<br />
=== CPU Licensing ===<br />
<br />
Samples: <br />
*QL-056AF-AA<br />
*<br />
<br />
'''1st and 2nd Letter = Unknown (usually "QL")'''<br />
<br />
'''3rd to 5th Letter = [[DEC Unique Product Identifier| Unique Product Identifier]] (UPI)'''<br />
<br />
'''6th Letter = Unknown (usually "A" or "G")'''<br />
<br />
'''7th Letter = CPU Code:'''<br />
*B - MicroVAX 3500, 3600<br />
*C - VAXstation 3200, 3500, 8000<br />
*D - VAX 8800, 6240, 8820<br />
*E - VAX 8550, 8700, 8810<br />
*F - VAX 8600, 8650<br />
*G - VAX 8530<br />
*H - VAX 8300, 8350<br />
*J - VAX 8200, 11/782<br />
*K - VAX-11/780, 11/785 <br />
*L - VAX-11/750<br />
*M - VAX-11/730, 11/725<br />
*N - MicroVAX II<br />
*P - MicroVAX 2000<br />
*Q - VAXstation II<br />
*R - VAXstation 2000<br />
*S - MicroVAX 3300, 3400<br />
*U - VAX 8830, 8842<br />
*V - VAX 8840<br />
*2 - VAX 6210<br />
*3 - VAX 6220<br />
*4 - VAX 6230<br />
<br />
'''8th and 9th Letter = Unknown (usually "AA")'''<br />
<br />
== External References ==<br />
<br />
*AA-5074O-RK System Software Information<br />
*IAS 3.4A SPD<br />
*EE-26108-68-84 DIGITAL Microcomponents Products U.S. Price List October-December 1984<br />
*EE-18587-04-80 PDP-11, VAX-11 Price List April - September 1980<br />
*ED PDP Systems and Options Catalog 1988<br />
<br />
[[Category: Digital Equipment Corporation]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=DEC_acronyms&diff=33622
DEC acronyms
2024-02-22T17:30:11Z
<p>Vaxorcist: "BR - Bus Request" added</p>
<hr />
<div>'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Acronym<br />
! Meaning<br />
|-<br />
| BR<br />
| [[Bus request line|Bus Request]] ([[UNIBUS]])<br />
|-<br />
| CBOX<br />
| Cache Box<br />
|-<br />
| CFS<br />
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])<br />
|-<br />
| CI<br />
| [[Computer Interconnect]]<br />
|-<br />
| CMI<br />
| [[CPU/Memory Interconnect]]<br />
|-<br />
| CRD<br />
| [[Customer Runnable Diagnostic]]<br />
|-<br />
| CSS<br />
| [[Computer Special Systems]]<br />
|-<br />
| DBN<br />
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]<br />
|-<br />
| DCL<br />
| [[Digital Command Language]]<br />
|-<br />
| DCS<br />
| [[Digital Classified Software]]<br />
|-<br />
| DDC<br />
| [[Digital Diagnostic Center]]<br />
|-<br />
| DSA<br />
| [[Digital Storage Architecture]]<br />
|-<br />
| DSC<br />
| [[Disk Save and Compress]]<br />
|-<br />
| DSDF<br />
| [[DSA Standard Disk Format]]<br />
|-<br />
| DSR<br />
| [[Digital Standard Runoff]]<br />
|-<br />
| DSSI<br />
| [[Digital Storage Systems Interconnect]]<br />
|-<br />
| DUP<br />
| [[Diagnostic and Utility Protocol]]<br />
|-<br />
| EBOX<br />
| Execution Box<br />
|-<br />
| ECO<br />
| ''[[Engineering Change Order]]''<br />
|-<br />
| FRU<br />
| [[Field Replacable Unit]]<br />
|-<br />
| IBOX<br />
| Instruction Box<br />
|-<br />
| GPX<br />
| [[Graphics Processing Extension]]<br />
|-<br />
| GIDIS<br />
| [[General Image Display Instruction Set]]<br />
|-<br />
| JBOX<br />
| Junction Box<br />
|-<br />
| LAD<br />
| Local Area Disk<br />
|-<br />
| LAST<br />
| Local Area System Transport<br />
|-<br />
| LAT<br />
| Local Area Transport<br />
|-<br />
| LAVC<br />
| [[Local Area VAXcluster]]<br />
|-<br />
| LBN<br />
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''<br />
|-<br />
| MDM<br />
| [[MicroVAX Diagnostic Monitor]]<br />
|-<br />
| MBOX<br />
| Memory Box<br />
|-<br />
| MCR<br />
| [[Monitor Console Routine]]<br />
|-<br />
| MDS<br />
| [[Maintenance Documentation Service]]<br />
|-<br />
| MSCP<br />
| [[Mass Storage Control Protocol]]<br />
|-<br />
| ODS-2<br />
| [[On-disk Structure 2]]<br />
|-<br />
| OTS<br />
| [[Object Time System]]<br />
|-<br />
| RBN<br />
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]<br />
|-<br />
| RCT<br />
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]<br />
|-<br />
| RDC<br />
| [[Digital Remote Diagnosis Center]]<br />
|-<br />
| RMS<br />
| [[Record Managment Services]]<br />
|-<br />
| SBI<br />
| [[Synchronous Backplane Interconnect]]<br />
|-<br />
| SCA<br />
| [[Systems Communication Architecture]]<br />
|-<br />
| SCS<br />
| [[Systems Communication Services]]<br />
|-<br />
| SDA<br />
| [[System Dump Analyzer]]<br />
|-<br />
| SDB<br />
| [[Standard Drive Bus]]<br />
|-<br />
| SDI<br />
| [[Standard Disk Interconnect]]<br />
|-<br />
| SDL<br />
| Structure Definition Language<br />
|-<br />
| STI<br />
| [[Standard Tape Interconnect]]<br />
|-<br />
| UETP<br />
| [[User Environment Test Package]]<br />
|-<br />
| UPI<br />
| [[DEC Unique Product Identifier| Unique Product Identifier]]<br />
|-<br />
| UQSSP<br />
| [[UNIBUS]] [[QBUS]] Storage Systems Port<br />
|-<br />
| VAXBI<br />
| [[VAX Bus Interconnect]]<br />
|-<br />
| VBOX<br />
| Vector Box<br />
|-<br />
| VDS / VAX/DS<br />
| [[VAX Diagnostic Supervisor]]<br />
|-<br />
| VUP<br />
| [[VAX Unit of Performance]]<br />
|-<br />
| VWS<br />
| [[VAX Workstation Software]]<br />
|-<br />
| WCS<br />
| [[Writable Control Store]]<br />
|-<br />
| XBN<br />
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]<br />
|-<br />
| XMI<br />
| [[Extended Memory Interconnect]]<br />
|}<br />
<br />
<br />
[[Category: Digital Equipment Corporation]]<br />
[[Category: DEC Acronyms]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=DEC_acronyms&diff=33606
DEC acronyms
2024-02-20T07:25:47Z
<p>Vaxorcist: "CRD - Customer Runnable Diagnostic" added</p>
<hr />
<div>'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Acronym<br />
! Meaning<br />
|-<br />
| CBOX<br />
| Cache Box<br />
|-<br />
| CFS<br />
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])<br />
|-<br />
| CI<br />
| [[Computer Interconnect]]<br />
|-<br />
| CMI<br />
| [[CPU/Memory Interconnect]]<br />
|-<br />
| CRD<br />
| [[Customer Runnable Diagnostic]]<br />
|-<br />
| CSS<br />
| [[Computer Special Systems]]<br />
|-<br />
| DBN<br />
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]<br />
|-<br />
| DCL<br />
| [[Digital Command Language]]<br />
|-<br />
| DCS<br />
| [[Digital Classified Software]]<br />
|-<br />
| DDC<br />
| [[Digital Diagnostic Center]]<br />
|-<br />
| DSA<br />
| [[Digital Storage Architecture]]<br />
|-<br />
| DSC<br />
| [[Disk Save and Compress]]<br />
|-<br />
| DSDF<br />
| [[DSA Standard Disk Format]]<br />
|-<br />
| DSR<br />
| [[Digital Standard Runoff]]<br />
|-<br />
| DSSI<br />
| [[Digital Storage Systems Interconnect]]<br />
|-<br />
| DUP<br />
| [[Diagnostic and Utility Protocol]]<br />
|-<br />
| EBOX<br />
| Execution Box<br />
|-<br />
| ECO<br />
| ''[[Engineering Change Order]]''<br />
|-<br />
| FRU<br />
| [[Field Replacable Unit]]<br />
|-<br />
| IBOX<br />
| Instruction Box<br />
|-<br />
| GPX<br />
| [[Graphics Processing Extension]]<br />
|-<br />
| GIDIS<br />
| [[General Image Display Instruction Set]]<br />
|-<br />
| JBOX<br />
| Junction Box<br />
|-<br />
| LAD<br />
| Local Area Disk<br />
|-<br />
| LAST<br />
| Local Area System Transport<br />
|-<br />
| LAT<br />
| Local Area Transport<br />
|-<br />
| LAVC<br />
| [[Local Area VAXcluster]]<br />
|-<br />
| LBN<br />
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''<br />
|-<br />
| MDM<br />
| [[MicroVAX Diagnostic Monitor]]<br />
|-<br />
| MBOX<br />
| Memory Box<br />
|-<br />
| MCR<br />
| [[Monitor Console Routine]]<br />
|-<br />
| MDS<br />
| [[Maintenance Documentation Service]]<br />
|-<br />
| MSCP<br />
| [[Mass Storage Control Protocol]]<br />
|-<br />
| ODS-2<br />
| [[On-disk Structure 2]]<br />
|-<br />
| OTS<br />
| [[Object Time System]]<br />
|-<br />
| RBN<br />
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]<br />
|-<br />
| RCT<br />
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]<br />
|-<br />
| RDC<br />
| [[Digital Remote Diagnosis Center]]<br />
|-<br />
| RMS<br />
| [[Record Managment Services]]<br />
|-<br />
| SBI<br />
| [[Synchronous Backplane Interconnect]]<br />
|-<br />
| SCA<br />
| [[Systems Communication Architecture]]<br />
|-<br />
| SCS<br />
| [[Systems Communication Services]]<br />
|-<br />
| SDA<br />
| [[System Dump Analyzer]]<br />
|-<br />
| SDB<br />
| [[Standard Drive Bus]]<br />
|-<br />
| SDI<br />
| [[Standard Disk Interconnect]]<br />
|-<br />
| SDL<br />
| Structure Definition Language<br />
|-<br />
| STI<br />
| [[Standard Tape Interconnect]]<br />
|-<br />
| UETP<br />
| [[User Environment Test Package]]<br />
|-<br />
| UPI<br />
| [[DEC Unique Product Identifier| Unique Product Identifier]]<br />
|-<br />
| UQSSP<br />
| [[UNIBUS]] [[QBUS]] Storage Systems Port<br />
|-<br />
| VAXBI<br />
| [[VAX Bus Interconnect]]<br />
|-<br />
| VBOX<br />
| Vector Box<br />
|-<br />
| VDS / VAX/DS<br />
| [[VAX Diagnostic Supervisor]]<br />
|-<br />
| VUP<br />
| [[VAX Unit of Performance]]<br />
|-<br />
| VWS<br />
| [[VAX Workstation Software]]<br />
|-<br />
| WCS<br />
| [[Writable Control Store]]<br />
|-<br />
| XBN<br />
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]<br />
|-<br />
| XMI<br />
| [[Extended Memory Interconnect]]<br />
|}<br />
<br />
<br />
[[Category: Digital Equipment Corporation]]<br />
[[Category: DEC Acronyms]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=DEC_acronyms&diff=33561
DEC acronyms
2024-02-18T08:28:56Z
<p>Vaxorcist: MDM added</p>
<hr />
<div>'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Acronym<br />
! Meaning<br />
|-<br />
| CBOX<br />
| Cache Box<br />
|-<br />
| CFS<br />
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])<br />
|-<br />
| CI<br />
| [[Computer Interconnect]]<br />
|-<br />
| CMI<br />
| [[CPU/Memory Interconnect]]<br />
|-<br />
| CSS<br />
| [[Computer Special Systems]]<br />
|-<br />
| DBN<br />
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]<br />
|-<br />
| DCL<br />
| [[Digital Command Language]]<br />
|-<br />
| DCS<br />
| [[Digital Classified Software]]<br />
|-<br />
| DDC<br />
| [[Digital Diagnostic Center]]<br />
|-<br />
| DSA<br />
| [[Digital Storage Architecture]]<br />
|-<br />
| DSC<br />
| [[Disk Save and Compress]]<br />
|-<br />
| DSDF<br />
| [[DSA Standard Disk Format]]<br />
|-<br />
| DSR<br />
| [[Digital Standard Runoff]]<br />
|-<br />
| DSSI<br />
| [[Digital Storage Systems Interconnect]]<br />
|-<br />
| DUP<br />
| [[Diagnostic and Utility Protocol]]<br />
|-<br />
| EBOX<br />
| Execution Box<br />
|-<br />
| ECO<br />
| ''[[Engineering Change Order]]''<br />
|-<br />
| FRU<br />
| [[Field Replacable Unit]]<br />
|-<br />
| IBOX<br />
| Instruction Box<br />
|-<br />
| GPX<br />
| [[Graphics Processing Extension]]<br />
|-<br />
| GIDIS<br />
| [[General Image Display Instruction Set]]<br />
|-<br />
| JBOX<br />
| Junction Box<br />
|-<br />
| LAD<br />
| Local Area Disk<br />
|-<br />
| LAST<br />
| Local Area System Transport<br />
|-<br />
| LAT<br />
| Local Area Transport<br />
|-<br />
| LAVC<br />
| [[Local Area VAXcluster]]<br />
|-<br />
| LBN<br />
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''<br />
|-<br />
| MDM<br />
| [[MicroVAX Diagnostic Monitor]]<br />
|-<br />
| MBOX<br />
| Memory Box<br />
|-<br />
| MCR<br />
| [[Monitor Console Routine]]<br />
|-<br />
| MDS<br />
| [[Maintenance Documentation Service]]<br />
|-<br />
| MSCP<br />
| [[Mass Storage Control Protocol]]<br />
|-<br />
| ODS-2<br />
| [[On-disk Structure 2]]<br />
|-<br />
| OTS<br />
| [[Object Time System]]<br />
|-<br />
| RBN<br />
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]<br />
|-<br />
| RCT<br />
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]<br />
|-<br />
| RDC<br />
| [[Digital Remote Diagnosis Center]]<br />
|-<br />
| RMS<br />
| [[Record Managment Services]]<br />
|-<br />
| SBI<br />
| [[Synchronous Backplane Interconnect]]<br />
|-<br />
| SCA<br />
| [[Systems Communication Architecture]]<br />
|-<br />
| SCS<br />
| [[Systems Communication Services]]<br />
|-<br />
| SDA<br />
| [[System Dump Analyzer]]<br />
|-<br />
| SDB<br />
| [[Standard Drive Bus]]<br />
|-<br />
| SDI<br />
| [[Standard Disk Interconnect]]<br />
|-<br />
| SDL<br />
| Structure Definition Language<br />
|-<br />
| STI<br />
| [[Standard Tape Interconnect]]<br />
|-<br />
| UETP<br />
| [[User Environment Test Package]]<br />
|-<br />
| UPI<br />
| [[DEC Unique Product Identifier| Unique Product Identifier]]<br />
|-<br />
| UQSSP<br />
| [[UNIBUS]] [[QBUS]] Storage Systems Port<br />
|-<br />
| VAXBI<br />
| [[VAX Bus Interconnect]]<br />
|-<br />
| VBOX<br />
| Vector Box<br />
|-<br />
| VDS / VAX/DS<br />
| [[VAX Diagnostic Supervisor]]<br />
|-<br />
| VUP<br />
| [[VAX Unit of Performance]]<br />
|-<br />
| VWS<br />
| [[VAX Workstation Software]]<br />
|-<br />
| WCS<br />
| [[Writable Control Store]]<br />
|-<br />
| XBN<br />
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]<br />
|-<br />
| XMI<br />
| [[Extended Memory Interconnect]]<br />
|}<br />
<br />
<br />
[[Category: Digital Equipment Corporation]]<br />
[[Category: DEC Acronyms]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=VAX&diff=33560
VAX
2024-02-18T08:25:12Z
<p>Vaxorcist: /* See also */ "Category:VAX Software" added</p>
<hr />
<div>'''VAX''' is the name (short for 'Virtual Address eXtension') for a family of computers from [[Digital Equipment Corporation|DEC]]. They were the successors to the [[PDP-11]] series of [[minicomputer]]s.<br />
<br />
==Operating Systems==<br />
<br />
The following Operating Systems are known to run on the VAX.<br />
<br />
*[[VMS]]<br />
*[[Unix/32V]]<br />
*[[BSD]]<br />
*[[Ultrix]]<br />
*[[NetBSD]]<br />
*[[OpenBSD]]<br />
*[[OracleDB]]<br />
<br />
==Diagnostic Software==<br />
<br />
There are two kinds of diagnostic software for VAX computers:<br />
<br />
* [[MicroVAX Diagnostic Monitor]] for all [[MicroVAX]] computers (except for the [[MicroVAX I]])<br />
* [[VAX Diagnostic Supervisor]] for all other VAX models<br />
<br />
==Simulators==<br />
<br />
There are 2 well known simulators for the VAX:<br />
<br />
*[[SIMH]]<br />
*[[CharonVAX]]<br />
<br />
==New Emulator Hardware==<br />
<br />
* [[UniBone/QBone]]<br />
<br />
==Russian Clones==<br />
<br />
[https://translate.google.fr/translate?sl=cs&tl=en&js=y&prev=_t&hl=en&ie=UTF-8&u=http%3A%2F%2Fwww.root.cz%2Fclanky%2Fpdp-11-a-smep-system-malych-elektronickych-pocitacu%2F&edit-text=&act=url SMEP minicomputer series]<br />
<br />
==See also==<br />
<br />
* [[MicroVAX]]<br />
* [[VAXserver]]<br />
* [[VAXstation]]<br />
* [[VAXcluster]]<br />
* [[:Category:VAXen|VAXen]]<br />
* [[:Category:DEC VAX systems|DEC VAX systems]]<br />
* [[VAX CPUs, Modules, Part Numbers and Firmware]]<br />
* [[:Category:VAX Software|VAX Software]]<br />
<br />
==External links==<br />
<br />
* [http://www.bitsavers.org/pdf/dec/vax/ VAX] - documentation at [[Bitsavers]]<br />
* [http://www.bitsavers.org/pdf/dec/vax/handbook/VAX_Hardware_Handbook_Volume_1_1986.pdf VAX Hardware Handbook Volume 1]<br />
* [http://www.bitsavers.org/pdf/dec/vax/handbook/VAX_Hardware_Handbook_Volume_2_1986.pdf VAX Hardware Handbook Volume 2]<br />
* [http://www.vaxarchive.org/ VAXarchive]<br />
* [http://simh.trailing-edge.com/docs/vax_proc.txt Processor charts]<br />
* [http://www.bitsavers.org/pdf/dec/pdp11/memos/740913_Summary_Of_11_VAX_Architecture.pdf Summary of 11/VAX Architecture] - an interesting insight into very early (September, 1974) thinking<br />
* [http://gordonbell.azurewebsites.net/Digital/VAX%20Strategy%20c1979.pdf Basic Product Strategy] - Bell's original strategy document (November,1978) on the VAX<br />
* [https://gordonbell.azurewebsites.net/Digital/Strecker%20Bell%20PDP-11%20VAX%20Alpha%20Retrospective.pdf What Have We Learned from the PDF’-11 - What We Have Learned from VAX and Alpha]<br />
* [https://gordonbell.azurewebsites.net/Digital/Bell_Retrospective_PDP11_paper_c1998.htm A Retrospective on What We Have Learned From the PDP-11: What Else Did We Need to Know That Could Have Been Useful in the Design of the VAX-11 to Make Alpha Easier?]<br />
* [http://9p.io/cm/cs/who/dmr/vax1.html JFO (Joe Ossanna) Notes on 32-bit VAX]<br />
<br />
{{Nav VAX}}<br />
<br />
[[Category: DEC Architectures]]<br />
[[Category: VAXen]]<br />
[[Category: 32-bit Computers]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=VAX_Diagnostic_Supervisor&diff=33559
VAX Diagnostic Supervisor
2024-02-18T08:20:49Z
<p>Vaxorcist: Added a LOT of details</p>
<hr />
<div>VDS - '''VAX Diagnostic Supervisor''' (sometimes abbreviated to VAX/DS) is a set of diagnostic software programs for the [[DEC]] [[VAX]] computers and peripheral devices.<br />
<br />
== Intro ==<br />
<br />
'''''"At best, a computer is as good as its diagnostic tools!"'''''<br />
<br />
That's what they must have thought at DEC when they developed their diagnostic software.<br />
<br />
Here we will take a closer look at the VAX Diagnostic Supervisor and also a quick side look at the [[User Environment Test Package]] (UETP).<br />
<br />
== Using VDS for simulated VAX Computers ==<br />
<br />
You may ask: "What are the VAX diagnostics good for when run on a simulated VAX?"<br />
<br />
Yes, many diagnostics do not run on a simulated VAX, but some work very well and are used e.g. for testing the various [[SIMH]] VAX simulators for correct execution of the VAX native mode instructions.<br />
<br />
Furthermore you can explore how precise the simulation mimics the real hardware.<br />
<br />
If you plan to test your real VAX, you can familiarize yourself with VDS and prepare your diagnosis in SIMH, and SIMH can assist you in preparing and creating a diagnostic kit on media appropriate for your VAX.<br />
<br />
Automated testing script for a SIMH VAX-11/750:<br />
<br />
SET CLOCK NOCALIBRATE=600K<br />
ATTACH -RQ RQ0 VAX_MINIMUM_DIAGS.dsk<br />
EXPECT "DS> " SEND "ATTACH UDA50 DW0 DUA 772150 154 5 10\r"; GO -Q<br />
EXPECT "DS> " SEND "ATTACH RA81 DUA DUA0\r"; GO -Q<br />
EXPECT "DS> " SEND "ATTACH KA750 CMI KA0 yes yes yes 0 0\r"; GO -Q<br />
EXPECT "DS> " SEND "ATTACH DW750 CMI DW0 8\r"; GO -Q<br />
EXPECT "DS> " SEND "SET LOAD DUA0:[SYSMAINT]\r"; GO -Q<br />
EXPECT "DS> " SEND "SELECT KA0\r"; GO -Q<br />
EXPECT "DS> " SEND "SET FLAGS TRACE\r"; GO -Q<br />
EXPECT "DS> " SEND "RUN EVKAB\r"; GO -Q<br />
BOOT -Q RQ0 /R5:10<br />
<br />
== VDS History ==<br />
<br />
VDS development began in parallel that to the first [[VAX]] model, the [[VAX-11/780]] in 1977.<br />
<br />
VDS was provided soley for the '''''"big VAXen"''''' (i.e. not for the [[MicroVAX]] and [[VAXstation]] computers), with one remarkable exception, the [[MicroVAX I]], resp. [[VAXstation I]].<br />
Each new VAX model received its CPU-specific VDS modules up to the [[VAX 9000]]; only the VAX models of the last two series, [[VAX 7000]] and [[VAX 10000]], were covered by other diagnostic methods.<br />
<br />
== Program Levels ==<br />
<br />
All VAX diagnostic programs are assigned to a '''level'''. Levels are numbered 1, 2R, 2, 3, 4, and 5. A program’s level indicates its run-time environment.<br />
<br />
* '''Level 1''' diagnostic programs run under an operating system. They do not use the VAX/DS. (=> UETP)<br />
* '''Level 2R''' diagnostic programs run under VAX/DS in user mode only.<br />
* '''Level 2''' diagnostic programs run in both user mode and standalone mode, under the control of the VAX/DS.<br />
* '''Level 3''' diagnostic programs run only in standalone mode, under the control of the VAX/DS.<br />
* '''Level 4''' diagnostic programs run in standalone without VAX/DS.<br />
* '''level 5''' diagnostic programs run in [[Writable Control Store|WCS]] or system console, not in VAX main memory. They do not use the VAX/DS.<br />
<br />
Only the levels 2R, 2, and 3 are managed by VDS.<br />
<br />
== Sections, Tests, Subtests, and Flags ==<br />
<br />
All diagnostic programs that run under the VAX/DS are composed of one or more '''sections'''. Each section has a name, and it is possible to specify, by name, which section of the program to execute. A program section can have one of two functions, depending on its design:<br />
<br />
* Test a certain major portion of the unit under test.<br />
* Facilitate a certain mode of testing. For example, there might be a quick-verify section, used to give the device a quick (but not thorough) test.<br />
<br />
In order to determine the number and names of the sections in a particular diagnostic program, use the <code>SHOW SECTIONS</code> command. However, every program contains a default section called <code>DEFAULT</code>, which will execute automatically if you do not specifically select a section. A section is selected with the <code>/SECTION</code> qualifier on the <code>RUN</code> or <code>START</code> command.<br />
<br />
Each section is composed of a set of '''tests'''; each test verifies either a particular function of the hardware or a particular subset of the component logic being tested. The VAX/DS allows you to specify which tests within a section to run. Each test may have some '''subtests'''. Tests are selected with the <code>/TEST</code> qualifier on the <code>RUN</code> or <code>START</code> command.<br />
<br />
Two sets of '''flags''' are provided to control certain aspects of a diagnostic program’s execution. These flags may be set or cleared before the diagnostic program is started.<br />
<br />
One set of flags is called the '''VAX/DS control flags'''. The flags in this set are interpreted by the VAX/DS and their meanings are the same in all diagnostic programs. The VAX/DS control flags are set with the <code>SET FLAGS</code> command.<br />
<br />
The other set of flags is referred to as the '''event flags'''. This set consists of 23 flags whose purposes are defined by the diagnostic programs. The user must read the documentation for specific diagnostic programs to determine if a definition has been assigned to any of the event flags. <code>SET EVENT FLAGS</code> command.<br />
<br />
== Diagnostic Program Documentation ==<br />
<br />
Documentation provided for each diagnostic program includes:<br />
<br />
* '''Help file'''<br />
:: The help file is referenced with the HELP command. It contains any operating instructions that may be unique to the diagnostic program. The help file for diagnostic program EVXYZ is EVXYZ.HLP; the help file for the VAX/DS is EVSAA.HLP<br />
<br />
* '''Documentation file''' <br />
:: The documentation file provides a detailed description of a diagnostic program's function, run-time requirements, operating instructions, fault detection, and maintenance history, plus explanations of each test’s function and execution flow. The documentation file for diagnostic program EVXYZ is EVXYZ.DOC.<br />
<br />
* '''Source Code listings'''<br />
:: Source code listings of the diagnostic programs are available. All VAX/DS diagnostic programs are structured in a standard format. For example, the initialization code for every diagnostic program is always located in the same relative area within the listing. To fully understand the source code listings of a VAX/DS diagnostic program, refer to the VAX Diagnostic Design Guide.<br />
<br />
The help file for a diagnostic program is shipped with the diagnostic program. The documentation file and source codelistings are available by ordering a [[Maintenance Documentation Service]] Option on microfiche.<br />
<br />
== Diagnostic Scopes ==<br />
<br />
There are two diagnostic scopes.<br />
<br />
* A CPU-specific scope: '''CPU Cluster Testing'''<br />
* A scope for the identical diagnostic programs for all types of VAX computers: '''Peripheral Diagnostics'''<br />
<br />
=== CPU Cluster Testing ===<br />
<br />
'''NOTE: The term "CPU cluster" used here means all components belonging to a CPU; there is no connection with the term [[VAXcluster|"VAXcluster" (alternatively: "VMScluster")]].'''<br />
<br />
The VAX CPU cluster is tested by a set of programs, existing at several program levels, as follows:<br />
<br />
* Level 5<br />
** Console tests<br />
** Processor tests<br />
** Memory tests<br />
* Level 4<br />
** VAX instruction set test (hardcore for VDS)<br />
** Cache and translation buffer tests (VAX-11/750 only)<br />
* Level 3<br />
** Memory tests (if no level 5 test possible)<br />
** Channel adapter tests<br />
** Cluster exerciser<br />
<br />
'''NOTE: The term "Channel adapter" used here means bus adapter, e.g. for [[UNIBUS]] or [[MASSBUS]].'''<br />
<br />
This set of programs implements the VAX diagnostic strategy by providing a set of building blocks by which a system may be tested, starting with the level 5 basic processor tests and ending with the level 3 cluster exerciser, which is a program meant to exercise all components of the cluster.<br />
<br />
=== Peripheral Diagnostics ===<br />
<br />
Thorough testing of a peripheral device requires the development of three different diagnostic programs. For each device type the following will typically (but not necessarily) exist:<br />
<br />
* A level 3 logic test<br />
* A level 3 function test<br />
* A level 2R function test<br />
<br />
This group of programs implements the diagnostic strategy by providing a facility for producing very accurate and detailed identifications of fault conditions via the level 3 programs and by also providing a method by which the device may be tested without bringing down the customer's operating system via the level 2R program.<br />
<br />
The level 3 logic test will provide the greatest detail of error resolution, indicating which section of logic is failing. This program will be used by technicians to repair bad logic boards, and will provide very high test coverage. Some devices contain ROM-resident microprograms ("self-tests") that perform logic testing, making a level 3 logic test unnecessary.<br />
<br />
The level 3 function test will provide a comprehensive test of all of the device’s functions. This program will be used to determine accurately whether or not a device is operating correctly. This is the definitive function test and provides very high test coverage. Level 3 function tests are usually required even if the device possesses self-testing capabilities, because self-tests generally are not capable of complete detection of function failures. <br />
<br />
The level 2R program will typically consist of a subset of the level 3 function test. It will test as much of the device’s functionality as can be tested in the user (VMS) environment. The tests it contains are exact or approximate copies of tests existing in the level 3 program.<br />
<br />
A typical sequence of use for these programs, when dealing with a system at a customer site, is as follows:<br />
<br />
# The customer (or field service) suspects a fault existing in the device.<br />
# The level 2R program is run to see if the error can be detected without stopping the operating system. If the error is found, go to step 4.<br />
# If the level 2R program cannot identify the fault, the operating system is brought down and the level 3 function test is run.<br />
# The fault is identified and the failing [[Field Replacable Unit|FRU]] is replaced. The operating system is then brought back up.<br />
# The failing FRU is brought back to DIGITAL, where the level 3 logic test, the level 3 function test, or perhaps a module test station is used to identify the failing logic on the FRU. The FRU is repaired.<br />
<br />
== VAX Diagnostic Coding Convention ==<br />
<br />
VAX diagnostic program names consist of 5 letters and a two-digit version number, e.g.: ECKAL-3.4:<br />
<br />
* E = VAX<br />
* C = 11/750<br />
* K = CPU<br />
* A = Supervisor<br />
* L = Unique identifier<br />
* 3 = Major revision<br />
* 4 = Minor Revision <br />
<br />
See the following 1986 VAX Diagnostic Coding Convention Table for letter breakdown:<br />
<br />
EPXYD-R.P<br />
<br />
E = System<br />
<br />
E = VAX<br />
<br />
P = Processor<br />
<br />
B = VAX 8200/8300<br />
D = VAX 8600<br />
S = VAX 11780<br />
T = VAX 11785<br />
C = VAX 11750<br />
N = VAX 11730 and 11725<br />
V = More than one VAX Processor<br />
<br />
X = Device Category<br />
<br />
A = Application (CR, LP, A-D, Misc.)<br />
C = Channel Adaptors (MBA, UBA)<br />
D = Communication Devices (DMC, DZ11)<br />
G = CI Adapter<br />
K = CPU<br />
L = Database Files<br />
M = Magnetic Tape (TE, TU, DT)<br />
P = Test Equipment<br />
Q = QIO Device Driver<br />
R = Rotating Memory (RP, RK, RM, RS, RX)<br />
S = System Monitor (Supervisor, Tape Monitor)<br />
T = Terminal (LA36, VT52)<br />
U = Utilities (Script file, Copy, Update)<br />
W = Workstations<br />
X = System Exerciser (EXR/BUSINT)<br />
Z = Media Packages<br />
0-9 = Engineering File<br />
<br />
Y = Device Type<br />
<br />
Category Application<br />
A = Line Printers, LP, LCP01<br />
B = Card Readers, CR<br />
L = LPA11-K<br />
Category Channel<br />
A = MBA<br />
B = UBA, DWBUA<br />
C = MA780<br />
D = IEC11, IEU11-A, DR70<br />
E = DT07<br />
F = DEC DATAWAY<br />
G = CI780<br />
H = CI750/CI780 MICROCODE VERIFICATION (INTERNAL)<br />
I = TEST BED ADAPTERS<br />
J = NBI ADAPTER<br />
K = CIBCI<br />
<br />
Category Communications<br />
A = DZ11,DZ32,DMZ32,DHU11,DMB32<br />
B = DMC<br />
C = Multiple Devices<br />
D = DR11-C<br />
E = DV11<br />
F = DR780,DF11-W<br />
G = DQS11<br />
H = KMC11-B<br />
I = KMS11-B<br />
J = DM11-BA<br />
K = DMS11-BA<br />
L = DMF32 Combo<br />
M = DMC11,DMR11,DMP11<br />
N = DN11<br />
O = CPI32<br />
P = PCL11<br />
R = DR11B,DR11-W,DRE11<br />
S = DRS11/DSS<br />
T = KCT32-A,FEPCM<br />
U = DUP11<br />
X = Multiple Devices<br />
W = UNA<br />
Y = DEBNT<br />
<br />
Category Database Files<br />
A = CRD DATABASE FILES<br />
B = SYSTEM EXERCISER DATABASE FILES<br />
<br />
Category Magnetic Tape<br />
A = TE16/77, TS11, TU78, TS05<br />
B = TU81,TU80<br />
<br />
Category QIO Device Drivers<br />
For this category, the fourth and fifth letters of the code are the device mnemonic.<br />
For example, EVQDB is the QIO device driver for the DB, or RP disk series.<br />
<br />
Category Test Equipment<br />
A = CI780 Node Tester<br />
B = NI Tester<br />
<br />
Category Rotating Memory<br />
A = Multiple devices<br />
B = RP04/5/6<br />
C = DCL/RP04/5/6<br />
D = RM03/RM05/RM80<br />
E = RK611,RK06,RK07<br />
F = RL02<br />
G = RM80<br />
H = RP07<br />
I = RX02<br />
J = ML11<br />
K = IDC<br />
L = UDA50(RA60,RA80,RA81)<br />
M = RC25 <br />
N = RUX50<br />
<br />
Category System Monitor<br />
A = Supervisor<br />
B = Autosizer<br />
C = DYDDM<br />
<br />
Category Terminals<br />
A = All Terminals<br />
B = Terminal exerciser<br />
C = VS11<br />
D = 11C03-LH Fastek<br />
G = VS70<br />
<br />
Category Utility<br />
A = Script File<br />
B = Copy Command file<br />
C = Updating file<br />
<br />
Category Workstation<br />
A = VS100<br />
<br />
Category Exerciser<br />
B = Exerciser Bus Interaction<br />
<br />
D = Fifth character makes the code unique. A through Z and 1 through 9.<br />
<br />
R = Revision (MAJOR)<br />
P = Revision (MINOR)<br />
<br />
== Distribution of Diagnostic Programs ==<br />
<br />
Typically, a VAX computer came with all the necessary diagnostic programs on console media at no additional charge, e.g.:<br />
<br />
* VAX-11/780: [[RX01/02 floppy drive|RX01 floppies]]<br />
* VAX-11/750, VAX-11/730, and VAX-11/725: [[TU58 DECtape II|TU58 cartridges]]<br />
* VAX 8600: [[RL01/02 disk drive|RL02 disk pack]]<br />
* VAX 8200, VAX 8250, VAX 8300, and VAX 8350: [[RX50 dual-diskette drive|RX50 floppies]]<br />
<br />
Additionally, you could buy larger collections of diagnostic programs on [[magnetic tape]] or [[Removable-pack disk|removable disk packs]].<br />
<br />
Extended documentation was available on microfiche at an extra charge.<br />
<br />
== VMS User Enviroment Test Package (UETP) ==<br />
<br />
From the very beginning of VMS V1.0 there was the '''User Enviroment Test Package''' (UETP), see: [http://bitsavers.trailing-edge.com/pdf/dec/vax/vms/2.0/AA-D643B-TE_VAX-VMS_2.0_UETP_Users_Guide_198003.pdf VAX/VMS UETP User’s Guide AA-D643A-TE]<br />
<br />
Quote from the first UETP manual:<br />
<br />
"''The UETP is a collection of tests designed to demonstrate that the hardware and software components of a VAX/VMS system are in working order. DIGITAL software support representatives run the UETP on a newly installed VAX/VMS system as the formal sample procedure.''"<br />
<br />
UETP is still used in the latest version of VMS (V9.2-2 for x86 as of this writing).<br />
<br />
[https://docs.vmssoftware.com/vsi-openvms-system-manager-s-manual-volume-2-tuning-monitoring-and-complex-systems/#_6017UETP| See here] for the latest VMS UETP manual.<br />
<br />
== ULTRIX System Exerciser Package ==<br />
<br />
[[ULTRIX]] has got a very similar tool to verify proper hardware operation at the operating system level, the '''System Exerciser Package'''.<br />
<br />
For the earliest reference found so far see the manual: [https://drive.google.com/file/d/1i3LoLAvTQC7dZl-T9X3SsQgg_6s_6TCY/view?usp=sharing ULTRIX-32 2.2 System Exercisers 1987 AA-KS95A-TE]<br />
<br />
The MIPS variants of ULTRIX include the System Exerciser Package, too.<br />
<br />
== Additional Diagnostic Tools ==<br />
<br />
* On-board ROM-based diagnostics (RBDs) / Self-tests<br />
* [[Diagnostic and Utility Protocol|DUP]] for [[Mass Storage Control Protocol|MSCP]] devices<br />
<br />
== CPU-specific Supervisors ==<br />
<br />
* '''EBSAA''' VAX 8200/8250/8300/8350 & VS8000 Diagnostic Supervisor<br />
* '''ECSAA''' VAX-11/750 DIAGNOSTIC SUPERVISOR<br />
* '''EDSAA''' VAX 8600/8650 Diagnostic Supervisor<br />
* '''EHSAA''' MicroVAX I VDS<br />
* '''EJSAA''' VAX 8820/8830/8840 Diagnostic Supervisor<br />
* '''ELSAA''' VAX 6210/6220/6230/6240/6310/6320/6330/6340/6350/6360 Diagnostic Supervisor<br />
* '''ENSAA''' VAX 725/730 Diagnostic Supervisor<br />
* '''ESSAA''' VAX 780/785 Diagnostic Supervisor<br />
* '''EXSAA''' ???<br />
* '''EZSAA''' VAX 8530/8550/8700/8800/8820N Diagnostic Supervisor<br />
* '''E?SAA''' VAX9000 Diagnostic Supervisor<br />
<br />
There is no supervisor for the series of VAX 7000 / VAX 10000 computers (see: [http://www.vaxhaven.com/images/4/4d/EK-7001A-TS-001.pdf VAX 7000 Advanced Troubleshooting EK-7001A-TS-001])<br />
<br />
== Set of Diagnostics for a SV-BXTAA VAX-11/750 System ==<br />
<br />
A SV-BXTAA VAX-11/750 System consists of:<br />
<br />
* [[KA750 CPU|VAX-11/750 CPU]]<br />
* [[MS750 Memory System|MS750 1MB memory]]<br />
* [[DECwriter IV|LA38 printing console terminal]]<br />
* [[RH750 Massbus Adapter]]<br />
* [[RM02/03 disk drive|RM03 MASSBUS disk drive subsystem]]<br />
* [[DZ11 asynchronous serial line interface|DZ11 terminal adapter]]<br />
* [[TS11 Subsystem|TS11 magnetic tape unit]]<br />
<br />
The diagnostics set for this system is made of:<br />
<br />
* CPU-specific diagnostic main program<br />
** '''ECSAA''' VAX 11750 DIAG SUPERVISOR<br />
<br />
* VAX-common automatic sizing program which automatically determines the current system configuration<br />
** '''EVSBA''' VAX AUTOSIZER DIAGNOSTIC<br />
<br />
* Set of VAX-11/750 CPU diagnostics<br />
** '''ECKAA''' VAX 11750 UDIAG MON<br />
** '''ECKAB''' VAX 11750 MICRO DPM<br />
** '''ECKAC''' VAX 11750 MICRO MIC<br />
** '''ECKAD''' VAX FP750 MICRODIAG<br />
** '''ECKAF''' VAX KC750 UDIAG<br />
** '''ECKAL''' VAX 11750 CACHE/TB DIAG<br />
** '''ECKAM''' VAX 11750 MEMORY DIAG<br />
** '''ECKAX''' VAX 11750 CLUSTER EXER<br />
<br />
* VAX-common instruction set diagnostic<br />
** '''EVKAA''' VAX INSTRUCTION SET TEST<br />
<br />
* VAX-11/750 bus diagnostics<br />
** '''ECCAA''' VAX 11750 RH750 DIAG<br />
** '''ECCBA''' VAX 11750 UBI/DW750 DIAG<br />
<br />
* Set of VAX-common peripheral diagnostics<br />
** '''EVTAA''' VAX TERMINAL DIAGNOSTIC<br />
** '''EVTBA''' VAX TERMINAL EXERCISER<br />
** '''EVDAA''' VAX DZ11 8 LINE ASYNC MUX<br />
** '''EVMAA''' VAX TM03/TE16/TU45-77 Tape<br />
** '''EVRDA''' VAX RM03/RM05/RM80 DISKLESS<br />
** '''EVRDB''' VAX RM03/RM05 FUNCTIONAL TEST<br />
<br />
== Booting the VAX Diagnostic Supervisor ==<br />
<br />
The command to boot the VAX Diagnostic Supervisor on a SIMH VAX is:<br />
<br />
BOOT RQ0 /R5:10<br />
<br />
* <code>RQ0</code> is the device identifier for the MSCP disk, unit 0, where the diagnostics are stored; adjust this according to your requirements.<br />
* <code>/R5:10</code> is the boot flag to boot the Diagnostic Supervisor located in directory <code>DUA0:[SYSMAINT]</code> or <code>DUA0:[SYS0.SYSMAINT]</code>.<br />
<br />
For booting the VAX Diagnostic Supervisor on a real VAX refer chapter 2.1 of the "'''VAX DS Diagnostic Supervisor User's Guide'''" [[#ref_1|[1]]]<br />
<br />
== Sample run of the VDS EVSBA AUTOSIZER ==<br />
<br />
DS> '''LOAD EVSBA.EXE'''<br />
DS> '''SET FLAGS QUICK'''<br />
DS> '''START /SECTION:MANUAL'''<br />
<br />
.. Program: EVSBA - AUTOSIZER LEVEL 3, revision 5.1, 3 tests,<br />
at 18:18:28.19.<br />
<br />
COMMAND? '''HELP'''<br />
<br />
<br />
HELP<br />
<br />
This is a manual section command. This program creates ATTACH<br />
commands for all devices in the system.<br />
(ATTACH,CHANGE,EXIT,HELP,LIST,READ,SIZE,WRITE) - These commands<br />
control the sizer in manual and selftest mode.<br />
To obtain further information type HELP followed by a topic.<br />
For example;<br />
HELP MANUAL<br />
<br />
Additional information available:<br />
<br />
ATTACH CHANGE DEFAULT DEVICE EVENT <br />
EXIT HELP LIST MANUAL QUICK <br />
READ SECTION SELFTEST SCRIPT SIZE <br />
SUMMARY WRITE <br />
<br />
COMMAND? '''SIZE'''<br />
COMMAND? '''LIST'''<br />
FILE IN MEMORY 'CONFIG.COM'<br />
!! AUTOMATIC SIZING PROGRAM.<br />
!! THIS IS A TOOL AND NOT A DIAGNOSTIC PROGRAM.<br />
!! CONFIGURATION FILE FOR SYSTEM.<br />
!! COMPUTER GENERATED CPU TYPE 2 MICROCODE REV LEVEL = 99 <br />
!! NUMERIC VALUES WITH A LEADING ZERO ARE ASSIGNED.<br />
!! FILE VALID ONLY FOR STANDARD HARDWARE CONFIGURATION.<br />
!! TIME IS 15-FEB-1984 18:18:56.85 <br />
!!<br />
!! *** QUICK FLAG SET. NO CHECKS MADE FOR TERMINALS ON DZ11/DZ32'S ***<br />
!!<br />
!!<br />
!! DEFINE PROCESSOR...<br />
!!<br />
DS> ATTACH KA750 HUB KA0 YES YES YES 027FF 0 <br />
!!<br />
!! DEFINE MEMORY...<br />
!!<br />
DS> ATTACH MS750 MS0 <br />
!!<br />
!! DEFINE UNIBUS ADAPTERS...<br />
!!<br />
DS> ATTACH DW750 HUB DW0 <br />
!!<br />
DS> ATTACH LP11 DW0 LPA 777514 0200 04 <br />
DS> ATTACH LP25 LPA LPA0 !! *** PRINTER TYPE IS ESTIMATED ***<br />
DS> ATTACH TS11 DW0 MSA0 772520 0224 05 <br />
DS> ATTACH UDA50 DW0 DUA 772150 0154 05 02 <br />
DS> ATTACH RA81 DUA DUA0 <br />
DS> ATTACH RA60 DUA DJA2 <br />
DS> ATTACH RX50 DUA DUA3 <br />
DS> ATTACH DZ11 DW0 TTA 760100 0300 05 EIA <br />
DS> ATTACH DZ11 DW0 TTB 760110 0310 05 EIA <br />
DS> ATTACH DZ11 DW0 TTC 760120 0320 05 EIA <br />
DS> ATTACH DZ11 DW0 TTD 760130 0330 05 EIA <br />
COMMAND? '''WRITE'''<br />
CONFIGURATION FILE IS NORMALLY READ/WRITTEN TO THE SUPERVISOR CONSOLE MEDIA<br />
VERIFY SUPERVISOR CONSOLE MEDIA LOADED.<br />
VERIFIED? [(Yes), No] '''YES'''<br />
COMMAND? '''EXIT'''<br />
DS> <br />
<br />
== See also ==<br />
<br />
* [[Running VDS Diagnostics on the SIMH VAX-11/750]]<br />
<br />
== External links ==<br />
<br />
This page contains condensed information from several DEC manuals, among others:<br />
<br />
* [http://bitsavers.org/pdf/dec/vax/diag/EP-EVNDX-25.0_Oct86.txt EVNDX25 VAX DIAGNOSTIC INDEX] <br />
* [https://vt100.net/mirror/hcps/si75fin1.pdf EK-SI75F-IN-001 VAX-11-750 Installation Manual] pdf-page 60ff<br />
* <div id="ref_1">[1] [http://bitsavers.org/pdf/dec/vax/diag/VAX_Diagnostic_Supervisor_Users_Guide_Apr89.pdf AA-FK66A-TE VAX DS Diagnostic Supervisor User's Guide] </div><br />
* [http://bitsavers.org/pdf/dec/vax/diag/EK-1VAXD-TM-001_VAX_Diagnostic_Design_Guide_Aug79.pdf EK-1VAXD-TM-003 VAX Diagnostic Design Guide]<br />
* [http://bitsavers.org/pdf/dec/vax/diag/AA-FK67A-TE_VAX_Diagnostic_Design_Guide_Apr89.pdf AA-FK67A-TE VAX Diagnostic Design Guide]<br />
* [http://www.bitsavers.org/pdf/dec/vax/vms/1.5/2b/AA-D643A-TE_VAX_VMS_UETP_Users_Guide_Aug78.pdf AA-D643A-TE VAX/VMS UETP User’s Guide]<br />
* [http://www.trailing-edge.com/~shoppa/11780diags/ VAX-11/780 Diagnostic Help Files]<br />
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/VAX/7001ATS1.PDF EK-7001A-TS-001 VAX 7000 Advanced Troubleshooting]<br />
<br />
[[Category: VAXen]]<br />
[[Category: VAX Software]]<br />
[[Category: SIMH Tutorials]]<br />
[[Category: VMS Practical Guides]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=VAX_8200&diff=33533
VAX 8200
2024-02-17T15:29:26Z
<p>Vaxorcist: First VAX 8200 support corrected to VMS V4.3A</p>
<hr />
<div>{{InfoboxVAX-Data<br />
| name = VAX 8200<br />
| Announcement = 29 January 1986<br />
| Codename = Scorpio<br />
| OS-support-VMS = V4.3A<br />
| CPU-name-VMS = KA820<br />
| CPU-module = KA820<br />
| Module = T1001-00<br />
| Num-proc = 1<br />
| VMS-CPU = 5<br />
| VMS-XCPU = 0<br />
| SID = 05282B14<br />
| XSID = 00000000<br />
| CPU-chip = V11 [[#ref_2|[2]]]<br />
| CPU-technology = ZMOS [[#ref_1|[1]]]<br />
| CPU-cycle = 200ns<br />
| CPU-clock = 5MHz [[#ref_2|[2]]]<br />
| Instruction-buffer = 8 bytes<br />
| Control-store = 15K 40-bit words [[#ref_3|[3]]]<br />
| WCS = 1K 40-bit words [[#ref_3|[3]]]<br />
| Cache = 8KB<br />
| Compatibility-mode = No<br />
| Console-processor = CPU<br />
| Console-device = RX50<br />
| Maximum-memory = 128MB [[#ref_1|[1]]]<br />
| Memory-checking = 7-bit ECC/longword [[#ref_3|[3]]]<br />
| Max-I/O-throughput = 13.3MB/s<br />
| BUS-vaxbi = 1 @ 13.3MB/s<br />
| LAN-support = optional<br />
| VUPs = 1.0<br />
}}<br />
<br />
The '''VAX 8200''' is a mid-range [[VAX]] uni-processor system built around the [[VAX Bus Interconnect|VAXBI]] [[bus]]; it can support an optional [[UNIBUS]] adapter.<br />
<br />
{{stub}}<br />
<br />
==References==<br />
<br />
<div id="ref_1">[1] VAX Systems Hardware Handbook -- VAXBI Systems. EB-31692-46</div><br />
<div id="ref_2">[2] KA825 Maintenance Advisory. EK-KA825-MA-001</div><br />
<div id="ref_3">[3] VAX Hardware Handbook. Volume 2-1986. </div><br />
<br />
==External links==<br />
<br />
* [http://vtda.org/docs/computing/DEC/VMS/AZ-GN4AC-TE_VAX_8200_8300_Owner's_Manual_Sep1986.pdf VAX 8200/8300 Owner's Manual] (AZ-GN4AC-TE)<br />
* [http://www.bitsavers.org/pdf/dec/vax/handbook/VAX_Hardware_Handbook_Volume_2_1986.pdf VAX Hardware Handbook Volume 2] - the VAX 8200 is described on page 1-10&ndash;1-11 (pg. 19-20 of the PDF) and covered in detail in Chapter 5, "VAX 8200 and VAX 8300 Processors" (pp. 86-102 of the PDF)<br />
<br />
{{Nav VAX}}<br />
<br />
[[Category: DEC VAX systems]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=DEC_acronyms&diff=33524
DEC acronyms
2024-02-17T09:03:06Z
<p>Vaxorcist: "WCS = Writable Control Store" added</p>
<hr />
<div>'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Acronym<br />
! Meaning<br />
|-<br />
| CBOX<br />
| Cache Box<br />
|-<br />
| CFS<br />
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])<br />
|-<br />
| CI<br />
| [[Computer Interconnect]]<br />
|-<br />
| CMI<br />
| [[CPU/Memory Interconnect]]<br />
|-<br />
| CSS<br />
| [[Computer Special Systems]]<br />
|-<br />
| DBN<br />
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]<br />
|-<br />
| DCL<br />
| [[Digital Command Language]]<br />
|-<br />
| DCS<br />
| [[Digital Classified Software]]<br />
|-<br />
| DDC<br />
| [[Digital Diagnostic Center]]<br />
|-<br />
| DSA<br />
| [[Digital Storage Architecture]]<br />
|-<br />
| DSC<br />
| [[Disk Save and Compress]]<br />
|-<br />
| DSDF<br />
| [[DSA Standard Disk Format]]<br />
|-<br />
| DSR<br />
| [[Digital Standard Runoff]]<br />
|-<br />
| DSSI<br />
| [[Digital Storage Systems Interconnect]]<br />
|-<br />
| DUP<br />
| [[Diagnostic and Utility Protocol]]<br />
|-<br />
| EBOX<br />
| Execution Box<br />
|-<br />
| ECO<br />
| ''[[Engineering Change Order]]''<br />
|-<br />
| FRU<br />
| [[Field Replacable Unit]]<br />
|-<br />
| IBOX<br />
| Instruction Box<br />
|-<br />
| GPX<br />
| [[Graphics Processing Extension]]<br />
|-<br />
| GIDIS<br />
| [[General Image Display Instruction Set]]<br />
|-<br />
| JBOX<br />
| Junction Box<br />
|-<br />
| LAD<br />
| Local Area Disk<br />
|-<br />
| LAST<br />
| Local Area System Transport<br />
|-<br />
| LAT<br />
| Local Area Transport<br />
|-<br />
| LAVC<br />
| [[Local Area VAXcluster]]<br />
|-<br />
| LBN<br />
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''<br />
|-<br />
| MBOX<br />
| Memory Box<br />
|-<br />
| MCR<br />
| [[Monitor Console Routine]]<br />
|-<br />
| MDS<br />
| [[Maintenance Documentation Service]]<br />
|-<br />
| MSCP<br />
| [[Mass Storage Control Protocol]]<br />
|-<br />
| ODS-2<br />
| [[On-disk Structure 2]]<br />
|-<br />
| OTS<br />
| [[Object Time System]]<br />
|-<br />
| RBN<br />
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]<br />
|-<br />
| RCT<br />
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]<br />
|-<br />
| RDC<br />
| [[Digital Remote Diagnosis Center]]<br />
|-<br />
| RMS<br />
| [[Record Managment Services]]<br />
|-<br />
| SBI<br />
| [[Synchronous Backplane Interconnect]]<br />
|-<br />
| SCA<br />
| [[Systems Communication Architecture]]<br />
|-<br />
| SCS<br />
| [[Systems Communication Services]]<br />
|-<br />
| SDA<br />
| [[System Dump Analyzer]]<br />
|-<br />
| SDB<br />
| [[Standard Drive Bus]]<br />
|-<br />
| SDI<br />
| [[Standard Disk Interconnect]]<br />
|-<br />
| SDL<br />
| Structure Definition Language<br />
|-<br />
| STI<br />
| [[Standard Tape Interconnect]]<br />
|-<br />
| UETP<br />
| [[User Environment Test Package]]<br />
|-<br />
| UPI<br />
| [[DEC Unique Product Identifier| Unique Product Identifier]]<br />
|-<br />
| UQSSP<br />
| [[UNIBUS]] [[QBUS]] Storage Systems Port<br />
|-<br />
| VAXBI<br />
| [[VAX Bus Interconnect]]<br />
|-<br />
| VBOX<br />
| Vector Box<br />
|-<br />
| VDS / VAX/DS<br />
| [[VAX Diagnostic Supervisor]]<br />
|-<br />
| VUP<br />
| [[VAX Unit of Performance]]<br />
|-<br />
| VWS<br />
| [[VAX Workstation Software]]<br />
|-<br />
| WCS<br />
| [[Writable Control Store]]<br />
|-<br />
| XBN<br />
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]<br />
|-<br />
| XMI<br />
| [[Extended Memory Interconnect]]<br />
|}<br />
<br />
<br />
[[Category: Digital Equipment Corporation]]<br />
[[Category: DEC Acronyms]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=Installing_VMS_V2.0_on_SIMH&diff=33523
Installing VMS V2.0 on SIMH
2024-02-17T08:00:56Z
<p>Vaxorcist: /* vax750.ini for a typical medium 16-user VAX-11/750 system */ Order no. added</p>
<hr />
<div>The aim of this tutorial is to show how to install [[VMS]] V2.0 on the [[SIMH]] [[VAX-11/750]] [[simulator]].<br />
<br />
<br />
== Preparations ==<br />
<br />
=== SIMH vax750 simulator ===<br />
<br />
You have the choice between the SIMH '''vax780''' and the SIMH '''vax750''' simulators in principle, because both the [[VAX-11/780]] and VAX-11/750 are supported by VMS V2.0.<br />
<br />
I choose the VAX-11/750 for this tutorial, because it's the "new" model (and I've got a real one ;-)). <br />
<br />
=== VMS V2.0 ===<br />
<br />
Get VMS V2.0 disk images from [https://drive.google.com/file/d/11VQN8ciGmUl3ps3YTnfN7OTtHT2b2wLO/view?usp=sharing here], unzip and put it in into the directory where the SIMH vax750 simulator resides. <br />
<br />
=== vax750.ini for a typical medium 16-user VAX-11/750 system ===<br />
<br />
Use the following vax750.ini file for a typical medium 16-user VAX-11/750 system (order no.: SV-BXTAA).<br />
<br />
[[File:VAX-11-750 RM03.png|400px|thumb|right|Medium [[VAX-11/750]] system with one [[RM03]] disk drives, a [[TS11]] tape drive, and an [[LA38]] console printer terminal]]<br />
<br />
<pre><br />
; ================================================<br />
; vax750.ini<br />
; ================================================<br />
;<br />
; Medium size 16 user system made of:<br />
; - 1M bytes of memory<br />
; - 16 DZ11 terminal lines<br />
; - 2 RM03 disk drives<br />
; - line printer<br />
; - TE16 magnetic tape unit<br />
<br />
SET QUIET<br />
<br />
SET CPU 1M<br />
SET THROTTLE 700K<br />
;SET CPU IDLE=VMS<br />
<br />
SET CONSOLE LOG=VMS020-01.LOG<br />
<br />
SET DZ LINES=16<br />
ATT DZ 6666<br />
<br />
SET LPT ENA<br />
ATT LPT printer.txt<br />
<br />
SET RP ENA<br />
SET RP0 RM03 ; DRA0:<br />
ATT RP0 VMS020.RM3<br />
<br />
SET RP1 RM03 ; DRA1:<br />
ATT RP1 DATA.RM3<br />
<br />
SET RP2 DIS<br />
SET RP3 DIS<br />
SET RP4 DIS<br />
SET RP5 DIS<br />
SET RP6 DIS<br />
SET RP7 DIS<br />
<br />
SET RL DIS<br />
<br />
SET HK DIS<br />
<br />
SET RQ DIS<br />
SET RY DIS<br />
SET TQ DIS<br />
SET TS DIS<br />
<br />
SET TU ENA<br />
SET TU0 TE16 ; MTA0:<br />
<br />
SET TU1 DIS<br />
SET TU2 DIS<br />
SET TU3 DIS<br />
SET TU4 DIS<br />
SET TU5 DIS<br />
SET TU6 DIS<br />
SET TU7 DIS<br />
<br />
<br />
BOOT RP0/R5:1<br />
;BOOT RP0<br />
</pre><br />
<br />
== Installation ==<br />
<br />
=== First boot ===<br />
Start the simh vax750 simulator:<br />
<br />
Windows:<br />
<pre>run vax750.exe</pre><br />
<br />
Linux:<br />
<pre>./vax750</pre><br />
<br />
Be aware that Linux is case sensitive!<br />
----<br />
SIMH tells you it will write a log:<br />
<br />
<pre><br />
Logging to file "VMS020-01.LOG"<br />
</pre><br />
<br />
VMS boots to the '''SYSBOOT>''' prompt. Enter the following two commands and confirm each with '''<Enter>''':<br />
<br />
<pre><br />
SYSBOOT> USE 16USER.PAR<br />
<br />
SYSBOOT> CONTINUE<br />
</pre><br />
<br />
This way you do:<br />
<br />
- Choose the parameter file for a medium 16-user VAX-11/750 system<br />
<br />
- Continue booting<br />
<br />
VMS finishes booting:<br />
<br />
<pre><br />
<br />
VAX/VMS Version V2.0 5-APR-1980 21:11<br />
<br />
Opcom, 3-JUN-1980 11:57:54.86, logfile initialized, operator=_OPA0:<br />
<br />
Login quotas - Interactive limit=64, Current interactive value=0<br />
SYSTEM job terminated at 3-JUN-1980 11:57:58.69<br />
<br />
</pre><br />
<br />
Press '''<Enter>''' to get to the login prompt.<br />
<br />
Log in with username '''SYSTEM''' and password '''MANAGER'''.<br />
<br />
The password is NOT echoed.<br />
<br />
<pre><br />
Username: SYSTEM<br />
<br />
Password: <br />
<br />
Welcome to VAX/VMS Version V2.0 <br />
<br />
$ <br />
</pre><br />
<br />
You're in!<br />
<br />
Try '''DIR''' as a first VMS command to show the files in your login directory:<br />
<br />
<pre><br />
$ DIR<br />
<br />
Directory _DRA0:[SYSMGR]<br />
<br />
ACCOUNTNG.DAT;1 CHARTYPE.DAT;1 ERFSTART.COM;1 FORMSTYPE.DAT;1<br />
LPA11STRT.COM;1 OPERATOR.LOG;1 RTTLOAD.COM;1 SYSHUTDWN.COM;1<br />
SYSTARTUP.COM;1 <br />
<br />
Total of 9 files.<br />
<br />
$<br />
</pre><br />
<br />
=== A first look around ===<br />
Let's have a first look at our installed VMS V2.0!<br />
<br />
==== For the users completely new to VMS ====<br />
Try the following commands.<br />
<br />
You can abreviate all commands to the extend that they do not get ambiguous, e.g. '''SH''' instead of '''SHOW'''<br />
<br />
VMS is not case-sensitive, but it is common practice to enter commands in UPPERCASE.<br />
----<br />
'''SHOW SYS''' shows you what's going on your system:<br />
<br />
<pre><br />
$ SH SYS<br />
<br />
VAX/VMS Processes on 3-JUN-1980 11:59:11.71 Uptime 0 00:01:19<br />
Pid Process Name UIC State Pri Dir. I/O CPU Page flts Ph.Mem<br />
00010000 NULL 000,000 COM 0 0 00:01:13.77 0 0 <br />
00010001 SWAPPER 000,000 HIB 16 0 00:00:00.11 0 0 <br />
00010017 ERRFMT 001,006 HIB 9 2 00:00:00.05 30 27 <br />
00010018 OPCOM 001,004 LEF 7 2 00:00:00.05 32 36 <br />
00010019 JOB_CONTROL 001,004 HIB 9 2 00:00:00.12 34 80 <br />
0001001A DRA0ACP 001,003 HIB 8 88 00:00:00.86 66 111 <br />
0002001B SYSTEM 001,004 CUR 4 8 00:00:00.34 82 109 <br />
<br />
$<br />
</pre><br />
<br />
- '''Pid''' = Process ID<br />
<br />
- '''Process Name''' (self-explaining)<br />
<br />
- '''UIC''' = Process owner (User ID)<br />
<br />
- '''State''' = Process state<br />
<br />
- '''Pri''' = Process priority<br />
<br />
- '''Dir. I/O''' = Process direct I/O count<br />
<br />
- '''CPU''' = Process CPU time used<br />
<br />
- '''Page flts''' = Process page faults<br />
<br />
- '''Ph.Mem''' = Process physical memory <br />
<br />
----<br />
'''SHOW DEV''' shows the devices on your VAX:<br />
<br />
<pre><br />
$ SH DEV<br />
<br />
List of Devices on 3-JUN-1980 11:59:20.81<br />
Device Device Device Err. Volume Free Trans Mount<br />
Name Status Characteristics Count Label Blocks Count Count<br />
DRA0: on line mnt 0 VAXVMSRL2 99033 23 1<br />
DRA1: on line 0 <br />
OPA0: on line 0 <br />
MTA0: on line 0 <br />
LPA0: on line 0 <br />
TTA0: on line 0 <br />
TTA1: on line 0 <br />
TTA2: on line 0 <br />
TTA3: on line 0 <br />
TTA4: on line 0 <br />
TTA5: on line 0 <br />
TTA6: on line 0 <br />
TTA7: on line 0 <br />
TTB0: on line 0 <br />
TTB1: on line 0 <br />
TTB2: on line 0 <br />
TTB3: on line 0 <br />
TTB4: on line 0 <br />
TTB5: on line 0 <br />
TTB6: on line 0 <br />
TTB7: on line 0 <br />
<br />
$<br />
</pre><br />
- '''DRA0''' is the first RM03 disk drive (the VMS system drive)<br />
<br />
- '''DRA1''' is the second RM03 disk drive (the data drive, still empty)<br />
<br />
- '''OPA0''' is the operator terminal (from which you boot the system)<br />
<br />
- '''LPA0''' is the system line printer<br />
<br />
- '''TTA0''' - '''TTB7''' are the sixteen user terminals<br />
<br />
- '''MTA0''' is the TE16 magtape drive<br />
<br />
----<br />
'''HELP''' shows the available help topic and brief instructions for using '''HELP''':<br />
<pre><br />
$ HELP<br />
<br />
HELP<br />
<br />
Help can be obtained on a particular topic by typing :<br />
HELP topic subtopic subsubtopic ...<br />
A topic can have the following format :<br />
1) an alphanumeric string (e.g. a command name, option, etc...)<br />
2) same preceded by a "/" (=interpreted as a qualifier)<br />
3) the match-all symbol "*"<br />
4) any of the above followed by "..." (on first topic only)<br />
Examples:<br />
HELP ASSIGN PARAMETERS<br />
HELP SET TERMINAL /LOWERCASE<br />
HELP SHOW...<br />
Abbreviations result in all matches being displayed.<br />
<br />
Additional information available:<br />
<br />
ALLOCATE ANALYZE APPEND ASSIGN BASIC BLISS CANCEL CLOSE COBOL CONTINUE COPY CORAL<br />
CREATE DEALLOCATE DEASSIGN DEBUG DECK DEFINE DELETE DEPOSIT DIFFERENCES DIRECTORY<br />
DISMOUNT DUMP EDIT EOD EOJ ERRORS EXAMINE EXIT FORTRAN GOTO HELP IF<br />
INITIALIZE INQUIRE JOB LEXICAL LIBRARY LINK LOGIN LOGOUT MACRO MAIL MCR<br />
MESSAGE MOUNT ON OPEN PASCAL PASSWORD PATCH PRINT PROCEDURE PURGE READ RENAME<br />
REPLY REQUEST RMS RUN SET SHOW SORT SPECIFY START STOP SUBMIT<br />
SYMBOLS SYNCHRONIZE SYSTEM TECO TYPE UNLOCK VTEDIT WAIT WRITE<br />
<br />
$ <br />
</pre><br />
----<br />
Be careful not to destroy the newly installed system; you are logged in as '''SYSTEM''' who can e.g. easily delete crucial system files.<br />
<br />
The use of '''SHOW''' commands cannot do any harm.<br />
<br />
==== For users who already know "newer" VMS versions (V4.x and later) ====<br />
<br />
You will probably miss some of the commands you know from "newer" VMS versions ...<br />
<br />
Some utilities have different names, others are not yet existing.<br />
<br />
- '''BACKUP''' is '''DSC''' in VMS V2.0<br />
<br />
- '''MONITOR''' is '''DISPLAY''' in VMS V2.0 (needs to be called '''MCR DISPLAY''')<br />
<br />
- '''SHOW MEMORY''' is not yet implemented in VMS V2.0<br />
<br />
- ...<br />
<br />
=== Orderly shutdown ===<br />
<br />
VMS needs an orderly shutdown. <br />
<br />
Don't just break out of the simulation using '''<Strg + e>''' and tell simh to exit.<br />
<br />
You might loose data not yet written to disk and (if Murphy comes around) destroy the file structures on your disk.<br />
<br />
Use the following command to perform an orderly shutdown:<br />
<br />
'''@SYS$SYSTEM:SHUTDOWN'''<br />
<br />
You will be asked for the shutdown delay in minutes (you can specify '''0''' minutes for an immediate shutdown), and you can give an optional reason for the shutdown to be displayed at the terminals of the users on your system (just press '''<Enter>''' to skip). <br />
<br />
Furthermore you can specify if you want to spin the disks down (not really relevant with SIMH ...).<br />
<br />
<pre><br />
$ @SYS$SYSTEM:SHUTDOWN<br />
<br />
System shutdown command procedure.<br />
3-JUN-1980 11:59:51<br />
<br />
How many minutes until shutdown?: 0<br />
<br />
Reason?: REBOOT<br />
<br />
Do you want to spin down the disks?: NO<br />
<br />
Opcom, 12:00:05.13, Operator terminal status, _OPA0:<br />
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, <br />
OPER(1,2,3,4,5,6,7,8,9,10,11,12)<br />
<br />
Login quotas - Interactive limit=0, Current interactive value=1<br />
Non-operator logins are disabled.<br />
<br />
_OPA0:,SYSTEM 12:00:06.12<br />
"BATCH AND DEVICE QUEUES HAVE BEEN STOPPED"<br />
<br />
<br />
_OPA0:,SYSTEM 12:00:06.81<br />
"SYSTEM SHUTDOWN IN 0 MINUTES. LOGINS ARE DISABLED, PLEASE LOGOFF.<br />
<br />
_OPA0:,SYSTEM 12:00:07.05<br />
"REBOOT<br />
<br />
Invoke installation dependent shutdown procedure.<br />
Stop all user processes.<br />
Dismount all mounted volumes.<br />
Opcom, 12:00:08.83, SYSTEM Accnt=SYSTEM <br />
Opcom, _OPA0:, "OPERATOR REQUESTED SHUTDOWN"<br />
<br />
<br />
Opcom, 3-JUN-1980 12:00:08.99, logfile closed, operator=_OPA0:<br />
<br />
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM<br />
<br />
<br />
Infinite loop, PC: 80007300 (BRB 80007300)<br />
sim> exit<br />
Goodbye<br />
Log file closed<br />
</pre><br />
<br />
When you get the simh prompt ('''sim>''') you can safely exit the simulator using the '''exit''' command. <br />
<br />
=== Subsequent boots ===<br />
Now that you have sucessfully installed VMS V2.0 you no longer need to boot into '''SYSBOOT>'''.<br />
<br />
Make a comment out of the command '''BOOT RP0/R5:1''' in the vax750.ini file by putting a semicolon in front of it.<br />
<br />
Remove the semicolon from the ''';BOOT RP0''' line to make it a command.<br />
<br />
From now on you'll boot directly into VMS V2.0!<br />
<br />
Congratulations!<br />
<br />
== "Connecting" User Terminals ==<br />
I recommend using a [[Telnet]] [[client]] such as [[PuTTY]] to connect to the 16 terminal lines.<br />
<br />
I use the following PuTTY settings:<br />
* Host Name: 127.0.0.1 (or your PCs IP address)<br />
* Connection type: Telnet <br />
* Port: 6666<br />
* Terminal/Keyboard/The Backspace key/: Control-?<br />
* Terminal/Keyboard/The function keys and keypad: VT100+<br />
<br />
<pre><br />
Connected to the VAX 11/780 simulator DZ device, line 0<br />
<br />
<br />
Username: SYSTEM<br />
<br />
Password: <br />
<br />
Welcome to VAX/VMS Version V2.0 <br />
<br />
$<br />
</pre><br />
<br />
== Recommended Reading ==<br />
* [http://bitsavers.org/pdf/dec/vax/vms/2.0/AA-D021C-TE_VAX-11_2.0_Software_Installation_Guide_198003.pdf AA-D021C-TE Software Installation Guide]<br />
<br />
* [http://bitsavers.org/pdf/dec/vax/vms/2.0/AA-D030B-TE_VAX_VMS_2.0_Primer_198003.pdf AA-D030B-TE VAX/VMS Primer]<br />
<br />
[[Category: SIMH Tutorials]]<br />
[[Category: VMS Practical Guides]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=DEC_acronyms&diff=33499
DEC acronyms
2024-02-16T08:30:12Z
<p>Vaxorcist: "Field Replacable Unit" link added</p>
<hr />
<div>'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Acronym<br />
! Meaning<br />
|-<br />
| CBOX<br />
| Cache Box<br />
|-<br />
| CFS<br />
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])<br />
|-<br />
| CI<br />
| [[Computer Interconnect]]<br />
|-<br />
| CMI<br />
| [[CPU/Memory Interconnect]]<br />
|-<br />
| CSS<br />
| [[Computer Special Systems]]<br />
|-<br />
| DBN<br />
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]<br />
|-<br />
| DCL<br />
| [[Digital Command Language]]<br />
|-<br />
| DCS<br />
| [[Digital Classified Software]]<br />
|-<br />
| DDC<br />
| [[Digital Diagnostic Center]]<br />
|-<br />
| DSA<br />
| [[Digital Storage Architecture]]<br />
|-<br />
| DSC<br />
| [[Disk Save and Compress]]<br />
|-<br />
| DSDF<br />
| [[DSA Standard Disk Format]]<br />
|-<br />
| DSR<br />
| [[Digital Standard Runoff]]<br />
|-<br />
| DSSI<br />
| [[Digital Storage Systems Interconnect]]<br />
|-<br />
| DUP<br />
| [[Diagnostic and Utility Protocol]]<br />
|-<br />
| EBOX<br />
| Execution Box<br />
|-<br />
| ECO<br />
| ''[[Engineering Change Order]]''<br />
|-<br />
| FRU<br />
| [[Field Replacable Unit]]<br />
|-<br />
| IBOX<br />
| Instruction Box<br />
|-<br />
| GPX<br />
| [[Graphics Processing Extension]]<br />
|-<br />
| GIDIS<br />
| [[General Image Display Instruction Set]]<br />
|-<br />
| JBOX<br />
| Junction Box<br />
|-<br />
| LAD<br />
| Local Area Disk<br />
|-<br />
| LAST<br />
| Local Area System Transport<br />
|-<br />
| LAT<br />
| Local Area Transport<br />
|-<br />
| LAVC<br />
| [[Local Area VAXcluster]]<br />
|-<br />
| LBN<br />
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''<br />
|-<br />
| MBOX<br />
| Memory Box<br />
|-<br />
| MCR<br />
| [[Monitor Console Routine]]<br />
|-<br />
| MDS<br />
| [[Maintenance Documentation Service]]<br />
|-<br />
| MSCP<br />
| [[Mass Storage Control Protocol]]<br />
|-<br />
| ODS-2<br />
| [[On-disk Structure 2]]<br />
|-<br />
| OTS<br />
| [[Object Time System]]<br />
|-<br />
| RBN<br />
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]<br />
|-<br />
| RCT<br />
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]<br />
|-<br />
| RDC<br />
| [[Digital Remote Diagnosis Center]]<br />
|-<br />
| RMS<br />
| [[Record Managment Services]]<br />
|-<br />
| SBI<br />
| [[Synchronous Backplane Interconnect]]<br />
|-<br />
| SCA<br />
| [[Systems Communication Architecture]]<br />
|-<br />
| SCS<br />
| [[Systems Communication Services]]<br />
|-<br />
| SDA<br />
| [[System Dump Analyzer]]<br />
|-<br />
| SDB<br />
| [[Standard Drive Bus]]<br />
|-<br />
| SDI<br />
| [[Standard Disk Interconnect]]<br />
|-<br />
| SDL<br />
| Structure Definition Language<br />
|-<br />
| STI<br />
| [[Standard Tape Interconnect]]<br />
|-<br />
| UETP<br />
| [[User Environment Test Package]]<br />
|-<br />
| UPI<br />
| [[DEC Unique Product Identifier| Unique Product Identifier]]<br />
|-<br />
| UQSSP<br />
| [[UNIBUS]] [[QBUS]] Storage Systems Port<br />
|-<br />
| VAXBI<br />
| [[VAX Bus Interconnect]]<br />
|-<br />
| VBOX<br />
| Vector Box<br />
|-<br />
| VDS / VAX/DS<br />
| [[VAX Diagnostic Supervisor]]<br />
|-<br />
| VUP<br />
| [[VAX Unit of Performance]]<br />
|-<br />
| VWS<br />
| [[VAX Workstation Software]]<br />
|-<br />
| XBN<br />
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]<br />
|-<br />
| XMI<br />
| [[Extended Memory Interconnect]]<br />
|}<br />
<br />
<br />
[[Category: Digital Equipment Corporation]]<br />
[[Category: DEC Acronyms]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=DEC_acronyms&diff=33498
DEC acronyms
2024-02-15T18:37:57Z
<p>Vaxorcist: "VDS / VAX Diagnostic Supervisor" added</p>
<hr />
<div>'''Acronyms''' from [[Digital Equipment Corporation]]. (Listings given in ''italics'' are not just DEC acronyms.)<br />
<br />
{| class="wikitable"<br />
|-<br />
! Acronym<br />
! Meaning<br />
|-<br />
| CBOX<br />
| Cache Box<br />
|-<br />
| CFS<br />
| [[Common File System]] ([[PDP-10]]/[[TOPS-20]])<br />
|-<br />
| CI<br />
| [[Computer Interconnect]]<br />
|-<br />
| CMI<br />
| [[CPU/Memory Interconnect]]<br />
|-<br />
| CSS<br />
| [[Computer Special Systems]]<br />
|-<br />
| DBN<br />
| [[DSA Standard Disk Format#Diagnostic Block Numbers (DBNs)|Diagnostic Block Number]]<br />
|-<br />
| DCL<br />
| [[Digital Command Language]]<br />
|-<br />
| DCS<br />
| [[Digital Classified Software]]<br />
|-<br />
| DDC<br />
| [[Digital Diagnostic Center]]<br />
|-<br />
| DSA<br />
| [[Digital Storage Architecture]]<br />
|-<br />
| DSC<br />
| [[Disk Save and Compress]]<br />
|-<br />
| DSDF<br />
| [[DSA Standard Disk Format]]<br />
|-<br />
| DSR<br />
| [[Digital Standard Runoff]]<br />
|-<br />
| DSSI<br />
| [[Digital Storage Systems Interconnect]]<br />
|-<br />
| DUP<br />
| [[Diagnostic and Utility Protocol]]<br />
|-<br />
| EBOX<br />
| Execution Box<br />
|-<br />
| ECO<br />
| ''[[Engineering Change Order]]''<br />
|-<br />
| FRU<br />
| Field Replacable Unit<br />
|-<br />
| IBOX<br />
| Instruction Box<br />
|-<br />
| GPX<br />
| [[Graphics Processing Extension]]<br />
|-<br />
| GIDIS<br />
| [[General Image Display Instruction Set]]<br />
|-<br />
| JBOX<br />
| Junction Box<br />
|-<br />
| LAD<br />
| Local Area Disk<br />
|-<br />
| LAST<br />
| Local Area System Transport<br />
|-<br />
| LAT<br />
| Local Area Transport<br />
|-<br />
| LAVC<br />
| [[Local Area VAXcluster]]<br />
|-<br />
| LBN<br />
| ''[[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Logical Block Number]]''<br />
|-<br />
| MBOX<br />
| Memory Box<br />
|-<br />
| MCR<br />
| [[Monitor Console Routine]]<br />
|-<br />
| MDS<br />
| [[Maintenance Documentation Service]]<br />
|-<br />
| MSCP<br />
| [[Mass Storage Control Protocol]]<br />
|-<br />
| ODS-2<br />
| [[On-disk Structure 2]]<br />
|-<br />
| OTS<br />
| [[Object Time System]]<br />
|-<br />
| RBN<br />
| [[DSA Standard Disk Format#Replacement Block Numbers (RBNs)|Replacement Block Number]]<br />
|-<br />
| RCT<br />
| [[DSA Standard Disk Format#Logical Block Numbers (LBNs)|Replacement/Revectoring Control Table]]<br />
|-<br />
| RDC<br />
| [[Digital Remote Diagnosis Center]]<br />
|-<br />
| RMS<br />
| [[Record Managment Services]]<br />
|-<br />
| SBI<br />
| [[Synchronous Backplane Interconnect]]<br />
|-<br />
| SCA<br />
| [[Systems Communication Architecture]]<br />
|-<br />
| SCS<br />
| [[Systems Communication Services]]<br />
|-<br />
| SDA<br />
| [[System Dump Analyzer]]<br />
|-<br />
| SDB<br />
| [[Standard Drive Bus]]<br />
|-<br />
| SDI<br />
| [[Standard Disk Interconnect]]<br />
|-<br />
| SDL<br />
| Structure Definition Language<br />
|-<br />
| STI<br />
| [[Standard Tape Interconnect]]<br />
|-<br />
| UETP<br />
| [[User Environment Test Package]]<br />
|-<br />
| UPI<br />
| [[DEC Unique Product Identifier| Unique Product Identifier]]<br />
|-<br />
| UQSSP<br />
| [[UNIBUS]] [[QBUS]] Storage Systems Port<br />
|-<br />
| VAXBI<br />
| [[VAX Bus Interconnect]]<br />
|-<br />
| VBOX<br />
| Vector Box<br />
|-<br />
| VDS / VAX/DS<br />
| [[VAX Diagnostic Supervisor]]<br />
|-<br />
| VUP<br />
| [[VAX Unit of Performance]]<br />
|-<br />
| VWS<br />
| [[VAX Workstation Software]]<br />
|-<br />
| XBN<br />
| [[DSA Standard Disk Format#External Block Numbers (XBNs)|External Block Number]]<br />
|-<br />
| XMI<br />
| [[Extended Memory Interconnect]]<br />
|}<br />
<br />
<br />
[[Category: Digital Equipment Corporation]]<br />
[[Category: DEC Acronyms]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=BA213_Enclosure&diff=33475
BA213 Enclosure
2024-02-13T20:58:46Z
<p>Vaxorcist: Fixed typo</p>
<hr />
<div>The '''BA213 Enclosure''' is a [[QBUS]] [[mounting box]] from [[Digital Equipment Corporation|DEC]] which is available in rack-mount, wall-mount, pedestal, single-[[cabinet]] (in an [[H9644]]), and double-cabinet versions. It is the 'bigger brother' to the [[BA23 Enclosure]], and the sibling to the [[BA123 Enclosure]].<br />
<br />
It contains a single, 12-s1ot, [[DEC card form factor|quad]]-height [[backplane]], with all 12 slots are [[QBUS#Backplanes|Q/CD]] slots; that backplane cannot be expanded.<br />
<br />
==BA213 Usage==<br />
<br />
The BA213 enclosure was used for a number of [[PDP-11]] and [[MicroVAX]] systems.<br />
<!--<br />
* [[PDP-11/23+]]<br />
* [[PDP-11/53]]<br />
* [[PDP-11/73]]<br />
* [[PDP-11/83]]<br />
* [[PDP-11/93]]<br />
<br />
* [[MicroVAX I]]<br />
* [[VAXstation I]]<br />
* [[MicroVAX II]]<br />
* [[VAXstation II]]<br />
* [[VAXstation 3200/3500 | VAXstation 3200]]<br />
<br />
Some versions of the computers listed above were also available in the BA123 enclosure, or in the [[H9642]] Medium System Cabinet.<br />
<br />
The H9642 Medium System Cabinet contains two BA23 enclosures, one 'Standard' BA23-A, and one 'Expander' BA23-C.<br />
--><br />
==External links==<br />
<br />
* [http://bitsavers.trailing-edge.com/scandocs.trailing-edge.com/micropdp11-volume_2_enclosures-EK-189AA-MG-001.pdf BA213 Enclosure Maintenance] (EK-189AA-MG-001)<br />
<br />
[[Category: DEC Mounting Boxes]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=Talk:MicroVAX_II&diff=33474
Talk:MicroVAX II
2024-02-13T20:53:10Z
<p>Vaxorcist: Created page with "== MicroVAX II a "personal computer"??? == Under no circumstances would I call a MicroVAX II a "personal computer". A MicroVAX I own once served five CNC programmers simultane..."</p>
<hr />
<div>== MicroVAX II a "personal computer"??? ==<br />
Under no circumstances would I call a MicroVAX II a "personal computer".<br />
A MicroVAX I own once served five CNC programmers simultaneously to write and test thousands of programs, including graphical simulations on Tektronik video terminals. There may have been rare cases of exclusive use, but these were the exception, not the rule. The later VAXstation 2000, on the other hand, can certainly be considered the first personal computer VAX. [[User:Vaxorcist|Vaxorcist]] ([[User talk:Vaxorcist|talk]]) 21:52, 13 February 2024 (CET)</div>
Vaxorcist
https://gunkies.org/w/index.php?title=BA123_Enclosure&diff=33473
BA123 Enclosure
2024-02-13T19:53:14Z
<p>Vaxorcist: Fixed typo</p>
<hr />
<div>The '''BA123 Enclosure''' is a [[QBUS]] [[mounting box]] from [[Digital Equipment Corporation|DEC]] which is available a caster-mounted single-[[cabinet]] form. It is the 'bigger brother' to the [[BA23 Enclosure]], and the sibling to the [[BA213 Enclosure]].<br />
<br />
It contains a single, 13-slot, [[DEC card form factor|quad]]-height [[backplane]]; the first 4 slots are [[QBUS#Backplanes|Q/CD]] slots, the next 8 are [[QBUS#Backplanes|Q/Q]]; the final slot is for a signal distribution board, for the connection of [[mass storage]] [[peripheral]]s. That backplane cannot be expanded.<br />
<br />
==BA123 Usage==<br />
<br />
The BA123 enclosure was used for a number of [[PDP-11]], [[MicroVAX]] and [[VAXstation]] systems:<br />
<br />
* [[VAXstation II]]<br />
<!--<br />
* [[PDP-11/23+]]<br />
* [[PDP-11/53]]<br />
* [[PDP-11/73]]<br />
* [[PDP-11/83]]<br />
* [[PDP-11/93]]<br />
<br />
* [[MicroVAX I]]<br />
* [[VAXstation I]]<br />
* [[MicroVAX II]]<br />
* [[VAXstation 3200/3500 | VAXstation 3200]]<br />
<br />
Some versions of the computers listed above were also available in the BA123 enclosure, or in the [[H9642]] Medium System Cabinet.<br />
<br />
The H9642 Medium System Cabinet contains two BA23 enclosures, one 'Standard' BA23-A, and one 'Expander' BA23-C.<br />
--><br />
==External links==<br />
<br />
* [http://bitsavers.trailing-edge.com/scandocs.trailing-edge.com/micropdp11-volume_2_enclosures-EK-188AA-MG-001.pdf BA123 Enclosure Maintenance] (EK-188AA-MG-001)<br />
* [https://vt100.net/mirror/hcps/gmzabmn.pdf VAXstation II Technical Manual, BA123 Enclosure] (AZ-GMZAB-MN)<br />
<br />
[[Category: DEC Mounting Boxes]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=VCB01_Video_Controller&diff=33472
VCB01 Video Controller
2024-02-13T19:50:48Z
<p>Vaxorcist: Fixed typo</p>
<hr />
<div>The '''VCB01 Video Controller''' (also called the '''QVSS''') is a [[QBUS]] [[bit-mapped display]] option, providing [[workstation]] capability for early [[VAXstation]] systems. It uses the [[QBUS#Variable address size|Q22]] version of the QBUS. The bitmap memory (also called video memory), is 256 kB of [[Metal Oxide Semiconductor|MOS]] [[Random Access Memory|RAM]], residing in the Q22-bus address space.<br />
<br />
It is a [[DEC card form factor|quad]]-height module, the '''M7602'''. In the [[VAXstation I]] and [[VAXstation II]], a subset (sometimes called the screen memory) of the bit-mapped video memory is displayed on a 48 cm (19 in) monochrome [[video display|monitor]] (the [[VR100 Monochrome Monitor]]). <br />
<br />
The VCB01 relies on the [[Central Processing Unit|CPU]] to generate all images stored in video memory.<br />
<br />
The VCB01 also provides several basic I/O functions, including:<br />
<br />
* [[Cursor]] controls<br />
* [[Mouse]] interface<br />
* [[Keyboard]] interface<br />
* Primitives for [[VT100]]-style split-screen scrolling<br />
<br />
{{semi-stub}}<br />
<br />
==See also==<br />
<br />
* [[VCB02 Video Controller]]<br />
<br />
==External links==<br />
<br />
* [https://bitsavers.org/pdf/dec/vax/610/EK-VS200-TM-PRE_VAXstation_I_Technical_Reference_Manual_Preliminary_198411.pdf VAXstation I Technical Reference Manual] (EK-VS200-TM-PRE) - the VCB01 is covered in Chapter 3, and elsewhere<br />
* [https://manx-docs.org/collections/hcps/glfabmn.pdf VAXstation II Technical Manual, BA23 Enclosure] (AZ-GLFAB-MN) - the VCB01 is covered in Appendix C<br />
* [https://www.9track.net/simh/video/#vcb01 Video Devices]<br />
<br />
[[Category: QBUS Display Controllers]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=TURBOchannel&diff=33471
TURBOchannel
2024-02-13T19:20:15Z
<p>Vaxorcist: Some details added</p>
<hr />
<div>The '''TURBOchannel''' was developed for and used on the [[VAXstation 4000 series]], the [[DECstation|MIPS-based DECstation series]], and the [[DEC 3000 series| Alpha-based DEC 3000 series]] of [[Digital Equipment Corporation|DEC]] [[workstation]] computers. <br />
<br />
The range of DEC TURBOchannel adapter types includes:<br />
* [[Video]] options: PMAG* MX/CX/PX/PXG Graphics Boards<br />
* [[Small Computer System Interface|SCSI]] options: PMAZ* SCSI controllers<br />
* [[Fiber Distributed Data Interface|FDDI]] option: PMAF TURBOchannel FDDI option board<br />
* [[Ethernet]] option: PMAD 10 Mbps Ethernet controller<br />
* [[Token Ring]] option: PMAT TURBOchannel Token Ring Adapter<br />
* [[VMEbus]] option: PMABV TURBOchannel to VME option board<br />
<br />
Additionally there were numerous TURBOchannel options from third-party vendors.<br />
<br />
{{stub}}<br />
<br />
==External links==<br />
<br />
* [https://en.wikipedia.org/wiki/TURBOchannel Wikipedia article on TURBOchannel]<br />
* [https://manx-docs.org/collections/antonio/dec/MDS-2000-01/cd1/SYS_OPT/TRBOCMG5.PDF EK-TRBOC-MG-005 TURBOchannel Maintenance Guide]<br />
<br />
[[Category: TURBOchannel]]<br />
[[Category: DEC Buses]]<br />
[[Category: Buses]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=TURBOchannel&diff=33459
TURBOchannel
2024-02-13T08:02:48Z
<p>Vaxorcist: /* External links */ Category added</p>
<hr />
<div>The '''TURBOchannel''' was developed for and used on the [[VAXstation 4000 series]], the [[DECstation|MIPS-based DECstation series]], and the [[DEC 3000 series| Alpha-based DEC 3000 series]] of [[Digital Equipment Corporation|DEC]] [[workstation]] computers. <br />
<br />
The range of TURBOchannel adapter types includes:<br />
* [[Video]]<br />
* [[Small Computer System Interface|SCSI]]<br />
* [[Fiber Distributed Data Interface|FDDI]]<br />
* [[Ethernet]]<br />
* [[VMEbus]]<br />
<br />
{{stub}}<br />
<br />
==External links==<br />
<br />
* [https://en.wikipedia.org/wiki/TURBOchannel Wikipedia article on TURBOchannel]<br />
<br />
[[Category: TURBOchannel]]<br />
[[Category: DEC Buses]]<br />
[[Category: Buses]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=TURBOchannel&diff=33458
TURBOchannel
2024-02-13T08:01:56Z
<p>Vaxorcist: Fixed typo</p>
<hr />
<div>The '''TURBOchannel''' was developed for and used on the [[VAXstation 4000 series]], the [[DECstation|MIPS-based DECstation series]], and the [[DEC 3000 series| Alpha-based DEC 3000 series]] of [[Digital Equipment Corporation|DEC]] [[workstation]] computers. <br />
<br />
The range of TURBOchannel adapter types includes:<br />
* [[Video]]<br />
* [[Small Computer System Interface|SCSI]]<br />
* [[Fiber Distributed Data Interface|FDDI]]<br />
* [[Ethernet]]<br />
* [[VMEbus]]<br />
<br />
{{stub}}<br />
<br />
==External links==<br />
<br />
* [https://en.wikipedia.org/wiki/TURBOchannel Wikipedia article on TURBOchannel]<br />
<br />
[[Category: TURBOchannel]]<br />
[[Category: DEC Buses]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=TURBOchannel&diff=33457
TURBOchannel
2024-02-13T08:01:04Z
<p>Vaxorcist: New page "TURBOchannel"</p>
<hr />
<div>The '''TURBOchannel''' was developed for and used on the [[VAXstation 4000 series]], the [[DECstation|MIPS-based DECstation series]], and the [[DEC 3000 series| Alpha-based DEC 3000 series]] of [[Digital Equipment Corporation|DEC]] [[workstation]] computers. <br />
<br />
The range of TURBOchannel adapter types include:<br />
* [[Video]]<br />
* [[Small Computer System Interface|SCSI]]<br />
* [[Fiber Distributed Data Interface|FDDI]]<br />
* [[Ethernet]]<br />
* [[VMEbus]]<br />
<br />
{{stub}}<br />
<br />
==External links==<br />
<br />
* [https://en.wikipedia.org/wiki/TURBOchannel Wikipedia article on TURBOchannel]<br />
<br />
[[Category: TURBOchannel]]<br />
[[Category: DEC Buses]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=VS40X&diff=33355
VS40X
2024-02-09T11:37:17Z
<p>Vaxorcist: Some details added</p>
<hr />
<div>VS40X-PA 8-plane GPX [[graphics]] option module, used in [[DEC]] [[VAXstation 2000]] and [[VAXstation 3100]] computers.<br />
<br />
The VS40X-PA has got 8 planes and supports a [[resolution]] of 1024 x 864 60Hz.<br />
<br />
There is a VS40-MA variant with 4 planes only.<br />
<br />
Both the VS40X-PA and the VS40X-MA are software-compatible with the [[VCB02|VCB02 Video Controller]].<br />
<br />
<br />
[[File:VS40X-PA_8_plane_GPX_graphics_option_module.JPG|thumb|300px|right|VS40X-PA 8-plane GPX graphics option module]]<br />
<br />
{{stub}}<br />
<br />
[[Category: VAXstation Peripherals]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=MORIA&diff=33252
MORIA
2024-02-06T18:06:48Z
<p>Vaxorcist: External links added</p>
<hr />
<div>== Preparations ==<br />
<br />
Get the [https://drive.google.com/file/d/1lOLpKWwBCLkqu2lBl_3Yf_eMdaenTEOX/view?usp=sharing VMS MORIA V4.43 kit].<br />
<br />
The VMS MORIA V4.43 kit includes:<br />
* SIMH VAX-11/750 Linux executable<br />
* SIMH VAX-11/750 Windows executable<br />
* SIMH VAX-11/750 configuration file<br />
* VMS V4.7 RA81 disk image (including VAX PASCAL V2.6)<br />
* VMS MORIA V4.43 RD31 disk image (MORIA sources & executable)<br />
* VMS MORIA V4.43 manual: MORIA-MANUAL.TXT<br />
<br />
Unzip to a directory of your choice.<br />
<br />
== Get it Running ==<br />
<br />
Enter your new MORIA directory and:<br />
<br />
* Linux: <code>./vax750 -q</code><br />
* Windows: <code>run vax750.exe -q</code><br />
<br />
The SIMH VAX-11/750 will boot VMS V4.7:<br />
<br />
(User input in '''bold''' typeface) <br />
<br />
VAX/VMS Version V4.7 28-Oct-1987 13:00<br />
<br />
<br />
<br />
%%%%%%%%%%% OPCOM 5-FEB-2024 17:48:51.47 %%%%%%%%%%%<br />
Logfile has been initialized by operator _OPA0:<br />
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;45<br />
<br />
%MOUNT-I-MOUNTED, MORIA mounted on _DUA1:<br />
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0<br />
SYSTEM job terminated at 5-FEB-2024 17:48:51.65 '''[Enter]''' <br />
<br />
Username: '''MORIA'''<br />
Welcome to VAX/VMS version V4.7<br />
Last interactive login on Monday, 5-FEB-2024 17:48<br />
$<br />
<br />
Start MORIA:<br />
<br />
$ '''MORIA'''<br />
<br />
*********************<br />
** Moria 4.80 **<br />
*********************<br />
COPYRIGHT (c) Robert Alan Koeneke<br />
<br />
Programers : Robert Alan Koeneke / University of Oklahoma<br />
Jimmey Wayne Todd / University of Oklahoma<br />
<br />
Dungeon Master: This file may contain updates and news.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[Press any key to continue, or <Control>-Z to exit]'''[Enter]'''<br />
<br />
Choose a race:<br />
<br />
Name : <br />
Race : <br />
Sex : <br />
Class : <br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Choose a race (? for Help): '''a'''<br />
a) Human b) Half-Elf c) Elf d) Halfling e) Gnome<br />
f) Dwarf g) Half-Orc h) Half-Troll<br />
<br />
Choose a sex:<br />
<br />
Name : <br />
Race : Human<br />
Sex : <br />
Class : <br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Choose a sex (? for Help): '''m'''<br />
m) Male f) Female<br />
<br />
<br />
Choose a class:<br />
<br />
Name : Age : 16 STR : 14 <br />
Race : Human Height : 72 INT : 14 <br />
Sex : Male Weight : 134 WIS : 14 <br />
Class : Social Class : 31 DEX : 15 <br />
CON : 13 <br />
CHR : 14 <br />
<br />
+ To Hit : 0 <br />
+ To Damage: 0 <br />
+ To AC : 0 <br />
Total AC : 0 <br />
Character Background<br />
You are one of several children of a Yeoman. You are a credit to the<br />
family. You have brown eyes, straight auburn hair, and an average<br />
complexion.<br />
<br />
<br />
<br />
Choose a class (? for Help): '''a'''<br />
a) Warrior b) Mage c) Priest d) Rogue e) Ranger<br />
f) Paladin<br />
<br />
<br />
Enter your player's name:<br />
<br />
Name : '''Beginner''' Age : 16 STR : 18/23 <br />
Race : Human Height : 72 INT : 12 <br />
Sex : Male Weight : 134 WIS : 12 <br />
Class : Warrior Social Class : 31 DEX : 17 <br />
CON : 15 <br />
CHR : 13 <br />
<br />
+ To Hit : 3 Level : 1 Max Hit Points : 19 <br />
+ To Damage: 3 Experience : 0 Cur Hit Points : 19 <br />
+ To AC : 1 Gold : 431 Max Mana : 0 <br />
Total AC : 0 Cur Mana : 0 <br />
<br />
<br />
(Miscellaneous Abilities)<br />
Fighting : Very Good Stealth : Bad Perception : Bad<br />
Bows/Throw : Good Disarming : Fair Searching : Poor<br />
Saving Throw: Good Magic Device: Fair Infra-Vision: 0 feet<br />
<br />
<br />
Enter your player's name [press <RETURN> when finished]<br />
<br />
<br />
Press any key to continue, or <Control>-Z to exit: '''[Enter]'''<br />
<br />
Name : Beginner Age : 16 STR : 18/23 <br />
Race : Human Height : 72 INT : 12 <br />
Sex : Male Weight : 134 WIS : 12 <br />
Class : Warrior Social Class : 31 DEX : 17 <br />
CON : 15 <br />
CHR : 13 <br />
<br />
+ To Hit : 3 Level : 1 Max Hit Points : 19 <br />
+ To Damage: 3 Experience : 0 Cur Hit Points : 19 <br />
+ To AC : 1 Gold : 431 Max Mana : 0 <br />
Total AC : 0 Cur Mana : 0 <br />
<br />
<br />
(Miscellaneous Abilities)<br />
Fighting : Very Good Stealth : Bad Perception : Bad<br />
Bows/Throw : Good Disarming : Fair Searching : Poor<br />
Saving Throw: Good Magic Device: Fair Infra-Vision: 0 feet<br />
<br />
<br />
<br />
<br />
[Press any key to continue, or <Control>-Z to exit] '''[Enter]'''<br />
<br />
<br />
You start at the town level now:<br />
<br />
##################################################################<br />
Human #................................................................#<br />
Warrior #..............................................##6##.............#<br />
Novice #..............................................#####.............#<br />
#...........###########......#####.............#####.............#<br />
STR : 18/23 #...........###########......1####.............#####.............#<br />
INT : 12 #...........###########......#####.............#####.............#<br />
WIS : 12 #...........###########........................#####.............#<br />
DEX : 17 #..........>###########..........................................#<br />
CON : 15 #...........##4########..........................................#<br />
CHR : 13 #............@...................................................#<br />
#................................................................#<br />
LEV : 1 #..............#3#.............................######5...........#<br />
EXP : 0 #..............###.............................#######...........#<br />
MANA: 0 #..............###........#####2#####..........#######...........#<br />
MHP : 19 #..............###........###########..........#######...........#<br />
CHP : 19 #..............###........###########..........#######...........#<br />
#..............###........###########..........#######...........#<br />
AC : 0 #..............###........###########..........#######...........#<br />
GOLD: 431 #..............###.............................#######...........#<br />
#................................................................#<br />
##################################################################<br />
Town level<br />
<br />
Your characters' symbol is <code>@</code>.<br />
<br />
You move using the arrow keys on the numeric keypad.<br />
<br />
See the comprehensive manual (MORIA-MANUAL.TXT) for the details of the game. <br />
<br />
To leave the game and save its current state, type '''[Ctrl + z]''' and enter a filename of your choice.<br />
<br />
To leave the game without saving, press '''[Ctrl + z]''' and confirm with '''q'''.<br />
<br />
After leaving the game you return to the VMS operating system prompt.<br />
<br />
To restart MORIA using your saved state, append the file name you chose when saving to the MORIA command, e.g.:<br />
<br />
$ '''MORIA GAME.SAV'''<br />
<br />
Using the MORIA command on its own results in a new game.<br />
<br />
When you are finished, log out from VMS. <br />
<br />
$ '''LOGOUT'''<br />
MORIA logged out at 6-FEB-2024 17:28:29.91<br />
<br />
== Game Management == <br />
<br />
You can reset the game to its original state; i.e.:<br />
* All saved games are lost (your save files remain, but will not work any longer)<br />
* The high score list is emptied<br />
<br />
Log in as "System Manager":<br />
<br />
Username: '''SYSTEM'''<br />
<br />
Password: '''MANAGER047''' (not echoed)<br />
Welcome to VAX/VMS version V4.7<br />
Last interactive login on Monday, 5-FEB-2024 17:48<br />
$ '''@RESET_MORIA'''<br />
<br />
== Graceful Shutdown of the VMS Operating System ==<br />
<br />
Although the VMS operating system is considered to be very robust and can withstand a lot of abuse, you are still recommended to shut it down properly.<br />
<br />
Log in as "System Manager" (see above).<br />
<br />
Run a graceful shutdown:<br />
<br />
$ '''SHUTDOWN'''<br />
<br />
== External links ==<br />
* [https://github.com/dungeons-of-moria/vms-moria Moria - VMS Pascal source code]<br />
* [https://umoria.org/highlights/ Moria Release Highlights]<br />
<br />
[[Category: SIMH Tutorials]]<br />
[[Category:Games]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=MORIA&diff=33246
MORIA
2024-02-06T16:36:48Z
<p>Vaxorcist: New page: "MORIA"</p>
<hr />
<div>== Preparations ==<br />
<br />
Get the [https://drive.google.com/file/d/1lOLpKWwBCLkqu2lBl_3Yf_eMdaenTEOX/view?usp=sharing VMS MORIA V4.43 kit].<br />
<br />
The VMS MORIA V4.43 kit includes:<br />
* SIMH VAX-11/750 Linux executable<br />
* SIMH VAX-11/750 Windows executable<br />
* SIMH VAX-11/750 configuration file<br />
* VMS V4.7 RA81 disk image (including VAX PASCAL V2.6)<br />
* VMS MORIA V4.43 RD31 disk image (MORIA sources & executable)<br />
* VMS MORIA V4.43 manual: MORIA-MANUAL.TXT<br />
<br />
Unzip to a directory of your choice.<br />
<br />
== Get it Running ==<br />
<br />
Enter your new MORIA directory and:<br />
<br />
* Linux: <code>./vax750 -q</code><br />
* Windows: <code>run vax750.exe -q</code><br />
<br />
The SIMH VAX-11/750 will boot VMS V4.7:<br />
<br />
(User input in '''bold''' typeface) <br />
<br />
VAX/VMS Version V4.7 28-Oct-1987 13:00<br />
<br />
<br />
<br />
%%%%%%%%%%% OPCOM 5-FEB-2024 17:48:51.47 %%%%%%%%%%%<br />
Logfile has been initialized by operator _OPA0:<br />
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;45<br />
<br />
%MOUNT-I-MOUNTED, MORIA mounted on _DUA1:<br />
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0<br />
SYSTEM job terminated at 5-FEB-2024 17:48:51.65 '''[Enter]''' <br />
<br />
Username: '''MORIA'''<br />
Welcome to VAX/VMS version V4.7<br />
Last interactive login on Monday, 5-FEB-2024 17:48<br />
$<br />
<br />
Start MORIA:<br />
<br />
$ '''MORIA'''<br />
<br />
*********************<br />
** Moria 4.80 **<br />
*********************<br />
COPYRIGHT (c) Robert Alan Koeneke<br />
<br />
Programers : Robert Alan Koeneke / University of Oklahoma<br />
Jimmey Wayne Todd / University of Oklahoma<br />
<br />
Dungeon Master: This file may contain updates and news.<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
[Press any key to continue, or <Control>-Z to exit]'''[Enter]'''<br />
<br />
Choose a race:<br />
<br />
Name : <br />
Race : <br />
Sex : <br />
Class : <br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Choose a race (? for Help): '''a'''<br />
a) Human b) Half-Elf c) Elf d) Halfling e) Gnome<br />
f) Dwarf g) Half-Orc h) Half-Troll<br />
<br />
Choose a sex:<br />
<br />
Name : <br />
Race : Human<br />
Sex : <br />
Class : <br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Choose a sex (? for Help): '''m'''<br />
m) Male f) Female<br />
<br />
<br />
Choose a class:<br />
<br />
Name : Age : 16 STR : 14 <br />
Race : Human Height : 72 INT : 14 <br />
Sex : Male Weight : 134 WIS : 14 <br />
Class : Social Class : 31 DEX : 15 <br />
CON : 13 <br />
CHR : 14 <br />
<br />
+ To Hit : 0 <br />
+ To Damage: 0 <br />
+ To AC : 0 <br />
Total AC : 0 <br />
Character Background<br />
You are one of several children of a Yeoman. You are a credit to the<br />
family. You have brown eyes, straight auburn hair, and an average<br />
complexion.<br />
<br />
<br />
<br />
Choose a class (? for Help): '''a'''<br />
a) Warrior b) Mage c) Priest d) Rogue e) Ranger<br />
f) Paladin<br />
<br />
<br />
Enter your player's name:<br />
<br />
Name : '''Beginner''' Age : 16 STR : 18/23 <br />
Race : Human Height : 72 INT : 12 <br />
Sex : Male Weight : 134 WIS : 12 <br />
Class : Warrior Social Class : 31 DEX : 17 <br />
CON : 15 <br />
CHR : 13 <br />
<br />
+ To Hit : 3 Level : 1 Max Hit Points : 19 <br />
+ To Damage: 3 Experience : 0 Cur Hit Points : 19 <br />
+ To AC : 1 Gold : 431 Max Mana : 0 <br />
Total AC : 0 Cur Mana : 0 <br />
<br />
<br />
(Miscellaneous Abilities)<br />
Fighting : Very Good Stealth : Bad Perception : Bad<br />
Bows/Throw : Good Disarming : Fair Searching : Poor<br />
Saving Throw: Good Magic Device: Fair Infra-Vision: 0 feet<br />
<br />
<br />
Enter your player's name [press <RETURN> when finished]<br />
<br />
<br />
Press any key to continue, or <Control>-Z to exit: '''[Enter]'''<br />
<br />
Name : Beginner Age : 16 STR : 18/23 <br />
Race : Human Height : 72 INT : 12 <br />
Sex : Male Weight : 134 WIS : 12 <br />
Class : Warrior Social Class : 31 DEX : 17 <br />
CON : 15 <br />
CHR : 13 <br />
<br />
+ To Hit : 3 Level : 1 Max Hit Points : 19 <br />
+ To Damage: 3 Experience : 0 Cur Hit Points : 19 <br />
+ To AC : 1 Gold : 431 Max Mana : 0 <br />
Total AC : 0 Cur Mana : 0 <br />
<br />
<br />
(Miscellaneous Abilities)<br />
Fighting : Very Good Stealth : Bad Perception : Bad<br />
Bows/Throw : Good Disarming : Fair Searching : Poor<br />
Saving Throw: Good Magic Device: Fair Infra-Vision: 0 feet<br />
<br />
<br />
<br />
<br />
[Press any key to continue, or <Control>-Z to exit] '''[Enter]'''<br />
<br />
<br />
You start at the town level now:<br />
<br />
##################################################################<br />
Human #................................................................#<br />
Warrior #..............................................##6##.............#<br />
Novice #..............................................#####.............#<br />
#...........###########......#####.............#####.............#<br />
STR : 18/23 #...........###########......1####.............#####.............#<br />
INT : 12 #...........###########......#####.............#####.............#<br />
WIS : 12 #...........###########........................#####.............#<br />
DEX : 17 #..........>###########..........................................#<br />
CON : 15 #...........##4########..........................................#<br />
CHR : 13 #............@...................................................#<br />
#................................................................#<br />
LEV : 1 #..............#3#.............................######5...........#<br />
EXP : 0 #..............###.............................#######...........#<br />
MANA: 0 #..............###........#####2#####..........#######...........#<br />
MHP : 19 #..............###........###########..........#######...........#<br />
CHP : 19 #..............###........###########..........#######...........#<br />
#..............###........###########..........#######...........#<br />
AC : 0 #..............###........###########..........#######...........#<br />
GOLD: 431 #..............###.............................#######...........#<br />
#................................................................#<br />
##################################################################<br />
Town level<br />
<br />
Your characters' symbol is <code>@</code>.<br />
<br />
You move using the arrow keys on the numeric keypad.<br />
<br />
See the comprehensive manual (MORIA-MANUAL.TXT) for the details of the game. <br />
<br />
To leave the game and save its current state, type '''[Ctrl + z]''' and enter a filename of your choice.<br />
<br />
To leave the game without saving, press '''[Ctrl + z]''' and confirm with '''q'''.<br />
<br />
After leaving the game you return to the VMS operating system prompt.<br />
<br />
To restart MORIA using your saved state, append the file name you chose when saving to the MORIA command, e.g.:<br />
<br />
$ '''MORIA GAME.SAV'''<br />
<br />
Using the MORIA command on its own results in a new game.<br />
<br />
When you are finished, log out from VMS. <br />
<br />
$ '''LOGOUT'''<br />
MORIA logged out at 6-FEB-2024 17:28:29.91<br />
<br />
== Game Management == <br />
<br />
You can reset the game to its original state; i.e.:<br />
* All saved games are lost (your save files remain, but will not work any longer)<br />
* The high score list is emptied<br />
<br />
Log in as "System Manager":<br />
<br />
Username: '''SYSTEM'''<br />
<br />
Password: '''MANAGER047''' (not echoed)<br />
Welcome to VAX/VMS version V4.7<br />
Last interactive login on Monday, 5-FEB-2024 17:48<br />
$ '''@RESET_MORIA'''<br />
<br />
== Graceful Shutdown of the VMS Operating System ==<br />
<br />
Although the VMS operating system is considered to be very robust and can withstand a lot of abuse, you are still recommended to shut it down properly.<br />
<br />
Log in as "System Manager" (see above).<br />
<br />
Run a graceful shutdown:<br />
<br />
$ '''SHUTDOWN'''<br />
<br />
<br />
== See Also ==<br />
<br />
[[Category: SIMH Tutorials]]<br />
[[Category:Games]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=TREK7&diff=33154
TREK7
2024-02-01T17:18:37Z
<p>Vaxorcist: /* External links */ Category "SIMH Tutorials" added</p>
<hr />
<div>== History ==<br />
<br />
The Star Trek simulation game '''TREK7''' was written in [[FORTRAN]] by Donald M. Ecclestone in the early 70ties for the [[PDP-10]].<br />
<br />
The game was ported to [[VAX]] computers running [[VMS]] in 1978 by the author with the help of Dan Gahlinger.<br />
<br />
Innumerable four-player games were played on the VAX computer systems at UWO (Western University) in London Ontario, Canada, for the next few years.<br />
<br>The game was run on the UWO [[VAX-11/750]] and [[VAX-11/782]] systems.<br />
<br />
By 1983 Donald had left the University, bequeathing the code to Dan.<br />
<br />
For some years TREK7 fell into a deep slumber until in 1993 Dan Gahlinger decided to revive it.<br />
<br />
== Characteristics ==<br />
<br />
TREK7 was written for [[Teletype]] terminals, which determines some of the characteristics of the game.<br><br />
[[Video terminal]]s, e.g. the [[VT52]] were just in the ascendent back then, and most computers still had their noisily and slow mechanical printing terminals.<br />
<br />
TREK7 input is possible in capitals only.<br />
To save time and paper, game output was limited to the bare necessities. The game map is printed only on request and you can even reduce its size at will.<br />
<br />
The game is just one programm/process enabling up to four players to take their turns one after another.<br />
<br />
A typical TREK7 ship command sequence consists of:<br />
<br />
* Optionally informing yourself ("Get ship information": <code>'''IN''' <RET></code>),<br />
* choosing an action ("Set course to coordinates 20,55": <code>'''CO''' <RET> '''2055''' <RET></code>),<br />
* starting the action ("Start moving": <code>'''GO''' <RET> '''M''' <RET></code>), and finally<br />
* receiving a report of incidents (if any).<br />
<br />
When it's not your turn you always get informed about the results of the other players actions, too. <br />
<br />
ENTERPRISE COMMAND: '''IN'''<br />
DEFLECTORS POSITION<br />
ENTERPRISE 100.0 (60,38) CREW REMAINING= 430<br />
KLINGON STARBASE 1 300.0 (49,11)<br />
ORION PRIVATEER UNKNOWN ( 6,29)<br />
DOOMSDAY MACHINE UNKNOWN (44,24)<br />
<br />
ENTERPRISE COMMAND: '''CO'''<br />
ENTER WARP FACTOR - BETWEEN 0 AND 10.0: 4<br />
ENTER TARGET COORDINATES: '''2055'''<br />
<br />
ENTERPRISE COMMAND: '''GO'''<br />
ENTER COMMAND STRING (M,P,T,B,Y,D,C,H FOR HELP)<br />
'''M'''<br />
ENGINE TEMP. = 4000 DEGREES<br />
DOOMSDAY MACHINE HAS COLLIDED WITH A MINE - DAMAGE REPORT-<br />
DAMAGE FACTOR 3- MINOR STRUCTURAL DAMAGE<br />
- THERE IS A DENT IN THE VESSEL <br />
<br />
PLEASE STANDBY WHILE THE POTEMPKIN TAKES ITS TURN<br />
<br />
== Status Quo ==<br />
<br />
Seven FORTRAN sources and two data files with nearly 7,000 lines of code are the framework of TREK7.<br />
<br />
The reconstruction of the VAX/VMS version of TREK7 from a transcription and a printout has recently been finished. <br />
<br />
The first step was to fix the sources so that the games compiles without compiler errors. <br />
<br />
The work so far was done by Dan Gahlinger using his stored printouts, because no more known versions on computer readable media were available by then.<br />
<br />
In September 2022 some crazy VAX guy (me) was looking for some interesting software to be run on his simh [[Installing VMS V2.0 on SIMH | VAX-11/750 under VMS V2.0]].<br />
By chance (asking Google) I found the TREK7 FORTRAN sources at sourceforge and contacted the publisher Dan Gahlinger.<br />
<br />
Dan explained the problems still present in TREK7 and I started refreshing my FORTRAN.<br />
<br />
It's been more than 30 year since I last used my knowledge of FORTRAN for some serious work.<br />
<br>But FORTRAN was the first programming language I learned, and more and more returned when I struggled with the TREK7 sources.<br />
<br />
The following manuals were of a great help:<br />
* AA-D035C-TE VAX-11 FORTRAN User's Guide<br />
* AA-D034C-TE VAX-11 FORTRAN Language Reference Manual<br />
* [http://bitsavers.org/pdf/dec/vax/vms/2.0/AA-D026B-TE_VAX_VMS_2.0_Symbolic_Debugger_Reference_198003.pdf AA-D026B-TE VAX-11 Symbolic Debugger Reference Manual]<br />
<br />
After detecting and fixing more than 60 bugs (mostly caused by transcription errors) in a second step, the game is playable again now.<br />
<br />
One of the most obstinate bugs was the "divide by zero" problem that has been plaguing the code for decades hindering any successful game.<br />
<br />
There still may be an unknown number of minor bugs, but TREK7 runs fine now in both single-user and multi-user mode. <br />
<br />
The testing platform is a SIMH VAX-11/750 running VMS V2.0 and VAX FORTRAN V2.4<br />
<br />
== Features ==<br />
<br />
* Multi-user<br />
* Up to four manually-operated ships (controlled by one to four terminals on the computer)<br />
* Zero to eight computer-operated enemies <br> (You can decide not to include any enemy to get accustomed to the game):<br />
** Klingon warship<br />
** Romulan warship<br />
** Gorn warship<br />
** Tholian warship<br />
** Orion ship<br />
** Doomsday machine<br />
** Kzinti warship<br />
** Moonbase Alpha<br />
* Starbases<br />
* Stars<br />
* Ion storms<br />
* Weaponry<br />
** Phaser beams<br />
** Photon torpedoes<br />
** Mines<br />
** Deflector beams<br />
** Tractor beams<br />
* Boarding<br />
* Transfer, Repair and Resupply<br />
* Information, Navigation and Travelling<br />
** Info function<br />
** Playing area map<br />
** Course<br />
** Warp drive<br />
* Communication<br />
** Radio<br />
** Jamming<br />
<br />
There's some time-restricting code in TREK7 (routine <code>TIMEX</code> in module <code>TREKD.FOR</code>) to prevent students from running it during class hours, but normally it's left disabled:<br />
<br />
IN ACCORDANCE WITH THE UNIVERSITY COMPUTING COUNCIL'S POLICY<br />
(SEE HLP:RESTRI.MEM), TREK7 CANNOT BE ACCESSED ON WEEKDAYS<br />
BETWEEN THE HOURS OF 1000 AND 1700.<br />
COME BACK TONIGHT AND PLAY IT WITHOUT THESE RESTRICTIONS.<br />
<br />
== TREK7 Ports ==<br />
<br />
* TREK7 PDP-10 FORTRAN<br />
* TREK7 VAX FORTRAN<br />
* TREK7 PDP-8 ALGOL 60 (this is a rumour from England)<br />
* TREK7 Linux FORTRAN (single user only)<br />
<br />
== Debugging, Alterations and Additions ==<br />
<br />
=== Comments ===<br />
<br />
The process of detecting and fixing bugs required some understanding of how the TREK7 FORTRAN source code works. <br />
The original sources contained very few comments that did not really help. <br />
<br />
So a lot of comments had to be added to comprehend this marvelous piece of software.<br />
All added comments are tagged with <code>CV</code> in the first two columns of each line so that they can easily be recognized and removed if desired.<br />
<br />
About 50% of the code is commented now, of which about 80 to 90% is ensured to be commented reasonably ok.<br />
The rest is more or less intelligent (or pure) guesswork.<br />
<br />
Some obscure sections are left over for the curiuos and knowing reader ;-)) <br />
<br />
Additional aids are (separately kept) lists of subroutines, common/local variables and their use; about 300 all together.<br />
<br />
=== Random Number Generator ===<br />
<br />
I could not resist to add a little enhancement to TREK7 - it is fully revertible if anyone cares.<br />
<br />
The random number generator originally included in TREK7 relies on a random number between 1-32767 asked from the player at the start of a game. <br />
If all subsequent player actions are recorded, the course of the game is fully reproducible.<br />
This is useful for testing and debugging, but not optimal for game fun.<br />
<br />
I added another source of randomness (the actual system time in hundredth of a second since last midnight, see: <code>TREKA.FOR</code>), which makes it virtually impossible to reproduce the course of the game.<br />
<br />
=== Full Size Map ===<br />
<br />
Opposed to the TREK7 standard, which limits the map size to 15x15 (and even less if ones ships sensors are damaged), I added a possibility to have a full size (60x60) map.<br />
<br />
=== Ideas not yet realized ===<br />
<br />
Some ideas (useful, interesting or pointless):<br />
* Log / Replay functions - logging all actions to a file / replaying saved game actions<br />
* Snapshot / Resume functions - saving all current game status parameters / restoring saved game status parameters <br />
* Time limits - making the game continue without your action when your time to react is over <br />
* Variable map size<br />
* Computer vs. computer mode <br />
<br />
== How to run TREK7 ==<br />
<br />
* [[Installing VMS V2.0 on SIMH]]<br />
* [https://drive.google.com/drive/folders/1VEM0MzCLDsv5WoX1XTqrZ0m901YdDW8p?usp=sharing| Get the TREK7 kit]<br />
<br />
==TREK7 Multi-Player Mode over Network==<br />
<br />
Thanks to SIMH you can use the multi-player mode of TREK7 over TCP/IP, be it local or Internet.<br />
<br />
For playing over Internet you must allow ingoing TELNET to the computer hosting the SIMH VAX.<br />
<br />
Your team players have to wait for the SIMH VAX-11/750 to finish booting.<br />
Tell them to connect when the time has come and that they shall not log in.<br />
<br />
Then they can start their PuTTY sessions one after another (in the order that you will assign the ships to the terminals).<br />
<br />
Your team players will receive a messages like this:<br />
<br />
Connected to the VAX 11/750 simulator DZ device, line 1<br />
<br />
Once they all have connected, you can break out of SIMH using <code><CTRL-e></code> and see the established connections:<br />
<br />
$ <CTRL-e><br />
Simulation stopped, PC: 80007104 (BRB 80007104)<br />
sim> show dz conn<br />
line1 : Connection from IP address 127.0.0.1<br />
Connection [127.0.0.1]:6666->[127.0.0.1]:37943<br />
Connected 00:00:18<br />
Telnet protocol<br />
line 2: Connection from IP address 127.0.0.1<br />
Connection [127.0.0.1]:6666->[127.0.0.1]:45899<br />
Connected 00:01:57<br />
Telnet protocol<br />
sim><br />
<br />
<br />
Don't break out of SIMH too early because your team players will not be able to connect while SIMH is stopped.<br />
<br />
Tell SIMH to continue using <code>cont</code> and start TREK7:<br />
<br />
sim> cont<br />
run trek7<br />
<br />
DONALD ECCLESTONE (C)1979 AND DAN GAHLINGER (C)1993 PRESENT<br />
<br />
T H E H O L Y T E R R O R - T R E K 7<br />
<br />
<br />
<br />
TYPE IN A RANDOM NUMBER BETWEEN 1-32767<br />
<br />
Have fun!<br />
<br />
<br />
== TREK7 Manual ==<br />
<br />
Most of the original TREK7 manual is preserved except for a few pages of the introduction:<br />
<br />
'''<u>TREK7 MANUAL VAX/VMS</u>'''<br />
DONALD M. ECCLESTONE 17-FEB-77<br />
COPYRIGHT © 1999, DAN GAHLINGER, ALL RIGHTS RESERVED.<br />
ULLI HÖLSCHER 15-OCT-2022<br />
<br />
'''<u>FOREWORD</u>'''<br />
<br />
<span style="color:red>THIS MANUAL WAS INITIALLY WRITTEN FOR TREK7 RUN ON PDP-10 <br />
COMPUTERS. THE PORT OF TREK7 TO VAX COMPUTERS RUNNING THE VMS <br />
OPERATING SYSTEM CAUSED A FEW ALTERATIONS. CHANGES, ADDITIONS,<br />
COMMENTS AND NOTES ADDED TO THE ORIGINAL MANUAL ARE FORMATTED IN<br />
RED.</span><br />
<br />
'''<u>DISCLAIMER</u>'''<br />
<br />
EVEN THOUGH I LIKED THE TV SHOW, I DISCLAIM THE ACCUSATION<br />
THAT I AM A TREKKIE. I DO NOT OWN A SINGLE PAIR OF VULCAN EARS, OR<br />
EVEN A POSTER OF LEONARD NIMOY. NOT ONLY THAT, BUT I HAVE<br />
COMMITTED TREKKIE SACRILEGE - THE ENTERPRISE CAN ACTUALLY BE<br />
DEFEATED.<br />
<br />
'''<u>INTRODUCTION</u>'''<br />
<br />
THE PROGRAM TREK7 SIMULATES A BATTLE BETWEEN SPACESHIPS, WHERE<br />
THE PEOPLE, WEAPONRY, AND SHIP ARE BASED UPON THE FUND ON THE<br />
TELEVISION SERIES ’STAR TREK’. THERE CAN BE UP TO FOUR PLAYERS IN<br />
A GAME AND THE PLAYERS HAVE THE CHOICE OF COMMANDING THE FOLLOWING<br />
SHIP:<br />
<br />
ENTERPRISE (UNITED FEDERATION OF PLANETS) (NCC-1701)<br />
POTEMPKIN (UNITED FEDERATION OF PLANETS) (NCC-1711)<br />
HAVOC (IMPERIAL KLINGON EMPIRE) (D-53)<br />
CARNAGE (IMPERIAL KLINGON EMPIRE) (D-73)<br />
<br />
THE ENTERPRISE AND POTEMPKIN ARE OF THE MK-IX HEAVY CRUISER<br />
CLASS WHICH IS THE MAIN ELEMENT OF THE U.F.P. PEACE-KEEPING<br />
FORCES. EACH SHIP HAS A CREW OF 430 AND TWO WEAPONS SYSTEMS:<br />
PHASER BEAMS AND PHOTON TORPEDOES.<br />
<br />
THE HAVOC AND CARNAGE ARE THE KLINGON EMPIRE EQUIVALENT OF THE<br />
ENTERPRISE AND POTEMPKIN AND ARE OF THE KL-VII BATTLE CRUISER<br />
CLASS D7. EACH SHIP HAS A CREW OF 430 AND TWO WEAPONS SYSTEMS:<br />
PHASER BEAMS AND DISRUPTOR BOLTS.<br />
<br />
A PHASER BEAMS IS A "BEAM OF ENERGY SIMILAR EMITTED BY A LASER<br />
BUT OF A PULSATING NATURE THAT CAN BE PHASED TO INTERFERE OR<br />
INTERACT WITH THE WAVE PATTERN OF ANY MOLECULAR FORM"(1). THE<br />
PHASER BANKS HAVE 6000 UNITS OF ENERGY THAT CAN BE USED TO EMIT A<br />
PHASER BEAM OF VARIABLE INTENSITY. THE INTENSITY IS PROPORTIONAL<br />
TO THE AMOUNT OF ENERGY USED. ALTHOUGH A PHASER BEAM HAS A<br />
THEORETICALLY UNLIMITED RANGE, THE FURTHER AWAY THE TARGET IS, THE<br />
LESS PRECISE THE BEAM AND THE PROBABILITY OF A MISS INCREASES.<br />
FURTHERMORE, AS DISTANCE INCREASES, THE INTENSITY OF THE BEAM<br />
DECREASES.<br />
<br />
(1) S. E. WHITFIELD, G. RODDENBERRY, ‘THE MAKING OF STAR TREK,<br />
(NEW YORK, 1972), P. 193<br />
<br />
TREK7 – DONALD M. ECCLESTONE. 17-FEB-79 – PRINTED @UWO ON 26-APR-1984 00:49<br />
<br />
<span style="color:red>[SOME TEXT MISSING FROM THE INTRODUCTION OF THE ORIGINAL MANUAL]</span><br />
<br />
THE SHIPS ARE ALSO EQUIPPED WITH 12 PHOTON TORPEDOES (ON<br />
KLINGON SHIPS THEY ARE CALLED DISRUPTOR BOLTS BUT THEY’RE BOTH<br />
EQUIVALENT WEAPONS), "ENERGY PODS OF MATTER AND ANTI-MATTER<br />
CONTAINED AND HELD TEMPORARILY SEPARATED IN A MAGNO-PHOTON FORCE<br />
FIELD". ONE PHOTON TORPEDO IS APPROXIMATELY EQUIVALENT TO A<br />
600‑UNIT PHASER BEAM. THE TORPEDO HAS A RANGE OF 10 UNITS AND IT<br />
DETONATES IF IT HITS AN OBSTRUCTING OBJECT.<br />
<br />
FOR DEFENCE, THE SHIPS HAVE DEFLECTOR SHIELDS. THE SHIELDS ARE<br />
MADE OF ENERGY AND THEY DEFLECT THE MAIN PART OF ENEMY FIRE AWAY<br />
FROM THE SHIP, EVEN THOUGH A PART OF THE FIRE DOES GET THROUGH.<br />
UNDER REPEATED HITS THE SHIELDS BECOME LESS EFFICIENT RESULTING IN<br />
GREATER DAMAGE. WHEN THE SHIELDS BECOME ZERO (IE. CEASE TO EXIST),<br />
IT WILL TAKE ONLY A SMALL EFFORT ON THE PART OF THE ENEMY TO CAVE<br />
IN THE COMPARATIVELY FRAGILE HULLS OF YOUR STARSHIP.<br />
<br />
THE GAME OF TREK7 IS PLAYED ON A 60 X 60 GRID OF SPACES,<br />
THROUGHOUT WHICH ARE RANDOMLY SCATTERED STARS AND ION STORMS. TO<br />
MANOEUVRE THROUGH ALL THIS, THE SHIPS POSSESS WARP DRIVE ENGINES<br />
(CALLED S-2 GRAF UNITS BY KLINGONS) WHICH PROPEL THEM AT GREATER-<br />
THAN-LIGHT SPEEDS. THE UNIT OF SPEED USED IS THE ’WARP’. WARP 1<br />
PROPELS THE SHIP AT THE SPEED OF LIGHT AND COVERS 1 SPACE (OR<br />
UNIT) ON THE 60 X 60 GRID. WARP 2 COVERS 2 UNITS. THE SHIPS’<br />
MAXIMUM SPEEDS ARE WARP 10 (WHICH COVERS 10 UNITS). <span style="color:red>USING WARP<br />
LESS THAN 1 DOES NOT MOVE A SHIP AT ALL.</span><br />
<br />
THE PLAYER HAS HIS CHOICE OF ENEMIES AND FOR HIS OPPONENT(S).<br />
HE CAN SELECT AMONGST KLINGON, ROMULAN, THOLIAN, GORN, ORION, AND<br />
KZINTI WARSHIPS, A DOOMSDAY MACHINE, AND MOONBASE ALPHA. THE<br />
COMPUTER CONTROLS THESE OPPOSING WARSHIPS. THE PLAYER OF COURSE,<br />
HAS THE OPTION OF SELECTING NO ENEMIES AT ALL <span style="color:red>BY ANSWERING ’N’<br />
(= NONE) WHEN ASKED FOR THE OPPONENTS HE WISHES TO FIGHT</span>, OR CAN<br />
FIGHT OTHER PLAYER’S SHIPS OR ENEMY STARBASES.<br />
<br />
'''<u>HOW TO PLAY THE GAME</u>'''<br />
<br />
'''1. <u>MANUALLY-OPERATED SHIPS</u>'''<br />
<br />
YOU’LL BE ASKED TO ENTER A STRING OF CHARACTERS INDICATING<br />
WHICH SHIPS YOU OR OTHER PLAYERS WISH TO COMMAND IN THE GAME. FOR<br />
EXAMPLE ENTERING ’ECH’ WOULD GIVE YOU THE ENTERPRISE, CARNAGE, AND<br />
HAVOC.<br />
<br />
AFTER THIS, IF YOU ARE PLAYING ANY SHIPS OTHER THAN THE<br />
ENTERPRISE, YOU WILL BE ASKED FOR THE TERMINALS TO USE. <span style="color:red>TYPE A<br />
BLANK ’ ’ FOR YOUR OWN TERMINAL AND THE TERMINAL NAMES (EG.<br />
’TTA1:', ’TTA2:’, ETC.) FOR THE OTHER SHIPS ONE AFTER ANOTHER.<br />
THESE TERMINALS MUST BE SWITCHED ON, BUT NOT LOGGED IN TO,<br />
OTHERWISE THE GAME WILL ABORT WITH AN ERROR MESSAGE.</span><br />
<br />
'''2. <u>COMPUTER-OPERATED ENEMIES</u>'''<br />
<br />
NEXT, YOU WILL BE ASKED FOR THE OPPONENTS YOU WISH TO FIGHT.<br />
TYPE IN A STRING OF CHARACTERS STANDING FOR THE SHIPS YOU WANT TO<br />
PLAY. (EG. ’GOD’ WILL GIVE YOU THE GORN WARSHIP, ORION PRIVATEER,<br />
AND A DOOMSDAY MACHINE.) YOU CANNOT PLAY MORE THAN ONE SHIP OF THE<br />
SAME NATIONALITY AT THE SAME TIME, SO TYPING ’KKK’ WILL GIVE ONLY<br />
ONE KLINGON WARSHIP, NOT THREE. EACH MANUAL-OPERATED SHIP IS<br />
EQUIPPED SO THAT IT CAN HANDLE AROUND TWO COMPUTER-OPERATED ENEMY<br />
SHIPS AT ONE TIME, UNLESS YOU PLAY THE DOOMSDAY MACHINE, IN WHICH<br />
CASE PRAYER IS THE BEST ANSWER. IF YOU HAVE A LUCKY STREAK, YOU<br />
MAY BE ABLE TO TAKE ON THREE OPPONENTS. IF YOU PLAY THE KZINTI YOU<br />
WILL BE ASKED TO ENTER PARAMETERS REGARDING THEIR STRENGTH AND<br />
STRATEGY. NOTE THAT ALL COMPUTER-OPERATED ENEMIES WILL FIGHT ALL<br />
MANUALLY-OPERATED SHIPS REGARDLESS OF NATIONALITY. IF YOU’RE A<br />
BEGINNER I SUGGEST YOU PLAY JUST THE KLINGONS TO GET A FEEL FOR<br />
THE GAME.<br />
<br />
HERE IS A RUNDOWN OF THE ENEMIES YOU CAN FIGHT:<br />
<br />
'''2.1 <u>KLINGONS</u>'''<br />
<br />
THE KLINGON WARSHIP IS COMMANDED BY CAPT. JAMES T. KIRK’S<br />
ARCH-RIVAL, CAPT. KOLOTH OF THE IMPERIAL KLINGON SPACE FLEET. HIS<br />
D6 CLASS BATTLE CRUISER IS EQUIPPED WITH DEFLECTOR SHIELDS, PHASER<br />
BANKS (WHICH FIRE BETWEEN 450 AND 1100 UNITS), AND S-2 GRAF UNITS<br />
WHICH CAN PROPEL HIS SHIP BETWEEN WARP 7 AND 9. HIS STRATEGY IS TO<br />
STICK BY YOUR SIDE AND ATTACK.<br />
<br />
'''2.2 <u>ROMULANS</u>'''<br />
<br />
THE ROMULAN WARSHIP IS MODELLED AFTER THE KLINGON D6 CLASS<br />
BATTLE CRUISER AND IS COMMANDED BY COMMANDER TAL. FOR THE SHIP’S<br />
DEFENCE, IT HAS DEFLECTOR SHIELDS AND A CLOAKING DEVICE WHICH CAN<br />
RENDER THE SHIP INVISIBLE TO YOUR SHIP’S SENSORS UNLESS IT IS<br />
WITHIN 5 UNITS OF YOUR SHIP. ALSO, THE LOWER THE ROMULAN’S<br />
DEFLECTORS GET (IE. THE MORE DAMAGE THEY RECEIVE), THE GREATER THE<br />
CHANCE THAT THEIR CLOAKING DEVICE WILL BREAK DOWN FOR A TIME.<br />
<br />
FOR OFFENSIVE WEAPONS THE SHIP IS EQUIPPED WITH A MOLECULAR<br />
IMPLOSION BEAM WHICH FATIGUES METALS CAUSING CRYSTALS TO LOSE<br />
COHESION AND COLLAPSE. IT IS EQUIVALENT TO A 300 - 1000 UNIT<br />
PHASER BEAM. THE ROMULANS ARE INITIALLY NEUTRAL IN THE GAME, NOT<br />
FIGHTING UNLESS YOU COME WITHIN 10 UNITS OF THEM OR IF YOU FIRE AT<br />
THEM.<br />
<br />
WHEN THE ROMULANS ATTACK, THEY DO NOT PROCEED DIRECTLY TO YOUR<br />
SHIP LIKE KLINGONS. INSTEAD THEY TAKE A BEARING ON YOU, THEN GO ON<br />
A RANDOM COURSE WITHIN 90 DEGREES OF THAT BEARING. THIS EMPLOYS<br />
THE FULL POTENTIAL OF THEIR CLOAKING DEVICE. THE ROMULAN RETREAT<br />
WHEN WHEN YOUR SHIELD EXCEEDS THEIRS BY 20 UNITS OR MORE. THEIR RETREAT<br />
IS SIMILAR TO THEIR ATTACK - THEY TAKE A BEARING DIRECTLY AWAY<br />
FROM YOU AND TRAVEL ALONG A RANDOM PATH WITHIN 90 DEGREES OF THAT<br />
BEARING. THE ROMULAN SHIP HAS A SPEED OF WARP 7 TO 9.<br />
<br />
'''2.3 <u>GORNS</u>'''<br />
<br />
A GORN CAN BE SUMMED UP IN FOUR WORDS - LARGE, REPTILLIAN,<br />
GREEN AND MEAN. THEY ARE BELIEVED TO ORIGINATE FROM A SINGLE<br />
PLANET OUTSIDE THE TERRITORIES OF THE FEDERATION AND KLINGON<br />
EMPIRE. THE GORN SHIP IS EQUIPPED WITH DEFLECTORS, PHASERS (OF<br />
POWER RANGING FROM 350 TO 900 UNITS) AND HAS A MAXIMUM SPEED OF<br />
WARP 11. THE GORN STRATEGY IS TO RETREAT UNTIL THEY HAVE THE UPPER<br />
HAND (UNTIL THEIR SHIELDS ARE AT LEAST 25 UNITS ABOVE YOURS), THEN<br />
ATTACK SHOWING NO MERCY.<br />
<br />
'''2.4 <u>THOLIANS</u>'''<br />
<br />
THOLIAN WARSHIPS ARE BLUE-GREEN AND HAVE A CRYSTALLINE<br />
TETRAHEDRAL SHAPE. THE SHIP WHICH IS ATTACKING YOU IS COMMANDED BY<br />
COMMANDER LOSKENE. THE SHIP IS EQUIPPED WITH ENERGY BEAMS<br />
EQUIVALENT TO A PHASER OF 600 TO 900 UNITS. IT IS ALSO EQUIPPED<br />
WITH DEFLECTOR SHIELDS AND HAS A SPEED OF WARP 5 TO 10.<br />
<br />
THE SHIP IS ALSO EQUIPPED WITH AN IMPROVED VERSION OF THE<br />
THOLIAN WEB WHICH, WHEN SPUN, CAN TRAP YOUR SHIP SO THAT IT CANNOT<br />
MOVE. THE WEB IS IMPERVIOUS TO PHOTON TORPEDOES AND DISRUPTOR<br />
BOLTS WHEN FIRED FROM WITHIN IT. IF ANY SHIP WHICH IS AN ENEMY OF<br />
THE THOLIANS COMES WITHIN 8 UNITS OF THE THOLIAN SHIP, THE WEB IS<br />
ACTIVATED ON THAT SHIP. WHEN YOU ARE TRAPPED IN A WEB, THE<br />
THOLIANS PREFER TO REMAIN AT A DISTANCE OF ABOUT 8 UNITS AWAY FROM<br />
YOU AND DESTROY YOU AT THEIR LEISURE. YOUR SHIP HAS A 14.27%<br />
CHANCE OF ESCAPING THE WEB ONLY WHEN YOU GO WARP 10.<br />
<br />
'''2.5 <u>ORIONS</u>'''<br />
<br />
THE ORION SYSTEM IS NOT PART OF EITHER THE FEDERATION OR<br />
KLINGON EMPIRE AND IS POLITICALLY NEUTRAL TOWARDS BOTH POWERS. THE<br />
ORIONS REMAIN NEUTRAL SO THAT THEIR MAIN BUT UNOFFICIAL INDUSTRY -<br />
SMUGGLING AND PIRACY - CAN BE CARRIED ON WITHOUT FEAR OF REPRISAL.<br />
THE ORIONS BASED MUCH OF THEIR SMUGGLING OPERATIONS ON THE KEY<br />
PLANET OF CORIDAN, HOWEVER THE PLANET HAS RECENTLY BEEN ACCEPTED<br />
INTO THE FEDERATION AS A RESULT OF THE INTERPLANETARY CONFERENCE<br />
HELD ON BABEL.<br />
<br />
DUE TO A CRACKDOWN ON THE SMUGGLING ON CORIDAN, THE SMUGGLERS<br />
HAVE GROWN AND HAVE TAKEN UP PIRACY. THEY NOW PREY ON FEDERATION<br />
AND KLINGON SHIPPING, AND HAVE BUILT A BATTLESHIP TO DESTROY THE<br />
STARSHIPS IN YOUR IN YOUR SECTOR, WHICH INCLUDES YOU. THE ORION<br />
SHIP IS ON A SUICIDAL MISSION AND IS EQUIPPED WITH PHASERS OF<br />
ENERGY BETWEEN 500 AND 1100 UNITS, AS WELL AS DEFLECTOR SHIELDS.<br />
IT HAS A HIGH DENSITY HULL WHICH SHIELDS THE SHIP AGAINST YOUR<br />
SENSORS AND ALLOWS IT TO ATTAIN WARP 12. THE BATTLE STRATEGY OF<br />
THE SHIP IS TO MAKE CLOSE PASSES OF YOUR SHIP AT MAXIMUM WARP AND<br />
FIRE UPON YOU WHEN IT IS AT THE CLOSEST POINT.<br />
<br />
'''2.6 <u>DOOMSDAY MACHINE</u>'''<br />
<br />
THE DOOMSDAY MACHINE IS A HUGE UNMANNED CYBERNETIC DEVICE FROM<br />
ANOTHER GALAXY WHICH DESTROYS STARS, BREAKING THEM DOWN IN ORDER<br />
TO DERIVE ENERGY FROM THEIR REMNANTS. THE MACHINE IS EQUIPPED WITH<br />
AN ANTI-PROTON BEAM WHICH IS EQUIVALENT TO A 1000 - 2000 UNIT<br />
PHASER BEAM. IT HAS A HULL OF EXTREMELY DENSE NEUTRONEUM WHICH<br />
MASKS IT AGAINST YOUR SENSORS, RENDERS YOUR PHASER BEAM VIRTUALLY<br />
INEFFECTIVE AGAINST IT AND MAKES IT IMPERVIOUS TO TRANSPORTER<br />
BEAMS.<br />
<br />
THE DOOMSDAY MACHINE WILL CONTENTEDLY EAT STARS AND WILL NOT<br />
FIRE UPON YOU UNLESS YOU FIRE UPON IT FIRST, OR IT COLLIDES WITH A<br />
MINE, AND IT WILL STOP FIRING AT IF YOU GET 7 OR MORE UNITS AWAY<br />
FROM IT AND IT RECEIVES NO MORE DAMAGE. THE MACHINE CANNOT<br />
DISTINGUISH BETWEEN A MINE AND A STAR, BUT IF IT FINDS A MINE, THE<br />
PROBABILITY THAT IT WILL EXPLODE AND CAUSE DAMAGE IS APPROXIMATELY<br />
71.42857%. BEWARE - IF YOU GET CLOSER TO THE MACHINE THAN THE<br />
NEAREST STAR, IT WILL EAT YOU. ALSO, WHEN THE MACHINE IS<br />
DESTROYED, EVERYTHING WITHIN 7 UNITS OF IT BLOWS UP AS WELL.<br />
<br />
'''2.7 <u>KZINTI</u>'''<br />
<br />
THE KZINTI ARE LARGE PANTHER-LIKE CREATURES WITH ORANGE FUR,<br />
AND COME FROM THE KZIN SYSTEM. THE KZINTI WARSHIP, THE ’TRAITOR’S<br />
CLAW’, COMMANDED BY CHUFT-CAPTAIN, CAN BE ARMED WITH INDUCTION<br />
BEAMS, X-RAY LASER CANNON, A WEB SIMILAR TO THE THOLIANS’, A<br />
CLOAKING DEVICE, A WEAPON THAT GENERATES FALSE IMAGES OF THE<br />
WARSHIP, AND A STASIS FIELD. IT CAN BE EQUIPPED WITH EITHER WARP<br />
OR IONIC DRIVE. THE IONIC DRIVE PROJECTS HIGH-VELOCITY IONS AND<br />
INTENSE RADIATION, SIMULATING A MINIATURE ION STORM. THE KZINTI<br />
CAN HAVE 3 BATTLE STRATEGIES - REGULAR ATTACK/RETREAT, KAMIKAZE<br />
(WHERE THE SHIP TRIES TO RAM YOU), AND CLOSE PASSES (LIKE THE<br />
ORIONS). THE KZINTI SHOW UP ON THE MAP AS A ’Z’.<br />
<br />
A NOTE ABOUT THE IMAGE GENERATOR WEAPON - EACH TIME THE KZINTI<br />
MOVE OR FIRE, A NUMBER OF FALSE IMAGES WILL BE PLACED ON THE MAP<br />
ALONG WITH THE ACTUAL IMAGE OF THE KZINTI, BUT WHEN THE KZINTI<br />
MOVE, ONLY THEIR ACTUAL IMAGE IS REMOVED FROM THE MAP, MORE IMAGES<br />
ARE GENERATED, AND THE ACTUAL IMAGE IS PLACED IN A NEW POSITION.<br />
<br />
THE KZINTI ARE PLAYER-PROGRAMMABLE, THAT IS THE PLAYER CHOOSES<br />
THEIR STRATEGY AND ARMAMENTS, BUT BEWARE - IF YOU MAKE THEM TOO<br />
WEAK, THEY WILL BE GIVEN ALL WEAPONS AT MAXIMUM SETTING.<br />
<br />
'''2.8 <u>MOONBASE ALPHA</u>'''<br />
<br />
NOW, BEFORE YOU STRING ME UP OR START THROWING STONES, LET ME<br />
EXPLAIN. IN MY OPINION, ALL SPACE:1999 LACKS THE IS A LAUGHTRACK<br />
BECAUSE IT IS ONE OF THE BEST COMEDIES ON TV. THE ONLY REASON I<br />
PUT MOONBASE ALPHA IN MY PROGRAM IS BECAUSE IT OFFERED A UNIQUE<br />
STRATEGY DIFFERENT FROM ALL OTHER ENEMY SHIPS.<br />
<br />
MOONBASE ALPHA SHOWS UP AS AN ’A’ ON THE MAP AND IT DOESN’T<br />
MOVE. IT HAS VERY PRIMITIVE DEFLECTOR SHIELDS WITH INITIALLY ONLY<br />
70 UNITS OF ENERGY IN THEM. IT ALSO HAS A NUMBER OF GROUND-BASED<br />
LASER CANNON WHICH CAN FIRE WITH A TOTAL FORCE OF 500 PHASER<br />
UNITS.<br />
<br />
IT IS ALSO EQUIPPED WITH 25 EAGLES, WHICH, FOR THOSE OF YOU<br />
LUCKY ENOUGH NEVER TO HAVE SEEN THE SHOW, ARE SMALL SHUTTLE-TYPE<br />
CRAFT WITH A CREW OF 2 AND PERHAPS A HANDFUL OF PASSENGERS. ALPHA<br />
CAN LAUNCH THEIR EAGLES 5 AT A TIME. EACH EAGLE CAN FIRE A LASER<br />
BEAM WITH AN EQUIVALENT ENERGY OF 200 PHASER UNITS, SO WHEN THE<br />
FIRST WAVE HITS YOU, THEY HIT WITH A FORCE OF 1000 UNITS. THE<br />
EAGLES HAVE A SPEED OF WARP 2, BUT HAVE NO DEFLECTOR SHIELDS SO<br />
THAT THE SMALLEST BLOW FROM YOUR PHASERS WILL WIPE ONE OUT. IF YOU<br />
COLLIDE WITH AN EAGLE, IT WILL BE JUST AS TOUGH YOU HIT A MINE.<br />
FURTHERMORE, IF YOU COME WITHIN A DISTANCE OF 1 UNIT AWAY FROM<br />
ALPHA, YOU WILL BE HIT BY AN EAGLE TAKING OFF.<br />
<br />
'''3. <u>STARBASES</u>'''<br />
<br />
AFTER CHOOSING YOUR ENEMIES, YOU’LL BE ASKED IF YOU WISH A<br />
STARBASE, DEPENDING ON WHETHER YOU’RE FIGHTING ENOUGH ENEMIES. A<br />
STARBASE SHOWS UP AS A ’*’ LIKE ALL STARS ON THE MAP, HAS A CREW<br />
OF 1000, CARRIES A SUPPLY OF 20 PHOTON TORPEDOES (20 DISRUPTOR<br />
BOLTS IF IT’S A KLINGON STARBASE) AND HAS A DEFLECTOR SHIELD<br />
STRENGTH OF 300 UNITS. IT CAN BE USED TO HELP YOU FIGHT, AND<br />
REPAIR AND RESUPPLY YOUR SHIP. YOU ARE GIVEN THE OPTION OF A<br />
STARBASE IF:<br />
<br />
A) YOU ARE ALONE AND ARE FIGHTING 3 OR MORE COMPUTER-OPERATED<br />
(C‑O) ENEMIES.<br />
B) YOU AND ANOTHER MANUAL-OPERATED (M-O) SHIP ON YOUR SIDE <br />
ARE FIGHTING 6 OR MORE C-O ENEMIES.<br />
C) YOU ARE FIGHTING ANOTHER M-O SHIP.<br />
D) YOU ARE ALWAYS GIVEN THE OPTION OF AN ENEMY STARBASE TO <br />
FIGHT.<br />
<br />
IN CASE C, ANY OTHER M-O SHIP MAY VETO YOUR CHOICE OF A<br />
STARBASE UNLESS THEY ALREADY HAVE A STARBASE.<br />
<br />
IN CASE D, THE ENEMY STARBASE WILL BE ALLIED WITH ANY OTHER<br />
C‑O ENEMIES IN THE GAME.<br />
<br />
'''4. <u>STARS</u>'''<br />
<br />
NEXT YOU’LL BE ASKED HOW MANY STARS YOU WISH IN YOUR AREA. I<br />
USUALLY SUGGEST BETWEEN 75 AND 200. IF YOU PUT IN TOO MANY STARS<br />
IT MAY BE DIFFICULT FOR YOU AND THE ENEMY TO MOVE AROUND. IF YOU<br />
PLAY THE DOOMSDAY MACHINE, YOU MAY WANT TO PUT IN ENOUGH STARS TO<br />
KEEP IT CONTENTED.<br />
<br />
ALSO, UP TO 5 STARS ON THE MAP MAY HAVE DILITHIUM CRYSTAL<br />
DEPOSITS ON ONE OF THEIR PLANETS, WHICH CAN BE USED TO BOOST YOUR<br />
ENERGY. YOU’LL BE NOTIFIED OF SUCH A STAR IF YOU COME WITHIN A<br />
DISTANCE OF 5 UNITS FROM IT, AND YOU’LL ACQUIRE THE CRYSTALS IF<br />
YOU COME WITHIN A DISTANCE OF 1 UNIT FROM IT.<br />
<br />
'''5. <u>TAKING TURNS</u>'''<br />
<br />
AT THIS POINT INITIALIZATION IS COMPLETE - YOU ARE ON YOUR<br />
OWN. COMMANDS ARE ACCEPTED FROM THE ENTERPRISE FIRST (IF IT’S IN<br />
THE GAME). WHEN IT HAS FINISHED MOVING AND/OR FIRING, THE<br />
POTEMPKIN TAKES ITS TURN NEXT, THEN THE HAVOC, THEN THE CARNAGE,<br />
THEN THE STARBASES FIRE, AND THEN THE COMPUTER-OPERATED SHIPS MOVE<br />
AND FIRE. FOLLOWING IS A LIST OF COMMANDS YOU CAN ENTER, EACH<br />
COMMAND CAN BE ABBREVIATED TO ITS FIRST TWO LETTERS.<br />
<br />
<span style="color:red>IF YOU DO NOT USE THE TWO LETTER ABBREVIATION, YOU NEED A<br />
SECOND [RETURN] FOR THE COMMAND TO GET GOING.<br />
<br />
IF YOU WANT TO DO NOTHING, JUST ENTER GO [ENTER] AND [ENTER]<br />
AGAIN, THIS WILL TRANSFER CONTROL TO THE NEXT SHIP.</span><br />
<br />
'''6. <u>COMMANDS</u><br />
<br />
NOTE - IN ALL THESE COMMANDS, IF YOU TYPE ’STOP’ WHEN ASKED<br />
FOR INPUT, THE USUAL RECOURSE IS TO CANCEL THE COMMAND. (THIS<br />
PROVIDES A FAST WAY OUT).<br />
<br />
'''6.1 <u>INFORMATION COMMANDS</u>'''<br />
<br />
'''6.1.1 <u>HELP</u>'''<br />
<br />
THE HELP COMMAND GIVES YOU A BRIEF LISTING OF COMMANDS AND<br />
INSTRUCTIONS.<br />
<br />
'''6.1.2 <u>SPOCK</u>'''<br />
<br />
THE SPOCK COMMAND GIVES SOME INTERESTING PROBABILITIES AND<br />
STATISTICS.<br />
<br />
'''6.1.3 <u>MAP</u>'''<br />
<br />
THE MAP COMMAND GIVES A MAP OF YOUR SURROUNDINGS. ALTHOUGH THE<br />
GAME IS PLAYED ON A 60X60 GRID, EACH SHIP CAN ONLY SEE A MAXIMUM<br />
OF 15 UNITS AWAY FROM IT, AND EVEN LESS IF YOU’VE RECEIVED ANY<br />
DAMAGE TO YOUR SENSORS. YOU’LL BE ASKED TO ENTER THE RADIUS OF<br />
YOUR MAP. AT TIMES YOU MAY WISH A SMALL MAP TO SAVE PRINTOUT TIME<br />
AND PAPER BY CHOOSING A SMALL RADIUS. HERE IS A LIST OF SYMBOLS<br />
THAT MAY APPEAR ON YOUR MAP:<br />
<br />
A-MOONBASE ALPHA G-GORN WARSHIP M-MINE T-THOLIAN WARSHIP<br />
C-CARNAGE H-HAVOC O-ORION PRIVATEER Z-KZINTI WARSHIP<br />
D-DOOMSDAY MACHINE I-ION STORM P-POTEMPKIN *-STAR/STARBASE<br />
E-ENTERPRISE K-KLINGON WARSHIP R-ROMULAN WARSHIP =-EAGLE<br />
<br />
IF YOU WISH TO SAVE TIME, YOU CAN ENTER THE MAP RADIUS WHEN<br />
YOU ENTER YOUR COMMAND. EG. ’MA,9’ WILL GIVE YOU A MAP OF RADIUS<br />
9, BUT YOU MUST USE THE SHORT FORM ’MA’ INSTEAD OF ’MAP’.<br />
<br />
'''6.1.4 <u>INFO</u>'''<br />
<br />
THE INFO COMMAND GIVES YOU THE STATUS OF ALL SHIPS EXCEPT<br />
EAGLES. THAT IS, YOU’LL BE TOLD THE DEFLECTOR SHIELD STRENGTH AND<br />
POSITION OF EACH SHIP (PROVIDING IT IS NOT CLOAKED OR SHIELDED<br />
AGAINST SENSORS). ALSO IT WILL GIVE YOU THE NUMBER OF CREW YOU<br />
HAVE ON YOUR OWN SHIP.<br />
<br />
'''6.1.5 <u>EAGLE</u>'''<br />
<br />
THE EAGLE COMMAND REPORTS THE POSITION OF ALL EAGLES IN THE<br />
GAME.<br />
<br />
'''6.1.6 <u>CREW</u>'''<br />
<br />
THE CREW COMMAND LISTS THE NUMBER OF YOUR CREW ON YOUR SHIP AS<br />
WELL AS ON YOUR STARBASE AND ON ANY SHIP YOU MAY HAVE BOARDED.<br />
<br />
'''6.1.7 <u>DAMAGE</u>'''<br />
<br />
THE DAMAGE COMMAND GIVES A DECK BY DECK LISTING OF DAMAGE ON<br />
YOUR SHIP. IT MERELY SUMMARIZES ALL PREVIOUS DAMAGE REPORTS.<br />
<br />
'''6.2 <u>MISCELLANEOUS COMMANDS</u>'''<br />
<br />
'''6.2.1 <u>TRANSFER</u>'''<br />
<br />
THE TRANSFER COMMAND ALLOWS YOU TO TRANSFER ENERGY FROM ONE<br />
SYSTEM TO ANOTHER. DURING A BATTLE ON THE TV SHOW, IT OFTEN<br />
HAPPENS THAT SCOTTY WILL REPORT ’SUH, I DON’T KNOW HOW MUCH LONGER<br />
OUR DEFLECTOR SHIELDS (OR WARP ENGINES, OR PHASER BANKS, ETC.)<br />
WILL HOLD UP’ AT WHICH POINT KIRK RISES AND SAYS ’DIVERT POWER TO<br />
THE DEFLECTORS’, OR ’POWER TO THE WARP DRIVE ENGINES’, OR ’POWER<br />
TO THE PEOPLE!’, AND ALL IS WELL. YOU CAN ACCOMPLISH THE SAME<br />
GOD‑LIKE FEATS USING THE TRANSFER COMMAND.<br />
<br />
YOU’LL BE ASKED TO ENTER A 2-LETTER CODE. THE FIRST LETTER IS<br />
THE SYSTEM YOU WISH TO TRANSFER ENERGY FROM AND THE SECOND LETTER<br />
IS WHERE YOU WISH TO TRANSFER IT TO. THE LETTERS CAN BE ’W’ (WARP<br />
ENGINES), ’P’ (PHASER BANKS), ’T’ (PHOTON TORPEDOES OR DISRUPTOR<br />
BOLTS). OR ’D’ (DEFLECTOR SHIELDS). (EG. ’PW’ TRANSFERS ENERGY<br />
FROM THE PHASERS TO THE WARP DRIVE ENGINES). THERE ARE<br />
RESTRICTIONS PLACED ON THE TRANSFER OF POWER FROM A TORPEDO: YOU<br />
CAN ONLY TRANSFER ENERGY INTO THE DEFLECTORS, AND YOU CANNOT<br />
CREATE A TORPEDO, SO I DON’T SUGGEST YOU USE THE ’TD’ OPTION<br />
UNLESS YOU’RE DESPERATE<br />
<br />
NEXT YOU’LL BE ASKED TO ENTER THE AMOUNT OF ENERGY YOU WISH TO<br />
TRANSFER. BEAR IN MIND THAT:<br />
<br />
1 PHOTON TORPEDO = 6 DEFLECTOR SHIELD UNITS.<br />
<br />
IF YOU WISH TO SAVE TIME, YOU CAN ENTER THIS NUMBER ALONG WITH<br />
THE 2-LETTER CODE. (EG. ’WP,4’ WOULD TRANSFER 4 WARPS FROM THE<br />
WARP ENGINES TO BECOME 4000 UNITS IN THE PHASER BANKS.)<br />
<br />
THERE ARE FOUR SPECIAL 2-LETTER CODES:<br />
<br />
’DD’ ALLOWS YOU TO TRANSFER ENERGY BETWEEN SHIPS AS LONG AS YOU ARE <br />
WITHIN 1 UNIT OF EACH OTHER. WHEN ASKED TO ENTER THE AMOUNT OF <br />
ENERGY, TYPE A POSITIVE NUMBER TO GIVE THE OTHER SHIP’S <br />
DEFLECTORS THAT AMOUNT OF ENERGY FROM YOUR DEFLECTORS, AND <br />
TYPE A NEGATIVE NUMBER TO TAKE THAT AMOUNT FROM THE OTHER SHIP <br />
AND PUT IT IN YOUR DEFLECTORS (YOU CAN ONLY TAKE ENERGY FROM A <br />
BOARDED C-O SHIP OR A DERELICT M-O SHIP). YOU’LL ALSO BE <br />
ASKED TO ENTER THE LETTER OF THE SHIP YOU WISH TO TRANSFER <br />
ENERGY WITH (EG. ’K’ FOR KLINGON WARSHIP).<br />
<br />
’##’ ALLOWS YOU TO TRANSFER PERSONNEL, DEFLECTOR ENERGY, AND PHOTON <br />
TORPEDOES (DISRUPTOR BOLTS) BETWEEN BETWEEN YOUR SHIP AND YOUR <br />
STARBASE WHEN YOU ARE DOCKED AT IT (WITHIN 1 UNIT OF DISTANCE).<br />
<br />
’STOP’ STOPS THE TRANSFER COMMAND.<br />
<br />
’??’ DISPLAYS CURRENT ENERGY LEVELS.<br />
<br />
'''6.2.2 <u>RADIO</u>'''<br />
<br />
THE RADIO COMMAND ALLOWS COMMUNICATION BETWEEN M-O SHIPS. YOU<br />
CAN DO FOUR THINGS WITH YOUR SUBSPACE RADIO:<br />
<br />
1) TRANSMIT- YOU’LL BE ASKED WHICH M-O SHIP YOU WISH TO TALK<br />
TO, AND LATER YOU’LL BE GIVEN THE INTERFERENCE LEVEL, WHICH<br />
DEPENDS ON: DISTANCE BETWEEN SENDER AND RECEIVER, WHETHER THE<br />
SENDER OR RECEIVER IS IN AN ION STORM OR NEAR A DOOMSDAY MACHINE<br />
AND WHETHER YOU (OR THE ENEMY) ARE JAMMING SUBSPACE. THE<br />
INTERFERENCE LEVEL GIVES THE PERCENTAGE PART OF YOUR MESSAGE WHICH<br />
WILL BE OBSCURED BY STATIC (RANDOM CHARACTERS JUMBLED INTO THE<br />
TRANSMISSION). A MESSAGE WITH AN INTERFERENCE LEVEL OF 0 - 20% IS<br />
ACCEPTABLE.<br />
<br />
YOU’LL BE TOLD WHAT THE ENERGY EXPENDED WILL REDUCE THE<br />
INTERFERENCE LEVEL TO AND YOU’LL BE ASKED WHICH CODE YOU WISH TO<br />
TRANSMIT THE MESSAGE IN. (IF YOU WISH TO CANCEL THE WHOLE IDEA AT<br />
THIS POINT, ENTER ’STOP’.) CODE O IS HAILING FREQUENCIES WITH A<br />
UNIVERSAL TRANSLATOR TIED IN SO ALL SHIPS CAN RECEIVE AND<br />
UNDERSTAND YOUR MESSAGE. IF YOU WISH ONLY YOUR SIDE TO UNDERSTAND<br />
THE MESSAGE, ENTER A CODE NUMBER BETWEEN 1 AND 8 (NOTING THAT THE<br />
ENEMY MAY HAVE BROKEN SOME OF THE CODES). THE MORE YOU USE ONE<br />
PARTICULAR CODE, THE GREATER THE CHANCE THAT THE ENEMY HAS BROKEN<br />
IT. AFTER ALL THIS, YOU’LL FINALLY BE ASKED TO ENTER YOUR MESSAGE<br />
(80 CHARACTER MAXIMUM).<br />
<br />
2) RECEIVE- THIS IS THE SAME AS TRANSMIT ONLY YOU USE PHASER<br />
ENERGY FOR BOOSTING THE SIGNAL SO YOU CAN UNDERSTAND THE OTHER<br />
SHIP’S MESSAGE THROUGH THE STATIC.<br />
<br />
3) JAM- YOU’LL BE ASKED TO ENTER THE AMOUNT OF PHASER ENERGY<br />
YOU WISH TO EXPEND TO RAISE THE SUBSPACE INTERFERENCE LEVELS. IF<br />
YOU ARE DISSATISFIED WITH THE AMOUNT YOU HAVE EXPENDED,YOU MAY USE<br />
THE COMMAND AGAIN TO ADJUST THE LEVEL BY INCREASING OR DECREASING<br />
THE ENERGY. EG. IF I MAKE A MISTAKE AND BLOW 500 PHASER UNITS, I<br />
CAN RETYPE THE COMMAND AND ENTER -500 WHEN IT ASKS FOR THE PHASER<br />
ENERGY EXPENDITURE, AND ALL WILL BE RESTORED. JAMMING WILL LAST<br />
UNTIL YOUR TURN ROLLS AROUND AGAIN AFTER ALL THE OTHER M-O AND C-O<br />
SHIPS HAVE MOVED AND FIRED.<br />
<br />
4) DISTRESS SIGNAL- THIS ACTIVATES YOUR DISTRESS BEACON AND<br />
NOTIFIES ALL SHIPS THAT YOU NEED HELP.<br />
<br />
'''6.2.3 <u>SURRENDER</u>'''<br />
<br />
THE SURRENDER COMMAND ALLOWS YOU TO SURRENDER. IF YOU ARE<br />
PLAYING NO M-O (MANUALLY-OPERATED) SHIPS, THIS PROVIDES A FAST WAY<br />
OUT OF THE GAME. IF YOU ARE PLAYING OTHER OPPOSING M-O SHIPS, YOUR<br />
DESIRE TO SURRENDER WILL BE ANNOUNCED TO ALL OTHER SHIPS IN THE<br />
GAME, AND YOU’LL BE ASKED TO PRESENT YOUR SURRENDER TO THE NEAREST<br />
M-O ENEMY VESSEL, WHO’LL USUALLY ASK YOU TO DROP YOUR SHIELDS AND<br />
PREPARE TO BE BOARDED. USE OF THIS COMMAND GUARANTEES YOU WILL<br />
PRESENT NO RESISTANCE TO HIS BOARDING PARTY. THUS, IF A SHIP<br />
ANNOUNCES TO YOU HE WISHES SURRENDER, INSIST HE USE THE SURRENDER<br />
COMMAND BEFORE YOU BOARD HIM, OR HE COULD BE TRYING TO TRICK YOU<br />
INTO SENDING OVER A PARTY WHICH HE CAN DESTROY.<br />
<br />
'''6.2.4 <u>NOSTOP</u>'''<br />
<br />
THE NOSTOP COMMAND, WHEN ACTIVATED, MEANS THAT THE GAME DOES<br />
NOT END WHEN YOU DEFEAT ALL THE ENEMIES.<br />
<br />
'''6.2.5 <u>ENEMY</u>'''<br />
<br />
THE ENEMY COMMAND ADDS MORE C-O ENEMIES TO THE GAME. EITHER<br />
YOU CAN CHOOSE AN ENEMY OR LET AN ENEMY BE CHOSEN AT RANDOM. THIS<br />
COMMAND, COMBINED WITH THE ’NOSTOP’ COMMAND, ALLOWS YOU TO TAKE ON<br />
ENEMIES ONE AFTER THE OTHER INSTEAD OF ALL AT ONCE.<br />
<br />
'''6.2.6 <u>CEASEFIRE</u>'''<br />
<br />
THE CEASEFIRE COMMAND ALLOWS YOU TO CONTROL YOUR STARBASE OR<br />
ANY C-0 SHIPS THAT YOU HAVE BOARDED. IT CAUSES THE SHIP OR BASE TO<br />
STOP FIRING, AND IF IT’S A SHIP, IT WILL SET COURSE TO THE NEAREST<br />
ALLIED M-O VESSEL.<br />
<br />
'''6.2.7 <u>ATTACK</u>'''<br />
<br />
THE ATTACK COMMAND CANCELS THE EFFECT OF THE ’CEASEFIRE’<br />
COMMAND ON THE STARBASE / YOUR SHIP YOU USED IT ON.<br />
<br />
'''<span style="color:red>6.2.8 <u>VERSION</u></span>'''<br />
<br />
'''<span style="color:red>THE VERSION COMMAND SHOWS THE TREK7 VERSION.</span> <br />
<br />
'''6.3 <u>COMMANDS TO SET WEAPONS</u>'''<br />
<br />
'''6.3.1 <u>COURSE</u>'''<br />
<br />
THE COURSE COMMAND ALLOWS YOU TO SET A NEW COURSE. YOU’LL BE<br />
ASKED TO ENTER THE WARP SPEED AT WHICH YOU WISH TO TRAVEL. WARP 1<br />
COVERS 1 UNIT ON THE MAP, WARP 10 COVERS 10 UNITS (NOTE THAT IF<br />
YOU WISH TO GO DIAGONALLY AT, SAY,A 45 DEGREE ANGLE,TO MOVE OUT OF<br />
THE POSITION YOU ARE IN YOU MUST GO AT LEAST WARP 1.42 (REMEMBER<br />
PYTHAGORAS!). IF YOU GO OVER WARP 6, ENGINE TEMPERATURES BEGIN TO<br />
CLIMB.<br />
<br />
NEXT, YOU’LL BE ASKED TO ENTER TARGET COORDINATES. NOTE:<br />
WHENEVER COORDINATES ARE REQUESTED, ENTER THEM IN 2I2 FORMAT (IF<br />
YOU KNOW FORTRAN). EG. TO ENTER (50,50) OR ( 1, 1), TYPE 5050 OR<br />
0101. YOU DO NOT HAVE TO SET A NEW COURSE EVERY TIME YOU MOVE. <br />
EG. IF I’M AT ( 1, 1) AND I WISH TO MOVE TO ( 1,50), I CAN ENTER<br />
O150 AS MY TARGET COORDINATES, EVEN THOUGH I WON’T REACH THERE<br />
UNTIL AT LEAST 5 MOVES FROM NOW. WARP AND TARGET COORDINATES CAN<br />
BE ENTERED WHEN THE COMMAND IS TYPED - EG. ’CO,5,1020’ WILL SET A<br />
COURSE TO (10,20) AT WARP 5 BUT YOU MUST USE THE SHORT FORM ’CO’<br />
OF THE COMMAND. IF YOU MAKE A MISTAKE OR WISH TO ENTER A NEW<br />
COURSE, SIMPLY TYPE THE COMMAND OVER AGAIN. <span style="color:red>YOU'LL BE TOLD WHEN<br />
YOU'VE REACHED TARGET COORDINATES, AND THE SHIP WILL STAY THERE<br />
UNTIL YOU SET A NEW COURSE AND MOVE AGAIN.</span><br />
<br />
NOTE 1- STEERING CONTROL- WHENEVER YOU MOVE, THE PROBABILITY<br />
OF YOU LOSING STEERING CONTROL AND VEERING OFF COURSE IS (DAMAGE<br />
FACTOR RECEIVED BY WARP DRIVE ENGINEERING * 5)%. IF WARP DRIVE<br />
ENGINEERING HAS RECEIVED NO DAMAGE, THE PROBABILITY IS 5%. WARP<br />
DRIVE ENGINEERING IS LOCATED ON DECK 16 ON THE ENTERPRISE<br />
(POTEMPKIN), AND DECK E4-AFT ON THE HAVOC (CARNAGE).<br />
<br />
NOTE 2- NACELLE SUPPORT PYLONS- IF YOUR NACELLE SUPPORT PYLONS<br />
HAVE BEEN HIT, THE NACELLES MAY RIP OFF IF YOU EXCEED A CERTAIN<br />
SPEED WHICH WILL BE REPORTED TO YOU. THE PROBABILITY THAT IT WILL<br />
RIP OFF =(AMOUNT BY WHICH THE SPEED LIMIT IS EXCEEDED * 10 + 10)%.<br />
HOWEVER, IF THE LIMIT AT WHICH THE NACELLES THREATEN TO RIP OFF<br />
IS WARP 1 (IE. THE PYLON IS DESTROYED), THEN THE PROBABILITY THAT<br />
IT WILL RIP OFF IS 100% IF YOU GO WARP 1 OR OVER. IF THE NACELLE<br />
DOES RIP OFF, IT WILL CONTINUE IN THE DIRECTION YOU WERE GOING,<br />
AND IF IT HITS ANYTHING, IT WILL BE HEAVILY DAMAGED.<br />
<br />
NOTE 3- ION STORMS- IF ANY SHIP ENTERS AN ION STORM, ITS SPEED<br />
WILL BE CUT IN HALF AND DAMAGE WILL RESULT.<br />
<br />
NOTE 4- COLLISION- IF A SHIP HITS A MINE OR EAGLE. DAMAGE WILL<br />
RESULT TO THE SHIP. IF A SHIP HITS ANOTHER SHIP, THEY WILL WIPE<br />
EACH OTHER OUT. AUTOMATIC CUTOFFS PREVENT SHIPS FROM COLLIDING<br />
WITH STARS.<br />
<br />
NOTE 5- WARP ENGINE SHUTDOWN- IF WARP ENERGY GOES BELOW O.5<br />
THE WARP ENGINES WILL BE SHUT DOWN AND THE ENGINE TEMPERATURE WILL<br />
RAPIDLY COOL TO AROUND ABSOLUTE ZERO. TO MOVE THEREAFTER YOU WILL<br />
HAVE TO BOOST WARP ENERGY AND WAIT A TURN TO RE-ENERGIZE THE<br />
ENGINES.<br />
<br />
NOTE 6- ENGINE TEMPERATURE- NORMAL ENGINE TEMPERATURE FOR A<br />
M‑O SHIP IS 4000 DEGREES. IF YOU GO OVER WARP 6 THE TEMPERATURE<br />
WILL INCREASE. THE DANGER LINE IS 6200 DEGREES - ONCE THE<br />
TEMPERATURE PASSES THAT THE PROBABILITY THAT AN ENGINE WILL<br />
EXPLODE IS ((TEMPERATURE - 6200) / 100)%. IF TEMPERATURES EXCEED<br />
7500 DEGREES, YOU’RE IN TROUBLE. TO COOL THE ENGINES, SIMPLY GO TO<br />
A SPEED LESS THAN WARP 6. THE SLOWER YOU GO, THE FASTER YOU’LL<br />
COOL OFF. TO CRASH-COOL THE ENGINES, SEE NOTE 5 ABOVE.<br />
<br />
'''6.3.2 <u>PHASER</u>'''<br />
<br />
THE PHASER COMMAND LOCKS PHASERS ON TARGET. YOU’LL BE ASKED TO<br />
ENTER THE AMOUNT OF PHASER ENERGY YOU WISH TO EXPEND. NOTE THAT<br />
THERE IS A MAXIMUM AMOUNT OF DAMAGE THAT CAN BE DONE WHEN A PHASER<br />
BEAM IS FIRED. THUS YOU ARE ADVISED NOT TO WASTE YOUR ENERGY BY<br />
FIRING TOO MUCH ENERGY AT A TIME. I ADVISE ABOUT 500 UNITS PER<br />
SHOT (0.0001 UNIT OR LESS IF YOU’RE FIRING AT AN EAGLE). TWO SHOTS<br />
OF 500 UNITS DO MORE DAMAGE THAN ONE SHOT OF 1000 UNITS.<br />
<br />
NEXT, YOU’LL BE ASKED TO ENTER THE TARGET COORDINATES. IF THE<br />
TARGET IS TOO FAR AWAY, YOUR PHASERS MAY MISS. THE PROBABILITY OF<br />
A MISS IS (2.5 * DISTANCE TO TARGET)%, SO I WOULDN’T FIRE UNLESS<br />
THE TARGET WAS WITHIN ABOUT 20 UNITS.<br />
<br />
ALTHOUGH PHASERS PASS THROUGH STARS AND ION STORMS, IF<br />
ANYTHING ELSE IS DIRECTLY BETWEEN YOU AND THE TARGET, YOU MAY HIT<br />
IT INSTEAD. ALLIED SHIPS HAVE NO SENSE OF HUMOUR AT ALL WHEN YOU<br />
HIT THEM ACCIDENTALLY.<br />
<br />
PHASER ENERGY AND TARGET CAN BE ENTERED WHEN THE COMMAND IS<br />
TYPED- EG. ’PH,500,2001’ LOCKS A 5OO-UNIT PHASER BEAM ONTO<br />
(20, 01). BUT YOU MUST USE THE SHORT FORM ’PH’ OF THE PHASER<br />
COMMAND.<br />
<br />
WHEN PHASERS ARE FIRED, THERE IS A 5% CHANCE THEY WILL<br />
SHORT‑CIRCUIT, AND ANOTHER 5% CHANCE A MAIN COIL WILL BURN OUT. IF<br />
THERE IS A COIL BURNOUT, THERE IS A 28.57% CHANCE IT WILL BE<br />
REPAIRED EACH TURN (ALTHOUGH THE PROBABILITY INCREASES IF YOU<br />
UNDERGO REPAIR MODE A, B OR C). ALSO, THE PROBABILITY THAT A<br />
PHASER WILL BOUNCE OFF THE DOOMSDAY MACHINE AND THUS CAUSE NO<br />
DAMAGE IS 66.7%.<br />
<br />
'''6.3.3 <u>TORPEDO</u>'''<br />
<br />
THE TORPEDO COMMAND LOCKS PHOTON TORPEDOES (DISRUPTOR BOLTS)<br />
ON TARGET. YOU WILL BE ASKED TO ENTER THE ANGLE AT WHICH THE<br />
TORPEDO IS TO BE FIRED FROM YOUR SHIP. THE COMPASS IS AS FOLLOWS-<br />
<br />
90<br />
I<br />
I<br />
180---------<span style="color:red>360</span><br />
I<br />
I<br />
270<br />
<br />
NOTE THAT THE MAXIMUM RANGE OF A TORPEDO IS 10 UNITS. IF,<br />
AFTER TRAVELLING THAT DISTANCE, THE TORPEDO ENCOUNTERS NOTHING, IT<br />
WILL BECOME A MINE AND WILL SHOW UP ON YOUR MAP AS AN ’M’. ONLY<br />
YOUR SENSORS CAN DETECT YOUR OWN MINE - NO OTHER SHIP CAN DETECT<br />
YOUR MINES AND YOU CAN DETECT NO OTHER SHIP’S MINES. THE ANGLE CAN<br />
BE ENTERED WITH THE COMMAND, EG. ’TO,90’ WILL LOCK A TORPEDO ONTO<br />
A 90 DEGREE BEARING.<br />
<br />
<span style="color:red>ALWAYS USE ’360’ DEGREES INSTEAD OF ’0’, BECAUSE THE COMPOSITE<br />
COMMAND ’TO,0’ WILL FAIL.</span><br />
<br />
WHEN TORPEDOES ARE FIRED THERE IS A 7% CHANCE THEY WILL<br />
SHORT‑CIRCUIT. ALSO, WHEN A TORPEDO IS FIRED WHILE YOU ARE TRAPPED<br />
IN A WEB, THERE IS A 25% CHANCE THAT IT WILL PIERCE THE WEB AND A<br />
25% CHANCE IT WILL BOUNCE OFF THE WEB AND STRIKE YOUR SHIP.<br />
<br />
'''6.3.4 <u>RESET</u>'''<br />
<br />
THE RESET COMMAND ALLOWS YOU TO RESET PHASERS AND TORPEDOES<br />
(DISRUPTORS) ONTO THE LAST TARGET THEY WERE SET. IF, AFTER FIRING<br />
PHASERS AND TORPEDOES, THE TARGET HAS NOT MOVED, YOU CAN USE THIS<br />
COMMAND TO LOCK PHASERS AND TORPEDOES ONTO THE TARGETS THEY WERE<br />
LOCKED ONTO DURING THE PREVIOUS TURN. THUS, THIS COMMAND SAVES YOU<br />
THE BOTHER OF RE-ENTERING THE ’PHASER’ AND ’TORPEDO’ COMMAND.<br />
<br />
'''6.3.5 <u>MINE</u>'''<br />
<br />
THE MINE COMMAND ALLOWS YOU TO CHANGE THE DISTANCE A TORPEDO<br />
(DISRUPTOR BOLT) WILL TRAVEL BEFORE IT BECOMES A MINE. THIS MAKES<br />
IT EASIER FOR YOU TO LAY A MINE FIELD. YOU WILL BE ASKED TO ENTER<br />
THE DISTANCE, BUT IT IS POSSIBLE TO ENTER IT WHEN YOU ENTER THE<br />
COMMAND. (EG. ’MI,6’ WILL MAKE THE NEXT TORPEDO BECOME A MINE<br />
AFTER IT HAS TRAVELLED 6 UNITS). NOTE THAT THIS COMMAND SHOULD BE<br />
USED ONLY AFTER YOU USE THE ’TORPEDO’ COMMAND, BECAUSE EACH TIME<br />
YOU USE THE TORPEDO COMMAND, THE TORPEDO IS SET TO THE DEFAULT<br />
DISTANCE OF 10 UNITS.<br />
<br />
'''6.3.6 <u>DEFLECT</u>'''<br />
<br />
THE DEFLECT COMMAND ALLOWS YOU TO LOCK YOUR DEFLECTOR BEAM ON<br />
A TARGET. THE DEFLECTOR BEAM DRAWS OFF YOUR DEFLECTOR SHIELD<br />
ENERGY TO PUSH OBJECTS A MAXIMUM OF 10 UNITS AWAY, OR LESS IF YOUR<br />
NAVIGATIONAL DEFLECTOR HAS RECEIVED DAMAGE. YOU WILL BE ASKED TO<br />
ENTER THE COORDINATES OF THE TARGET. THE DEFLECTOR BEAM WILL DO<br />
DIFFERENT THINGS DEPENDING ON THE TYPE OF TARGET:<br />
<br />
A) THE TARGET IS A SHIP- YOUR DEFLECTOR BEAM WILL ONLY BE ABLE<br />
TO SLOW THE SHIP DOWN IF IT IS HEADING TOWARDS YOU. YOU WILL BE<br />
ASKED TO ENTER THE AMOUNT OF DEFLECTOR SHIELD ENERGY YOU WISH TO<br />
EXPEND SLOWING THE ENEMY DOWN. THE AMOUNT OF ENERGY (E) ENTERED<br />
WILL SLOW THE ENEMY SHIP’S SPEED BY A FACTOR OF 2**(-E/5). THUS E<br />
= 5 WILL CUT THE SHIP’S SPEED IN HALF, E = 10 WILL SLOW IT TO<br />
1/4 SPEED, AND E = 15 WILL SLOW IT TO 1/8 SPEED.<br />
<br />
B) THE TARGET IS AN EAGLE OR MINE- YOUR DEFLECTOR BEAM WILL BE<br />
ABLE TO PUSH IT AWAY FROM YOU OUT OF THE LIMIT OF YOUR DEFLECTOR<br />
BEAM RANGE. YOU WILL BE ASKED TO ENTER THE DISTANCE YOU WISH TO<br />
PUSH THE OBJECT AWAY. PUSHING THE OBJECT AWAY 1 UNIT WILL USE<br />
1 UNIT OF DEFLECTOR SHIELD ENERGY.<br />
<br />
C) THE TARGET IS EMPTY SPACE OR AN ION STORM- NOTHING WILL<br />
HAPPEN, NO MATTER HOW MUCH ENERGY YOU EXPEND.<br />
<br />
D) THE TARGET IS A STAR, DOOMSDAY MACHINE OR MOONBASE ALPHA-<br />
NOTHING WILL HAPPEN SINCE THE TARGET IS TOO MASSIVE FOR IT TO<br />
HANDLE.<br />
<br />
You CAN ENTER THE TARGET AND ENERGY OR DISTANCE WITH THE<br />
COMMAND ITSELF. (EG. ’DE,5,5050’ WILL TRAIN THE DEFLECTOR BEAM ON<br />
(50, 50). IF THE TARGET IS AN ATTACKING SHIP, IT WILL BE SLOWED TO<br />
1/2 SPEED. IF THE TARGET IS AN EAGLE OR MINE, IT WILL BE PUSHED<br />
5 UNITS).<br />
<br />
'''6.3.7 <u>YANK</u>'''<br />
<br />
THE YANK COMMAND ALLOWS YOU TO LOCK YOUR TRACTOR BEAM ON A<br />
TARGET. THE TRACTOR BEAM DRAWS OFF YOUR WARP ENGINE ENERGY TO PULL<br />
IN OBJECTS A MAXIMUM OF 10 UNITS AWAY, OR LESS IF YOUR TRACTOR<br />
BEAM MACHINERY ROOM HAS RECEIVED DAMAGE. YOU WILL BE ASKED TO<br />
ENTER THE COORDINATES OF THE TARGET. THE TRACTOR BEAM WILL DO<br />
DIFFERENT THINGS DEPENDING ON THE TYPE OF TARGET:<br />
<br />
A) TARGET IS A SHIP- YOUR TRACTOR BEAM WILL ONLY BE ABLE TO<br />
SLOW THE SHIP DOWN IF IT IS HEADING AWAY FROM YOU. YOU WILL BE<br />
ASKED TO ENTER THE AMOUNT OF WARP ENERGY YOU WISH TO EXPEND IN<br />
SLOWING THE SHIP DOWN. THE AMOUNT OF ENERGY (E) ENTERED WILL SLOW<br />
THE SHIP’S SPEED BY A FACTOR OF 2**(-E/0.5). THUS E = 0.5 WILL CUT<br />
THE SHIP’S SPEED IN HALF, E = 1.0 WILL SLOW IT TO 1/4 SPEED, AND E<br />
= 1.5 WILL SLOW IT TO 1/8 SPEED.<br />
<br />
B) THE TARGET IS AN EAGLE OR MINE- YOUR TRACTOR BEAM WILL BE<br />
ABLE TO PULL IT TOWARDS YOU. YOU WILL BE ASKED TO ENTER THE<br />
DISTANCE YOU WISH TO PULL THE OBJECT. PULLING THE OBJECT 1 UNIT<br />
WILL USE 0.1 UNIT OF WARP ENERGY. IF THE EAGLE HITS YOUR SHIP, IT<br />
WILL BE AS THOUGH YOU COLLIDED WITH IT. HOWEVER, IF A MINE REACHES<br />
YOUR SHIP, YOU WILL GAIN A PHOTON TORPEDO (OR DISRUPTOR BOLT).<br />
<br />
C) --SEE (C) IN 6.3.6 ABOVE.<br />
<br />
D) --SEE (D) IN 6.3.6 ABOVE.<br />
<br />
YOU CAN ENTER THE TARGET AND ENERGY OR DISTANCE WITH THE<br />
COMMAND ITSELF. (EG. ’YA,1,5050’ WILL TRAIN THE TRACTORS ON<br />
(50,50). IF THE TARGET IS A RETREATING SHIP, IT WILL BE SLOWED TO<br />
1/4 SPEED. IF THE TARGET IS AN EAGLE OR MINE, IT WILL BE PULLED 1<br />
UNIT.)<br />
<br />
'''6.3.8 <u>BOARD</u>'''<br />
<br />
THE BOARD COMMAND ALLOWS YOU TO BOARD OTHER SHIPS OR STARBASES<br />
IN ORDER TO EITHER REINFORCE YOUR SHIP OR AN ALLIED SHIP, OR TO<br />
TAKE AN ENEMY SHIP OVER AND GAIN AN ALLY WHO WILL HELP YOU. FOR A<br />
SUCCESSFUL BOARDING PARTY, YOU MUST BE WITHIN TRANSPORTER RANGE OF<br />
THE TARGET (5 UNITS, BUT PREFERABLY RIGHT NEXT TO YOUR SHIP), AND<br />
HAVE ONLY MINOR DAMAGE TO YOUR TRANSPORTERS (DECK 7 ON THE<br />
ENTERPRISE, DECK E8-AFT ON THE HAVOC). ALSO, IF YOU’RE BOARDING AN<br />
ENEMY SHIP, THEIR DEFLECTORS SHOULD BE FAIRLY LOW (AT MOST 25 FOR<br />
BEST RESULTS) AND YOU SHOULD USE A FAIRLY LARGE BOARDING FORCE<br />
(SAY 100 OR MORE UNLESS IT’S AN EAGLE, WHERE 3-5 WILL PROBABLY DO.<br />
<br />
YOU’LL BE ASKED TO ENTER THE NUMBER IN THE BOARDING PARTY AND<br />
THE TARGET COORDINATES, WHICH CAN ALSO BE ENTERED WHEN THE COMMAND<br />
ITSELF IS ENTERED (EG. ’BO,250,5025’ WILL PREPARE 250 PEOPLE TO<br />
TRANSPORT TO (50,25). IF YOU ENTER A NEGATIVE CREW NUMBER, YOU CAN<br />
BEAM BACK CREW FROM A PREVIOUSLY-BOARDED SHIP, ALLIED SHIP,<br />
STARBASE OR EAGLE.<br />
<br />
WHEN A BOARDED SHIP IS HIT, CASUALTIES WILL BE ASSIGNED<br />
AMONGST THE BOARDING PARTY ON THE SHIP. IF THE CREW ON A C-0<br />
BOARDED SHIP FALLS BELOW 25, YOU WILL LOSE CONTROL OF THAT SHIP<br />
AND CONTROL WILL REVERT BACK TO THE ENEMY. YOU WILL LOSE CONTROL<br />
OF A BOARDED EAGLE IF THE CREW ON IT FALLS BELOW 2.<br />
<br />
TRANSPORTER BEAMS BOUNCE OFF THE DOOMSDAY MACHINE. IF YOU<br />
BOARD MOONBASE ALPHA, ALL REMAINING EAGLES WILL BE LAUNCHED<br />
CONTAINING YOUR MEN. IF YOU BOARD THE KZINTI WARSHIP SUCCESSFULLY,<br />
IT WILL BE SET TO ATTACK/RETREAT MODE AND IT WILL ALWAYS ATTACK.<br />
BOARDED C-0 SHIPS AND STARBASES CAN BE CONTROLLED USING THE<br />
’CEASEFIRE’ AND ’ATTACK’ COMMANDS. BOARDED M-O SHIPS WILL BE<br />
CONTROLLED FROM YOUR TERMINAL.<br />
<br />
WHENEVER YOU BOARD A C-O WARSHIP, AND THE BOARDING PARTY GAINS<br />
CONTROL OF IT, THERE IS A 16.6% CHANCE THAT THE PARTY WILL MUTINY<br />
AND DEFECT TO THE ENEMY, AND A FURTHER 16.6% CHANCE THAT THE ENEMY<br />
WILL SELF-DESTRUCT TO AVOID CAPTURE.<br />
<br />
IF YOU TRY TO BOARD A MANUALLY-OPERATED SHIP THAT HAS<br />
SURRENDERED WITH THE ’SU’ COMMAND, THE BOARDING PARTY WILL<br />
AUTOMATICALLY TAKE OVER THE SHIP, OTHERWISE THERE IS A 16.6%<br />
CHANCE THAT THE PARTY WILL DEFECT TO THE ENEMY. IF NEITHER OF<br />
THOSE THINGS HAPPEN, THEN IT IS UP TO THE OTHER SHIP TO DEFEND<br />
ITSELF USING INTRUDER CONTROL COMMANDS.<br />
<br />
SAY THAT AN ENEMY FORCE HAS JUST LANDED ON YOUR SHIP. THEY<br />
WILL TAKE OVER YOUR SHIP IF:<br />
<br />
1) THEY WIPE OUT YOUR CREW, OR<br />
<br />
2) THEY TAKE OVER EVERY DECK OF YOUR SHIP.<br />
<br />
YOU WILL WIN CONTROL OF YOUR SHIP IF YOU WIPE OUT THE ENEMY<br />
FORCES. ENEMY FORCES INITIALLY CAN TAKE OVER 4 DECKS AT A TIME,<br />
BUT YOU CAN COMBAT THEM USING YOUR INTRUDER CONTROL COMMANDS:<br />
<br />
1) SOUND INTRUDER ALERT- THIS DOES NOT AFFECT THE ENEMY BUT IT<br />
WARNS YOUR CREW OF THE CONDITION AND SO THE CASUALTIES AMONG YOUR<br />
CREW GO DOWN.<br />
<br />
2) EVACUATE PERSONNEL FROM ENEMY-HELD AREAS- BY DOING THIS,<br />
CASUALTIES AMONG YOUR CREW GO DOWN, BUT THE ENEMY IS ABLE TO<br />
DOUBLE THE RATE AT WHICH IT TAKES OVER DECKS OF YOUR SHIP.<br />
<br />
3) CLOSE SECTION ISOLATION DOORS/SEAL OFF ENEMY-HELD AREAS-<br />
DOING THIS CUTS THE ENEMY’S RATE OF SPREAD IN HALF.<br />
<br />
4) FLOOD ENEMY-HELD AREAS WITH NEURAL GAS- DOING THIS CUTS<br />
DOWN THE ENEMY FORCES BY 5 TO 15%.<br />
<br />
5) FLUSH RADIOACTIVE WASTE INTO ENEMY-HELD AREAS- DOING THIS<br />
INCREASES CASUALTIES ON BOTH SIDES BY 15 TO 25%.<br />
<br />
6) DEPRESSURIZE ENEMY-HELD AREAS- DOING THIS INCREASES<br />
CASUALTIES ON BOTH SIDES BY ABOUT 30%.<br />
<br />
7) DISPATCH SECURITY TEAMS TO ENEMY-HELD AREAS- THE<br />
PROBABILITY THAT THE SECURITY TEAMS WILL WIN IS (50 * (NUMBER IN<br />
SECURITY FORCES) / (NUMBER OF INTRUDERS))%. IF YOUR TEAMS LOSE,<br />
THE ENEMY WILL NONE THE LESS SUFFER CASUALTIES.<br />
<br />
8) ACTIVATE SELF-DESTRUCT MECHANISM- TO BE USED AS A LAST<br />
RESORT. THE MECHANISM IS QUITE FINICKY SO IT WILL ONLY WORK 1/3 OF<br />
THE TIME. IT WILL NOT WORK AT ALL IF THE INTRUDERS CAPTURE THE<br />
BRIDGE.<br />
<br />
9) OFFER NO RESISTANCE/SURRENDER- COWARD!<br />
<br />
IF YOU SUCCEED IN WIPING OUT THE INTRUDERS, THERE IS A 20%<br />
CHANCE THAT THE LAST ENEMY WILL DETONATE A BOMB IN YOUR SHIP, BUT<br />
BY INTERROGATION OF THE ENEMY PRISONERS YOU WILL LEARN:<br />
<br />
1) WHERE THEY CAME FROM,<br />
<br />
2) THE ENEMY SHIP’S CREW, DEFLECTORS, PHASERS, AND WARP<br />
ENERGY, THE NUMBER OF TORPEDOES (DISRUPTORS), ENGINE TEMPERATURE,<br />
AND MAYBE EVEN A COUPLE OF SUBSPACE CODES.<br />
<br />
'''6.3.9 <u>CANCEL</u>'''<br />
<br />
THE CANCEL COMMAND ALLOWS YOU TO CANCEL PREVIOUSLY-ENTERED<br />
’PH’, ’TO’, ’YA’, ’DE’, OR ’BO’ COMMANDS. YOU CAN ENTER A ’P’ TO<br />
CANCEL THE ’PH’ COMMAND, ’T’ TO CANCEL THE ’TO’ COMMAND, ’Y’ TO<br />
CANCEL ’YA’, ’D’ TO CANCEL ’DE’ OR ’B’ TO CANCEL THE ’BO’ COMMAND.<br />
THE STRING CAN BE ENTERED WHEN YOU ENTER THE COMMAND (EG. ’CA,PT’<br />
WILL CANCEL THE PHASER AND TORPEDO COMMANDS). YOU ARE NOW FREE TO<br />
RE-ENTER THE CANCELLED COMMANDS IF YOU WISH.<br />
<br />
'''6.4 <u>COMMANDS TO CAUSE ACTION</u>'''<br />
<br />
OKAY, YOU’VE SET YOUR COURSE AND LOCKED YOUR WEAPONS USING THE<br />
COMMANDS FROM THE PREVIOUS SECTION. NOW IT’S TIME TO ACTUALLY MOVE<br />
AND FIRE.<br />
<br />
'''6.4.1 <u>GO</u>'''<br />
<br />
THE GO COMMAND ALLOWS YOU TO MOVE AND FIRE IN ANY SEQUENCE.<br />
YOU WILL BE ASKED TO ENTER A STRING OF CHARACTERS REPRESENTING THE<br />
ORDER IN WHICH YOU WISH TO EXECUTE AN ACTION. ENTER ’M’ TO MOVE,<br />
’P’ TO FIRE PHASERS, ’T’ TO FIRE PHOTON TORPEDOES (OR DISRUPTOR<br />
BOLTS), ’B’ TO INITIATE A BOARDING PARTY, ’Y’ TO ENGAGE A TRACTOR<br />
BEAM, AND/OR ’D’ TO ENGAGE A DEFLECTOR BEAM. IF THE FIRST<br />
CHARACTER IN THE STRING IS A ’C’, THE COMMAND IS CANCELLED SO YOU<br />
COULD GO BACK AND AND SET A WEAPON IF YOU HAD FORGOTTEN. YOU CAN<br />
USE ANY CHARACTER IN ANY ORDER BUT YOU CAN’T USE THE SAME<br />
CHARACTER MORE THAN ONCE IN THE SAME STRING, SO ’TMYTB’ IS ILLEGAL<br />
SINCE YOU TRIED TO FIRE TORPEDOES TWICE. IF YOU INTEND TO ENTER A<br />
COMMAND LIKE ’MT’, MAKE SURE THAT THE TORPEDOES ARE LOCKED ONTO<br />
THE BEARING THE TARGET WILL BE AT AFTER YOU MOVE.<br />
<br />
IT IS ALSO POSSIBLE TO EXECUTE AN ACTION IF SOME PREVIOUS<br />
ACTION WAS SUCCESSFUL OR NOT, BY USING PARENTHESES.<br />
<br />
EG. ’B(M)(PT)’ - IF THE BORD WAS SUCCESSFUL, WE MOVE, OTHERWISE WE<br />
FIRE PHASERS AND TORPEDOES.<br />
<br />
EG. ’B()(P)’ - IF THE BORD WAS SUCCESSFUL, WE DO NOTHING,<br />
OTHERWISE WE FIRE PHASERS.<br />
<br />
EG. ’M(T)P’ - IF THE MOVE WAS SUCCESSFUL, FIRE TORPEDOES, THEN<br />
FIRE PHASERS (REGARDLESS OF WHETHER THE MOVE WAS OR WAS NOT<br />
SUCCESSFUL).<br />
<br />
IN TURN, THIS PARENTHESIZED FORMS CAN BE NESTED WITHIN OTHER<br />
PARENTHESIZED FORMS, AND CAN BE COMBINED WITH THE OTHER FORMS TO A<br />
LIMIT OF 6 LEVELS OF NESTING AND A TOTAL LENGTH OF 80 CHARACTERS<br />
IN THE LINE.<br />
<br />
EG. ’M(T(P(B(D(Y)))))’ AND ’M(T()(B))(PY)D’ ARE POSSIBLE.<br />
<br />
I’LL LEAVE IT TO YOU TO FIGURE OUT WHAT THEY DO.<br />
<br />
’M’ IS SUCCESSFUL IF WE REACH TARGET COORDINATES.<br />
<br />
’P’ IS SUCCESSFUL IF THE PHASER BEAM HITS A SHIP.<br />
<br />
’T’ IS SUCCESSFUL IF THE TORPEDO HITS A SHIP.<br />
<br />
'''7. <u>WHAT HAPPENS DURING AND AFTER YOU GO</u>'''<br />
<br />
WHEN YOU FIRE PHASERS, DAMAGE TO THE ENEMY IS CALCULATED<br />
TAKING INTO ACCOUNT THE ENEMY’S DEFLECTOR SHIELD STRENGTH, THE<br />
STRENGTH OF THE PHASER BEAM, THE DISTANCE BETWEEN YOU AND THE<br />
ENEMY SHIP, WHETHER THE ENEMY IS IN AN ION STORM, AND A RANDOM<br />
NUMBER. WITH A PHOTON TORPEDO, DISRUPTOR BOLT OR MINE, DAMAGE IS<br />
CALCULATED AS ABOVE ONLY WITHOUT INVOLVING DISTANCE.<br />
<br />
WHEN A C-O SHIP SUFFERS DAMAGE, ITS DEFLECTOR SHIELD STRENGTH<br />
DECREASES BY 1.6 TIMES THE DAMAGE FACTOR. WHEN AN M-O SHIP OR<br />
STARBASE SUFFERS DAMAGE, ITS DEFLECTOR STRENGTH DECREASES BY 1.6<br />
TIMES THE MAXIMUM DAMAGE FACTOR, AND CASUALTIES ARE CALCULATED<br />
AMONGST THE CREW. WHEN THE DEFLECTOR SHIELD STRENGTH OF A SHIP<br />
BECOMES LESS THAN ZERO, THE SHIP IS DESTROYED. IF THE CREW OF A<br />
SHIP IS KILLED OFF, IT WILL DRIFT IN SPACE AS A DERELICT UNTIL<br />
BOARDED. THE GAME IS OVER WHEN ONLY ONE SIDE (IE. ONLY C-O<br />
ENEMIES, M-O KLINGON SHIPS OR M-O FEDERATION SHIPS) REMAINS.<br />
<br />
'''7.1 <u>DAMAGE</u>'''<br />
<br />
WHEN YOUR SHIP IS HIT, DAMAGE WILL BE ASSIGNED TO VARIOUS<br />
PARTS OF YOUR SHIP. FOLLOWING IS A LISTING OF WHAT HAPPENS IF<br />
VARIOUS PARTS OF YOUR SHIP ARE HIT:<br />
<br />
1) PHOTON TORPEDO BANKS (ENTERPRISE (POTEMPKIN) DECK 3)- NUMBER OF <br />
PHOTON TORPEDOES DECREASES.<br />
<br />
2) DISRUPTOR BANKS (PART OF HAVOC (CARNAGE) S-2 GRAF UNITS)- <br />
NUMBER OF DISRUPTOR BOLTS DECREASES.<br />
<br />
3) CREWS QUARTERS (ENTERPRISE DECKS 4, 5, 6, 7, 17, 18 19; HAVOC <br />
DECKS 7, 8 E3-FWD, E4-FWD, E5-FWD, ES-AFT. E6-MIDSHIPS) <br />
NUMBER OF CASUALTIES WILL INCREASE.<br />
<br />
4) SICK BAY ON ENTERPRISE (DECK 7)- IF IT RECEIVES MAJOR DAMAGE, <br />
DR. MCCOY WILL CROAK.<br />
<br />
5) TRANSPORTER ROOMS (ENTERPRISE DECK 7; HAVOC DECK ES-AFT)-<br />
NUMBER OF CASUALTIES DURING BOARDING PARTIES INCREASES.<br />
<br />
6) SHIP’S COMPUTER (ENTERPRISE DECK 8; HAVOC DECK 4)- AUXILIARY<br />
COMPUTERS COME ONLINE.<br />
<br />
7) PHASER BANKS (ENTERPRISE DECK 11; HAVOC DECK 11)- PHASER ENERGY<br />
DECREASES.<br />
<br />
8) WARP DRIVE ENGINEERING (ENTERPRISE DECK 16; HAVOC DECK E4-AFT)-<br />
THE CHANCE THAT YOU WILL LOSE STEERING CONTROL INCREASES.<br />
<br />
9) DEFLECTOR ENERGY PUMP (ENTERPRISE DECK 19; HAVOC DECK 10)-<br />
DEFLECTOR SHIELD ENERGY DECREASES.<br />
<br />
10) TRACTOR BEAM MACHINERY ROOM (ENTERPRISE DECK 23; HAVOC<br />
DECK 4)- TRACTOR BEAM RANGE DECREASES.<br />
<br />
11) IMPULSE ENGINES - MAXIMUM WARP DECREASES BY AT MOST 1 UNIT.<br />
<br />
12) WARP DRIVE ENGINE NACELLES/S-2 GRAF UNIT NACELLES - MAXIMUM<br />
WARP DECREASES AND WHEN ENGINES ARE USED THE ENGINE<br />
TEMPERATURE RISES MORE RAPIDLY.<br />
<br />
13) MAIN SENSOR (ENTERPRISE EXTERNAL; HAVOC DECK 10)- RANGE OF MAP<br />
DECREASES.<br />
<br />
14) NAVIGATIONAL DEFLECTOR (ENTERPRISE EXTERNAL; HAVOC DECK<br />
E6‑MIDSHIPS)- RANGE OF DEFLECTOR BEAM DECREASES.<br />
<br />
15) NACELLE SUPPORT PYLONS - THERE IS A CHANCE THE NACELLES WILL<br />
RIP OFF IF YOU G0 OVER A CERTAIN SPEED WHICH WILL BE<br />
GIVEN TO YOU AS A WARNING.<br />
<br />
'''7.2 <u>REPAIR</u>'''<br />
<br />
YOUR SHIP HAS 3 MODES OF REPAIR:<br />
A) ALL DECKS’ DAMAGE FACTORS ARE REDUCED BY 3, PHASER<br />
ENERGY IS INCREASED BY 5OO UNITS, DEFLECTORS BY AT LEAST 10<br />
UNITS, WARP ENERGY BY 1 UNIT, AND CREW AND TORPEDOES MAY BE<br />
INCREASED.<br />
<br />
B) UP TO 8 DECKS ARE REPAIRED, LOWERING THEIR DAMAGE<br />
FACTORS BY A MAXIMUM OF 5, PHASER ENERGY IS INCREASED BY 500<br />
UNITS DEFLECTOR SHIELD ENERGY BY 10 UNITS, WARP ENERGY BY 1<br />
UNIT.<br />
<br />
C) UP TO 4 DECKS ARE REPAIRED, LOWERING THEIR DAMAGE<br />
FACTORS BY A MAXIMUM OF 5.<br />
<br />
IF, FROM THE TIME YOU ENTER THE GO COMMAND UNTIL YOUR TURN<br />
OCCURS AGAIN, YOU SUSTAIN ANY DAMAGE AT ALL, YOU WILL NOT UNDERGO<br />
REPAIR. YOUR DAMAGE CONTROL PARTIES WILL BE TOO BUSY CONTROLLING<br />
THE DAMAGE TO REPAIR ANYTHING.<br />
<br />
IF, DURING THIS TIME, YOU DO SOMETHING (SUCH AS MOVE, FIRE<br />
PHASERS, TORPEDOES, BOARDING PARTY, TRACTOR OR DEFLECTOR BEAM),<br />
BUT DO NOT SUSTAIN ANY DAMAGE, YOU WILL UNDERGO REPAIR MODE C,<br />
SINCE YOUR DAMAGE CONTROL PARTIES WILL BE FREE TO DO A LITTLE<br />
REPAIR WORK.<br />
<br />
IF, DURING THIS TIME YOU DO NOTHING AT ALL (SUCH AS BY TYPING<br />
NOTHING WHEN ASKED TO ENTER THE CONTROL STRING AFTER YOU TYPE<br />
’GO’), YOU WILL UNDERGO REPAIR MODE B, SINCE YOUR DAMAGE CONTROL<br />
PARTIES WILL BE FREE TO START REPAIRS.<br />
<br />
IF YOU ARE DOCKED AT STARBASE (IE. 1 UNIT AWAY FROM IT), YOU<br />
WILL UNDERGO REPAIR MODE A SINCE STARBASES HAVE COMPLETE REPAIR<br />
FACILITIES. ALSO, WHILE AT STARBASE, YOU CAN INCREASE DEFLECTORS,<br />
CREW AND TORPEDOES (DISRUPTORS) BY DRAWING ON STARBASE RESOURCES<br />
(USING THE ’**’ OPTION IN THE ’TRANSFER’ COMMAND).<br />
<br />
NOTE- ONCE YOUR WARP DRIVE ENGINE NACELLES ARE DESTROYED,<br />
YOUR ENGINES CAN ONLY BE REPAIRED AT STARBASE.<br />
<br />
NOTE- ONCE THE NUMBER OF CREW ON YOUR SHIP DIPS BELOW 100, YOU<br />
WILL NOT HAVE ENOUGH PEOPLE TO MAKE REPAIR MODES B OR C.<br />
<br />
NOTE- IF YOUR PHASERS HAVE A MAIN COIL BURNOUT, THEY WILL<br />
REPAIR FASTER IF YOU ARE UNDERGOING REPAIR MODE A, B OR C.<br />
<br />
'''7.3 <u>ENEMY FIRING</u>'''<br />
<br />
WHEN THE GAME BEGINS, THE ENTERPRISE TAKES THE FIRST TURN.<br />
AFTER IT HAS GONE (IE. AFTER IT HAS ENTERED A GO COMMAND), THE<br />
POTEMPKIN TAKES ITS TURN, THEN THE HAVOC, AND FINALLY THE CARNAGE.<br />
IF ANY OF THESE SHIPS ARE NOT IN THE GAME, THEN THE TURN PASSES<br />
DIRECTLY TO THE NEXT SHIP LISTED. AFTER THE CARNAGE HAS GONE, THE<br />
FUN BEGINS:<br />
<br />
1) STARBASES OPEN FIRE (IF THEY’RE IN THE GAME) UNLESS THE<br />
STARBASE CREW IS ZERO, STARBASE DEFLECTORS LESS THAN 25, OR THE<br />
NEAREST ENEMY VESSEL IS MORE THAN 25 UNITS AWAY. STARBASES CONVERT<br />
AND FIRE 5 DEFLECTOR ENERGY UNITS AT THE NEAREST ENEMY (0.1 UNITS<br />
IF THE TARGET IS AN EAGLE). IF STARBASE RECEIVES NO DAMAGE SINCE<br />
ITS LAST TURN, IT WILL UNDERGO REPAIR, INCREASING ITS DEFLECTOR<br />
STRENGTH BY 10 UNITS.<br />
<br />
2) COMPUTER-OPERATED SHIPS (KLINGON, ROMULAN, THOLIAN, ETC.)<br />
MOVE AND FIRE. THESE SHIPS DO NOT OPEN FIRE UNLESS THE NEAREST<br />
ENEMY VESSEL IS LESS THAN 25 UNITS AWAY. THE PROBABILITY THAT THE<br />
ENEMY WILL MISS IS (3 * DISTANCE TO TARGET)%.<br />
<br />
3) IT’S BACK TO THE ENTERPRISE’S TURN.<br />
<br />
'''8. <u>IF YOU’RE A BEGINNER....</u>'''<br />
<br />
IF YOU’VE MADE IT THIS FAR. AND YOU’RE CONFUSED, TAKE HEART.<br />
THINGS COULD BE WORSE - YOU COULD BE THIS MONSTER’S PROGRAMMER.<br />
IF YOU’RE A BEGINNER, I SUGGEST YOU IGNORE THE POTEMPKIN, HAVOC,<br />
CARNAGE AND STARBASES AND JUST PLAY AS THE ENTERPRISE. AS YOUR<br />
FIRST ENEMY, TRY THE KLINGON WARSHIP. I’VE DELIBERATELY MADE THEM<br />
EASIER TO BEAT THAN THE OTHERS SO YOU CAN GET A BIT OF PRACTICE IN<br />
BEFORE MOVING UP TO HARDER ENEMIES. AS YOUR FIRST COMMAND IN A<br />
GAME, TRY A MAP OR INFO COMMAND (NOTE ALL COMMANDS CAN BE<br />
ABBREVIATED TO JUST THE FIRST 2 LETTERS). HERE’S A LIST OF THE<br />
BASIC COMMANDS YOU SHOULD KNOW: MAP, INFO, TRANSFER, COURSE,<br />
PHASER, TORPEDO, CANCEL, GO. FROM THESE BASIC COMMANDS YOU EXPAND<br />
YOUR KNOWLEDGE AND BECOME A FANCIER PLAYER AS TIME PROGRESSES.<br />
<br />
OFTEN BEGINNERS TO THE GAME WILL ASK ME IF SOMETHING OR OTHER<br />
IS POSSIBLE OR LEGAL IN THE GAME. THE ANSWER IS: TRY IT! IF<br />
SOMETHING IS ILLEGAL, YOU’LL BE TOLD. THESE INSTRUCTIONS ARE NOT<br />
MEANT TO BE COMPREHENSIVE - JUST BECAUSE SOMETHING IS NOT<br />
MENTIONNED HERE DOES NOT MEAN IT CAN’T BE DONE.<br />
<br />
LIVE LONG AND PROSPER.<br />
<br />
'''9. <u>ENTERPRISE DECKS</u>'''<br />
<br />
HERE IS A LISTING OF THE FILE ’KIRK.DAT’ WHICH CONTAINS THE<br />
DECKS OF THE ENTERPRISE AND POTEMPKIN TO WHICH DAMAGE IS ASSIGNED.<br />
THE ENTERPRISE (POTEMPKIN) CONSISTS OF A SAUCER-SHAPED PRIMARY<br />
HULL (DECKS 1 TO 11), A CYLINDRICAL SECONDARY HULL (DECKS<br />
8‑SECONDARY TO 23) BELOW THE PRIMARY HULL, AND TWO CYLINDRICAL<br />
WARP DRIVE NACELLES WHICH ARE CONNECTED TO THE SECONDARY HULL BY<br />
SUPPORT PYLONS.<br />
<br />
Deck 1-Bridge<br />
Deck 2-Sciences Laboratories<br />
Deck 3-Photon Torpedo Bank/Sciences Labs<br />
Deck 4-Junior Officers Quarters/Fresh Water Tanks/Briefing Room<br />
Deck 5-Officers Quarters/Emerg. Battery Rooms/Air Cond. Mach. Rooms<br />
Deck 6-Main Crew’s Quarters/Main Mess room/Engineering<br />
Deck 7-Sick Bay/Emerg. Bridge/Transporter Rooms/Engineering/Quarters<br />
Deck 8-Life Quality Facilities/Ship’s Computer/Recreation Facilities<br />
Deck 8-Secondary Hull-Separation Machinery<br />
Deck 9-Recycling and Fabrication Facilities/Raw Materials Storage<br />
Deck 9-Secondary Hull-Aux. Machinery Room<br />
Deck 10-Cargo + Basic Raw Materials Storage/Cargo Transporter<br />
Deck 10-Secondary Hull-Observation Lounges<br />
Deck 11-Phaser Banks/Aux. Fire Control/Power Sensor Platform<br />
Deck 11-Secondary Hull-Observation Lounges<br />
Deck 12-Observation Lounges<br />
Deck 13-Observation Lounges<br />
Deck 14-Observation Lounges/Cargo Hold<br />
Deck 15-Visicoms/Air Cons. Mach. Room/Fresh Water Tanks<br />
Deck 16-Medical Section/Warp Drive Engineering/Maintenance Shops<br />
Deck 17-Crew’s Quarters/Hanger Observation Gallery,Control Tower<br />
Deck 18-Crew’s Quarters/Shuttlecraft Hangar Deck/Deflector Energy Pump<br />
Deck 19-Crew’s Quarters/Hydroponics Lab/Botany Section<br />
Deck 20-Recreation Area/Swimming Pool/Shuttlecraft Maintenance<br />
Deck 21-Food + Beverages Preparation Center/Bowling Alley/Laundry<br />
Deck 22-Waste Reconversion and Fabrication Facilities<br />
Deck 23-Stowage/Cargo Holds/Tractor Beam Mach. Room<br />
Primary Hull - Impulse Engine<br />
Port Warp Drive Engine Nacelle<br />
Starboard Warp Drive Engine Nacelle<br />
Port Nacelle Support Pylon/Jeffries Tube<br />
Main Sensor and Navigational Deflector<br />
Starboard Nacelle Support Pylon/Jeffries Tube<br />
<br />
'''10. <u>HAVOC DECKS</u>'''<br />
<br />
HERE IS A LISTING OF THE FILE ’KOLOTH.DAT’ WHICH CONTAINS THE<br />
DECKS OF THE HAVOC AND CARNAGE TO WHICH DAMAGE IS ASSIGNED. THE<br />
HAVOC (CARNAGE) CONSISTS OF A BULBOUS PRIMARY HULL (DECKS 0 TO 11)<br />
CONNECTED BY A LONG NARROW ACCESS ROOM TO THE SECONDARY (OR<br />
ENGINEERING) HULL (DECKS E1 TO E9), AND TWO S-2 GRAF UNIT NACELLES<br />
WHICH ARE CONNECTED TO THE ENGINEERING HULL BY SUPPORT PYLONS.<br />
<br />
Deck 0-Search and Navigation Sensors<br />
Deck 1-Bridge<br />
Deck 2-Medical and Sciences Labs<br />
Deck 3-Sick Bay/Ship’s Computers/Tractor Beam Mach. Room<br />
Deck 4-Transporter Rooms/Ship’s Computers/Life Support<br />
Deck 5-Food Preparation/Small Arms Arsenal<br />
Deck 6-Fwd-Emerg. Bridge/Inspirational Media Room/Weapons Range/H2O Tanks<br />
Deck E6-Midships-Crews Quarters/Navigation Deflectors/Emerg. Computers<br />
Deck E6-Aft-2nd Class Emerg. Bridge/Aft Surveilance Room/Emerg. Batteries<br />
Deck 7-Senior Officers’ Quarters<br />
Deck 8-Junior Officers’ Quarters<br />
Deck 9-Forward Surveillance Room/Interrogation Room, Mind Scanner, Agony Booth<br />
Deck 10-Main Sensor/Deflector Energy Pump/Aux. Fire Control<br />
Deck 11-Phaser Banks<br />
Deck E1-Hangar Deck<br />
Deck E2-Craft Maintenance/Emerg. Generator<br />
Deck E3-Fwd-Ship’s Guards’ Quarters/Water Source<br />
Deck E3-Aft-Emerg. Reactor/Engineering Computers/Impulse Engine Room<br />
Deck E4-Fwd-Crew’s Quarters<br />
Deck E4-Aft-Engineering/Water+Waste Reconversion/Power Conversion<br />
Deck E5-Fwd-Fesh Water Tanks/Sciences Laboratories/Crews Quarters<br />
Deck E5-Aft-Combat Troops’ Quarters/Battle Sick Bay/Air Cond. Mach. Room<br />
Deck E7-Port-Crew’s Gymnasium/Laundry/Weapons Proficiency Room<br />
Deck E7-Stbd-Food Fabrication/Visicoms/Interrogation Rooms/Brig<br />
Deck E8-Fwd-Waste Reconversion and Fabrication Facilities<br />
Deck E8-Aft-Main Arsenal/Combat Troops Staging Area/Mass Invasion Transporters<br />
Deck E9-Cargo/Storage Facilities for Prefab Fortifications<br />
Impulse Engines<br />
Port S-2 Graf Unit Nacelle/Disruptor Banks<br />
Starboard S-2 Graf Unit/Disruptor Banks<br />
Port Nacelle Support Pylon/Engine Machinery<br />
Starboard Nacelle Support Pylon/Engine Machinery<br />
Primary-Secondary Hull Access Boom/Access Boom Engine/Cooling Tubes<br />
<br />
'''11. <u>THANKS</u>'''<br />
<br />
I OWE A DEBT OF GRATITUDE TO THE MANY PEOPLE WHO HAVE LENT ME<br />
BOOKS, GIVEN ME SUGGESTIONS, HELPED ME DEBUG THE PROGRAM, AND EVEN<br />
DONATED COMPUTER TIME; ETC.; WITHOUT WHOSE HELP THIS PROGRAM<br />
WOULDN’T BE THE MONSTER IT IS TODAY. THANKS TO: MR. STEPHEN<br />
B. SHARPE, DR. A: DIXON (UNIVERSITY OF WESTERN ONTARIO),<br />
MR. D. MACRAE (UWO), MR. D. KIDD (UWO), MR. J. E. BROWN (OAKRIDGE<br />
SECONDARY SCHOOL, LONDON ONTARIO), MR. LORNE JOHNSON (OAKRIDGE),<br />
GEOFFREY A. COLLYER, JEFF WENN, TERRY FAVELL, AND A SCORE OF<br />
OTHERS.<br />
<br />
'''12. <u>BIBLIOGRAPHY</u>'''<br />
<br />
BOOKS:<br />
<br />
BLISH, JAMES. SPOCK MUST DIE. NEW YORK : BANTAM BOOKS INC., 1970.<br />
<br />
BLISH, JAMES, STAR TREK 1 TO STAR TREK 12. NEW YORK : BANTAM BOOKS<br />
INC., 1967 - 77.<br />
<br />
FOSTER,ALAN DEAN. STAR TREK LOG 1 TO STAR TREK LOG 9. NEW YORK :<br />
BALLANTINE BOOKS, 1974 - 77.<br />
<br />
GERROLD,DAVID. THE TROUBLE WITH TRIBBLES. NEW YORK : BALLANTINE<br />
BOOKS, 1973.<br />
<br />
GERROLD, DAVID. THE WORLD OF STAR TREK. NEW YORK : BALLANTINE<br />
BOOKS, 1975.<br />
<br />
JOSEPH, FRANZ. STAR FLEET TECHNICAL MANUAL. 1ST ED., NEW YORK :<br />
BALLANTINE BOOKS, 1975.<br />
<br />
TRIMBLE, BJO. STAR TREK CONCORDANCE. 1ST ED., NEW YORK :<br />
BALLANTINE BOOKS, 1975.<br />
<br />
WHITFIELD, STEPHEN E., AND GENE RODDENBERRY. THE MAKING OF STAR<br />
TREK. NEW YORK : BALLANTINE BOOKS, 1968.<br />
<br />
BLUEPRINTS:<br />
JOSEPH, FRANZ. STAR TREK BLUEPRINTS - GENERAL PLANS - CONSTITUTION<br />
CLASS U.S.S. ENTERPRISE. 2ND ED., NEW YORK : BALLANTINE BOOKS,<br />
1975.<br />
<br />
MCMASTER, MICHAEL. BOOK OF KLINGON PLANS - D7 CLASS BATTLE<br />
CRUISER. 1ST ED., LOS ANGELES : LINCOLN ENTERPRISES.<br />
<br />
== External links ==<br />
<br />
* tbd<br />
<br />
[[Category: Games]]<br />
[[Category: SIMH Tutorials]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=MULTI-TREK&diff=33153
MULTI-TREK
2024-02-01T17:15:59Z
<p>Vaxorcist: Category "SIMH Tutorials" added</p>
<hr />
<div>While searching the Internet for information on the [[VAX]] [[TREK7]] game, I stumbled over another Star-Trek game called '''MULTI-TREK''' or just '''MTREK''' in the [[DECUS]] [https://www.digiater.nl/openvms/decus/ collection of VMS software tapes].<br />
<br />
I used the [[ods2]] tool from the [[SIMH]] [https://github.com/open-simh/simtools tools collection] to transfer the MTREK files to a VMS disk image file.<br />
<br />
I decided to use the [[FORTRAN]] source files instead of the [[RATFIV]] ones, because I could not get the RATFIV [[compiler]] going (I will try that again later).<br />
<br />
The date of the RATFIV source files (28-APR-1982) gave me a clue to try [[VMS]] V3 for MTREK, which proved to be successful.<br />
<br />
Using the @BUILD command gave some error messages, which were overcome in some steps by trial and error.<br />
<br />
The nasty surprise showed up when I started the MTREK program that had compiled and linked so easy.<br />
Directly after entering the chosen vessel number, the program "froze" and did not accept anymore input except CTRL-C or CTRL-Y, both of which aborted the game.<br />
After studying the sources, and some simple debugging attempts, I decided to employ the VAX [[debugger]] to obtain more information as to what was going on.<br />
<br />
A helpful chap from the U.K., Dave Roberts, replied to my call for help on the [https://forum.vcfed.org/index.php?forums/dec/ VCFed DEC Forum]; and together we attempted to debug and correct the errant behaviour.<br />
<br />
The first step to success was the detection of the endless loop that caused the "freezing" of the program.<br />
Then Dave found the suspicious subroutine "INCHAR", and after analyzing the QIO calls and their return codes with two VMS manuals I provided, he finally found out that a necessary initialisation routine was commented out for whatever reason. After removing the "C" (for "Comment") in the respective source line, followed by re-compiling and re-linking, MTREK ran as expected. Little cause for a great event ...<br />
<br />
Hurray, game time!<br />
<br />
This is an example of a player's view at the universe:<br />
<br />
Energy : 9848.5 * * Scores<br />
Shields : 0.0<br />
R 1 -1000. *<br />
Warp : 3.00 * 2 0.<br />
Course : 3.00 3 0.<br />
4 0.<br />
X co-ord : 38.8 * 5 0.<br />
Y co-ord : 89.5 1 6 0.<br />
# 7 0.<br />
Torps : 10 8 0.<br />
Seekers : 4<br />
Hyper : 3<br />
Scan: 2<br />
Def Ship : 2 * Dir : 1.75<br />
Def Direc: 1.75 Dist: 51.08<br />
* Sect: 7, 2<br />
. .<br />
<br />
== Introduction to MTREK ==<br />
<br />
File "aareadme.doc" from the MTREK distro:<br />
<br />
MULTI-TREK is a game similar to traditional Star-Trek games<br />
except that it involves several players (currently up to 8), who<br />
play against each other in real time rather than against<br />
imaginary Klingons, Romulans or whatever. The MULTI-TREK<br />
universe consists of a 100 by 100 matrix, of which an approximate<br />
20 by 20 matrix of each player's immediate area is displayed and<br />
continuously updated at their terminal. MULTI-TREK was<br />
originally submitted to the New Orleans RSX/IAS sig tape, then to<br />
the 1979 San Diego RSX/IAS sig tape with the addition of robot<br />
ships. Since then it has been recoded in RATFIV and has<br />
significant enhancements and improvements, most notably the<br />
addition of energy nets, an improved screen display, much better<br />
input-output (any terminal with clear screen and cursor<br />
positioning may be used at speeds from 1200 baud on up), use of<br />
default ship and direction with most commands ("L" sets the<br />
default direction), more competitive scoring, smarter robot<br />
ships,reverse polish command sequences (fewer keystrokes), and<br />
fewer bugs. This version is being submitted to the Spring 1982<br />
VAX tapes and features the rpn command sequences and fades that<br />
don't exactly show up on radar locates. Complete instructions<br />
for starting and playing MULTI-TREK are in the file MTREK.DOC.<br />
<br />
The game consists of a driver task (MTREKD), a player task<br />
(MTREK) for each terminal, and a shared global common area for<br />
inter-task communication. This version runs on VAX VMS, however,<br />
it should run under any system with shared global areas and<br />
rudimentary task switching or time-sharing. Real-time systems<br />
without time-sharing may have to play with priorities to insure<br />
that the driver task gets sufficient CPU time and that all<br />
players get an equal amount of time.<br />
<br />
MULTI-TREK was written with a structured Fortran called<br />
RATFIV. The IAS version contains all of the Fortran produced by<br />
RATFIV, as well as the RATFIV source (file type .RAT). The VAX<br />
VMS version does not include the .FOR files, however the RATFIV<br />
compiler is included on both distribution tapes.<br />
<br />
MTREK will work properly with any terminal with clear screen<br />
and cursor positioning. The source code is set up to drive<br />
ADM3-A's or VT100's and VT52's. If you are using different<br />
terminals, you should modify the file "TERMINAL.RAT" (you could<br />
modify "TERMINAL.FTN") to drive your terminal. Modification<br />
should be straight-forward as the code is commented on where to<br />
change it.<br />
<br />
To build MTREK, do<br />
<br />
@BUILD<br />
<br />
The VAX VMS version places the common area, LEDFOR, on<br />
SYS$SHARE and installs it /WRITE/SHARE. It also puts MTREK.EXE,<br />
the player task, and MTREKD.EXE, the universe manager task, on<br />
SYS$SYSTEM, and installs MTREK.EXE with DETACH and ACNT<br />
privileges, so that anyone can start up MTREKD as a detached<br />
process (only one copy of MTREKD runs at a time, however).<br />
<br />
After building MTREK, first run MTREKINI. Then, on VAX VMS<br />
systems, say MCR MTREK and you are off and running. On IAS<br />
systems, the universe manager MTREKD must be started by hand<br />
before MTREK is run. You can run MTREKD on a dedicated terminal<br />
or install it and run it /REAL.<br />
<br />
== Status Quo ==<br />
<br />
== How to run MTREK on a real VAX or SIMH VAX ==<br />
<br />
Get the [https://drive.google.com/drive/folders/1LznfGLX4LDHMgJRgRLYSItrvrFNLwri9?usp=sharing MTREK kit] and follow the instructions included.<br />
<br />
== MTREK Manual ==<br />
<br />
File "mtrek.doc" from the MTREK distro:<br />
<br />
1.0 INTRODUCTION<br />
<br />
This game was written as a tool to test the use of shared global<br />
areas with time-shared programs. The game consists of five parts, the<br />
shared global area, the driver task (MTREKD) which controls the<br />
universe, the MTREK task which interfaces with the players, the<br />
initialization program (MTREKINI), and the robot ship program (ROBOT).<br />
<br />
The source code for the game is intended to be public so that<br />
enhancements can be added by any interested party. Those making<br />
additions should add their names to those listed as contributors at<br />
the start of the MTREKD program.<br />
<br />
NOTE<br />
<br />
MTREK was originally developed under IAS but is written<br />
almost entirely in RATFOR and should be readily convertible to<br />
RSX-11M or, for that matter, to any system that supports<br />
shared global areas and time-shared tasks or some equivalent.<br />
<br />
MTREK was originally written at Boeing Computer Services<br />
in Seattle, Washington by Don Ledford, John Lutch, and Ray<br />
French. The current game is an enhanced version developed at<br />
The Institute For Cancer Research in Philadelphia, Pa. by<br />
Bill Wood, Bill Cael, and Bob Stodola.<br />
<br />
<br />
Good luck, and don't get discouraged as the game requires a little<br />
practice!<br />
<br />
<br />
2.0 PLAYING MULTI-TREK<br />
<br />
The game is very similar to the traditional Star-Trek game with<br />
the following exceptions. First, the game involves several players<br />
(1-8), each of whom has his own terminal and starship. Second, the<br />
game runs in real time as far as the players are concerned. For<br />
example, if you are going warp 8 you will continue to move regardless<br />
of your activity at the terminal (unless you are destroyed, hit<br />
something, run out of energy, or change your warp speed). Each<br />
player's status and position as well as the scores of all players is<br />
displayed and continuously updated at each player's terminal. (The<br />
update rate is 2.5 times per second, but the source code is commented<br />
on where to change it should you wish to do so.) Third, at the present<br />
time there are no Klingons or Romulans to shoot down, instead you<br />
shoot (or at least attempt to shoot) the other players.<br />
<br />
The universe consists of a 100 by 100 matrix which wraps around<br />
itself. Therefore if you move off one end of the universe you appear<br />
on the other end. (This is true of phasers and torpedoes also.)<br />
<br />
The universe is made up of the following items:<br />
<br />
1. " " Empty space<br />
<br />
2. "-" Universe boundary<br />
<br />
3. "*" Star<br />
<br />
4. "B" Star-base (ram it to dock and thereby refuel)<br />
<br />
5. "H" Hyperspace point (described below)<br />
<br />
6. "R" Random hyperspace point (also described below)<br />
<br />
7. "+" Torpedo<br />
<br />
8. "^" Homing torpedo (seeker)<br />
<br />
9. "#" Black hole will pursue nearest player<br />
<br />
10. "@" Anti-matter pod<br />
<br />
11. "%" Energy net<br />
<br />
12. "1"-"8" Player's ships<br />
<br />
<br />
2.1 Hyperspace Ports<br />
<br />
When a hyperspace port is hit by a ship the ship is teleported to<br />
a new location in the universe. The "H" type of hyperspace port can<br />
be used to go to a set location whereas the "R" type of port produces<br />
a random jump. The "H" ports are located at fixed locations; these<br />
are as follows:<br />
<br />
^PORT ^NUMBER ^X ^COORD ^Y ^COORD<br />
----------- ------- -------<br />
<br />
1 20 75<br />
2 50 70<br />
3 80 75<br />
4 20 25<br />
5 50 30<br />
6 80 25<br />
<br />
^THE NETWORK OF PORTS LOOKS LIKE THIS:<br />
<br />
1 3<br />
2<br />
<br />
<br />
<br />
<br />
5<br />
4 6<br />
<br />
<br />
By using the "H" command a player can set the port number he<br />
wishes to appear beside the next time he goes into hyperspace through<br />
an "H" type port. For example, if a player used the "H" command to<br />
set his hyperspace setting to 4, the next time he ran into an "H"<br />
character he would appear near coordinates 20,25.<br />
<br />
A player's anti-matter pod can travel through hyper-space also;<br />
upon re-emergence in the universe, it blows up. Pods going through<br />
random hyperspace reappear randomly; those going through "H" type<br />
ports reappear at the pod owner's current hyperspace jump point.<br />
<br />
<br />
2.2 Scoring<br />
<br />
The current scores of all players are displayed on the screen. A<br />
'*' beside a score indicates an active player. The following actions<br />
result in score changes:<br />
<br />
1. Torpedo hit on enemy vessel: +500<br />
<br />
2. Homer hit on enemy vessel: +300<br />
<br />
3. Phaser hit on enemy vessel: +(between 70 and 200 depending on<br />
distance)<br />
<br />
4. Pod explosion: +(between 300 and 1500 depending<br />
on distance)<br />
<br />
5. Torpedo hit on base: -200<br />
<br />
6. Getting destroyed: -1000<br />
<br />
<br />
2.3 Energy Consumption<br />
<br />
1. Shooting phasers: -50<br />
<br />
2. Warp: -.5 * WARP SPEED per time interval<br />
<br />
3. Send message: -10<br />
<br />
4. Collide with star: -200<br />
<br />
5. Collide with ship: -100<br />
<br />
6. Cloaking: -25 per time interval (default)<br />
<br />
7. Energy net: -75 per net unit constructed (default)<br />
<br />
8. Tractor beam: -100 per time interval (default)<br />
<br />
Energy loss due to weapon hit is a function of shield strength<br />
and weapon energy.<br />
<br />
<br />
2.4 Calculations<br />
<br />
The following formula are used:<br />
<br />
1. Phaser hit energy:<br />
<br />
ENERGY=900./(4. + DISTANCE)<br />
<br />
2. Torpedo hit energy:<br />
<br />
ENERGY=500.<br />
<br />
3. Shield protection:<br />
<br />
SHIELD ABSORBTION FACTOR=SHIELD ENERGY/1000.<br />
(^WITH A MAXIMUM VALUE OF 1.)<br />
SHIELD DIRECTION FACTOR=<br />
(.5 + ABS(SHIP'S DIREC - WEAPON'S DIREC)/360)<br />
SHIELD FACTOR = SHIELD DIRECTION FACTOR *<br />
SHIELD ABSORBTION FACTOR<br />
<br />
SHIELD ENERGY =<br />
SHIELD ENERGY - SHIELD FACTOR * ENERGY OF HIT<br />
ENERGY OF SHIP = ENERGY OF SHIP -<br />
(1.2 - SHIELD FACTOR) * ENERGY OF HIT * 6<br />
<br />
4. Tractor beam pull:<br />
<br />
8./SQRT(MAX(1., DISTANCE BETWEEN SHIPS-6.))<br />
<br />
Anti-matter causes both damage to the scan, and results in an<br />
energy hit. Both of these effects are energy dependent.<br />
<br />
<br />
2.5 MTREK commands<br />
<br />
All commands consist of one character, and most of them can be<br />
preeceded by a numeric argument. This argument can be input with the<br />
command character, or can be a default ship or direction. Generally,<br />
typing a new ship number or direction changes the default ship or<br />
direction, however there are exceptions. In addition, the "L" (long<br />
range scan) command changes the default direction to the direction of<br />
the scanned ship, which is convenient for firing at the scanned ship.<br />
See below for other commands which change the defaults. To use a<br />
default value, simply type the command letter.<br />
<br />
1. Help<br />
"?" Prints a summary of all commands.<br />
<br />
2. Shields<br />
"S" Raise or lower shields. This may be preceeded by a<br />
real number (+ or -). Your default shield change value<br />
is reset every time you set positive shields, and this<br />
default value may be used by just typing the "S"<br />
command. 1000 units is the most that will do any good.<br />
But you may want a little reserve.<br />
<br />
3. Reset<br />
"R" Clears the screen and redraws the entire display.<br />
<br />
4. Torpedoes<br />
"T" Fire torpedoes. A direction may be specified. "T"<br />
fires in the default direction, a number fires in that<br />
direction and resets the default. Torpedoes move at<br />
warp 10, and destroy anti-matter pods.<br />
<br />
5. Phasers<br />
"P" Fire phasers. A direction may be specified. "P" fires<br />
in the default direction, A number fires in that<br />
direction and resets the default. Phasers are<br />
instantaneous, have a range of 10 squares, and shoot a<br />
band 3 squares wide. They will not destroy torpedoes<br />
(except homers).<br />
<br />
6. Locate<br />
"L" Long range scan for another player. The "L" command<br />
sets the default direction to that of the scanned ship.<br />
It may be precceded by a ship number as an argument.<br />
"L" locates a default ship. If a ship number is given,<br />
the default ship is reset to that ship.<br />
<br />
7. Message<br />
"M" Send a message to another player on subspace radio.<br />
"M" sends to the default ship, a ship number sends to<br />
that ship. A ship number of zero broadcasts the<br />
message to all ships. The default ship is not reset.<br />
<br />
8. Warp<br />
"W" Set warp speed 0-8.<br />
<br />
9. Course<br />
"C" Set course 0-12 (clock face). This does not affect<br />
your warp speed or default direction. However, the<br />
default direction may be used to set the course. All<br />
directions are to be specified in "clock face" numbers.<br />
For example:<br />
<br />
0. is up<br />
<br />
9. is left 3. is right<br />
<br />
6. is down<br />
<br />
7.5 is toward the lower left corner, etc.<br />
<br />
10. Quit<br />
"Q" Quit.<br />
<br />
11. Hyperspace<br />
"H" Set hyperspace jump point 1 through 6.<br />
<br />
12. Cloak on<br />
"F" Fade away. The cloaking device is a continuous energy<br />
drain when activated. A cloaked ship cannot move.<br />
Typeing "F" will toggle this mode.<br />
<br />
13. Cloak off<br />
"A" Appear.<br />
<br />
14. Energy net on/off<br />
"E" Start/stop energy net construction. Energy nets<br />
provide a "wall" which other ships will bounce off of,<br />
however your ship travels instantaneously through your<br />
energy nets. Torpedoes may be used to destroy nets.<br />
The black hole is blocked by them. Phasers do not<br />
penetrate nets.<br />
<br />
15. Seeking torpedo launch<br />
"K" If you specify a ship number to home in on the default<br />
will be changed. If none is specified then the default<br />
ship is located. Homing torpedoes can not be fired at<br />
faded ships. Homing torpedoes destroy anti-matter<br />
pods. Seeking torpedoes can be shot down with phasers<br />
(at least sometimes).<br />
<br />
16. Anti-matter launch<br />
"Z" If a direction is specified the default direction is<br />
reset. Pods move at warp 5. "Z" fires in the default<br />
direction, When an anti-matter pod hits a hyper-space<br />
port, it travels through it to your current hyperspace<br />
jump point and blows up. Pods also travel through<br />
random hyper-space ports to a random location and blow<br />
up.<br />
<br />
17. Anti-matter freeze<br />
"N" Stop movement of anti-matter device. (It will become a<br />
static mine.)<br />
<br />
18. Anti-matter detonate<br />
"X" Detonate anti matter pod. This explosion destroys an<br />
entire area, except for bases and hyperspace points.<br />
The pattern of the explosion is as below.<br />
<br />
X <br />
X X X <br />
X X X<br />
X X X X X X X <br />
X X X <br />
X X X<br />
X<br />
<br />
Ships within 4 of an exploding pod lose some energy and<br />
have their vision partially obscured. The black hole<br />
is randomly relocated when caught in a pod explosion.<br />
<br />
19. Tractor beams<br />
"B" Set tractor beam target ship (1-8). 0 to stop tractor<br />
beam. Tractor beams are used to pull your opponent's<br />
ship towards you. The closer the ships are the<br />
stronger the pull of the tractor beam. The default<br />
ship is reset.<br />
<br />
20. Verbose/Non-verbose mode<br />
"V" Flip on/off verbose mode. In non-verbose mode, only<br />
the first letter of each word is printed. For example,<br />
<br />
+ TORPEDO HIT ALIEN!<br />
<br />
becomes<br />
<br />
+THA<br />
<br />
This is sometimes useful in the heat of battle on a<br />
slow (1200 baud) terminal.<br />
<br />
21. Flush type-ahead buffer<br />
" " The game keeps an internal typeahead buffer of up to 20<br />
characters. Typeing " " will flush this buffer.<br />
<br />
<br />
3.0 STARTING THE GAME<br />
<br />
If you are starting a new game, first initialize the universe<br />
using MTREKINI:<br />
<br />
$ RUN MTREKINI<br />
<br />
It will ask a series of set up questions (defaults are invoked by<br />
<CR>):<br />
<br />
1. Any random integer between -32k and +32k (default = 0).<br />
<br />
2. A star density between 2 and 3 is good (default = 2.0).<br />
<br />
3. About 20 to 25 star-bases is ok (default = 20).<br />
<br />
4. Usually 5-10 random jump points (default = 6).<br />
<br />
5. A cloaking energy drain of 20 to 40 (default = 25).<br />
<br />
6. Net construction energy drain of 0 to 2000 (default = 75).<br />
<br />
7. Tractor beam energy drain of 0 to 2000 (default = 100).<br />
<br />
8. Black hole speed of 2. to 5. (default = 4.5).<br />
<br />
<br />
3.1 Player Initiation<br />
<br />
Several crt terminals are required to play the game. The driver<br />
program, MTREKD, may be started automatically on your system. (It is<br />
at ICR.) If not, it must be started up prior to playing. Then each<br />
player should issue the following command at his terminal:<br />
<br />
$ RUN MTREK<br />
<br />
A list of unoccupied ships will be displayed, so choose an unoccupied<br />
ship and you are ready to play. It is possible for two or more<br />
players to control the same ship by selecting an occupied ship, e.g.,<br />
one player can control navigation and the other weapons. Players may<br />
enter and leave the game at any time.<br />
<br />
<br />
3.2 Robot Ships<br />
<br />
In addition to playing against human opponents you can turn the<br />
unused ships over to computer control. This is done by starting the<br />
ROBOT program. You can choose the ships to be controlled and the<br />
capability of the ships' robot skippers.<br />
<br />
Each running ROBOT program can control several ships which will<br />
act as a team. If more than one ROBOT program is started then their<br />
ships will fight with each other. Robot ships are started with the<br />
command:<br />
<br />
$ RUN ROBOT<br />
<br />
A list of unoccupied ships will be displayed. Enter the number(s) of<br />
the ship(s) to be under robot control. When the robot "team" has been<br />
selected, enter <CR> and the ROBOT program will ask several questions<br />
to set up the ability of the robot skippers (as with MTREKINI,<br />
defaults are invoked by <CR>):<br />
<br />
1. Maximum speed of robot ships (default = warp 8).<br />
<br />
2. Robot reaction time (default = 1.5).<br />
<br />
3. Amount of phaser fire (default = 5).<br />
<br />
4. Degree of inaccuracy (default = 0 degrees).<br />
<br />
<br />
4.0 TERMINATING THE GAME<br />
<br />
It is important that the last MTREK players clean up the system<br />
before they leave. This is done by issuing the following set of<br />
commands:<br />
<br />
1. Terminate each MTREK program by entering the "Q" command.<br />
<br />
2. If you are running any ROBOT programs abort each one as follows:<br />
<br />
<CNTRL> C<br />
<br />
Note that the universe manager, MTREKD, stops running about 30 seconds<br />
after everyone quits playing.<br />
<br />
<br />
Now mop up the blood, sweat, and tears; logout; and go home.<br />
<br />
Some useful additions to the original manual:<br />
<br />
5.0 ADDITIONS TO THE MANUAL<br />
<br />
<br />
5.1 ADDITIONS TO STARTING THE GAME<br />
<br />
There are two special values for the startup settings which make<br />
playing easier for the beginner:<br />
<br />
1. Setting star density to 0 results in no stars in your way at all.<br />
<br />
2. Setting black hole speed to 0 will create no black holes to eat up<br />
your vessel.<br />
<br />
<br />
5.2 THE UNIVERSE MAP<br />
<br />
At any time you can generate a map of the complete universe using<br />
RUN MAP. The result is put into the file UNIVERSE.MAP. You can either<br />
view it on the terminal with TYPE UNIVERSE.MAP or print it with PRINT<br />
UNIVERSE.MAP.<br />
<br />
The map shows everything in the current state of the universe. <br />
Furthermore you get the status quo of all 8 ships.<br />
<br />
A typical map looks like this:<br />
<br />
---------------------------------------------------------------*-----------------------*------------<br />
-..*..........*....R...............................*...............................................-<br />
-......*......................................................................*....................-<br />
-................................................................................B.................-<br />
-...............*...............R...............................................................*..-<br />
-...............................*..............B..*....................................6........*..-<br />
-..............*.......B...................*........................................*...........*..-<br />
-..................B...................................................................*...........-<br />
-........................+..................................................................B......-<br />
-.....................*..................*.........................................................-<br />
-......................................*...........................................................-<br />
-.........*............*....................B....................................**................-<br />
*.................................................*..........................*.....................-<br />
-.......*.............*............................................................................-<br />
-......*...........................................................................................-<br />
-...............................................................*..................................-<br />
-..............*...................................................................................-<br />
-.....*...............................*.....................................*......................-<br />
-...............*..................................................................................-<br />
-.................................................*................................................-<br />
-....................*......*...................................................................**.-<br />
-....................*.....*.........................................*.........*...................-<br />
*..........*..R................................*.......B...*...........................*...........-<br />
-......*.............................................................................**............-<br />
-........................................................*.....*...................................-<br />
-..................H.......................*..............*....................H...................-<br />
-........*...........*.......................*.................................................*...-<br />
-................*.............................................................*...................-<br />
-.............................................................B....................................-<br />
-..................................................................................................-<br />
-................................................H....................*.......*....................-<br />
-.................................................................*...................*............-<br />
-..................................*.............................R.*................*..............-<br />
-.................................................*.................*..*.*........*................-<br />
-.*...............................................................*................................-<br />
-.......................*................*.*..................................*....................-<br />
-...............................................*..................................................-<br />
-.................B...................**....................*.............................*.*......-<br />
-......*................................*............*..........................4..................-<br />
-.....................*............................................................................-<br />
-...................................*.....*.............**.........................................-<br />
-..................................................................................................-<br />
-............................................................................*.....................-<br />
-..............................................................*..*.......*.*......................-<br />
-..........*..................................................................................*....-<br />
-.*......*..................B......................................................................-<br />
-..........................................................................*.......................-<br />
-............................#..............*......................................................-<br />
-..................................................................................................-<br />
-....................................................*...........................................B.-<br />
-................*.....................................................................*...........-<br />
-.......................*.........................................................................*-<br />
-...*............................................*...................................*....B.B*.....-<br />
-...............*.................................................................................*B<br />
-....................................................*.............................................-<br />
-.......*....................................*.............................*.......................-<br />
-..................................................................................................-<br />
-......................................................*..................................*........-<br />
-..................................................................................................-<br />
-.....................................................................*............B...............-<br />
-........*.......................................................*.............*................B..-<br />
-...................*.........*..........................*.........................................-<br />
-.....................................+............................*.*.............................-<br />
-..........................................*..........*.........*..................................-<br />
-..................................................................................................-<br />
-*.........................................................*...................................*...-<br />
-.................................................................................B...............*-<br />
-.*................................................................*..................*............*<br />
-...................B...........................................................7..................-<br />
-................*........................*...........................*............................-<br />
-...........*.................*..................H.................................................-<br />
-....*...............**............................................................................-<br />
-..................................................................................................-<br />
-...........................................................*......................................*<br />
-...................+...*......R...................................................................-<br />
-..................H............................................*..............HR....3.............-<br />
-............................................*.......................B.............................-<br />
-...................................*..............................*..........*....*.....B.........-<br />
-...............................................*....................+...........................*.-<br />
-...*.................................................................*............................-<br />
*.....................................................*.................................*..........-<br />
-..................................................................................................-<br />
-.......*....................................+...............................................*.....-<br />
-...........................+...................B.......................................*..........-<br />
-........*.................................................B.......................................-<br />
-...........................................5...........................*..........................-<br />
-..*.............................................................................................*.-<br />
-................................+.......+............................*.............*..............-<br />
-......................*...................................*.......................................-<br />
-............................*.....*......................*..........*.............................-<br />
-......................................1.2.........................................................-<br />
-......................................8...........................................................-<br />
-.......*..........................................................................................-<br />
-*.....................................................................*...........................-<br />
-.....................................................................*..........*............*....-<br />
-...................................*........+.....................................................-<br />
-......*................................................................................*..........-<br />
-.............................................................*....................................-<br />
-..................................................................................................-<br />
--------------------------------------------------+------*----------------------*--------*-----*----<br />
<br />
<br />
SHIP: 1 SHIP: 2 SHIP: 3 SHIP: 4 SHIP: 5 SHIP: 6 SHIP: 7 SHIP: 8<br />
SCORE: 2150 SCORE: 0 SCORE: 0 SCORE: 0 SCORE: 0 SCORE: 0 SCORE: 0 SCORE: 1400<br />
X: 40.40 X: 42.50 X: 86.50 X: 81.50 X: 45.50 X: 88.50 X: 81.50 X: 40.59<br />
Y: 10.12 Y: 10.50 Y: 25.50 Y: 62.50 Y: 15.50 Y: 95.50 Y: 32.50 Y: 9.00<br />
WARP: 8.00 WARP: 0.00 WARP: 0.00 WARP: 0.00 WARP: 0.00 WARP: 0.00 WARP: 0.00 WARP: 8.00<br />
DIR: 2.49 DIR: 3.00 DIR: 3.00 DIR: 3.00 DIR: 3.00 DIR: 3.00 DIR: 3.00 DIR: 0.32<br />
ENERGY: 3677 ENERGY:10000 ENERGY:10000 ENERGY:10000 ENERGY:10000 ENERGY:10000 ENERGY:10000 ENERGY: 2332<br />
SHIELD:1200. SHIELD: 0. SHIELD: 0. SHIELD: 0. SHIELD: 0. SHIELD: 0. SHIELD: 0. SHIELD:1200.<br />
TORPS: 3 TORPS: 10 TORPS: 10 TORPS: 10 TORPS: 10 TORPS: 10 TORPS: 10 TORPS: 0<br />
SEEKERS: 3 SEEKERS: 4 SEEKERS: 4 SEEKERS: 4 SEEKERS: 4 SEEKERS: 4 SEEKERS: 4 SEEKERS: 0<br />
HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3<br />
<br />
== External links ==<br />
<br />
* [https://www.digiater.nl/openvms/decus/vax82a/mtrek/ MTREK on the VAX SYSTEMS SIG SPRING 82 SYMPOSIUM TAPE]<br />
<br />
[[Category: Games]]<br />
[[Category: SIMH Tutorials]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=MULTI-TREK&diff=33152
MULTI-TREK
2024-02-01T17:14:43Z
<p>Vaxorcist: /* How to run MTREK on a VAX */</p>
<hr />
<div>While searching the Internet for information on the [[VAX]] [[TREK7]] game, I stumbled over another Star-Trek game called '''MULTI-TREK''' or just '''MTREK''' in the [[DECUS]] [https://www.digiater.nl/openvms/decus/ collection of VMS software tapes].<br />
<br />
I used the [[ods2]] tool from the [[SIMH]] [https://github.com/open-simh/simtools tools collection] to transfer the MTREK files to a VMS disk image file.<br />
<br />
I decided to use the [[FORTRAN]] source files instead of the [[RATFIV]] ones, because I could not get the RATFIV [[compiler]] going (I will try that again later).<br />
<br />
The date of the RATFIV source files (28-APR-1982) gave me a clue to try [[VMS]] V3 for MTREK, which proved to be successful.<br />
<br />
Using the @BUILD command gave some error messages, which were overcome in some steps by trial and error.<br />
<br />
The nasty surprise showed up when I started the MTREK program that had compiled and linked so easy.<br />
Directly after entering the chosen vessel number, the program "froze" and did not accept anymore input except CTRL-C or CTRL-Y, both of which aborted the game.<br />
After studying the sources, and some simple debugging attempts, I decided to employ the VAX [[debugger]] to obtain more information as to what was going on.<br />
<br />
A helpful chap from the U.K., Dave Roberts, replied to my call for help on the [https://forum.vcfed.org/index.php?forums/dec/ VCFed DEC Forum]; and together we attempted to debug and correct the errant behaviour.<br />
<br />
The first step to success was the detection of the endless loop that caused the "freezing" of the program.<br />
Then Dave found the suspicious subroutine "INCHAR", and after analyzing the QIO calls and their return codes with two VMS manuals I provided, he finally found out that a necessary initialisation routine was commented out for whatever reason. After removing the "C" (for "Comment") in the respective source line, followed by re-compiling and re-linking, MTREK ran as expected. Little cause for a great event ...<br />
<br />
Hurray, game time!<br />
<br />
This is an example of a player's view at the universe:<br />
<br />
Energy : 9848.5 * * Scores<br />
Shields : 0.0<br />
R 1 -1000. *<br />
Warp : 3.00 * 2 0.<br />
Course : 3.00 3 0.<br />
4 0.<br />
X co-ord : 38.8 * 5 0.<br />
Y co-ord : 89.5 1 6 0.<br />
# 7 0.<br />
Torps : 10 8 0.<br />
Seekers : 4<br />
Hyper : 3<br />
Scan: 2<br />
Def Ship : 2 * Dir : 1.75<br />
Def Direc: 1.75 Dist: 51.08<br />
* Sect: 7, 2<br />
. .<br />
<br />
== Introduction to MTREK ==<br />
<br />
File "aareadme.doc" from the MTREK distro:<br />
<br />
MULTI-TREK is a game similar to traditional Star-Trek games<br />
except that it involves several players (currently up to 8), who<br />
play against each other in real time rather than against<br />
imaginary Klingons, Romulans or whatever. The MULTI-TREK<br />
universe consists of a 100 by 100 matrix, of which an approximate<br />
20 by 20 matrix of each player's immediate area is displayed and<br />
continuously updated at their terminal. MULTI-TREK was<br />
originally submitted to the New Orleans RSX/IAS sig tape, then to<br />
the 1979 San Diego RSX/IAS sig tape with the addition of robot<br />
ships. Since then it has been recoded in RATFIV and has<br />
significant enhancements and improvements, most notably the<br />
addition of energy nets, an improved screen display, much better<br />
input-output (any terminal with clear screen and cursor<br />
positioning may be used at speeds from 1200 baud on up), use of<br />
default ship and direction with most commands ("L" sets the<br />
default direction), more competitive scoring, smarter robot<br />
ships,reverse polish command sequences (fewer keystrokes), and<br />
fewer bugs. This version is being submitted to the Spring 1982<br />
VAX tapes and features the rpn command sequences and fades that<br />
don't exactly show up on radar locates. Complete instructions<br />
for starting and playing MULTI-TREK are in the file MTREK.DOC.<br />
<br />
The game consists of a driver task (MTREKD), a player task<br />
(MTREK) for each terminal, and a shared global common area for<br />
inter-task communication. This version runs on VAX VMS, however,<br />
it should run under any system with shared global areas and<br />
rudimentary task switching or time-sharing. Real-time systems<br />
without time-sharing may have to play with priorities to insure<br />
that the driver task gets sufficient CPU time and that all<br />
players get an equal amount of time.<br />
<br />
MULTI-TREK was written with a structured Fortran called<br />
RATFIV. The IAS version contains all of the Fortran produced by<br />
RATFIV, as well as the RATFIV source (file type .RAT). The VAX<br />
VMS version does not include the .FOR files, however the RATFIV<br />
compiler is included on both distribution tapes.<br />
<br />
MTREK will work properly with any terminal with clear screen<br />
and cursor positioning. The source code is set up to drive<br />
ADM3-A's or VT100's and VT52's. If you are using different<br />
terminals, you should modify the file "TERMINAL.RAT" (you could<br />
modify "TERMINAL.FTN") to drive your terminal. Modification<br />
should be straight-forward as the code is commented on where to<br />
change it.<br />
<br />
To build MTREK, do<br />
<br />
@BUILD<br />
<br />
The VAX VMS version places the common area, LEDFOR, on<br />
SYS$SHARE and installs it /WRITE/SHARE. It also puts MTREK.EXE,<br />
the player task, and MTREKD.EXE, the universe manager task, on<br />
SYS$SYSTEM, and installs MTREK.EXE with DETACH and ACNT<br />
privileges, so that anyone can start up MTREKD as a detached<br />
process (only one copy of MTREKD runs at a time, however).<br />
<br />
After building MTREK, first run MTREKINI. Then, on VAX VMS<br />
systems, say MCR MTREK and you are off and running. On IAS<br />
systems, the universe manager MTREKD must be started by hand<br />
before MTREK is run. You can run MTREKD on a dedicated terminal<br />
or install it and run it /REAL.<br />
<br />
== Status Quo ==<br />
<br />
== How to run MTREK on a real VAX or SIMH VAX ==<br />
<br />
Get the [https://drive.google.com/drive/folders/1LznfGLX4LDHMgJRgRLYSItrvrFNLwri9?usp=sharing MTREK kit] and follow the instructions included.<br />
<br />
== MTREK Manual ==<br />
<br />
File "mtrek.doc" from the MTREK distro:<br />
<br />
1.0 INTRODUCTION<br />
<br />
This game was written as a tool to test the use of shared global<br />
areas with time-shared programs. The game consists of five parts, the<br />
shared global area, the driver task (MTREKD) which controls the<br />
universe, the MTREK task which interfaces with the players, the<br />
initialization program (MTREKINI), and the robot ship program (ROBOT).<br />
<br />
The source code for the game is intended to be public so that<br />
enhancements can be added by any interested party. Those making<br />
additions should add their names to those listed as contributors at<br />
the start of the MTREKD program.<br />
<br />
NOTE<br />
<br />
MTREK was originally developed under IAS but is written<br />
almost entirely in RATFOR and should be readily convertible to<br />
RSX-11M or, for that matter, to any system that supports<br />
shared global areas and time-shared tasks or some equivalent.<br />
<br />
MTREK was originally written at Boeing Computer Services<br />
in Seattle, Washington by Don Ledford, John Lutch, and Ray<br />
French. The current game is an enhanced version developed at<br />
The Institute For Cancer Research in Philadelphia, Pa. by<br />
Bill Wood, Bill Cael, and Bob Stodola.<br />
<br />
<br />
Good luck, and don't get discouraged as the game requires a little<br />
practice!<br />
<br />
<br />
2.0 PLAYING MULTI-TREK<br />
<br />
The game is very similar to the traditional Star-Trek game with<br />
the following exceptions. First, the game involves several players<br />
(1-8), each of whom has his own terminal and starship. Second, the<br />
game runs in real time as far as the players are concerned. For<br />
example, if you are going warp 8 you will continue to move regardless<br />
of your activity at the terminal (unless you are destroyed, hit<br />
something, run out of energy, or change your warp speed). Each<br />
player's status and position as well as the scores of all players is<br />
displayed and continuously updated at each player's terminal. (The<br />
update rate is 2.5 times per second, but the source code is commented<br />
on where to change it should you wish to do so.) Third, at the present<br />
time there are no Klingons or Romulans to shoot down, instead you<br />
shoot (or at least attempt to shoot) the other players.<br />
<br />
The universe consists of a 100 by 100 matrix which wraps around<br />
itself. Therefore if you move off one end of the universe you appear<br />
on the other end. (This is true of phasers and torpedoes also.)<br />
<br />
The universe is made up of the following items:<br />
<br />
1. " " Empty space<br />
<br />
2. "-" Universe boundary<br />
<br />
3. "*" Star<br />
<br />
4. "B" Star-base (ram it to dock and thereby refuel)<br />
<br />
5. "H" Hyperspace point (described below)<br />
<br />
6. "R" Random hyperspace point (also described below)<br />
<br />
7. "+" Torpedo<br />
<br />
8. "^" Homing torpedo (seeker)<br />
<br />
9. "#" Black hole will pursue nearest player<br />
<br />
10. "@" Anti-matter pod<br />
<br />
11. "%" Energy net<br />
<br />
12. "1"-"8" Player's ships<br />
<br />
<br />
2.1 Hyperspace Ports<br />
<br />
When a hyperspace port is hit by a ship the ship is teleported to<br />
a new location in the universe. The "H" type of hyperspace port can<br />
be used to go to a set location whereas the "R" type of port produces<br />
a random jump. The "H" ports are located at fixed locations; these<br />
are as follows:<br />
<br />
^PORT ^NUMBER ^X ^COORD ^Y ^COORD<br />
----------- ------- -------<br />
<br />
1 20 75<br />
2 50 70<br />
3 80 75<br />
4 20 25<br />
5 50 30<br />
6 80 25<br />
<br />
^THE NETWORK OF PORTS LOOKS LIKE THIS:<br />
<br />
1 3<br />
2<br />
<br />
<br />
<br />
<br />
5<br />
4 6<br />
<br />
<br />
By using the "H" command a player can set the port number he<br />
wishes to appear beside the next time he goes into hyperspace through<br />
an "H" type port. For example, if a player used the "H" command to<br />
set his hyperspace setting to 4, the next time he ran into an "H"<br />
character he would appear near coordinates 20,25.<br />
<br />
A player's anti-matter pod can travel through hyper-space also;<br />
upon re-emergence in the universe, it blows up. Pods going through<br />
random hyperspace reappear randomly; those going through "H" type<br />
ports reappear at the pod owner's current hyperspace jump point.<br />
<br />
<br />
2.2 Scoring<br />
<br />
The current scores of all players are displayed on the screen. A<br />
'*' beside a score indicates an active player. The following actions<br />
result in score changes:<br />
<br />
1. Torpedo hit on enemy vessel: +500<br />
<br />
2. Homer hit on enemy vessel: +300<br />
<br />
3. Phaser hit on enemy vessel: +(between 70 and 200 depending on<br />
distance)<br />
<br />
4. Pod explosion: +(between 300 and 1500 depending<br />
on distance)<br />
<br />
5. Torpedo hit on base: -200<br />
<br />
6. Getting destroyed: -1000<br />
<br />
<br />
2.3 Energy Consumption<br />
<br />
1. Shooting phasers: -50<br />
<br />
2. Warp: -.5 * WARP SPEED per time interval<br />
<br />
3. Send message: -10<br />
<br />
4. Collide with star: -200<br />
<br />
5. Collide with ship: -100<br />
<br />
6. Cloaking: -25 per time interval (default)<br />
<br />
7. Energy net: -75 per net unit constructed (default)<br />
<br />
8. Tractor beam: -100 per time interval (default)<br />
<br />
Energy loss due to weapon hit is a function of shield strength<br />
and weapon energy.<br />
<br />
<br />
2.4 Calculations<br />
<br />
The following formula are used:<br />
<br />
1. Phaser hit energy:<br />
<br />
ENERGY=900./(4. + DISTANCE)<br />
<br />
2. Torpedo hit energy:<br />
<br />
ENERGY=500.<br />
<br />
3. Shield protection:<br />
<br />
SHIELD ABSORBTION FACTOR=SHIELD ENERGY/1000.<br />
(^WITH A MAXIMUM VALUE OF 1.)<br />
SHIELD DIRECTION FACTOR=<br />
(.5 + ABS(SHIP'S DIREC - WEAPON'S DIREC)/360)<br />
SHIELD FACTOR = SHIELD DIRECTION FACTOR *<br />
SHIELD ABSORBTION FACTOR<br />
<br />
SHIELD ENERGY =<br />
SHIELD ENERGY - SHIELD FACTOR * ENERGY OF HIT<br />
ENERGY OF SHIP = ENERGY OF SHIP -<br />
(1.2 - SHIELD FACTOR) * ENERGY OF HIT * 6<br />
<br />
4. Tractor beam pull:<br />
<br />
8./SQRT(MAX(1., DISTANCE BETWEEN SHIPS-6.))<br />
<br />
Anti-matter causes both damage to the scan, and results in an<br />
energy hit. Both of these effects are energy dependent.<br />
<br />
<br />
2.5 MTREK commands<br />
<br />
All commands consist of one character, and most of them can be<br />
preeceded by a numeric argument. This argument can be input with the<br />
command character, or can be a default ship or direction. Generally,<br />
typing a new ship number or direction changes the default ship or<br />
direction, however there are exceptions. In addition, the "L" (long<br />
range scan) command changes the default direction to the direction of<br />
the scanned ship, which is convenient for firing at the scanned ship.<br />
See below for other commands which change the defaults. To use a<br />
default value, simply type the command letter.<br />
<br />
1. Help<br />
"?" Prints a summary of all commands.<br />
<br />
2. Shields<br />
"S" Raise or lower shields. This may be preceeded by a<br />
real number (+ or -). Your default shield change value<br />
is reset every time you set positive shields, and this<br />
default value may be used by just typing the "S"<br />
command. 1000 units is the most that will do any good.<br />
But you may want a little reserve.<br />
<br />
3. Reset<br />
"R" Clears the screen and redraws the entire display.<br />
<br />
4. Torpedoes<br />
"T" Fire torpedoes. A direction may be specified. "T"<br />
fires in the default direction, a number fires in that<br />
direction and resets the default. Torpedoes move at<br />
warp 10, and destroy anti-matter pods.<br />
<br />
5. Phasers<br />
"P" Fire phasers. A direction may be specified. "P" fires<br />
in the default direction, A number fires in that<br />
direction and resets the default. Phasers are<br />
instantaneous, have a range of 10 squares, and shoot a<br />
band 3 squares wide. They will not destroy torpedoes<br />
(except homers).<br />
<br />
6. Locate<br />
"L" Long range scan for another player. The "L" command<br />
sets the default direction to that of the scanned ship.<br />
It may be precceded by a ship number as an argument.<br />
"L" locates a default ship. If a ship number is given,<br />
the default ship is reset to that ship.<br />
<br />
7. Message<br />
"M" Send a message to another player on subspace radio.<br />
"M" sends to the default ship, a ship number sends to<br />
that ship. A ship number of zero broadcasts the<br />
message to all ships. The default ship is not reset.<br />
<br />
8. Warp<br />
"W" Set warp speed 0-8.<br />
<br />
9. Course<br />
"C" Set course 0-12 (clock face). This does not affect<br />
your warp speed or default direction. However, the<br />
default direction may be used to set the course. All<br />
directions are to be specified in "clock face" numbers.<br />
For example:<br />
<br />
0. is up<br />
<br />
9. is left 3. is right<br />
<br />
6. is down<br />
<br />
7.5 is toward the lower left corner, etc.<br />
<br />
10. Quit<br />
"Q" Quit.<br />
<br />
11. Hyperspace<br />
"H" Set hyperspace jump point 1 through 6.<br />
<br />
12. Cloak on<br />
"F" Fade away. The cloaking device is a continuous energy<br />
drain when activated. A cloaked ship cannot move.<br />
Typeing "F" will toggle this mode.<br />
<br />
13. Cloak off<br />
"A" Appear.<br />
<br />
14. Energy net on/off<br />
"E" Start/stop energy net construction. Energy nets<br />
provide a "wall" which other ships will bounce off of,<br />
however your ship travels instantaneously through your<br />
energy nets. Torpedoes may be used to destroy nets.<br />
The black hole is blocked by them. Phasers do not<br />
penetrate nets.<br />
<br />
15. Seeking torpedo launch<br />
"K" If you specify a ship number to home in on the default<br />
will be changed. If none is specified then the default<br />
ship is located. Homing torpedoes can not be fired at<br />
faded ships. Homing torpedoes destroy anti-matter<br />
pods. Seeking torpedoes can be shot down with phasers<br />
(at least sometimes).<br />
<br />
16. Anti-matter launch<br />
"Z" If a direction is specified the default direction is<br />
reset. Pods move at warp 5. "Z" fires in the default<br />
direction, When an anti-matter pod hits a hyper-space<br />
port, it travels through it to your current hyperspace<br />
jump point and blows up. Pods also travel through<br />
random hyper-space ports to a random location and blow<br />
up.<br />
<br />
17. Anti-matter freeze<br />
"N" Stop movement of anti-matter device. (It will become a<br />
static mine.)<br />
<br />
18. Anti-matter detonate<br />
"X" Detonate anti matter pod. This explosion destroys an<br />
entire area, except for bases and hyperspace points.<br />
The pattern of the explosion is as below.<br />
<br />
X <br />
X X X <br />
X X X<br />
X X X X X X X <br />
X X X <br />
X X X<br />
X<br />
<br />
Ships within 4 of an exploding pod lose some energy and<br />
have their vision partially obscured. The black hole<br />
is randomly relocated when caught in a pod explosion.<br />
<br />
19. Tractor beams<br />
"B" Set tractor beam target ship (1-8). 0 to stop tractor<br />
beam. Tractor beams are used to pull your opponent's<br />
ship towards you. The closer the ships are the<br />
stronger the pull of the tractor beam. The default<br />
ship is reset.<br />
<br />
20. Verbose/Non-verbose mode<br />
"V" Flip on/off verbose mode. In non-verbose mode, only<br />
the first letter of each word is printed. For example,<br />
<br />
+ TORPEDO HIT ALIEN!<br />
<br />
becomes<br />
<br />
+THA<br />
<br />
This is sometimes useful in the heat of battle on a<br />
slow (1200 baud) terminal.<br />
<br />
21. Flush type-ahead buffer<br />
" " The game keeps an internal typeahead buffer of up to 20<br />
characters. Typeing " " will flush this buffer.<br />
<br />
<br />
3.0 STARTING THE GAME<br />
<br />
If you are starting a new game, first initialize the universe<br />
using MTREKINI:<br />
<br />
$ RUN MTREKINI<br />
<br />
It will ask a series of set up questions (defaults are invoked by<br />
<CR>):<br />
<br />
1. Any random integer between -32k and +32k (default = 0).<br />
<br />
2. A star density between 2 and 3 is good (default = 2.0).<br />
<br />
3. About 20 to 25 star-bases is ok (default = 20).<br />
<br />
4. Usually 5-10 random jump points (default = 6).<br />
<br />
5. A cloaking energy drain of 20 to 40 (default = 25).<br />
<br />
6. Net construction energy drain of 0 to 2000 (default = 75).<br />
<br />
7. Tractor beam energy drain of 0 to 2000 (default = 100).<br />
<br />
8. Black hole speed of 2. to 5. (default = 4.5).<br />
<br />
<br />
3.1 Player Initiation<br />
<br />
Several crt terminals are required to play the game. The driver<br />
program, MTREKD, may be started automatically on your system. (It is<br />
at ICR.) If not, it must be started up prior to playing. Then each<br />
player should issue the following command at his terminal:<br />
<br />
$ RUN MTREK<br />
<br />
A list of unoccupied ships will be displayed, so choose an unoccupied<br />
ship and you are ready to play. It is possible for two or more<br />
players to control the same ship by selecting an occupied ship, e.g.,<br />
one player can control navigation and the other weapons. Players may<br />
enter and leave the game at any time.<br />
<br />
<br />
3.2 Robot Ships<br />
<br />
In addition to playing against human opponents you can turn the<br />
unused ships over to computer control. This is done by starting the<br />
ROBOT program. You can choose the ships to be controlled and the<br />
capability of the ships' robot skippers.<br />
<br />
Each running ROBOT program can control several ships which will<br />
act as a team. If more than one ROBOT program is started then their<br />
ships will fight with each other. Robot ships are started with the<br />
command:<br />
<br />
$ RUN ROBOT<br />
<br />
A list of unoccupied ships will be displayed. Enter the number(s) of<br />
the ship(s) to be under robot control. When the robot "team" has been<br />
selected, enter <CR> and the ROBOT program will ask several questions<br />
to set up the ability of the robot skippers (as with MTREKINI,<br />
defaults are invoked by <CR>):<br />
<br />
1. Maximum speed of robot ships (default = warp 8).<br />
<br />
2. Robot reaction time (default = 1.5).<br />
<br />
3. Amount of phaser fire (default = 5).<br />
<br />
4. Degree of inaccuracy (default = 0 degrees).<br />
<br />
<br />
4.0 TERMINATING THE GAME<br />
<br />
It is important that the last MTREK players clean up the system<br />
before they leave. This is done by issuing the following set of<br />
commands:<br />
<br />
1. Terminate each MTREK program by entering the "Q" command.<br />
<br />
2. If you are running any ROBOT programs abort each one as follows:<br />
<br />
<CNTRL> C<br />
<br />
Note that the universe manager, MTREKD, stops running about 30 seconds<br />
after everyone quits playing.<br />
<br />
<br />
Now mop up the blood, sweat, and tears; logout; and go home.<br />
<br />
Some useful additions to the original manual:<br />
<br />
5.0 ADDITIONS TO THE MANUAL<br />
<br />
<br />
5.1 ADDITIONS TO STARTING THE GAME<br />
<br />
There are two special values for the startup settings which make<br />
playing easier for the beginner:<br />
<br />
1. Setting star density to 0 results in no stars in your way at all.<br />
<br />
2. Setting black hole speed to 0 will create no black holes to eat up<br />
your vessel.<br />
<br />
<br />
5.2 THE UNIVERSE MAP<br />
<br />
At any time you can generate a map of the complete universe using<br />
RUN MAP. The result is put into the file UNIVERSE.MAP. You can either<br />
view it on the terminal with TYPE UNIVERSE.MAP or print it with PRINT<br />
UNIVERSE.MAP.<br />
<br />
The map shows everything in the current state of the universe. <br />
Furthermore you get the status quo of all 8 ships.<br />
<br />
A typical map looks like this:<br />
<br />
---------------------------------------------------------------*-----------------------*------------<br />
-..*..........*....R...............................*...............................................-<br />
-......*......................................................................*....................-<br />
-................................................................................B.................-<br />
-...............*...............R...............................................................*..-<br />
-...............................*..............B..*....................................6........*..-<br />
-..............*.......B...................*........................................*...........*..-<br />
-..................B...................................................................*...........-<br />
-........................+..................................................................B......-<br />
-.....................*..................*.........................................................-<br />
-......................................*...........................................................-<br />
-.........*............*....................B....................................**................-<br />
*.................................................*..........................*.....................-<br />
-.......*.............*............................................................................-<br />
-......*...........................................................................................-<br />
-...............................................................*..................................-<br />
-..............*...................................................................................-<br />
-.....*...............................*.....................................*......................-<br />
-...............*..................................................................................-<br />
-.................................................*................................................-<br />
-....................*......*...................................................................**.-<br />
-....................*.....*.........................................*.........*...................-<br />
*..........*..R................................*.......B...*...........................*...........-<br />
-......*.............................................................................**............-<br />
-........................................................*.....*...................................-<br />
-..................H.......................*..............*....................H...................-<br />
-........*...........*.......................*.................................................*...-<br />
-................*.............................................................*...................-<br />
-.............................................................B....................................-<br />
-..................................................................................................-<br />
-................................................H....................*.......*....................-<br />
-.................................................................*...................*............-<br />
-..................................*.............................R.*................*..............-<br />
-.................................................*.................*..*.*........*................-<br />
-.*...............................................................*................................-<br />
-.......................*................*.*..................................*....................-<br />
-...............................................*..................................................-<br />
-.................B...................**....................*.............................*.*......-<br />
-......*................................*............*..........................4..................-<br />
-.....................*............................................................................-<br />
-...................................*.....*.............**.........................................-<br />
-..................................................................................................-<br />
-............................................................................*.....................-<br />
-..............................................................*..*.......*.*......................-<br />
-..........*..................................................................................*....-<br />
-.*......*..................B......................................................................-<br />
-..........................................................................*.......................-<br />
-............................#..............*......................................................-<br />
-..................................................................................................-<br />
-....................................................*...........................................B.-<br />
-................*.....................................................................*...........-<br />
-.......................*.........................................................................*-<br />
-...*............................................*...................................*....B.B*.....-<br />
-...............*.................................................................................*B<br />
-....................................................*.............................................-<br />
-.......*....................................*.............................*.......................-<br />
-..................................................................................................-<br />
-......................................................*..................................*........-<br />
-..................................................................................................-<br />
-.....................................................................*............B...............-<br />
-........*.......................................................*.............*................B..-<br />
-...................*.........*..........................*.........................................-<br />
-.....................................+............................*.*.............................-<br />
-..........................................*..........*.........*..................................-<br />
-..................................................................................................-<br />
-*.........................................................*...................................*...-<br />
-.................................................................................B...............*-<br />
-.*................................................................*..................*............*<br />
-...................B...........................................................7..................-<br />
-................*........................*...........................*............................-<br />
-...........*.................*..................H.................................................-<br />
-....*...............**............................................................................-<br />
-..................................................................................................-<br />
-...........................................................*......................................*<br />
-...................+...*......R...................................................................-<br />
-..................H............................................*..............HR....3.............-<br />
-............................................*.......................B.............................-<br />
-...................................*..............................*..........*....*.....B.........-<br />
-...............................................*....................+...........................*.-<br />
-...*.................................................................*............................-<br />
*.....................................................*.................................*..........-<br />
-..................................................................................................-<br />
-.......*....................................+...............................................*.....-<br />
-...........................+...................B.......................................*..........-<br />
-........*.................................................B.......................................-<br />
-...........................................5...........................*..........................-<br />
-..*.............................................................................................*.-<br />
-................................+.......+............................*.............*..............-<br />
-......................*...................................*.......................................-<br />
-............................*.....*......................*..........*.............................-<br />
-......................................1.2.........................................................-<br />
-......................................8...........................................................-<br />
-.......*..........................................................................................-<br />
-*.....................................................................*...........................-<br />
-.....................................................................*..........*............*....-<br />
-...................................*........+.....................................................-<br />
-......*................................................................................*..........-<br />
-.............................................................*....................................-<br />
-..................................................................................................-<br />
--------------------------------------------------+------*----------------------*--------*-----*----<br />
<br />
<br />
SHIP: 1 SHIP: 2 SHIP: 3 SHIP: 4 SHIP: 5 SHIP: 6 SHIP: 7 SHIP: 8<br />
SCORE: 2150 SCORE: 0 SCORE: 0 SCORE: 0 SCORE: 0 SCORE: 0 SCORE: 0 SCORE: 1400<br />
X: 40.40 X: 42.50 X: 86.50 X: 81.50 X: 45.50 X: 88.50 X: 81.50 X: 40.59<br />
Y: 10.12 Y: 10.50 Y: 25.50 Y: 62.50 Y: 15.50 Y: 95.50 Y: 32.50 Y: 9.00<br />
WARP: 8.00 WARP: 0.00 WARP: 0.00 WARP: 0.00 WARP: 0.00 WARP: 0.00 WARP: 0.00 WARP: 8.00<br />
DIR: 2.49 DIR: 3.00 DIR: 3.00 DIR: 3.00 DIR: 3.00 DIR: 3.00 DIR: 3.00 DIR: 0.32<br />
ENERGY: 3677 ENERGY:10000 ENERGY:10000 ENERGY:10000 ENERGY:10000 ENERGY:10000 ENERGY:10000 ENERGY: 2332<br />
SHIELD:1200. SHIELD: 0. SHIELD: 0. SHIELD: 0. SHIELD: 0. SHIELD: 0. SHIELD: 0. SHIELD:1200.<br />
TORPS: 3 TORPS: 10 TORPS: 10 TORPS: 10 TORPS: 10 TORPS: 10 TORPS: 10 TORPS: 0<br />
SEEKERS: 3 SEEKERS: 4 SEEKERS: 4 SEEKERS: 4 SEEKERS: 4 SEEKERS: 4 SEEKERS: 4 SEEKERS: 0<br />
HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3 HYPER: 3<br />
<br />
== External links ==<br />
<br />
* [https://www.digiater.nl/openvms/decus/vax82a/mtrek/ MTREK on the VAX SYSTEMS SIG SPRING 82 SYMPOSIUM TAPE]<br />
<br />
[[Category: Games]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=Installing,_Configuring,_and_Testing_A_VMS_V4.7_Local_Area_VAXcluster_on_SIMH&diff=33131
Installing, Configuring, and Testing A VMS V4.7 Local Area VAXcluster on SIMH
2024-01-30T16:09:11Z
<p>Vaxorcist: /* Install DECnet Routing Key */ Fixed typo</p>
<hr />
<div>The aim of this tutorial is to show how to install a [[VMS]] V4.7 [[Local Area VAXcluster]] (short: LAVC) on the [[SIMH]] [[MicroVAX II]] [[simulator]].<br />
<br />
== Local Area VAXclusters ==<br />
<br />
=== Today's Advantages of Local Area VAXclusters ===<br />
<br />
Two common problems:<br />
* You own a [[MicroVAX]] or [[VAXstation]] without a working disk<br />
* You have no load device (e.g. tape or CDROM drive) to install software on your MicroVAX or VAXstation<br />
<br />
A Local Area VAXcluster built with a SIMH simulator is the perfect solution for this problems:<br />
* You can run your MicroVAX or VAXstation diskless<br />
* You can install software on your MicroVAX or VAXstation disk<br />
<br />
And if you use a [[Raspberry Pi]] instead of a normal PC for your SIMH host, you will save a lot of electric energy!<br />
<br />
It doesn't matter whether you boot real MicroVAXen or VAXstations or SIMH simulated ones from your VAXcluster; there is no difference except for speed (the SIMH VAXen are faster).<br />
<br />
=== Local Area VAXcluster Vocabulary ===<br />
<br />
* '''Boot Node''' = LAVC Server<br />
* '''Satellite Node''' = LAVC Client<br />
<br />
=== Introduction to Local Area VAXclusters ===<br />
<br />
A Local Area VAXcluster configuration consists of one or two [[boot node]]s and up to 26 [[satellite node]]s.<br />
<br />
A boot node is both a management center for the [[cluster]] and a major resource provider. <br />
Its system disk contains the cluster common files for startup, authorization, and queue setup, as well as the directory roots from which the satellite nodes are booted.<br />
<br />
A boot node makes available to the cluster such resources as user and application data disks, printers, and distributed batch processing facilities.<br />
<br />
In a Local Area VAXcluster configuration, a boot node may be any VAX system except [[VAX-11/725]] or [[VAX-11/730]], or it may be one of the following [[MicroVAX II]] or [[VAXstation II]] systems:<br />
* MicroVAX II with an [[RA series]] system disk.<br />
* MicroVAX II with an [[RD54]] system disk, or VAXstation II with an RD54 or any larger system disk. Note that these boot nodes support a maximum of three satellites. In addition, it is recommended that the satellites use local RD series disks for [[paging]] and [[swapping]].<br />
<br />
The satellite nodes are booted remotely from a boot node's system disk.<br />
<br />
Generally, these nodes are consumers of cluster resources, though they may also sometimes provide disk serving and batch processing resources.<br />
<br />
If satellite nodes are equipped with RD series disks, they may, for enhanced performance, use such local disks for paging and swapping.<br />
<br />
Satellite nodes may be any of the following:<br />
* MicroVAX II<br />
* [[MicroVAX 2000]]<br />
* VAXstation II<br />
* [[VAXstation 2000]]<br />
* [[VAXstation II/GPX]]<br />
* [[VAXstation II/RC]]<br />
<br />
'''Caution'''<br />
<br />
All MicroVAX II and VAXstation II machines in a Local Area VAXcluster configuration must use Revision E (or later) [[QBUS]] Network Adapter ([[DEQNA]]) devices and must have at least 3MB memory. Diskless machines require at least 4MB memory.<br />
<br />
== Preparations ==<br />
<br />
=== Suitable SIMH VAX simulators ===<br />
<br />
As boot node I chose the [[SIMH]] '''microvax2''' simulator because this was the cheapest way to build a Local Area VAXcluster from new in 1987.<br />
<br />
If you already had a "big" VAX back then with enough disk space available you could use that one, too, of course.<br />
<br />
I decided to use VMS V4.7 as there is no hassle with "License PAKs", but this restricts the choice of VAXen for boot and satellite nodes (see above).<br />
<br />
There will probably be a tutorial for VMS V5.5-2H2 and/or VMS V6.2 Local Area VAXclusters in the near future, too.<br />
<br />
=== VMS Versions needed ===<br />
<br />
To install VMS V4.7 (which is an update version only) you have to start with VMS V4.6 which is a full version.<br />
<br />
Get all the software needed (and a manual) [https://drive.google.com/drive/folders/1EtOslkPzuj4W4iw8MBPl886diDcAoKJp?usp=sharing here].<br />
<br />
=== microvax2.ini for the Boot Node (a Typical Large MicroVAX II System) ===<br />
<br />
; ================================================<br />
; microvax2.ini<br />
; ================================================<br />
;<br />
; Large MicroVAX II system made of:<br />
; - 16 MB memory<br />
; - 1 DZV11 terminal multiplexer with 4 lines<br />
; - 1 RQDX3 disk/floppy controller<br />
; - 1 RA82 disk drive<br />
; - 1 RX50 dual floppy disk drive<br />
; - 1 TKQ50 tape cassette drive controller<br />
; - 1 TK50 tape cassette drive<br />
; - 1 DELQA Ethernet adapter<br />
<br />
SET QUIET<br />
<br />
SET CPU 16M<br />
SET CPU IDLE=VMS<br />
SET CPU CONHALT<br />
SET CPU AUTOBOOT<br />
<br />
ATT NVR NVR-MVII.BIN<br />
<br />
SET CONSOLE LOG=VMS_V4.7_LAVC.LOG<br />
<br />
SET RQ ENA<br />
SET RQ0 RA82<br />
ATT RQ0 -F VHD VMS047_VHD.R82<br />
<br />
SET RQ1 RX50<br />
SET RQ2 RX50<br />
<br />
SET RQ3 DIS<br />
<br />
SET DZ LINES=4<br />
;ATT DZ 6666<br />
<br />
SET TQ ENA<br />
ATT TQ0 staba046.tap<br />
<br />
SET TQ1 DIS<br />
SET TQ2 DIS<br />
SET TQ3 DIS<br />
<br />
SET LPT DIS<br />
SET RL DIS<br />
SET TS DIS<br />
<br />
SET XQ ENA<br />
SET XQ TYPE=DELQA<br />
;SET XQ MAC=08-00-2B-0B-18-1A<br />
;ATT XQ eth0<br />
BOOT<br />
<br />
== Installation ==<br />
<br />
=== Start the SIMH MicroVAX II Simulator ===<br />
<br />
Windows:<br />
run microvax2.exe<br />
<br />
Linux:<br />
./microvax2<br />
<br />
Be aware that Linux is case sensitive!<br />
<br />
=== Boot VMS V4.6 Standalone Backup ===<br />
<br />
sim> '''BOOT'''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
KA630-A.V1.3<br />
<br />
<br />
Performing normal system tests.<br />
<br />
<br />
5..4..3..<br />
<br />
Tests completed.<br />
<br />
<br />
<br />
<br />
<br />
>>> '''B MUA0'''<br />
<br />
2..1..0..<br />
<br />
<br />
<br />
<br />
MicroVMS Version V4.6 6-Jul-1987 17:00<br />
<br />
<br />
<br />
PLEASE ENTER DATE AND TIME (DD-MMM-YYYY HH:MM) 21-JUL-2022 14:37<br />
<br />
%BACKUP-I-IDENT, Stand-alone BACKUP V4.6; the date is 21-JUL-2022 14:37:02.63<br />
$ <br />
<br />
=== Restore VMS V4.6 REQUIRED Saveset ===<br />
<br />
$ ['''STRG + e''']<br />
<br />
Simulation stopped, PC: 80008B1F (BRB 80008B1F)<br />
sim> '''ATT TQ0 BB-BT05D-BE_VMS4.6_87.tap'''<br />
sim> '''C'''<br />
<br />
$ <br />
$ '''BACKUP/LOG/VERIFY MUA0:REQUIRED/SAVE DUA0:'''<br />
<br />
%BACKUP-S-CREATED, created DUA0:[000000]000000.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[000000]BACKUP.SYS;1<br />
%BACKUP-S-CREATED, created DUA0:[000000]CONTIN.SYS;1<br />
%BACKUP-S-CREATED, created DUA0:[000000]CORIMG.SYS;1<br />
%BACKUP-S-CREATED, created DUA0:[000000]SYS0.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]MOM$SYSTEM.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSCBI.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSERR.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSERR]ERRSNAP.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSEXE.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]BACKUP.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]BADBLOCK.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CLUSTRLOA.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CNDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CONFIGURE.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CONINTERR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]COPY.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CRDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CREATE.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CSP.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CVDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]CWDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DBDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DCL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DDDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DELETE.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DIRECTORY.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DISMOUNT.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DLDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DMDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DQDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DRDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DUDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DVDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DXDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DYDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]DZDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ERRFMT.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ERRSNAP.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ESDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]ETDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]F11BXQP.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]FILESERV.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]FPEMUL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]INSTALL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]JOBCTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LADRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LCDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LIDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LOGINOUT.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]LPDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MASK_IMAGE.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MBXDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MP.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MSCP.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]MTAAACP.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]NODRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]NOTICE.TXT;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]OPCCRASH.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]OPCOM.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PADRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PAGEFILE.SYS;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PBDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PDDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]PUDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RENAME.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]REPLY.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]REQUEST.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RMS.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RMS.STB;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RUNDET.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]RXDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SCSLOA.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SET.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SETP0.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SHOW.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SHUTDOWN.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SMGMAPTRM.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]STACONFIG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]STARTUP.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]STARTUP.INS;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SWAPFILE.SYS;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYS.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSBOOT.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSGEN.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSINIT.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA410.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA41A.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA41D.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA41W.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA650.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA65D.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA65W.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA730.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA750.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA780.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA790.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA8NN.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOA8SS.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAUV1.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAUV2.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAWS1.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAWS2.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSLOAWSD.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSUAF.DAT;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]SYSUAF.RL2;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TERMTABLE.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TFDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TMDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TPU.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TSDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TTDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TUDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TVDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]TYPE.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VAXEMUL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VAXVMSSYS.PAR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VMB.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VMOUNT.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]VMSHELP.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XADRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XDDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XEDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XFDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XGDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XMDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XQDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]XWDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]YCDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]YEDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]YFDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSEXE]YIDRIVER.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSHLP.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSHLP]EXAMPLES.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSLIB.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]ADARTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]BASRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]BASRTL2.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]CDDSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]COBRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]CRFSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]DCLTABLES.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]DCXSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]DISMNTSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]DTKSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]EDTSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]ENCRYPSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]FORRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]IMGDMP.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]LBRSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]LIBRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]LIBRTL2.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]MOUNTSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]MTHRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]PASRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]PLIRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]RPGRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SCNRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SCRSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SECURESHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SMGSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]SUMSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]TPU$CCTSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]TPUSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]TRACE.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]UISSHR.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]UVMTHRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]VAXCRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]VAXCRTLG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSLIB]VMSRTL.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSMAINT.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSMGR.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SECAUDIT.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SYCONFIG.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SYENVIRON.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SYSHUTDWN.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]SYSTARTUP.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]VMSIMAGES.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMGR]VMSIMAGES.DAT;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSMSG.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]ADAMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]CLIUTLMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]DBGTBKMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]FILMNTMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]NETWRKMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]PASMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]PLIMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]PRGDEVMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]RPGMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SCNMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SHRIMGMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SYSMGTMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]SYSMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]TPUMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSMSG]VAXCMSG.EXE;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSTEST.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0]SYSUPD.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]BLISSREQ.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]CVTLICENSE.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]DECNET.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]DEVELOP.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]EXAMPLES.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]FILETOOLS.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]HELP.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]LIBRARY.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]MANAGER.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]MASK_IMAGE.CLD;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]MISCTOOLS.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]QUEUES.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]REQUIRED.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]SETDEFBOO.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]TEXTTOOLS.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]UETP.TLR;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSINSTAL.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSINSTAL.FDL;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSTAILOR.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[SYS0.SYSUPD]VMSUPDATE.COM;1<br />
%BACKUP-S-CREATED, created DUA0:[000000]SYSEXE.DIR;1<br />
%BACKUP-S-CREATED, created DUA0:[000000]VOLSET.SYS;1<br />
%BACKUP-I-STARTVERIFY, starting verification pass<br />
%BACKUP-S-COMPARED, compared DUA0:[000000]000000.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[000000]BACKUP.SYS;1<br />
%BACKUP-S-COMPARED, compared DUA0:[000000]CONTIN.SYS;1<br />
%BACKUP-S-COMPARED, compared DUA0:[000000]CORIMG.SYS;1<br />
%BACKUP-S-COMPARED, compared DUA0:[000000]SYS0.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]MOM$SYSTEM.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSCBI.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSERR.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSERR]ERRSNAP.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSEXE.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]BACKUP.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]BADBLOCK.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CLUSTRLOA.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CNDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CONFIGURE.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CONINTERR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]COPY.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CRDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CREATE.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CSP.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CVDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]CWDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DBDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DCL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DDDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DELETE.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DIRECTORY.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DISMOUNT.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DLDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DMDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DQDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DRDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DUDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DVDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DXDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DYDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]DZDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]ERRFMT.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]ERRSNAP.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]ESDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]ETDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]F11BXQP.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]FILESERV.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]FPEMUL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]INSTALL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]JOBCTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]LADRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]LCDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]LIDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]LOGINOUT.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]LPDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]MASK_IMAGE.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]MBXDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]MP.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]MSCP.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]MTAAACP.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]NODRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]NOTICE.TXT;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]OPCCRASH.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]OPCOM.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]PADRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]PAGEFILE.SYS;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]PBDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]PDDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]PUDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RENAME.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]REPLY.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]REQUEST.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RMS.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RMS.STB;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RUNDET.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]RXDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SCSLOA.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SET.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SETP0.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SHOW.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SHUTDOWN.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SMGMAPTRM.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]STACONFIG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]STARTUP.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]STARTUP.INS;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SWAPFILE.SYS;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYS.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSBOOT.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSGEN.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSINIT.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA410.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA41A.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA41D.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA41W.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA650.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA65D.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA65W.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA730.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA750.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA780.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA790.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA8NN.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOA8SS.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOAUV1.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOAUV2.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOAWS1.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOAWS2.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSLOAWSD.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSUAF.DAT;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]SYSUAF.RL2;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TERMTABLE.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TFDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TMDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TPU.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TSDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TTDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TUDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TVDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]TYPE.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VAXEMUL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VAXVMSSYS.PAR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VMB.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VMOUNT.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]VMSHELP.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]XADRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]XDDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]XEDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]XFDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]XGDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]XMDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]XQDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]XWDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]YCDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]YEDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]YFDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSEXE]YIDRIVER.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSHLP.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSHLP]EXAMPLES.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSLIB.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]ADARTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]BASRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]BASRTL2.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]CDDSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]COBRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]CRFSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]DCLTABLES.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]DCXSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]DISMNTSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]DTKSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]EDTSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]ENCRYPSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]FORRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]IMGDMP.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]LBRSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]LIBRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]LIBRTL2.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]MOUNTSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]MTHRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]PASRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]PLIRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]RPGRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SCNRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SCRSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SECURESHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SMGSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]SUMSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]TPU$CCTSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]TPUSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]TRACE.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]UISSHR.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]UVMTHRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]VAXCRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]VAXCRTLG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSLIB]VMSRTL.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSMAINT.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSMGR.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SECAUDIT.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SYCONFIG.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SYENVIRON.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SYSHUTDWN.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]SYSTARTUP.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]VMSIMAGES.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMGR]VMSIMAGES.DAT;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSMSG.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]ADAMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]CLIUTLMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]DBGTBKMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]FILMNTMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]NETWRKMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]PASMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]PLIMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]PRGDEVMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]RPGMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]SCNMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]SHRIMGMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]SYSMGTMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]SYSMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]TPUMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSMSG]VAXCMSG.EXE;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSTEST.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0]SYSUPD.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]BLISSREQ.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]CVTLICENSE.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]DECNET.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]DEVELOP.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]EXAMPLES.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]FILETOOLS.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]HELP.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]LIBRARY.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]MANAGER.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]MASK_IMAGE.CLD;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]MISCTOOLS.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]QUEUES.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]REQUIRED.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]SETDEFBOO.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]TEXTTOOLS.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]UETP.TLR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]VMSINSTAL.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]VMSINSTAL.FDL;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]VMSTAILOR.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[SYS0.SYSUPD]VMSUPDATE.COM;1<br />
%BACKUP-S-COMPARED, compared DUA0:[000000]SYSEXE.DIR;1<br />
%BACKUP-S-COMPARED, compared DUA0:[000000]VOLSET.SYS;1<br />
%BACKUP-I-PROCDONE, Operation completed. Processing finished at 21-JUL-2022 14:37:38.49<br />
If you do not want to perform another standalone BACKUP operation,<br />
use the console to halt the system.<br />
<br />
If you do want to perform another standalone BACKUP operation, <br />
ensure the standalone application volume is online and ready.<br />
Enter "YES" to continue: ['''STRG + e''']<br />
Simulation stopped, PC: 80008B1F (BRB 80008B1F)<br />
sim> '''EXIT'''<br />
Goodbye<br />
<br />
=== Finish Installation and Configure System ===<br />
<br />
sim> '''ATT TQ0 BB-BT05D-BE_VMS4.6_87.tap'''<br />
sim> '''BOOT'''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
KA630-A.V1.3<br />
<br />
<br />
Performing normal system tests.<br />
<br />
<br />
5..4..3..<br />
<br />
Tests completed.<br />
<br />
<br />
<br />
<br />
<br />
>>> '''B DUA0'''<br />
<br />
2..1..0..<br />
<br />
<br />
<br />
<br />
VAX/VMS Version KG 15-Jun-1987 10:00<br />
<br />
<br />
Please enter the date and time (DD-MMM-YYYY HH:MM): 21-jul-2022 14:43<br />
<br />
Enter drive holding distribution kit (DDCU): '''MUA0:'''<br />
<br />
%MOUNT-I-MOUNTED, VMS046 mounted on _MUA0:<br />
If this node is part of a cluster, you may want to set up<br />
your system disk to run multiple cluster nodes from a single disk.<br />
<br />
Do you want to know more about cluster system disks [N]? '''Y'''<br />
<br />
In a cluster, you can run multiple systems with up to 14 nodes sharing<br />
all files except PAGEFILE.SYS, SWAPFILE.SYS, SYSDUMP.DMP and VAXVMSSYS.PAR.<br />
<br />
Do you want to generate a cluster common system disk [N]? '''Y'''<br />
<br />
In order to successfully boot the system, you must provide a nonzero value<br />
for the SYSGEN parameter SCSSYSTEMID and a nonblank value for the SYSGEN<br />
parameter SCSNODE. See the Guide to VAXclusters for information on<br />
setting up other SYSGEN parameters after the system is installed. <br />
<br />
Enter this node's SCSSYSTEMID value: '''1025'''<br />
Enter this node's SCSNODE name: '''EARL'''<br />
<br />
Restoring library saveset.<br />
%BACKUP-I-STARTVERIFY, starting verification pass<br />
<br />
Restoring optional saveset.<br />
%BACKUP-I-STARTVERIFY, starting verification pass<br />
<br />
Creating [V4COMMON] directory tree.<br />
%DCL-I-SUPERSEDE, previous value of SYS$COMMON has been superseded<br />
%DCL-I-SUPERSEDE, previous value of SYS$SYSROOT has been superseded<br />
%DCL-I-SUPERSEDE, previous value of SYS$COMMON has been superseded<br />
<br />
Now we will ask you for new passwords for the following accounts:<br />
SYSTEM, SYSTEST, FIELD<br />
<br />
<br />
<br />
Enter new password for account SYSTEM: '''vms047''' (not echoed)<br />
<br />
Re-enter the password for account SYSTEM for verification: '''vms047''' (not echoed)<br />
<br />
%UAF-I-MDFYMSG, user record(s) updated<br />
<br />
<br />
Enter new password for account SYSTEST: '''vms047''' (not echoed)<br />
<br />
Re-enter the password for account SYSTEST for verification: '''vms047''' (not echoed)<br />
<br />
%UAF-I-MDFYMSG, user record(s) updated<br />
<br />
<br />
Enter new password for account FIELD: '''vms047''' (not echoed)<br />
<br />
Re-enter the password for account FIELD for verification: '''vms047''' (not echoed)<br />
<br />
%UAF-I-MDFYMSG, user record(s) updated<br />
<br />
Creating RIGHTS database file, SYS$SYSTEM:RIGHTSLIST.DAT<br />
Ignore any "%SYSTEM-F-DUPIDENT, duplicate identifier" errors.<br />
%UAF-I-RDBCREMSG, RIGHTSLIST.DAT created<br />
%UAF-I-RDBADDMSGU, identifier DEFAULT value: [000200,000200] added to RIGHTSLIST.DAT<br />
%UAF-I-RDBADDMSGU, identifier FIELD value: [000001,000010] added to RIGHTSLIST.DAT<br />
%UAF-I-RDBADDMSGU, identifier SYSTEM value: [000001,000004] added to RIGHTSLIST.DAT<br />
%UAF-I-RDBADDMSGU, identifier SYSTEST value: [000001,000007] added to RIGHTSLIST.DAT<br />
%UAF-E-RDBADDERRU, unable to add SYSTEST_CLIG value: [000001,000007] to RIGHTSLIST.DAT<br />
-SYSTEM-F-DUPIDENT, duplicate identifier<br />
%UAF-I-NOMODS, no modifications made to system authorization file<br />
%UAF-I-RDBDONEMSG, rights database modified<br />
<br />
AUTOGEN computes the SYSGEN parameters for your configuration<br />
and then reboots the system with the new parameters.<br />
<br />
After the reboot, you may want to do one or more of the following tasks<br />
(consult the Guide to VAX/VMS System Manager's Reference Manual for<br />
detailed information): <br />
<br />
- Delete SYS$SYSTEM:STARTUP.INS<br />
<br />
- DECOMPRESS THE SYSTEM LIBRARIES - For space considerations, many of the system<br />
libraries are shipped in a data compressed format. If you have enough disk<br />
space, you may decompress them for faster access. Use SYS$UPDATE:LIBDECOMP.COM<br />
to data expand the libraries. If you choose not to decompress these libraries<br />
there will be a negative impact on the performance of the HELP and LINK<br />
commands.<br />
<br />
- APPLY THE MANDATORY UPDATE - The mandatory update for VMS V4.6 must be applied<br />
as soon as possible. You will be unable to install any optional software <br />
products until this update has been applied.<br />
<br />
<br />
Running AUTOGEN -- Please wait.<br />
<br />
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.<br />
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.<br />
You may wish to purge this file.<br />
%AUTOGEN-I-END, GETDATA phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.<br />
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.<br />
You may wish to purge this file.<br />
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.<br />
You may wish to purge this file.<br />
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.<br />
<br />
%AUTOGEN-I-CREATE, DISK$VAXVMSRL4:[SYS0.SYSEXE]PAGEFILE.SYS<br />
will be modified to hold 13200 blocks.<br />
%SYSGEN-I-EXTENDED, DISK$VAXVMSRL4:[SYS0.SYSEXE]PAGEFILE.SYS;1 extended<br />
<br />
<br />
%AUTOGEN-I-CREATE, DISK$VAXVMSRL4:[SYS0.SYSEXE]SWAPFILE.SYS<br />
will be modified to hold 8400 blocks.<br />
%SYSGEN-I-EXTENDED, DISK$VAXVMSRL4:[SYS0.SYSEXE]SWAPFILE.SYS;1 extended<br />
<br />
<br />
%AUTOGEN-I-DUMPFILE, A 32772 block dump file will be created.<br />
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created<br />
<br />
%AUTOGEN-I-END, GENFILES phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.<br />
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.<br />
<br />
The system is shutting down to allow the system to boot with the<br />
generated site-specific parameters and installed images.<br />
<br />
The system will automatically reboot after the shutdown and the<br />
upgrade will be complete.<br />
<br />
<br />
<br />
SHUTDOWN -- Perform an Orderly System Shutdown<br />
<br />
<br />
%SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check...<br />
%SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed<br />
<br />
%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.<br />
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.<br />
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0<br />
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.<br />
%JBC-E-JOBQUEDIS, system job queue manager is not running<br />
<br />
SHUTDOWN message from user SYSTEM at Batch 14:46:25<br />
The system will shut down in 0 minutes; back up soon. Please log off.<br />
Reboot system with AUTOGENerated parameters<br />
<br />
<br />
%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.<br />
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.<br />
%SHUTDOWN-I-REMOVE, All installed images will now be removed.<br />
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.<br />
<br />
Loading system software.<br />
?06 HLT INST<br />
<br />
PC = 20050419<br />
<br />
?15 CORRPTN<br />
<br />
<br />
=== Apply Mandatory Update ===<br />
<br />
<br />
KA630-A.V1.3<br />
<br />
<br />
Performing normal system tests.<br />
<br />
<br />
5..4..3..<br />
<br />
Tests completed.<br />
<br />
<br />
<br />
<br />
<br />
>>> ['''STRG + e''']<br />
Simulation stopped, PC: 20040CD1 (TSTB R1)<br />
sim> '''ATT TQ0 BB-KY83C-BE_VMS4.6-MUP_87.tap'''<br />
sim> '''C'''<br />
<br />
<br />
<br />
>>> '''B DUA0'''<br />
<br />
2..1..0..<br />
<br />
<br />
<br />
<br />
VAX/VMS Version KG 15-Jun-1987 10:00<br />
<br />
<br />
<br />
<br />
The MicroVMS system is now executing the system startup procedure.<br />
<br />
%UAF-I-RDBADDMSG, identifier SYS$NODE_EARL value: %X80010000 added to RIGHTSLIST.DAT<br />
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0<br />
SYSTEM job terminated at 21-JUL-2022 14:47:48.52<br />
<br />
<br />
<br />
Username: '''SYSTEM'''<br />
<br />
Password: '''vms047''' (not echoed)<br />
Welcome to VAX/VMS version KG <br />
<br />
$ '''@SYS$UPDATE:VMSINSTAL * MUA0:'''<br />
<br />
<br />
VAX/VMS Software Product Installation Procedure KG <br />
<br />
<br />
It is 21-JUL-2022 at 14:48.<br />
Enter a question mark (?) at any time for help.<br />
<br />
* Are you satisfied with the backup of your system disk [YES]? '''YES'''<br />
<br />
Please mount the first volume of the set on MUA0:.<br />
* Are you ready? '''YES'''<br />
<br />
%MOUNT-I-MOUNTED, MUP046 mounted on _EARL$MUA0:<br />
<br />
The following products will be processed:<br />
<br />
VMSMUP V4.6<br />
<br />
<br />
Beginning installation of VMSMUP V4.6 at 14:48<br />
<br />
%VMSINSTAL-I-RESTORE, Restoring product saveset A...<br />
<br />
<br />
This kit contains the mandatory update for Version 4.6 of VAX/VMS.<br />
It must be applied to the 4.6 base kit.<br />
<br />
<br />
<br />
1) Apply all fixes to the system<br />
2) Create a file with the descriptions of all fixes<br />
3) Both of the above<br />
<br />
* What would you like to do [3]: '''3'''<br />
<br />
%VMSMUP-I-FIXDESC, The fixes are described in SYS$UPDATE:VMSMUP046.TXT<br />
* Do you want to purge files replaced by this installation [YES]? '''YES'''<br />
<br />
%MOUNT-I-MOUNTED, MUP046 mounted on _EARL$MUA0:<br />
%BACKUP-I-STARTVERIFY, starting verification pass<br />
%BACKUP-W-NOFILES, no files selected from MUA0:[000000]VMSMUP046.B;<br />
%DELETE-W-SEARCHFAIL, error searching for SYS$COMMON:[SYSUPD.KITINSTAL_SCRATCH]*.*;*<br />
-RMS-E-DNF, directory not found<br />
-SYSTEM-W-NOSUCHFILE, no such file<br />
%BACKUP-I-STARTVERIFY, starting verification pass<br />
%BACKUP-W-NOFILES, no files selected from MUA0:[000000]VMSMUP046.C;<br />
<br />
1) CTDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]CTDRIVER.EXE;1<br />
<br />
2) F11BXQP (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]F11BXQP.EXE;2<br />
<br />
3) LATSYM (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]LATSYM.EXE;2<br />
<br />
4) PEDRIVER (miscellaneous fix)<br />
<br />
5) RMS (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]RMS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]RMS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]RMS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]RMS.EXE;1<br />
<br />
6) SYS (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]SYS.EXE;1<br />
<br />
7) SYSLOA8NN (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]SYSLOA8NN.EXE;1<br />
<br />
8) TUDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]TUDRIVER.EXE;1<br />
<br />
9) UETINIT00 (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]UETINIT00.EXE;1<br />
<br />
10) VAXCRTL (miscellaneous fix)<br />
<br />
11) VAXCRTL (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]VAXCRTL.EXE;1<br />
<br />
12) VAXCRTLG (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]VAXCRTLG.EXE;1<br />
<br />
13) XQDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMSMUP046]XQDRIVER.EXE;1<br />
<br />
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...<br />
<br />
Installation of VMSMUP V4.6 completed at 14:48<br />
<br />
%VMSINSTAL-I-REBOOT, This product requires that the system be rebooted.<br />
<br />
<br />
SHUTDOWN -- Perform an Orderly System Shutdown<br />
<br />
<br />
%SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check...<br />
%SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed<br />
<br />
%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.<br />
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.<br />
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1<br />
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.<br />
%JBC-E-JOBQUEDIS, system job queue manager is not running<br />
<br />
SHUTDOWN message on EARL from user SYSTEM at _EARL$OPA0: 14:48:47<br />
EARL will shut down in 0 minutes; back up soon. Please log off node EARL.<br />
Reboot after VMSMUP V4.6 installation.<br />
<br />
1 terminal has been notified on EARL.<br />
<br />
%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.<br />
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.<br />
%SHUTDOWN-I-REMOVE, All installed images will now be removed.<br />
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.<br />
<br />
<br />
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM<br />
<br />
Infinite loop, PC: 80008D7E (BRB 80008D7E)<br />
sim> '''EXIT'''<br />
Goodbye<br />
<br />
=== Install Local Area VAXcluster Key ===<br />
<br />
<br />
sim> '''ATT TQ0 AQ-JK26A-BE LOCAL AREA VAXCLUSTER 1.0 86.tap'''<br />
sim> '''BOOT'''<br />
<br />
<br />
<br />
<br />
<br />
KA630-A.V1.3<br />
<br />
<br />
Performing normal system tests.<br />
<br />
<br />
5..4..3..<br />
<br />
Tests completed.<br />
<br />
<br />
<br />
<br />
<br />
>>> '''B DUA0'''<br />
<br />
2..1..0..<br />
<br />
<br />
<br />
<br />
VAX/VMS Version V4.6 6-Jul-1987 17:00<br />
<br />
<br />
<br />
<br />
The MicroVMS system is now executing the system startup procedure.<br />
<br />
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0<br />
SYSTEM job terminated at 21-JUL-2022 14:50:26.03<br />
<br />
<br />
<br />
Username: '''SYSTEM'''<br />
<br />
Password: '''vms047''' (not echoed)<br />
Welcome to VAX/VMS version V4.6<br />
Last interactive login on Thursday, 21-JUL-2022 14:47<br />
<br />
$ '''@SYS$UPDATE:VMSINSTAL * MUA0:'''<br />
<br />
<br />
VAX/VMS Software Product Installation Procedure V4.6 <br />
<br />
<br />
It is 21-JUL-2022 at 14:50.<br />
Enter a question mark (?) at any time for help.<br />
<br />
* Are you satisfied with the backup of your system disk [YES]? '''YES'''<br />
<br />
Please mount the first volume of the set on MUA0:.<br />
* Are you ready? '''YES'''<br />
<br />
%MOUNT-I-MOUNTED, LAV mounted on _EARL$MUA0:<br />
<br />
The following products will be processed:<br />
<br />
LAV V1.0<br />
<br />
<br />
Beginning installation of LAV V1.0 at 14:51<br />
<br />
%VMSINSTAL-I-RESTORE, Restoring product saveset A...<br />
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...<br />
<br />
Installation of LAV V1.0 completed at 14:51<br />
<br />
<br />
<br />
VMSINSTAL procedure done at 14:51<br />
<br />
== Cluster Configuration ==<br />
<br />
=== Configure Cluster Boot Node ===<br />
<br />
<br />
$ '''@SYS$MANAGER:BOOT_CONFIG'''<br />
<br />
Boot Node Configuration Procedure<br />
<br />
This procedure can CONFIGURE a Local Area VAXcluster boot node<br />
or ADD another system disk.<br />
<br />
<br />
<br />
CONFIGURE a boot node or ADD another system disk [CONFIGURE]? '''CONFIGURE'''<br />
<br />
This procedure configures a boot node in a cluster. It initializes <br />
the cluster authorization file, sets the volume label of SYS$SYSDEVICE <br />
to EARL_SYS, modifies SYS$SYSTEM:MODPARAMS.DAT, invokes AUTOGEN, <br />
and reboots the system with the new parameters.<br />
<br />
To ensure that you have the required privileges, invoke this<br />
procedure from the system manager's account.<br />
<br />
WARNING - The cluster PASSWORD will not be echoed.<br />
<br />
Enter this cluster's group number: '''1'''<br />
Enter this cluster's password: '''SECRET''' (not echoed)<br />
<br />
Re-enter this cluster's password for verification: '''SECRET''' (not echoed)<br />
<br />
<br />
Enter this node's SCSSYSTEMID value: '''1025'''<br />
<br />
Enter this node's DECnet node name: '''EARL'''<br />
<br />
How many boot nodes will be in this cluster (1 or 2)? '''1'''<br />
<br />
AUTOGEN computes the SYSGEN parameters for your configuration<br />
and then reboots the system with the new parameters.<br />
<br />
After the reboot, you may want to configure other nodes in<br />
your cluster.<br />
<br />
<br />
Running AUTOGEN -- Please wait.<br />
<br />
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.<br />
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.<br />
You may wish to purge this file.<br />
%AUTOGEN-I-END, GETDATA phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.<br />
%AUTOGEN-I-OVERRIDE, user specified value for VAXCLUSTER<br />
overrides preceding requirements for this parameter in PARAMS.DAT<br />
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.<br />
You may wish to purge this file.<br />
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.<br />
You may wish to purge this file.<br />
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.<br />
%AUTOGEN-I-NOCHANGE, No page file modifications will be made.<br />
%AUTOGEN-I-NOCHANGE, No swap file modifications will be made.<br />
<br />
%AUTOGEN-I-NOCHANGE, No dump file modifications will be made.<br />
<br />
%AUTOGEN-I-END, GENFILES phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.<br />
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.<br />
<br />
The system is shutting down to allow the system to boot with the<br />
generated site-specific parameters and installed images.<br />
<br />
The system will automatically reboot after the shutdown and the<br />
upgrade will be complete.<br />
<br />
<br />
<br />
SHUTDOWN -- Perform an Orderly System Shutdown<br />
<br />
<br />
%SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check...<br />
%SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed<br />
<br />
%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.<br />
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.<br />
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1<br />
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.<br />
%JBC-E-JOBQUEDIS, system job queue manager is not running<br />
<br />
SHUTDOWN message on EARL from user SYSTEM at _EARL$OPA0: 14:52:02<br />
EARL will shut down in 0 minutes; back up soon. Please log off node EARL.<br />
Reboot system with AUTOGENerated parameters<br />
<br />
1 terminal has been notified on EARL.<br />
<br />
%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.<br />
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.<br />
%SHUTDOWN-I-REMOVE, All installed images will now be removed.<br />
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.<br />
<br />
Loading system software.<br />
?06 HLT INST<br />
<br />
PC = 20050419<br />
<br />
?15 CORRPTN<br />
<br />
=== Install DECnet Routing Key ===<br />
<br />
KA630-A.V1.3<br />
<br />
<br />
Performing normal system tests.<br />
<br />
<br />
5..4..3..<br />
<br />
Tests completed.<br />
<br />
<br />
<br />
<br />
<br />
>>> ['''STRG + e''']<br />
Simulation stopped, PC: 20040CD1 (TSTB R1)<br />
sim> '''ATT RQ1 netrtg040.RX5'''<br />
sim> '''C'''<br />
<br />
<br />
<br />
>>> '''B DUA0'''<br />
<br />
2..1..0..<br />
<br />
<br />
<br />
<br />
VAX/VMS Version V4.6 6-Jul-1987 17:00<br />
<br />
<br />
<br />
waiting to form or join VAXcluster<br />
%STACONFIG-I-LOADSECDB, loading the Local Area VAXcluster security database<br />
%STACONFIG-I-CLUSDEV, starting Local Area VAXcluster protocol on _XQA0: <br />
%STACONFIG-I-LOADMSCP, loading the MSCP disk server<br />
%STACONFIG-I-SERVDEV, now serving device _EARL$DUA0:<br />
%STACONFIG-I-SERVDEV, now serving device _EARL$DUA1:<br />
<br />
%CNXMAN, Proposing formation of a VAXcluster<br />
<br />
%CNXMAN, Now a VAXcluster member -- system EARL<br />
<br />
%CNXMAN, Completing VAXcluster state transition<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 14:54:20.54 %%%%%%%%%%%<br />
Logfile has been initialized by operator _EARL$OPA0:<br />
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 14:54:20.54 %%%%%%%%%%%<br />
14:54:18.28 Node EARL (csid 00000000) proposed formation of a VAXcluster<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 14:54:20.54 %%%%%%%%%%%<br />
14:54:18.28 Node EARL (csid 00010001) is now a VAXcluster member<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 14:54:20.54 %%%%%%%%%%%<br />
14:54:18.29 Node EARL (csid 00010001) completed VAXcluster state transition<br />
<br />
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0<br />
SYSTEM job terminated at 21-JUL-2022 14:54:20.69<br />
<br />
<br />
<br />
Username: '''SYSTEM'''<br />
<br />
Password: '''vms047''' (not echoed)<br />
Welcome to VAX/VMS version V4.6<br />
Last interactive login on Thursday, 21-JUL-2022 14:50<br />
<br />
$ '''@SYS$UPDATE:VMSINSTAL * DUA1:'''<br />
<br />
<br />
VAX/VMS Software Product Installation Procedure V4.6 <br />
<br />
<br />
It is 21-JUL-2022 at 14:55.<br />
Enter a question mark (?) at any time for help.<br />
<br />
* Are you satisfied with the backup of your system disk [YES]? '''YES'''<br />
<br />
Please mount the first volume of the set on DUA1:.<br />
* Are you ready? '''YES'''<br />
<br />
%MOUNT-I-MOUNTED, NETRTG01 mounted on _EARL$DUA1:<br />
<br />
The following products will be processed:<br />
<br />
NETRTG V4.0<br />
<br />
<br />
Beginning installation of NETRTG V4.0 at 14:55<br />
<br />
%VMSINSTAL-I-RESTORE, Restoring product saveset A...<br />
<br />
DECnet-VAX Full Function Key installation<br />
<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.NETRTG040]NETACP.EXE;1<br />
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...<br />
<br />
Installation of NETRTG V4.0 completed at 14:55<br />
<br />
<br />
<br />
VMSINSTAL procedure done at 14:55<br />
<br />
$<br />
<br />
=== Configure DECnet ===<br />
<br />
$ '''@SYS$MANAGER:NETCONFIG'''<br />
<br />
DECnet-VAX network configuration procedure<br />
<br />
This procedure will help you define the parameters needed to get DECnet <br />
running on this machine. You will be shown the changes before they are <br />
executed, in case you wish to perform them manually.<br />
<br />
<br />
What do you want your DECnet node name to be? [EARL]: '''EARL'''<br />
<br />
What do you want your DECnet address to be? [1.1]: '''1.1'''<br />
<br />
Do you want to operate as a router? [NO (nonrouting)]: '''YES'''<br />
<br />
Do you want a default DECnet account? [YES]: '''YES'''<br />
<br />
Here are the commands necessary to setup your system.<br />
<br />
--------------------------------------------------------------------------<br />
$ RUN SYS$SYSTEM:NCP<br />
PURGE KNOWN OBJECTS ALL<br />
PURGE MODULE CONFIGURATOR KNOWN CIRCUITS ALL<br />
$ DEFINE/USER SYS$OUTPUT NL:<br />
$ DEFINE/USER SYS$ERROR NL:<br />
$ RUN SYS$SYSTEM:NCP ! Remove existing entry, if any<br />
PURGE NODE 1.1 ALL<br />
PURGE NODE EARL ALL<br />
$ RUN SYS$SYSTEM:NCP<br />
DEFINE EXECUTOR ADDRESS 1.1 STATE ON<br />
DEFINE EXECUTOR NAME EARL<br />
DEFINE EXECUTOR MAXIMUM ADDRESS 1023<br />
DEFINE EXECUTOR TYPE ROUTING IV<br />
DEFINE EXECUTOR NONPRIVILEGED USER DECNET<br />
DEFINE EXECUTOR NONPRIVILEGED PASSWORD DECNET<br />
$ DEFINE/USER_MODE SYSUAF SYS$SYSTEM:SYSUAF.DAT<br />
$ RUN SYS$SYSTEM:AUTHORIZE<br />
ADD DECNET /OWNER="DECNET DEFAULT" -<br />
/PASSWORD=DECNET -<br />
/UIC=[376,376] /ACCOUNT=DECNET -<br />
/DEVICE=SYS$SPECIFIC: /DIRECTORY=[DECNET] -<br />
/PRIVILEGE=(TMPMBX,NETMBX) -<br />
/DEFPRIVILEGE=(TMPMBX,NETMBX) -<br />
Press RETURN to continue<br />
<br />
<br />
/FLAGS=(CAPTIVE) /LGICMD=NL: -<br />
/NOBATCH /NOINTERACTIVE <br />
$ CREATE/DIRECTORY SYS$SPECIFIC:[DECNET] /OWNER=[376,376]<br />
$ RUN SYS$SYSTEM:NCP<br />
DEFINE LINE QNA-0 STATE ON<br />
DEFINE CIRCUIT QNA-0 STATE ON COST 4<br />
DEFINE LOGGING MONITOR STATE ON<br />
DEFINE LOGGING MONITOR EVENTS 0.0-9<br />
DEFINE LOGGING MONITOR EVENTS 2.0-1<br />
DEFINE LOGGING MONITOR EVENTS 4.2-13,15-16,18-19<br />
DEFINE LOGGING MONITOR EVENTS 5.0-18<br />
DEFINE LOGGING MONITOR EVENTS 128.0-4<br />
--------------------------------------------------------------------------<br />
<br />
<br />
Do you want to go ahead and do it? [YES]: YES<br />
<br />
%UAF-I-ADDMSG, user record successfully added<br />
%UAF-I-RDBADDMSGU, identifier DECNET value: [000376,000376] added to RIGHTSLIST.DAT<br />
%UAF-I-DONEMSG, system authorization file modified<br />
%UAF-I-RDBDONEMSG, rights database modified<br />
%NCP-I-NMLRSP, listener response - Success <br />
Logging sink type = monitor<br />
%NML-I-RECADDED, Database entry added<br />
<br />
The changes have been made.<br />
<br />
If you have not already installed the DECnet-VAX license, then do so now.<br />
<br />
After the license has been installed, you should invoke the procedure<br />
SYS$MANAGER:STARTNET.COM to startup DECnet-VAX with these changes.<br />
<br />
<br />
(If the license is already installed) Do you want DECnet started? [YES]: '''YES'''<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 14:56:19.93 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet starting<br />
<br />
%RUN-S-PROC_ID, identification of created process is 2020002D<br />
%RUN-S-PROC_ID, identification of created process is 2020002F<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 14:56:25.05 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 4.10, circuit up<br />
From node 1.1 (EARL), 21-JUL-2022 14:56:20.11<br />
Circuit QNA-0<br />
<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 14:56:30.60 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 4.7, circuit down, circuit fault<br />
From node 1.1 (EARL), 21-JUL-2022 14:56:30.60<br />
Circuit QNA-0, Line synchronization lost<br />
<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 14:56:30.60 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 4.10, circuit up<br />
From node 1.1 (EARL), 21-JUL-2022 14:56:30.60<br />
Circuit QNA-0<br />
<br />
<br />
=== Configure Cluster Satellite Node TRICK ===<br />
<br />
<br />
$ '''@SATELLITE_CONFIG'''<br />
<br />
<br />
<br />
Satellite Configuration Procedure<br />
<br />
<br />
This procedure configures a satellite node in the cluster.<br />
It can ADD or REMOVE a satellite node, and it can MODIFY <br />
the network database.<br />
<br />
To ensure that you have the required privileges, invoke this<br />
procedure from the system manager's account.<br />
<br />
If the local disk on the satellite node is to be INITIALIZED for <br />
paging and swapping, please be sure you are satisfied with the<br />
BACKUP of the local disk before proceeding.<br />
<br />
<br />
ADD, REMOVE or MODIFY a satellite node [ADD]? '''ADD'''<br />
<br />
Verifying circuits in network database...<br />
<br />
May this procedure temporarily interrupt DECnet traffic [YES]? '''YES'''<br />
<br />
What is the device name for the new system root [SYS$SYSDEVICE:]? '''SYS$SYSDEVICE:'''<br />
<br />
What is the name of the new system root [SYS1]? '''SYS6'''<br />
<br />
What is the DECnet node name of the satellite node? '''TRICK'''<br />
<br />
What is the DECnet node address of the satellite node? '''1.6'''<br />
<br />
Allow conversational bootstraps on the satellite node [NO]? '''NO'''<br />
<br />
Creating directory tree SYS6...<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSEXE> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSLIB> created<br />
%SET-I-ENTERED, EARL$DUA0:<000000>V4COMMON.DIR;1 entered as EARL$DUA0:<SYS6>SYSCOMMON.DIR;<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSTEST> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSMAINT> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSMGR> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSHLP> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSHLP.EXAMPLES> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSUPD> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSMSG> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSERR> created<br />
%CREATE-I-CREATED, EARL$DUA0:<SYS6.SYSCBI> created<br />
System root SYS6 created.<br />
<br />
What is the hardware address of the satellite node? '''08-00-2B-0C-15-21'''<br />
<br />
Updating network database...<br />
<br />
Size of pagefile for the new satellite [10000 blocks]? '''10000'''<br />
<br />
Size of swap file for the new satellite [8000 blocks]? '''8000'''<br />
<br />
May the local satellite disk be used for paging and swapping? '''NO'''<br />
<br />
%SYSGEN-I-CREATED, EARL$DUA0:<SYS6.SYSEXE>PAGEFILE.SYS;1 created<br />
%SYSGEN-I-CREATED, EARL$DUA0:<SYS6.SYSEXE>SWAPFILE.SYS;1 created<br />
The satellite configuration procedure has successfully completed.<br />
<br />
This node has been configured to allow the satellite node to <br />
join this cluster.<br />
<br />
The first time the satellite node boots, "NETCONFIG" and<br />
"AUTOGEN" will run automatically.<br />
<br />
<br />
$<br />
<br />
== Cluster Testing VMS V4.6 ==<br />
<br />
=== microvax2000.ini for the Satellite Node (a Diskless MicroVAX 2000) ===<br />
<br />
; microvax2000.ini<br />
<br />
SET QUIET<br />
<br />
SET CPU MODEL=MICROVAX<br />
SET CPU 8M<br />
SET CPU CONHALT<br />
SET CPU IDLE=VMS<br />
<br />
ATT NVR NVR-VS2000.BIN<br />
<br />
SET CONSOLE LOG=TRICK_001.LOG<br />
<br />
SET RD0 DIS<br />
SET RD1 DIS<br />
SET RD2 DIS<br />
SET RD3 DIS<br />
<br />
SET RZ1 DIS<br />
SET RZ2 DIS<br />
SET RZ3 DIS<br />
SET RZ4 DIS<br />
SET RZ5 DIS<br />
SET RZ6 DIS<br />
SET RZ7 DIS<br />
<br />
SET XS ENA<br />
set NAR MAC=08-00-2B-0C-15-21<br />
ATT XS tap:tap2<br />
<br />
BOOT<br />
<br />
=== Boot of Cluster Satellite TRICK MicroVAX 2000 ===<br />
<br />
Ensure that the Boot Node EARL and the Satellite Node TRICK are connected via Ethernet.<br />
<br />
I use [[Connect Multiple SIMH Network Instances on one Computer|this setup]].<br />
<br />
KA410-A V2.3 <br />
<br />
F_..E...D...C?..B...A...9...8...7...6...5...4_..3_..2_..1...<br />
<br />
<br />
?? C 0080 0000.0004<br />
? 6 00A0 0000.4001<br />
<br />
<br />
>>> '''B ESA0'''<br />
<br />
<br />
-ESA0<br />
<br />
System loaded by node EARL (AA-00-04-00-01-04)<br />
<br />
<br />
<br />
VAX/VMS Version V4.7 28-Oct-1987 13:00<br />
<br />
<br />
<br />
%CNXMAN, Discovered system EARL<br />
<br />
%CNXMAN, Established connection to system EARL<br />
%STACONFIG-I-LOADMSCP, loading the MSCP disk server<br />
waiting to form or join VAXcluster<br />
<br />
%CNXMAN, Sending VAXcluster membership request to system EARL<br />
<br />
%CNXMAN, Now a VAXcluster member -- system TRICK<br />
Configuring network...<br />
%UAF-E-UAEERR, invalid username, username already exists<br />
%UAF-I-NOMODS, no modifications made to system authorization file<br />
%UAF-I-RDBNOMODS, no modifications made to rights database<br />
%NCP-I-NMLRSP, listener response - Success <br />
Logging sink type = monitor<br />
%NML-I-RECADDED, Database entry added<br />
%AUTOGEN-I-BEGIN, GETDATA phase is beginning.<br />
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:PARAMS.DAT has been created.<br />
You may wish to purge this file.<br />
%AUTOGEN-I-END, GETDATA phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, GENPARAMS phase is beginning.<br />
%AUTOGEN-I-NEWFILE, A new version of SYS$MANAGER:VMSIMAGES.DAT has been created.<br />
You may wish to purge this file.<br />
%AUTOGEN-I-NEWFILE, A new version of SYS$SYSTEM:SETPARAMS.DAT has been created.<br />
You may wish to purge this file.<br />
%AUTOGEN-I-END, GENPARAMS phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, GENFILES phase is beginning.<br />
%AUTOGEN-I-NOCHANGE, No page file modifications will be made.<br />
%AUTOGEN-I-NOCHANGE, No swap file modifications will be made.<br />
<br />
%AUTOGEN-I-DUMPFILE, A 12292 block dump file will be created.<br />
%SYSGEN-I-CREATED, SYS$SYSROOT:[SYSEXE]SYSDUMP.DMP;1 created<br />
<br />
%AUTOGEN-I-END, GENFILES phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, SETPARAMS phase is beginning.<br />
%AUTOGEN-I-END, SETPARAMS phase has successfully completed.<br />
%AUTOGEN-I-BEGIN, REBOOT phase is beginning.<br />
<br />
The system is shutting down to allow the system to boot with the<br />
generated site-specific parameters and installed images.<br />
<br />
The system will automatically reboot after the shutdown and the<br />
upgrade will be complete.<br />
<br />
<br />
<br />
SHUTDOWN -- Perform an Orderly System Shutdown<br />
<br />
<br />
%SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check...<br />
%SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed<br />
<br />
%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.<br />
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.<br />
%SET-I-INTSET, login interactive limit = 0, current interactive value = 0<br />
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.<br />
%SYSTEM-F-DEVOFFLINE, device is not in configuration or not available<br />
%OPCOM-W-NOREMBROAD, no VAXcluster terminals were notified because OPCOM is not available<br />
<br />
SHUTDOWN message on TRICK from user SYSTEM at TRICK Batch 12:07:55<br />
TRICK will shut down in 0 minutes; back up soon. Please log off node TRICK.<br />
Reboot system with AUTOGENerated parameters<br />
<br />
<br />
%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.<br />
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.<br />
%SHUTDOWN-I-REMOVE, All installed images will now be removed.<br />
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.<br />
<br />
<br />
83 BOOT SYS<br />
<br />
-ESA0<br />
<br />
System loaded by node EARL (AA-00-04-00-01-04)<br />
<br />
<br />
<br />
VAX/VMS Version V4.7 28-Oct-1987 13:00<br />
<br />
<br />
<br />
%CNXMAN, Discovered system EARL<br />
<br />
%CNXMAN, Established connection to system EARL<br />
waiting to form or join VAXcluster<br />
<br />
%CNXMAN, Sending VAXcluster membership request to system EARL<br />
<br />
%CNXMAN, Now a VAXcluster member -- system TRICK<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:09:56.42 %%%%%%%%%%%<br />
Logfile has been initialized by operator _TRICK$OPA0:<br />
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1<br />
<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:09:56.74 %%%%%%%%%%%<br />
12:09:38.71 Node TRICK (csid 00010004) is now a VAXcluster member<br />
<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:09:56.81 %%%%%%%%%%%<br />
Operator _EARL$OPA0: has been enabled, username SYSTEM<br />
<br />
%RUN-S-PROC_ID, identification of created process is 2080002C<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:10:04.31 %%%%%%%%%%%<br />
Message from user DECNET on TRICK<br />
DECnet starting<br />
<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:10:08.27 %%%%%%%%%%% (from node EARL at 26-JUL-2022 12:10:08.13)<br />
Message from user DECNET on EARL<br />
DECnet event 4.15, adjacency up<br />
From node 1.1 (EARL), 26-JUL-2022 12:10:08.13<br />
Circuit QNA-0, Adjacent node = 1.6 (TRICK)<br />
<br />
<br />
%RUN-S-PROC_ID, identification of created process is 2080002E<br />
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0<br />
SYSTEM job terminated at 26-JUL-2022 12:10:11.66<br />
<br />
<br />
<br />
Username: '''SYSTEM'''<br />
<br />
Password: '''vms047''' (not echoed)<br />
Welcome to VAX/VMS version V4.7 on node TRICK<br />
Last interactive login on Tuesday, 26-JUL-2022 11:59<br />
Last non-interactive login on Sunday, 24-JUL-2022 19:23<br />
<br />
$ '''SHOW NET'''<br />
<br />
VAX/VMS Network status for local node 1.6 TRICK on 26-JUL-2022 12:10:42.97<br />
<br />
This is a nonrouting node, and does not have any network information.<br />
The designated router for TRICK is node 1.1 .<br />
<br />
$ '''@SYS$SYSTEM:SHUTDOWN'''<br />
<br />
<br />
SHUTDOWN -- Perform an Orderly System Shutdown<br />
<br />
How many minutes until final shutdown [0]: ['''Enter''']<br />
Reason for shutdown [Standalone]: ['''Enter''']<br />
Do you want to spin down the disk volumes [NO]? ['''Enter'''] <br />
Do you want to invoke the site-specific shutdown procedure [YES]? ['''Enter''']<br />
Should an automatic system reboot be performed [NO]? ['''Enter''']<br />
When will the system be rebooted [later]: ['''Enter''']<br />
<br />
Shutdown options (enter as a comma-separated list):<br />
REMOVE_NODE Remaining nodes in the cluster should adjust quorum<br />
CLUSTER_SHUTDOWN Entire cluster is shutting down<br />
REBOOT_CHECK Check existence of basic system files<br />
<br />
Shutdown options [NONE]: ['''Enter''']<br />
<br />
%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:11:13.78 %%%%%%%%%%%<br />
Operator status for operator _TRICK$OPA0:<br />
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,<br />
OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11,<br />
OPER12<br />
<br />
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.<br />
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1<br />
%SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down.<br />
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.<br />
%JBC-E-JOBQUEDIS, system job queue manager is not running<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:11:15.12 %%%%%%%%%%%<br />
Message from user DECNET on TRICK<br />
DECnet shutting down<br />
<br />
<br />
%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.<br />
<br />
SHUTDOWN message on TRICK from user SYSTEM at _TRICK$OPA0: 12:11:15<br />
TRICK will shut down in 0 minutes; back up later. Please log off node TRICK.<br />
Standalone<br />
<br />
1 terminal has been notified on TRICK.<br />
1 terminal has been notified on EARL.<br />
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.<br />
%SHUTDOWN-I-REMOVE, All installed images will now be removed.<br />
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:11:18.10 %%%%%%%%%%%<br />
Message from user SYSTEM on TRICK<br />
_TRICK$OPA0:, TRICK shutdown was requested by the operator.<br />
<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:11:18.35 %%%%%%%%%%%<br />
Logfile was closed by operator _TRICK$OPA0:<br />
Logfile was SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1<br />
<br />
%%%%%%%%%%% OPCOM 26-JUL-2022 12:11:18.42 %%%%%%%%%%%<br />
Operator _TRICK$OPA0: has been disabled, username SYSTEM<br />
<br />
<br />
<br />
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM<br />
<br />
<br />
Infinite loop, PC: 80008D7E (BRB 80008D7E)<br />
sim> '''exit'''<br />
Goodbye<br />
<br />
=== Boot of Cluster Satellite TRICK (seen from Boot Node) ===<br />
<br />
$ <br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:10:20.61 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 0.3, automatic line service<br />
From node 1.1 (EARL), 21-JUL-2022 16:10:19.52<br />
Circuit QNA-0, Load, Requested, Node = 1.6 (TRICK)<br />
File = EARL$DUA0:<SYS6.>, Operating system, Ethernet address = 08-00-2B-0C-15-21<br />
<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:10:25.61 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 0.3, automatic line service<br />
From node 1.1 (EARL), 21-JUL-2022 16:10:24.14<br />
Circuit QNA-0, Load, Successful, Node = 1.6 (TRICK)<br />
File = EARL$DUA0:<SYS6.>, Operating system, Ethernet address = 08-00-2B-0C-15-21<br />
<br />
<br />
<br />
$ <br />
%PEA0, Software is Closing Virtual Circuit - REMOTE NODE TRICK <br />
<br />
<br />
$ <br />
%CNXMAN, Discovered system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:10:29.21 %%%%%%%%%%%<br />
16:10:29.21 Node EARL (sysid 1025) discovered node TRICK (sysid 1030)<br />
<br />
<br />
$ <br />
%CNXMAN, Established connection to system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:10:29.22 %%%%%%%%%%%<br />
16:10:29.22 Node EARL (csid 00010001) established connection to node TRICK<br />
<br />
<br />
$ <br />
%CNXMAN, Received VAXcluster membership request from system TRICK<br />
<br />
%CNXMAN, Proposing addition of system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:10:39.21 %%%%%%%%%%%<br />
16:10:39.21 Node EARL (csid 00010001) received VAXcluster membership request from node TRICK<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:10:39.21 %%%%%%%%%%%<br />
16:10:39.21 Node EARL (csid 00010001) proposed addition of node TRICK<br />
<br />
<br />
$ <br />
%CNXMAN, Completing VAXcluster state transition<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:10:39.88 %%%%%%%%%%%<br />
16:10:39.88 Node EARL (csid 00010001) completed VAXcluster state transition<br />
<br />
<br />
$ '''SHOW CLUSTER'''<br />
<br />
View of Cluster from system ID 1025 node: EARL 21-JUL-2022 16:11:24<br />
+-------------------+---------+<br />
| SYSTEMS | MEMBERS |<br />
+--------+----------+---------+<br />
| NODE | SOFTWARE | STATUS |<br />
+--------+----------+---------+<br />
| EARL | VMS V4.6 | MEMBER |<br />
| TRICK | VMS V4.6 | MEMBER |<br />
+--------+----------+---------+<br />
<br />
$ <br />
%CNXMAN, Lost connection to system TRICK<br />
<br />
%CNXMAN, Timed-out lost connection to system TRICK<br />
<br />
%CNXMAN, Proposing reconfiguration of the VAXcluster<br />
<br />
%CNXMAN, Removed from VAXcluster system TRICK<br />
<br />
%CNXMAN, Completing VAXcluster state transition<br />
<br />
$ <br />
<br />
=== Cluster Satellite TRICK Reboot (seen from Boot Node) ===<br />
<br />
SHUTDOWN message on EARL from user SYSTEM at _TRICK$OPA0: 16:18:01<br />
TRICK will shut down in 0 minutes; back up later. Please log off node TRICK.<br />
Standalone<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:18:04.50 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 16:18:04.30)<br />
Message from user SYSTEM on TRICK<br />
_TRICK$OPA0:, TRICK shutdown was requested by the operator.<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:18:04.77 %%%%%%%%%%%<br />
Operator _TRICK$OPA0: has been disabled, username SYSTEM<br />
<br />
<br />
$ <br />
%CNXMAN, Lost connection to system TRICK<br />
<br />
%CNXMAN, Timed-out lost connection to system TRICK<br />
<br />
%CNXMAN, Proposing reconfiguration of the VAXcluster<br />
<br />
%CNXMAN, Removed from VAXcluster system TRICK<br />
<br />
%CNXMAN, Completing VAXcluster state transition<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:18:14.93 %%%%%%%%%%%<br />
16:18:14.93 Node EARL (csid 00010001) lost connection to node TRICK<br />
<br />
%PEA0, Software is Closing Virtual Circuit - REMOTE NODE TRICK <br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:18:14.94 %%%%%%%%%%%<br />
16:18:14.93 Node EARL (csid 00010001) timed-out lost connection to node TRICK<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:18:14.94 %%%%%%%%%%%<br />
16:18:14.93 Node EARL (csid 00010001) proposed reconfiguration of the VAXcluster<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:18:14.94 %%%%%%%%%%%<br />
16:18:14.93 Node TRICK (csid 00010003) has been removed from the VAXcluster<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:18:14.94 %%%%%%%%%%%<br />
16:18:14.93 Node EARL (csid 00010001) completed VAXcluster state transition<br />
<br />
<br />
$ <br />
%CNXMAN, Deleting CSB for system TRICK<br />
<br />
%CNXMAN, Discovered system TRICK<br />
<br />
== Upgrade to VMS V4.7 ==<br />
<br />
=== Install Main Upgrade === <br />
<br />
$ ['''STRG + e''']<br />
Simulation stopped, PC: 80008B1F (BRB 80008B1F)<br />
sim> '''ATT TQ0 BB-KY59A-BE_VMS_4.7.tap'''<br />
sim> '''C'''<br />
<br />
$ '''MC NCP'''<br />
<br />
NCP>'''SET EXEC STATE OFF'''<br />
<br />
NCP>'''EXIT'''<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:20:12.60 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 0.7, aborted service request<br />
From node 1.1 (EARL), 21-JUL-2022 16:20:12.60<br />
Circuit QNA-0, Receive error<br />
<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:20:17.65 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 2.0, local node state change<br />
From node 1.1 (EARL), 21-JUL-2022 16:20:17.08<br />
Operator command, Old state = On, New state = Off<br />
<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:20:17.65 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 4.7, circuit down, circuit fault<br />
From node 1.1 (EARL), 21-JUL-2022 16:20:17.08<br />
Circuit QNA-0, Line synchronization lost<br />
<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:20:17.93 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet shutting down<br />
<br />
<br />
$ '''@SYS$UPDATE:VMSINSTAL VMS047'''<br />
<br />
<br />
VAX/VMS Software Product Installation Procedure V4.6 <br />
<br />
<br />
It is 21-JUL-2022 at 16:20.<br />
Enter a question mark (?) at any time for help.<br />
<br />
* Are you satisfied with the backup of your system disk [YES]? YES<br />
* Where will the distribution volumes be mounted: '''MUA0:'''<br />
<br />
Please mount the first volume of the set on MUA0:.<br />
* Are you ready? '''YES'''<br />
<br />
%MOUNT-I-MOUNTED, VMS047 mounted on _EARL$MUA0:<br />
<br />
The following products will be processed:<br />
<br />
VMS V4.7<br />
<br />
<br />
Beginning installation of VMS V4.7 at 16:23<br />
<br />
%VMSINSTAL-I-RESTORE, Restoring product saveset A...<br />
<br />
<br />
This kit contains Version 4.7 of VAX/VMS. It must be installed <br />
upon Version 4.6 of VAX/VMS. <br />
<br />
NOTE: Among the new images shipped in this kit are<br />
PEDRIVER.MSKEXE and DSDRIVER.MSKEXE. If your<br />
system is running LAVc or volume shadowing <br />
software, you MUST reapply the LAVC or volume <br />
shadowing key(s) AFTER applying the Version 4.7 <br />
update. If you do not reapply the appropriate keys,<br />
your system will not be running the updated<br />
images.<br />
<br />
<br />
<br />
The first phase of the upgrade will attempt to verify that all Digital<br />
supplied accounts are secured against obvious penetration attempts.<br />
<br />
%UPGRADE-I-PWD_OKAY, account password for SYSTEM verified<br />
%UPGRADE-I-PWD_OKAY, account password for FIELD verified<br />
%UPGRADE-I-PWD_OKAY, account password for SYSTEST verified<br />
<br />
%UPGRADE-W-PWD_INVALID, account password for SYSTEST_CLIG is invalid<br />
-UPGRADE-I-PWD_WEAK, password is too easy to guess<br />
<br />
Because of the preceding error, you must take action to secure this account.<br />
You must either disable this account, change its password, or do both.<br />
<br />
* Do you want to disable the account [YES]? '''YES'''<br />
<br />
%UPGRADE-I-DISUSER, account SYSTEST_CLIG disabled<br />
<br />
* Do you want to change the account password [YES]? '''YES'''<br />
<br />
<br />
You must now select a new primary password for the SYSTEST_CLIG account. The<br />
password you select must be at least 8 characters in length and may not<br />
be the same as the name of the account.<br />
<br />
<br />
New password: '''vms04747''' (not echoed)<br />
<br />
Verification: '''vms04747''' (not echoed)<br />
<br />
%UAF-I-MDFYMSG, user record(s) updated<br />
%UPGRADE-I-PWD_SET, primary password for account SYSTEST_CLIG set<br />
<br />
%UPGRADE-I-NONEXIST, account USER does not exist<br />
%UPGRADE-I-NONEXIST, account USERP does not exist<br />
<br />
<br />
1) Apply all fixes to the system<br />
2) Create a file with the descriptions of all fixes<br />
3) Both of the above<br />
<br />
* What would you like to do [3]: '''3'''<br />
<br />
%VMS-I-FIXDESC, The fixes are described in SYS$UPDATE:VMS047.TXT<br />
* Do you want to purge files replaced by this installation [YES]? '''YES'''<br />
<br />
%MOUNT-I-MOUNTED, VMS047 mounted on _EARL$MUA0:<br />
%BACKUP-I-STARTVERIFY, starting verification pass<br />
<br />
1) ADARTL (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ADARTL.EXE;1<br />
<br />
2) AGEN (miscellaneous fix)<br />
<br />
3) AUTOGEN (edit text file)<br />
<br />
4) BACKUP (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]BACKUP.EXE;1<br />
<br />
5) CLUSTRLOA (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]CLUSTRLOA.EXE;3<br />
<br />
6) COBRTL (miscellaneous fix)<br />
<br />
7) COBRTL (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]COBRTL.EXE;2<br />
<br />
8) CSP (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]CSP.EXE;3<br />
<br />
9) CTDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-ECOSET, eco level 1 already set in VMI$ROOT:[SYSEXE]CTDRIVER.EXE;2<br />
%VMSINSTAL-W-NOFILE, New file CTDRIVER.EXE does not exist.<br />
<br />
10) DEBUG (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]DEBUG.EXE;1<br />
<br />
11) DSDRIVER (miscellaneous fix)<br />
<br />
12) ERFCTLSHR (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ERFCTLSHR.EXE;1<br />
<br />
13) ERFLIB (miscellaneous fix)<br />
%VMS-I-ERFLIB.TLB TA79 update completed successfully, <br />
<br />
14) ERFPROC1 (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ERFPROC1.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ERFPROC1.EXE;1<br />
<br />
15) ESDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ESDRIVER.EXE;1<br />
<br />
16) ETDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ETDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ETDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ETDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ETDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]ETDRIVER.EXE;1<br />
<br />
17) F11BXQP (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]F11BXQP.EXE;3<br />
<br />
18) HSCPAD (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]HSCPAD.EXE;1<br />
<br />
19) JOBCTL (new image)<br />
<br />
20) LATCP (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]LATCP.EXE;2<br />
<br />
21) LATSYM (new image)<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]LATSYM.EXE;3<br />
<br />
22) LTDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]LTDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]LTDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]LTDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]LTDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]LTDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]LTDRIVER.EXE;1<br />
<br />
23) MOM (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]MOM.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]MOM.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]MOM.EXE;1<br />
<br />
24) MONITOR (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]MONITOR.EXE;1<br />
<br />
25) MTAAACP (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]MTAAACP.EXE;1<br />
<br />
26) NETACP (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETACP.EXE;1<br />
<br />
27) NETDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NETDRIVER.EXE;1<br />
<br />
28) NODRIVER (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NODRIVER.EXE;3<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]NODRIVER.EXE;3<br />
<br />
29) PEDRIVER (miscellaneous fix)<br />
<br />
30) RMS (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-ECOSET, eco level 1 already set in VMI$ROOT:[SYSEXE]RMS.EXE;2<br />
%PATCH-I-ECOSET, eco level 2 already set in VMI$ROOT:[SYSEXE]RMS.EXE;2<br />
%PATCH-I-ECOSET, eco level 3 already set in VMI$ROOT:[SYSEXE]RMS.EXE;2<br />
%PATCH-I-ECOSET, eco level 4 already set in VMI$ROOT:[SYSEXE]RMS.EXE;2<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]RMS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]RMS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]RMS.EXE;1<br />
<br />
31) SATELLITE_CONFIG (edit text file)<br />
<br />
32) SECURESHR (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SECURESHR.EXE;1<br />
<br />
33) SET (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SET.EXE;1<br />
<br />
34) SMBSRVSHR (new image)<br />
<br />
35) STABACKUP (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]STABACKUP.EXE;1<br />
<br />
36) SYS (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-ECOSET, eco level 80 already set in VMI$ROOT:[SYSEXE]SYS.EXE;2<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
%PATCH-I-ECONOTSET, eco level 88 not set in VMI$ROOT:[SYSEXE]SYS.EXE;2<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYS.EXE;1<br />
<br />
37) SYSINIT (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYSINIT.EXE;3<br />
<br />
38) SYSLOA790 (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYSLOA790.EXE;3<br />
<br />
39) SYSLOA8NN (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-ECOSET, eco level 1 already set in VMI$ROOT:[SYSEXE]SYSLOA8NN.EXE;2<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]SYSLOA8NN.EXE;1<br />
<br />
40) TPUSHR003 (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]TPUSHR.EXE;1<br />
<br />
41) TTDRIVER (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]TTDRIVER.EXE;3<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]TTDRIVER.EXE;3<br />
<br />
42) TUDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-ECOSET, eco level 1 already set in VMI$ROOT:[SYSEXE]TUDRIVER.EXE;2<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]TUDRIVER.EXE;1<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]TUDRIVER.EXE;1<br />
<br />
43) TVDRIVER (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]TVDRIVER.EXE;2<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]TVDRIVER.EXE;2<br />
<br />
44) UETDISK00 (new image)<br />
<br />
45) UETINIT00 (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-ECOSET, eco level 1 already set in VMI$ROOT:[SYSTEST]UETINIT00.EXE;2<br />
%VMSINSTAL-W-NOFILE, New file UETINIT00.EXE does not exist.<br />
<br />
46) UETINIT01 (new image)<br />
<br />
47) UISSHR (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]UISSHR.EXE;4<br />
<br />
48) VAXCRTL (miscellaneous fix)<br />
<br />
49) VAXCRTL (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-ECOSET, eco level 1 already set in VMI$ROOT:[SYSLIB]VAXCRTL.EXE;2<br />
%VMSINSTAL-W-NOFILE, New file VAXCRTL.EXE does not exist.<br />
<br />
50) VAXCRTLG (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-ECOSET, eco level 1 already set in VMI$ROOT:[SYSLIB]VAXCRTLG.EXE;2<br />
%VMSINSTAL-W-NOFILE, New file VAXCRTLG.EXE does not exist.<br />
<br />
51) VMB (new image)<br />
%VMS-I-VMB, ****************** IMPORTANT ********************<br />
%VMS-I-VMB, A new VMB.EXE was just copied to your system disk.<br />
%VMS-I-VMB, If your VAX processor bootstraps from an HSC disk over the <br />
%VMS-I-VMB, CI, you must update your console device after completing <br />
%VMS-I-VMB, this update procedure. See Section 1.7 of the Version 4.7<br />
%VMS-I-VMB, VMS Release Notes for instructions.<br />
%VMS-I-VMB, ***************************************************<br />
<br />
52) VPM (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]VPM.EXE;1<br />
<br />
53) XGDRIVER (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]XGDRIVER.EXE;3<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]XGDRIVER.EXE;3<br />
<br />
54) XQDRIVER (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-ECOSET, eco level 1 already set in VMI$ROOT:[SYSEXE]XQDRIVER.EXE;2<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]XQDRIVER.EXE;1<br />
<br />
55) YFDRIVER (new image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.VMS047]YFDRIVER.EXE;3<br />
<br />
%VMS-E-ERRORS, Of the 55 fixes listed above, the following 4 should be reviewed:<br />
9, 45, 49, 50<br />
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...<br />
<br />
Installation of VMS V4.7 completed at 16:24<br />
<br />
%VMSINSTAL-I-REBOOT, This product requires that the system be rebooted.<br />
<br />
<br />
SHUTDOWN -- Perform an Orderly System Shutdown<br />
<br />
<br />
%SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check...<br />
%SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed<br />
<br />
%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:24:30.63 %%%%%%%%%%%<br />
Operator status for operator _EARL$OPA0:<br />
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,<br />
OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11,<br />
OPER12<br />
<br />
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.<br />
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1<br />
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.<br />
%JBC-E-JOBQUEDIS, system job queue manager is not running<br />
<br />
SHUTDOWN message on EARL from user SYSTEM at _EARL$OPA0: 16:24:30<br />
EARL will shut down in 0 minutes; back up soon. Please log off node EARL.<br />
Reboot after VMS V4.7 installation.<br />
<br />
1 terminal has been notified on EARL.<br />
<br />
%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.<br />
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.<br />
%SHUTDOWN-I-REMOVE, All installed images will now be removed.<br />
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:24:30.79 %%%%%%%%%%%<br />
Message from user SYSTEM on EARL<br />
_EARL$OPA0:, EARL shutdown was requested by the operator.<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:24:30.80 %%%%%%%%%%%<br />
Logfile was closed by operator _EARL$OPA0:<br />
Logfile was SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;1<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:24:30.81 %%%%%%%%%%%<br />
Operator _EARL$OPA0: has been disabled, username SYSTEM<br />
<br />
<br />
<br />
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM<br />
<br />
Infinite loop, PC: 80008D7E (BRB 80008D7E)<br />
<br />
=== Boot VMS V4.7 and Re-Install Local Area VAXcluster Key ===<br />
<br />
<br />
sim> '''BOOT'''<br />
<br />
<br />
<br />
<br />
KA630-A.V1.3<br />
<br />
<br />
Performing normal system tests.<br />
<br />
<br />
5..4..3..<br />
<br />
Tests completed.<br />
<br />
<br />
<br />
<br />
<br />
>>> b dua0<br />
<br />
2..1..0..<br />
<br />
<br />
<br />
<br />
VAX/VMS Version V4.7 28-Oct-1987 13:00<br />
<br />
<br />
<br />
%STACONFIG-I-LOADSECDB, loading the Local Area VAXcluster security database<br />
SYSGEN%W-NOMSG, Message number 00000910<br />
PEDRIVER.EXE<br />
<br />
%STACONFIG-W-WARNING, unable to locate PEDRIVER, STS = 00000908<br />
<br />
waiting to form or join VAXcluster<br />
<br />
%CNXMAN, Proposing formation of a VAXcluster<br />
<br />
%CNXMAN, Now a VAXcluster member -- system EARL<br />
<br />
%CNXMAN, Completing VAXcluster state transition<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:28:01.53 %%%%%%%%%%%<br />
Logfile has been initialized by operator _EARL$OPA0:<br />
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:28:01.53 %%%%%%%%%%%<br />
16:27:59.48 Node EARL (csid 00000000) proposed formation of a VAXcluster<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:28:01.53 %%%%%%%%%%%<br />
16:27:59.48 Node EARL (csid 00010001) is now a VAXcluster member<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:28:01.53 %%%%%%%%%%%<br />
16:27:59.48 Node EARL (csid 00010001) completed VAXcluster state transition<br />
<br />
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0<br />
SYSTEM job terminated at 21-JUL-2022 16:28:01.68<br />
<br />
<br />
<br />
Username: '''SYSTEM'''<br />
<br />
Password: '''vms047''' (not echoed)<br />
Welcome to VAX/VMS version V4.7<br />
Last interactive login on Thursday, 21-JUL-2022 16:14<br />
<br />
$ ['''STRG + e''']<br />
Simulation stopped, PC: 80008B1F (BRB 80008B1F)<br />
sim> '''ATT TQ0 AQ-JK26A-BE LOCAL AREA VAXCLUSTER 1.0 86.tap'''<br />
sim> '''C'''<br />
<br />
<br />
$ '''@SYS$UPDATE:VMSINSTAL * MUA0:'''<br />
<br />
<br />
VAX/VMS Software Product Installation Procedure V4.7 <br />
<br />
<br />
It is 21-JUL-2022 at 16:28.<br />
Enter a question mark (?) at any time for help.<br />
<br />
* Are you satisfied with the backup of your system disk [YES]? '''YES'''<br />
<br />
Please mount the first volume of the set on MUA0:.<br />
* Are you ready? '''YES'''<br />
<br />
%MOUNT-I-MOUNTED, LAV mounted on _EARL$MUA0:<br />
<br />
The following products will be processed:<br />
<br />
LAV V1.0<br />
<br />
<br />
Beginning installation of LAV V1.0 at 16:29<br />
<br />
%VMSINSTAL-I-RESTORE, Restoring product saveset A...<br />
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...<br />
<br />
Installation of LAV V1.0 completed at 16:29<br />
<br />
<br />
<br />
VMSINSTAL procedure done at 16:29<br />
<br />
<br />
<br />
$ <br />
<br />
=== Install VMS V4.7 Security Update ===<br />
<br />
$ ['''STRG + e''']<br />
Simulation stopped, PC: 80008B1F (BRB 80008B1F)<br />
sim> '''ATT TQ0 BB-MI46A-BE_VMS_V47SECUPD030.tap'''<br />
sim> '''C'''<br />
<br />
<br />
$ '''@SYS$UPDATE:VMSINSTAL * MUA0:'''<br />
<br />
<br />
VAX/VMS Software Product Installation Procedure V4.7 <br />
<br />
<br />
It is 21-JUL-2022 at 16:29.<br />
Enter a question mark (?) at any time for help.<br />
<br />
* Are you satisfied with the backup of your system disk [YES]? '''YES'''<br />
<br />
Please mount the first volume of the set on MUA0:.<br />
* Are you ready? '''YES'''<br />
<br />
%MOUNT-I-MOUNTED, V47SEC mounted on _EARL$MUA0:<br />
<br />
The following products will be processed:<br />
<br />
V47SECUPD V3.0<br />
V50SECUPD V3.0<br />
<br />
<br />
Beginning installation of V47SECUPD V3.0 at 16:29<br />
<br />
%VMSINSTAL-I-RESTORE, Restoring product saveset A...<br />
<br />
Mandatory security update kit<br />
<br />
<br />
1) Apply all fixes to the system<br />
2) Create a file with the descriptions of all fixes<br />
3) Both of the above<br />
<br />
* What would you like to do [3]: '''3'''<br />
<br />
%V47SECUPD-I-FIXDESC, The fixes are described in SYS$UPDATE:V47SECUPD030.TXT<br />
* Do you want to purge files replaced by this installation [YES]? YES<br />
<br />
%MOUNT-I-MOUNTED, V47SEC mounted on _EARL$MUA0:<br />
<br />
1) INSTALL (new image)<br />
<br />
2) MOUNTSHR (new image)<br />
<br />
3) SECURESHR (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.V47SECUPD030]SECURESHR.EXE;1<br />
<br />
4) SYS (patch image)<br />
%PATCH-I-NOLCL, image does not contain local symbols<br />
%PATCH-I-NOGBL, some or all global symbols not accessible<br />
%PATCH-I-WRTFIL, updating image file VMI$ROOT:[SYSUPD.V47SECUPD030]SYS.EXE;1<br />
<br />
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target directories...<br />
<br />
Installation of V47SECUPD V3.0 completed at 16:30<br />
<br />
%VMSINSTAL-I-REBOOT, This product requires that the system be rebooted.<br />
%VMSINSTAL-W-PRODSKIP, Products that have not been installed will be skipped.<br />
<br />
<br />
SHUTDOWN -- Perform an Orderly System Shutdown<br />
<br />
<br />
%SHUTDOWN-I-BOOTCHECK, Performing reboot consistency check...<br />
%SHUTDOWN-I-CHECKOK, Basic reboot consistency check completed<br />
<br />
%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:30:07.34 %%%%%%%%%%%<br />
Operator status for operator _EARL$OPA0:<br />
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,<br />
OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11,<br />
OPER12<br />
<br />
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.<br />
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1<br />
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.<br />
%JBC-E-JOBQUEDIS, system job queue manager is not running<br />
<br />
SHUTDOWN message on EARL from user SYSTEM at _EARL$OPA0: 16:30:07<br />
EARL will shut down in 0 minutes; back up soon. Please log off node EARL.<br />
Reboot after V47SECUPD V3.0 installation.<br />
<br />
1 terminal has been notified on EARL.<br />
<br />
%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.<br />
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.<br />
%SHUTDOWN-I-REMOVE, All installed images will now be removed.<br />
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:30:07.59 %%%%%%%%%%%<br />
Message from user SYSTEM on EARL<br />
_EARL$OPA0:, EARL shutdown was requested by the operator.<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:30:07.60 %%%%%%%%%%%<br />
Logfile was closed by operator _EARL$OPA0:<br />
Logfile was SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;2<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:30:07.60 %%%%%%%%%%%<br />
Operator _EARL$OPA0: has been disabled, username SYSTEM<br />
<br />
<br />
<br />
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM<br />
<br />
Infinite loop, PC: 80008D7E (BRB 80008D7E)<br />
sim> '''EXIT'''<br />
Goodbye<br />
<br />
<br />
=== Boot Boot Node after VMS V4.7 Security Update ===<br />
<br />
sim> '''BOOT'''<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
KA630-A.V1.3<br />
<br />
<br />
Performing normal system tests.<br />
<br />
<br />
5..4..3..<br />
<br />
Tests completed.<br />
<br />
<br />
<br />
<br />
<br />
>>> '''B DUA0'''<br />
<br />
2..1..0..<br />
<br />
<br />
<br />
<br />
VAX/VMS Version V4.7 28-Oct-1987 13:00<br />
<br />
<br />
<br />
%STACONFIG-I-LOADSECDB, loading the Local Area VAXcluster security database<br />
waiting to form or join VAXcluster<br />
%STACONFIG-I-CLUSDEV, starting Local Area VAXcluster protocol on _XQA0: <br />
%STACONFIG-I-LOADMSCP, loading the MSCP disk server<br />
%STACONFIG-I-SERVDEV, now serving device _EARL$DUA0:<br />
%STACONFIG-I-SERVDEV, now serving device _EARL$DUA1:<br />
<br />
%CNXMAN, Proposing formation of a VAXcluster<br />
<br />
%CNXMAN, Now a VAXcluster member -- system EARL<br />
<br />
%CNXMAN, Completing VAXcluster state transition<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:32:44.41 %%%%%%%%%%%<br />
Logfile has been initialized by operator _EARL$OPA0:<br />
Logfile is SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;3<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:32:44.41 %%%%%%%%%%%<br />
16:32:42.46 Node EARL (csid 00000000) proposed formation of a VAXcluster<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:32:44.41 %%%%%%%%%%%<br />
16:32:42.46 Node EARL (csid 00010001) is now a VAXcluster member<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:32:44.41 %%%%%%%%%%%<br />
16:32:42.47 Node EARL (csid 00010001) completed VAXcluster state transition<br />
<br />
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0<br />
SYSTEM job terminated at 21-JUL-2022 16:32:44.57<br />
<br />
<br />
<br />
Username: '''SYSTEM'''<br />
<br />
Password: '''vms047''' (not echoed)<br />
Welcome to VAX/VMS version V4.7<br />
Last interactive login on Thursday, 21-JUL-2022 16:28<br />
<br />
$ '''@startnet'''<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:34:59.70 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet starting<br />
<br />
%RUN-S-PROC_ID, identification of created process is 2020002D<br />
%RUN-S-PROC_ID, identification of created process is 2020002F<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:35:04.84 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 4.10, circuit up<br />
From node 1.1 (EARL), 21-JUL-2022 16:34:59.90<br />
Circuit QNA-0<br />
<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:35:10.85 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 0.7, aborted service request<br />
From node 1.1 (EARL), 21-JUL-2022 16:35:10.85<br />
Circuit QNA-0, Receive error<br />
<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:05.85 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 4.10, circuit up<br />
From node 1.1 (EARL), 21-JUL-2022 16:36:05.85<br />
Circuit QNA-0<br />
<br />
=== Get rid of the recurring DECnet Event Messages ===<br />
<br />
There's a kind of "bug" in VMS V4.7:<br />
<br />
As long as there's no other DECnet computer connected, DECnet is permanently flapping down and up again.<br />
<br />
This does not hurt in itself, but the recurring OPCOM messages are distracting and disturbing, so let's switch them off.<br />
<br />
Enter the following NCP commands to switch the messages for DECnet Events 0.7 and 4.10 off:<br />
<br />
Delete from the volatile DECnet database (current settings): <br />
<br />
$ '''MC NCP CLEAR LOGGING MONITOR EVENTS 0.7'''<br />
$ '''MC NCP CLEAR LOGGING MONITOR EVENTS 4.10'''<br />
<br />
Delete from the permanent DECnet database (settings for subsequent boots): <br />
<br />
$ '''MC NCP PURGE LOGGING MONITOR EVENTS 0.7'''<br />
$ '''MC NCP PURGE LOGGING MONITOR EVENTS 4.10''' <br />
<br />
All other DECnet event messages remain.<br />
<br />
== Cluster Testing VMS V4.7 ==<br />
<br />
=== Boot of Cluster Satellite TRICK (seen from Boot Node) ===<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:13.43 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 0.3, automatic line service<br />
From node 1.1 (EARL), 21-JUL-2022 16:36:13.42<br />
Circuit QNA-0, Load, Requested, Node = 1.6 (TRICK)<br />
File = EARL$DUA0:<SYS6.>, Operating system, Ethernet address = 08-00-2B-0C-15-21<br />
<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:18.42 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 0.3, automatic line service<br />
From node 1.1 (EARL), 21-JUL-2022 16:36:16.49<br />
Circuit QNA-0, Load, Successful, Node = 1.6 (TRICK)<br />
File = EARL$DUA0:<SYS6.>, Operating system, Ethernet address = 08-00-2B-0C-15-21<br />
<br />
<br />
<br />
$ <br />
%PEA0, Software is Closing Virtual Circuit - REMOTE NODE TRICK <br />
<br />
<br />
$ <br />
%CNXMAN, Discovered system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:22.85 %%%%%%%%%%%<br />
16:36:22.85 Node EARL (sysid 1025) discovered node TRICK (sysid 1030)<br />
<br />
<br />
$ <br />
%CNXMAN, Established connection to system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:22.87 %%%%%%%%%%%<br />
16:36:22.87 Node EARL (csid 00010001) established connection to node TRICK<br />
<br />
<br />
$ <br />
%CNXMAN, Received VAXcluster membership request from system TRICK<br />
<br />
%CNXMAN, Proposing addition of system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:35.08 %%%%%%%%%%%<br />
16:36:35.08 Node EARL (csid 00010001) received VAXcluster membership request from node TRICK<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:35.08 %%%%%%%%%%%<br />
16:36:35.08 Node EARL (csid 00010001) proposed addition of node TRICK<br />
<br />
<br />
$ <br />
%CNXMAN, Completing VAXcluster state transition<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:35.77 %%%%%%%%%%%<br />
16:36:35.77 Node EARL (csid 00010001) completed VAXcluster state transition<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:53.66 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 16:36:53.71)<br />
16:36:36.42 Node TRICK (csid 00010002) is now a VAXcluster member<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:36:53.78 %%%%%%%%%%%<br />
Operator _TRICK$OPA0: has been enabled, username SYSTEM<br />
<br />
=== Shutdown of Satellite Node TRICK (seen from Boot Node) ===<br />
<br />
$ <br />
%CNXMAN, Lost connection to system TRICK<br />
%PEA0, Software is Closing Virtual Circuit - REMOTE NODE TRICK <br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:40:49.74 %%%%%%%%%%%<br />
16:40:49.74 Node EARL (csid 00010001) lost connection to node TRICK<br />
<br />
<br />
$ <br />
%CNXMAN, Re-established connection to system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:41:04.30 %%%%%%%%%%%<br />
16:41:04.30 Node EARL (csid 00010001) re-established connection to node TRICK<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:41:15.07 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 16:40:51.25)<br />
16:40:40.18 Node TRICK (csid 00010002) lost connection to node EARL<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:41:15.12 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 16:40:51.27)<br />
16:40:40.49 Node TRICK (csid 00010002) re-established connection to node EARL<br />
<br />
<br />
$ <br />
<br />
SHUTDOWN message on EARL from user SYSTEM at _TRICK$OPA0: 16:42:34<br />
TRICK will shut down in 0 minutes; back up later. Please log off node TRICK.<br />
Standalone<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:42:36.35 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 16:42:13.02)<br />
Message from user SYSTEM on TRICK<br />
_TRICK$OPA0:, TRICK shutdown was requested by the operator.<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:42:36.81 %%%%%%%%%%%<br />
Operator _TRICK$OPA0: has been disabled, username SYSTEM<br />
<br />
<br />
$ <br />
%CNXMAN, Lost connection to system TRICK<br />
<br />
%CNXMAN, Timed-out lost connection to system TRICK<br />
<br />
%CNXMAN, Proposing reconfiguration of the VAXcluster<br />
<br />
%CNXMAN, Removed from VAXcluster system TRICK<br />
<br />
%CNXMAN, Completing VAXcluster state transition<br />
<br />
$ <br />
%PEA0, Software is Closing Virtual Circuit - REMOTE NODE TRICK <br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:42:46.99 %%%%%%%%%%%<br />
16:42:46.99 Node EARL (csid 00010001) lost connection to node TRICK<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:42:46.99 %%%%%%%%%%%<br />
16:42:46.99 Node EARL (csid 00010001) timed-out lost connection to node TRICK<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:42:47.07 %%%%%%%%%%%<br />
16:42:46.99 Node EARL (csid 00010001) proposed reconfiguration of the VAXcluster<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:42:47.07 %%%%%%%%%%%<br />
16:42:46.99 Node TRICK (csid 00010002) has been removed from the VAXcluster<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:42:47.07 %%%%%%%%%%%<br />
16:42:46.99 Node EARL (csid 00010001) completed VAXcluster state transition<br />
<br />
<br />
$ <br />
%CNXMAN, Deleting CSB for system TRICK<br />
<br />
%CNXMAN, Discovered system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:42:47.49 %%%%%%%%%%%<br />
16:42:47.49 Node EARL (sysid 1025) discovered node TRICK (sysid 1030)<br />
<br />
<br />
$ <br />
%CNXMAN, Deleting CSB for system TRICK<br />
<br />
$ <br />
%PEA0, Software is Closing Virtual Circuit - REMOTE NODE TRICK <br />
<br />
<br />
=== Boot of Satellite Node TRICK (seen from Boot Node) ===<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:46:31.37 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 0.3, automatic line service<br />
From node 1.1 (EARL), 21-JUL-2022 16:46:31.37<br />
Circuit QNA-0, Load, Requested, Node = 1.6 (TRICK)<br />
File = EARL$DUA0:<SYS6.>, Operating system, Ethernet address = 08-00-2B-0C-15-21<br />
<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:46:36.37 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 0.3, automatic line service<br />
From node 1.1 (EARL), 21-JUL-2022 16:46:35.17<br />
Circuit QNA-0, Load, Successful, Node = 1.6 (TRICK)<br />
File = EARL$DUA0:<SYS6.>, Operating system, Ethernet address = 08-00-2B-0C-15-21<br />
<br />
<br />
<br />
$ <br />
%PEA0, Software is Closing Virtual Circuit - REMOTE NODE TRICK <br />
<br />
<br />
$ <br />
%CNXMAN, Discovered system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:46:41.49 %%%%%%%%%%%<br />
16:46:41.49 Node EARL (sysid 1025) discovered node TRICK (sysid 1030)<br />
<br />
<br />
$ <br />
%CNXMAN, Established connection to system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:46:41.50 %%%%%%%%%%%<br />
16:46:41.50 Node EARL (csid 00010001) established connection to node TRICK<br />
<br />
<br />
$ <br />
%CNXMAN, Received VAXcluster membership request from system TRICK<br />
<br />
%CNXMAN, Proposing addition of system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:47:53.52 %%%%%%%%%%%<br />
16:47:53.52 Node EARL (csid 00010001) received VAXcluster membership request from node TRICK<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:47:53.52 %%%%%%%%%%%<br />
16:47:53.52 Node EARL (csid 00010001) proposed addition of node TRICK<br />
<br />
<br />
$ <br />
%CNXMAN, Completing VAXcluster state transition<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:47:54.21 %%%%%%%%%%%<br />
16:47:54.21 Node EARL (csid 00010001) completed VAXcluster state transition<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:48:11.46 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 16:48:11.53)<br />
16:48:06.13 Node TRICK (csid 00010003) is now a VAXcluster member<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:48:11.58 %%%%%%%%%%%<br />
Operator _TRICK$OPA0: has been enabled, username SYSTEM<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:50:48.90 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 16:50:48.97)<br />
Message from user DECNET on TRICK<br />
DECnet starting<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:50:52.75 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 4.15, adjacency up<br />
From node 1.1 (EARL), 21-JUL-2022 16:50:52.75<br />
Circuit QNA-0, Adjacent node = 1.6 (TRICK)<br />
<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 16:50:55.91 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 16:50:56.03)<br />
Message from user DECNET on TRICK<br />
DECnet event 4.15, adjacency up<br />
From node 1.6 (TRICK), 21-JUL-2022 16:50:55.81<br />
Circuit SVA-0, Adjacent node = 1.1<br />
<br />
<br />
<br />
$ '''SHOW NET'''<br />
<br />
VAX/VMS Network status for local node 1.1 EARL on 21-JUL-2022 16:51:08.09<br />
<br />
<br />
<br />
Node Links Cost Hops Next Hop to Node<br />
<br />
1.1 EARL 0 0 0 (Local) -> 1.1 EARL<br />
1.6 TRICK 0 4 1 QNA-0 -> 1.6 TRICK<br />
<br />
Total of 2 nodes.<br />
<br />
$ '''SET HOST TRICK'''<br />
<br />
<br />
Username: '''SYSTEM'''<br />
<br />
Password: '''vms047''' (not echoed)<br />
Welcome to VAX/VMS version V4.7 on node TRICK<br />
Last interactive login on Thursday, 21-JUL-2022 16:49<br />
<br />
$ '''LOGOUT'''<br />
<br />
SYSTEM logged out at 21-JUL-2022 16:51:39.45<br />
%REM-S-END, control returned to node _EARL::<br />
<br />
$ <br />
<br />
=== Shutdown of Satellite Node TRICK (seen from Boot Node) ===<br />
<br />
SHUTDOWN message on EARL from user SYSTEM at _TRICK$OPA0: 17:44:47<br />
TRICK will shut down in 0 minutes; back up later. Please log off node TRICK.<br />
Standalone<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:44:47.89 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 17:44:47.86)<br />
Message from user DECNET on TRICK<br />
DECnet shutting down<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:44:50.60 %%%%%%%%%%% (from node TRICK at 21-JUL-2022 17:44:50.60)<br />
Message from user SYSTEM on TRICK<br />
_TRICK$OPA0:, TRICK shutdown was requested by the operator.<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:44:50.90 %%%%%%%%%%%<br />
Operator _TRICK$OPA0: has been disabled, username SYSTEM<br />
<br />
<br />
$ <br />
%CNXMAN, Lost connection to system TRICK<br />
<br />
%CNXMAN, Timed-out lost connection to system TRICK<br />
<br />
%CNXMAN, Proposing reconfiguration of the VAXcluster<br />
<br />
%CNXMAN, Removed from VAXcluster system TRICK<br />
<br />
%CNXMAN, Completing VAXcluster state transition<br />
<br />
$ <br />
%PEA0, Software is Closing Virtual Circuit - REMOTE NODE TRICK <br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:45:00.13 %%%%%%%%%%%<br />
17:45:00.13 Node EARL (csid 00010001) lost connection to node TRICK<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:45:00.13 %%%%%%%%%%%<br />
17:45:00.13 Node EARL (csid 00010001) timed-out lost connection to node TRICK<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:45:00.13 %%%%%%%%%%%<br />
17:45:00.13 Node EARL (csid 00010001) proposed reconfiguration of the VAXcluster<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:45:00.15 %%%%%%%%%%%<br />
17:45:00.13 Node TRICK (csid 00010003) has been removed from the VAXcluster<br />
<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:45:00.15 %%%%%%%%%%%<br />
17:45:00.13 Node EARL (csid 00010001) completed VAXcluster state transition<br />
<br />
<br />
$ <br />
%CNXMAN, Deleting CSB for system TRICK<br />
<br />
%CNXMAN, Discovered system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:45:00.64 %%%%%%%%%%%<br />
17:45:00.64 Node EARL (sysid 1025) discovered node TRICK (sysid 1030)<br />
<br />
<br />
$ <br />
%CNXMAN, Deleting CSB for system TRICK<br />
<br />
$ <br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:45:22.70 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet event 4.18, adjacency down<br />
From node 1.1 (EARL), 21-JUL-2022 17:45:22.70<br />
Circuit QNA-0, Adjacent node listener receive timeout<br />
Adjacent node = 1.6 (TRICK)<br />
<br />
<br />
<br />
$ <br />
%PEA0, Software is Closing Virtual Circuit - REMOTE NODE TRICK <br />
<br />
<br />
=== Shutdown Boot Node EARL ===<br />
<br />
$ '''@SYS$SYSTEM:SHUTDOWN'''<br />
<br />
<br />
<br />
SHUTDOWN -- Perform an Orderly System Shutdown<br />
<br />
How many minutes until final shutdown [0]: '''[Return]'''<br />
Reason for shutdown [Standalone]: <br />
Do you want to spin down the disk volumes [NO]? '''[Return]'''<br />
Do you want to invoke the site-specific shutdown procedure [YES]? '''[Return]'''<br />
Should an automatic system reboot be performed [NO]? '''[Return]'''<br />
When will the system be rebooted [later]: '''[Return]'''<br />
<br />
Shutdown options (enter as a comma-separated list):<br />
REMOVE_NODE Remaining nodes in the cluster should adjust quorum<br />
CLUSTER_SHUTDOWN Entire cluster is shutting down<br />
REBOOT_CHECK Check existence of basic system files<br />
<br />
Shutdown options [NONE]: '''[Return]'''<br />
<br />
%SHUTDOWN-I-OPERATOR, This terminal is now an operator's console.<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:47:04.61 %%%%%%%%%%%<br />
Operator status for operator _EARL$OPA0:<br />
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,<br />
OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10, OPER11,<br />
OPER12<br />
<br />
%SHUTDOWN-I-DISLOGINS, Interactive logins will now be disabled.<br />
%SET-I-INTSET, login interactive limit = 0, current interactive value = 1<br />
%SHUTDOWN-I-SHUTNET, The DECnet network will now be shut down.<br />
%SHUTDOWN-I-STOPQUEMAN, The queue manager will now be stopped.<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:47:04.70 %%%%%%%%%%%<br />
Message from user DECNET on EARL<br />
DECnet shutting down<br />
<br />
%JBC-E-JOBQUEDIS, system job queue manager is not running<br />
<br />
SHUTDOWN message on EARL from user SYSTEM at _EARL$OPA0: 17:47:04<br />
EARL will shut down in 0 minutes; back up later. Please log off node EARL.<br />
Standalone<br />
<br />
1 terminal has been notified on EARL.<br />
<br />
%SHUTDOWN-I-SITESHUT, The site-specific shutdown procedure will now be invoked.<br />
%SHUTDOWN-I-STOPUSER, All user processes will now be stopped.<br />
%SHUTDOWN-I-REMOVE, All installed images will now be removed.<br />
%SHUTDOWN-I-DISMOUNT, All volumes will now be dismounted.<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:47:05.08 %%%%%%%%%%%<br />
Message from user SYSTEM on EARL<br />
_EARL$OPA0:, EARL shutdown was requested by the operator.<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:47:05.09 %%%%%%%%%%%<br />
Logfile was closed by operator _EARL$OPA0:<br />
Logfile was SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;3<br />
<br />
%%%%%%%%%%% OPCOM 21-JUL-2022 17:47:05.11 %%%%%%%%%%%<br />
Operator _EARL$OPA0: has been disabled, username SYSTEM<br />
<br />
<br />
<br />
SYSTEM SHUTDOWN COMPLETE - USE CONSOLE TO HALT SYSTEM<br />
<br />
Infinite loop, PC: 80008D7E (BRB 80008D7E)<br />
sim> exit<br />
Goodbye<br />
Log file closed<br />
<br />
== Recommended Reading ==<br />
<br />
* AA-JP20C-TE VMS Local Area VAXcluster Manual (included in the [https://drive.google.com/drive/folders/1EtOslkPzuj4W4iw8MBPl886diDcAoKJp?usp=sharing installation set]])<br />
<br />
[[Category: SIMH Tutorials]]<br />
[[Category: VMS Practical Guides]]</div>
Vaxorcist
https://gunkies.org/w/index.php?title=Installing_and_Using_the_SIMH_InfoServer150VXT&diff=33111
Installing and Using the SIMH InfoServer150VXT
2024-01-28T09:23:16Z
<p>Vaxorcist: "See also" added</p>
<hr />
<div>== Preparations ==<br />
<br />
=== Networking Setup ===<br />
<br />
Set up networking using [[Connect Multiple SIMH Network Instances on one Computer|these instructions]].<br />
<br />
=== Get InfoServer Software CDROMs ===<br />
<br />
Get the [https://www.digiater.nl/openvms/freeware/v80/infoserver/infoserver.zip InfoServer software CDROMs here].<br />
<br />
=== SIMH InfoServer Setup ===<br />
<br />
Use the follwing <code>infoserver150vxt.ini</code> file for the InfoServer150 configuration:<br />
<br />
; ================================================<br />
; infoserver150vxt.ini<br />
; ================================================<br />
<br />
SET QUIET<br />
<br />
; CPU Settings<br />
SET CPU 4M<br />
SET CPU IDLE=INFOSERVER<br />
SET CPU CONHALT<br />
ATTACH NVR VAX412.NVR<br />
<br />
SET CONSOLE LOG=150vxt_001.log<br />
<br />
SET DZ DISABLED<br />
<br />
SET RZ0 DISABLED<br />
<br />
SET RZ1 RZ23<br />
ATTACH RZ1 INFO.DSK<br />
<br />
SET RZ2 RRD42<br />
ATT RZ2 -R ag-r7lfa-bs.img<br />
SET RZ3 DIS<br />
SET RZ4 DIS<br />
SET RZ5 DISABLED<br />
SET RZ7 DISABLED<br />
<br />
SET RZB0 DISABLED<br />
SET RZB1 DISABLED<br />
SET RZB2 DISABLED<br />
SET RZB3 DISABLED<br />
SET RZB4 DISABLED<br />
SET RZB5 DISABLED<br />
SET RZB7 DISABLED<br />
<br />
; Connect InfoServer network device to host device eth0<br />
;ATT XS tap:tap0<br />
<br />
; Auto-Boot the InfoServer Software on Chevrons Output<br />
; EXPECT ">>> " SEND "BOOT\r"; GO -Q<br />
<br />
BOOT CPU<br />
; ================================================<br />
; End<br />
; ================================================<br />
<br />
== Install InfoServer 150 Software from CDROM ==<br />
<br />
KA41-2 V1.0<br />
<br />
F_..E?..D...C?..B?..A...9_..8?..7...6...5?..4_..3_..2_..1?..<br />
<br />
<br />
?? E 0040 0000.0014<br />
? D 0050 0000.0081<br />
?? C 0080 0000.0004<br />
?? B 0010 0004.0020<br />
?? 8 0060 0000.0002<br />
? 6 80A1 0000.4001<br />
?? 5 0001 0000.000A<br />
?? 1 00C0 0000.1004<br />
<br />
>>> '''SH BFLG'''<br />
00000000<br />
<br />
>>> '''SET BFLG D0000000'''<br />
<br />
>>> '''BOOT DKA200'''<br />
<br />
-DKA200<br />
<br />
InfoServer 150 V3.5<br />
Copyright (c) 1990 - 1997 Digital Equipment Corporation<br />
%ESS-I-CONFIGDEV, Device configuration complete. 2 devices found<br />
<br />
%ESS-I-FORMDISK, Formatting internal InfoServer disk, please wait...<br />
%ESS-I-COPIED, Copy operation completed successfully.<br />
%ESS-I-CREATEDBOOT, Boot partition created successfully.<br />
%ESS-I-UPDATE, Update request completed successfully.<br />
%ESS-I-UPDATESYS, Please REBOOT the InfoServer to run the installed version.<br />
%ESS-I-VERIFY, Verifying DK1:<br />
<br />
Enter Password: '''ESS''' [not echoed]<br />
<br />
<br />
Digital Equipment Corporation<br />
InfoServer 150 V3.5<br />
<br />
<br />
InfoServer> '''SHOW DEVICE'''<br />
<br />
Device Device Device Device Dev. Size/ Volume Device<br />
Name State Type Address Record Num. Label Char<br />
<br />
DK1: On Hard Disk A/1 204863 UNKNOWN AME<br />
DK2: On Compact Disc A/2 98880 IS_V35 AME<br />
<br />
InfoServer> '''DIR DK1:'''<br />
<br />
Directory DK1:<br />
<br />
Partition Name Used/Alloc Services<br />
-------------------- ----------------- --------------------<br />
BOOT_PARTITION 5000/5008 <br />
IS1000_V35 1027/1040 Temp MOP<br />
<br />
DK1: has 2 partitions in use. 6048 of 204863 blocks allocated. <br />
Largest contiguous free extent is 198784 blocks.<br />
<br />
InfoServer> '''REBOOT'''<br />
_Are you sure you want to reboot the server now [No]? '''YES'''<br />
<br />
?06 HLT INST<br />
<br />
PC = 80033FEB<br />
<br />
<br />
>>> '''[CTRL-e]'''<br />
Simulation stopped, PC: 20048DA5 (BSBW 20048DC1)<br />
sim> '''EXIT'''<br />
Goodbye<br />
<br />
== Verify Installation ==<br />
<br />
KA41-2 V1.0<br />
<br />
F_..E...D...C?..B?..A...9_..8?..7...6...5?..4_..3_..2_..1?..<br />
<br />
<br />
?? C 0080 0000.0004<br />
?? B 0010 0004.0020<br />
?? 8 0060 0000.0002<br />
? 6 80A1 0000.4001<br />
?? 5 0001 0000.000A<br />
?? 1 00C0 0000.1004<br />
<br />
>>> '''SHOW BOOT'''<br />
DKA0,DKA100<br />
<br />
>>> '''SET BOOT DKA100'''<br />
<br />
>>> '''SHOW BOOT'''<br />
DKA100<br />
<br />
>>> '''SHOW BFLG'''<br />
D0000000<br />
<br />
>>> '''BOOT'''<br />
<br />
-DKA100<br />
<br />
InfoServer 150 V3.5<br />
Copyright (c) 1990 - 1997 Digital Equipment Corporation<br />
%ESS-I-CONFIGDEV, Device configuration complete. 2 devices found<br />
<br />
%ESS-I-VERIFY, Verifying DK1:<br />
<br />
Enter Password: '''ESS''' [not echoed]<br />
<br />
Digital Equipment Corporation<br />
InfoServer 150 V3.5<br />
<br />
<br />
InfoServer> '''REBOOT'''<br />
_Are you sure you want to reboot the server now [No]? YES<br />
<br />
?06 HLT INST<br />
<br />
PC = 80033FEB<br />
<br />
>>> '''[CTRL-e]'''<br />
Simulation stopped, PC: 20048DA5 (BSBW 20048DC1)<br />
sim> '''EXIT'''<br />
Goodbye<br />
<br />
== Change infoserver150vxt.ini to boot automatically ==<br />
<br />
Remove the <code>;</code> from the line:<br />
; EXPECT ">>> " SEND "BOOT\r"; GO -Q <br />
<br />
in <code>infoserver150vxt.ini</code>, save and restart the InfoServer150.<br />
<br />
== Install additional InfoServer Functions ==<br />
<br />
KA41-2 V1.0<br />
<br />
F_..E...D...C?..B?..A...9_..8?..7...6...5?..4_..3_..2_..1?..<br />
<br />
<br />
?? C 0080 0000.0004<br />
?? B 0010 0004.0020<br />
?? 8 0060 0000.0002<br />
? 6 80A1 0000.4001<br />
?? 5 0001 0000.000A<br />
?? 1 00C0 0000.1004<br />
<br />
>>> BOOT<br />
<br />
-DKA100<br />
<br />
InfoServer 150 V3.5<br />
Copyright (c) 1990 - 1997 Digital Equipment Corporation<br />
%ESS-I-CONFIGDEV, Device configuration complete. 2 devices found<br />
<br />
%ESS-I-VERIFY, Verifying DK1:<br />
<br />
Enter Password: '''ESS''' [not echoed]<br />
<br />
<br />
Digital Equipment Corporation<br />
InfoServer 150 V3.5<br />
<br />
<br />
InfoServer> '''SHOW FUNCTIONS'''<br />
<br />
* Function Information for InfoServer V3.5 *<br />
<br />
InfoServer Functions Installed: Other Functions Available:<br />
------------------------------- --------------------------<br />
X-terminal services Open disk access (any client) <br />
Open tape access (any client) <br />
CD-R functions <br />
<br />
Additional functions from the 'Other Functions Available' list can be<br />
installed from Function-CDROMs available from Digital. Contact your Digital<br />
representative to purchase additional functions.<br />
<br />
<br />
InfoServer> '''[CTRL-e]''' <br />
Simulation stopped, PC: 80033F36 (INCL 8003A094)<br />
sim> SH RZ<br />
RZ 7 units<br />
RZ1 104MB, attached to INFO.DSK, write enabled<br />
RZ23, autosize, RAW format<br />
RZ2 50MB, attached to ag-r7lfa-bs.img, read only, write locked<br />
RRD42, autosize, RAW format<br />
sim> '''ATT RZ2 ag-pjxka-re.img'''<br />
sim> '''C'''<br />
<br />
<br />
InfoServer> '''UPDATE FUNCTIONS DK2: DK1:'''<br />
%ESS-I-UPDATE, Update request completed successfully.<br />
<br />
InfoServer> '''SHOW FUNCTIONS'''<br />
<br />
* Function Information for InfoServer V3.5 *<br />
<br />
InfoServer Functions Installed: Other Functions Available:<br />
------------------------------- --------------------------<br />
X-terminal services Open tape access (any client) <br />
Open disk access (any client) CD-R functions <br />
<br />
Additional functions from the 'Other Functions Available' list can be<br />
installed from Function-CDROMs available from Digital. Contact your Digital<br />
representative to purchase additional functions.<br />
<br />
<br />
InfoServer> '''[CTRL-e]'''<br />
Simulation stopped, PC: 80033F36 (INCL 8003A094)<br />
sim> '''ATT RZ2 ag-pjxla-re.img'''<br />
sim> '''C'''<br />
<br />
<br />
InfoServer> UPDATE FUNCTIONS DK2: DK1:<br />
%ESS-I-UPDATE, Update request completed successfully.<br />
<br />
InfoServer> '''SHOW FUNCTIONS'''<br />
<br />
* Function Information for InfoServer V3.5 *<br />
<br />
InfoServer Functions Installed: Other Functions Available:<br />
------------------------------- --------------------------<br />
X-terminal services CD-R functions <br />
Open disk access (any client) <br />
Open tape access (any client) <br />
<br />
Additional functions from the 'Other Functions Available' list can be<br />
installed from Function-CDROMs available from Digital. Contact your Digital<br />
representative to purchase additional functions.<br />
<br />
<br />
InfoServer> '''[CTRL-e]'''<br />
Simulation stopped, PC: 80033F36 (INCL 8003A094)<br />
sim> '''ATT RZ2 ag-q1mua-xe.img'''<br />
sim> '''C'''<br />
<br />
<br />
InfoServer> '''UPDATE FUNCTIONS DK2: DK1:'''<br />
%ESS-I-UPDATE, Update request completed successfully.<br />
<br />
InfoServer> '''SHOW FUNCTIONS'''<br />
<br />
* Function Information for InfoServer V3.5 *<br />
<br />
InfoServer Functions Installed: Other Functions Available:<br />
------------------------------- --------------------------<br />
X-terminal services <br />
Open disk access (any client) <br />
Open tape access (any client) <br />
CD-R functions <br />
<br />
<br />
InfoServer> '''REBOOT'''<br />
_Are you sure you want to reboot the server now [No]? '''YES'''<br />
<br />
?06 HLT INST<br />
<br />
PC = 80033FEB<br />
<br />
<br />
>>> '''[CTRL-e]'''<br />
Simulation stopped, PC: 20046A33 (TSTL 4(SP))<br />
sim> '''EXIT'''<br />
Goodbye<br />
<br />
== Verify New InfoServer Functions ==<br />
<br />
KA41-2 V1.0<br />
<br />
F_..E...D...C?..B?..A...9_..8?..7...6...5?..4_..3_..2_..1?..<br />
<br />
<br />
?? C 0080 0000.0004<br />
?? B 0010 0004.0020<br />
?? 8 0060 0000.0002<br />
? 6 80A1 0000.4001<br />
?? 5 0001 0000.000A<br />
?? 1 00C0 0000.100C<br />
<br />
>>> BOOT<br />
<br />
-DKA100<br />
<br />
InfoServer 150 V3.5<br />
Copyright (c) 1990 - 1997 Digital Equipment Corporation<br />
%ESS-I-CONFIGDEV, Device configuration complete. 2 devices found<br />
<br />
%ESS-I-VERIFY, Verifying DK1:<br />
<br />
Enter Password: '''ESS''' [not echoed]<br />
<br />
<br />
Digital Equipment Corporation<br />
InfoServer 150 V3.5<br />
<br />
<br />
InfoServer> '''SHOW FUNCTIONS'''<br />
<br />
* Function Information for InfoServer V3.5 *<br />
<br />
InfoServer Functions Installed: Other Functions Available:<br />
------------------------------- --------------------------<br />
X-terminal services <br />
Open disk access (any client) <br />
Open tape access (any client) <br />
CD-R functions <br />
<br />
<br />
InfoServer> '''REBOOT'''<br />
_Are you sure you want to reboot the server now [No]? YES<br />
<br />
?06 HLT INST<br />
<br />
PC = 80033FEB<br />
<br />
<br />
>>> sim> '''EXIT'''<br />
Goodbye<br />
<br />
== See also ==<br />
<br />
* [[Infoserver series]]<br />
<br />
[[Category:SIMH Tutorials]]</div>
Vaxorcist