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 6 ... 89
46
Networking / Re: Updated Samba Client
« on: December 18, 2023, 05:25:47 am »
Only thought is what's VIRTUALADDRESSLIMIT set to? Not that Samba should be using lots of RAM, but still of interest...

VIRTUALADDRESSLIMIT=2048

47
Networking / Re: Updated Samba Client
« on: December 18, 2023, 12:11:11 am »
Hey Dave!

@Dariusz - FYI, there is a Jansson package at netlabs-exp. It seems to work OK here.

Right on, thank you. My yum search missed it b/c I left out the ".dll".

So feedback on what I'm seeing, which puts me in a really weird "no-go" situation: NDCTL comes up fine, it maps the shares successfully, but immediately afterwards as I attempted to actually access the shares WPS completely locked-up.

Hmm...OK, I initially thought: maybe some kind of a conflict between the new ndpsmb.dll and the old one (although I shut-down the service in NDCTL before tossing the new DLL into place, and it would appear it was fine at that time). So off I went to re-boot my machine...

...and upon coming back was greeted by a never seen before WPS/Desktop msg: "...system does not have enough memory to show/load Desktop..."!!! ugh???? Yeah, the Desktop never populated, the WarpCenter came up, all my utils fired up, but not the Desktop, just the BLUE screen.

OK, so mind you I am running a crazy large JFS cache, that being 1.2G, but it's awfully nice for my purposes, and I regularly have this machine up for 20-24 days (longest ever was 45 actually) and what usually brings it down is the low shared memory.

But...testing it is, so off I went downsizing the cache, a few attempts later having gotten to 0.5G and still showing the very same Desktop error message I had decided to STOP.

Sooo...whatever is causing the issue is a brick-wall for me. Happy to troubleshoot Paul, tell me what level of debugging you might like...

48
Networking / Re: Updated Samba Client
« on: December 17, 2023, 05:50:16 pm »
Hi Paul,

Deployed in my config of: remote Samba shares are on the NAS box and Win7Pro machine.

NDCTL appears to successfully start the manager, but no shares actually show.

I find the following in the ndctl.log:

Code: [Select]
11:39:04.250:
NetDrive for OS/2(R) Control Program version 3.1.6.941 Nov 17 2019

11:39:04.250: 2023-12-17

11:39:04.250: NDFSDIR environment variable found: G:\util\NDFS
11:39:04.250: NetDrive working directory is G:\util\NDFS
11:39:04.250: File system driver name is NDFS32.
11:39:04.260: NetDrive configuration file 'G:\util\NDFS\ndctl.cfg' has been processed.
11:39:04.260: Registered Version

11:39:04.260: Registered to Dariusz Piatkowski

11:39:04.260: [   local] internal plugin has been initialized.
11:39:04.260: [  ndpftp] (level 2) plugin has been loaded.
11:39:04.260: [  ndpiso] (level 2) plugin has been loaded.
11:39:04.270: [  ndpdav] (level 2) plugin has been loaded.
11:39:04.280: NDF0033: The system can't load the module: JANSSON4
11:39:04.280: NDF0029: [  ndpsmb] plugin has not been loaded.
11:39:04.280: NDF0007: The system error is SYS0002
11:39:04.290: [ ndpnfs3] (level 3) plugin has been loaded.
11:39:04.290: Initialization completed. The control program is running.
11:39:04.420: NDF0045: Resource SMBFS (W) specified in file volumes.cfg, line 4 was not mounted
11:39:04.420: NDF0007: The system error is SYS0050
11:39:04.420: NDF0045: Resource SMBFS (W) specified in file volumes.cfg, line 6 was not mounted
11:39:04.420: NDF0007: The system error is SYS0050
11:39:04.420: NDF0045: Resource SMBFS (W) specified in file volumes.cfg, line 7 was not mounted
11:39:04.420: NDF0007: The system error is SYS0050
11:39:04.420: NDF0045: Resource SMBFS (W) specified in file volumes.cfg, line 10 was not mounted
11:39:04.420: NDF0007: The system error is SYS0050
11:40:48.410: NetDrive Control Program has been interrupted by File System Driver.

...but seeing this in the above LOG:

Quote
NDF0033: The system can't load the module: JANSSON4

makes me think another module besides smbcl418 & gnutls30 is needed?

I didn't get any hits with "yum provides */jansson4"...

Thanks as always!

49
Applications / Re: XWP v1.0.16
« on: December 17, 2023, 05:33:58 pm »
Hey Rich!

