From eeb9cf88247ebcac8fbacd8ecf8a83a712987e1e Mon Sep 17 00:00:00 2001 From: Paul Kimpel Date: Sat, 4 Apr 2015 09:54:05 -0700 Subject: [PATCH] Reconstruct Google Code wiki history from r377 on 2013-11-23. --- WebUIHowToSetUpCANDE.wiki | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/WebUIHowToSetUpCANDE.wiki b/WebUIHowToSetUpCANDE.wiki index 6cbb521..c3cea8c 100644 --- a/WebUIHowToSetUpCANDE.wiki +++ b/WebUIHowToSetUpCANDE.wiki @@ -9,11 +9,11 @@ = Introduction = -This page describes how to the timesharing features to an existing emulator environment for the Burroughs B5500 system. At the end is a short sample session using CANDE. +This page describes how to setup the timesharing features to an existing emulator environment for the Burroughs B5500 system. At the end is a short sample session using [http://en.wikipedia.org/wiki/CANDE CANDE] (Command AND Edit - a command line shell and text editor for MCP). == Prerequisites == -The procedure described below assumes you have the retro-B5500 emulator installed and set up with the default DCMCP (Datacom MCP) software as described in [WebUIGettingStarted WebUI Getting Started]. +The procedure described below assumes you have the retro-B5500 emulator installed and set up with the default DCMCP (DataCom MCP) software as described in [WebUIGettingStarted WebUI Getting Started]. Before proceeding, you should have a basic familiarity with the emulator, SPO, card reader, and tape drive. See the following pages for information these topics: @@ -28,7 +28,7 @@ There were several variations of the MCP (Master Control Program) operating syst The B5500, first available in early 1965, was essentially the same system, but with the addition of a new Head-per-Track disk subsystem. HPT disk offered capacities up to one billion 6-bit characters. The MCP was completely rewritten to take advantage of this new disk, becoming known as the Disk File MCP (DFMCP). -Data communications interface hardware became available for the B5500 shortly after the DFMCP was released. The most commonly-used interface was the B249 Data Transmission Control Unit DTCU) paired with one or more B487 Data Transmission Terminal Units (DTTU). Each DTTU could support up to 16 line-adapter slots. Each adapter supported one data communications circuit. Later a programmable interface, the Data Communications Processor (DCP), originally developed for the B6500 project, became available on the B5500. The B5500 was then renamed for marketing purposes as the B5700. +Data communications interface hardware became available for the B5500 shortly after the DFMCP was released. The most commonly-used interface was the B249 DTCU (Data Transmission Control Unit) paired with one or more B487 Data Transmission Terminal Units (DTTU). Each DTTU could support up to 16 line-adapter slots. Each adapter supported one data communications circuit. Later a programmable interface, the Data Communications Processor (DCP), originally developed for the B6500 project, became available on the B5500. The B5500 was then renamed for marketing purposes as the B5700. The DFMCP was enhanced to support this datacom equipment, becoming the Data Communications MCP (DCMCP). Its capabilities were oriented towards transaction processing, where multiple remote stations exchanged messages with one or more central server programs, rather than interactive timesharing. @@ -42,7 +42,7 @@ Core memory for the TSMCP is divided into two portions at a site-specified locat Memory above the fence is organized into a number of "swap areas" for use by the interactive programs initiated by remote users. Code and data segments for these programs are allocated solely within their respective swap areas. This supported the "time slicing" of memory for interactive programs, as all of the non-shared memory used by an interactive program was in its swap area, and could be paged out to disk as a unit, making room for the swap areas of other users to be paged in for their time slice. -To manage remote interactive sessions, Burroughs developed the Command and Edit (CANDE) handler. This was a command-line interface somewhat like what we would call a shell today, but with a line-oriented file editor built in. Most terminal devices of the day were teletype-like devices, which could only support line editing. Full-screen editing was something still in the future. +To manage remote interactive sessions, Burroughs developed the Command AND Edit (CANDE) handler. This was a command-line interface somewhat like what we would call a shell today, but with a line-oriented file editor built in. Most terminal devices of the day were teletype-like devices, which could only support line editing. Full-screen editing was something still in the future. With CANDE, users could create and edit source and text files, compile programs, and run programs, interacting with the programs through so-called "remote files." CANDE also supported commands to rename and delete files, list files to the terminal, copy files to line printer and card punch devices, and manage their interactive session. A basic security system isolated each user's files from other users. The owner could specify permissions that allowed other users to share individual files.