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 ... 89
1
Applications / Re: lSwitcher v 2.94
« on: June 16, 2024, 02:25:00 pm »
Andy,

Does anyone else have an issue when Ctrl clicking the desktop icon that barely a small highlight shows up and now list of processes to kill?

I assume you meant to say "...and NO list of processes..."?

If yes, correct, that's what I see here as well in the pop-up switching window. This does work for all the other icons of running programs I see however.

2
Applications / Re: AOS RAM Disk
« on: June 09, 2024, 03:14:59 pm »
Hello Roberto,

... But reducing the virtualaddresslimit to 1024, it already shows me 1gb of cache.
 The price is the reduction of memory...

Yup, this JFS thing is all about balancing the hardware resources in a manner most beneficial to the way YOU use YOUR machine. So there really are no generalizations, other than perhaps some starting points?

With my particular hardware combo I'm able to run this large of a JFS cache with 'VIRTUALADDRESSLIMIT=2048' setup. I found that going lower than that will start causing problems with our current applications, as others have pointed out as well.

So the 'balance' thing here is probably more heavily skewed towards 'being able to run an app' as opposed to 'having a fast FS cache'.

...I've still set up my ArcaOS NAS like this, but I don't see any performance improvements in file transfer.
 I'll have to do more tests...

I would NOT expect at all there to be file transfer performance improvements, other than I suppose the fact that the larger cache allows your target write operation to be cached.

...
[C:\]cachejfs

          SyncTime:      32 seconds
            MaxAge:     128 seconds
        BufferIdle:       8 seconds
        Cache Size: 1048576 kbytes
        Min Free buffers:    8000 (   32000 K)
        Max Free buffers:   15000 (   60000 K)
Lazy Write is enabled...

One last comment is re: SyncTime, MaxAge and BufferIdle. Be careful with these. I have my setups as large as they are because my machine is hooked up to a UPS fulltime. Therefore, the chance of power going out and the JFS cache NOT getting flushed out is very minimal. Still, a hard TRAP could still happen, so there is always some risk there.

Just for reference, here are my notes on this topic:

Code: [Select]
/LAZY:synctime,maxage,bufferidle
enables write cache with the following parameters:

- synctime : the interval at which the sync thread runs
default = 16

- maxage : is the longest time that a frequently modified file is kept in cache
default = synctime * 4

- bufferidle : is the time indicating a "recent" change. Changes newer than this
               value are not written unless the last write was older than maxage.
default = MIN(1,synctime/8)

3
Applications / Re: AOS RAM Disk
« on: June 08, 2024, 01:24:58 am »
Hello roberto!


Code: [Select]
...
IFS=C:\OS2\JFS.IFS /CACHE:1048576 /LW:32,128,8 /AUTOCHECK:*
CALL=C:\OS2\CMD.EXE /Q /C C:\OS2\CACHEJFS.EXE /LW:32,128,8 /MINBUFFER:8000 /MAXBUFFER:15000 >NUL
...
[C:\]cstats
cachesize     32768   cbufs_protected       10302
hashsize      16384   cbufs_probationary     2585
nfreecbufs    18938   cbufs_inuse               0
minfree        8000   cbufs_io                  0
maxfree       13000 **   jbufs_protected         681
numiolru          0   jbufs_probationary      255
slrun         10983   jbufs_inuse               0
slruN         21844   jbufs_io                  0
Other             7   jbufs_nohomeok            0

So here is the thing: my JFS cache is really large, 1Gig, therefore the '/CACHE:1048576' setting.

When you attempted to run as big of a cache on your system, given that JFS wasn't able to allocate that much RAM it actually defaulted to 10% of your accessible RAM (or maybe 20%??? I don't remember the default at the moment), which gave you a JFS cache of about 128M.

This is confirmed by your cstats value of cachesize=32768, where each such buffer is 4096 bytes. You can get a true JFS cache size by running the following:

Code: [Select]
[G:\os2]cachejfs

          SyncTime:      32 seconds
            MaxAge:     128 seconds
        BufferIdle:       8 seconds
        Cache Size: 1048576 kbytes
        Min Free buffers:    8000 (   32000 K)
        Max Free buffers:   24000 (   96000 K)
