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 ... 88
16
Applications / Re: AcpiDaemon start
« on: January 27, 2024, 10:52:20 pm »
Hmm...always had it in CONFIG.SYS, never tried in startup.cmd, but I am not experiencing the sort of issues you are seeing.

17
Networking / Re: ArcaMapper and Network Protocols
« on: January 27, 2024, 10:49:00 pm »
Mark,

1) If you include 'client max protocol = NT1' in smb.conf, is there a difference?

Further on this topic, you could try setting 'ntlm auth = yes' to force just the use of NTLMv1 authentication protocol. I say this because I see the following in the log:

Code: [Select]
...
[2024/01/26 11:52:44.426000,  5] ../../auth/credentials/credentials_ntlm.c:182(cli_credentials_get_ntlm_response)
  NTLMSSP challenge set by NTLM2
...

which to me means: yup, it's trying to use NTLMv2 authentication.

In fact, 'ntlm auth' and 'lanman auth' go hand-in-hand, both need to be set to 'no' in order to force NTLMv1.

2) Do you have 'name resolve order =' line in your smb.conf?

This has previously caused me some issues as I wasn't able to resolve my lan hostnames and needed to use their static IP addresses. It's been a while though and today things work fine here with the following setting:

'name resolve order = lmhosts host wins bcast'

Above comments based on my reading of O'Reilly's "Using Samba" 3rd ed, 2007 (yup, a little old).

18
Networking / Re: Updated Samba Client
« on: January 27, 2024, 09:40:33 pm »
David,

...On a different subject - on directories with windows exe files, the WPS blocks while apparently it tries to determine the icons for the files. If the files are large it can take a very long time (minutes - like it reads the whole file) to display and free the WPS...

That has always been the bahaviour I've seen on my end.

In particular, I have my general software library on the NAS, which easily serves all the individual PC installs, but that is a set of directories I generally stay away from viewing on my OS/2 machine for the very reason you mentioned.

It's like the whole EXE has to be read in order for ANY info to actually show.

19
Setup & Installation / Re: Are there any 8GB Nvme compatiable motherboard
« on: January 20, 2024, 07:38:46 pm »
Hi Doug,

Anyone aware of a motherboard that handles nvme and provides os/2 access to the full 8gb of main memory?...

What about finding a mb that provides OS/2 with a nice linear memory map (no holes) and using an adapter for nvme chores?

Assuming that the original goal of finding both proves to be a challenge, I am thinking an adapter would be the easier of the two to handle in ad-hoc fasion...I mean as long as the mb provides a nice PCIe x4 (or greater, such as x8 for multiple NVMe drives) you would be good.

20
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

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

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

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

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

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

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

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

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

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

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

Pages: 1 [2] 3 4 ... 88