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] 2 3 ... 16
Multimedia / Re: Updated Uniaud32 build
« on: May 13, 2020, 12:29:38 pm » - release & debug builds included.

3.5 works ok on my CA0106/CA0111 [SB Live!/Audigy/X-Fi Series]

Multimedia / Re: Updated Uniaud32 build
« on: May 13, 2020, 12:20:34 pm »
'Not enough memory to run PMShell.exe on the Protshell = statement in Config.sys' (I have 8MB). Never saw that before!

It possible that new Uniaud32 consumes more system memory - try to decrease VAL.

Multimedia / Re: PC Speaker output to sound card?
« on: April 17, 2020, 10:12:07 am »
It will list all the imports. If you find something like this:
REL OFF(32)  0014       imp DOSCALLS.286

Hi Lars

do not forget  Dos16Beep   (DOSCALLS.50)

Theseus tells me: "RAM available to OS/2 = CFF0B000 bytes (3327.043M)", I think this is a good amount of RAM,

True - that is very good amount (max what I have seen is "RAM available to OS/2 = DFE6D000 bytes (3582.426M)")

Unfortunately, some of the latest Intel based mobos have less than 1Gb  and this issue cannot be solved (AFAIK). 1Gb is too little - and thus swap is inevitable.

If I choose mobo, the first thing I will be interested in is how much memory will be available for OS/2.

by the time WPS comes up and all my stuff starts up I usually have about 2970M left with about 210M of free shared memory (this is really the biggest problem actually as it routinely gets exhausted after a couple of days of steady FF use).

Amount of available phys mem does not have any influence on free shared (high) memory.

So here is my combo:
1) MSI 880G-E45 motherboard

How much RAM is available below 4Gb border ?

Applications / Re: OS/4 (technical details only)
« on: March 24, 2020, 07:30:32 pm »
if you were to boot in the OS2 config that would actually produce a valid output.

nope.  I got the same output with OS/2 config too.

Applications / Re: OS/4 (technical details only)
« on: March 24, 2020, 06:25:25 pm »
Can anything be done to fix the DMI table?

AFAIK DMI table is provided by mobo manufacturer  - so no idea how to fix it.

In case someone else is attempting to use ANPM on an OS4 configured system they will likely fail as well.
FYI, here is what I'm seeing:

Code: [Select]
# dmidecode 3.1
Scanning /dev/mem for entry point.
SMBIOS 2.5 present.
54 structures occupying 1934 bytes.
Table at 0x0009F800.

Invalid entry length (0). DMI table is broken! Stop.

I use ANPM on OS/4 system for quite long - so far so good.

Here is my output of dmidecode
Code: [Select]
# dmidecode 2.12
SMBIOS version fixup (2.33 -> 2.3).
SMBIOS 2.3 present.
41 structures occupying 1581 bytes.
Table at 0xDFEDF000.

Invalid entry length (0). DMI table is broken! Stop.

I subsequently booted up using my OS4 config and came to find out that ANPM credentials check on the sub repos failed again.

ANPM could have some other reason to fail on OS/4.

Applications / Re: Hardware Explorer
« on: February 16, 2020, 08:45:42 am »
Seems like the OS4 version is more 'complete', however that also means there are double occurencies of hardware being listed.

For example, if you look at the Realtek NIC you will find the following:
1) r8169_0 Network Adapter
2) Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

You are very observant :).  OS/4 version is not just more 'complete'   -  OS/4 adds to it's RM all equipment that is available on PCI bus, considering  bus topology.

What you can see under PCI_Bus_0  is your real PCI tree and thus PCI_Bus_0 is your root bridge.

OS/4 RM combines real PCI tree and adapters added by drivers if a certain driver provides PCI address for its  adapter.   For ex.  Lars's USB controllers' drivers.

If a driver does not provide PCI address - then you can see its adapter under PCI_Bus_Misc node which is artificial and does not reflect real PCI tree.

Applications / Re: Unofficial VBox Additions - vbxgradd.dll
« on: February 09, 2020, 11:53:17 am »
ok thanks, on the command line output says the work is done, but then I cannot find the renamed VBXGRADD.DLL.

Module name and file name is not the same. Now you have gengradd.dll file which contains VBXGRADD but not GENGRADD module.

Article Discussions / Re: Community Ideas BrainStorm for 2020
« on: February 05, 2020, 06:49:47 am »
I've heard of OS/4, but I honestly don't understand what it is.  Is it a kernal replacement?

Here is some info.

Applications / Re: Hardware Explorer
« on: January 25, 2020, 07:59:46 pm »
Starting from SVN5686 OS/4 organizes RM info in a bit different way.
One can see a real PCI bus(es) structure of his equipment (see  PCI_Bus_0 node and its tree).
It is something similar  to output of PCI.exe.

If any driver provides PCI info to RM  -  it is also reflected in Hardware Explorer.
So far this PCI info is provided by Lars's USB drivers only.

Only thing missing here is more video info beyond VGA.

VGA info is provided by screen03.sys on OS/4 and resource.sys on OS/2.
These drivers are not very smart so cannot give more info.
At the same time HardWare Explorer showed the name of my graphic card  correctly.

Dave, I will try to add LFB mapping in screen03.sys. What info would you like to see ?

Applications / Re: Trap Seamonkey 2.42.9
« on: January 24, 2020, 08:19:40 pm »
I found the issue with Chatzilla, seems our gif parser doesn't like taskbar-irc.gif so I converted it from 256 colours to 32 bit.
Easiest way to update is to just replace it. With SeaMonkey closed, replace it in your profile at extensions\{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}\chrome\chatzilla\skin\modern\chatzilla\images
You could also try installing the updated XPI. This failed here, possibly due to profile corruption so I ended up removing Chatzilla and the extensions\staged folder and simply replacing the files in extensions\{59c81df5-4b7a-477b-912d-4e0fdf64e5f2}

I tried to replace taskbar-irc.gif  and my Chatzilla  locked.

If one meets the same, open about:config and set the preference xpinstall.signatures.required to false.

Dave, the latest Chatzilla is 0.9.93   -

Thank you, especially Wim, Laurence and OS4USER for your comments. Now I think I will manage it without help.

Martin, I have to admit that I tested your cmdme.exe  in a wrong way  -  I started new cmd  with  "start cmd" command from command line provided by cmdme.exe  and a new process was not a direct child of cmdme  -  that is what I stated.

Now I traced this case  with proper scope (I hope :) ) and I can see  that cmdme.exe  is delivering new process "cmd"  automatically after start. Yes,  this "cmd"  is a direct child of cmdme.exe.

If I press Cntr-C  in cmdme.exe  window  it generates DosSendSignalException with a proper PID and signal.

DosSendSignalException returns you ERROR_NO_SIGNAL_SENT because cmd.exe does not report itself as "receiver of signals".

From  an example  I posted earlier   you may see   how  a potential child ("DosSetExceptionHandler.exe")  is organized to be a  "receiver of signals".

Please recheck it   - but it looks like  it is working in this way.


>because new processes  are _NOT_ direct children of CmdMe

How do I have to execute cmd.exe so it gets a direct children of my program?

I am not an expert - but enclosed example gives me direct child, so DosSendSignalException returns ok  - pls check.

I was not able to get direct child using DosStartSession  -  have to learn out more.

In the attachment, you will find the current exe (version number 0.10). I have written all important stuff into the readme text file.

Well, I have tested you CmdMe - everything is working as expected:

DosSendSignalException returns 205 because new processes  are _NOT_ direct children of CmdMe.   Even I use /sync key.

You can easily check this fact  with Theseus.

Pages: [1] 2 3 ... 16