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 - Andi B.

Pages: [1] 2 3 ... 43
Applications / Re: Test build of dooble with qt5
« on: May 03, 2022, 11:38:40 am »
....deserve a very focused HowTo once the origin of their actual weakness -I see not being the only one having troubles- will be determined...
Guess this has to be done by people how actually have problems and a solution. Maybe a wiki page? People like me can't contribute much as it simply worked.

Applications / Re: Test build of dooble with qt5
« on: May 03, 2022, 09:54:46 am »
Hope that at final phase of all testings, a guide will explain the complete set of software/configuration needed to make it work well.

Here it was that easy as I could imagine it could be. yum install dooble -> installed only this one package. After that it worked. Other programs still work too. No problem with AOO, Seamonkey, Thunderbird, ... all works well. Probably cause I kept my system up to date before. And I had installed simple browser before.

Applications / Re: Test build of dooble with qt5
« on: April 26, 2022, 09:10:37 am »
I do not have a \var\log\app directory or any trp files anywhere in my \var\log directory.
Where does your LOG environment variable point to? 'set log' or 'echo %log%'

Networking / Re: Test build wpa_supplicant v2.7 - v2.10-devel
« on: April 04, 2022, 01:22:56 pm »
You pushed via ssh? Or https? Have to check if there are new certificates at netlabs-exp. Usually I'm very careful with -exp stuff. 

Networking / Re: Test build wpa_supplicant v2.7 - v2.10-devel
« on: April 03, 2022, 01:21:15 pm »
I never activated two factor authentication so no problem. Only issue at sourceforge is I have to use git from command line. SmartGit don't work. At least I cant get our ancient version to work. When pushing from cli I've to type the password at command line. Link https://username:password@sourceforge... does not honor the password. Pushing via SSH doesn't work for me too. Some /nonexistant/known.sites (?) error. No clue if it's our ssh or my setup. I've never used ssh before so probably the problem is my missing knowledge.

It took a while until sourceforge showed up my content. Your cc-os2 looks fine.  At least to my not very experienced eyes ;-). I see the '' build. Is this the stable one with inline nss*? I'm still using your SeaMonkey/2.42.9esr Build-Identifikator: 20190520220003 cause this is the most stable here.

Edit - should have read your comment first before posting.

Btw. sometimes I'm very pissed off from all these pseudo-security nonsense with tons of javascript and redirection to foreign sites. Just renewed my ArcaOS subscription and was pleased to see that you can simply pay with credit card by using your basic card data and click pay. Here in Europe you've all these crappy, expensive 3 way authentication now. Name, number, expiration date, security number, link to other site, even more secure-secure-secure password, and finally a sms tan. Stupidly complex. Payment can be so simple without all these overkill.

Networking / Re: Test build wpa_supplicant v2.7 - v2.10-devel
« on: April 02, 2022, 07:41:59 pm »
Yes did the same in the meantime -

