Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: coleman@cam.nist.gov (Sean Sheridan Coleman X5672)
Newsgroups: comp.sys.sun
Subject: keyboard problem with openwindows
Keywords: Windows
Message-ID: <875@brchh104.bnr.ca>
Date: 17 Dec 90 17:20:15 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 11
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 9, Issue 402, message 14
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

As posted previously, I stated that I couldn't get openwindows to start up
because of an error due to the keyboard. I received a note stating that
the problem was due to the dip switch settings on the keyboard. I looked
at the settings on the board and found them to be set to all 0's like the
README FIRST pages for 4.1.1 stated ( this  has the scoop about the bug).

I switched all the settings to 1, and I was able to get openlook to work.
Why would all 0's cause it to fail? What does all 1's do to the keyboard?

Sean Coleman
coleman@bldrdoc.gov