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 ... 9
Article Discussions / Re: ArcaOS Wishlist - 6 months !!
« on: December 30, 2017, 08:16:51 pm »
I have had two systems myself where a NIC and disc controller would not work without MSI IRQ support.

Interesting. Could you please describe your systems, especially what mobo is in them and output of PCI.exe.

Programming / Re: OS/4 & PmDDk.sys
« on: December 26, 2017, 07:41:27 pm »
I found it interesting. Is there any more documentation about PMDD.SYS ?

Some short description is provided in the distribution packet.

Is this an original development (PMDDK.SYS) ? Or was it from another source like IBM DDK ?

It is not from IBM DDK.  PmDDk.sys  is written on C32 (mainly) and uses KEE unlike the original pmdd.sys

Adam, Valery,   tnx for testing.

Applications / Re: XWP v1.0.12 Beta 1
« on: December 24, 2017, 02:04:54 pm »
I have attached a new transparent boot logo. See what you think.  This is far more advanced than the others I have uploaded. This has been a learning experience.

Very nice logo

Programming / OS/4 & PmDDk.sys
« on: December 19, 2017, 04:46:34 pm »
PmDDk.sys  is added to distribution packet  starting from svn5073.

PmDDk.sys is a KEE optimized version of original PmDD.sys and it can work on any kernel with KEE (Aurora)

I did both, the result is that I see the following in graphics.log:

from snapos2.pdf:
Code: [Select]
Alternatively, you can use the gaoption “vidmem” option to not only limit the amount
of video memory reported, but also the amount mapped into the physical memory space.

Here is the mistake  - it has to be written into the virtual memory space but not into physical memory space, but the rest looks like true.

Indirect confirmation is in your log :
Code: [Select]
Attempting to enable write combining, base = 0xD0000000, length = 0x02000000 ... Success!So the set of LFB aperture is indeed 0x02000000 bytes =  32M.

I believe you will have the same even without SET SNAP_MAXVRAM_32MB=Y, but with “vidmem” only.

2) ...but that made me greedy, because I miss my bigger HPFS386 cache

You can use Theseus to analyze free System Memory to set HPFS386 cache as big as possible.
(System->Kernel Information->System Object Summary)

I have about 180M free system memory after system booted   - it looks sufficient.

Code: [Select]
in my config.sys. Pretty sure the SNAP documentation explains this.

according to SNAP documentation  SET SNAP_MAXVRAM_32MB=Y is not the same with "gaoption vidmem 32"

what is mentioned in your C:\OS2\DRIVERS\SNAP\CONFIG\GRAPHICS\graphics.log ?

To Neil:

Code: [Select]
Direct Interface to video extensions - DIVE
   Video bus bandwidth   :     7282.561    Megabytes/second

Is it really that much faster than an accelerated ATI card?

This VBB value is typical for latest Intel built-in video with a proper set of caching mode for LFB.
We need somebody with such processor and ATI card  to know what is  faster (I am curios too).
And it will be necessary to test this issue on real  applications not only Sysbench. I am using SNAP with ATI x850 and when I switch my comp to Panorama for tests, I recognize  dramatic decreasing of scrolling  speed (for example, any help file in NewView). Probably, on latest Intel built-in video, such decrease will not happen.

To Dariusz:

LIBC Error: Couldn't register process in shared memory!

I'm curious, what are you guys setting your VIRTUALADDRESSLIMIT to?

Pre Arca SNAP has a bad habit - it is mapping ALL memory available on a video card into address space (if  I am not wrong, even twice).

It looks absolutely senseless - just a waste of address space.
Fortunately, there is a way to "fix" this. "gaoption vidmem 8" reduces size of mem to be mapped by SNAP to 8M (it is sufficient for 1280x1024x16M)

I always use  VIRTUALADDRESSLIMIT = 3072 (/CACHE:262144  for JFS.IFS)

Applications / Re: XWP v1.0.12 Beta 1
« on: October 23, 2017, 07:03:30 pm »

I'm pleased to announce the first beta for XWorkplace v1.0.12.

Tnx for updating XWP.

1) Is it possible to get "Virtual address limit"  not from config.sys but from DosQuerySysInfo ?
    (attached is a sample of the code)
Code: [Select]
    ULONG val = 0;
    if (rc == NO_ERROR)
        printf("Virtual address limit: %d\n",val);

2) Is it possible to change the text in Shutdown dialog like that ?

Internet / Re: Firefox 45.9.0 & Youtube
« on: October 16, 2017, 07:53:02 pm »
it solved youtube video issue for me

it looks like vp9 consumes too much CPU power

Hardware / Re: ArcaOS Hardware recommendations?
« on: June 25, 2017, 08:51:50 am »
Memory above 3.5 GBs is only useful as a ramdisk, FAT, FAT32 or HPFS

Some recent motherboards map to first 4G region only 2G of physical memory in spite of the fact that there are much more of installed memory present. (I saw it on some mobo with Intel B85 and B150 chipsets).

Other other models of mobo map 3G - 3.5G. Of course, it is better to have as much as possible phys mem in first 4G region. OS/2, being a 32bits system, can use only phys mem in first 4G for regular purposes.

There hasn't been done any deep research how chipsets influence the mem mapping in first 4G (may be B85 and B150 map more phys mem on some other models of mobo).


Applications / Re: Are you getting ready for ArcaOS?
« on: March 10, 2017, 03:15:30 pm »
Anyone else have any idea what actually needs VDM support?

Kernel provides two kinds of VDMs: MiniVDM and "regular" VDM.

MiniVDMs is used for: calling Int10 and int13 from a protected mode.

What ppl usually can see in a process list is a MiniVDM for Int10,  -  video driver uses it  for communicating with video BIOS.

I have never seen MiniVDM for int13.

Regular VDM is used for running  dos/win sessions. To run dos/win sessions it is necessary to set PROTECTONLY=no  and to load the list of DEVICE=C:\OS2\MDOS\*.sys

MiniVDM is working  even with PROTECTONLY=yes and no MDOS drivers installed.

Programming / Re: OS4 -4762 problem--- no acpi4.bpd
« on: December 18, 2016, 12:24:02 am »
Well, I've run out of time to mess with this, -- gotta go! Thanks for the help, but 4747 doesn't work here either. Possibly problem with eCS's ACPI (ver 3.22.03).

I have never tried 3.22.03 and as far as I know  there is a patch for this ver
So try to apply  it.  Available patches are here
Do not forget to add  /ST=0  to acpi.psd command line 

Programming / Re: OS4 -4762 problem--- no acpi4.bpd
« on: December 17, 2016, 09:12:32 pm »
no, acpi4.bpd  is really optional  -  nothing special is in it
try 4747, for example
copmport log is very welcome

Pages: [1] 2 3 ... 9