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 ... 96
1
Storage / How to discover the newly assigned USB drive letter?
« on: May 14, 2025, 05:50:11 am »
I'm using a little nifty REXX script to download pics off of my DSLR's memory card:

- issue the LVM rediscover attached media with '@LVM.EXE /RediscoverPRM'
- if no errors encountered start doing the copy

My problem is that when I created that script I never attempted to figure out what that removable media assigned drive letter is...it was simpler to just use a static name (used to be drive 'W:' and assigned to the disk with LVM) and run with it.

Well, recently I added a few NAS shares to my NetDrive and happened to map this to the drive letter which was previously assigned to the USB storage media card. Now my script doesn't work b/c that old drive letter is no longer usable and the USB stuff is assigned 'D:' instead.

OK, seems simple, but where the heck do I even start with querrying this in REXX?

I took a stab at this by reading through Alex Taylor's "RxLVM Library Reference - Version 0.5.1 - March 18, 2007", but that's really about all sorts of disk functions, so not what I'm looking for.

Any other references I could look up for this functionality?

Thanks!

2
Setup & Installation / Re: Troubleshooting process trap/dump...how?
« on: May 07, 2025, 05:30:10 pm »
UPDATE
======


OK, so perhaps not the real RC for the re-boot issue - I'm still working through that - but I do know what was causing the RSYNC issues I recently started to see.

In short: I have been experiencing problems with Lucide and opening PDFs that are stored on my NAS box.

Opening a single PDF is fine, 90% of the time I can open the 2nd one, 75% of the time I can open the 3rd one, but eventually Lucide comes up and no content shows and Lucide hangs. I can normally use the WPS TaskList to kill that Lucide instance, all others previously opened stay working, re-open the last doc and for the most part that's OK.

This only happens when I open multiple PDFs, which normally isn't the case, so for the most part it's not a big deal...but you know: when it becomes a nuisance is when you do in fact want multiple PDFs open, well, it was time to dig into this.

Seemingly the older versions of the Samba client & NetDrive plugins didn't show this, or at least I do not recall ever having these problems...so off I went redeploying older Samba Client & NetDrive combinations.

The combo I deployed most recently was samba-client-4.10.10-0.oc00.i686.rpm & ndpsmb-3.6.0-20190420.wpi, which means I was running Samba 4.10.10 client and NetDrive 3.6.0 plugin. (client stuff going into \usr\local\bin & \lib locations, etc.)

That did in fact improve my Lucide situation, considerably so, although not entirely.

HOWEVER

...what I did not know is that this combination (or most likely the Samba client) did mess around with the file DATES!!!

Sooo....the local & NAS dates would no longer match, as in: neither the CREATE nor MODIFIED dates were matching, and I couldn't determine what the pattern was either.

This in turn explained the strange RSYNC LOG results I would see where the most recent run of RSYNC if immediately re-ran would right away cause massive discrepancies (given my RYSNC options to match on MODIFIED dates and correct them).

I have now moved to samba-client-4.11.5-0.oc00.i686.rpm & ndpsmb-3.7.3-samba411-20220108.zip, which does correctly show the DATES...and that in turn has allowed RSYNC to breeze through it's regular runs because the vast majority of the files do NOT change.

So my RSYNC issue is "closed" now...lol

Appreciate all the feedback everyone!

3
Setup & Installation / Re: Troubleshooting process trap/dump...how?
« on: May 07, 2025, 04:59:09 pm »
Rsync forks into 3 processes here, backing up over USB.
Ok, cool...thanks for confirming this Dave...i.e. nothing unusual/suspect going on here (at least as far as RSYNC goes  :-\)

4
Setup & Installation / Re: Troubleshooting process trap/dump...how?
« on: May 06, 2025, 08:11:44 pm »
OK, so a bit of an update, and this may ultimately be a RSYNC issue, or perhaps a samba client problem...?

Last night the machine died...TWICE...lol, within 10 mins of each reboot. As it happened my cron schedule has multiple RSYNC jobs scheduled (they do NOT run in parallel though) and the 1st reboot happened in the middle of the 1st RSYNC, and the 2nd during the next scheduled run (different SOURCE & TARGET locations though, but both copying from a LOCAL directory to the NAS box - which is accessed through a NetDrive samba share).

So seeing as I had just about touched on all the other things I could possibly think of, I decided to run the same RSYNC job manually (as in not scheduled).

The RSYNC CLI is this:

RSYNC --archive --delete --progress --stats --whole-file --no-xattrs --human-readable --quiet  --exclude-from=G:\mptn\etc\rsync_exclude --log-file=G:\tmp\log\rsync_REMOTE_backup.log G:/DESKTOP/Automotive V:/public/documents

