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 ... 25 26 [27] 28
Programming / Re: OS/4 kernel and extended KEE
« on: January 07, 2014, 09:26:01 am »

I do have a com port on this machine, unfortunately I don't have a com port on any other of my machines available. Therefore I cannot create a log.

you may try to use USB->COM adapter  for machine  with terminal

comport log is essential for such cases

Programming / Re: OS/4 kernel and extended KEE
« on: January 07, 2014, 08:59:24 am »


you should not add  and you may leave TIMER0 in your config.sys

but it is not a big problem  - you will just have a  warrning


probably it is no more supported in os/4

By the way, does the debug kernel (os4krnl) support:
1) the full KDB command set ?
2) also work with UDP instead of serial interface ?

1) yes

2) I do not know if anybody test it.

It would be great if you can show comport log.

Programming / Re: OS/4 ? QSINIT ?
« on: January 06, 2014, 08:54:57 pm »

Why does the QSINIT kernel not become part of OS/4 and replaces the one from the OS/4 package?


They are being developed by two different developers.

Programming / Re: OS/4 kernel and extended KEE
« on: January 06, 2014, 08:45:31 pm »

Why would you want to use OS2APIC.PSD ?  If you use the OS/4 kernel you might as well use OS4APIC.PSD which is contained in the OS/4 zip file. Or is there any good reason not to do so ?

OS2APIC.PSD is rather limited in that it does not support IRQs > 15 which I believe is equivalent to the /PIC (or maybe /VW) mode of David's ACPI.PSD. Also OS2APIC.PSD has not worked on my system. My system seems to have broken MP tables. It only works properly in symmetric mode (using the IOAPIC instead of the old-fashioned PIC).
I believe the /APIC switch of OS2APIC.PSD was never completely implemented. It just does nothing on my system.


os/4 kernel loads CLOCK03a.SYS instead of CLOCK01.SYS   so I suspect that os/2 kernel is in use.

and I agree with you   -  it is almost impossible to find a comp where os2apic.psd could work with IOAPIC (it would work if  IRQ <=15)

Programming / Re: OS/4 ? QSINIT ?
« on: January 06, 2014, 02:26:51 pm »
2) from the website, it's completely unobvious of what the latest version is for the OS4 core project. I'd go with the SVN revision numbers but I could never be sure. It's also not clear what version was reasonably stable and what version was not. I would also think it would be a good idea to remove all versions that proved to be too unstable for most testers.

3) it's completely unobvious in how far the QSINIT project relates to the OS4 project. Does QSINIT "overwrite" the OS2LDR contained in the OS/4 zips ? What would be the benefit to use QSINIT in favor of the OS2LDR that comes with the OS/4 kernel zip ? Is that the same group of developers of these 2 projects ?

4) there is no FAQ that would collect common problems or such. Also there is about no documentation. All the information is contained in the few postings floating around on the os2world website. Who is going to bother and go through the effort to test the OS/4 kernel if he is more or less completely on his own ? Not too many people I would think ...

For me, 2) and 3) and 4) are the most pressing problems

2) latest ver is here

3) you can use QSINIT instead of OS2LDR contained in the OS/4 zips

4) if os2word  wants,   it is possible to do a kind of wiki

Programming / Re: OS/4 ? QSINIT ?
« on: January 06, 2014, 02:13:23 pm »
About the problems with Veit's PCIBUS.SNP, see:,176.msg1453.html#msg1453


I am running os/4 kernel with Veit's PCIBUS.SNP  -  never see a problem.

Hardware / OS/4 sees up to 4G memory
« on: January 05, 2014, 10:03:54 am »
Reading last messages in news and in forum one may think that OS/4 has a problem with memory more than 512M. It is not true. OS/4 "from a box" sees all available memory and may use it (but not memory above 4G) .

More over, OS/4 kernel works fine on some resent hardware where OS/2 kernel reboots at the beginning of boot  (much earlier than PSD or BASEDEV  is loaded).

Hardware / Re: Webcam Support for OS/2 and eCS!!
« on: September 13, 2013, 07:01:34 am »
After a long time of intensive development and tremendous work done by Wim Brul and a bit testing of me I have the honour to announce that finally Webcam Support for OS/2 and eComstation has been achieved!!

Excellent job!  Congratulation! 

I tried just for fun to connect my old Logitech  camera  - definitely not C250.

DEVICE=C:\OS2\BOOT\USBECD.SYS /D:046D:08B5:0003 /N:$LTC250$

It sayd [0000001D] Obtain Thread error!    -   is any chance to run it with my camera?