Lazy Write is enabled

Therefore, if you are interested in increasing your JFS cache size you may want to inch-up on the 1Gig slowly...maybe go to 256M, than 512M, etc...

4
Applications / Re: AOS RAM Disk
« on: June 07, 2024, 07:23:10 pm »
hey Dave!

Dariusz, did you ever publish your updates to diskio, also have you considered adding them to Sysbench, which basically uses diskio for disk benchmarking.

Nope...b/c I started the work on converting it to handle SSD's 4K sector sizes and ran into some problems with DosDevIOCtl32 return RC=87, which I wasn't able to resolve.

However, for what it's worth, here is the DISKIO version that I previously published in the forum here on a separate thread => https://www.os2world.com/forum/index.php/topic,2676.0.html.

5
Applications / Re: AOS RAM Disk
« on: June 07, 2024, 04:00:38 am »
Not quite RAM disk related, but for the folks who are experiencing that "...system seems to freeze for 4 - 8 seconds and then resume..." behaviour: if you are using JFS, this may be a symptom of your JFS settings causing it to run out of free buffers and needing to purge the cache(s) to free up the buffers.

This is well documented by Sjoerd Visser in his "Dynamically Tuning the JFS Cache for Your job" presentation deck from way back in 2009.

Bottom line: this can be brought on by several 'system use' activities, but it basically causes the JFS code to write out dirty buffers to disk. The key to dealing with this on my rather large JFS cache (1G) was to watch the typical system use (log cstats output) and adjust the MIN & MAX free buffer settings in pair with the overall LazyWrite setups.

This is a trial & error thing as your machine will be heavily driven by what your usage patterns are.

For what it's worth, here is what I have:

CONFIG.SYS:
IFS=G:\OS2\JFS.IFS /CACHE:1048576 /LW:32,128,8 /AUTOCHECK:*
CALL=G:\OS2\CMD.EXE /Q /C G:\OS2\CACHEJFS.EXE /LW:32,128,8 /MINBUFFER:8000 /MAXBUFFER:24000 >NUL

5 Days into using my box (last time it was up for 27 days, normal desktop stuff, nothing fancy), castat shows:

Code: [Select]
[G:\]cstats
cachesize    262144   cbufs_protected       35795
hashsize     131072   cbufs_probationary    22467
nfreecbufs   101902   cbufs_inuse               0
minfree        8000   cbufs_io                  0
maxfree       24000   jbufs_protected      101075
numiolru          0   jbufs_probationary      894
slrun        136870   jbufs_inuse               0
slruN        174762   jbufs_io                  0
Other            11   jbufs_nohomeok            0

...with the nfreecbufs never dropping so low that they show zero (0) as slruN approaches slrun value.

I started with MIN=8000 and MAX=16000, and that gave a pretty solid system, although sometimes I would get that tell-tale "hang" feeling. So I moved to MIN=4000 thinking that would free up the buffers for caching duties..welllll...no sirr....wrong move...that completely resulted in a solid and repeatable "system hang". So back to the drawing board so to speak, I set my MIN=8000 and increased MAX=24000. RESULTS => SOLID, the most solid system I have had for years.

The thing that 'ruins' my JFS cache (spoils it actually) is the nightly disk copy (rcopy) run. If it wasn't for that activity my cbufs_protected would stay very large, which means I have a good amount of content that's being successfully cached. Of course, the jbufs_protected is equally important as that allows JFS to quickly figure out where to "go" to retrieve the content as opposed to having to read the data from the disk itself. Again, which one should be the focus for you entirely depends on what disk access patterns you see.

Anyways...balance, somewhere out there are the right settings for your machine.

Last but not least, my JFS formatted RAM DISK results are (diskio):

Drive cache/bus transfer rate: 629714 k/sec
Data transfer rate on cylinder 0   : 680303 k/sec
Data transfer rate on cylinder 634 : 680021 k/sec

meanwhile the SSD results are:

Drive cache/bus transfer rate: 125467 k/sec
Data transfer rate on cylinder 0   : 286615 k/sec
Data transfer rate on cylinder 30399: 253408 k/sec

