Installing Ultrix 4.5 on SIMH - Revision history

Vaxorcist: /* Running the Emulator */ Made "MOP" a link

2026-09-06T18:32:49Z

Running the Emulator: Made "MOP" a link

← Older revision		Revision as of 18:32, 6 September 2026
Line 165:		Line 165:
	>>>boot/r5:3 dua0		>>>boot/r5:3 dua0

	Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''MOP'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.		Note: You can also boot from ethernet (<code>boot XQA0</code>) but this requires a DEC-specific boot server in your network (the protocol is called ''[[MOP]]'' for ''Maintenance Operations Protocol''), which is beyond the scope of this document. I did get it to work a few years ago though, but it was a bit difficult to set up.

	For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..		For a list and description of all commands available in the bootloader (hint: there are lots), see the ''KA655 CPU System Maintenance'' guide mentioned in the ''References'' section..

Rayrayemu: Fixed error in ed command note.

2023-09-29T07:30:05Z

Fixed error in ed command note.

← Older revision		Revision as of 07:30, 29 September 2023
Line 277:		Line 277:
	Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.		Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

	Note: These changes also work for Ultrix 4.4. If you would like to try 4.2 ~~or 4.3~~, use 164 instead of 173 and 184 instead of 193.		Note: These changes also work for Ultrix 4.3 and 4.4. If you would like to try 4.2, use 164 instead of 173 and 184 instead of 193.

	After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:		After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

Rayrayemu: Added instructions for other versions of Ultrix.

2023-09-29T07:10:03Z

Added instructions for other versions of Ultrix.

← Older revision		Revision as of 07:10, 29 September 2023
Line 276:		Line 276:

	Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.		Then we change line 193 from <code>rz* )</code> to <code>ra* )</code> since we're trying to install on an RA type disk which was apparently not supported in ULTRIX out of the box.

			Note: These changes also work for Ultrix 4.4. If you would like to try 4.2 or 4.3, use 164 instead of 173 and 184 instead of 193.

	After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:		After writing the file with <code>w</code> and quitting ed with <code>q</code>, we're back at the prompt, at which point we can use CTRL+D to retry the installation:

Vaxorcist: /* SimH configuration */ Corrected RQDX3 link

2023-08-19T19:55:04Z

SimH configuration: Corrected RQDX3 link

← Older revision		Revision as of 19:55, 19 August 2023
Line 17:		Line 17:
	*64mb memory		*64mb memory
	*[[DELQA]] network card (XQ0)		*[[DELQA]] network card (XQ0)
	*Two [[RA90]] disk drives (with 1.2gb each) attached to an [[RQDX3]] controller (RQ0 and RQ1)		*Two [[RA90]] disk drives (with 1.2gb each) attached to an [[RQDX3 MFM Disk & Floppy QBUS Controller\|RQDX3]] controller (RQ0 and RQ1)
	*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)		*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
	*[[TK50]] tape attached as unit 0 on the first [[TQK50]] controller (TQ0)		*[[TK50]] tape attached as unit 0 on the first [[TQK50]] controller (TQ0)

Vaxorcist: Some links added

2023-06-16T18:10:17Z

Some links added

← Older revision		Revision as of 18:10, 16 June 2023
Line 1:		Line 1:
	This WORK-IN-PROGRESS guide will be a simple guide to installing ULTRIX 4.5 for VAX on ~~SimH~~.		This WORK-IN-PROGRESS guide will be a simple guide to installing [[ULTRIX]] 4.5 for VAX on [[SIMH]].

	==Requirements==		==Requirements==
	The following is a list of things required for installation		The following is a list of things required for installation
	*A recent version of the [[SIMH]] emulator		*A recent version of the SIMH emulator
	**Make sure the binary you're using includes Ethernet support		**Make sure the binary you're using includes [[Ethernet]] support
	**I'm using a self-compiled version (git revision 0e8c0aea)		**I'm using a self-compiled version (git revision 0e8c0aea)
	*An ISO image of ULTRIX 4.5 for VAX		*An ISO image of ULTRIX 4.5 for [[VAX]]
	**See the "Resources" section for a download link		**See the "Resources" section for a download link
	**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist		**It's probably also possible to install it from tape, although I don't know if any installation tapes for ULTRIX 4.5 exist
