Just a Bunch of Scanners (JBOS?)
Comments
don-code
h2odragon
SCSI cabling issues are so much more fun 20 years on, and happening to someone else.
Once had a system with 16 SCSI controllers and 36 disks connected to them.
panki27
> so that I could prove “Chris O” wrong on StackExchange.
If that is the case and this works, why is there no answer stating that on StackExchange?
gorkish
It'd be worthwhile to ask why that answer persisted on SE in the first place.
I've used iscsi before with sg and scd devices; it's never even occurred to me that anyone should think it's limited to disks, because, well, it's not.
For the record, ATA-over-Ethernet (AoE) is/was a competing protocol to iSCSI, and it also has generic ATAPI support.
For anyone looking to build a rube goldberg machine for thier youtube channel or get up to similar shenanigans, I think it would be funny use case to get a SCSI Ethernet adapter running over iSCSI.
While it's not a SCSI model, I suspect that the scanner on my LaserJet 1100a, circa 1997 - which I still use at least weekly - has more staying power than many scanners made available in the last 10 or 20 years. I still use it with SANE on a modern laptop running Fedora.
The last released driver for this scanner was for Windows 2000. That driver works fine on Windows XP, but not on Windows Vista or higher. Luckily, as a Linux user, hplip supports the scanner out of the box. When I was still a Windows user, I'd run NT4 in a virtual machine, pass the parallel port through, then share a folder between the local machine and the VM.
The fact that it's a parallel scanner presented its own set of archaic problems, like "what mode do I put the parallel port in?". Luckily, since upgrading to a machine without a parallel port, I've let that be the responsibility of a JetDirect 300x, which exposes the scanner as an IP network device. I've had significantly fewer problems since adopting that setup.
The page count on the scanner is around 25,000, and still holding strong.