The ram disk is 2-3x faster here.

EDIT
====

One more thing to add to this, albeit this is easily identifieable and most likely NOT the situation everyone else is seeing: I tried running AHCI driver here and on my hardware that would result in what seemed like a complete HARD lock for about 4-8 secs at a time. Once that "event" passed the system was available for use once again. I tried a boat-load of different setups and configs but none of it helped. Subsequently i went away from AHCI.

6
Dave,

Yum install libtiff-legacy-tools looks like it would install tiff2pdf, version 3.9.5-2. Might have to install after upgrading
Seems that an issue should be raised at Bitwise about the missing tools.

Yup...happens to be the same conclusion I had just arrived at LOL, but our posts virtualy crossed each other!

I suspect you are right...

7
Question for the masses: I'm at libtiff-tools 4.0.9 level here, and the 4.6.x release has been sitting out there in EXP state, so I thought I'd take a stab at it with the pre-req of course being the baseline libtiff itself.

The libtiff-tools however drops just about all the "tiff2..." EXE files...so tools themselves, and I see not legacy version out there that still provides these.

Specifically I am after the tiff2pdf.exe one, as PDFmergeNX uses that...

Sooo...I went back to the previous version b/c the latest & greatest doesn't quite seem to be just that.

Is there something else out there that has this? Doing a 'yum provides */tiff2pdf.exe' just lists the previous releases and shows nothing at the 4.6.x level.

EDIT
====

Just spotted libtiff-legacy-tools, but that's at 3.9.5-2 level, and wouldn't that be an older version of libtiff-tools-4.0.9-1? (which is what I had before I executed the upgrade)

8
Applications / Re: XWP v1.0.16
« on: April 29, 2024, 02:32:53 am »
Hello Martin,

...I think that XWPProgramFile Class (or is it some other WPS Class?) has already something implemented (See picture) on the "Module" tab. But I have no idea how to have the same information for DLLs files...

Hmm...so for some reason I do not see this being populated for some EXEs, such as the NewView.exe, where at CLI there certainly is BLDLEVEL info showing.

DLL wise, turns out that not all DLLs are classified as XWPProgramFile object, which is perhaps why so it happened that the DLLs I was looking at showed no such Module tab.

So at a follow-up, two actually, I'm curious:
1) DLL object type conversion
- reading that other thread you shared, it seems like this was a manual process that needed to be done for every new DLL, is that correct?

2) re: XWP NEW Feature request: now that I understand what's already there (or should be there), I would like to just stick to the menu selection which would simply show that BLDLEVEL info in it's own pop-up

9
Applications / Re: XWP v1.0.16
« on: April 29, 2024, 12:52:50 am »
Rich,

New feature request: would you consider implementing BLDLEVEL file object pop-up functionality?

What I'm envisioning is the ability to right click on a DLL, or any object that does contain the BLDLEVEL information, and have this stuff either pop-up directly under some sort of 'Version' or 'BldLevel' menu entry, or perhaps another place such as under 'Properties'???

10
Multimedia / Re: mplayer - just stopped working...sort of...
« on: April 28, 2024, 08:01:50 pm »
Hello KO!

...
3. What's the value of '2D Acceleration' ?


"YES" on my machine


Then, your system should play a movie with 2D acceleration, that is, SNAP mode. Nevertheless, if it fails, your system or SNAP driver seem not to support 1080p with 2D acceleration. In order to verify this, how about other smaller clips than 1080p, such as 720p ?

Great pointer!!!

Sure enough, finding a few other videos I was able to play them through SNAP config, although that's not to say all 720s played, some would, some would not.

Then I remembered: the SNAP vidmem size is something I had tweaked in the past in order to free up max ram for my JFS cache (1G)...sure enough, I had it set to 18M, which for regular use was perfectly sufficient (1920x1200 x 2 heads). However, in this case, whether its the double-buffering or something else, perhaps this was causing me a problem?

I doubled up to 36M, and YUP...all of my 1080 vides play back just fine!!!