having selected the MEDIUM size option I came to discover what I felt was a rather curious font/sizing choice for the default XWP menu, that being: '9. WarpSans Bold'. [...]  it feels (again, VERY subjective lol) like the [non-Bold] 10 pt is the better fitting size.

My overriding goal In implementing 'Text Size' was "user acceptance". Put another way, avoiding anything that would give people a reason for not using a feature that would clearly benefit them.

First and foremost in the list of things to avoid was any consideration of aesthetics. I fully agree with you that 'WarpSans Bold' at any size is a lousy font for menus. But, after all these years of people not complaining about it, it wasn't for me to go changing the status quo. By having Text Size use the exact same fonts that have been in place since eCS 1.0, no one can claim "aesthetic degradation" as a reason for not using it.
...

Understood, and your point is well taken.

Any ideas where WarpCenter hides it's font selection??? That's the only remaining piece of getting to a suitable display configuration for my OS/2 box...tried the old "drag & drop" font, but that didn't stick.

OK, there is something else I'd like to toss into the conversation though: I'm getting weird looking file sizes in the Xview folders, take a look at the attached screenshot.

What's weird about this is that NOT all files show this behaviour.

For example, looking at '192.168.1.10_20231215.txt', in CL it shows up as:

Code: [Select]
12-15-23 11:44p        11,736      0 a---  192.168.1.10_20231215.txt

...and clearly XWP does show that size, but it is followed by a string ".99,999,999,999,977"???

Here is an even weirder use-case, take a look at '192.168.1.10_20231214.txt'

Code: [Select]
12-14-23  9:55p         4,362      0 a---  192.168.1.10_20231214.txt

...and in XWP that shows up as "436,2.0,000,000,000,001". It's almost as if the decimal place markers get tossed into the wrong place???

Is this a user configuration mistake?

The only such user-adjustable config I can think of is the 'WPS => Status Bars => P2', but that really appears to be applicable only to status bars.

50
Setup & Installation / Re: sigh....Python3 upgrade - curl problem?
« on: December 14, 2023, 02:30:20 am »
Last update on my part, maybe relevant to others who might run into this type of an issue.

I proceeded with the remaining python package updates to bring things up to the python2 release level. Subsequently, YUM/RPM/ANPM all appear to work successfully with the following combination of packages having been deployed:

Code: [Select]
Installed Packages

python-rpm-macros.noarch                      3.9-3.oc00
python-srpm-macros.noarch                     3.9-3.oc00
python-unversioned-command.pentium4           3.9.17-1.oc00

python2-dateutil.noarch                       1:2.8.1-3.oc00
python2-deltarpm.pentium4                     3.6-1.oc00
python2-libxml2.pentium4                      2.9.10-3.oc00
python2-pycurl.pentium4                       7.44.1-3.oc00
python2-rpm.pentium4                          4.13.0-20.oc00
python2-six.noarch                            1.10.0-2.oc00
python2.7.pentium4                            2.7.18-3.oc00

python3.pentium4                              3.9.17-1.oc00
python3-dateutil.noarch                       1:2.8.1-3.oc00
python3-libs.pentium4                         3.9.17-1.oc00
python3-pycurl.pentium4                       7.44.1-3.oc00
python3-six.noarch                            1.10.0-2.oc00

There are a couple more python2 packages that perhaps could be deployed (in my specific use-case), but I haven't taken that chance:

- python2-rpm-macros.noarch                     1-3.oc00
- python2.7-unversioned-command.pentium4        2.7.18-3.oc00

51
Applications / Re: XWP v1.0.16
« on: December 11, 2023, 03:18:58 am »
Rich!

First of all, as many others have stated: big 'Thank You' for not only keeping this great WPS enhancement alive, but improving it as well!

Playing with the new Text Size - was on Standard - I selected Medium size, clicked Test and was a bit surprised to see the Properties notebook shrink in size. Is that supposed to happen?

Absolutely!

The size of dialog windows and their contents is proportional to the size of the default system font. IOW, a bigger font produces bigger dialogs. This worked great back in the days when all dialogs used the default font (System Proportional) for their text. As the font size increased, the dialogs automatically grew to accommodate. Then along came WarpSans...
...
'Text Size' addresses this by *always* setting the default system font to a size that will comfortably handle whatever size of WarpSans you choose. For the "Small" and "Medium" (9 and 10pt WarpSans) sizes, that's 10pt System Proportional. The result is dialogs that are the "correct" size - in this case, smaller.

A question and suggestion (albeit a personal taste based one):

1) QUESTION
The 'Text Size' tab HELP states the following in relation to those using SNAP:

