OS2 World Community Forum

Public Discussions => General Discussion => Topic started by: ivan on May 17, 2015, 12:29:27 am

Title: OS4 kernel and associated files
Post by: ivan on May 17, 2015, 12:29:27 am
I don't know if this is the correct place but here goes.

One of my guys at work today asked how the OS4 kernel project was getting on ans since I didn't know I downloaded the latest (os2krnlSVN4363_unoff.zip) to have a look see.

Unzipping produces frustration. 
The read me is from 2008 but since the install shouldn't have changed that is OK.
Whatnew is several versions old and has the last couple of entries in Russian.

OS4APIC.PSD does have reasonable documentation.

Clock03b.sys, doscall1.dll and screen03.sys are just there with no information about them at all.  Looking in doscall1, it appears to be a special build for the SMP version of OS4.

It would help if those doing this work would give some indication of what these three are for and what we can expect from using them.  I assume the doscall1.dll is a direct replacement - if so how do you get back to using the IBM version or does it work with the IBM SMP kernel?  Are the two sys files replacements or do they work in conjunction with the IBM versions?

I could try replacing everything on a test machine, and most probably will if the night shift becomes too boring, but it would be helpful if there was some indication of what did what and what should happen.

If anyone can throw any light on this I will be very thankful.
Title: Re: OS4 kernel and associated files
Post by: OS4User on May 17, 2015, 01:47:50 am
I don't know if this is the correct place but here goes.

One of my guys at work today asked how the OS4 kernel project was getting on ans since I didn't know I downloaded the latest (os2krnlSVN4363_unoff.zip) to have a look see.

Unzipping produces frustration. 
The read me is from 2008 but since the install shouldn't have changed that is OK.
Whatnew is several versions old and has the last couple of entries in Russian.

OS4APIC.PSD does have reasonable documentation.

Clock03b.sys, doscall1.dll and screen03.sys are just there with no information about them at all.  Looking in doscall1, it appears to be a special build for the SMP version of OS4.

It would help if those doing this work would give some indication of what these three are for and what we can expect from using them.  I assume the doscall1.dll is a direct replacement - if so how do you get back to using the IBM version or does it work with the IBM SMP kernel?  Are the two sys files replacements or do they work in conjunction with the IBM versions?

I could try replacing everything on a test machine, and most probably will if the night shift becomes too boring, but it would be helpful if there was some indication of what did what and what should happen.

If anyone can throw any light on this I will be very thankful.

hi,  you can find some details here http://www.os2world.com/wiki/index.php/Phoenix_OS/4
Title: Re: OS4 kernel and associated files
Post by: muffetta on May 19, 2015, 08:39:42 am
Unfortunately I always get this error with almost all the latest releases:

DHRouter error, dh IM$
068606fb

Any suggestion?
Title: Re: OS4 kernel and associated files
Post by: OS4User on May 19, 2015, 03:13:07 pm
Unfortunately I always get this error with almost all the latest releases:

DHRouter error, dh IM$
068606fb

Any suggestion?

show you config.sys and comport log
Title: Re: OS4 kernel and associated files
Post by: muffetta on May 19, 2015, 07:36:59 pm
I do not have a comport.log to submit for now (no null-modem cable).
I might try a drive a time, the most likely?
Title: Re: OS4 kernel and associated files
Post by: OS4User on May 19, 2015, 09:42:54 pm
I do not have a comport.log to submit for now (no null-modem cable).
I might try a drive a time, the most likely?

The message you've got says that there was a DevHelper called in interrupt time which can't be called in interrupt time.

The problem was most likely created by some driver you have. I would suggest to remove all not necessary drivers and try to boot again.

Comport log is very welcome, as it may help resolve the problem. At least it would help find out which devhelper was called and this had called the problem.

