Return to the archive index

Re: Twiddler-FAQ.linux

From: "David H. Silber" <>
Date: Wed, 4 Nov 1998 23:51:25 -0500

On Wed, Nov 04, 1998 at 02:22:12PM -0500, Tim Gray wrote:
> The Twiddler-FAQ  version 0.001Alpha

Tim,

I have added to your document.  Please feel free to use as much of this
as you think is appropriate.

This work was done on a Debian GNU/Linux system.

The first column is a key to my changes.  `*' means new text.  `|' means
changed text.  ``' means a comment that may or may not be needed in an
actual production copy of this FAQ.

| The Twiddler-FAQ  version 0.002Alpha

  So you have a twiddler and cant get it to behave on your Linux computer? Me
  too! but after compiling a bunch of information from various sources I have
  came up with this small FAQ, to be expanded and corrected as time
  permits....

| Step 1 - download the twiddler driver from handykey for Linux.  (From
| http://www.handykey.com/drivers/Twid-LinuxV2.tar.gz)  This FAQ is
  based on the origional driver(Version2.0)  and not the enhanced version.
|
| Untar this as root into your favorite directory.
* # mkdir twiddler
* # cd twiddler
* # tar -xvzf ../Twid-LinuxV2.tar.gz

  Step 2 - edit the twid_defaults.ini file to remove all traces of dos
  Ctrl-M's the program will choke as soon as it sees one CTRL-M. so eradicate
  them all carefully. In fact I would work on a copy and not the actual file.

  Step 3 - after you have edited the twid_defaults.ini file move it to your
  /etc directory (you must still be root to do this!)  and be sure it is
  world readable.
* # sed -e "s/.$//" < twid_defaults.ini > /etc/twid_defaults.ini
* # chmod 644 /etc/twid_defaults.ini

  Step 4 - untar the a2x.tar.gz where it sits, it will make a rats nest of
  directories to navigate through.. find the source code and look at the
  makefile (If you dont know how to deal with makefiles or sourcecode dont
  worry it will compile on a normal linux system) now run xmkmf. After xmkmf
  has finished run make.  everything should compile (On slackware it will, I
  have tried it from slackware 2.0 to 3.5 and it compiled flawlessly on all)
  red hat is another matter... the GCC compiler under Red Hat is broken and
  will sometimes not work, long with Red-Hat not following normal filesystem
  setup. (I.E. directory layout is bizzare compared to the rest of the linux
| world.) This proceedure also works just fine on a Debian GNU/Linux system,
* but the a2x execuatble could not find ``libXt.so.6'' until the lib6g-dev
* package was upgraded to version 3.3.2.3a-6 and the executable was rebuilt.
| When make is done copy the a2x program to your /sbin directory (Or
| wherever you desire. I put it in /bin so I dont have to mess with path
  statements)
* # tar -xvzf a2x.tar.gz
* # cd pub/R6untarred/contrib/programs/a2x
* # xmkmf
* # make
* # cp a2x /usr/local/sbin
` (I suggest that we don't reccomend that people stuff things into the
` system /sbin directory.  There is a file system standard that specifies
` that user-added facilities are added under /usr/local.  Some systems
` [Debian, Red Hat, others] have package management systems that expect
` to fully control what goes into the system directories.)

  Step 4 - go back to where you untarred twiddler and copy that to your /sbin
  or /bin directory.  Plug in the twiddler (if it hasnt been plugged in
  already) and let's see if this works.  type twiddler to run the driver.
* # cd ../../../../..
* # cp twiddler /usr/local/sbin
* # twiddler

  NOTE : the twiddler driver wants to see the twiddler on com2 or /dev/cua1
  if you dont have it there type twiddler -p 0 for com1 1 for com2 2 for com3
  etc.... (remember Linux device numbers start at 0!)

  Everything should be working. unless you get an error stating that the
  twiddler cant be found, then check the port you are connected to and try
  again.

  Step5 - Xwindows!!!!  note.. be sure you dont have the twiddler plugged
  into the port that X expects to find a mouse, it will kill the twiddler
  driver. I have yet to figure out how  to configure X without a mouse /dev
  entry.  If your mouse doesnt work press CTRL-ALT-F1 to exit to text mode,
  press CTRL-C to stop XWindows.. look for a message on your screen from a2x
  - it will complain there.

  that's it for now.... I'll have more detail later with some utilities to
  strip the CTRL-M's for you in a tarball

-- 
David H. Silber


--
Subcription/unsubscription/info requests: send e-mail with subject of
"subscribe", "unsubscribe", or "info" to 
Wear-Hard Mailing List Archive (searchable): http://wearables.ml.org

+Previous Message in Thread | Next Message in Thread

From Wear-Hard Mailing list Archive (WH)
Maintained by R. Paul McCarty

Archive created with babymail