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 - Dariusz Piatkowski

Pages: 1 2 [3] 4 5 ... 89
31
Networking / Re: Updated Samba Client
« on: January 05, 2024, 04:11:59 am »
David,
...How do I force whether it uses smb1 or smb2? Don't see a choice in the ndctl console...

NDCTL has it, but it's at the individual resource level, so open one up (or create a new one if you don't have anything saved) and look for the "Support NTLMv1" radio button...right hand side of the window.

EAs support can be dis/en-abled here as well.

32
Applications / Re: ArcaOS 5.1 - First Impressions
« on: January 04, 2024, 04:12:47 am »
Hi Roderik,

Here is BTW the bad news. The values that Robert entered in the CFG file do not matter. You can only enter integer numbers....

Not going to argue with you there as I do not know the logic PowerManager implements (I asked David A when I had opened the Ticket on the issue I was seeing, never got the answer to that question though).

Regardless, as I mentioned at the start of my original response, there is one way to tell and that is to turn on the LOG and see what's there:

Code: [Select]
01 Jan 16:21:10 AcpiDaemon ========== AcpiDaemon 3.23.16 Starting ==========
01 Jan 16:21:10 AcpiDaemon Detected APM version 3.23
01 Jan 16:21:10 AcpiDaemon LID set to Do Nothing, PowerButton to Do Nothing
01 Jan 16:21:10 AcpiDaemon Log to screen:Off
01 Jan 16:21:10 AcpiDaemon NOTIFY: ========== Notify thread is starting ==========
01 Jan 16:21:10 AcpiDaemon PWRBT: ========== Power Button thread is starting ==========
01 Jan 16:21:10 AcpiDaemon PWRBT: Calling AcpiTkWaitPressButton
01 Jan 16:21:10 AcpiDaemon NOTIFY: Calling AcpiTkWaitNotify()
01 Jan 16:21:10 AcpiDaemon PIPE: ========== Pipe thread is starting =================
01 Jan 16:21:10 AcpiDaemon PM: ========== Power Manager thread is starting ==========
01 Jan 16:21:10 AcpiDaemon PM: Enable=0 Verbose=1 CheckInterval=1000 PreferredMode=0 PMset=0
01 Jan 16:21:10 AcpiDaemon PM: MaxTemp=85 OverTempPower=25 MaxAC=100 MaxBattery=50 MinPwr=15, DecAt=15 IncAt=25 AllAt=75 IdleCount=2
01 Jan 16:21:10 AcpiDaemon APM: ========== APM thread is starting ==========
01 Jan 16:22:10 AcpiDaemon PM: Number of controllable CPUs: 1 of 6 total CPUs

...problem solved, the above tells me exactly what PowerMan is doing with my settings.

33
Applications / Re: ArcaOS 5.1 - First Impressions
« on: January 04, 2024, 12:29:25 am »
Hi roberto,

-Dariusz
I think you misinterpreted my message, the values you indicate are ones that I was with on my test machine using them for a while but they're not the right ones. The right ones are the others. In fact, I've already changed all my computers at work, including the server...

I'm sorry but I'm not sure what the FINAL values are?

Your thread posting I responded to is what I quoted in my response, but here it is as it appears right now:

Quote
and changing only these two values changed everything completely.
; IdleCount: Number of CheckIntervals needed to determine system idle, default=5
IdleCount = 0.3125

; CheckInterval: Delay time between checking cpu load and temperature (seconds), default=1
CheckInterval = 1.3125

If anyone wants to try it.

I am experimenting with other values, and with 0.3125 and 125 , I have 8 processors with less than 25% evenly distributed all, 6 taps open, a youtube video in the background, with Dooble 632. Interesting.
Sorry, modyfy 0.03125 and 125

So what actually are you finding to be the MORE stable set of values than the above listed:
IdleCount = 0.3125
CheckInterval = 1.3125
?

Because the recommendation I made to shut OFF PowerMan were based on your conclusion that different values are improving things for you.

Either way, did you shut it OFF and if yes, what were the results (if any)?

34
Networking / Re: Updated Samba Client
« on: January 02, 2024, 02:36:35 am »
...What server and version is the NAS running?...

Don't know off the top of my head, will telnet into the NAS box a bit later to see if I can get something from the LOGs (old ZyXel NSA425 box).

I do use the 4.11.12 client on our OS/2 side though.

35
Networking / Re: Updated Samba Client
« on: January 02, 2024, 02:07:39 am »
David and Paul,

