From: atindra@mindspring.com (Atindra Chaturvedi)
Subject: [TUHS] Happy birthday, PDP-8!
Date: Tue, 21 Mar 2017 19:57:51 -0400 (GMT-04:00) [thread overview]
Message-ID: <27014037.20741.1490140671733@mswamui-swiss.atl.sa.earthlink.net> (raw)
Brings back memories...
Back in early 1981 I worked for a shipping line in Cranford NJ in their IT department. The company had just ordered 4 new super-wide cargo ships that just fit the Panama Canal and the Chief Marine Architect came to the IT department to ask for assistance in programming a PDP-8 to write a load distribution check program so that the ship would not keel over, or break in the middle - when being loaded 12 stack high containers. Had to take into account stress and strain - mathematical algorithms. My boss called me in to talk to him and he asked " if I knew how to determine the area under a curve..." - I knew my engineering math - Simpson's rule and also FORTRAN IV and was immediately drafted. What was needed also was a graphical way of entering the data, and displaying the results optionally graphically on the screen (tty ?). My friend Wayne Rawls knew BASIC - he wrote the front end - passed me the input on a large floppy - my FORTRAN IV program ran and did the stress/strain analysis for the ship - and I passed the output back to him on the floppy that he then displayed on-screen.
A lot of grinding of the floppy drives for the FORTRAN compiler - no spinning hard disks as the PDP-8 would be installed on-board ship - and in those days of A/C computer rooms would be a non-starter.
It all worked well - Wayne took the PDP-8 on a ship to Norfolk to get it checked out and the company used it for many years !
Atindra.
-----Original Message-----
>From: Dave Horsfall <dave at horsfall.org>
>Sent: Mar 21, 2017 5:34 PM
>To: The Eunuchs Hysterical Society <tuhs at tuhs.org>
>Subject: [TUHS] Happy birthday, PDP-8!
>
>OT, but of interest to a few people here :-)
>
>The venerable PDP-8 was introduced in 1965 today (or tomorrow if you're on
>the wrong side of the date line). It was the first computer I ever
>used, back around 1970 (I think I'd just left school and was checking out
>the local University's computer department, with a view to majoring in
>Computer Science (which I did)).
>
>--
>Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
next reply other threads:[~2017-03-21 23:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 23:57 Atindra Chaturvedi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-21 21:52 Dave Horsfall
2018-03-21 21:59 ` George Michaelson
[not found] <mailman.659.1490686648.3779.tuhs@minnie.tuhs.org>
2017-03-28 22:10 ` Johnny Billquist
2017-03-28 2:38 Noel Chiappa
[not found] <mailman.1.1490580001.4973.tuhs@minnie.tuhs.org>
2017-03-27 23:30 ` Johnny Billquist
2017-03-27 23:33 ` Steve Nickolas
2017-03-27 23:49 ` Johnny Billquist
2017-03-27 1:24 Noel Chiappa
2017-03-27 14:07 ` Arthur Krewat
2017-03-27 0:31 Noel Chiappa
2017-03-27 0:37 ` Arthur Krewat
2017-03-27 12:05 ` Tim Bradshaw
2017-03-27 13:35 ` Tony Finch
2017-03-27 21:37 ` Terry Smith
2017-03-21 21:34 Dave Horsfall
2017-03-22 16:34 ` Ron Natalie
2017-03-26 19:49 ` Dave Horsfall
2017-03-26 20:11 ` Paul Winalski
2017-03-26 22:20 ` Greg 'groggy' Lehey
2017-03-26 22:25 ` Greg 'groggy' Lehey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27014037.20741.1490140671733@mswamui-swiss.atl.sa.earthlink.net \
--to=atindra@mindspring.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).