Code: [Select]
Note: if you use SNAP/Scitech Graphics, please remove any SET SDDFONTSIZE= or SET SDDFONTDPI= entries from 'config.sys' before rebooting to ensure expected results.

Can you elaborate further?

I do use SNAP, and upon seeing this I REMed the statements in my CONFIG.SYS. But several reboots later, having saived my new INI files (backup) I turned these back ON and see no difference. Therefore I am curious what you were worried about?

2) SUGGESTION
1920x1200 display here (x2 given SNAP multi-head). I had previously moved all my FOLDERS to using 10. WarpSans, and was toying with the idea of adjusting the MENUs as well, etc. Just never got around to it.

Given your XWP update however, and having selected the MEDIUM size option I came to discover what I felt was a rather curious font/sizing choice for the default XWP menu, that being: '9. WarpSans Bold'.

Take a look at the attached couple of screenshots.

- first one is the default XWP MEDIUM setting
- the second one is my tweaked setting of '10. WarpSans' (mostly b/c I prefer the light fonts)

Given the overall proportionality of the results it feels (again, VERY subjective lol) like the 10 pt is the better fitting size.

52
Setup & Installation / Re: sigh....Python3 upgrade - curl problem?
« on: December 11, 2023, 12:37:25 am »
Hi Alex,

For the record, to clear up any confusion: ANPM does use Python 2. (Blame the Python guys for deciding to make Python 3 a different i.e. incompatible scripting language from Python 2.)...

OK, so ANPM does need Python2, perfect.

FWIW, this is not a blame assignment take on my part, rather I simply want to understand the operational criteria within which I need to contain the PythonX installs on my system.

The priority here being: ANPM & our RPM/YUM installations working perfectly, everything else becomes a secondary thing.

So taking Dave's response further: can you define what specific PythonX level of other utils we should be matching up here? Or should I consider your response above to me: pick up everything that's 'python2-xx'?

I just want to play it safe...that approach has worked for me for quite a long time, and I was holding off on this Python upgrade for a very long time primarily because of that reason.

Thanks, as always!

53
Programming / EXE header 'Module' field change - how?
« on: December 10, 2023, 09:09:05 pm »
This is more of a nuisance driven inquiry, but the UPSMONS util (UPS Monitor) has the following EXEHDR defintion:

Code: [Select]
...
Module:                         TEMPLATE
Description:                    VisPro/REXX Runtime Version 2.01, COPYRIGHT (c)
HockWare Inc. 1994
Executable format level:        0
CPU type:                       Intel 80386 or upwardly compatible
Operating system:               Operating System/2

Module type:                    Program
                                NO internal fixups in executable image
Application type:               Uses PM Windowing API
...

Subsequently, TEMPLATE is what shows up in Theseus instead of 'UPSMONS'.

Looking at this I thought: "hmm, so I'm guessing this may be coming from the EXE HDR", and indeed it is, "so how can I change that?"

Is there a quick way to to do so? I'm thinking one of the OS/2 Toolkit utils may do this...but nothing obvious jumps out at me looking at the "Tools" INF.

Any ideas?

54
Setup & Installation / Re: sigh....Python3 upgrade - curl problem?
« on: December 10, 2023, 08:38:19 pm »
...let me add the following:

Given the following RPM package installs on my system today:

Code: [Select]
Installed Packages
python-pycurl.pentium4                        7.19.5.1-2.oc00        installed
python-rpm-macros.noarch                      3.9-3.oc00             installed
python-srpm-macros.noarch                     3.9-3.oc00             installed
python-unversioned-command.pentium4           3.9.17-1.oc00          installed
python2-deltarpm.pentium4                     3.6-1.oc00             installed
python2-libxml2.pentium4                      2.9.10-3.oc00          installed
python2-rpm.pentium4                          4.13.0-20.oc00         installed
python2.7.pentium4                            2.7.18-3.oc00          installed
python3.pentium4                              3.9.17-1.oc00          installed
python3-dateutil.noarch                       1:2.8.1-3.oc00         installed
python3-libs.pentium4                         3.9.17-1.oc00          installed
python3-pycurl.pentium4                       7.44.1-3.oc00          installed
python3-six.noarch                            1.10.0-2.oc00          installed

I seem to be OK.

However, looking at what's out there in the repositories, there are basically:

1) python
2) python2
3) python3

versions of most of such RPM packages, albeit not all (meaning, no one-to-one match for each package).

