Author Topic: Java applications  (Read 692021 times)

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5735
  • Karma: +150/-1
Re: Java applications
« Reply #435 on: March 17, 2026, 11:54:36 pm »
I did try connecting OS/2 xterm to it, both with 127.0.0.1:0 and :1 and using my IP address. Couldn't connect in all cases. Same with xman, which is pretty simple.

P.R.

  • Newbie
  • *
  • Posts: 12
  • Karma: +3/-0
Re: Java applications
« Reply #436 on: March 18, 2026, 07:24:54 pm »
I did try connecting OS/2 xterm to it, both with 127.0.0.1:0 and :1 and using my IP address. Couldn't connect in all cases. Same with xman, which is pretty simple.
While the exact software configuration is unclear, the "xhost +" line in the props file is likely commented out by default. This must be enabled to allow external access. On the Linux system, you need to point the DISPLAY variable to the OS/2 machine's IP address using the terminal:

export DISPLAY=[IP-Address]:0
Afterward, running xterm will redirect the output as intended.

If you are working from an active XFree86 session on OS/2, set weirdx.displaynum=1 in the props file, as display 0 is already occupied. Even in this case, the DISPLAY variable must be initialized in the terminal first.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5735
  • Karma: +150/-1
Re: Java applications
« Reply #437 on: March 19, 2026, 02:06:37 am »
Not sure what "props" file you are referencing. And you don't need to set %DISPLAY% if you pass it on the command line, -display xxx.xxx.xxx.xxx:1 or for XFree/2, -display :0 to use pipes instead of tcp/ip.
I simply used PATH and BEGINLIBPATH to set things up and trying to run something like xterm (which complains about being suid-root,
Code: [Select]
[H:\tmp]xterm -display 127.0.0.1:0
_X11TransSocketINETConnect: Can't connect: errno = 61
_X11TransSocketINETConnect: Can't connect: errno = 61
_X11TransSocketINETConnect: Can't connect: errno = 61
_X11TransSocketINETConnect: Can't connect: errno = 61
_X11TransSocketINETConnect: Can't connect: errno = 61
_X11TransSocketINETConnect: Can't connect: errno = 61
This usually works with various Xservers, bitchX, HOBX11, as long as you get the screen right. As no other X server is currently running here, :0 should be correct but I did try :1.
Hmm, just tried 2 with "xclock -display 127.0.0.1:2 and xclock appeared in the WeirdX window. Weird it would be using screen 2.
Not everything runs, no xterm, or even xman. mwm and twm do run. Hmm, need various gccxxx.dll's and X11ROOT set and more run. been a long time. X doesn't work on a UEFI install and here, on a BIOS install it broke when I changed from VGA cable to Displayport.

P.R.

  • Newbie
  • *
  • Posts: 12
  • Karma: +3/-0
Re: Java applications
« Reply #438 on: March 19, 2026, 10:29:01 pm »
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.

Dave Yeo

  • Hero Member
  • *****
  • Posts: 5735
  • Karma: +150/-1
Re: Java applications
« Reply #439 on: March 21, 2026, 06:06:26 am »
Originally, I was just running the jar file Martin posted. Now that I have downloaded the archive, the props file is setup with "weirdx.displaynum=2", probably the default.
X won't run on UEFI as the video BIOS is in the wrong place (address). I thought of trying to fix it a couple of years back, managed to setup the right environment and compiled it, but the xserver always failed to run with an out of memory error. Shame as I was also wondering about back porting a newer video module.
X also won't run here using display port__>DVI, though it did run with a VGA cable, and I'm too lazy to change the cable.
xterm is now giving a better error here,
Code: [Select]
[F:\usr\X11R6]xterm
Unable to open \dev\ptyp0, errno=5
Not sure how or if possible to have a ptyp in weirdx. eterm dies here with the wrong jpg.dll.
The gimp does start up here and wants to configure itself. Haven't gone further.
Be aware, a lot of these ports want %HOME% to use slashes instead of backslashes as a directory separator. Probably other ports are happier with slashes. It's EMX.
I see you have a port of Mosiac, don't remember seeing that. I do have Warpzilla (Mozilla 0.98) and it runs in Weirdx. Can't do much with it as the SSL/TLS stuff is so old. Could give you a copy if you want.
I couldn't get any screen shots, what are you using?