...I tried using a Windows machine (this is with the updated smbd.exe on the server) when the OS/2 machine showed '0 files' and Windows worked! Windows works fairly good with the 4.18 server on OS/2 with the new smbd.exe (maybe a little slower than the 4.11 server) - both when sharing the root of the drive and a subdirectory.

 Yes, when I restart NDCTL after I get the '0 files' condition on OS/2, it starts to work again. For awhile... There are no traps on the server and don't need to restart it...

This may be a VERY remote possibility, but for quite some time I've had a similar issue with my NetDrive install here.

Basically everything works fantastic, until it doesn't! The symptoms are exactly what you describe: the share connection still shows up in NetDrive, but attempting to query any of the share's contents fails and most often simply produces the '0 files' message. For me that typically manifested itself as WPS folders that were simply empty when I would open them up.

Given that we really didn't have anyone around to troubleshoot the NetDrive problem I took to writing some REXX stuff to periodically check that the NAS share is still "accessible". When it no longer is, I simply bounce NDCTL and things come right back up.

Weird...I have this scheduled through cron here, runs every 15 mins and AFAIK I never experience the annoying "grrrh, NetDrive is down again" feeling.

Like I said above, very REMOTE possibility, but the symptoms are precisely what I'm seeing here, so while the new samba release may not be the absolutely root cause of what you're seeing, it may somehow be contributing to NetDrive failing???

36
Applications / Re: ArcaOS 5.1 - First Impressions
« on: January 01, 2024, 10:57:16 pm »
Roberto!!!

Happy New Year to you sir...let's see what's going on here:

.. checking things I found this in :

C:\MPTN\ETC\acpid.cfg

Alright...so one thing to start off with: consider turning ON the LOGs, in the same acpid.cfg file, at the very top you have the following section:

Code: [Select]
;############## General Deamon Settings ##################################
[ACPID]
; LogFile: Where to write the log file, full path, default=No log file
LogFile = G:\tmp\log\acpidaemon.log

; AcpiLog: Where to write the acpica$ log file, full path, default=don't create
AcpiLog = G:\tmp\log\AcpiCA.log

; ConfigCheckInterval: Delay in seconds between checking for config file changes, default=10
;ConfigCheckInterval = 10
...

The values above reflect my system config, so adjust accordingly. Point being, the acpidaemon.log & acpiCA.log files will have a LOT of useful info to look at.

Now let's look at the control values you were using:

...and changing only these two values changed everything completely.
; IdleCount: Number of CheckIntervals needed to determine system idle, default=5
IdleCount = 0.3125

; CheckInterval: Delay time between checking cpu load and temperature (seconds), default=1
CheckInterval = 1.3125

OK, so what exactly do these two settings do?

The ACPI daemon uses the CheckInterval as the frequency (in seconds) of checking the CPU Load & Temperature, further on, it uses the IdleCount value as the number of times the CPU Load & Temperature will be checked to determine if the system is experiencing a no-load situation, namely it appears to be in IDLE state.

From the ACPI perspective that would indicate that the CPU status can now be adjusted (and most likely set as INACTIVE) in order to lower the power consumption, which for battery operated machines is what matters!

The 'Power Manager Settings' section of the ACPI documentation (INF) file does a nice job of explaining this in pretty good details. The key take away here is that the recommendation is NOT to use CPU THROTTLING (which can be set in the [PreferredMode] section, if you have a specific reason to try a particular value).

OK, so this is all theory...how about Real-World???

Well, in my case the machine being a 24x7 box that's using a steady power supply I simply shut OFF the PowerMan function entirely because I found the control logic to be unsuitable for my purposes: CPU cores would constantly go off-line (to avoid power usage) and the time it took for them to spool back up (when the usage demanded it) took too long (regardless of how aggressive of the settings combination I would use).

So the advice I would give you is as follows: FOR TESTING PURPOSES ONLY, disable PowerMan, reboot and see what's going on.

To disable PowerMan you make the following adjustment:

Code: [Select]
;############## Power Manager Settings ###################################
[PowerMan]

; Enable: 1=enabled, 0=disabled, default=1
Enable = 0

Notice how I set 'Enable = 0', which disables it.

Test it out, if this addresses your issue and your BIOS does not report crazy CPU Temps, than you always have to option to simply NOT use PowerMan.

37
General Discussion / Re: A Ghost of Christmas Past is Still Present
« on: December 28, 2023, 01:00:41 am »
Dave, everyone!!!

Merry Christmas Mark, Dariusz and everyone else here.

