Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: segaloco <segaloco@protonmail.com>,
	Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: Original print of V7 manual? / My own version of troff
Date: Wed, 10 Jan 2024 12:26:02 -0500	[thread overview]
Message-ID: <CAC20D2MBtfBhJb_asSfRwu2h73uhX_NkT6Zosh3OugF=nkTWZQ@mail.gmail.com> (raw)
In-Reply-To: <7wv881tzt9.fsf@junk.nocrew.org>

[-- Attachment #1: Type: text/plain, Size: 3134 bytes --]

Rich Salz reminded me of the name of the system I was thinking of -- Atex.
Given my later interactions with their editorial and IT departments, I'm
not sure that Carnex was in the production system there (particularly given
the Gunkies description).  I never saw it but it could have been before
anyone I knew was working there.   By the mid/late 80's, they were using
Atex for most things.

FWIW: By the mid/late 1980s, the IBM PC had been out for a few years, and
many people had access to DOS systems.  At the Globe, their Atex System had
a 300-baud modem on it (and it was 300 baud, not 1200 because the IT folks
at the Globe claimed that the Atex required something special about that
model modem -- I never knew what -- I've always guessed it was something to
do with the maintenance contract not technical but it was not my job -- I
just took it as a wonderment and dealt with it).

But the big feature Atex offered the Globe was it allowed the reporters
to upload and spool their stories, and then the Atex set the type for the
editors independent of the filing. But the reporters had to file their
story using a very rigid format convention that they all hated (*i.e.*, ask
humans to conform to the needs of the computer, not the other way round).
By then, most of the reporters used a PC and a simple word processor to
edit and then upload to Atex via a terminal emulator program such as
ProComm or Kermit.

The Atex side was exceedingly dumb and unforgiving.  If the user or the
system made any error, Atex would toss the story (*i.e.,* not put anything
in the spool), and there was no communications protection so that line
noise could cause issues. I never saw their side, but I gather Atex was not
too friendly to the editors,  as there was no way to find out what had been
accepted remotely, so they often had to ask the reporters to file the
stories multiple times.

My sister was working as an occasional stringer for them, given her
statehouse connections.  I got her to get me the specs for the Atex
input system, and I wrote some scripts for her to use the Masscomp box to
prep her stories for them and send them off to the Atex System.   I became
an informal help desk for several of her reporter and photographer friends.
:-)   I have some interesting stories WRT to all that - but they are not
particularly computer-based -- the Richard Reed (the shoe bomber) story and
its famous picture you have all undoubtedly seen is one of my favorites.

Clem


ᐧ

On Wed, Jan 10, 2024 at 2:25 AM Lars Brinkhoff <lars@nocrew.org> wrote:

> Clem Cole <clemc@ccc.com> writes:
> > The software varied greatly, depending on the target customer.   For
> > instance, by the early 80s,  the Boston Globe's input system was still
> > terrible - even though the computers had gotten better.  I had a couple
> of
> > friends working there, and they used to b*tch about it.
>
> Here's something about Camex used at Boston Globe.
> https://gunkies.org/wiki/Camexec
>
> Any comments or additions to this?
>
> I occasionally bug Speciner about scanning his printouts.
>

[-- Attachment #2: Type: text/html, Size: 4942 bytes --]

      reply	other threads:[~2024-01-10 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240108032428.co3ozmlneoop6sa2@illithid>
     [not found] ` <20240108051049.7643537404E9@freecalypso.org>
     [not found]   ` <20240108071109.ykg42tw2gjeacs5f@illithid>
     [not found]     ` <20240109093851.2A29737401E3@freecalypso.org>
     [not found]       ` <c9cfe3f4-7751-6e83-113e-734c99de818e@bitsavers.org>
     [not found]         ` <Zc86g8c-4HH_VPOa1hRm9KY-41ZzzYnSgir_adjejDy6GrsCxHTb9qwocryL7PTLaPK-e4Feso6SOaaLhzn0UfNRQVX2sD596N1CM7uepjU=@protonmail.com>
2024-01-09 22:07           ` Clem Cole
2024-01-10  7:25             ` Lars Brinkhoff
2024-01-10 17:26               ` Clem Cole [this message]

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='CAC20D2MBtfBhJb_asSfRwu2h73uhX_NkT6Zosh3OugF=nkTWZQ@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=coff@tuhs.org \
    --cc=lars@nocrew.org \
    --cc=segaloco@protonmail.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).