Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Dave Yeo

Pages: [1] 2 3 ... 279
Applications / Re: HOBLink and ArcaOS
« on: Today at 03:40:31 am »
While on the subject, I've been testing Xfree86 on the latest beta, basically AOS 5.1. Previously my old install crashed when returning to the WPS, so I started over.
Downloaded all X450*.zip files from, unzipped them to somewhere that is not @unixroot but is \usr, in my case Y:\usr\X11R6, also need \usr\adm. It may work installing to @unixroot\usr but I prefer to avoid it as Xfree86 is EMX and various kLIBC ports might find it and try to use it.
Added device=y:\usr\X11R6\lib\xf86sup.sys to config.sys and rebooted.
My xenv.cmd,
Code: [Select]
set X11ROOT=Y:
set X11PATH=Y:\usr\X11R6
set PATH=%X11PATH%\bin;%PATH%
set DISPLAY=local/127.0.0:0.0
set TERMCAP=%X11ROOT%/usr/X11R6/lib/X11/etc/xterm.termcap
set term=ansi
set logname=dave
set user=dave
set HOME=f:\home\dave
set XSERVER=%X11ROOT%/usr/X11R6/bin/XFree86.exe
SET MANPATH=%X11ROOT%/xfree86/man;e:/emx/man;%MANPATH%

After running it in a cmd prompt, run startx and here everything was correctly probed and I found myself at the X desktop.
It is slightly broken, the window manager twm should have been started and for some reason it isn't. Run start twm in a xterm. Later can install a better window manager.
Ctrl-esc to return to the OS/2 desktop, there are 3 xterms by default, typing exit in the login one will close Xfree86, due to the window manager not starting automatically, the other 2 xterms should also be manually exited, or close them after with the window list or xcentre.
This should give a working X desktop. Note that it will not work on an UEFI install, doesn't like the BIOS and can't probe the screens, so only for a BIOS install.

Log will be written to \usr\adm.
Edit: fix typo

Applications / Re: Rsync and eaclean
« on: March 31, 2023, 07:34:30 pm »
It's easy to test, create a file, lets say a text file with e.exe. It has no EA's. Use a libc program on it, lets say cp to new file, the copy has the EA's.
Knut had plans for the EA's and was very resistant to removing them, unluckily he seems to have lost interest.

I was trying to install original OS/2 Warp 3 with 3.5" floppies.   It has two boot floppies then the CD-ROM.    The floppies work in another system, so I don't think the floppies are bad (they are backups from the original IBM disks).

But on this Gateway Solo 9300 with a Pentium III processor, on disk 2 of the install it gets this crash.  Does anyone know if this is an OS/2 crash error, or if it's a BIOS system related crash?    I thought maybe it was a Gateway system error (the system is from about '98) but this could be from an OS/2 build date ('94 sounds about right year).

Is there any known "Pentium III compatibility error" known with old OS/2 ?

Yes, towards the end, IBM put out various kernel fixes for then current modern hardware such as the PIII. SSE might have been an issue.
You could try the boot disks from, might have to hunt the URL's.
Otherwise, Warp v4+fp15.

Applications / Re: Rsync and eaclean
« on: March 31, 2023, 07:00:59 am »
Just for the record, PMMail does not use EAs. Using RSync to copy the mail store does add EAs to every file.

I don't know why that would cause RSync to use more time to transfer the files.

Isn't PMMail now compiled with GCC/Libc? Libc does add EA's to everything it touches.

Perhaps \os2\system\somd.msg?

General Discussion / Re: PMfax
« on: March 28, 2023, 08:34:20 pm »
Looks like a winmodem, so no, it won't work under OS/2. Something like a USB USR robotics modem will work as the USB interface is presented as a com port.

Programming / Re: Qt6 Development
« on: March 26, 2023, 11:56:30 pm »
Can you build with a prefix of qt6 or /qt6? For now, that seems the best way to keep it separate from @unixroot

I'm actually now not so certain it was the gcc version causing the issues - I reset GCC to the rpm version, and still got errors. I'd also been messing around yesterday on that box wih replacing the i686 versions of libs with the pentium4 ones - so maybe something go screwed up there too.

Perhaps I'll install to @unixroot/usr950 or something to keep it seperate - or just to @unixroot/usr/local ?

Sorry, got confused between Qt and GCC. @unixroot/usr950 or back to @unixroot/local950, nice to have co-existence between different versions as well as the choice of what is on the PATH, @unixroot/usr/local is usually on the PATH, LIBPATH and ahead of @unixroot/usr.

Programming / Re: Qt6 Development
« on: March 26, 2023, 09:08:11 pm »
Can you build with a prefix of qt6 or /qt6? For now, that seems the best way to keep it separate from @unixroot

Well, with SeaMonkey, and IIRC, also Firefox, there's a setting  under Browser-->Link Behaviour, Links from other applications with the choices of the current tab/window, a new tab in the current window or a new window. IIRC, the default is a new window.
To start another browser instance, need the parameter -no-remote along with -profilemanager or -profile=name or such.

I quite like Dooble, it's nice and light... my only complaint now is if I open a link from a Web Folder, it opens a new instance of Dooble rather than open a new tab in the existing instance (and sucks up a bunch of memory). Any of you programmers know if this is something that can be corrected within Dooble, or is it in the nature of OS/2? I could raise an issue on the Dooble github if it is possible to correct there...


Open an issue. Textbrowser is pretty good about implementing things like this, often as a setting. It has the same problem opening from a cmd line, so mention that. I'd assume it has the same behaviour on all platforms.

Programming / Re: Qt6 Development
« on: March 24, 2023, 02:39:43 am »
Probably does need an up to date NSS.
I tried building the RPM, for some reason my environment was rejecting the directive to use the git repository.
Last time I tried doing the proper build, I ran into problems which I now forget. It was a weird build method, build NSPR4, then use that build system to build NSS.
I believe the OS/2 code hasn't been removed from NSPR4 and NSS yet, but Bitwise patched it quite a bit. NSPR4 is sort of a universal libc.

Hardware / Re: Dell KB900 keyboard - workable?
« on: March 23, 2023, 03:10:08 am »
The wireless part should work fine. I've had a few wireless keyboards (no Dell) including where the adapter that plugs into the USB port supports both keyboard and mouse, they've all worked as basic keyboards and/or mouse.

Hardware / Re: AM4 and 570 chips sets
« on: March 22, 2023, 03:39:30 am »
Seems to be mostly done excepting the documentation, which I'd hate to have to write :)  I'm running and it seems pretty solid but my hardware is not the newest.
Looking at the last beta announcement, a few cosmetic fixes and as for TODO, documentation updates.
Possibly other things are happening in their lives, once released, I'm sure there will be a flurry of issues, many from not reading and rereading the documentation.

Hardware / Re: AM4 and 570 chips sets
« on: March 19, 2023, 10:30:09 pm »
Be interesting to try v5.1 on that box when it finally gets released, though not good news if Linux won't install. What was the problem with Linux?

Pages: [1] 2 3 ... 279