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
Setup & Installation / Re: Are there any 8GB Nvme compatiable motherboard
« on: January 20, 2024, 06:55:02 pm »
What do you mean by the full 8GB's? OS/2 is limited to 4GB address space, minus PCI address space...

Yeah, I'm thinking Doug is looking for a hardware config Dave that allows OS/2 to set aside the max <4GB space it can possibly use, as well as anything above that 4GB mark for ramdisk...heck, I suppose you don't necessairly have to stop at 8GB, but not sure what one might need a bigger ramdisk for.

In comparison to Dave's numbers, here is what my ancient MSI board shows:

Code: [Select]
Total physical memory:      8,191 MB
Accessible to system:       3,199 MB
Additional (PAE) memory:    4,992 MB

32
Applications / Re: NewView - control over NEW window placement?
« on: January 09, 2024, 07:54:11 pm »
Hi Alex,

Quote
Unfortunately the off-set placement of every NEW window is something that Alex doesn't see the benefit of changing

It would be more accurate to say that I couldn't find a practical way to avoid it that didn't cause more problems.

Fair enough, your list email response was rather terse and pointed to technical reasons, which I concluded to mean that per your assessment there was no ROI on pursuing this further.

...I originally did try to eliminate the offset when opening on a different virtual desktop. The problem is that NewView only knows about the most recently opened existing window, so there's no way to skip the offsetting in a way that's consistent....I did consider trying to have NewView detect and scan through every possible existing instance, but this would have been a major undertaking, with significant overhead, that I wasn't confident I could make work in any event, and for IMHO very little practical payoff...

I can certainly appreciate the thinking going into this.

So how about a counter-proposal, one that will tie in to the argument that Andi made in this last post: why even force the offset on the user?

Forget about coming up with a very sophisticated logic to deal with all the permutations. You are absolutely right to say that pursing such an approach would be of little practical gain. In fact, given Andi's post and my own dislike of the offset I would suggest that we introduce a Settings option to turn ON or OFF the offset.

That way no existing (significant I'm hoping, but I'm already skating on thin ice here :-[) code changes need to happen as hopefully the offset can be set to either the CURRENT value (and program works exactly as it does today), or to an ALTERNATIVE value of 0 (zero), so that no offset is applied.

Would this not be viable?

33
Programming / Re: Installing VisualAge 4 on ArcaOS 5.x
« on: January 08, 2024, 03:30:51 pm »
...Turns out I somehow didn't copy the entire installation CD on my VM, so VACPP.RSP and other files weren't where expected...

Not sure what the software level is that you ended up deploying, but if it's the base stuff make sure you apply the fixpak release that's avaialable, for VACPP 4.0 that's just FP1.

34
Applications / Re: NewView - control over NEW window placement?
« on: January 08, 2024, 03:25:23 pm »
David, everyone...

FYI - there is a new NewView release on Hobbes - seems to fix this issue...

Yup, we covered this in the Testers' List, the issue I had originally reported (the post above) was addressed, good there.

Unfortunately the off-set placement of every NEW window is something that Alex doesn't see the benefit of changing, or perhaps to be more true to his statement, "...deliberate choice..." as there are various technical reasons to leave it as-is, subseuently that's not going to change.

I disagree with that direction, but I'm in no position to force the change, so I'll run with what is being handed out! (know thy "swimlane" lol)

To your "Thank You Alex" point, absolutely agree with that statement, just not the design decision itself.

35
Networking / Re: Updated Samba Client
« on: January 06, 2024, 11:43:41 pm »
...It would be nice if some others could test the updated smbd / netdrive plugin to get some more data points...
OK, but what is the exact use-case you are looking for Paul?

I had previously tried your client update and that results is a "face meets brick wall" (LOL) event here, been following the thread all along, but so far I'm not picking up on anything that I can specifically test out.

36
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.

37
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.

38
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)?

39
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.

40
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???

41
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.

42
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!!!

43
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!

44
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...!

45
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?

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