Terrible etiquette :( on my part: while responding to Mark's post I of course did not intend to leave everyone else out...Merry Christmas and a Happy New Year to all!!!

38
General Discussion / Re: A Ghost of Christmas Past is Still Present
« on: December 25, 2023, 09:29:41 pm »
Mark!

Glad to hear you're alive and kickin'...even though sometimes it feels like life is handing you one hurdle after another...the good news is: it'll pass!

For now, enjoy those still around you, and the things that bring you happiness.

Merry Christmas and a much Happier New Year!

39
Utilities / Re: LinearMemoryMap.cmd => new version produces an error...why?
« on: December 24, 2023, 08:01:15 pm »
Good sir!!!

It works fine now.

I was using your latest code, but I added my own section in the 'expose' procedure to point to where my Theseus was installed - as opposed to changing the two "well known places" you had already accounted for. Then when I had ran into that issue I commented that code out, but left it in the source, which is the reason why you're seeing the missmatch.

Bad debugging & error reporting on my part, my appologies as that just wasted your time trying to pinpoint where the issue was.

Thanks again Steven...!

40
Utilities / LinearMemoryMap.cmd => new version produces an error...why?
« on: December 23, 2023, 05:06:46 pm »
So Steven Levine published an updated version of this awesome util, but I'm now seeing an error, which I can't quite decipher:

Code: [Select]
[G:\util\theseus]linearmemorymap
Writing results to G:\util\theseus\linearmemorymap-20231223-1059.lst

[G:\util\theseus]G:\OS2\CMD.EXE /c G:\UTIL\MISC\LinearMemoryMap.cmd -  1>G:\util\theseus\linearmemorymap-20231223-1059.lst
Running from G:\util\theseus
NOVALUE signaled at G:\UTIL\MISC\LinearMemoryMap.cmd line 190.
REXX reason = DIR.
Source ="if dir \== '' then".
   545 *-*         Call lineout 'STDERR', 'Exiting.';
Exiting.
       +++   Interactive trace. "Trace Off" to end debug, ENTER to Continue.

   546 *-*         Nop;

   547 *-*         If symbol('RC') \== 'VAR';

   547 *-*         Then;
   548 *-*           rc = 255;

   549 *-*         Exit rc;

ERROR signaled at G:\UTIL\MISC\LinearMemoryMap.cmd line 114.
REXX reason = G:\OS2\CMD.EXE /c G:\UTIL\MISC\LinearMemoryMap.cmd - >G:\util\theseus\linearmemorymap-20231223-1059.lst.
RC = 255.
Source ="cmd".
   545 *-*         Call lineout 'STDERR', 'Exiting.';
Exiting.
       +++   Interactive trace. "Trace Off" to end debug, ENTER to Continue.

   546 *-*         Nop;

   547 *-*         If symbol('RC') \== 'VAR';

   549 *-*         Exit rc;


I'm running this from the Theseus directory, the linearmemorymap-20231223-1059.lst is created, and appears to be fine.

Any ideas?

41
I have an amateur/hobbyist background in VB.NET but have also written some applications in Python (for Linux), in PHP (for Linux and Windows) and in C (for DOS). I'd like to start experimenting with development for OS/2 but I don't really know a good place to start. I know I'll need OpenWatcom as a compiler.
...
Would anyone have any recommendations for where to start? Equally, does anyone know if there's a legitimate way to obtain either VX-REXX or VisProREXX anymore since I expect they've long since been abandoned now? I've been keeping an eye out for them on eBay but haven't seen them come up at all...

So I would say the following:

1) you need to 'pick your path', that being either VACPP (which really means 3.65.x stuff) or GCC

2) if GCC is your choice, then most likely Watcom C is going to play a role, and others who are much more in-depth on this topic will be able to comment better, but stuff like WRC come into play here

In other words, I suppose the two big questions that you need to answer are:

1) are you writing from 'scratch' OS/2 stuff (for which VACPP is probably best suited, despite some of it's current limitations)

OR

2) are you most interested in porting other Linux / GCC / QT stuff over to our platform?

42
Applications / Re: Panorama Maximum Resolution
« on: December 21, 2023, 08:05:32 pm »
...the BIOS offers Panorama only resolutions it thinks the 'monitor in conjunction with the current connection' (DP, DVI, HDMI, ...) is capable. Then Panorama tries to select the predefined BIOS mode (resolution) which matches best OR tries to patch on of the BIOS modes to a better resolution...

@Andi's description above is spot-on: it is the combination of all of the above components that all come together to negotiate the best display configuration.

@Martin,
Do you have the option to try your config using it's native BIOS as opposed to the UEFI mode?

