Author Topic: OS/4 (technical details only)  (Read 155166 times)

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1316
  • Karma: +26/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #180 on: April 09, 2019, 04:02:38 am »
OS4User!

...How is your testing of acpi4.bpd doing  (hope you've managed to get it) ?

Very well indeed. The test version allows me to use the /APIC switch. I've attached the matching LOG for this run.

The icing on the cake would be if I could finally use the full 6 cores of my Phenom II X6 cpu...however as long as I'm using SNAP that will most likely not happen - I'm hitting the dreaded Blue Screen of death (right before WPS starts up).

Anyways, thank you...I'll put some runtime on this combo and report back!

OS4User

  • Sr. Member
  • ****
  • Posts: 406
  • Karma: +10/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #181 on: April 09, 2019, 06:57:54 am »
Hi

tnx for testing

your system reports about 5 enabled and one disabled CPUs, I do not knot why one is disabled.

however as long as I'm using SNAP that will most likely not happen - I'm hitting the dreaded Blue Screen of death (right before WPS starts up).

you can try http://gus.biysk.ru/os4/test/sddhelp/sddhelp_v01a.RAR and
http://gus.biysk.ru/os4/test/gradd/gradd.sys

David Graser

  • Hero Member
  • *****
  • Posts: 869
  • Karma: +84/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #182 on: April 09, 2019, 09:02:27 pm »
Finally am starting to see some traps with FFSandyBridge. I have attached. trap files.

OS4User

  • Sr. Member
  • ****
  • Posts: 406
  • Karma: +10/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #183 on: April 09, 2019, 09:23:16 pm »
Finally am starting to see some traps with FFSandyBridge. I have attached. trap files.

It looks like you ran FFSandyBridge on noAVX kernel.

By the way, why do you set your VAL so low ?

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1316
  • Karma: +26/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #184 on: April 10, 2019, 01:18:02 am »
hey!

...your system reports about 5 enabled and one disabled CPUs, I do not knot why one is disabled...

I have disabled the 6th core because leaving it in 'enabled' state and not using any APIC parameters to limit the # of cores being used always causes the WPS blue-screen hang, ie: they all get used and that causes some type fo an error. Subsequently I just found it easier to simply disable the core that doesn't actually get used otherwise.

Anyways, alright...I've seen the additional drivers you listed before, wasn't quite sure what to make of 'em before...I'll give these a try and report back.

Thanks again, input is much appreciated!

Dave Yeo

  • Hero Member
  • *****
  • Posts: 4775
  • Karma: +99/-1
    • View Profile
Re: OS/4 (technical details only)
« Reply #185 on: April 10, 2019, 02:03:46 am »
Finally am starting to see some traps with FFSandyBridge. I have attached. trap files.

How long had your system been up when these happened?
OS4user makes a good point about your VIRTUALADDRESSLIMIT. I'd suggest raising it, perhaps to 2560

Edit, actually these trps are the same as I get trying to run the Sandybridge build. I guess due to not using a AVX aware kernel.
« Last Edit: April 10, 2019, 02:13:33 am by Dave Yeo »

David Graser

  • Hero Member
  • *****
  • Posts: 869
  • Karma: +84/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #186 on: April 10, 2019, 03:36:14 am »
Finally am starting to see some traps with FFSandyBridge. I have attached. trap files.

How long had your system been up when these happened?
OS4user makes a good point about your VIRTUALADDRESSLIMIT. I'd suggest raising it, perhaps to 2560

Edit, actually these trps are the same as I get trying to run the Sandybridge build. I guess due to not using a AVX aware kernel.

I had the VIRTUALADDRESSLIMIT remmed out in the config.os4 statement.  Put it back in.

The howto doc stated to rem it out.

CHANGES TO CONFIG.OS4:

    1. REM the following lines out:
        PSD=ACPI.PSD                  (see note about ACPI.PSD usage below)
        BASEDEV=APM.ADD               (it is not compatible with OS/4)
        BASEDEV=TIMER0.SYS            (it is not used with OS/4)
        DEVICE=C:\OS2\BOOT\PmDD.SYS   (PmDDk.SYS will be used instead)
        VIRTUALADDRESSLIMIT=xxxx      (is set in C:\OS2LDR.INI)
        SET NSPR_OS2_NO_HIRES_TIMER=1 (OS/4 provides bugless DosTmrQueryTime)

I must have had some kind of corruption.  FF would come up but not access the internet.  Back leveled kernel and it was working normally.  Tested many other kernels  with the latest test kernel and everything is now working as it should.  What ever happened must have been causing the traps.  Will continue to monitor.  Everything is back to normal.
« Last Edit: April 10, 2019, 03:57:38 am by David Graser »

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1316
  • Karma: +26/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #187 on: April 10, 2019, 04:05:28 am »
OS4User,

...Anyways, alright...I've seen the additional drivers you listed before, wasn't quite sure what to make of 'em before...I'll give these a try and report back....

Nah, no luck.

The replacement drivers result in the same symptom as my normal OS2APIC boot - WPS hang.

I actually suspect this may have something to do with how memory is being allocated during boot, and maybe it's a result of the known SNAP SMP instability (although various parties have said numerous changes were made to the drivers to fix some of this).


Dave Yeo

  • Hero Member
  • *****
  • Posts: 4775
  • Karma: +99/-1
    • View Profile
Re: OS/4 (technical details only)
« Reply #188 on: April 10, 2019, 05:19:02 am »

I had the VIRTUALADDRESSLIMIT remmed out in the config.os4 statement.  Put it back in.

The howto doc stated to rem it out.

CHANGES TO CONFIG.OS4:

    1. REM the following lines out:
        PSD=ACPI.PSD                  (see note about ACPI.PSD usage below)
        BASEDEV=APM.ADD               (it is not compatible with OS/4)
        BASEDEV=TIMER0.SYS            (it is not used with OS/4)
        DEVICE=C:\OS2\BOOT\PmDD.SYS   (PmDDk.SYS will be used instead)
        VIRTUALADDRESSLIMIT=xxxx      (is set in C:\OS2LDR.INI)
        SET NSPR_OS2_NO_HIRES_TIMER=1 (OS/4 provides bugless DosTmrQueryTime)

I must have had some kind of corruption.  FF would come up but not access the internet.  Back leveled kernel and it was working normally.  Tested many other kernels  with the latest test kernel and everything is now working as it should.  What ever happened must have been causing the traps.  Will continue to monitor.  Everything is back to normal.

The Howto (mine is from Dec) says, including typos,
Quote
***Note***

    OS/4 kernel sets VirtualAddressLimit (VAL) according to settings in os2lsr.ini
    Supplied os2ldr.ini.template contains setting for VAL as 3072 which is
    optimal for many cases. But if your application/system requires some other
    value of VAL just edit your OS2LDR.INI to set VAL to desirable value.

David Graser

  • Hero Member
  • *****
  • Posts: 869
  • Karma: +84/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #189 on: April 10, 2019, 08:30:50 am »
Thanks everyone for the info! I made a few changes to my os2ldr.ini file.

CalY

  • Guest
Re: OS/4 (technical details only)
« Reply #190 on: April 21, 2019, 05:32:11 pm »
Installed OS4 on P4 2.6ghz single core 2gb ram with ECS 2.1. Tried kernel versions 5511 and 5403. When starting Kon editor from program object immediate trap 000d every time. After testing found if loading Kon through email client or file manger, editor loads and functions normal.
Ideas on cause of behavior appreciated.

OS4User

  • Sr. Member
  • ****
  • Posts: 406
  • Karma: +10/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #191 on: April 21, 2019, 09:43:29 pm »
Tried kernel versions 5511 and 5403. When starting Kon editor from program object immediate trap 000d every time

try 5514

CalY

  • Guest
Re: OS/4 (technical details only)
« Reply #192 on: April 23, 2019, 10:51:52 pm »
Kon loaded normal. with 5514 kernel. Now got trap 000e errors in Postroad Mail and Firefox 31

OS4User

  • Sr. Member
  • ****
  • Posts: 406
  • Karma: +10/-0
    • View Profile
Re: OS/4 (technical details only)
« Reply #193 on: April 24, 2019, 04:27:57 pm »
Kon loaded normal. with 5514 kernel. Now got trap 000e errors in Postroad Mail and Firefox 31

pls  give more info:   trap screen or comport log,  where to get Postroad Mail  and how do you run Postroad Mail  to get this trap, etc.

CalY

  • Guest
Re: OS/4 (technical details only)
« Reply #194 on: April 26, 2019, 03:18:58 pm »
Will leave this for now until I get another machine available for testing. All the traps are disturbing hard drive on main machine. Is ACPI necessary with OS4? This computer did not have it enabled.