So how do we know what should be installed, or to be more specific: which pythonX versions are needed by which apps? Seems pretty easy to answer, after all that's what dependency checking is for...but if that was the case shouldn't ANPM have complained about my attempt to update python-pycurl??? (maybe it can't do that b/c it doesn't check the packages that are being updated against it's built-in "bare necessities" list?)

In other words: I never spotted ANPM documented as requiring Python2 for example...clearly I ran it for quite some time, up until today, using python-dateutil instead of python2-dateutil...so what are the real/known dependencies?

55
Setup & Installation / Re: sigh....Python3 upgrade - curl problem?
« on: December 10, 2023, 08:25:18 pm »
Martin & JTA,

Thank you both for your feedback!

While I was aware of what you both highlighted, I did not realize that certain python2 version packages must not be upgraded, at least my results so far indicate that be the case for the python-pycurl package.

I'm reluctant to execute any other upgrades, and will monitor whether the python3-dateutil needs to be either reverted, or the python-dateutil re-installed.

56
Setup & Installation / Re: sigh....Python3 upgrade - curl problem?
« on: December 10, 2023, 08:20:50 pm »
Hi Dave,

Thanks for the quick response.

Hmm, I never forced any Python upgrades besides the python2.7/python3 one and see I have python2-pycurl and python3-pycurl installed. Lots of things are python2 including ANPM.
If yum itself works, install python2-curl or perhaps download the zip and install the 8 files manually to get ANPM working then install the package.

Alright...so I continued to troubleshoot the issue in the meantime, as in reviewing the scripts ANPM uses and concluded that it's a Python2 dependent implementation.

Therefore, precisely as you pointed out it made sense to bring back the pycurl RPM in order for the current YUM/ANPM to get back into working status.

To that end, I now see the following:

Code: [Select]
[G:\]rpm -i /test/python-pycurl-7.19.5.1-2.oc00.pentium4.rpm
error: Failed dependencies:
        python-pycurl < 7.44.1-3.oc00 is obsoleted by (installed) python3-pycurl-7.44.1-3.oc00.pentium4

...clearly the python-pycurl and python3-pycurl are incompatible with each other, and in hindsight it seems like I should NOT have attempted to upgrade anything beyond just the core Python itself (at which point in time this becomes a little nonsensical / counterintuitive, after all, if the Python runtime is now at 3.x and if I happen to be using other python utils, shouldn't I be updating them all to make sure I am using the matching python stuff???).

Anyways, OK, so it looks like I'm going to force RPM to install python-pycurl regardless:

Code: [Select]
[G:\]rpm -ivh --nodeps /test/python-pycurl-7.19.5.1-2.oc00.pentium4.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:python-pycurl-7.19.5.1-2.oc00    ################################# [100%]

Yup, all good now: YUM at CLI works, as does ANPM.

57
Setup & Installation / sigh....Python3 upgrade - curl problem?
« on: December 10, 2023, 06:06:09 pm »
So this whole 'upgrade to python3' is by now a well traversed path, I did my reading, took to the CLI approach of executing: 'yum install python3 python2.7', which gave me the following results:

Code: [Select]
[G:\]yum install python3 python2.7
Loaded plugins: changelog, downloadonly, ps, replace, verify
Setting up Install Process
Resolving Dependencies
There are unfinished transactions remaining. You might consider running yum-comp
lete-transaction first to finish them.
--> Running transaction check
---> Package python2.7.pentium4 0:2.7.18-3.oc00 will be installed
--> Processing Dependency: python-rpm-macros for package: python2.7-2.7.18-3.oc00.pentium4
--> Processing Dependency: python-srpm-macros for package: python2.7-2.7.18-3.oc00.pentium4
---> Package python3.pentium4 0:3.9.17-1.oc00 will be installed
--> Processing Dependency: python3-libs = 3.9.17-1.oc00 for package: python3-3.9.17-1.oc00.pentium4
--> Processing Dependency: python39.dll for package: python3-3.9.17-1.oc00.pentium4
--> Running transaction check
---> Package python-libs.pentium4 0:2.7.6-25.oc00 will be obsoleted
--> Processing Dependency: python-libs = 2.7.6-25.oc00 for package: python-2.7.6-25.oc00.pentium4
---> Package python-rpm-macros.noarch 0:3.9-3.oc00 will be installed
---> Package python-srpm-macros.noarch 0:3.9-3.oc00 will be installed
---> Package python3-libs.pentium4 0:3.9.17-1.oc00 will be obsoleting
--> Running transaction check
---> Package python.pentium4 0:2.7.6-25.oc00 will be obsoleted
---> Package python-unversioned-command.pentium4 0:3.9.17-1.oc00 will be obsoleting
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================

 Package                      Arch       Version            Repository     Size
================================================================================

Installing:
 python-unversioned-command   pentium4   3.9.17-1.oc00      netlabs-rel   8.6 k
     replacing  python.pentium4 2.7.6-25.oc00
 python2.7                    pentium4   2.7.18-3.oc00      netlabs-rel    18 M
 python3                      pentium4   3.9.17-1.oc00      netlabs-rel    22 k
 python3-libs                 pentium4   3.9.17-1.oc00      netlabs-rel    13 M
     replacing  python-libs.pentium4 2.7.6-25.oc00
Installing for dependencies:
 python-rpm-macros            noarch     3.9-3.oc00         netlabs-rel   9.1 k
 python-srpm-macros           noarch     3.9-3.oc00         netlabs-rel    15 k

Transaction Summary
================================================================================

Install       6 Packages

Total download size: 30 M
Is this ok [y/N]:

INPUT => Y

Downloading Packages:
(1/6): python-rpm-ma | 9.1 kB  00:00
(2/6): python-srpm-m |  15 kB  00:00
(3/6): python-unvers | 8.6 kB  00:00
(4/6): python2.7-2.7 |  18 MB  00:07     ====-] 2.1 MB/s |  17 MB  00:00 ETA
(5/6): python3-3.9.1 |  22 kB  00:00
(6/6): python3-libs- |  13 MB  00:05     ==== ] 1.9 MB/s |  12 MB  00:00 ETA
--------------------------------------------------------------------------------

