But please just do not try just as a short in the dark. That is what you are doing.
Can you rewrite this line? I don,t undertand it.
I would strongly recommend not changing these settings... Why I have not seen ANYBODY ever changing these settings.
Stability increases me and the system improves. Are you suggesting that I don't modify anything, and that 50% of the startups fail with a system crash?
Did you disable hyperthreading ? Can you upload a testlog generic ?
From what I have seen, some computers work better with hyperthreading ON, and others work better OFF. For me that is a myth.
What I have seen in some Bios, is that they have an option to select Legacy mode, or Modern hardware option.
In legacy mode, the dbexpert works perfect, but a lot of programs do not even open, Lucide...., in Modern hardware is more compatible with all programs, but the dbexpert sometimes closes unexpectedly.
I attach a generic testlog
Saludos
I mean it comes across as if you are just taking a gamble. As I typed I have never seen anybody else change the settings you just mentioned.
What do you base it on it fixes your system ? You are most likely changing the timing and you get lucky.
If you consider that a fix, well its work around...
Did you notice that your system did install (phase 1 and phase 2). There is reason this works..
Because the PSD runs with /MAXCPU=1. There is only one CPU core active when the installer runs...
Look its a free world. But all information indicates switching on hyperthreading with OS/2 is simply not recommended.
Its already known for years that supporting hyperthreading would require kernel changes. The testlog you send states:
More CPUs (

than cores (4) detected.
HyperThreading/SMT can cause problems for OS/2 systems.
*** This system has a configuration that may cause system problems and may make
*** it difficult or impossible to provide support.
It might run better is your experience. But you are going against the advise of David from A.N. who did most of the work on the ACPI.PSD.
Again its a free world but hyperthreading in genereal is not recommended with OS/2.
It seems hyperthreading on OS/2 on modern systems seem to work, but the cause is unknown. In the past we have seen systems hang at the bootlogo or when PM comes up, or just freeze while the system is running.
Hence the genereal recommendation turn off hyperthreading.
Now do you use startup.cmd or the startup folder to start any programs ?
I would recommend for now to keep the virtualaddresslimit set to 2048 and not 3072.
One other thing I noticed (which I can not explain) is this:
----- Contents of file: C:\var\log\xwptrap.log ---------------------------------
*** Excessive file size truncated. Showing the last 20000 bytes. ***
0065F940: 0065F624 PMMERGE 00:FFFFFFFF
0065F150: 0065F4C4 PMMERGE 00:FFFFFFFF
0065F940: 0065F624 PMMERGE 00:FFFFFFFF
0065F150: 0065F4C4 PMMERGE 00:FFFFFFFF
0065F940: 0065F624 PMMERGE 00:FFFFFFFF
0065F150: 0065F4C4 PMMERGE 00:FFFFFFFF
Look we are more then willing to help you, but please provide more information. You write an email that you are not happy with 5.1.0. Then state you modified a setting and that seems to make it work... But little to no information what you did to your system after install
Do a new install either UEFI or legacy and make a small log what you modify on the system.
And please answer this question:
Now do you use startup.cmd or the startup folder to start any programs ?|
Roderick