OS/2, eCS & ArcaOS - Technical > Applications
LarsenCommander - new test version
Andi B.:
--- Quote from: Alfredo Fernández Díaz on December 05, 2023, 03:32:36 pm ---I'm glad to to see LC actively developed once again. Thank you, Andi - will be giving it a spin : )
Quick question - is NLS functional?
--- End quote ---
It should be all included in the package. I remember I've worked on adding all necessary components for NLS to the distribution script long time ago. But I didn't test it. So feedback is appreciated.
Remember at https://sourceforge.net/p/lcmd-git/tickets/ there's a ticket system. Although I try to read all infos here, chances that something get remembered in future is much higher when there's a ticket ;-). No clue if you need an account for that. For me sourceforge works pretty good with our ancient SM (and so FF I think). In contrary to other sites username/password authentication still works.
Alfredo Fernández Díaz:
Hi again, Andi, thank you...
--- Quote from: Andi B. on December 08, 2023, 10:58:16 am ---It should be all included in the package.
--- End quote ---
I asked whether it is functional because I saw a bunch of old RC translated files under the 'locale' subdir with no obvious way to switch languages from within the application (and still can't find it).
--- Quote ---I remember I've worked on adding all necessary components for NLS to the distribution script long time ago. But I didn't test it. So feedback is appreciated.
--- End quote ---
OK, fiddling about a bit, under locale there is an old email called 'reply.txt' that you can get rid of. Its slightly more updated cousin 'readme_translation.txt' (which you could refactor) reads "start Larsen Commander version 1.5.1 or 1.5.2 with this command: LCMD.EXE -rcFileLocale lcmd_it.rc" . I cloned the English file onto a Spanish one in the LC folder and changed a few strings -- LC picks it up with the proper parameters in place in the program object. Functional, but a bit cumbersome to keep switching languages while translation is in progress.
--- Quote ---Remember at https://sourceforge.net/p/lcmd-git/tickets/ there's a ticket system. Although I try to read all infos here, chances that something get remembered in future is much higher when there's a ticket ;-). No clue if you need an account for that. For me sourceforge works pretty good with our ancient SM (and so FF I think). In contrary to other sites username/password authentication still works.
--- End quote ---
OK, but let me see first if I can figure out the locale format ("text" and "hint" are obvious, but what are "alt1", 2, and 3?), how everything is put together (menus seem to be scattered), and whether the autogenerated mnemonics and such do not make translation much of a PITA.
Andi B.:
--- Quote from: Rich Walsh on June 10, 2023, 05:45:41 am ---The solution to this particular problem is to get rid of the DLL -- there's no reaon for it to exist. The original author claimed that VACPP 4.0 couldn't handle a 16-bit call so he created a separately-compiled file. But rather than simply linking it into the exe with all the other .obj files, he created a dll. Why?
...
--- End quote ---
It seems it was that easy - add ' source "gl16os2.obj"' to lcmd.icc and don't delete gl16os2.obj during the build. As far as I can see the only 16 bit function which is used by lcmd is Dos16MemAvail. But no clue when it is called. Have to test a while to be sure there's no sideeffect.
Andi B.:
I've just uploaded v1.08.02 at https://sourceforge.net/projects/lcmd-git/files/
From the Readme -
--- Code: ---Change History:
---------------
20240416 v1.8.2
- Improve EA handling routines to reduce memory leaks and silent crashes
- Fix TRAP 000e in JFS while copying >69000 files. Hint, please use latest ArcaOS (kernel, JFS, ACPI 3.23.17, ...)
- Removed gl16os2.dll dependency (link .obj into .exe)
- Handel out of memory conditions more gracefully
- Added abtrace for logging via pmprintf.dll (if available on target system)
- Improved build cmd files to break on error (ERRORLEVEL handling)
- Tuneed lxlite options to not remove bldlevel info
- Change to David G. icon files (no clue where they are used)
- Again tuning of dynamic copy buffer size adoption (even more speed on my system :-) )
- Change icons to the ones supplied by David G. Thanks for that although it's not clear to me where they are used.
(- Disable integrated exception handlers in favor of exceptq) reverted back
- Disabled ExceptQ handler as I can't get it to work in conjunction with lcmds own handlers
--- End code ---
Bug reports please here - https://sourceforge.net/p/lcmd-git/tickets/
Of course I'll keep reading here as well from time to time. Have fun.
Btw. I've a really hard time to track down and reduce this terrible JFS traps when copying a lot of files. It seems to me that JFS still does not touch some memory pages when feed with >4k buffers some times which I guess leads to these 000e traps. Combined with the memory leaks which LCMD suffered when lot of files where copied I had uncountable crashes with long chkdsks afterwards. Now the I reduced memory need for extended attribute handling I can't see these memory leaks anymore with above512. But on some scenarios LCMD still seems to eat up some system resources which report out of memory. Closing LCMD will recover from such situations now.
If you encounter hangs of LCMD you may look at the lcmd.log file in the directory of lcmd.exe. F.i. tail -n 50 lcmd.log will show you the last messages which usually shows some exception infos. For this you've to enable 'Debug' or 'Test' in Help - Debug - Options. Be aware running LCMD with 'Debug' for a long time or while copying huge amount of files let lcmd.log become very big in minutes.
Btw. if you've pmprintf.dll on your system PmPrintf.exe will show you these messages from LCMD with 'Debug' or 'Test' enabled too.
Andy Willis:
I have just downloaded it so I haven't had a chance to use it to say anything about it other than to thank you for your work on it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version