X-Win32 Knowledge Base   >   Command not found

Search


About StarNet

StarNet Communications has been a leading developer of X Windows solutions since 1989. After establishing X-Win32 as the de facto standard in the higher education market during the early to mid-1990s -- 150 unlimited Campus Site Licenses worldwide -- X-Win32 has become of one the top three PC X servers in the government and commercial sectors as well.

Unlike its major rivals, Exceed (Hummingbird) and Reflection-X (WRQ/Attachmate), X-Win32 offers a highly focused PC X server that offers superior performance and productivity features, stability, ease of use and low cost (40% or better in most cases).

StarNet also delivers unequaled customer support. Our state-of-the-art engineering infrastructure allows us to fix problems and make a new release available quickly (overnight in many cases). As our testimonials page shows, StarNet customers consistently rate their X-Win32 experience as the best in the industry.




Command not found

When starting a StarNetSSH, rsh, or rexec session in X-Win32 you may receive the error below in X-Win32’s Messages window (which can be opened by selecting the Show Messages item from the tray or system menus):

Command not found

There are a few possible causes for this, all of which are related to the value in the command field of the session in X-Config:

  • There is a typo in the value for the command field; it could be a typo in the program name itself (e.g. “xxterm” instead of “xterm”), or it could be an extra shell control character (e.g. “xterm ; -ls -display” instead of “xterm -ls -display”)
    • Solution: Correct the typo in the command field
    • The program being run on the remote host is not available on that host. For example, dtterm is typically available only on systems that use the Common Desktop Environment (CDE), such as Solaris, HP-UX, or AIX, but not on SuSE, Red Hat, Debian, Ubuntu, or FreeBSD.
    • Solution: Install the program that you are trying to run on the remote host
    • Solution: Use an alternative program already available on the remote host (e.g. xterm on Linux systems instead of dtterm)
    • The program being run on the remote host is not in the system path on the remote host; this is more typicaly on older Linux or UNIX operating systems.
  • Solution: Specify the path to the program completely (e.g. /usr/X11R6/bin/xterm (Linux), /usr/openwin/bin/xterm (Solaris), or /usr/dt/bin/dtterm (CDE systems) )

    Category:Errors
    Category:Sessions



How Can We Improve This KB Article?

Please rate the quality of this article: Excellent Good Fair Poor

Did this article answer your question? If not, we'd like to hear more about it:

Do you need additional assistance? If so, enter your email address:

Articles are periodically updated based on your feedback. If you enter an email address, then you will be given the opportunity to open a case, for which you will receive a response within 2 business days.