Recent Posts

Pages: [1] 2 3 ... 10
1
Internet / Re: Problems with OpenSSL library after update.
« Last post by Steven Levine on Today at 04:51:55 am »
Oops - wrong repo and wrong branch.  In the current netlabs sources, the code has moved to crypto\cpuid.c.

Some of the interesting code points are at

crypto\cpuid.c:18
unsigned int OPENSSL_ia32cap_P[4];

crypto\cpuid.c:110
    if ((env = ossl_getenv("OPENSSL_ia32cap")) != NULL) {
        int off = (env[0] == '~') ? 1 : 0;

poly1305-x86.pl:119
      if ($avx>1) {
   &mov   ("ecx",&DWP(8,"edi"));
   &test   ("ecx",1<<5);         # AVX2?
   &jz   (&label("no_sse2"));

Since vmovdqa is an AVX2 instruction, we want to turn off

  bit #64+5 denoting availability of AVX2 instructions;

to disable the problematic code path.

The brute force

  set OPENSSL_ia32cap=:0

should do this.  The less brutish

  set OPENSSL_ia32cap=:~0x20

should also work, but might leave other problem code paths enabled.
2
Internet / Re: Problems with OpenSSL library after update.
« Last post by Dave Yeo on February 07, 2026, 05:41:38 pm »
Looking at the configure options, of interest,
Code: [Select]
# no-asm        do not use assembler
...
# 386           generate 80386 code in assembly modules
# no-sse2       disables IA-32 SSE2 code in assembly modules, the above
#               mentioned '386' option implies this one

Attempting to build the RPM, I've got to,
Code: [Select]
Configuring OpenSSL version 3.4.1 for target os2
Using os-specific seed configuration
syntax error at (eval 25) line 102, near ",
)"
Missing right curly or square bracket at (eval 25) line 104, at end of line
Created configdata.pm
Running configdata.pm
Can't locate OpenSSL/fallback.pm in @INC (@INC contains: K:/util/perl /@unixroot/usr/local/lib/perl5 /@unixroot/usr/local/share/perl5 /@unixroot/usr/lib/perl5/vendor_perl /@unixroot/usr/share/perl5/vendor_perl /@unixroot/usr/lib/perl5 /@unixroot/usr/share/perl5 .) at configdata.pm line 36239.
BEGIN failed--compilation aborted at configdata.pm line 36239.
error: Bad exit status from /@unixroot/var/tmp/rpm-tmp.ywakbN (%build)


RPM build errors:
    Bad exit status from /@unixroot/var/tmp/rpm-tmp.ywakbN (%build)

Need to continue adding Perl stuff and hopefully get around the syntax error.
3
Internet / Re: Problems with OpenSSL library after update.
« Last post by Digi on February 07, 2026, 11:48:28 am »
It appears it should be possible to configure OPENSSL at runtime to avoid attempting to use the problematic code via the OPENSSL_ia32cap environment variable.

I've been playing around with different values ​​for this variable, but so far without success.

For the curious, the relevant code is at

crypto\cryptlib.c:694
    if ((env = getenv("OPENSSL_ia32cap"))) {

in the netlabs openssl sources.

I don't see such a line in file https://github.com/bitwiseworks/openssl-os2/blob/master/crypto/cryptlib.c . There are only 282 lines.
4
Internet / Re: Problems with OpenSSL library after update.
« Last post by Steven Levine on February 07, 2026, 06:55:23 am »
It occurred to me that we might not be the only platform that might bump up against this kind of compatibility problem, so I went hunting.

It appears it should be possible to configure OPENSSL at runtime to avoid attempting to use the problematic code via the OPENSSL_ia32cap environment variable.

See

  https://docs.openssl.org/1.1.1/man3/OPENSSL_ia32cap/#description

and

  https://stackoverflow.com/questions/40091888/how-to-disable-avx-instructions-in-openssl

For the curious, the relevant code is at

crypto\cryptlib.c:694
    if ((env = getenv("OPENSSL_ia32cap"))) {

in the netlabs openssl sources.

5
Applications / EmTec Network Suite 5.0.8a
« Last post by Martin Iturbide on February 07, 2026, 01:51:20 am »
Hello

I contacted Markus Schmidt from EmTec and he made a recompile of his "EmTec Network Suite".
It has USENET, FTP and Gopher software, now freeware. FTP does not has SSL. Markus told me it can be open sourced if I get permission from Thomas Bradford. I sent him an email, but I'm not sure if he still has that one.

The idea is to test the software a little bit and I will upload it to hobbes as the latest version.

Regards
6
Graphics and Window Design / Re: Bigicons-Alt_options_config_pngs
« Last post by David Graser on February 06, 2026, 06:44:00 am »
blue screen - set 20
7
Internet / Re: Problems with OpenSSL library after update.
« Last post by Dave Yeo on February 04, 2026, 06:55:17 pm »
Yes, the long term plan is to move GCC to compiling to ELF, which it is already capable of. Wlink in theory can link ELF files to OS/2 executables and does mostly work for C programs. CPLUS is another matter. As well other parts of the toolchain would need updating. Need a skilled programmer that is interested.
As for OpenSSL, another option might be not using the assembly code. Haven't looked at OpenSSL, but generally these projects have C code as well as assembly with the C code being a fall back for times when there is no assembly available like using a different CPU. Be slower and need to recompile the library.
8
Internet / Re: Problems with OpenSSL library after update.
« Last post by OS4User on February 04, 2026, 05:29:59 pm »
It is a bit tricky case.

OS4Team added (may be 7 years ago or more) AVX support on user`s request and it works fine. Of course, the application which is supposed to use AVX has to be compiled and linked properly. It means all the data has to be aligned in accordance with the AVX requirements.

My investigation has shown than we can reach the necessary alignment but we have to provide the following:
 - compilation has to be done to ".elf"  (not ".obj")
 - the linker has to understand ".elf"

These two are very far from OS4Team interest and activity. What OS4Team can do to help  is only remove AVX support, but for me it sounds stupid.
9
Hardware / Re: Serial Port Shenanigans - ArcaOS 5.1.1 on a Lenovo M920t
« Last post by AmbulatoryCorpse on February 04, 2026, 11:43:11 am »
Thanks for the FOSSIL overview.

I am a little confused by the vmodem vs physical modem stuff, but I have a very wild, shot in the dark, suggestion. 

The sio package includes a serial port emulator service (vmodem.sys) and a telnet server (vmodem.exe). Between them they can create around 250 virtual serial ports that interact with bbs software to handle guests from the internet parallel to actual physical phone lines. Default it provides 4, effectively emulating a 4 port multi serial card with modems.


Try switching on CSM AND limiting your system to a single processor and see if SIO will run.  To limit to a single processor add /MAXCPU=1 to the ACPI.PSD line in CONFIG.SYS, e.g.

PSD = ACPI.PSD /MAXCPU=1

The reason I suggest this is the COM.SYS on my AOS 5.1 system is dated 8/3/2002 and SIO2K was released 6/6/2002, so they were both revised/released about the same time, suggesting that maybe the issue isn't in the COM stack/driver/interface but rather someplace else.

One processor should still be fast enough to handle multiple BBS "lines" - after all people were running multi-line BBS on machines before there were multi-core processor machines.


At this point I'm pretty sure what I'm running into is sio trying to use things that aren't present in the modern LPC bus, but would be present in the ISA bus that the OS says it's talking to. I think proper fixes could be someone writing a replacement for (parts of) sio or someone writing an updated ISA driver that can recognize LPC emulating ISA then fix up other things. I'm trying to make sense of technical information beyond me, so yeah.

At any rate I will try apci and orther suggestions when I next have time.
10
Hardware / Re: Serial Port Shenanigans - ArcaOS 5.1.1 on a Lenovo M920t
« Last post by Doug Clark on February 03, 2026, 06:14:57 pm »
Thanks for the FOSSIL overview.

I am a little confused by the vmodem vs physical modem stuff, but I have a very wild, shot in the dark, suggestion.  Try switching on CSM AND limiting your system to a single processor and see if SIO will run.  To limit to a single processor add /MAXCPU=1 to the ACPI.PSD line in CONFIG.SYS, e.g.

PSD = ACPI.PSD /MAXCPU=1

The reason I suggest this is the COM.SYS on my AOS 5.1 system is dated 8/3/2002 and SIO2K was released 6/6/2002, so they were both revised/released about the same time, suggesting that maybe the issue isn't in the COM stack/driver/interface but rather someplace else.

One processor should still be fast enough to handle multiple BBS "lines" - after all people were running multi-line BBS on machines before there were multi-core processor machines.
Pages: [1] 2 3 ... 10