18 Mar
2013
18 Mar
'13
12:07 a.m.
A friend sent me a list today of documents he has, wondering if they are of
interest to classic computer folk. Most of these categories are outside my
expertise, so I'm asking here if these should get archived, and if so who
volunteers to do it :-).
Here's the list:
Control Data 6000 Series manuals
=====================================================
Kronos 2.1 Instant Manual
Control Data Cyber 70 Series Models 72/73/74 6000 Series Computer
Systems
Kronos 2.1 Terminal User's Instant Manual
Control Data Cyber 70 Series Models 72/73/74 6000 Series Computer
Systems
Small (6.5" x 4") "pocket" manuals for operating the Kronos OS
original printing dated 10/1973
Algol Generic Reference Manual
Control Data 3000/6000
Revision A, 5/31/1968
Modify Reference Manual
Control Data Cyber 170, Cyber 70, 6000 Series and 7600 computer systems
Card based version control
Revision E, 10/1/1974
APL*Cyber Reference Manual
Control Data Cyber 170, Cyber 70, 6000 Series and 7600 computer systems
Revision C, August 1974
Oregon State Open Shop Operating System (OS3)
====================================================
Assembly listing of OS3 operating system dated September 1974
Assembly language listing of core operating system.
OS3 was a demand-paged, virtual memory, multi-user operating system
that used a PDP8 as a front end to multiplex many teletypes scattered
around the Oregon State campus.
OS-3 Reference Manual for OS-3 Version 4.3
July 1973
OSU: Grope User's Manual
January 1972
"Grope" (Graphical Representation of Parameterized Expressions) was an
input and graphing system running on OS-3 and a Tektronix 4002A
terminal.
Grafit User Notes
February 1973
Jeff Ballance, Jo Ann Baughman, Larry Hubble
"The GRAFIT system is an interactive program for displaying data on the
Tektronix terminal and/or the Calcomp plotter or on a Hewlett-Packard
teletype compatible X-Y plotter and/or the Calcomp plotter."
Various OSU computer center manual on editing tools
Useful Features of OS-3
James S. Sasser
August 1974
Primer for Users of Oregon State's Open Shop Operating System (OS-3)
September 1972
A Brief Description of OSCAR (Third Revision)(Describes Version 56)
Joel Davis, Gilbert A. Bachelor
September 1969
"OSCAR" (Oregon State Conversational Aid to Research) is an
arithmetical interpreter for use at remote teletype or CRT connections
to the CDC 3300."
OSCAR: A User's Manual with Examples (revised September 1969)
Jo Ann Baughman, Mary Lynn Berryman, Joel Davis
September, 1969
MISC
====================================================
Concurrent Pascal - Introduction
Per Brinch Hansen
Concurrent Pascal Machine
Per Brinch Hansen
Concurrent Pascal Report
Per Brinch Hansen
Sequential Pascal Report
Per Brinch Hansen
Alfred C. Hartmann
Information Science California Institute of Technology
7"x10" manuals published in July 1975
Laural Manual
Douglas K. Brotz
Palo Alto Research Center
"Laural is an Alto-based, display-oriented, computer mail system
interface."
published May 1981
Sail
Stanford Artificial Intelligence Laboratory
Memo AIM-289, Report STAN-CS-76-578
edited by John F. Reiser
August 1976
"Sail is a high-level programming language for the PDP-10 computer. It
includes
an extended ALGOL 60 compiler and a companion set of execution-time
routines. In
addition to ALGOL, the language features: (1) flexible linking to
hard-coded machine
language algorithms, (2) complete access to the PDP-10 I/O facilities,
(3) a complete
system of compile-time arithmetic and logic as well as a flexible macro
system, (4) a
high-level debugger, (5) records and references, (6) sets and lists,
(7) an associative
data structure, (8) independent processes, (0) procedure
varaiables(sic), (10) user
modifiable error handling, (11) backtracking, and (12) interrupt
facilities."
various UNIX 'man' printouts and misc manuals.
Things like:
Berkeley Font Catalog (October 1980)
Typesetting Mathematics -- User's Guide (Second Edition)
Brian W. Kerninghan and Lorinda L. Cherry
Bell Laboratories, August 1978
Typing Documents on the UNIX System: Using the -ms Macros with Troff
and Nroff
M.E. Lesk
Bell Laboratories, May 1982
... many more UNIX Nroff and Troff manuals
ba.uuYumYum (March 1986)
a dining guide compiled from reviews public in group ba.general
--
o< The ASCII Ribbon Campaign Against HTML Email!
18 Mar
18 Mar
10:16 a.m.
Al Kossow who runs bitsavers.org seems to be your best bet. He is a
saint for doing this, from my experiences, he is extremely busy with a
huge backlog of donated manuals to scan/archive. I also have lots of
unneeded manuals and I am honestly little reluctant sending him
anything as Im afraid they would just sit and never get scanned. I
wish there were more folks out there with fancy document scanners to
do the grunt work of scanning documents for Al. I am sure I am not
alone here. A whole army of scanners is probably whats needed!
On Mon, Mar 18, 2013 at 12:07 AM, Vincent Slyngstad
<v.slyngstad at frontier.com> wrote:
A friend sent me a list today of documents he has,
wondering if they are of
interest to classic computer folk. Most of these categories are outside my
expertise, so I'm asking here if these should get archived, and if so who
volunteers to do it :-).
Here's the list:
Control Data 6000 Series manuals
=====================================================
Kronos 2.1 Instant Manual
Control Data Cyber 70 Series Models 72/73/74 6000 Series Computer
Systems
Kronos 2.1 Terminal User's Instant Manual
Control Data Cyber 70 Series Models 72/73/74 6000 Series Computer
Systems
Small (6.5" x 4") "pocket" manuals for operating the Kronos OS
original printing dated 10/1973
Algol Generic Reference Manual
Control Data 3000/6000
Revision A, 5/31/1968
Modify Reference Manual
Control Data Cyber 170, Cyber 70, 6000 Series and 7600 computer systems
Card based version control
Revision E, 10/1/1974
APL*Cyber Reference Manual
Control Data Cyber 170, Cyber 70, 6000 Series and 7600 computer systems
Revision C, August 1974
Oregon State Open Shop Operating System (OS3)
====================================================
Assembly listing of OS3 operating system dated September 1974
Assembly language listing of core operating system.
OS3 was a demand-paged, virtual memory, multi-user operating system
that used a PDP8 as a front end to multiplex many teletypes scattered
around the Oregon State campus.
OS-3 Reference Manual for OS-3 Version 4.3
July 1973
OSU: Grope User's Manual
January 1972
"Grope" (Graphical Representation of Parameterized Expressions) was an
input and graphing system running on OS-3 and a Tektronix 4002A
terminal.
Grafit User Notes
February 1973
Jeff Ballance, Jo Ann Baughman, Larry Hubble
"The GRAFIT system is an interactive program for displaying data on the
Tektronix terminal and/or the Calcomp plotter or on a Hewlett-Packard
teletype compatible X-Y plotter and/or the Calcomp plotter."
Various OSU computer center manual on editing tools
Useful Features of OS-3
James S. Sasser
August 1974
Primer for Users of Oregon State's Open Shop Operating System (OS-3)
September 1972
A Brief Description of OSCAR (Third Revision)(Describes Version 56)
Joel Davis, Gilbert A. Bachelor
September 1969
"OSCAR" (Oregon State Conversational Aid to Research) is an
arithmetical interpreter for use at remote teletype or CRT connections
to the CDC 3300."
OSCAR: A User's Manual with Examples (revised September 1969)
Jo Ann Baughman, Mary Lynn Berryman, Joel Davis
September, 1969
MISC
====================================================
Concurrent Pascal - Introduction
Per Brinch Hansen
Concurrent Pascal Machine
Per Brinch Hansen
Concurrent Pascal Report
Per Brinch Hansen
Sequential Pascal Report
Per Brinch Hansen
Alfred C. Hartmann
Information Science California Institute of Technology
7"x10" manuals published in July 1975
Laural Manual
Douglas K. Brotz
Palo Alto Research Center
"Laural is an Alto-based, display-oriented, computer mail system
interface."
published May 1981
Sail
Stanford Artificial Intelligence Laboratory
Memo AIM-289, Report STAN-CS-76-578
edited by John F. Reiser
August 1976
"Sail is a high-level programming language for the PDP-10 computer. It
includes
an extended ALGOL 60 compiler and a companion set of execution-time
routines. In
addition to ALGOL, the language features: (1) flexible linking to
hard-coded machine
language algorithms, (2) complete access to the PDP-10 I/O facilities,
(3) a complete
system of compile-time arithmetic and logic as well as a flexible macro
system, (4) a
high-level debugger, (5) records and references, (6) sets and lists,
(7) an associative
data structure, (8) independent processes, (0) procedure
varaiables(sic), (10) user
modifiable error handling, (11) backtracking, and (12) interrupt
facilities."
various UNIX 'man' printouts and misc manuals.
Things like:
Berkeley Font Catalog (October 1980)
Typesetting Mathematics -- User's Guide (Second Edition)
Brian W. Kerninghan and Lorinda L. Cherry
Bell Laboratories, August 1978
Typing Documents on the UNIX System: Using the -ms Macros with Troff
and Nroff
M.E. Lesk
Bell Laboratories, May 1982
... many more UNIX Nroff and Troff manuals
ba.uuYumYum (March 1986)
a dining guide compiled from reviews public in group ba.general
--
o< The ASCII Ribbon Campaign Against HTML Email!
1:40 p.m.
On 3/18/13 10:16 AM, Kurt Nowak wrote:
Al Kossow who runs bitsavers.org seems to be your best
bet.
I sent a msg saying that I was interested.
1:46 p.m.
In article <CA+tCPu812ZmiZ2Dp-rJinv90PkcJuy4pAivH7TT_b3da-0z+hw at mail.gmail.com>,
Kurt Nowak <knowak at alumni.calpoly.edu> writes:
Al Kossow who runs bitsavers.org seems to be your best
bet. He is a
saint for doing this, from my experiences, he is extremely busy with a
huge backlog of donated manuals to scan/archive. I also have lots of
unneeded manuals and I am honestly little reluctant sending him
anything as Im afraid they would just sit and never get scanned. I
wish there were more folks out there with fancy document scanners to
do the grunt work of scanning documents for Al. I am sure I am not
alone here. A whole army of scanners is probably whats needed!
I help out Al by offloading scanning for him when I can. I do lots of
scanning for bitsavers. I am happy to have other cctalk members send
me documents for scanning. For instance I recently scanned a bunch of
Stardent documentation: <http://manx.classiccmp.org/search.php?cp=126&q=>
I have access to a nice 600dpi optical sheet feed scanner at work that
makes quick work of most things. Stuff that is in 3-ring binders or
loose sheets works best. Stuff that is spiral bound is the next
easiest to scan and stuff that is glue or sewn bound is the most
amount of work.
I tend to scan stuff that is of interest to me personally, so that
means that terminals and graphics items tend to go to the head of the
queue for me.
--
"The Direct3D Graphics Pipeline" free book
<http://tinyurl.com/d3d-pipeline>
The Computer Graphics Museum <http://computergraphicsmuseum.org>
The Terminals Wiki <http://terminals.classiccmp.org>
Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
19 Mar
19 Mar
9:03 a.m.
New subject: Scanning Requirements was Re: Old manuals -- Need archiving?
Hi Richard (and Al) -?
If one had the capability and interest in submitting scanned images is there any
particular format, meta-data or other criteria that would be helpful?
?
Lee Courtney
________________________________
From: Richard <legalize at xmission.com>
To: cctalk <cctalk at classiccmp.org>
Sent: Monday, March 18, 2013 1:46 PM
Subject: Re: Old manuals -- Need archiving?
In article <CA+tCPu812ZmiZ2Dp-rJinv90PkcJuy4pAivH7TT_b3da-0z+hw at mail.gmail.com>,
? ? Kurt Nowak <knowak at alumni.calpoly.edu> writes:
Al Kossow who runs bitsavers.org seems to be your best
bet. He is a
saint for doing this, from my experiences, he is extremely busy with a
huge backlog of donated manuals to scan/archive. I also have lots of
unneeded manuals and I am honestly little reluctant sending him
anything as Im afraid they would just sit and never get scanned. I
wish there were more folks out there with fancy document scanners to
do the grunt work of scanning documents for Al. I am sure I am not
alone here. A whole army of scanners is probably whats needed!
I help out Al by offloading scanning for him when I can.? I do lots of
scanning for bitsavers.? I am happy to have other cctalk members send
me documents for scanning.? For instance I recently scanned a bunch of
Stardent documentation: <http://manx.classiccmp.org/search.php?cp=126&q=>
I have access to a nice 600dpi optical sheet feed scanner at work that
makes quick work of most things.? Stuff that is in 3-ring binders or
loose sheets works best.? Stuff that is spiral bound is the next
easiest to scan and stuff that is glue or sewn bound is the most
amount of work.
I tend to scan stuff that is of interest to me personally, so that
means that terminals and graphics items tend to go to the head of the
queue for me.
--
"The Direct3D Graphics Pipeline" free book
<http://tinyurl.com/d3d-pipeline>
? ? The Computer Graphics Museum <http://computergraphicsmuseum.org>
? ? ? ? The Terminals Wiki <http://terminals.classiccmp.org>
? Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>
18 Mar
18 Mar
11:25 a.m.
On 03/18/2013 12:07 AM, Vincent Slyngstad wrote:
A friend sent me a list today of documents he has,
wondering if they are
of interest to classic computer folk. Most of these categories are
outside my expertise, so I'm asking here if these should get archived,
and if so who volunteers to do it :-).
I'm certain that Al K. will be interested in those not already on bitsavers.
CDC "Modify" is a great illustration of what happens when a company
allows regional rivalries cam suck the life out of development budgets.
MODIFY was a CVS-type utility that exactly paralleled (and probably
was a derivative of) the UPDATE utility. MODIFY was used by MACE/KRONOS
people and UPDATE was used by SCOPE/NOSBE people. UPDATE and SCOPE were
pretty much West Coast products and KRONOS/MACE were east-of-the-Rockies
projects.
SCOPE is a descendant of the old Chipppewa OS and MACE/KRONOS was a
product bootlegged by Greg Mansfield and Dave Callender of the CDC Arden
Hills (MN) ops. "MACE" is an acronym for "Mansfield's Answer for
Customer Engineering". I'd met Dave Callender (whose real interest was
bats and knew Greg Mansfield quite well (he eventually ended up at
Cray). Both thought that they had a good idea and found it easier to
bootleg a compatible (to SCOPE) product than convince the administration
that they had a better way.
Eventually, this lead to a rivalry, then an attempt to merge the two
(largely compatible) OS projects, costing thousands of man-hours and a
two-culture dichotomy in program development. I can't help but think
that this hurt CDC greatly.
--Chuck
4249
days inactive
4250
days old
5 comments
6 participants
participants (6)
-
aek＠bitsavers.org -
cclist＠sydex.com -
charlesleecourtney＠yahoo.com -
knowak＠alumni.calpoly.edu -
legalize＠xmission.com -
v.slyngstad＠frontier.com