1) booting with OS4krnl produces a hard trap right after PMSHELL (I can not tell at all what is going on, so this looks like a candidate for a COM port debug, I need to get this organized though)
Similar stuff sometimes happens on my computer as well. In the comport log it looks like this:
DelayHardError SYS3171: 4 string(s):
Pid 0020 Tid 0001 Slot 0045 HobMte 053A
C:\OS2\PMSHELL.EXE
c0000005
1f93b94a
P1=00000002 P2=0003ff14 P3=XXXXXXXX P4=XXXXXXXX
EAX=00000000 EBX=1f93b93c ECX=00040028 EDX=0004f564
ESI=00000000 EDI=0004f3f4
DS=0053 DSACC=d0f3 DSLIM=ffffffff
ES=0053 ESACC=d0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC=**** GSLIM=********
CS:EIP=005b:1f93b94a CSACC=d0df CSLIM=ffffffff
SS:ESP=0053:0003ff18 SSACC=d0f3 SSLIM=ffffffff
EBP=00040054 FLG=00010206
PMWP.DLL 0001:0000b94a
This happens once every 100 boots approx. I don't know the reason and it happens much later after the init of the kernel has finished.
It's possible that it's some old bug that has no relation to OS/4. I remember on the original kernel there sometimes happened situations when there appeared PMshell background and nothing more. Somebody offered a solution with organizing a kind of delay before PMshell start, but I cannot find that post.
Of course, this can be something else, in this situation comport log should help.
2) booting with OS4krnl but ACPI.PSD produces a trap with a complaint regarding missing ACPI4.BPD file...did some researching here but best I could do was to find an earlier forum post (http://www.os2world.com/forum/index.php?topic=785.0) and having re-read the on-line docs multiple times I still can not tell whether I should be attempting to patch the ACPI.PSD driver with the patch files supplied at the OS4 site (I am guessing the answer is a NO because those patches are meant for 3.22.06 release whereas I'm running 3.22.08 here)
Yes, ACPI.PSD has to be patched and used with /ST=0. Indeed, the patch does very simple thing:
in ACPI.PSD there is something like this:
if (ST==0)
{
ST=4096
}
patch makes this code out of it:
if (ST==0)
{
ST=0
}
thus, if one asks for ST=0 he does get ST=0. I would like to stress that this patch does not "spoil" ACPI.PSD and it still can be used with original kernel.
ACPI4.BPD - it is an optional acpi driver. It is not obligatory for booting the system.
It is true that there are patches only for 3.22.06 and 3.22.03, that's because nobody had asked for something else. If you insist, patch for 08 will also be produced. At the same time you may try OS/4 with 06 (ACPI.PSD only the rest may remain 08)
I will a couple more combinations here, like RETAIL vs DEBUG kernels and /APIC vs none for OS4APIC.PSD driver.
waiting for result (better with comport log

)