Applications / Re: os4apic.psd is released
« on: August 13, 2013, 07:53:27 am »
While I know the OS/4 team does not have access to the current ACPI code.

As far as I know ACPI code is closed and available only for eCS team.

The readme file of the os4acpi.txt states for example states:

"OS4APIC.PSD hangs IBM kernel because of lack of service and some other
reasons. Unfortunately there is no way to avoid it due to the bug in the
IBM kernel. "

What is ment by that ? Could the details be more specific ?

In fact it's not bug and it will not affect ACPI.psd in any way. What was meant probably is that in IBM kernel there is no scenario that when PSD is present in config.sys and returns error to INSTALL command. IBM kernel in this case will hang. As OS4APIC is meant only for OS/4 kernel and it uses its features it will not work on IBM kernel. Yes, OS4APIC can recognize IBM kernel, so what? IBM kernel still can't accept error to INSTALL.

MemFiles_en.txt states:
"The main goal is to run ACPI on AMD chipsets where int 13h cannot be used after switching
ACPI on."

From what I can tell about this above description is that its to generic (lacks details) or is just wrong.
I think its the last case. Possibly our PSD version still has some bugs in it.
But from what I can tell (also after haven spoken with David) there is no such thing as INT 13 going away
on AMD systems when ACPI is loaded. It was just that the orginal PSD code made wrong switched between real mode
and procted mode and that caused the hang! That is now fixed.  Has nothing todo with OS2LDR or OS2KRNL bugs.

Yes, you are right. It was a bug in earlier ACPI.PSD and it has nothing in common with kernel and ldr. But earlier there was an opinion that it was connected with AMD chipset. But later ACPI.PSD is working good where that bug used to appear.

As far as I know, there is no mode switch code in PSD, may be David meant switching between PIC and IOAPIC ?

Since David started working on ACPI I can only state the amount of random system freezes and locks has basicly gone
away. Of the 50 systems I have had access to test eCS on, only 1 box still fails with ACPI.

Yes, David did and is doing a great job for improving ACPI.PSD

Applications / os4apic.psd is released
« on: August 10, 2013, 04:59:57 pm »
it looks like it will be distributed with os4krnl

Setup & Installation / Re: UEFI & SecureBoot?
« on: August 01, 2013, 05:27:33 pm »
What did help in some cases was to replace the eCS Loader with the OS/4 Loader - but you have to replace the kernel back to 104smp as well

looks like this issue is fixed in

Programming / Re: OS/4 kernel and extended KEE
« on: June 18, 2013, 11:24:47 pm »
  Since I last posted I have been using the OS4 kernel (retail) with no trouble. Maybe the freeze I got then was from something else (Flash??). I did have a POPUPLOG from DMISL.EXE which is something I've never had before...

would be interesting to see

  I have one question: Is os2krnl.ini necessary? I ask because I don't see anything in ___hlp$ that would make me think I need to add anything to os2krnl.ini, but maybe I don't understand the instructions....

OS/4 kernel with switched ON preload option will load all files which will be necessary on stage 1 of boot process into a kind of memory disk and then the hard drive will not be touched until the stage 2.

For this purpose kernel  builds a list of such files. This list includes  all BASEDEVs + PSD from config.sys,   BASEDEVs which loads without config.sys,  SNOOPERS from snoop.lst  and files mentioned in os4krnl.ini

Actually os4krnl.ini serves for a user to enable him to add files which are needed to be preloaded and about which the kernel didn't guess.

If during boot kernel will try to load some file which was not preloaded - user will receive a message something like  "Please add driver.sys to os4kernel.ini".

In majority of cases os4krnl.ini will be absent or empty. I personally can't imagine a situation when something has to be added there, but who knows.

Programming / Re: OS/4 kernel and extended KEE
« on: June 13, 2013, 11:38:25 pm »
What is ACPI4.SYS?

It will be an acpi driver for os/4 kernel. Current kernel is trying to load it, but in case it is missing nothing fatal happens.

Programming / Re: OS/4 kernel and extended KEE
« on: June 12, 2013, 02:22:04 pm »
  I gave this (4033) a try and when booting I get this error: 'File not found or corrupted: acpi4.sys'. I don't have this file (eCS 2.1).

acpi4.sys  is optional  -  system just will not use it.

It seemed to work well for about 5 minutes, but then my desktop froze and I had to hard reset.

It would be great if you could show com port log, especially at the moment of such freeze.

Is there anything in particular you want tested?

Nothing special just stability and working in general.

Programming / Re: OS/4 kernel and extended KEE
« on: June 12, 2013, 12:14:30 am »
A bug is fixed (freezing before switching to graphic mode)

Pages: 1 ... 25 26 [27] 28