INTL 3:770/1 3:770/3
REPLYADDR 68g.1499@etr6.net
REPLYTO 3:770/3.0 UUCP
MSGID: a44e43f8
REPLY: d0bdd7c6
PID: SoupGate-Win32 v1.05
On 2/2/24 11:34 AM, Scott Alfter wrote:
> In article ,
> 68g.1499 <68g.1499@etr6.net> wrote:
>> On 2/1/24 9:40 AM, The Natural Philosopher wrote:
>>> On 01/02/2024 06:32, 68g.1499 wrote:
>>>> Ok ... I'm not gonna ask why you'd want a completely separate
>>>> print server, based on an old Pi, rather than just printing
>>>> directly from/to whatever :-)
>>>>
>>> It avoids massively long printer cables obviously, when you have a
>>> pre-existent network of some sort...
>>
>> Um ... printers have come with network ports/wi-fi for at
>> least 15 or more years now. You don't need "long cables",
>> except for ethernet, and thus the printer can be 300+ meters
>> away in the junk shed and work just fine. You can see and
>> print to it from any PC-like-thing directly.
>
> The printers I'm connecting that way are definitely older than that. There
> was a LaserJet 1320n that had built-in Ethernet connectivity, but that
> wasn't what I'd bought the better part of 20 years ago.
The HPLJ-2 was a damned workin' MACHINE. Almost
indestructible. Good quality, acceptable speed.
But it wasn't Wi-Fi.
But it COULD be Wi-Fi or Ethernet. Just takes a
cheap adapter or two. You can also SHARE it from
a Win or Lin unit. No need for intermediary stuff.
Anyway, just saying that there ARE solutions beyond
a dedicated print server. Easier, more future
utility.
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 15/0 19/38 90/1 105/81 106/201 128/260 129/305 135/225 153/7715
SEEN-BY: 218/700 226/30 227/114 229/110 112 113 200 206 307 317 400
SEEN-BY: 229/426 428 470 550 616 664 700 266/512 282/1038 291/111
SEEN-BY: 292/854 320/219 322/757 342/200 396/45 460/58 633/280 281
SEEN-BY: 633/412 418 420 509 2744 712/848 770/1 3 100 330 340 772/210
SEEN-BY: 772/220 230 5020/400 5075/35
PATH: 770/3 1 633/280 229/426
|