The other thing to investigate is the memory allocation (framebuffer I believe) needed to support a specific resolution. I can only assume that the UEFI VESA Emulator, once the actual display mode is negotiated, attempts to do so, which is why perhaps the following shows up in the LOG:

Code: [Select]
Product Name: UEFI VESA Emulator v1.0
VBE VRAM size 1000000 (16 MiB) (rounded) 1000000 (16 MiB)

In my experience with SNAP in trying to minimize the amount of memory it tried to allocate/address, and which would typically run up against what OS/2 could possibly access on my machine (ATI 256M video card, but my 1920x1200x2 really doesn't NEED all that space so why should SNAP set-aside that much ram for video card purposes?), I took to setting SNAP to use a much smaller framebuffer with 'gaoption vidmem 32', which sets that to 32M total.

By my calculation your 3840x2160 in 32-bit colour needs about 32M, so the current size shown in the LOG is too small, although it is perfectly fine for the resolution that Panorama is picking up for it's use at that time.

In comparison my 1920x1200 in 32-bit colour only needs 9M, and even with dual-head display that's only 18M.

43
Applications / Re: Panorama Maximum Resolution
« on: December 21, 2023, 12:05:10 am »
...I can not say that my HDMI cable is the best quality, but my only reference here is that the same machine (TP T14s with Dual Boot) with Windows 11, with this same cable, is producing "3840x2160" output through the HDMI port to the 4K TV...

Oh, I'm sorry but I missed that.

In that case, you are good-to-go, and this would appear to be an OS/2 matter.

I'm curious, does Panorama offer the functionality to capture your EDID and dump it out? If the answer is YES, you could certainly do that and parse it through a number of EDID decoders.

Ultimately, assuming the BIOS is not the issue here, the reason why this matters is that a video device driver would want to know what the output device is capable of displaying, and EDID is the record structure meant to facilitate that communication.

So again, assuming Panorama is reading EDID (which I believe it is), it should conclude based on that record what the max capability of your display is, and presuming that your video hardware is capable of addressing that space, it would proceed to use that configuration.

I have a boat-load of SNAP experience, including building custom EDID records and flashing those one displays, unfortunately I do not know the Panorama side of this.

44
Applications / Re: Panorama Maximum Resolution
« on: December 20, 2023, 11:24:33 pm »
Martin,

The HDMI cable matters here. More specifically, the cable itself must be designed to comply with a specific HDMI specification. Beyond that, there are real differences between 'Standard HDMI' and 'High Speed HDMI', latter one being capable fo 4K resolutions for example, while the former is limtted to 720p or 1080i (TV speak here to simplify).

Here is a nice, quick and simple article tht summarizes it all => https://www.cdw.com/content/cdw/en/articles/hardware/hdmi-cable-buying-guide-learn-all-you-need-to-know-about-hdmi-cables.html

45
Martin, everyone...

1) The question would be, what features you think ArcaOS and OS/2 are lacking when referring to the GUI that you think will be useful?
- Since this is a personal option question, there are no right or wrong answers. I just want to know more about it.

WPS is extremely extensible and configurable. From my perspective XWPS has been able to deliver the right mix of enhancements. Therefore, there are no obvious/blatant functionality gaps that cause me lost time, or are a major hinderance to getting things done.

2) Once you install ArcaOS or even OS/2, what utilities (or customization) do you use to improve the GUI as you like?
- For example, for me now it is must XWP 1.0.16 with xCenter big icons
- Or some others like X-It to have more function buttons on their desktop windows.

X-It for me had a bunch of "nice-to-have" things in it that XWPS never had, or perhaps didn't include in its roadmap.

I still miss the easy stuff like:
- window roll-up/down titlebar quickie
- folder sort titlebar quickie
- text field COPY/PASTE quickies (yes, XWPS has some of it, but not quite in such an easy-to-use way, and not everywhere)

The one thing that bugs me though, and this is very specific to my setup (which is a dual panel SNAP) is the lack of ability to make applications 'sticky' to a particular screen. Basically, I really want my apps and all of their dialogs to open up on the 'parent' window, as opposed to always jumping to the HEAD_0 (vs HEAD_1 - as the parent) window.

Clearly, this is not an issue if I'm starting stuff on HEAD_0, but than again what's the point of doing dual-head displays if I am always "defaulted" to HEAD_0??? lol

Parallel to this is the concept of having various pop-ups (think lSwitch task-picked window) showing in the currently active HEAD, as opposed to be centered between both of them. But these kind of things are usually app specific, and without deep diving into something like SNAP (which as best as I can tell has been basically 'put out to the pasture') it's hard to imagine this going anywhere.

Pages: 1 2 [3] 4 5 ... 89