Eventually settled on 24M, which also happens to be the previous setting I had in place for a very long time...not sure why I had moved away from that, was probably experimenting with a larger JFS cache and just never remembered to bump that back up.

Anyways...sir: thank you for that spot-on remark!!!

11
Applications / Re: LarsenCommander - new test version
« on: April 28, 2024, 06:05:07 pm »
Hi Andi,
...
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
...

Repeat of the same performance tests for the newest version:

1) from SAMBA share to ramdisk
OLD: Peak=56,220K, Avg=46,516K
NEW: Peak=51,367K, Avg=45,832K

2) from ramdisk to SSD drive (Samsung 860 Evo, SATA)
OLD: Peak=310,118K, Avg=220,910K
NEW: Peak=503,901K, Avg=311,825K

...which naturally made my eyeballs nearly pop out b/c let's be honest, my SSD isn't that fast!!!

So a re-do produced the following NEW:
NEW: Peak=430,674K, Avg=183,007K

...which while still pretty high for a Peak, I suspect this has everything to do with my crazy ass JFS cache, which is 1G in size.

Couple more tests later though the higher Peak appears to be sustained, so perhaps there is a little bit more improvement here Andi!!!?

Thank you again!

12
Multimedia / Re: mplayer - just stopped working...sort of...
« on: April 19, 2024, 02:40:44 am »

3. What's the value of '2D Acceleration' ?


"YES" on my machine

13
Networking / Re: Netdrive and ArcaOS
« on: April 08, 2024, 03:57:18 am »
Neil, everyone...

You can just run the NetDrive installer on ArcaOS, and it will replace the Arca Noae version with the full version. It even keeps your NetDrive settings the same.

Slightly different outcome here, although this is OS/2 SMP 4.52, so not an out-of-the-box AN install.

Anyways...I have been using NetDrive for some years now, and have installed in the same configuration the AN ArcapMapper stuff, primarily for testing purposes.

Both work, one does not replace the other (as far as binaries go), from functionality perspective that is somewhat the case (with the already mentioned shortcomings of the AN solution), but the programs are different.

So Glenn, you should be able to install NetDrive and have it functioning on it's own...but as mentioned, carefully navigate as both of these solutions attempt to deliver the same functionality.

14
Multimedia / Re: mplayer - just stopped working...sort of...
« on: April 08, 2024, 12:58:32 am »
Hello KO!

...Try -msglevel vo=9 for detailed message, please.

OK, done...here are the snippets for both SNAP & VMAN (where VMAN did actually work and SNAP did not):

1) SNAP
Code: [Select]
MPlayer 1.5-9.1.0 (C) 2000-2022 MPlayer Team

Playing G:\tmp\AUTO\20210130_210808.mp4.
libavformat version 59.17.102 (internal)
libavformat file format detected.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x2f4cf0]Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol
[lavf] stream 0: video (h264), -vid 0
[lavf] stream 1: audio (aac), -aid 0, -alang eng
VIDEO:  [H264]  1920x1080  24bpp  30.000 fps  16946.1 kbps (2068.6 kbyte/s)
KVA: Selected video mode = SNAP
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 59.21.100 (internal)
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
Clip info:
 major_brand: mp42
 minor_version: 0
 compatible_brands: isommp42
 creation_time: 2021-01-31T02:08:22.000000Z
 location: +42.2680-083.0048/
 location-eng: +42.2680-083.0048/
 com.android.version: 10
 com.android.capture.fps: 30.000000
Load subtitles in G:\tmp\AUTO\
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 48000 Hz, 2 ch, floatle, 256.0 kbit/8.33% (ratio: 32006->384000)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
KAI: Open failed!!!
AO: [null] 48000Hz 2ch floatle (4 bytes per sample)
Starting playback...
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [kva] 1920x1080 => 1920x1080 Planar YV12
KVA: Using 0x32315659 (Planar YV12) image format, vo_config_count = 0
KVA: Selected FOURCC = YV12
KVA: Setup failed!!!
FATAL: Cannot initialize video driver.

2) VMAN
Code: [Select]
MPlayer 1.5-9.1.0 (C) 2000-2022 MPlayer Team

