Trace: » linux06.html

[hemmerling] Linux 6/8 - Linux with X-Terminals and Terminals

X-Terminals, X-Server

The Tandberg TDV 6230F X-Terminal

Tandberg TDV 6230F X-Terminal

The Tandberg Mouse

  • The X-terminal Tandberg TDV 6230F is shipped with a serial Logitech Mouse series 9, modell “CC-93-9F”, FCC-ID “DZLCC”. Siemens/Nixdorf shipps this terminal with a Logitec mouse, modell “CC-9”, Siemens/Nixdorf Code “S26361 - H143 REV.A.”, FCC-ID “DZLCC”.
  • Do you know any replacement ? If so, please tell me.

How to setup SUSE 7.1 Linux for use with a Tandberg "TDV 6230F" X-Terminal

  • An X-terminal Tandberg TDV 6230F is to be connected to a PC with SUSE 7.1 Linux, Linux kernel 2.4.16, in a separate subnet. The installation software for the terminal was available on CDROM.
  • Do you know how to reset of the password ? If so, please tell me.
  • Or do you know any “master” password ? If so, please tell me. I got my terminal without password set, so no problem. But several other fresh owners who bought such a terminal from second hand, asked me so !
Setup of the X-Terminal
  • The terminal ( MAC address 08:00:06:03:1c:aa ) is connected by 10Base2 to a Linux PC. The fixed IP address is assigned to the terminal, the fixed IP address is assigned to the network card “eth1”, which belongs to the same subnetwork, by the configuration program “Yast”. For testing, the boot service type is set to “manual” for the X-terminal. The network connection is tested by command “ping”.
Installation of the sofware packages with "Yast"
  • DHCP server and client ( n/dhcp, n/dhcpn ), IP traffic analyser ( n/iptraf ), TFTP server and client ( n/tftp ), BootP, display manager XDM.
