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

Pages: 1 ... 11 12 [13] 14 15 ... 19
181
Programming / Re: New OS/4 kernel :: SVN4227
« on: January 07, 2016, 11:09:38 am »
Beyond just that very selfish reason above, here is a more precise one: if the /ST=0 parameter in the ACPI.PSD drive does in fact get ignored, and the authors have set some arbitrary value for the size of the stack, then I would consider this to be a defect. So if the OS4 team patches the binary to actually correct this behaviour then I'm actually questioning why the "core" OS2 maintainer team refuses to fix the code itself?

The case is a bit more complicated. OS/2 kernel offers to PSD very small stack (2672 bytes). It is ok for os2apic.psd and  it looks like not enouph for ACPI.PSD. That is why ACPI.PSD does some actions to increase PSD stack offered by the kernel. It is not an easy thing since PSD stack is organized on per processor base. At the same time ACPI.PSD recognizes /ST key to set desirable PSD stack size on user demand.  ACPI.PSD does not allow the user to set stack size = 0 (as it is really senseless), but if one finds a way (the patch helps) to set "ST=0", ACPI.PSD will not go through the procedure of increasing PSD stack offered by the kernel.

OS/4 starting from svn ver 4250 has unified PSD/interrupt stack with 12k size thus ACPI.PSD has no need to increase it. At the same time, "not easy" ASPI.PSD procedure for increasing PSD stack, simply spoils internal data structure of OS/4 kernel. That is way ACPI.PSD has to be patched and /ST=0 has to be used in order to work with OS/4.

182
Programming / Re: New OS/4 kernel :: SVN4227
« on: January 06, 2016, 12:21:22 am »
With due respect to you, I can't agree with all your statements.

Suggesting anything to the OS4 team is lost ground.

On the contrary. OS/4 team will gladly hear reasonable advice, suggestions, bug reports, etc.

They have given NO reason whatsoever why they removed something that worked just fine and that is WELL DOCUMENTED to exist.

May be one day trace facility will be re-enabled.

What they do is wasting time but of course they can waste all the time they want, after all, it's their time.

There are people who use OS/4 and find it useful. Moreover, there are several HW where the original kernel wasn't able to run at all(in any configurations with any loaders), only OS/4 could run there. Thus OS/4 isn't that much of a waste of time as it may seem.

183
Programming / Re: New OS/4 kernel :: SVN4227
« on: January 04, 2016, 09:37:15 pm »
It remains a secret of the OS4Krnl developer team why they removed the trace and strace facilities.
Without that none of the USB drivers can be traced as they are making good use of OS/2 built in tracing mechanism. Tracing is about the only chance for a developer to do offline analysis of problems surfacing at the user's site (unless you want to recode your own tracing facility).

I have never use trace facilities, same time KernPrintf was sufficient  to debug clock03 and some other drivers.

184
Programming / Re: New OS/4 kernel :: SVN4502
« on: January 02, 2016, 10:42:13 am »
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:

Code: [Select]
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:
Code: [Select]
if (ST==0)
{
    ST=4096
}

patch makes this code out of it:
Code: [Select]
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 ;) )

185
Programming / Re: New OS/4 kernel :: SVN4502
« on: December 25, 2015, 08:56:14 pm »
OS/4 kernel svn4502 is released. The changes have occurred mostly in clock$.
If HPET is available in the computer, clock$ will use it for providing DosTmrQueryTime/Freq with 64bit time stamp.

186
Programming / Re: New OS/4 kernel :: SVN4227
« on: December 20, 2015, 09:46:19 pm »
OS/4 kernel svn4500 is released. Starting from this ver OS/4 kernel loads clock03c.sys instead of  clock03b.sys
New clock driver is in a package with kernel.

187
Programming / Re: New OS/4 kernel :: SVN4227
« on: August 27, 2015, 07:39:23 pm »
 OS/4 tested HW list is updated http://www.os2world.com/wiki/index.php/Phoenix_OS/4#OS.2F4_Tested_Hardware_List

current   svn version  is 4410

188
Applications / Re: Firefox 31.8.0 Beta 5 - First Impressions
« on: July 25, 2015, 12:06:46 pm »
Have just tested it too.  What I have seen - works ok, except for video from YouTube -
the sound is very slow  and video is also very slow - so it is unusable for YouTube.

FF24 works ok  with YouTube on my system.

189
General Discussion / Re: News from the front line
« on: July 11, 2015, 05:44:43 pm »
I'm running now 24.8.1and have 206Mb left for use.

try to mark dlls so they are loaded  into high mem

190
Programming / Re: os2krnlSVN4375_unoff.zip with Trap 0008
« on: June 28, 2015, 12:57:31 pm »
Hi,

catching Kernellog works fine here.  :D

Wim's COM1GET.CMD works out of the box!
DTerm works fine also after adjusting the baudrate with ctrl+b to 115200.

If of interest, here is the log.

it looks ok

191
Programming / Re: os2krnlSVN4375_unoff.zip with Trap 0008
« on: June 26, 2015, 06:08:26 pm »
shouldn't the switch be /ST=0???
as you added /ST0

Thanks a lot !!! :)  I really missed that.

/ST=0 did the trick!
The trap is gone!

For the case that debugging should be necessary in the future, has ecs a required terminalsoftware on board?

congratulation,

for debugging you can use  ZOC  as "terminalsoftware"
same time you terminal can work under windows or linux

do not hesitate to update http://www.os2world.com/wiki/index.php?title=Phoenix_OS/4&action=edit&section=3 if you realized that you have learned something new 

192
Programming / Re: os2krnlSVN4375_unoff.zip with Trap 0008
« on: June 26, 2015, 04:20:02 pm »
This is a native installation. T60 has no comport but dockingstation has.
I never before tried this.
What do I need? Nullmodemcable? Terminalsoftware?

1.) docking station
2.) com to com cable (null modem cable)
3.) another computer with com port and terminal software

show you os2ldr.ini and config.sys

193
Programming / Re: os2krnlSVN4375_unoff.zip with Trap 0008
« on: June 26, 2015, 03:43:14 pm »
ACPI.PSD was not patched.

Now ACPI3_22_03.PAT is done on ACPI.PSD.
Config.sys reads: PSD=ACPI.PSD /ST0 /VW
The problem is still there, same trap at startup.  :(

can you show me comport log ?

194
Programming / Re: os2krnlSVN4375_unoff.zip with Trap 0008
« on: June 26, 2015, 02:08:48 pm »
Hi,
this is my first try of OS4-System. Installation is done as described.
The system stops after:

Internal revision 15.1_SMP.4375
Loading: oemhlp.bpd ....Ok
Loading: acpi4.bpd File not found or corrupted

 PIC mask = 0xFFFB IF = 1
TRAP 0008
...
location ##0168:fff9b56c - 000f:0008f56c
3443, 0 trap.asm

System is a T60 with 3GB RAM
Config.sys is unmodified.
What is acpi4.bpd?

hi

I hope, that if you are using an acpi.psd than it has been patched and the /ST=0 is added   -  pls check and confirm

acpi4.bpd  is an experimental acpi driver for os/4 kernel  and not obligatory

regards

195
My priorities are having a decent browser and good multimedia (especially video) support.

+1

Pages: 1 ... 11 12 [13] 14 15 ... 19