From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] VAX faxing?
Date: Sun, 4 Jan 2015 17:40:39 -0500 [thread overview]
Message-ID: <CAC20D2PoQ=Fvdjdfmc-+Xsun5Lj=8PZCyv5mKKDwpdrJzctWig@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.11.1501050446570.58880@aneurin.horsfall.org>
Yeah - some of the modems were. IIRC: Sam Leffler (sam "usual email
punctuation" errno.com) did the original FlexFax SW and we had a couple
kicking around. My memory is that the modems that could also support Fax
in those days, sucked at UUCP, so most of us did want to dedicate a phone
line to one of them.
Also the scanner interface was not very easy. We tried to replace an HP
fax machine with SW, including a scanner and fax modem, but it was not very
satisfactory for the non-technical types.
I don't have any memory of "large-scale" use however. What was cool was
some of the printers knew how to use PS as the format, instead of the
1860's style scanning [yes, FAX was invented for the US civil war and
originally ran over telegram lines - the current format is just a super-set
of the old mechanical scan system from those days].
On Sun, Jan 4, 2015 at 12:50 PM, Dave Horsfall <dave at horsfall.org> wrote:
> On Sun, 4 Jan 2015, Cory Smelosky wrote:
>
> > Were VAXen ever used to send/receive faxes large-scale? What software
> > was used and how was it configured?
>
> I don't think fax modems were even invented then, were they?
>
> I remember using FlexFax (then renamed to Hylafax) quite a lot, sometimes
> for nefarious purposes (it was trivial to fake the CSID)...
>
> --
> Dave Horsfall DTM (VK2KFU) "Bliss is a MacBook with a FreeBSD server."
> http://www.horsfall.org/spam.html (and check the home page whilst you're
> there)
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150104/d2062c21/attachment.html>
next prev parent reply other threads:[~2015-01-04 22:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-04 8:30 Cory Smelosky
2015-01-04 17:50 ` Dave Horsfall
2015-01-04 22:40 ` Clem Cole [this message]
2015-01-04 23:15 ` Erik E. Fair
2015-01-04 23:36 ` Jacob Ritorto
2015-01-05 4:31 ` Dave Horsfall
2015-01-05 4:31 ` Lyndon Nerenberg
2015-01-05 4:54 ` Erik E. Fair
2015-01-05 11:11 ` Steffen Nurpmeso
2015-01-08 23:11 ` Michael Parson
2015-01-05 1:02 ` Lyndon Nerenberg
2015-01-05 1:48 ` Clem Cole
2015-01-05 4:10 ` Lyndon Nerenberg
2015-01-05 9:59 ` Jacob Goense
2015-01-06 1:55 ` [TUHS] State of networking in the early '90s Warren Toomey
2015-01-06 7:02 ` Erik E. Fair
2015-01-06 7:37 ` Angus Robinson
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='CAC20D2PoQ=Fvdjdfmc-+Xsun5Lj=8PZCyv5mKKDwpdrJzctWig@mail.gmail.com' \
--to=clemc@ccc.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).