Activation of services
  • Modification of /etc/inetd.conf:
    tftp dgram udp wait root /usr/sbin/tcpd in.tftpd -s /tftpboot
    bootps dgram udp wait root /usr/sbin/bootpd bootpd -c /tftpboot
  • Modification of /etc/dhcpd.conf:
    option subnet-mask;
    default-lease-time 600;
    max-lease-time 7200;
    subnet netmask {
    option broadcast-address; 
    host tandberg_data {
    hardware ethernet 08:00:06:03:1c:aa;
  • Just have a look at /etc/X11/xdm/xdm-config:
    xdmcp 177/tcp # X Display Manager Control Protocol
    xdmcp 177/udp # X Display Manager Control Protocol
  • Modification of /etc/X11/xdm/xdm-config:
    DisplayManager.requestPort: 177
  • Modification of /etc/rc.config:
    # Shall dynamic host configuration Server DHCP be started? (yes/no)
  • The DHCP service may be started manually by the command “rcdhcp start”.
  • Modification of /etc/rc.config:
    # Here you can set the default Display manager (kdm/xdm/gdm/wdm/console).
    # Attention: CHECK_INITTAB has to be set to yes, to activate this feature.
    # If DISPLAYMANAGER is set to console, SuSEconfig will not bother you
    # with a missing XF86Config.
    # SuSEconfig can do some modifications to /etc/inittab. If you don't want
    # this, set CHECK_INITTAB to no. (yes/no)
Installation of the X-terminal software
  • According to the description of the files ”/cdrom/README” and ”/cdrom/docs/instman.txt”, the following directory structure has to be created before, manually:
  • The first directory if for the boot image XtdFwm and the configuration files, the second directory ist the base directory for X11 fonts, example files and further configuration files. The name of the third directory depents on the IP of the connected X-terminal: E.g. the directory 192.168 contains the configuration files for X-terminals of the IP subnet 192.168.xx.xx. Please create an “empty” text file 2.133 in this directory, because the X-terminal runs on the IP
  • By default, the X-terminal is lookign for the boot image “XtdF”. So please create a symbolic link, if necessary:
    cd /tftpboot
    ln XtdFwm XtdF
Useful hints
  • The configuration file /tftpboot/XtdFwm.cnf is destroyed by the configuration script /cdrom/tdinstall, unfortunately - the values of the variables are inserted, but the names of the variables including the assignment character ”=” are deleted in the text file. The directory /tftpboot/tftpboot/usr/lib/X11/td/examples/configs/ contains a set of correct configuration pattern files, for comparison.
  • In the diagnostic menu of the X-terminal, syntax errors happening during the processing of the file /tftpboot/XtdFwm.cnf and the sucessful or failing loading of fonts are registered.


  • The boot service type is set to “BootP” for the X-Window terminal, the configuration is saved. Thereafter, the terminal is powered-down and up. It boots up to the login window of XDM, finally.
My Experiences
  • The IP traffic analyser “iptraf” was useful to track XDMCP requests of the X-terminal.
  • The KDE desktop is not displayed properly on the grayscale screen of the X-terminal.
  • If the X-terminal is rebooted by the “session control” menu, it does not get any IP, in spite of active BootP and DHCP services on the Linux PC. After a power-down and up, the X-terminal boots properly.

The X-Server Software "X Appeal"

The Tool

The X-server 'X Appeal' for MSDOS "Xtreme s.r.l. - X Appeal" ( - 2004-12-08 ) is an X-server for MSDOS on 386/486 PCs with 4 MB RAM and network “Packet” driver, no DPMI support ( i.e. does not run in the DOS box of Windows ). 30 days expiration, a maximum of 8 connections = a maximum of 8 open windows on the X-Window screen.

Software Installation

  • The X-server MSDOS software X Appeal, running on a 486/66 PC, 16 MB Ram, a 3Com 3C509 Ethernet network card ( an EM100TX-ISA by Adaptec / Cogent, alternatively ) and an S3 graphics card “V7 Mirage” by SPEA/Videoseven ( a “V7 Vega Plus” graphics card by Videoseven, alternatively ) is to be connected to a PC with SUSE-Linux 7.1, Linux kernel 2.4.16.
  • There are two download offers:
    • Version is archived at Simtel ( “”, “”, “”, “”, “”, “”, “”, “”, “”, “”, “”, “”, “xappeal.txt” ). Additional packet drivers are available by Simtel too.
    • The archives “” .. “” and “xappeal.txt” of Version are offered for download at the original "X Appeal, HTTP Download" website until 2004-12-08. Note that the archives “” ( accelerated server for 8514 cards ), “” ( accelerated server for AGX-based cards ), “” ( accelerated server for Mach8-based cards ) do not exist, in comparison to version, although it can be selected by the installation software !
  • Use an “Unzip” utilty to extract the contents of each archive to a different 1.44 MB floppy disk.
  • Extract the archives “” and “” and the file “xappeal.txt” from the archive “”. Extract the installation instructions and the manual from the archive “”. Either print the documentation on paper or transfer the files to a second PC ( e.g. your Linux PC ) and read it !
  • Extract the files from the archive “” and run “uvconfig.exe”, the configuration software for the VESA graphics driver “UNIVBE”. Please note what it tells you about your graphics card. For my two graphics cards, it tells me:
    Video Card: S3 SuperVGA (80c805revA/B) with 1 Mb
    RAM DAC: AT&T ATT 20C491 24 bit DAC
    Clock Chip: (Discrete clock selection)
    Video Card: Avance Logic SuperVGA (ALG2228) with 1 Mb
    RAM DAC: Avance Logic AG1201 24 bit DAC
    Clock Chip: (Discrete clock selection)
  • The network connection to your Linux host is handled by a “Packet” driver for your chosen network device. Please make a “Packet” driver work with your network device. “X Appeal” is already shipped with a set of “Packet” drivers in the archive “XA3122-A.ZIP”. Simtel has a more complete libary. For modern network devices ( PCI cards, USB and Firewire devices ), it is up to the manufacturer of the network device to supply such. Please configure your network device ( interupt, I/O address, memory area ) and do a test installation of the “Packet” driver.
    • The Ethernet network card “3C509” by 3Com is supported by a “Packet” driver shipped with “X Appeal”.
    • The EM100TX-ISA (100 half-duplex) by Adaptec / Cogent is just shipped with an “ODI” driver for MSDOS. Read the file “pktdrv.txt” which is shipped with the “ODI” driver. The appendix “B” of the installation manual of “X Appeal” explains deeply how to configure the necessary “ODI to Packet driver converter”.
  • Follow the installation instructions. Note that due to the used 386 DOS-extender neither the installation software nor the X-server can be run in a DOS box of Windows. Please install the X-server “X_SVGA” as default X-server, at first, before trying to install a special X-server for your graphics card.
  • I did not succeed to use a font server for “X Appeal”, due to a runtime crash at startup. Here is how to activate a font server on the Linux host, anyhow:
    • Modification of /etc/inetd.conf:
      # x11 fontserver
  • I did not yet succeed to use “BootP” for assigning a dynamic IP to the X-server at startup :-(. Here is how to activate a font server on the Linux host, anyhow:
    • Modification of /etc/inetd.conf:
      bootps dgram udp wait root /usr/sbin/bootpd bootpd -c /tftpboot
  • FAQ:
    • Q: During the installation process, I am asked to insert disks with certain contents. How do I learn what's on the different installation floppy disks ? A: Have a look at the file “xappeal.txt”.
    • Q: Where is the “Packet” driver loaded and unloaded ? A: In the batch file /xappeal3/x.bat.
    • Q: Where is the default X-server loaded ? A: In the batch file /xappeal3/x.bat.
    • Q: How to shut down the X-server ? A: Press “CTRL-ALT-BACKSPACE”, but be aware not to press “CTRL-BREAK” ( breaks into an undetermined state of MSDOS - mostly the PC reboots afterwards).
    • Q: How to reconfigure “X Appeal” and the X-server “X_SVGA” after exchanging the graphics card ? A: Run the program “uvconfig.exe” in the installation directory and copy the modified file univbe.drv from the installation directory to the configuration directory.
    • Q: Limitations of the trial version ? A: A maximum of 8 connections = a maximum of 8 open windows on the X-Window screen. If you don't set the date of you PC to an anicent date ( e.g. 1996-01-01 ), the 30 days trial version has expired from the start: The performance is limited and Trucolor/Hicolor modes are not available.
  • If you like, have a look at my configuration file ”/xappeal3/xappeal.cfg”: GitHub "hemmerling/xserver-configuations/blob/master/xappeal/xappeal.cfg".
  • I succeeded to run the X-server “X_SVGA”, but I failed to run the X-server “X_S3” due to a runtime crash at startup.

Some other X-server Software

OpenSource & Free



Other Thin Clients, Terminals and Terminal Emulations



Forums, Newsgroups

Appropriate OpenDirectory Directory Pages

en/linux06.html.txt · Last modified: 2023/11/30 21:56 (external edit) · []
Recent changes RSS feed Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki