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 - Lars

Pages: [1] 2 3 ... 96
1
Setup & Installation / Cannot update python
« on: May 12, 2025, 08:34:13 am »
Hi there,

I am offered python3 update to 3.13.2.-1. ANPM properly download all dependencies but fails with a "depsolve" problem.
I have tried both, copy python2.7.exe to python.exe and also python3.9.exe to python.exe but it fails anyway.
How do I force installation ? Obviously, I cannot do that from ANPM but a simple "yum update" does not offer such a thing as a --force switch.

2
Setup & Installation / Re: Troubleshooting process trap/dump...how?
« on: May 05, 2025, 06:12:12 pm »
1) you will need LOGDAEMON.EXE so that (Ring 3) applications can use the "LogAddEntries" API to write to the System Log. Not many apps need it but it does not hurt to have it running. "LogAddEntries" API is only documented in the Debugging Handbook.

2) you will need LOG.SYS so that Ring 0 device drivers/IFS etc. can use the DevHlp_LogEntry device helper to write to the System Log. It is also required by LOGDAEMON.EXE to operate. Not many device drivers use it (if any) but it does not hurt to have it running

3) You can safely remove all that EP... stuff as it is the outdated FFST stuff which has been superseded long ago, see here:
https://www.edm2.com/index.php/First_Failure_Support_Technology/2
From the list, only keep the following as actually, that is the new FFST stuff (I will need to recheck just to be sure):
FFST.EXE
FFSTCONF.EXE
FFSTPCT.EXE
ERRLOG.DLL
FFCONFIG.DLL
FFDUMP.DLL
FFGUI.DLL
FFIPC.DLL
FFPCT.DLL
FFPROBE.DLL
FFST.DLL
FFST.HLP

4) FFST.EXE is the system log daemon, it is started by SMSTART.EXE (see what THESEUS.EXE reports). It seemingly replaces EPWDDE3.EXE, EPWROUT.EXE, EPW.EXE.

5) Finally, FFST.DLL contains routine "FFSTProbe" which effectively supersedes "LogAddEntries" (see above) to write to the System Log but both still coexist where "LogAddEntries" is easier to use but requires a handwritten DLL to format the logged data where "FFSTProbe" uses a text template formatting approach that however is overly complicated.



3
Setup & Installation / Re: Troubleshooting process trap/dump...how?
« on: May 05, 2025, 08:06:04 am »
Hi Dariusz,

you are not alone with the "my system suddenly reboots without any trace" problem. I have experienced the same more than once.

1) you are using a very outdated version of FFST (RUN=G:\OS2\EPWDDR3.EXE, DEVICE=G:\OS2\EPWDD.SYS) that predates the stuff that came with  Warp 4 (and after, of course). Do not do that. I suggest to deinstall it. >= Warp 4 comes with everything you need.

2) Lower your VIRTUALADDRESSLIMIT value. I suggest to start with 512 (which is the lowest value and equivalent to having no high memory at all) and then, raise up to a value that is still lower than your current value. If 512 is too low, you will need to start with a value that works for your system. VIRTUALADDRESSLIMIT can only be raised in chunks of 512 MB (0x20000000). XWorkplace kernel object will only select values that are possible. The default value for VIRTUALADDRESSLIMIT is 1024 (MB).

My suspicion is that 2) is the most likely culprit. The problem with a too high value is that OS/2 seemingly can run into problems on memory allocation (be it the system arena located above the VIRTUALADDRESSLIMIT value, or the user area below this value). And OS/2 does a very bad job of detecting this problem with the result that it does not even stop with a critical error message and a system trap dump. Obviously, the failure to allocate memory in the system arena is a fatal problem that renders the system completely unusable.
An alternative behaviour to these sudden reboots seems to be a complete system freeze (with the same effect as if all HW interrupts are being disabled).

Lowering this value has still not completely eliminated the problem for me but it has lowered the frequency with which these sudden reboots occur.

4
Setup & Installation / Re: PYTHON - v2 vs v3 and dependencies...
« on: April 27, 2025, 07:36:47 pm »
ANPM comes with Python2 scripts to begin with.

5
Setup & Installation / Re: PYTHON - v2 vs v3 and dependencies...
« on: April 27, 2025, 05:34:42 pm »
You have already identified the problem: your python.exe is the same as python3.9.exe.
Just copy python2.7.exe over python.exe and you are fine.

6
Setup & Installation / Re: PYTHON - v2 vs v3 and dependencies...
« on: April 27, 2025, 05:03:28 pm »
Make sure that in your \usr\bin directory, you copy python2.7.exe to python.exe (if not already done). Nothing else ever worked for me.
And yes, I also have python 3 installed as I can find python3.9.exe within that same directory. But as I said, using Python3 will only get you into trouble.

7
Applications / Re: EXIFTool
« on: April 23, 2025, 05:40:38 pm »
I think that would just ask for desaster if you already have Perl installed via YUM/RPM.

You would have an outdated Perl installed via WarpIn alongside an up-to-date installation via YUM/RPM without really knowing what is being used by the EXIF tool.

The best way would be to remove the idiotic dependency in the WIS script. Unfortunately, I have no time to do it and for the time being, Steve's suggestion is likely the way to go forward.

8
Applications / Re: EXIFTool
« on: April 23, 2025, 01:47:49 am »
As I mentioned elsewhere: the WPI package script needs rework to get rid of the dependency on the Perl WPI package as Perl is now delivered via YUM/RPM.

9
Programming / Re: DOSBox-x - infinite loop in configure/make
« on: April 20, 2025, 02:30:10 pm »
Just a guess: try DID_DIRECTORY_SELECTED.

10
Applications / Re: SSL update: Firefox XUL.DLL can no longer load
« on: April 18, 2025, 01:24:16 pm »
No ssl3.dll im my Firefox directory (containing xul.dll, lgpllibs.dll, mozdqlt3.dll).
Either AN provides ssl3.dll together with their delivery of Firefox or maybe you copied it over yourself.

11
Applications / Re: SSL update: Firefox XUL.DLL can no longer load
« on: April 18, 2025, 12:20:35 pm »
Thanks, that did the trick. I still wonder why "ssl3.dll" got lost on my system.

12
Applications / SSL update: Firefox XUL.DLL can no longer load
« on: April 18, 2025, 12:01:12 pm »
Hallo,

I updated openssl just a few days ago. Now XUL.DLL (part of Firefox) can no longer load as it complains that ssl3.dll is missing which is true.
Is there a newer build of XUL.DLL that uses the updated SSL11.DLL ? Or maybe a newer delivery of Firefox ? I have no AN account.
What I can also find on my system is "ossl3.dll" but not "ssl3.dll". I doubt that I can simply rename the file as the internal DLL name is "ossl3".


13
Multimedia / Re: Updated Uniaud32 build
« on: April 16, 2025, 03:40:33 pm »
Thanks Sigurd, I'll have a look at these a bit later. I've just been thinking about this part of your testlog:
Code: [Select]
Period size min=2f0 max=2f0
Error -22 second time.. Bailing

This comes from:
https://trac.netlabs.org/uniaud/browser/GPL/branches/uniaud32-exp/lib32/sound.c#L1015
& https://trac.netlabs.org/uniaud/browser/GPL/branches/uniaud32-exp/lib32/sound.c#L1025

Error -22 is EINVAL or Invalid Parameter. This suggests that one of the parameters set between https://trac.netlabs.org/uniaud/browser/GPL/branches/uniaud32-exp/lib32/sound.c#L965 & https://trac.netlabs.org/uniaud/browser/GPL/branches/uniaud32-exp/lib32/sound.c#L995 are causing the problem. The trick is know which one.

What I might do is create a specific build which writes each parameter one by one so we can see which one causes the issue.

The logic is really twisted. Without any evidence, I would think that it is possible that:
"periodbytes*nrperiods"
might exceed
"bufsize = hw_param_interval((&params), SNDRV_PCM_HW_PARAM_BUFFER_BYTES)->max;"
which of course is forbidden.

Maybe you can print out these values to begin with.

14
Multimedia / Re: Updated Uniaud32 build
« on: April 16, 2025, 02:36:50 pm »

@Lars - I think about it once again, regarding differences in hardware - the only thing I did during testing was switching form 16 to 1 CPU (/MAXCPU=1 Switch in config.sys). Do not know, if that effect things in any way


The kernel will create one management structure per CPU. If you have 1 CPU instead of 16 (known to OS/2, I mean), that will likely make a difference.

15
Multimedia / Re: Updated Uniaud32 build
« on: April 15, 2025, 06:47:16 pm »
ok, thanks.

For the 2 trap screens that you posted, that means:

trap screen 1: EIP = E1DA82E1 -> what ??? Have you run this on another computer or have you changed configuration ?

trap screen 2: EIP = E5D780A2 -> offset = E5D780A2 - E5CDB000 = 9D082

I find this in the MAP file:  0003:0009D072       component_match_add_release_

That would mean the trap occurs in "component_match_add_release". Provided that the (debug) MAP file is close enough to the binary the trap occured in.

Pages: [1] 2 3 ... 96