Line 14:		Line 14:
	==SimH configuration==		==SimH configuration==
	The machine I'm using to run ULTRIX has the following configuration		The machine I'm using to run ULTRIX has the following configuration
	*DEC MicroVAX 3800		*[[DEC]] [[MicroVAX 3800/3900\|MicroVAX 3800]]
	*64mb memory		*64mb memory
	*DELQA network card (XQ0)		*[[DELQA]] network card (XQ0)
	*Two [[RA90]] disk drives (with 1.2gb each) attached to an RQDX3 controller (RQ0 and RQ1)		*Two [[RA90]] disk drives (with 1.2gb each) attached to an [[RQDX3]] controller (RQ0 and RQ1)
	*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)		*CD ROM drive attached to the same RQDX3 controller as unit 2 (RQ2)
	*[[TK50]] tape attached as unit 0 on the first TQK50 controller (TQ0)		*[[TK50]] tape attached as unit 0 on the first [[TQK50]] controller (TQ0)
	*DZV11 terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)		*[[DZV11]] terminal multiplexer with 16 lines, attached to telnet port 1005 (DZ)
	*LPT line printer attached to text file <code>printer_output.txt</code>		*[[LPT]] line printer attached to text file <code>printer_output.txt</code>

	Here's my config file (I called it <code>simh.conf</code>)		Here's my config file (I called it <code>simh.conf</code>)

Vaxorcist: Category added

2022-07-03T16:42:12Z

Category added

← Older revision		Revision as of 16:42, 3 July 2022
Line 1,195:		Line 1,195:

	[[Category:SIMH Tutorials]]		[[Category:SIMH Tutorials]]
			[[Category: ULTRIX]]

Darkstar: /* Network configuration */ DNS/BIND updates

2017-01-22T11:21:03Z

Network configuration: DNS/BIND updates

← Older revision		Revision as of 11:21, 22 January 2017
Line 1,112:		Line 1,112:
	*** Can't find server name for address 192.168.1.1: Not implemented		*** Can't find server name for address 192.168.1.1: Not implemented
	*** Default servers are not available		*** Default servers are not available
	The problem is that ULTRIX sends so-called ''inverse queries'' (not to be confused with the well-known ''reverse lookups'', which are actually just regular forward lookups to a specific TLD) to map IP addresses to hostnames. Most DNS servers don't support these inverse queries anymore. ~~I have yet to find~~ an ~~implementation that does. Alternatively there~~ might be ~~a way~~ to ~~disable inverse~~ queries ~~in ULTRIX~~. ~~If anyone knows of either, let me know~~...		The problem is that ULTRIX sends so-called ''inverse queries'' (not to be confused with the well-known ''reverse lookups'', which are actually just regular forward lookups to a specific TLD) to map IP addresses to hostnames. Most DNS servers don't support these inverse queries anymore. Apparently, BIND8 still included an option "fake-iquery" which might be used to support these queries. Versions before BIND8 (4.x) supported IQUERY natively. I have yet to test both variants to see which (if any) of them work.

	==Shutting down cleanly==		==Shutting down cleanly==

Darkstar: /* Network configuration */

2015-12-06T16:28:32Z

Network configuration

@@ Line 1,103: / Line 1,103: @@
 ...
 </pre>
 ==Shutting down cleanly==

Darkstar: /* Resources */

2015-12-06T11:49:30Z

Resources

← Older revision		Revision as of 11:49, 6 December 2015
Line 1,181:		Line 1,181:
	*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]		*DEC KA655 CPU System Maintenance [http://bitsavers.trailing-edge.com/pdf/dec/vax/655/EK-306A-MG-001_655Mnt_Mar89.pdf]
	*Some notes and links to more ULTRIX information [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/docs.html]		*Some notes and links to more ULTRIX information [https://web-docs.gsi.de/~kraemer/COLLECTION/ULTRIX/docs.html]
			*Ultrix Guide to Disk Maintenance [http://www.carelife.com/manuals/Ultrix_Guide_Disk_Maint.PDF]
			*Some random notes about ULTRIX 4.0 (some also apply to 4.5) [http://apfelboymchen.net/gnu/UNIX/vax-ultrix.html]

	[[Category:SIMH Tutorials]]		[[Category:SIMH Tutorials]]

Darkstar: /* Enabling outside access */

2015-12-06T10:56:36Z

Enabling outside access

← Older revision		Revision as of 10:56, 6 December 2015
Line 1,167:		Line 1,167:
	Requires secure terminal		Requires secure terminal
	</pre>		</pre>
	~~I still~~ have to ~~figure out what~~ to ~~change~~ so ~~that root access is permitted through telnet~~... ~~But it's no big deal for now~~		To enable root access for all telnet sessions, you will have to edit the /etc/ttys file and change every line that starts with "ttyp" to include the secure flag:
			ttyp0 none network
			will become
			ttyp0 none network secure
			and so on...

	==Resources==		==Resources==