If you want  you may try to contact me at netlabs IRC channel.
Title: Re: OS4 kernel and associated files
Post by: muffetta on May 20, 2015, 09:41:15 am
Comport.log in attach, done on a MSWindows machine at work, i hope this help.
Title: Re: OS4 kernel and associated files
Post by: muffetta on May 20, 2015, 10:38:15 am
Using the latest OS4, with and without /APIC switch
Title: Re: OS4 kernel and associated files
Post by: muffetta on May 20, 2015, 08:52:40 pm
Ok, my new (used) Lenovo X61s works great!
patched ACPI.PSD ver. 3.22.06
In config.sys:
PSD=ACPI.PSD /VW /ST=0
In os2ldr.ini:
os4krnl      =  OS4KRNL using config.os4,LOGSIZE=4096,CFGEXT=OS4,VALIMIT=3072
Works still in progress  ;)!
I'll submit comport.log asap
After, we'll try the desktop, i need a null-modem cable.
Thanks!
Title: Re: OS4 kernel and associated files
Post by: muffetta on May 21, 2015, 10:21:01 am
The logs from 'muffetta kernel', patched ACPI.PSD and config.os5, at EOF Theseus4 report.
System stable and very fast, running all this night.
Still using SNAP.
Let me know  :D.
Title: Re: OS4 kernel and associated files
Post by: Neil Waldhauer on May 25, 2015, 05:44:17 pm
I have a new system that is limited to 512 MB RAM.
I'm trying out the OS/4 loader and kernel in order to see close to the installed 4 GB.

The OS/4 loader is working fine to load OS/2 loader.
It works with updated DOSCALL1.DLL
But it still reports 512 MB RAM.

I cannot load the OS/2 kernel, even with Alt-F7 to suppress the LOGO.
The machine simply resets.

I cannot load the OS/4 kernel.
Loading: acpi4.sys. File not found or corrupted.


Where can I get acpi4.sys?
Do I even need the OS/4 kernel just to see 4 GB RAM?
Title: Re: OS4 kernel and associated files
Post by: OS4User on May 25, 2015, 05:53:34 pm

I cannot load the OS/4 kernel.
Loading: acpi4.sys. File not found or corrupted.

acpi4.sys is optional

show your com port log, config.sys  and os2ldr.ini
Title: Re: OS4 kernel and associated files
Post by: Neil Waldhauer on May 26, 2015, 02:22:51 am
Well, I'd hoped for answers to my questions, but here are the files, in hopes for answers later.

I'm not using any com port, so there won't be a log.
I've attached the config.sys.
os2loader.ini is unchanged from the distribution.

This memory hole problem is unexpected. I thought I had this same hardware working without a memory hole. Perhaps it can be eliminated in BIOS.

Title: Re: OS4 kernel and associated files
Post by: Doug Bissett on May 26, 2015, 04:07:05 am
Quote
This memory hole problem is unexpected. I thought I had this same hardware working without a memory hole. Perhaps it can be eliminated in BIOS.

Try QSINIT. It has worked for me, and you can use the RAMDISK that uses memory above the  GB mark (if you have any).
Title: Re: OS4 kernel and associated files
Post by: Neil Waldhauer on May 26, 2015, 05:10:45 am
Thanks, Doug. I tried QS_INIT, and it seems to fix the memory hole. I'm seeing 3492 MB now. If I change BIOS settings for video, the available memory goes up or down as expected.

Title: Re: OS4 kernel and associated files
Post by: OS4User on May 26, 2015, 07:29:45 am
Well, I'd hoped for answers to my questions, but here are the files, in hopes for answers later.

I'm not using any com port, so there won't be a log.
I've attached the config.sys.
os2loader.ini is unchanged from the distribution.

This memory hole problem is unexpected. I thought I had this same hardware working without a memory hole. Perhaps it can be eliminated in BIOS.

if you wish to use acpi.psd with os/4 kernel you should patch it http://gus.biysk.ru/os4/Patches/AcpiPsdPatches.rar   and  add /ST=0  to command line

patch will not spoil acpi.psd  -  you will still be able to use it with original kernel
Title: Re: OS4 kernel and associated files
Post by: Neil Waldhauer on May 30, 2015, 09:08:19 pm
Thanks, OS4User. I will go that route when I get a chance. As I work with QSINIT to find the rest of my RAM, I'm seeing a conflict with the Arca Noae release of MultiMac (R8169.ADD). This may affect the OS4 loader as well. If I revert to MultiMac from eCS 2.2 b2, QSINIT works well to show the full RAM of the system.