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 - Andi B.

Pages: [1] 2 3 ... 60
1
General Discussion / Re: Brainstorm: What is Next with OS/2 ?
« on: March 20, 2025, 09:24:28 am »
My top priorities would be -
1) stable operation on Ryzen7 either with integrated graphic or external (at least AMD B550) without trap when Virtualaddresslimit is above 1536 and 3140x2160 resolution. If you see the ticket you know what I mean in detail.
2) solving PM (GPI, gradd, Panorama, ??) problems which leads to no window update anymore after some time or when memory gets low (usually seen with VBOX running, but pretty sure not a VBOX problem only, but mem management and graphic)

Regarding browser I fear we never ever will have a browser with the features I need (I'm used to) again. So no priority for me. Dooble works to some extend and I appreciate the efforts made here. But it never will get the features I'm used to from SM or FF.


2
Applications / Re: OO 4.1.11 trouble
« on: March 17, 2025, 03:24:43 pm »
Quote
LIBPATH=.;G:\usr\local\lib;G:\usr\lib;G:\usr\bin;
Usually I suggest putting the '.;' at the end of this line. Or at least after the x:\usr\xxx entries. This would avoid loading old/wrong/special/... dlls from outside the somehow 'maintained' versions (by ANPM/yum/rpm) at the default locations. And will reduce the risk of using 'wrong' dlls a lot I think.

Imaging you've an old program which an old dll in it's own path and you load it at system start. From startup folder or tcpexit.cmd or startup.cmd or.... Then this program would load the 'wrong' dll into memory. All programs started afterwards have to use this 'wrong' dll cause it's already loaded in memory. Until the program (all programs which use the 'wrong' dll) are closed or you cheat the system with libpathstrict and beginlibpath.

Maybe you wanna test this.

Edit - there was a time when I have to yum downgrade icuxxx (?) to let AOO run. But I think this was well before 4.1.11.
Edit2 - you've assured that you don't run the AOO quickstart from an older version?

3
Article Discussions / Re: RPM Packages - 2025 (Pentium 4)
« on: March 11, 2025, 05:53:29 pm »
I don't think DataSeeker needs more than 686. It's compiled with VAC3.65. But I don't remember if I set any special option. OTOH there was no single report of anyone that it does not work on his system. So maybe even 386 is enough.

4
Virtualization / Re: print under virtual box
« on: March 08, 2025, 11:04:14 am »
What the heck is "Datenstrommodus"? Is it a translation for raw mode?

I'm a native German speaker but I don't understand how someone can make such a weird translation.

5
In UEFI mode, I also have to run at 3840 x 2160 x 16. In Legacy mode 3840 x 2160 x 32 works OK. VESA BIOS in 4K mode is flakey on several of my computers. This is one area where a video driver would be a plus.
How do you setup 16 bit? I've only 16M colors and no other selection available here with Panorama (bare metal).

6
... running it at 3840x2160x16...
Do you really run it with 16 bit (65536 colors) or do you mean 32 bit (16M colors)?

7
Applications / Re: LarsenCommander - new test version
« on: February 26, 2025, 01:54:30 pm »
Ouch, I don't have access to the source code at netlabs :-(.
It this one? https://trac.netlabs.org/openjfs/browser#branches
I can watch it without being logged on. Maybe it was the upppercase on the URL.

Regards

I was at the main trac page and even logged in and did not found the usual 'source code' button. Just found out netlabs has 2 jfs projects. One jfs another openjfs. I was here - https://trac.netlabs.org/jfs while correct link should be - https://trac.netlabs.org/openjfs/.

Last check in seems to were 21 years ago. Not sure how much of this old code is still in use. Thanks anyway.

8
Applications / Re: LarsenCommander - new test version
« on: February 26, 2025, 12:21:27 pm »
Thank you very much. Enough stuff to test and try out. Have to bookmark this. OTOH I thought this lcmd version would be really the last one.....

Ouch, I don't have access to the source code at netlabs :-(.


9
Applications / Re: LarsenCommander - new test version
« on: February 26, 2025, 08:37:02 am »
Quote
These info levels are undocumented in the CPS.
Wow. Some of your explanations sounds familiar. After I invested countless hours on reading original Lcmd code, edm2 and all the help files of os2tk45. But where did you get the undocumented stuff from? Answers from some experts in some goups which you noted somewhere? Or is there a place where someone document such undocumented stuff? Stevens site?

Btw: these idiots which wrote the control programming appendum for DosOpenL f.i. should be sent to jail. Again I stumbled over this wrong description and examples (variables versus pointers). It's a mess when the official documentation is so wrong in so many places :-(.

Btw2: It's a somehow educated guess that the file system is faulty here. With different versions of EA handling in Lcmd I very often got 'Trap 000e in JFS'. The last implementation which I think perfectly correct, let the IFS silently stop working only sometimes. Unfortunately I need to copy a few hundred thousand files with a lot of GBs. So still have no simple scenario to reproduce.

Btw3: For my problem I think it's not the DosRead buffer size as this is already limited (<1 - ~16MB) here. AFAIK the problem Silvan reported happens with about 400MB and above. OTOH David explained in the ticket it's not the buffer size which triggers this one known problem, but 2 DosOpenL calls where the first one does nothing. Do you think Davids explanation in the ticket is wrong? Or is he talking about another problem? Is it worth to test with read buffers max. 1MB f.i.?

10
Applications / Re: LarsenCommander - new test version
« on: February 25, 2025, 11:43:27 am »
Interesting. But if I understand it correctly it should be fixed since a while. I can reproduce problems here even with ArcaOS5.1EN.

OTOH LarsenCommander doing the copy stuff a bit unusual so this may be another JFS problem others rarely encounter. Lcmd reads the file (in chunks if bigger than internal dynamic buffer) and writes it to target. So far so good. Then it reads in all EAs from source file and then writes the EAs to the target. This EA handling is strange when you see it the first time. Reading every EA name and data with dynamic size.... And I think the problem occurs when writting the EAs.

Unfortunately I didn't find a way on OS/2 to read and write all EAs of a file at once. These can be <64k anyway so no would be no problem on todays systems. Reading all these EA entries in a loop by name and values is a mess.

11
Applications / Re: LarsenCommander - new test version
« on: February 23, 2025, 04:22:34 pm »
I've just released v1.09.00. See https://sourceforge.net/projects/lcmd-git/files/

For me this is a major improvement as now the EA logic finally works without memory leaks. At least for my (extensive) testing. Also the focus switching problem improved a lot. Maybe not fully solved but at least the test cases I had. The copy buffer size limit setting now will be honored again. Mind now in MBytes not KBytes. Not sure if translations in all languages are correct.

Unfortunately there is still one problem I couldn't solve. But during extensive testing and debugging I'm pretty sure this is a file system driver (JFS) problem. Copying huge amount of files can lead to file system hangs. Sometimes after 80'000 files, sometimes after 800'000 files. First I thought it's a problem with log file overflow (beyond 2GB). But now as I changed this to LFS support too and numerous test with and without logging file enabled I'm pretty sure it's something very low level in JFS or NVME or ? driver. Given that no one else mentioned this problem until now and given 1.09 is able to copy at least 10 times more files without problems than any version before I think it's time to make it public. Enjoy v1.09.00.

Code: [Select]
Change History:
---------------
20250222 v1.9.0
- Improved Extended Attribute handling again. Now it should handle all sizes of EAs and checks and limits to <64k
- EA handling now really fixes memory leaks
- Reenabled max copy buffer size setting in but now use MB instead of KB because it is in HigherMem arena since
1.8.0 (?) anyway
- Improved focus switching logic. Don not set focus on unrelated windows after copy/del operations.
- Skip sending lot of GUI (PM) messages for updating progress dialog with fast disks while copying and deleting files.
This is to work around PM memory leaks (crashes) when hammered with very much messages in a short period of time.
With fast disks copying or deleting small files takes few ms or even less. The previous logic to update the
progress bar after each file (and during a file when it is bigger) is changed to not send more than about one
message in 125ms. PM seems to be not safely ignore to much unhandled messages and starts to eat up shared memory.
Eventually this crashes the whole system when the process is not closed before. F.i. this skipps more than 69000
messages when copying the ApacheOpenOffice source code tree. The same skipping logic improves speed when deleting lot
of files. F.e. 33s instead 53s for AOO source code tree (about 70k files). More than 76000 messages where skipped with
that new delete logic.
- Change LOG file handling to LargeFileSupport to allow more than 2GB log files. This is needed cause with very heavy
logging previous versions hang the whole file system starting with the log file directory at 2GB log file size
(> 100k files copied with DEBUG)

12
Many thanks for your latest version. Now I can enter email addresses (@) and the other stuff like {[]}\|²³µ€~ which was not possible before.

13
Events / Re: ArcaOS 5.1.1 is out.
« on: February 22, 2025, 09:42:53 am »
How did you change the colors on the clock portion of Xcenter?
Usually drag and drop colors from the "Farbpalette" (color palette?) is the OS/2 way to do such things. Dropping without any key is usually background I think and with <SHFT> is text color. I've ever try it out cause I don't remember. With the xwidgets this works.

14
Quote
Please check this: http://os2.snc.ru/pub/freerdp/test/freerdp-wpi-20250217.zip
Quick test - I works :-)

