widmer@luna ~]$ witnotp &You should include the appropriate setup in your .cshrc (or .bashrc or...) file. Wit!P assumes that it will find everything it needs in the execute search path, so using an alias for witnotp will not work:
[1] 9566
witnotp: Command not found.
[widmer@luna ~]$
[widmer@luna ~]$ alias witnotp /home/wnprun/bin/witnotpWit!P will start the GUI on the host defined by the command line argument host or by the environment variable DISPLAY (REMOTEHOST, if DISPLAY is not defined). If the GUI host is different from the machine where the witnotp script is executed (or even if Wit!P thinks that the two systems are different), the GUI (sw_server) will be started using a remote-shell command (rsh). The rsh command will fail, if you do not have the appropriate entries either in ~/.rhosts or /etc/hosts.equiv:
[widmer@luna ~]$ witnotp&
[1] 9578
[widmer@luna ~]$ netfsname: Command not found.
sorry, cant execute client sw_client.exe
AW on bigone 42> witnotpIf you are using a precompiled binary version, you may get messages like the one below:
Connecting to server on remote host
Permission denied.
rsh: connection failed
Waiting to make connection to server port_19945 on luna.ph.chbs...
[widmer@luna ~/junk]$ witnotpFix: install the missing library (or in the case of missing readline library, build re-compile Wit!P without readline support).
Server changed directory to /home/widmer/junk
sw_client.exe: error while loading shared libraries: libreadline.so.4.1: cannot load shared object file: No such file or directory
On a PC running Windows/NT, the middle shortcut (WitNotPNT) may be used to launch the Wit!P GUI server and the client. This method does not work for non-NT flavors of Windows. Instead, the left shortcut (WitNotP) should be used to start the GUI server, and the right shortcut (WitNotPC) should be used to start the Wit!P client (unless the client is used on a remote Unix (or Linux) host. The most common cause of failure is that Wit!P has been installed in a non-standard location (a directory other than C:\wnp-nt) without making the necessary changes to the batch files and shortcuts. If WIt!P fails to start, check the following: