[Wylug-help] SCSI Parity

[James Holden (Wylug)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I posted this message to Usenet recently, and wondered if any WYLUG
minds might have any ideas.

To keep it on topic, I'm not averse to connecting the printer to a Linux
box with an Adaptec 1540 board I have laying around, if I can disable
parity checking on that.


Here goes with the original message.........

I'm trying to find a way to disable parity checking on the SCSI
interface on one of my SGIs. An odd request, I know, but I have a
device which appears to generate bad parity and I want to get it
connected. I don't care if I have to connect it to my Indy, Indigo2,
O2 or even my old R3000 Indigo.

The device is an Alps MD-2010 dry ink printer. I get parity errors
when the bus is probed on power up. My bad parity theory is drawn from
this Usenet thread:

http://groups.google.com/groups?selm=7e7713%2450j%241%40nnrp1.dejanews.com&oe=UTF-8&output=gplain

Some guy couldn't get a similar printer working on an Adaptec card in
a G3 mac. It seems that the onboard SCSI interface on older macs
ignores parity, to the Alps' brokenness doesn't bother it.

I suppose I could put together a device to do the parity for the
printer out of discretes, but it'd be a long shot. Some XORs and
tristate buffers should work. Anybody got any good reasons why it
wouldn't?

If I get the printer talking on the SCSI bus, I'm pretty certain that
it'll work with CUPS, which supports the printer and supports SCSI
printers.

Help!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/uzYHmHdHQoNYhjoRArsAAKDPSg9SZ4cVZ8xaQjYPYzEDiHjRSgCeNPRT
WbHZiaKPBWx9z/qav/GBRvE=
=j5VL
-----END PGP SIGNATURE-----