Not much time for extensive test, but €@²³µ work now. Thanks.

15
I've now checked with xkbev which key codes is received. On the local keyboard AltGr produces keycode 108. When connected via ofreerdp the same key on the remote keyboard produces 2 keycodes - 37 and 64. Which probably is Ctrl and Alt. And this does not work. There are more differences but this one is the biggest problem.

Connecting the Linux box from Win10 instead OS/2 the Win AltGr produces keypress 37, keyrelease 37, keypress 113 and keyrelease 113.

So either our ofreerdp should send
1) keypress 108 when pressing AltGr and keyrelease 108 when releasing AltGr (in the meantime the other keys are should sent as usual) to mimik local behaviour or
2) keypress 37, keyrelase 37, keypress 113, keyrelease 113 to mimik Win behaviour. But Win make autorepeat of this sequence as long as AltGr is pressed. So option 1) like local keyboard maybe better

Have to say I'm no expert on this. But working combinations are -
- Win to Linux
- OS/2 to Win
non AltGr working is with -
- OS/2 to Linux

Also /kbd: options seems to do nothing (not implemented?) on our OS/2 client (ofreerdp.exe) as it always shows the usage messages. But this can be overcome with xrdp.ini and xrdp_keyboard.ini entries (force DE with override instead default to EN).

Pages: [1] 2 3 ... 60