Playing G:\tmp\AUTO\20210130_210808.mp4.
libavformat version 59.17.102 (internal)
libavformat file format detected.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x2f4cf0]Protocol name not provided, cannot determine if input is local or a network protocol, buffers and access patterns cannot be configured optimally without knowing the protocol
[lavf] stream 0: video (h264), -vid 0
[lavf] stream 1: audio (aac), -aid 0, -alang eng
VIDEO:  [H264]  1920x1080  24bpp  30.000 fps  16946.1 kbps (2068.6 kbyte/s)
KVA: Selected video mode = VMAN
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 59.21.100 (internal)
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
Clip info:
 major_brand: mp42
 minor_version: 0
 compatible_brands: isommp42
 creation_time: 2021-01-31T02:08:22.000000Z
 location: +42.2680-083.0048/
 location-eng: +42.2680-083.0048/
 com.android.version: 10
 com.android.capture.fps: 30.000000
Load subtitles in G:\tmp\AUTO\
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 48000 Hz, 2 ch, floatle, 256.0 kbit/8.33% (ratio: 32006->384000)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
KAI: Open failed!!!
AO: [null] 48000Hz 2ch floatle (4 bytes per sample)
Starting playback...
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [kva] 1920x1080 => 1920x1080 Planar YV12
KVA: Using 0x32315659 (Planar YV12) image format, vo_config_count = 0
[swscaler @ 0x79d2b0]bicubic scaler, from yuv420p to bgra using MMXEXT
[swscaler @ 0x79d2b0]using unscaled yuv420p -> bgra special converter
KVA: Selected FOURCC = BGR4
Fontconfig error: Cannot load default config file
Selected font is fixed-width.
Selected font is fixed-width.
A:   nan V:   0.0 A-V:    nan ct:    nan   0/  0 ??% ??% ??,?% 0 0

I truncated the remaining LOG entries because they are just repeating as the file continues to be read.

The only strange thing (perhaps?) which I noticed is that VMAN also shows "KAI: Open failed!!!" log entry, however it does produce actual video playback.

...How about trying to launch mplayer with default options, that is, just [mplayer mp4-file] ? In this case, you should rename your ini file.

Finally, this is true for VLC ?

In order to rule out any of my config options I ran from CLI having previously renamed smplyer's CONFIG file so that it wouldn't be pulled in.

Yes, this is consistent in VLC as well (3.0.18 here), which I have set to VMAN previously (at some point in time).

Thanks!

15
Multimedia / Re: mplayer - just stopped working...sort of...
« on: March 30, 2024, 07:49:35 pm »
OK, so DIVE made no difference, but as I looked into this more I noted that my mplayer version was a little old.

So off I went deploying the most recent release, alas, same result:

Quote
[G:\test\mplayer]mplayer.exe -xy 1 G:\tmp\AUTO\20210128_201140.mp4
MPlayer 1.5-9.1.0 (C) 2000-2022 MPlayer Team
Setting process priority: realtime

Playing G:\tmp\AUTO\20210128_201140.mp4.
Cache fill:  0.00% (0 bytes)

libavformat version 59.17.102 (internal)
libavformat file format detected.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x2f4cf0]Protocol name not provided, cannot determine
 if input is local or a network protocol, buffers and access patterns cannot be
configured optimally without knowing the protocol
[lavf] stream 0: video (h264), -vid 0
VIDEO:  [H264]  1920x1080  24bpp  30.000 fps  34089.8 kbps (4161.4 kbyte/s)
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 59.21.100 (internal)
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
Clip info:
 major_brand: mp42
 minor_version: 0
 compatible_brands: isommp42
 creation_time: 2021-01-29T01:14:08.000000Z
 location: +42.2680-083.0048/
 location-eng: +42.2680-083.0048/
 com.android.version: 10
 com.android.capture.fps: 30.000000
Load subtitles in G:\tmp\AUTO\
Audio: no sound
Starting playback...
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [kva] 1920x1080 => 1920x1080 Planar YV12
KVA: Setup failed!!!
FATAL: Cannot initialize video driver.

..

Pages: [1] 2 3 ... 89