Author Topic: New OS/4 kernel :: SVN4227  (Read 148957 times)

dbanet

  • Guest
Re: New OS/4 kernel is available :: SVN4166 :: screen03.sys release
« Reply #45 on: February 18, 2014, 07:20:07 pm »
I'm announcing that I've finally made the page about OS/4, that may be considered fairly useful, but it does not cover the complicated cases, as the troubleshooting section is not written. Also the FAQs section is not complete (I think it may be three times longer).

Here it is.

http://www.os2world.com/wiki/index.php/OS/4

dbanet

  • Guest
Re: New OS/4 kernel is available :: SVN4166 :: screen03.sys release
« Reply #46 on: February 20, 2014, 07:39:05 pm »
Hooray!

Phoenix finally made a move towards open source software! @Martini

There is the FULL SOURCE CODE OF THE QSINIT KERNEL BOOTLOADER AVAILABLE at -->
--> ftp://dixieos2.tk/public/QS/QS_SDK.ZIP
« Last Edit: February 20, 2014, 07:58:05 pm by Boris »

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4712
  • Karma: +41/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Thank you very much for releasing the source code to the public.

Even that the license is "Source code available for non-commercial use only" and does not qualify as open source, I feel that is a great first step for the collaborative growing of this loader.

Thanks !!
Martin Iturbide
OS2World NewsMaster
... just share the dream.

dbanet

  • Guest
Doug, and everyone else, help in writing (some sections are not finished) and editing (my English is not good enough) the wiki page about OS/4 is needed.

Doug Bissett

  • Hero Member
  • *****
  • Posts: 1593
  • Karma: +4/-2
    • View Profile
I haven't updated to the SVN4168 version, yet, but I seem to have found a problem that makes it undesirable to continue using the OS4 kernel. I use PROCDUMP to get process dumps when something crashes (specifically PMMail, but I trap all crashes). The dump seems to work, but the PM Dump Facility won't read the resulting dumps, making them useless.

Doug, and everyone else, help in writing (some sections are not finished) and editing (my English is not good enough) the wiki page about OS/4 is needed.

I have had time to take a quick look. What is there seems to be okay, but it does need work. I will poke away at it when I find time.  Thanks...

dbanet

  • Guest
Doug, I will report this, but due to the situation in Ukraine, I'm afraid it may not get fixed very soon... please, be patient...

arr531

  • Guest
Re: New OS/4 kernel :: SVN4169
« Reply #51 on: March 09, 2014, 08:07:08 pm »
I just checked over at their server and the os/4 kernel is now at 4170 dated March 9 2014.

dbanet

  • Guest
Re: New OS/4 kernel :: SVN4169
« Reply #52 on: March 10, 2014, 10:55:45 am »
I just checked over at their server and the os/4 kernel is now at 4170 dated March 9 2014.
And now 4171.

arr531

  • Guest
Re: New OS/4 kernel :: SVN4171
« Reply #53 on: March 10, 2014, 03:21:01 pm »
4171? Wow that was fast.  :)

dbanet

  • Guest
Re: New OS/4 kernel :: SVN4171
« Reply #54 on: March 10, 2014, 11:02:08 pm »
4171? Wow that was fast.  :)

I mean, I know about every release, I'm just sometimes too lazy^Wbusy to update the first post.

dbanet

  • Guest
Re: New OS/4 kernel :: SVN4172
« Reply #55 on: March 11, 2014, 11:24:41 pm »
4172.
Up!

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1317
  • Karma: +26/-0
    • View Profile
Re: New OS/4 kernel :: SVN4172
« Reply #56 on: March 19, 2014, 09:59:05 pm »
Boris,
I had previously attempted to get 4168 running, no luck. Now tried 4172, unfortunately no luck either, even more, I am seeing the same issue as with 4168.

Namely, upon selecting the configuration to book (os2ldr.ini) the line stating which configuration is booting is displayed and then....NUTHING...the screen sits there, no HARD lock, num-lock, caps-lock still works...but nothing actually happens on the screen.

Here is my os2ldr.ini:
=== START ===
[kernel]
os2ldr.104   =  IBM OS2LDR 14.104a_SMP ,Restart
os2ldr.105   =  IBM OS2LDR 14.105a_SMP ,Restart
os4krnlr     =  OS4 Current - RETAIL,PRELOAD,NOLOGO,CFGEXT=os4
os4krnl      =  OS4 Current - DEBUG,PRELOAD,NOLOGO,LOADSYM,CFGEXT=os4
os4krnl      =  OS4 Current - DEBUG - show driver names,ALTF2,NOLOGO,CFGEXT=os4
=== END ===

All the other files are present, doscall1.dll has been replaced with the one from the package, clock & screen drivers are present.

Any ideas what to try next? I have no idea how to even get some debug info up on the screen.

This is on a machine which successfully runs a 5-core Phenom II X6 CPU (MSI 880G-E45 motherboard) using the "OS2APIC.PSD /P=5 /APIC" driver.

Thanks!

OS4User

  • Sr. Member
  • ****
  • Posts: 406
  • Karma: +10/-0
    • View Profile
Re: New OS/4 kernel :: SVN4172
« Reply #57 on: March 20, 2014, 09:11:32 pm »
Dariusz,

please  show com port log   -  it may help to understand where is hang

dbanet

  • Guest
Re: New OS/4 kernel :: SVN4172
« Reply #58 on: March 21, 2014, 01:03:31 pm »
Can you please join IRC channel #netlabs on freenode, and PM me, dbanet?
I see you're having issues running OS/2 on your machine, but for me it's hard to understand your English, and also you've reported very small amount of information that is needed to debug your configuration -- it is almost impossible to help you while discussing offline (on a forum), or a lot of time more needed.

You won't get a live reaction of OS/4 kernel developers like that, but I'm here to support OS/4 kernel users, to promote this project, and to avoid wastage of kernel developers' time by providing them qualitative, useful, detailed bug reports from users.

Sorry for a huge delay -- didn't have time to open my RSS reader.

Dariusz Piatkowski

  • Hero Member
  • *****
  • Posts: 1317
  • Karma: +26/-0
    • View Profile
Re: New OS/4 kernel :: SVN4172
« Reply #59 on: March 22, 2014, 02:10:01 pm »
Dariusz,

please  show com port log   -  it may help to understand where is hang

How do I do that? I see the DEBUG setup instructions, but nothing (as best as I can tell) about troubleshooting through the COM port.

I can only assume this requires me to hook up another OS/2 PC over the COM port? No problem there, I still have my old machine...but could use some detailed instructions to walk me through this.