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 - Lars

Pages: 1 ... 68 69 [70] 71 72 ... 85
1036
General Discussion / Re: Problems booting ArcaOS
« on: August 15, 2018, 04:05:06 pm »
I doubt it has Something to do with broken Harddisk. I am seeing the same Problem Here but it Happens only occasionally. I suspect IT IS yet another SMP issue as I never See this Problem with only one core (which you could try as a Test).

1037
Storage / Re: PMSHELL
« on: August 03, 2018, 09:16:23 am »
That much sounds like a memory leak either in some WPS class (which is likely, given its lousy stability) or even in the memory subsystem (which is rather unlikely, compared to option 1).

But this memory leakage problem is not related to the question of low/high memory arena. It is likely a problem of dynamically allocated memory that is not properly freed when no longer in use. Since every WPS class remains loaded for as long as PMSHELL is executing, that memory will be leaked until you shut down the system or do a WPS restart.

As a test: if you observe this leakage, just do a WPS restart (via XWorkplace/eWorkplace) and see if that brings back the lost memory.

1038
Storage / Re: PMSHELL
« on: August 02, 2018, 11:02:04 am »
Whenever you have data in a data segment that is marked to load high you will get in deep shit trouble if that data needs to be passed for access by a 16-bit DLL (either directly or indirectly via intermediate DLLs).
That's because the standard way to thunk a 32-bit address to a 16-bit address will miserably fail for data in the high memory area but thunking is necessary so that 16-bit code can access data in a 32-bit data segment.

It should be obvious that it is almost impossible to know if data will eventually be accessed by 16-bit code and therefore it is a bad idea in general to mark data segments to load high.

Marking code segments to load in high memory is less risky. Only if some 16-bit code needs the address for a piece of code loaded in high memory this will miserably fail. But this happens not very often, compared to the "data case".

And then there is dynamically allocated (data) memory, that is, (data) memory allocated by an application during the runtime of the application. Here you can only rely on the programmer to make the correct decisions as you cannot influence this as a user.
It is the programmer's job to investigate if that memory is going to be used by 16-bit code or not. If yes, there are also means to generate a memory alias in low memory so that the address can be properly thunked for use by 16-bit code. But again, it's the programmers' job to do it right.

1039
Applications / Re: OS/4 (technical details only)
« on: July 02, 2018, 05:05:30 pm »
So what does ACPI.PSD add ? If I use ACPI4.BPD I can do the things that I expect: for example, execute "shutdown" with the system powering off at the end (much like APM). For CPU temperature control, I don't know in how far ACPI4.BPD supports that.

The one thing that OS4APIC.PSD/ACPI4.BPD does not support is MSI interrupts (or am I wrong ?) which the latest versions of ACPI.PSD do. But as far as I understand you need 2 things for MSI to work:
1) MSI support in ACPI.PSD (or OS4APIC.PSD/ ACPI4.BPD)
2) MSI support in the kernel itself (AN comes with an updated kernel that goes together with the latest versions of ACPI.PSD)


That's one of the reasons why I said repeatedly that the OS4 kernel needs better documentation ...

1040
Applications / Re: OS/4 (technical details only)
« on: July 02, 2018, 09:16:46 am »
OS4APIC.PSD supports multiple processors and in particular, the use of the APIC instead of the old PIC (something that is necessary for a multi-core / multi-processor system ,the PIC does not support a multi-processor configuration).
It does not support ACPI as such. However there is a free driver ACPI4.BPD (or some such, on the web page where you also find the OS4 kernel) that adds ACPI support. The current state of ACPI4.BPD is experimental. You just drop the file into the \OS2\BOOT directory where it is loaded automagically.
Apart from OS4KRNLR / OS4KRNL you will also need to dump all the other stuff of the OS4 kernel package to the right place. There are various drivers that need to go into the OS2\BOOT directory, including OEMHLP.BPD which is the OS4 kernel guys' way of supporting the OEMHLP driver interface. Again, this driver is loaded automagically (as every driver under OS4 which has the .BPD file name extension).
Last but not least you have an updated DOSCALL1.DLL in the OS4 kernel package. I have placed that into a subdir \OS4\DLL so that I can create myself an alternate config.os4 (which you need to do anyway so that you can load different drivers for the OS4 kernel) where I put \OS4\DLL before \OS2\DLL in LIBPATH.
I can only speak for myself but on my system (an 8-core AMD board from ASRock) the OS4 kernel works just as well as the standard OS2 kernel.

The only current change that the OS4 kernel guys have decided to do is to make the RM (Resource Management) interface to the drivers a 32-bit/flat interface which brings some changes to device driver writers. But nothing the users is directly affected with.

If you do all of the above then yes, you won't need ACPI.PSD if you run the OS4 kernel.

1041
Applications / Re: OS/4 (technical details only)
« on: July 01, 2018, 11:10:23 pm »
OS/4 comes with OS4APIC.PSD which you have to use with the /APIC Switch to Use multiple CPUs.