...but having kicked off this very run manually after much much longer than it normally runs I eventually killed it with CTRL-C in the CLI window, which produced the following error message:

Code: [Select]
...
2025/05/06 13:57:20 [126] rsync: writefd_unbuffered failed to write 4 bytes to socket [sender]: Broken pipe (32)
2025/05/06 13:57:20 [126] rsync: connection unexpectedly closed (78453 bytes received so far) [sender]
2025/05/06 13:57:20 [126] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9.1]
...

Soooo...I'm going to retry this again, but quite honestly I'm at a complete loss as to what's going on here.

This example here normally runs for all of two minutes...yup, that's all. Meanwhile today's run was 4 hrs. long and I suspect there was some kind of networking hangup that was encountered given that last error message.

This CTRL-C kill did not generate a process dump, which I think is the correct outcome.

EDIT #1
======

One more thing: take a look at the attached Theseus screenshot...RSYNC actually seems to create THREE processes, of which two have 2 threads, and the last one has a single thread...is that normal???


EDIT #2
======

...and yet the very next run of RSYNC, albeit with a different SOURCE & TARGET combo, completes just fine!!!

WHAT DA????

5
Setup & Installation / Re: Troubleshooting process trap/dump...how?
« on: May 05, 2025, 05:07:17 pm »
Hi Lars,

1) you are using a very outdated version of FFST (RUN=G:\OS2\EPWDDR3.EXE, DEVICE=G:\OS2\EPWDD.SYS) that predates the stuff that came with  Warp 4 (and after, of course). Do not do that. I suggest to deinstall it. >= Warp 4 comes with everything you need.

OK, so I need a little help here. The OS/2 Toolkit doc "Problem Determination Programmer's Guide" has a decent amount of details on how to USE the SYSTEM and PROCESS dumps, logs, etc...but nowhere does it actually spell out the required pieces that are needed to set this up.

In fact, the complete "PROC DUMP" section of my CONFIG.SYS is as follows:

Code: [Select]
REM ******************************************
REM ***       OS/2 DUMP/TRACE - START      ***
REM ******************************************
DEVICE=G:\OS2\LOG.SYS /OFF
RUN=G:\OS2\SYSTEM\LOGDAEM.EXE /E:g:\tmp\trp
DUMPPROCESS=G:\tmp\trp /F=10240
RUN=G:\OS2\EPWDDR3.EXE
DEVICE=G:\OS2\EPWDD.SYS

REM RUN=G:\OS2\EPWROUT.EXE 1
REM RUN=G:\OS2\EPW.EXE

REM *** USB LARS DEBUG => 2 TRACEBUF lines below
REM TRACEBUF=128 /M=WRAP,QUEUED,NODTI /D=ALL
REM TRACE=ON 225,226
REM ******************************************
REM ***       OS/2 DUMP/TRACE - END        ***
REM ******************************************

...where I actually have all of the above REM'ed out normally and unless I hit an issue I want to track I never have this turned on.

The only mention of FFST I have is in the Toolkit doc, stating the following:

Quote
...The OS/2 Logging Facility device driver LOG$ is not loaded.  To activate logging enter DEVICE=\OS2\LOG.SYS and RUN=\OS2\SYSTEM\LOGDAEM.EXE in config.sys and reboot...

But at least that would imply having those two alone in CONFIG.SYS should be sufficient. I did go back to re-reading the notes and will remove the '/OFF' parameter of the LOG.SYS driver.

Strangely enough I have found no place on my machine where any FFST install/uninstal options exist. The standard 'Selective Uninstall' shows nothing there other than standard Warp4 stuff.

...
2) Lower your VIRTUALADDRESSLIMIT value. I suggest to start with 512 (which is the lowest value and equivalent to having no high memory at all) and then, raise up to a value that is still lower than your current value. If 512 is too low, you will need to start with a value that works for your system. VIRTUALADDRESSLIMIT can only be raised in chunks of 512 MB (0x20000000). XWorkplace kernel object will only select values that are possible. The default value for VIRTUALADDRESSLIMIT is 1024 (MB)...

I will go to this option as the last resort simply due to the fact that my RSYNC jobs have been executing on nightly basis for several years now, no misses.

6
Setup & Installation / Re: Troubleshooting process trap/dump...how?
« on: May 05, 2025, 04:39:14 pm »
Dave and Pete,

Gents, I'm thinking what you pointed out should not be the root cause simply due to the fact that I have about 3 monts on this box since my most recent CPU change, and even less so given the tuning I executed thereafter (memory, etc.). So I would say that the "dust has barely settled", but...point noted, I regularly (every three months or so) clean the various air filters on the case, so I will certainly review all of the above!