Total                                           2.2 MB/s |  30 MB     00:13

Running Transaction Check
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Warning: RPMDB altered outside of yum.
  Installing : python-srpm-macros-3.9-3.oc00.noarch                         1/8
  Installing : python3-libs-3.9.17-1.oc00.pentium4                          2/8
  Installing : python3-3.9.17-1.oc00.pentium4                               3/8
  Installing : python-rpm-macros-3.9-3.oc00.noarch                          4/8
  Installing : python2.7-2.7.18-3.oc00.pentium4                             5/8
  Installing : python-unversioned-command-3.9.17-1.oc00.pentium4            6/8
  Erasing    : python-2.7.6-25.oc00.pentium4                                7/8
  Erasing    : python-libs-2.7.6-25.oc00.pentium4                           8/8

Rpmdb checksum is invalid: dCDPT(pkg checksums): python3-libs.pentium4 0:3.9.17-1.oc00 - u

Following this upgrade my inventory of python RPM packages installed is as follows:

Code: [Select]
Installed Packages
python-dateutil.noarch                        2.6.0-1.oc00           installed
python-pycurl.pentium4                        7.19.5.1-2.oc00        installed
python-rpm-macros.noarch                      3.9-3.oc00             installed
python-srpm-macros.noarch                     3.9-3.oc00             installed
python-unversioned-command.pentium4           3.9.17-1.oc00          installed
python2-deltarpm.pentium4                     3.6-1.oc00             installed
python2-libxml2.pentium4                      2.9.10-3.oc00          installed
python2-rpm.pentium4                          4.13.0-20.oc00         installed
python2.7.pentium4                            2.7.18-3.oc00          installed
python3.pentium4                              3.9.17-1.oc00          installed
python3-libs.pentium4                         3.9.17-1.oc00          installed

Therefore, my next logical (and maybe this was a mistake???) step was to upgrade all the pythonx stuff to python3, which I went to ANPM for:

1) python3-dateutil - this seems to have gone fine
Code: [Select]
----------[ 10 Dec 2023 10:26:12 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_install_dep.py python3-dateutil
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Return code: 0
----------[ 10 Dec 2023 10:26:25 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_install.py python3-dateutil
No argument pipe.
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
Running Transaction Check
Warning: RPMDB altered outside of yum.
PackageSackError(): Rpmdb checksum is invalid: dCDPT(pkg checksums): python3-six.noarch 0:1.10.0-2.oc00 - u
Error: Rpmdb checksum is invalid: dCDPT(pkg checksums): python3-six.noarch 0:1.10.0-2.oc00 - u
PackageSackError()
Return code: 0
----------[ 10 Dec 2023 10:26:41 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_list.py
Setting up yum
No argument pipe.
Adding temporary repositories
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
Initializing cache
Requesting package list
Return code: 0
----------[ 10 Dec 2023 10:27:05 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_info.py python3-six
Warning: progress pipe not available.
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Return code: 0
----------[ 10 Dec 2023 10:27:17 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_files.py installed python3-six
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Return code: 0
----------[ 10 Dec 2023 10:27:51 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_files.py installed python-unversioned-command
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Return code: 0
----------[ 10 Dec 2023 10:28:02 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_info.py python-unversioned-command
Warning: progress pipe not available.
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Return code: 0

2) python3-curl - this seems to have NOT gone fine
Code: [Select]
----------[ 10 Dec 2023 10:29:24 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_install_dep.py python3-pycurl
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
No argument pipe.
Return code: 0
----------[ 10 Dec 2023 10:29:32 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_install.py python3-pycurl
No argument pipe.
Enabling temporary repository arcanoae-sub
Enabling temporary repository arcanoae-exp
Enabling temporary repository arcanoae-stage
Enabling temporary repository arcanoae-arcaos
Running Transaction Check
Warning: RPMDB altered outside of yum.
PackageSackError(): Rpmdb checksum is invalid: dCDPT(pkg checksums): python3-pycurl.pentium4 0:7.44.1-3.oc00 - u
Error: Rpmdb checksum is invalid: dCDPT(pkg checksums): python3-pycurl.pentium4 0:7.44.1-3.oc00 - u
PackageSackError()
Return code: 0
----------[ 10 Dec 2023 10:29:58 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_list.py
Traceback (most recent call last):
  File "G:\UTIL\ANPM\scripts\yum_list.py", line 6, in <module>
    import yum
  File "G:/usr/lib/python2.7/site-packages/yum/__init__.py", line 52, in <module>
    import config
  File "G:/usr/lib/python2.7/site-packages/yum/config.py", line 30, in <module>
    from parser import ConfigPreProcessor, varReplace
  File "G:/usr/lib/python2.7/site-packages/yum/parser.py", line 4, in <module>
    import urlgrabber
  File "G:/usr/lib/python2.7/site-packages/urlgrabber/__init__.py", line 55, in <module>
    from grabber import urlgrab, urlopen, urlread
  File "G:/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 512, in <module>
    import pycurl
ImportError: No module named pycurl
Return code: 0
----------[ 10 Dec 2023 10:30:00 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_list.py available
Traceback (most recent call last):
  File "G:\UTIL\ANPM\scripts\yum_list.py", line 6, in <module>
    import yum
  File "G:/usr/lib/python2.7/site-packages/yum/__init__.py", line 52, in <module>
    import config
  File "G:/usr/lib/python2.7/site-packages/yum/config.py", line 30, in <module>
    from parser import ConfigPreProcessor, varReplace
  File "G:/usr/lib/python2.7/site-packages/yum/parser.py", line 4, in <module>
    import urlgrabber
  File "G:/usr/lib/python2.7/site-packages/urlgrabber/__init__.py", line 55, in <module>
    from grabber import urlgrab, urlopen, urlread
  File "G:/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 512, in <module>
    import pycurl
ImportError: No module named pycurl
Return code: 0
----------[ 10 Dec 2023 10:39:59 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_populate.py
Traceback (most recent call last):
  File "G:\UTIL\ANPM\scripts\yum_populate.py", line 6, in <module>
    import yum
  File "G:/usr/lib/python2.7/site-packages/yum/__init__.py", line 52, in <module>
    import config
  File "G:/usr/lib/python2.7/site-packages/yum/config.py", line 30, in <module>
    from parser import ConfigPreProcessor, varReplace
  File "G:/usr/lib/python2.7/site-packages/yum/parser.py", line 4, in <module>
    import urlgrabber
  File "G:/usr/lib/python2.7/site-packages/urlgrabber/__init__.py", line 55, in <module>
    from grabber import urlgrab, urlopen, urlread
  File "G:/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 512, in <module>
    import pycurl
ImportError: No module named pycurl
Return code: 0
----------[ 10 Dec 2023 10:40:01 ]----------
Executing: @python2.7 G:\UTIL\ANPM\scripts\yum_list.py
Traceback (most recent call last):
  File "G:\UTIL\ANPM\scripts\yum_list.py", line 6, in <module>
    import yum
  File "G:/usr/lib/python2.7/site-packages/yum/__init__.py", line 52, in <module>
    import config
  File "G:/usr/lib/python2.7/site-packages/yum/config.py", line 30, in <module>
    from parser import ConfigPreProcessor, varReplace
  File "G:/usr/lib/python2.7/site-packages/yum/parser.py", line 4, in <module>
    import urlgrabber
  File "G:/usr/lib/python2.7/site-packages/urlgrabber/__init__.py", line 55, in <module>
    from grabber import urlgrab, urlopen, urlread
  File "G:/usr/lib/python2.7/site-packages/urlgrabber/grabber.py", line 512, in <module>
    import pycurl
ImportError: No module named pycurl
Return code: 0

Sure enough, ANPM is no longer able to pull anything up, reports a pipe error, although from CLI I get the following:

Code: [Select]
[G:\]yum list python* |less
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:

   No module named pycurl

Please install a package which provides this module, or
verify that the module is installed correctly.

It's possible that the above module doesn't match the
current version of Python, which is:
2.7.18 (default, Dec 27 2021, 15:11:56)
[GCC 9.2.0 20190812 (OS/2 RPM build 9.2.0-5.oc00)]

If you cannot solve this problem yourself, please go to
the yum faq at:
  http://yum.baseurl.org/wiki/Faq

So it would appear that installing python3-pycurl obsoleted python-pycurl (which I would have expected is the correct thing to do), but for some reason ANPM continues to see python 2.7.18 as the version it is executing.

From any CLI when checking for the installed Python3 version I get the following:

Code: [Select]
[G:\]python --version
Python 3.9.17

...so clearly I'm running Python3, but ANPM is still using 2.7.18, is that by design?

Either way, any ideas how I can get back to a working YUM/RPM/ANPM config?...and what (if anything) do I do about the remaining pythonx RPM packages (do I upgrade, or leave alone)?

OH, BTW: a system reboot was executed to rule out any other impacts, results are the same

58
Applications / Re: LarsenCommander - new test version
« on: December 03, 2023, 06:53:15 pm »
Andi,

...
On Samba shares I can not get more then about 36MBytes/s. No matter what the other system is running. I think this is limited by our netdrive/samba client setup. It's not the GBit network. You can check with ftp to the same system and will get something more close to 1GBit (80-90MByte/s IIRC).

Totally agree, here is what Kai Uwe Rommel's excellent NETIO utility reports ('orclsrvr' is my Win7Pro box on the LAN):

Code: [Select]
[G:\]netio -t orclsrvr

NETIO - Network Throughput Benchmark, Version 1.30
(C) 1997-2008 Kai Uwe Rommel

TCP connection established.
Packet size  1k bytes:  108.65 MByte/s Tx,  82.77 MByte/s Rx.
Packet size  2k bytes:  109.66 MByte/s Tx,  108.81 MByte/s Rx.
Packet size  4k bytes:  108.43 MByte/s Tx,  111.03 MByte/s Rx.
Packet size  8k bytes:  106.60 MByte/s Tx,  105.70 MByte/s Rx.
Packet size 16k bytes:  104.48 MByte/s Tx,  9.06 MByte/s Rx.
Packet size 32k bytes:  110.89 MByte/s Tx,  111.15 MByte/s Rx.

So the pipe is big enough, althought the severe drop with the 16k packet is always there, but otherwise it's pretty much using the full Gig.

Just to stay consistent in my testing (given that the network throughput is being tested against a different box - not the NAS one) I re-ran the same test but just with the NEW LCMD version:

1) from SAMBA WIN7 share to ramdisk
NEW: Peak=74,012K, Avg=50,996K

The NAS box is just a little slower, although I do NOT see this when moving stuff between the Win7 and NAS boxes, so that tells me it is indeed our Samba client.

...Ramdisk - writting to our RAMDISK is not more than about 55MBytes/s here. It would be faster when using strategy 1 but this would limit to <2GB and does have other big problems which is the reason I stick without /1.

I wonder about your really fast SATA performance. I've tested here with Samsung 850 Pro, Samsung EVO 870, Samsung 860 QVD and various HDDs including my WD black. It seems my 9 year old 4 core system can not handle more than about 160MBytes/s. So I currently I can't test with systems as fast as yours.

For my RAMDISK I just have the following in my CONFIG.SYS:

'BASEDEV=HD4DISK.ADD /V'

...and my QSSETUP.CMD shows:

'ramdisk Y: jfs'

It's been a while since I was testing the performance of that configuration...probably not since I moved from HPFS386 to JFS actually.

Here are the DISKIO metrics for my SSDs:

1) Evo 850
Quote
[G:\]diskio -hd 2
DISKIO - Fixed Disk Benchmark, Version 1.20

Dhrystone 2.1 C benchmark routines (C) 1988 Reinhold P. Weicker
Dhrystone benchmark for this CPU: 6089057 runs/sec

Hard disk 2: 255 sides, 30401 cylinders, 63 sectors per track = 238472 MB
Drive cache/bus transfer rate: 129526 k/sec
Data transfer rate on cylinder 0   : 349038 k/sec
Data transfer rate on cylinder 30399: 318076 k/sec
CPU usage by full speed disk transfers: 6%
Average latency time: 0.1 ms
Average data access time: Disk read error.

Multithreaded disk I/O (4 threads):
 124476 k/sec, 4% CPU usage

and here is the Evo 860
Quote
[G:\]diskio -hd 4
DISKIO - Fixed Disk Benchmark, Version 1.20

Dhrystone 2.1 C benchmark routines (C) 1988 Reinhold P. Weicker
Dhrystone benchmark for this CPU: 6047660 runs/sec

Hard disk 4: 255 sides, 15960 cylinders, 240 sectors per track = 476929 MB
Drive cache/bus transfer rate: 151264 k/sec
Data transfer rate on cylinder 0   : 373430 k/sec
Data transfer rate on cylinder 15958: 384912 k/sec
CPU usage by full speed disk transfers: 21%
Average latency time: 0.0 ms
Average data access time: 0.3 ms

Multithreaded disk I/O (4 threads):
 216995 k/sec, 29% CPU usage

My box is pretty ancient by today's standards as well (MSI 890FXA-GD70), but it has SATA3 SB850 controller, which did make a difference when I moved to that motherboard from my old SATA2 controller one.

...but anyways, that's just a tanget to this core LCMD changes feedback.

59
Applications / Re: LarsenCommander - new test version
« on: December 02, 2023, 08:12:35 pm »
Hi Andi,

I've upload a new version here - https://sourceforge.net/projects/lcmd-git/files/
...
Changes from last release are -
- Fine tuning for dynamic copy buffer size adoption
- Reduce logging while copying huge amount of files (reduces memory needs and log file size)
- Disable playing priority games in hope of better overall system response
- Adding ExceptQ handler (not working yet as own exception is still active)
- Fixed some cppcheck warnings (thanks Andy Willis for that)
- Add some comments for using highmem in some places (currently not used)
- Add writing to PmPrintf queue in parallel to log file when #ifdef __DEBUG_TRACE__
- Use HighMem for copy buffer

Especially the tuning of the copy buffer algorithm makes a big difference in copy speed in so some cases. At least with my rather fast HDDs and SSDs and big files. But also with Samba shares or other source/targets differences can be observed. All my measurements gave good results...

Application functionality seems to be spot-on.

File xfer performance wise, here are the results for movement of a test 800M AVI file:

1) from SAMBA share to ramdisk
OLD:  Peak=58,270K, Avg=43,550K
NEW: Peak=56,220K, Avg=46,516K

...so I'm thinking this is more about being network bound (1G LAN, but of course the Samba share box - NAS is the limitation here)

2) from ramdisk to SSD drive (Samsung 860 Evo, SATA)
OLD:  Peak= 82,788K, Avg=  45,545K
NEW: Peak=310,118K, Avg=220,910K

...here I'm thinking there is an OBVIOUS and huge difference! In fact I was floored by how much of a change this was, pretty much maxing out the throughput I would normally see on my DISKIO tests, so I'd say this is an extremely good result Andi!!! Cheers to you sir.

Now, a couple of further remarks as I'm wondering if you would consider looking into these further:

1) NOT an obivous bug, but maybe one???
Opening up a MP4 file causes my MPLAYER app to be started, but because I actually have a CMD that drives it (which accepts a parameter - [Input Scaling Factor] "%*" - that pops up as that INPUT box which allows me to input a scaling factor) the video starts playing, but I notice that the MPLAYER app actually was started twice.

This is why I'm thinking it maybe a bug...and perhaps only dealing with instantiating CMD started apps, because doing the very same thing for PDF files for example opens up a single instance of Lucide.

2) file type specific icons
Let me use the example of JPGs. If these have the icon stored as EA, LCMD pulls these in and shows them. However my NAS does not support EAs, and therefore all of the pics simply show a document icon as opposed to the DEFAULT PMVIEW icon.

This behavious applies to numerous other filetypes as well.

Would it therefore be possible to modify LCMD to use default APP-specific ICONS for particular filetype when the EAs do not have the icon information available?

Once again, thank you for maintaining and enhancing LCMD!!!

60
Utilities / Re: touch?
« on: November 27, 2023, 12:27:54 am »
Rick!

...In linux I would just say touch newfile, then I could nano and edit it...touch does exist Ive noticed in Arca but does not act in how I would expect...

Lars' trick is by far the quickest one I think!!! (kudos to you sir 8))

...ok, but having said that, what's the issue you're running into with 'touch'? I just tried it here, no problems...

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