1042
For everyone using the (lousy) OS/2 DHCP client (dynamic IP address served by a DHCP server instead of static address), you need to add this line to %ETC%\dhcpcd.cfg:

ifconfig_options "mtu 1492 -trailers"

Adjust to your needs. "-trailers" promises some speed improvement, I don't know if that helps.

1043
Setup & Installation / Re: dead "VDM" entry in process list
« on: May 16, 2018, 03:24:14 pm »
In theory, a PnP BIOS should also offer a 16-bit protected mode entry point as the minimum (and even an optional 32-bit entry point).
The problem (as so often) seems to be that about no manufacturer properly implements or tests it.

Legacy BIOS is a dead horse. It's all too late by now. And I guess nobody will have the time to rewrite the exsting drivers to use some x86emu library. And how exactly does the x86emu library work ?

1044
Setup & Installation / Re: dead "VDM" entry in process list
« on: May 15, 2018, 01:55:20 pm »
But I need Win16. On my older computer (eCS 1.2), I have not this entry.

I have no problems with this entry, if it has got nothing to do with the seamless/DOS window problem.

This "VDM" is started by Panorama because Panorama has to access the real mode BIOS in order to do its video mode selection/management etc.
For that Panorama directly issues the documented real mode DOS video interrupt calls. These calls can only be executed by the VDM.

By the way: DANIS506.ADD (and of course IBMS506.ADD) can start a "VDM" for about the same purpose: in order to offer "INT13" support, it issues real mode DOS interupt13 disk management calls which are then executed by the VDM. By specifying the "/!BIOS" parameter you turn off that support (which for the most part is not necessary as DANIS506.ADD has other and better means to query the same info).


Yes, these started VDMs have nothing to do with seamless or even fullscreen DOS application sessions.


1045
Hardware / Re: How to deinstal ACPI driver?
« on: May 15, 2018, 01:34:08 pm »
You yourself chose the wrong "default base install". "Modern hardware, safe mode" was the wrong choice for you.
I cannot exactly remember the wording but "Modern hardware, ACPI based" or such would have been the correct choice for you.

1046
Hardware / Re: How to deinstal ACPI driver?
« on: May 14, 2018, 05:29:24 pm »
1) The EDM artictle is grossly outdated. Most of the listed params are no longer valid. Read ACPI.INF which comes with the ACPI installation. It lists the valid parameters.

2) are you sure that you are actually using a SMP kernel ? You should run "bldlevel OS2KRNL" in your root dir. The output should contain something like "SMP".

1047
Applications / Re: WPTools error message
« on: May 14, 2018, 07:45:53 am »
Running checkini from the Recovery Choices Menu F2 command line hangs on my ArcaOS system. If it doesn't work on a known good system, I doubt it will be useful in the distressed client system.

You got me wrong. I did not recommend to run checkini from a booted commandline. I stated that it might be impossible to run checkini from a booted commandline. Which you have now proven.

1048
Applications / Re: WPTools error message
« on: May 10, 2018, 12:31:09 pm »
Has he booted to a commandline in order to run checkini.exe or was that from a fully booted up system ?

I have never tried but I think it is possible that you cannot run checkini.exe from a booted commandline (say: hitting F2 on bootup). It is possible that too much of the system is "missing". Additionally, a DIFFERENT config.x (when hitting F2 on bootup)  is used as a replacement for config.sys.
A simple test should verify this.

Of course you can also have a corrupted system memory arena (for whatever reason). Obviously, the LIBPATH setting is cached somewhere. If that cached directory info is corrupted along the way then ...

1049
Internet / Re: Firefox and Traps
« on: May 04, 2018, 02:58:49 pm »
It might be possible to build a version of Firefox without the MMOS2 dependency

Of course it would be desirable to have a Firefox version that dynamically queries the availability of MMOS2 and if not available, to skip all the Multimedia related stuff, like using libkai to allocate a sound instance for example ...
I fear that is work that nobody has time for ...

Needless to say there is no defined way to query the availability of MMOS2. Just looking for the presence/absence of an environment variable would be lousy. Attempting to open a driver (like ssmdd.sys or r0stub.sys) would be better ...

1050
... and, as far as I understand from what I have read so far, you cannot use AHCI or you will have to buy yourself an AHCI PCIe card where I don't know how you would tell OS2AHCI.ADD to skip the Ryzen built-in AHCI controller and instead use the controller of the plug-in card.

Or maybe use SATA ("IDE mode" in BIOS).

Looks like for an OS/2 user, the new Ryzen CPU is more of a hinderance than help. Additionally, Intel seems to go the same way for their new generation of CPUs/boards. I deduce this from the fact that the new Intel boards will only work with Windows >= 10 because you will need drivers specially adapted to the specific HW (say good bye to standards). There clearly is no interest/business case in providing these drivers for Windows 7 or 8.

Pages: 1 ... 68 69 [70] 71 72 ... 85