Seems bitbucket locked us out since March 1. I've problems with ssh to sourceforge too. But https still works there. At least from command line. SmartGit doesn't work :-(

Networking / Re: Test build wpa_supplicant v2.7 - v2.10-devel
« on: April 02, 2022, 05:49:08 pm »
Official v2.10 for other platforms is out for a while now. I started to port it to OS/2 immediately after it was released. There are a lot of changes but I think no really important things for us compared to my latest release. Anyway I wanted to make this official release available for us too. But there is a problem which I stuck currently so I can't say if or when I can finish 2.10 release. Problem is the current code needs a lot of time to establish a wpa2 secured connection here. Definitely longer then with my previous release. Sometimes it seems it takes forever. I'm currently stuck with this problem.

I've done a lot of ifdefs for IPv6 code. Although there is a compiler switch for IPv6 these were missing. It seems on other platforms they can't imagine that there are still platforms out there without IPv6 support. Although my current code compiles fine this 'long time to connect' problem drives me crazy. No clue if it's a problem with our genmac driver or some porting issue. Anyway if anyone wants to play with the code and help to debug (reading and interpreting wpa_supplicant debug messages) drop me a mail. I'll update the source code at my bitbucket git repository. But there are some test code which needs to cleaned up once the connection problem is solved before making a release. This is just to keep you informed.

Edit - can't upload to bitbucket anymore -
Code: [Select]
remote: Bitbucket Cloud recently stopped supporting account passwords for Git authentication.
remote: See our community post for more details:
remote: App passwords are recommended for most use cases and can be created in your Personal settings:
fatal: Authentication failed for ''

Tried to setup a ssh key. But it's not possible to add the public key at with our browsers :-(

Edit2 - uploaded current code to

Hardware / Re: Problems Recovering a JFS Drive
« on: March 19, 2022, 08:30:39 pm »
Have you searched the ArcaNoea bugtracker for that? I'm pretty sure this was mentioned there too. I had the same/similar problem a few times, at least the same/similar message. I think there too low memory for running chkdsk.

Applications / Re: XWP v1.0.15
« on: February 25, 2022, 09:25:52 am »
Startup and Shutdown

    XStartup: restart automatically after fixing the order of class-replacements
    XShutdown: add "XWP_ACPIDELAY=xxx" environment variable to change the default shutdown delay of 250ms

Have you read my comment on the ticket? Have you taken my code from the branch or developed your own solution for the same problem?


Networking / Re: USB Modem
« on: February 24, 2022, 06:18:22 pm »
Here in Austria I never got the IBM dialer to work. Injoy did the job for years. But I never tracked down what's the reason.

When I could get to the desktop without a crash or reboot, as soon as I attempted to open the XWLAN monitor the system crashed.  I remember getting a TRAP 000E screen, so that verifies perhaps the problem that was stated regarding XWLAN's power control.

Don't think so.

IIRC trap000E is double fault. Something which happen with genmac sometimes. Guess you've followed all the genmac instructions, did you? I think it is important to have helperw.sys (???) near the top of config.sys.

If you can boot to desktop I would suggest you try the programs in the genmac folder. IIRC there's a ssid.exe and some others. Probably one of them triggers the trap in genmac too.

Programming / Re: gcc - building libarchive
« on: February 06, 2022, 12:00:35 pm »
Built for me with make LDFLAGS=-lpthread V=1 haven't looked at configure closely though it looks like it just checks for pthread.h without actually linking it.
Thanks that did the trick. Had to remove some other xxFLAGS I tried before and sh ./configure. But now it seems to work.

Next step, try to build iii-0.3 (libarchive is a requirement for that).

Programming / gcc - building libarchive
« on: February 04, 2022, 07:11:22 pm »
I try to build *nix library libarchive and get the following error about unresolved '_pthread_mutex_unlock'.

Code: [Select]
  CC       libarchive/archive_write_set_passphrase.lo
  CC       libarchive/filter_fork_posix.lo
  CC       libarchive/xxhash.lo
./libtool: 2643: ./libtool: func__fatal_error: not found
weakld: error: Unresolved symbol (UNDEF) '_pthread_mutex_unlock'.
weakld: info: The symbol is referenced by:
weakld: error: Unresolved symbol (UNDEF) '_pthread_mutex_lock'.
weakld: info: The symbol is referenced by:
Ignoring unresolved externals reported from weak prelinker.
Error! E2028: _pthread_mutex_lock is an undefined reference
Error! E2028: _pthread_mutex_unlock is an undefined reference
file P:\dev\ports\libarchive-3.3.3\libarchive\.libs\archive_random.o(archive_random.o): undefined symbol _pthread_mutex_lock
file P:\dev\ports\libarchive-3.3.3\libarchive\.libs\archive_random.o(archive_random.o): undefined symbol _pthread_mutex_unlock
make.exe[1]: *** [] Error 1
make.exe[1]: Leaving directory `P:/dev/ports/libarchive-3.3.3'
make.exe: *** [all] Error 2

"P:\usr\lib\pthread.a" includes these functions. Seems this file isn't linked.

Any ideas?

Setup & Installation / Re: SSD partition miss aligned.
« on: February 03, 2022, 01:55:22 pm »
I already have a 64GB and a 128GB SSD out of order (end of life)
You mean not working anymore? Which manufacturer/type?

Setup & Installation / Re: SSD partition miss aligned.
« on: February 03, 2022, 09:35:18 am »

I use DFsee (or dfsanos2 via minilvm) to create partitions. All my SSDs (including Samsung 860 EVO, 500 GB) work.

OK, but how do you know that your partition boundaries are actually aligned?

Remy's point is that unless you have that 4K alignment, it is known that the performance of your SSD is degraded given multiple memory page reads that occur otherwise (I believe, but easy to find detailed on-line explanation out there).

I do have various SSDs. Samsung Evo 840, 850, 860, Crucial, noname, even one with IDE interface, different WD drives, SanDisk.... Usually when not in a preinstalled Win system they are all partitioned with DFSee. A few with the DFSee engine included in ArcaOS installer. They all work. They all work very fast. They all work reliable as far as I can say using some of them about 10 years now. Of course some are newer so no clue if they all will work in 20 years too.

I measure transfer speed, reading/writing of small and large files and usually compare it to the at that time state of the art other OS. And I'm quite happy with the performance.

But I don't care how DFSee aligns partitions. I guess it does it right. At least in my experience it doesn't do it wrong. If I would fear about some problems with DFSee I would ask in the DFSee group. But I definitely don't complain about a problem I've never seen in any of my systems.

Pages: [1] 2 3 ... 43