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
Setup & Installation / Re: RAM disk and temp folders...what else?
« on: April 19, 2018, 10:05:23 pm »
There are a bunch of other drivers like CLOCK03.SYS etc. where it's also not clear if these drivers are mandatory or not and if they have to be added to config.sys or if they are loaded automatically by the kernel.

I would like to try the OS4 kernel and other programs and drivers but there is nowhere enough information to let me do so.

Lars, Ivan

OS/4 distr contains HowTo file about installation process of OS/4 kernel.
Pls let me know if anything is unclear in this file and still creates complication.

If any technical questions arise, pls put them into

Ivan, at least two persons reported about successful run OS/4 on Rysen

Applications / Re: OS/4 (technical details only)
« on: April 17, 2018, 06:12:54 pm »
I re-read the Wiki you posted above and will get the debug kernel setup and ready to go. Beyond this though, is there anything specific I need to do in order to capture the "moment" the system traps?

My assumption is that maybe through the debug kernel I have some way to communicate with the OS/2 box, but even if that is the case, once the trap occurs, how do I know what additional information to log? Can you provide any 'working instructions' for this? Even high-level stuff might help...

Welcome on board :)

You do not need anything specific, you will see trap info in your comport log.
Additional info always depends on trap info, working instruction is quite big,  it is called
"The OS/2 Debugging Handbook"  for ex.

Applications / Re: OS/4 (technical details only)
« on: April 17, 2018, 11:20:08 am »
Can it be possible for the author to explain a little bit what was patched on this DIVE.DLL ?

Hi Martin

some details is here

Applications / OS/4 (technical details only)
« on: April 16, 2018, 08:09:59 pm »
Patched DIVE.DLL can increase video speed on OS/4 system.

At the same time the patched DIVE.DLL is not compatible with original OS/2 -  to avoid missboot do the following:

1) Create C:\OS4 dir
2) Put the patched DIVE.DLL into C:\OS4
3) Insert C:\OS4; exactly after LIBPATH=  into your CONFIG.OS4 so you will have LIBPATH=C:\OS4;.;.......

This way the patched DIVE.DLL will be loaded instead of original DIVE.DLL and  original DIVE.DLL will remain for booting with CONFIG.SYS (for ex. original kernel).

Applications / Re: VirtualBox v5.0.51 Testing
« on: April 15, 2018, 09:37:20 am »
... I really don't know which kernel you are referring to when saying OS4 kernel...

here is some info,324.0.html

I remember someone said they had managed to do it but there were very few details given. I that person, or anyone else that has managed to get ArcaOS / OS/2 running on a Ryzen or A12 APU could post the details it would be most appreciated,1581.msg15660.html#msg15660

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 ?

Pages: [1] 2 3 ... 9