Computer Old Farts Forum
 help / color / mirror / Atom feed
From: grog at lemis.com (Greg 'groggy' Lehey)
Subject: [COFF] Daisy wheel printers (was: [TUHS] The Elements Of Style: UNIX As Literature)
Date: Tue, 10 Nov 2020 11:48:03 +1100	[thread overview]
Message-ID: <20201110004803.GQ99027@eureka.lemis.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2011100851280.48674@aneurin.horsfall.org>

On Tuesday, 10 November 2020 at  9:08:44 +1100, Dave Horsfall wrote:
> On Mon, 9 Nov 2020, Greg 'groggy' Lehey wrote:
>
>> The Qume printers seemed to have been the best round 1980 when we used
>> them in our applications.  In particular, a large choice of wheels and
>> fine-grained spacing.  I forget how the spacing worked.
>
> Presumably some sort of a table lookup, based on which character is about
> to be hit?  Or are you referring to the micro-spacing itself?

"Yes".  As I said, I forget.  I have a feeling that it must have been
explicit micro-spacing, since the machine didn't know anything about
the kind of daisy wheel that was fitted.

>> The golfball console for the /360 was much earlier than that, like the
>> /360 itself.  The model numbers I recall were 735, and the newer
>> generation 2731/2735.  The last digit related to the carriage width
>> (11"/15").
>
> I once had a fine collection of goofballs (as we called them); sadly lost
> in a house move :-(

I was going to say "ditto", but I think I actually sold them along
with the 735.

>> Round the time in question I bought a second-hand 735 machine.  It had
>> an arcane interface that directly talked to the magnets.  I built an
>> interface for it to a parallel port [...]
>
> I'd like to know a bit more about that interface...  You'd have to
> control the carriage, roller, swivel/tilt/hit etc.

Yes, I'm trying to recall that too.  The ball itself was controlled by
6 signals: Up 1, up 2 (for the 4 rows of characters), left 1, left 2,
left 2 (yes, twice) and right 5, for a total of 11 columns.  But my
recollection was that I only had about 10 power transistors driving
the thing.  I wish I had kept more details.  Maybe there's something
amongst the useless junk in the shed.

> How did you detect the BREAK key to get the 360's attention and
> unlock the keyboard?

I didn't.  The 735 doesn't have a BREAK key.  It was a typewriter, not
a teletype.  I used it as a printer in addition to a normal glass TTY.

Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20201110/7bec0f8e/attachment.sig>


  reply	other threads:[~2020-11-10  0:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEuQd1AWs=jpHYk3nGpKsBV=qF4DZVXvXzynSeDK5S-r-hfryw@mail.gmail.com>
     [not found] ` <20201106014109.GP26296@mcvoy.com>
     [not found]   ` <CAD2gp_Q-wTvG2cAW5goJFYW3A6qF9zOuTh=Y4Kahh0nLBtof2Q@mail.gmail.com>
     [not found]     ` <20201106063725.GB99027@eureka.lemis.com>
     [not found]       ` <5BE1CBD5-C9EB-45D4-B135-E58BCCCBE38C@gmail.com>
     [not found]         ` <3c54b19d-e604-68eb-2b4b-0b65e9cfb896@earthlink.net>
2020-11-06 17:56           ` [COFF] [TUHS] The Elements Of Style: UNIX As Literature clemc
     [not found]       ` <20201106150609.GR26296@mcvoy.com>
     [not found]         ` <CALMnNGg=9KHCwqaqdFESBQr=Ru_qzM=x-S2fc=ewgJNf2zLRFQ@mail.gmail.com>
     [not found]           ` <20201106222302.GG26411@mcvoy.com>
2020-11-07  0:16             ` dave
     [not found]     ` <CAKzdPgx1Ptu=sahO3o5KYS-A=vnfXK-hs=QeVwO_Vd1cFfaeqw@mail.gmail.com>
     [not found]       ` <a588c934-e403-2a4e-4701-669b8c14e989@gmail.com>
     [not found]         ` <CAC20D2PPw3Ua3-VpMYjh=NaC09=9Q528kqEvE7SvmO3Ly2JO0A@mail.gmail.com>
     [not found]           ` <175409f6-af94-601e-3db3-a5af5d7f64d0@gmail.com>
2020-11-06 15:53             ` clemc
2020-11-06 19:22               ` tytso
2020-11-06 19:24                 ` clemc
2020-11-06 22:58               ` grog
2020-11-07 21:04                 ` clemc
2020-11-07 23:05                   ` dave
2020-11-09  4:36                   ` [COFF] Daisy wheel printers (was: [TUHS] The Elements Of Style: UNIX As Literature) grog
2020-11-09 14:26                     ` clemc
2020-11-10  0:10                       ` grog
2020-11-10 14:48                         ` clemc
2020-11-10 15:10                           ` stewart
2020-11-09 22:08                     ` dave
2020-11-10  0:48                       ` grog [this message]
     [not found]             ` <202011061546.0A6Fkv3D034443@elf.torek.net>
2020-11-06 16:22               ` [COFF] [TUHS] The Elements Of Style: UNIX As Literature clemc
2020-11-06 18:12                 ` torek
2020-11-07  2:52                 ` cym224
     [not found]               ` <20201106225422.GD99027@eureka.lemis.com>
     [not found]                 ` <20201106232901.AkY2I%steffen@sdaoden.eu>
2020-11-07  4:22                   ` grog
2020-11-07 20:31                     ` steffen
2020-11-11  8:31           ` [COFF] " peter
2020-11-11 12:21             ` tih
2020-11-11 21:09             ` dave

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=20201110004803.GQ99027@eureka.lemis.com \
    --to=coff@minnie.tuhs.org \
    /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).