28 Oct
2012
28 Oct
'12
3:29 a.m.
----- Original Message -----
<snip>
I was asking about the
UDS1100
<snip>
From: Tothwolf <tothwolf at concentric.net>
To: General Discussion: On-Topic and Off-Topic Posts <cctalk at classiccmp.org>
Cc:
Sent: Sunday, 28 October 2012 6:47 PM
Subject: Re: networking classic hardware
On Sat, 27 Oct 2012, Tom Sparks wrote:
>??For printing, I used a multi-port parallel autoswitch with its inputs
connected to the different computers I wanted to print from.
file sharing and printer sharing is on
the top of the list, the others are at the bottom of the list
??From: Tothwolf <tothwolf at
concentric.net>
>??Ok, having re-read the entire thread, I have a better idea of what you
are
after.
??<snip>
??I hoping to use ethernet hardware, so I can use power over ethernet, ATA
over
ethernet, KVM over ip, Audio over ethernet etc
IMO, you are getting way ahead of yourself. AFAIK, the Lantronix UDS10
doesn't support PoE anyway.
the newer version dose (UDS1100)
In fact, I don't think /any/ of their older
(read: halfway affordable) devices support PoE.
i'm looking at using PoE to
eliminate as many wall warts? as possible
As far as KVM over IP goes,
that's a whole 'nother ball of wax...
i'll leave kvming (is that a
word?) to a later date
<snip>
??what about Zmodem for basic file transfer?
Software for many classic machines may not have support for Zmodem since it was
one of the later protocols. Some may support protocols such as Xmodem or Kermit,
but may or may not support proper CRC checking. On the Linux machine, lrzsz and
ckermit will support these.I knew there were older transfer protocols ??i've
contacted lantronix, to see if the could add auto-switch mode to
the firmware
Good luck. Unless you have a support contract, Lantronix is highly unlikely to
add a feature to unsupported / "legacy" devices. Keep in mind that Lantronix also only provides
Windows drivers for port redirection with their serial devices.
like normal,
windows runs the world :)
I did find some linux com port redirectors
Based on my own experience I'd recommend using parallel where you can for
sending print jobs out to the Linux machine and save serial for outgoing
connections from and data transfers to/from the classic hardware.
thats what i was
think
If you need to
remotely locate your printers, have the Linux machine talk to print server
devices near your printers. If the Linux machine is close to the printers and
you don't have very many printers, skip the ethernet print servers entirely
and save yourself the trouble and headaches they absolutely /will/ cause.
I am
looking at a 1:1 ratio with the printer servers (1 printer to 1 printer server)