From: "Mike McCarthy, W1NR" <lists@w1nr.net>
To: Phil <phillor@telstra.com>
Cc: linux-hams@vger.kernel.org
Subject: Re: USB converters and old hardware
Date: Thu, 08 Apr 2010 06:20:56 -0400 [thread overview]
Message-ID: <4BBDAE08.9010507@w1nr.net> (raw)
In-Reply-To: <201004081508.45770.phillor@telstra.com>
There are many PCI and PCI-e cards with both types of ports that respond
like "real" serial and parallel ports. I generally buy the cheapest ones
I can find at mwave.com (they all seem to use the same chip) and have no
problems. No go for laptops. Best solution I have seen for laptops are
the legacy docking stations for the Dell Latitude line.
Mike, W1NR
Phil wrote:
> Thank you for reading this.
>
> I have two old hardware items that I would like to put back into service.
>
> The first is a Baycom style modem that of course does not work with USB to
> serial converters because of the non-standard way in which the modem
> interacts with the serial port. An acquaintance told me that genuine USB to
> serial converters are available but a Google search does not indicate this to
> be true. Can anyone suggest how I might be able to use this modem again?
>
> The second question is more programming related and concerns a hardware
> item that used to operate via a parallel port. I thought a USB to parallel
> converter would easily solve this problem but it does not. The converter
> does allow me to use an old printer and it does cause /dev/parport0 to be
> generated. The problem is that ioctl(fd,PPCLAIM) now causes the following
> error message to be displayed:
>
> "Parport claim: No such device or address"
>
> This indicates to me that the parallel converter does what it is intended to
> do, allow the use of old printers, but nothing else. Is there an alternative
> way to programme such a port? I've played with the outport C instruction
> briefly but I'm unsure of the base address of the port. Are genuine serial and
> parallel ports available for newer computers?
>
> I'm reluctant to build new gear when the old stuff works perfectly.
>
>
next prev parent reply other threads:[~2010-04-08 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 5:08 USB converters and old hardware Phil
2010-04-08 10:20 ` Mike McCarthy, W1NR [this message]
2010-04-09 1:09 ` Phil
2010-04-13 14:42 ` walter harms
2010-04-13 17:52 ` IT2 Stuart Blake Tener, USNR
2010-04-14 5:37 ` Douglas Cole
2010-04-14 15:18 ` IT2 Stuart Blake Tener, USNR
2010-04-15 1:51 ` Phil
2010-04-15 14:49 ` IT2 Stuart Blake Tener, USNR
2010-04-15 17:47 ` USB converters and old hardware (in general) Dave Platt
2010-04-15 17:48 ` USB converters and old hardware (Baycom in particular) Dave Platt
2010-04-15 19:22 ` Tomi Manninen
2010-04-15 20:05 ` Adam Sampson
2010-04-15 20:41 ` Dave Platt
2010-04-15 15:55 ` USB converters and old hardware Niall Parker
2010-04-15 16:56 ` IT2 Stuart Blake Tener, USNR
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=4BBDAE08.9010507@w1nr.net \
--to=lists@w1nr.net \
--cc=linux-hams@vger.kernel.org \
--cc=phillor@telstra.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