Neil,
Understand what you are saying, but what's weird is that I've been using RSYNC for a few years now to routinely do this nightly backup. Sure, RSYNC has had other issues (some of what you pointed to), but never this kind of a re-boot. I suspect RSYNC however is putting on some stress on a part of the system (could be hardware, could be software) that's most likely failing.

Both of the above suggestions have sent me on a bit of a manual maintenance run: CHKDSK all my drives (JFS), etc...about to start all of that actually!

7
Setup & Installation / Troubleshooting process trap/dump...how?
« on: May 05, 2025, 05:51:12 am »
So I've got a weird problem that just seemingly has shown up about a couple of weeks ago: I've seen three separate RSYNC jobs die part-way through a LOCAL backup, and as best as I can tell my OS/2 box reboots at the same time.

Now the strange part is that I can't find anything listed in places like POPUPLOG.OS2 or as TRP files...so it's rather tough to figure out whether this is a hardware or a software issue. At the moment I am leaning towards this being a hardware thing.

Having said that, I know that this is not a CPU cooling problem as I am running a pretty capable setup here and that's something I've been through multiple times so I know there is spare room there...but it could be something else, such as memory, or even CPU/core problems.

Sooo...I went back to my CONFIG.SYS and re-enabled the system LOG stuff I had previously enabled:

Code: [Select]
...
DEVICE=G:\OS2\LOG.SYS /OFF
RUN=G:\OS2\SYSTEM\LOGDAEM.EXE /E:g:\tmp\trp
DUMPPROCESS=G:\tmp\trp /F=10240
RUN=G:\OS2\EPWDDR3.EXE
DEVICE=G:\OS2\EPWDD.SYS
...

Not sure though if there is anything else I should be looking at to try to maximize the data capture should RSYNC cause either that hardware or perhaps software fault again.

What have you used in your previous attempts to narrow this kind of a problem down?

Thanks!

8
JTA!

