{"id":137,"date":"2016-05-07T12:16:08","date_gmt":"2016-05-07T12:16:08","guid":{"rendered":"http:\/\/mal-home.dyndns.org\/wordpress\/?p=137"},"modified":"2016-05-07T12:16:08","modified_gmt":"2016-05-07T12:16:08","slug":"decserver-200","status":"publish","type":"post","link":"https:\/\/avitech.com.au\/?p=137","title":{"rendered":"DECserver 200"},"content":{"rendered":"

\"ds200-front-view\"<\/a><\/p>\n

What is it?<\/h3>\n

The DECserver 200 is a “terminal server”. It enables up to 8 terminals to login to various DEC computer systems over an Ethernet link.<\/p>\n

Back in the day a DECserver it was used to connect terminals and printers to DEC systems.\u00a0 Typically these were VAX machines, though some PDP-11 systems also supported them.<\/p>\n

DECservers were a welcome development for two reasons:<\/p>\n

    \n
  1. You no longer needed to have machine-specific terminal multiplexers in the computer itself. The computer now needed to have only one serial port (for the system console) and an Ethernet interface. You could add as many user terminals and printers as needed by adding one or more DECservers to the network. Each DECserver 200 supports 8 devices (terminals or printers).<\/li>\n
  2. From the one terminal on your desk you could now connect to any computer on your network that supports DEC’s LAT protocol. This includes VAX computers running VMS and PDP-11 computers running RSX-11M.\u00a0 So you could now switch between computers (and switch between multiple “sessions” on the one computer) on the one terminal without unplugging any cables.<\/li>\n<\/ol>\n

    Very conveniently, Linux also has great support for DECservers.<\/p>\n

    So a VT100, VT220 or other terminal connected to a DECserver can also connect to all the Linux computers on your network. And from the one terminal you can switch between Linux machines and\/or between multiple sessions on the one Linux computer.<\/p>\n

    DECservers work over the LAT protocol. No other network protocols (such as DECnet or TCP\/IP) are required. So another nice thing is that you can connect to a Linux box via a DECserver without knowing its IP address – or even if the Linux box doesn’t have an IP address assigned to it.<\/p>\n

    The LAT protocol does however have two significant limitations:<\/p>\n

      \n
    1. It won’t pass through a router. So the DECserver needs to be connected to the same Ethernet segment as the computers you want to connect to. It will pass through repeaters and hubs just fine though. If you are using say a 4-port router at home to connect to the Internet, you should find that it works fine connected to one port on your router, with the Linux box connected to a different port.<\/li>\n
    2. It generally won’t work over a WiFi connection.\u00a0 Apparently WLAN is not “true Ethernet”. From the little I know about this topic, I gather that the WLAN specification allows WiFi devices to discard (rather than transmit) non-IP packets, in order to avoid unnecessary congestion of the radio link.\u00a0 LAT is a non-IP protocol, and therefore can be discarded. So its best to connect both the DECserver and the target computer to your network over wired Ethernet connections.<\/li>\n<\/ol>\n

      Hooking up the DECserver 200<\/h3>\n

      Connecting up the DECserver is a pretty simple process.\u00a0 Here’s a picture of the rear panel:<\/p>\n

      <\/a><\/p>\n

      We just need to connect 3 cables:<\/p>\n

        \n
      1. Connect the Ethernet port (15-pin AUI conenctor) to your LAN. You’ll need an AUI-to-10baseT converter, The CentreCOM 210T (as shown in the picture) works great.<\/li>\n
      2. Connect Port 1 (the DB25M connector labelled J1) to a terminal or terminal emulator. You’ll need a “null modem” cable to connect each port to a terminal (such as a VT220) or a PC’s serial port. Only 3 wires are needed: TXD, RXD and GND. The TXD and RXD wires need to be “crossed” in the null-modem cable. Port 1 is the only port that shows console messages, such as the boot messages.<\/li>\n
      3. Connect power. There is no power on\/off switch, presumably because a DECserver was intended to be always on.<\/li>\n<\/ol>\n

        The console<\/h3>\n

        With a terminal connected up to Port 1 and the DS connected to a properly configured network, the initial display on the terminal looks like this:<\/p>\n

        Local -901- Initializing DECserver \"08-00-2B-0B-46-B4\" -- ROM BL20, H\/W Rev A.A\nLocal -902- Waiting for image load\nLocal -903- Loading from host \"98-4B-E1-08-85-82\"\nLocal -904- Image load complete<\/pre>\n
        When a DECserver is powered up, it needs to download its firmware from a server on the network. It does this by requesting the file “PR0801ENG.SYS” using the MOP protocol. The dialog above shows us that it succesfully loaded the firmware image from a network host with MAC address 98-4B-E1-08-85-82 (this is an Ubuntu 14.04 system on my LAN).<\/p>\n
        At this point, nothing more will be displayed on the console until you press ENTER twice. Doing so allows the DS to determine the baud rate of your terminal. You will then be greeted by a username prompt. Type in anything you like here – this does not need to be a valid login name on any system. Here’s what you can expect to see:<\/p>\n
        DECserver 200 Terminal Server V3.1 (BL37) - LAT V5.1\n\nPlease type HELP if you need assistance\n\nEnter username> PUTTY\n\nLocal><\/pre>\n
        Showing available services<\/h3>\n
        A DS200 enables terminals plugged in to the Ports of the DECserver to connect to computers or other services (such as printers connected to a DECserver) on the network. Each computer that you can login to broadcasts (on the network) the name of its “service” using the LAT protocol. DECservers listen to these broadcasts and maintain a list of the currently available services.<\/p>\n
        To see the available services we use the SHOW SERVICES command, which can be abbreviated to SHOW SERV:<\/p>\n
        Local> show serv\n\nService Name        Status       Identification\n\nASR33               Available    ASR33 Teletype on Port 8\nLA50                Available    LA50 printer on Port 2\nN36L                Available    Linux 3.2.0-23-generic\nRPI-SD              Available    Linux 4.1.17-v7+\n\nLocal><\/pre>\n
        In the list above we can see two services that are being offered by a DECserver: an ASR33 Teletype and an LA50 printer. We can also see two computers that are offering a login service: N36L is a HP Microserver N36L running Ubuntu 14.04, and RPI-SD is a Raspberry Pi running Raspbian Jessie.<\/p>\n
        Connecting to a service<\/h3>\n
        We can connect to any of these services using the CONNECT command. Here’s an example:<\/p>\n
        Local> CONNECT RPI-SD\nLocal -010- Session 1 to RPI-SD established\n\nrpi-sd login: pi\nPassword:\nLast login: Sun May  8 12:01:46 AEST 2016 on tty1\nLinux rpi-sd 4.1.17-v7+ #838 SMP Tue Feb 9 13:15:09 GMT 2016 armv7l\n\nThe programs included with the Debian GNU\/Linux system are free software;\nthe exact distribution terms for each program are described in the\nindividual files in \/usr\/share\/doc\/*\/copyright.\n\nDebian GNU\/Linux comes with ABSOLUTELY NO WARRANTY, to the extent\npermitted by applicable law.\npi@rpi-sd:~$\n<\/pre>\n
        You can keep the connection open and drop back to the DS200’s “LOCAL>” prompt by forcing the terminal to send a BREAK signal on the RS232 line. On a VT-series terminal with an LK201 keyboard this is done by pressing F5 on the top row of the keyboard. In PUTTY you can do this by pressing CTRL-BREAK.<\/p>\n
        Once back at the “LOCAL>” prompt you can get a list of all your active sessions using the SHOW SESSIONS command:<\/p>\n
        Local> SHOW SESSIONS\nPort 1:  PUTTY               Local Mode    Current Session: 1\n- Session 1: Connected       Interactive   RPI-SD\n\n\nLocal><\/pre>\n
        From here you can open new connections (without disturbing your existing sessions) using the CONNECT command again.<\/p>\n
        You can resume an existing session using the RESUME command. You can use “RESUME” by itself if only one session is active. Otherwise you need to specify the number of the session that you want to resume:<\/p>\n
        Local> RESUME 1\nLocal -012- RPI-SD session 1 resumed\n\n<\/pre>\n
        When you resume a session you won’t see any obvious output from the host system, until you enter text on the keyboard. This is because the host system is unaware that you had temporarily disconnected from it. If you want to permanently disconnect, just issue the appropriate “logout” command on the host system:<\/p>\n
        pi@rpi-sd:~$ logout\n\nLocal -011- Session 1 disconnected from RPI-SD\nLocal><\/pre>\n
        If you were connected to a device (such as a printer) rather than a computer, you can disconnect from the service using the DISCONNECT command:<\/p>\n
        Local> DISCONNECT SESSION 1\nLocal -011- Session 1 disconnected from ASR33\nLocal>\n<\/pre>\n
        Privileged mode<\/h3>\n
        When the DECserver is first powered up you will be using it as an ordinary user. This will enable you to examine and change some DECserver settings (not many) and connect to a computer on your network that is running the LAT protocol. You need to change to “privileged” mode if you want to change other DECserver settings. Once you are in privileged mode you will find that the help screens also show many more options that are not visible to an ordinary user.<\/p>\n
        Here’s how we change to privileged mode (the default password to enter privileged more is SYSTEM):<\/p>\n
        Local> SET PRIV\nPassword>\nLocal><\/pre>\n
        Help<\/h3>\n
        The DS200 has a fairly comprehensive built-in help system. The layout and use of the DECserver help system is very similar to the help system in VMS.<\/p>\n
        Although not a full substitute for the written manuals, you will be able to solve many problems just using the online help.<\/p>\n
        Here’s an example of its use:<\/p>\n
        Local> HELP SET PORT\nDEFINE\/SET PORT\n\nUse DEFINE PORT to change the port characteristics that  take  effect  when  the\nport  is  next  logged in.  Use SET PORT to change the port characteristics that\nyou wish to take effect immediately,  but only stay in effect until port logout.\n\n{DEFINE} PORT [ALL      ] port-characteristic(s)\n{SET   }      [port-list]\n\nALL & port-list           determines whether the command affects all ports\n                          or a specific list of ports.\n\nAdditional HELP is available for the port-characteristics:\n\nACCESS             DEDICATED SERVICE      INTERRUPTS         PREFERED SERVICE\nALTERNATE SPEED    DIALUP                 LIMITED VIEW       QUEUING\nAUTHORIZED GROUPS  DSRLOGOUT              LOCAL SWITCH       REMOTE MODIFICATION\nAUTOBAUD           DTRWAIT                LOSS NOTIFICATION  RING\nAUTOCONNECT        FLOW CONTROL           MESSAGE CODES      SECURITY\nAUTOPROMPT         {INPUT } FLOW CONTROL  MODEM CONTROL      SESSION LIMIT\nBACKWARD SWITCH    {OUTPUT}               MULTISESSIONS      {INPUT } SPEED\nBREAK              FORWARD SWITCH         NAME               {OUTPUT}\n\nEnter <CTRL\/Z> to exit HELP or press  to continue...\nBROADCAST          GROUPS                 ON-DEMAND LOADING  SIGNAL CHECK\nCHARACTER SIZE     INACTIVITY LOGOUT      PARITY             TYPE\n                                          PASSWORD           USERNAME\n\nDEFINE\/SET PORT Subtopic? ACCESS\nDEFINE\/SET PORT ACCESS\n\nUse the ACCESS port characteristic to control connection access to the port.\n\nACCESS {DYNAMIC}\n       {LOCAL  }  *\n       {NONE   }\n       {REMOTE }\n\nDYNAMIC allows a port to alternate between operating as a local access port  and\na remote access port.\n\nLOCAL allows a port user to log in to the DECserver,  initiate  connections  and\nuse the server commands.\n\nNONE disables the port completely.\n\nREMOTE allows the port to be accessed only by remote connection requests.\n\nDEFINE\/SET PORT Subtopic? DEDICATED\nDEFINE\/SET PORT DEDICATED\n\nUse DEDICATED to set up a service  to  which  the  port  automatically  connects\nat port login.  The  port is dedicated to this  service  and  its  users  cannot\nenter any local mode commands.\n\nDEDICATED {service-name} [NODE {node-name}] [DESTINATION {port-name}]\n          {NONE        } [     {NONE     }] [            {NONE     }]\n\nservice-name            is the name of the preferred service\n\nNODE node-name          specifies a service node offering the preferred service\n\nDESTINATION port-name   specifies a port that offers the service\n\nEnter NONE to cancel a previous service-name, node-name, or port-name entry.\n\nDEFINE\/SET PORT Subtopic?\nSET Subtopic?\nTopic?\nLocal><\/pre>\n
        Reverse LAT<\/h3>\n
        A DECserver can also offer (and broadcast) a “service”. This is sometimes referred to as “reverse LAT”<\/p>\n
        Once the DECserver has been configured to offer a service, the name of the service will be broadcast by the DECserver over the network (using the LAT protocol). For example, we could define a service called “ASR33” on Port 8 of our DECserver 200. Once this has been done, it will show up in the list of services (when the SHOW SERV) command is used. Terminal users on this DECserver (or on any other DECserver) will be able to connect to it. And a computer on the network will be able to connect to it by name and use it as a network printer.<\/p>\n
        Local> DEFINE SERVICE ASR33 IDENTIFICATION \"ASR33 Teletype on Port 8\" PORTS 8\nLocal> SET SERVICE ASR33 IDENTIFICATION \"ASR33 Teletype on Port 8\" PORTS 8\nLocal><\/pre>\n
        Let’s use the SHOW SERV command to see the list of available services<\/p>\n
        Local> SHOW SERV\n\nService Name        Status       Identification\n\nASR33               Available    ASR33 Teletype on Port 8\nLA50                Available    LA50 printer on Port 7\nN36L                Available    Linux 3.2.0-23-generic\nRPI-SD              Available    Linux 4.1.17-v7+\n\nLocal><\/pre>\n
        In the above list we can see the “ASR33” service that we’ve just defined. We can also see another service (LA50) that I’ve previously defined for Port 7, as well as the two computers mentioned earlier.<\/p>\n
        We now use the DEF PORT and SET PORT commands to setup port 8 appropriately. The main things we need to do are: (a) set the baud rate to suit the connected device; (2) disable auto-baud detection so that our selected baud rate is used; and (3) set access to “remote” or “dynaic”. The access mode “remote” is appropriate for a device such as a printer) that should not be able to initiate connections through the DECserver. “Dynamic” is appropriate for a device such as an ASR33 that should be accessible remotely (as a printer) but also permitted to initiate a connection to a computer.<\/p>\n
        Local> SET PRIV\nPassword>\nLocal> DEF PORT 8 ACCESS DYNAMIC\nLocal> SET PORT 8 ACCESS DYNAMIC\nLocal> DEF PORT 8 AUTOBAUD DISABLED\nLocal> SET PORT 8 AUTOBAUD DISABLED\nLocal> DEF PORT 8 SPEED 110\nLocal> SET PORT 8 SPEED 110\nLocal><\/pre>\n
        We can now see the new setting using the SHOW PORT command:<\/p>\n
        Local> SHOW PORT 8\n\n\nPort 8:                                Server: DS-TOMAS\n\nCharacter Size:            8           Input Speed:         110\nFlow Control:            XON           Output Speed:        110\nParity:                 None           Modem Control:  Disabled\n\nAccess:              Dynamic           Local Switch:       None\nBackwards Switch:       None           Name:             PORT_8\nBreak:                 Local           Session Limit:         4\nForwards Switch:        None           Type:               Soft\n\nPreferred Service: None\n\nAuthorized Groups:   0\n(Current)  Groups:   0\n\nEnabled Characteristics:\n\nAutoprompt,  Broadcast,  Input Flow Control,  Loss Notification,\nMessage Codes,  Output Flow Control,  Verification\n\nLocal><\/pre>\n
        Note that if we had not disabled autobaud, the word “Autobaud” would have appeared at the start of the list of “Enabled Characteristics” in the above output.<\/p>\n
        You may also want to DEF\/SET “BROADCAST DISABLED” on the port, to stop DECserver broadcast messages from appearing on the printed output of your device.<\/p>\n
        Useful links<\/h3>\n
        Here are some links to relevant material that I discovered when writing this post:<\/p>\n
        DECserver 200MC via Linux<\/a> Focus is mainly on getting mopd to work in Linux. Also discusses using Linux to remotely manage a DECserver.<\/p>\n
        Setting up the mop server, Diskless NetBSD HOW-TO<\/a> Setting up mopd on netBSD, OpenNSD, FreeBSD and Linux.<\/p>\n
        Connecting a DECserver to modern Linux<\/a><\/p>\n
        Ubuntu man page for mopd<\/a> The definitive (but brief) explanation of the Linux mopd service, including command-line switches.<\/p>\n
        Getting a DECserver 200\/MC Working<\/a> Excellent article on setting up VAX\/VMS tobe able to connect in via a DECserver 200<\/p>\n
        DECnet for Linux<\/a> Very helpful guide to some of the more complicated aspects of the LAT driver in Linux<\/p>\n
        An Introduction to the Decserver 200<\/a> Appears to be a hacker’s guide to navigating around and through DECserver VMS systems<\/p>\n
        What is a terminal type or terminal emulation, and how do I set it?<\/a> Some snippets of information about setting the terminal type in Unix and VMS systems<\/p>\n
        Commands to set up a DECserver using DECnet Phase IV MOP<\/a> Guide to setting up VMS systems to serve up DESserver firmware via MOP<\/p>\n
        Where to from here?<\/h3>\n
        In a future post soon, we’ll look at what’s needed to configure a Linux machine (such as a RPi) or a VAX machine to offer a login service over LAT.<\/p>\n","protected":false},"excerpt":{"rendered":"
        What is it? The DECserver 200 is a “terminal server”. It enables up to 8 terminals to login to various DEC computer systems over an Ethernet link. Back in the day a DECserver it was used to connect terminals and printers to DEC systems.\u00a0 Typically these were VAX machines, though some PDP-11 systems also supported ..<\/p>\n
        <\/div>\n
        Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[1],"tags":[],"class_list":["post-137","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p7xTsk-2d","jetpack-related-posts":[{"id":1285,"url":"https:\/\/avitech.com.au\/?p=1285","url_meta":{"origin":137,"position":0},"title":"[Outdated post] Vintage computers for sale or swap","author":"malcolm","date":"13-October-2016","format":false,"excerpt":"15-May-2021: Note this is a very old post - most of the items below are no longer available. It's time to thin out my vintage computer collection a little. Below is a list of items currently available. My order of priority for finding new homes for this equipment is as\u2026","rel":"","context":"With 40 comments","block_context":{"text":"With 40 comments","link":"https:\/\/avitech.com.au\/?p=1285#comments"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/factory-20151007-143900-Medium.jpg?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/factory-20151007-143900-Medium.jpg?resize=350%2C200 1x, https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/factory-20151007-143900-Medium.jpg?resize=525%2C300 1.5x, https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/factory-20151007-143900-Medium.jpg?resize=700%2C400 2x, https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/factory-20151007-143900-Medium.jpg?resize=1050%2C600 3x"},"classes":[]},{"id":285,"url":"https:\/\/avitech.com.au\/?p=285","url_meta":{"origin":137,"position":1},"title":"DECnet Level 2 routing","author":"malcolm","date":"3-May-2016","format":false,"excerpt":"I have a few VAX\/VMS DECnet machines with node addresses in Area 4. Their full DECnet node addresses are 4.200, 4.202, etc.\u00a0 When I connect a DECnet machine in Area 33 (full address 33.13) to the same Ethernet segment, each of the Area 4 machines can see each other over\u2026","rel":"","context":"In "DECnet"","block_context":{"text":"DECnet","link":"https:\/\/avitech.com.au\/?cat=3"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":252,"url":"https:\/\/avitech.com.au\/?p=252","url_meta":{"origin":137,"position":2},"title":"VT220 current loop interface","author":"malcolm","date":"14-May-2016","format":false,"excerpt":"This post takes a brief look at the current loop connectors used by DEC. The main focus of this post is the cabling needed to connect a VT220 terminal to a computer (such as a PDP-11\/10) using the 20mA current loop interface. DEC's standard connector DEC used an 8-pin Mate-N-Lok\u2026","rel":"","context":"In "Current loop"","block_context":{"text":"Current loop","link":"https:\/\/avitech.com.au\/?cat=10"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/conn-male-top.jpg?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/conn-male-top.jpg?resize=350%2C200 1x, https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/conn-male-top.jpg?resize=525%2C300 1.5x, https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/conn-male-top.jpg?resize=700%2C400 2x, https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/conn-male-top.jpg?resize=1050%2C600 3x"},"classes":[]},{"id":334,"url":"https:\/\/avitech.com.au\/?p=334","url_meta":{"origin":137,"position":3},"title":"Garage Sale on Sat 28-May-2016","author":"mmacleod@iinet.net.au","date":"20-May-2016","format":false,"excerpt":"I'm having a garage sale on Saturday 28 May 2016 to thin out my vintage computer collection a little. Everything put out for sale will be $5 to $20 per item - including large VAX machines. The items available include those shown below (and many more): The items include, for\u2026","rel":"","context":"Similar post","block_context":{"text":"Similar post","link":""},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/20160519_173658_resized-e1463733391540.jpg?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/20160519_173658_resized-e1463733391540.jpg?resize=350%2C200 1x, https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/20160519_173658_resized-e1463733391540.jpg?resize=525%2C300 1.5x, https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/20160519_173658_resized-e1463733391540.jpg?resize=700%2C400 2x, https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/05\/20160519_173658_resized-e1463733391540.jpg?resize=1050%2C600 3x"},"classes":[]},{"id":1413,"url":"https:\/\/avitech.com.au\/?p=1413","url_meta":{"origin":137,"position":4},"title":"New neon indicator for DEC 871B Power Controller","author":"malcolm","date":"26-December-2016","format":false,"excerpt":"The 871B Power Controller is a single-phase 240VAC power controller found in some PDP-11 systems. It has 6 switched power sockets. One of my holiday projects was to replace the faulty neon indicator in this Power Controller. I have just posted a short webpage with some information about this repair,\u2026","rel":"","context":"In "DEC"","block_context":{"text":"DEC","link":"https:\/\/avitech.com.au\/?cat=2"},"img":{"alt_text":"","src":"https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/12\/20161226_105815-Large-300x169.jpg?resize=350%2C200","width":350,"height":200},"classes":[]},{"id":605,"url":"https:\/\/avitech.com.au\/?p=605","url_meta":{"origin":137,"position":5},"title":"Imaging DEC VAX\/VMS CDs","author":"malcolm","date":"10-June-2016","format":false,"excerpt":"I have some original VMS CDROMs. I was looking for a way to image these (for use with SIMH) and also a way to write ISO images back to blank CDs, to use on real hardware. This should be a fairly simple process using a modern Linux computer and the\u2026","rel":"","context":"In "VMS"","block_context":{"text":"VMS","link":"https:\/\/avitech.com.au\/?cat=5"},"img":{"alt_text":"vaxvms061cd","src":"https:\/\/i0.wp.com\/avitech.com.au\/wp-content\/uploads\/2016\/06\/vaxvms061cd-300x300.jpg?resize=350%2C200","width":350,"height":200},"classes":[]}],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/avitech.com.au\/index.php?rest_route=\/wp\/v2\/posts\/137","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/avitech.com.au\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/avitech.com.au\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/avitech.com.au\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/avitech.com.au\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=137"}],"version-history":[{"count":0,"href":"https:\/\/avitech.com.au\/index.php?rest_route=\/wp\/v2\/posts\/137\/revisions"}],"wp:attachment":[{"href":"https:\/\/avitech.com.au\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=137"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/avitech.com.au\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=137"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/avitech.com.au\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=137"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}