-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I never said the problem was with Linux...I said that I think that the problem is with the Bios, so I'm going to take a look at it in a bit. I may also try a different cable. On Tue, Jun 22, 2004 at 04:05:56PM -0700, Debee Norling wrote: > It is likely the problem's with your BIOS or cable and not with Linux. > > Try getting help looking at your BIOS settings -- write down whatever it's > set to and change it. I have worked for a decade in tech support and know > that just because BIOS says the port is ECP, or AT standard doesn't mean > that's how it is really set. Sometimes the message in the BIOS setup program > doesn't match how the BIOS actually sets up the port. > > And even though Linux doesn't talk to the BIOS, it does talk to the > hardware, and BIOS configures those settings directly and permanently. > > It's also a real good idea to just try another cable. I had a Braille > embosser which, with only one computer and one particular cable printed > complete gibberish. But when I examined the gibberish closely I realized > that the ASCII value of every character was incremented by two. This problem > was solved by using another cable, even though the cable I was using worked > fine with a laserjet on another PC. > > --Debee > > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup - -- Failure is not an option, it comes bundled with your Microsoft product. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFA2MR9Nohoaf1zXJMRAlUnAJ9IgA/LfzCU6mx3q32Ymt7/g+pPUACgrBgk XXGeHyfnd6QRNuP0c9XpO4Y= =PH+1 -----END PGP SIGNATURE-----