...With a HostOS (Windows/Linux), virtualization (Virtualbox), and Winflector (pipe 64-bit apps directly into OS/2), all running on a single modern hardware platform (laptop/desktop, i7, 32gb ram, ssd's), there are no OS/2 problems of any kind. The trend of use can be reversed, and made upward again...

Great post...I'm particularly interested in Winflector as I've been using Thinstuff for a while now which relies on the RDP protocol to share individual apps. On our end I use FreeRDP, and that works very well indeed.

Having said that, Thinstuff does not support Win10, and so there is a definite end-of-the-road there, and by the looks of it Winflector certainly does.

Looking at Winflector site though they talk about using "client" to connect to the hosted Apps, so what does that look like on our OS/2 platform? Is that RDP still?

Thanks,
-Dariusz

9
Setup & Installation / Re: PYTHON - v2 vs v3 and dependencies...
« on: April 27, 2025, 05:22:39 pm »
Hey Lars!

Make sure that in your \usr\bin directory, you copy python2.7.exe to python.exe (if not already done). Nothing else ever worked for me.
And yes, I also have python 3 installed as I can find python3.9.exe within that same directory. But as I said, using Python3 will only get you into trouble.

So here are the actually Python RPM packages I have installed:

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

...and that means I have the following in \usr\bin:

Code: [Select]
[G:\usr\bin]dir pyth*

The volume label in drive G is OS2.
The Volume Serial Number is 45B6:75C3.
Directory of G:\usr\bin

 7-04-23  1:50p             9    149 a---  python
 7-04-23  1:50p         1,057    124 a---  python.exe
12-27-21  9:15a            13    153 a---  python2
12-27-21  9:15a            16    156 a---  python2-config
12-27-21  9:15a            15    155 a---  python2.7
12-27-21  9:15a         1,813    124 a---  python2.7-config
12-27-21  9:15a         1,076    124 a---  python2.7.exe
 7-04-23  1:46p            13    153 a---  python3
 7-04-23  1:50p            15    155 a---  python3.9
 7-04-23  1:50p         1,057    124 a---  python3.9.exe

So the weird part is that python.exe is alreday there and it was part of the python-unversioned-command-3.9.17-1.oc00.pentium4 RPM in my case.

Here is what the various python invocationg scripts actually translate to:

Code: [Select]
[G:\usr\bin]type python
./python3
[G:\usr\bin]type python2
python2.7.exe

[G:\usr\bin]type python3
python3.9.exe

10
Setup & Installation / PYTHON - v2 vs v3 and dependencies...
« on: April 27, 2025, 04:02:26 pm »
So I noticed that libxml2 RPM package got updated to 2.12.4 whereas currently I'm at 2.9.10.

OK, cool, I figured seeing as it was in '-REL' status I'd pull the trigger and get it updated on my machine as well.

However, doing so resulted in an error (during install and not in the pre-check stage ABAICT) and produced the attached error. Basically it turns out my python2-libxml2 has a dependency on the libxml2 RPM.

Hmm...OK, so let me sort this out. Off I went looking thinking that I had already installed Python3 anyways, so why did I still have Python2 on this box, and did it still even make sense to do so.

Take a look at my list of Python stuff that's currently installed here...so yeah, it's a bit of a mix of things.

Now I recall thinking/reading in the past that our RPM/YUM solution required Python2, but checking the RPM/YUM Netlabs page (https://trac.netlabs.org/rpm) I'm not finding anything there calling this out.

So my question is: is Python2 needed for anything RPM/YUM related? I do not use Python for anything but this and maybe one or two little utilities.

It feels like I should perhaps just try to move to Python3...???

Thanks!

11
Hi Silvan!

no need the hassle. I might create a new rpm within some days

Installed the 4.7.0 release here, a few days into this and things seems to be working quite fine.

So for what it's worth, is this post here the most appropriate/quasi-official way to provide you with that feedback in order to move the RPM from '-EXP' to '-REL'??? (seeing as I haven't seen anyone else complain of negative results)

I've often wandered who/how/when this whole thing works...

12
Martin, everyone...

...I also agreed that Arca Noae should bring a developer to the scene to finally got a modern web browser on ArcaOS. Arca Noae is the only one with resources that can help with this, the rest of the community does not generate any incomes to be directly invest on the OS...Even if it is younger developer that does not knows OS/2, at least hire him permanently to learn the OS/2 API in a few months...

Umm...folks, we are a DEAD platform...I hate to say it, but that's just the pragmatic part of me screaming in my head!!! LOL

So Martin, as much as I would love to contribute ($$$) again to this effort, the reality is that you can't simply go fishing for a resource, especially someone younger that needs to do a WHOLE STACK worth of learning only to develop a skill that's basically completely unusable anywhere else.

Yup, that's that.

The problem I have always seen as the proverbial "brick wall" of our platform is the fact that we seemingly still do not hava a ready 'out of the box' DEV enviornment. This is a significant mountain to climb for anyone that even attempts to do this.

Look, I've been professionally employed writing code (albeit Oracle PL/SQL DBMS stuff, and some other stuff) but the point is, that's sort of like learning how to ride a bike, and once you figure that out it's just a matter of getting used to different gear sets, handling, etc.

I will tell you this: having tried to upgrade our DISKIO utility (and that thing is a tiny, itsy-bitsy piece of functionality) it's been nearly impossible to find all the pertinent references that allow us to account for how things have changed between the '90s where OS/2 was still a viable platform to how things are today.

Don't get me wrong, I'm not a coding Pro, but I'm no newbie when it comes to DEV environments, IDEs, libraries, etc...so why does it always feel like getting anything off the ground on our platform is like climbing Mt. Everest???  :o ::)

13
Multimedia / Re: Updated Uniaud32 build
« on: April 26, 2025, 05:00:26 pm »
Hi Paul!

...https://smedley.id.au/tmp/uniaud32-linux-6.12.21-20250415.zip fixes the out of memory errors when manipulating mixer controls.

Good results here!

CARD info
Code: [Select]
[G:\]unimix -card
Command line mixer for UNIAUD32. Version 1.1
Detected UNIAUD version 2.02.06
Detected 1 audio adapter(s)
Card info for adapter 0:
  num: 0
  id: SB
  driver: HDA-Intel
  name: HDA ATI SB
  longname: HDA ATI SB at 0xfeb00000 irq 16
  mixer: Realtek ALC892
  componenets: HDA:10ec0892,1462640a,00100302

The last release I tested was your uniaud32-linux-6.2.12-20230414.zip drop, this booted fine, sounds worked but I always had a TRAP in mplayer (different mp4 streams, etc.).

This uniaud32-linux-6.12.21-20250415.zip does NOT exhibit this, so far so good!

Thank you!

14
Applications / Re: EXIFTool
« on: April 26, 2025, 04:03:22 pm »
...WPIView 1.1.0 is not found on hobbesarchive.

Can be found on FilePile https://www.os2site.com/sw/util/installers/wpiview110.zip..

Yeah...but...the Hobbes location does show WPIView_1-2t.zip which is appears to be a test release of an upgrade to 1.1 found at the link you Pete show above.

For what it's worth, I took a look at it and while I spotted a new button (which appears to say 'Build Too'), selecting it does not seem to actually do anything other than what the 'Extract' button does.

15
OK, that's excellent...thank You Silvan!

Pages: [1] 2 3 ... 96