The behavior of wiredx is configured via the `props` file, which can be found in `misc/config` after unzipping the archive. I’m surprised that Channel 2 is pre-set in your case; the default is definitely 0. Among other things, these settings allow you to define the output window size, color depth, and keyboard layout. There are also specific functions for remote login (SSH) and the `esd` sound Server — though these require a suitably old Linux counterpart to function.
Yes, that's right, you can also start a local program by directly entering the DISPLAY address. If only one XServer is running, no additional parameters are needed, provided the standard environment variables are set. Personally, I’ve made it a habit to explicitly set the `DISPLAY` variable when redirecting from a Linux source like a Raspberry Pi.
Overall, XFree86 (4.5) is quite temperamental and its structure remains confusing. Unfortunately, it no longer runs under UEFI; I still use two older laptops where it works fine.
### Testing xterm and Redirection
I haven't spent much time with the ported XFree86 version of `xterm` yet. I just tried several startup commands, but it consistently hangs with a **"suid-root"** notice. `eterm` also complains when called from the command line, as it strictly requires an active XServer.
It seems `xterm` only works within the full-screen XFree86 server. I tried redirecting `xterm` to WeirdX or HOBX11 from a full-screen session, but surprisingly, that failed as well. I also forgot the specific syntax for a moment: XFree86 requires `SET` instead of `export`, though changing it didn't help. Even attempts to redirect `xterm` to the Pi get stuck on the "suid-root" error. It's just another quirk of this old port—it’s always good for a surprise.
### Window Managers and Rootless Mode
Other ported XFree86 programs provided they run at all can be displayed on WeirdX. Some window managers also work if configured beforehand. I’ve attached two screenshots showing **IceWM** and **WindowMaker** for illustration.
The program still has enormous potential. Unfortunately, the aforementioned bug hinders the "rootless" (seamless) mode for almost all applications. While you can start software like Gimp locally in transparent mode, you can't actually work with it, which is a shame. In `rootlesswm` mode, WeirdX provides a TWM server and the single window on the **WPS**. I’ve included a screenshot of this as well. However, due to the bug, these useful features aren't viable in `rootlesswm` mode, forcing you back into `InBrowser` mode, confined to the program window.