Recent Posts

Pages: [1] 2 3 ... 10
1
Hardware / Re: Dell KB900 keyboard - workable?
« Last post by Dave Yeo on Today at 03:10:08 am »
The wireless part should work fine. I've had a few wireless keyboards (no Dell) including where the adapter that plugs into the USB port supports both keyboard and mouse, they've all worked as basic keyboards and/or mouse.
2
Hardware / Dell KB900 keyboard - workable?
« Last post by Dariusz Piatkowski on Today at 02:51:49 am »
Hi Everyone,

Dell sent me an email with a discount code...and well, all my keyboards are still wired, so this one seems like a real nice upgrade.

It is a full keyboard and the comms are done through a Wireless RF2.4GHz & Bluetooth 5.1 setups. The RF link is accomplished through 'Secure Link USB Type-A Receive', which is a little plug that connects to your USB port.

My hope is that this literally just becomes a standard USB keyboard...but...that may be wishful thinking only...LOL, so I'm curious of anyone has tried either this specific keyboard, or keyboards like this with a similar connectivity setup?

Here is the link to the Product Support Page => https://www.dell.com/support/kbdoc/en-ca/000208146/dell-premier-collaboration-keyboard-kb900-usage-and-troubleshooting-guide

Thanks!

BTW: This keyboard will support pairing up with 2 Bluetooth devices as well, which means this is also a nice way to get comfy typing away in front of a larger tablet, or even a laptop.
3
Left/Right Alt+Shift worked well enough for me with PM sessions
[...]
Does anyone know what the system-provided mechanism for switching keyboard layers in VIO sessions is?
OK, self-reply after comparing a Russian system to a "russified" one and fiddling a bit: the switching mechanism is the same hotkey, by default Left Alt + Left Shift to switch from Latin to Russian, and Right Alt + Right Shift to switch from Russian to Latin. Apparently the problem is, it works in VIO sessions only if 866 is the primary system codepage. OTOH it works in PM sessions regardless of CP866 being primary or secondary :(
4
Good catch Martin, that was going to be my suggestion: look at the xxx-legacy stuff.

All in all I find Lucide to be pretty spot on with the exception of a couple of things:

1) PSCRIPT print jobs occasinoally trap on my Brother printer, this I can deal with: GSView will handle the print just fine

BUT

2) Lucide is extremely slow over the LAN and pulling PDFs from any Samba shares out there...watchin the tcp/ip traffic literally looks like just about all the data that's getting pulled down also seems to go back up to the source...weird...very weird...and only the PDFs do this, no issue with JPEGs, videos, etc!

Anyways, both are another issue...so separate topic, sorry to pollute this discussion!
5
Programming / Re: Qt6 Development
« Last post by Paul Smedley on Today at 01:10:55 am »
Yeah there is a reason dmitry make single process mode the default ;) I assume my current code you mean 6.3.2?

I may have found the problem causing the trap - the changes in https://github.com/psmedley/qt6-webengine-os2/commit/feb87f70dac13bb5b805fbd271e1ac98568ec062#diff-6d3616171ce7881cc8d3a757c2f9b476d645e4c61df77cdf47a5bf7a423bf56c - specifically the implementation of DecommitAndZeroSystemPagesInternal() is clearly wrong. I should have actually read the original code and the fix (I think) is pretty obvious and much simpler using   PA_CHECK(MyDosSetMem(reinterpret_cast<void*>(address), length, PAG_DECOMMIT));

Linking a new DLL now.
6
Programming / Re: Qt6 Development
« Last post by Andy Willis on Today at 12:53:30 am »
OK, we now have DLLs but it's not working yet:
Code: [Select]
[109:1:0322/222035.678000:ERROR:shared_buffer_dispatcher.cc(298)] Failed to map shared memory region.
[109:8:0322/222037.341000:ERROR:shared_buffer_dispatcher.cc(298)] Failed to map shared memory region.
[109:1:0322/222037.875000:ERROR:system_network_context_manager.cpp(274)] Cannot use V8 Proxy resolver in single process mode.
[109:1:0322/222037.892000:ERROR:system_network_context_manager.cpp(274)] Cannot use V8 Proxy resolver in single process mode.

I get the second pair with the current code.  I find that if I disable single process mode that I then have a better chance of loading pages but the system _will_ lock up much faster.

I'm not too worried about the second pair of messages, but the former sounds more serious. I'll have to go look at the code at https://github.com/psmedley/qt6-webengine-os2/blob/6.4.x/src/3rdparty/chromium/mojo/core/shared_buffer_dispatcher.cc#L298

Edit: Seems like due to my copy of posix code in https://github.com/psmedley/qt6-webengine-os2/commit/fe6e0638c422e146cb2379bf6a275d668b144edd#diff-0b0cccfdd90d1b8b3e0eced8a42e148326a514e6b73c3eea1435b488abe39e9b
7
Hi again, and thank you.

Basic system configuration I had covered, but I had forgotten about KLayer/2 -- it works great for text mode sessions too!

Now, for completeness sake...

Nice as KLayer/2 is, I had forgotten about it because I did not really need it -- Left/Right Alt+Shift worked well enough for me with PM sessions, which is all I needed (some 10 years ago). Does anyone know what the system-provided mechanism for switching keyboard layers in VIO sessions is?
8
Applications / Re: pdf plugin for Lucide missing after Poppler upgrade
« Last post by mauro on March 22, 2023, 08:53:26 pm »
in fact, that made it WORK !
next by the package name Poppler-legacy-70 there was also specified 0.59.0

Thank you.   :D
9
Applications / Re: pdf plugin for Lucide missing after Poppler upgrade
« Last post by Martin Iturbide on March 22, 2023, 08:33:37 pm »
Hi Again

By any chance do you have the "poppler-legacy-70" package installed?
Seems that  lupplr.DLL makes reference to that old poppler, that I guess was renamed as "legacy" on the rpm. With that you don't need to backlevel the main poppler package.

Regards
10
Hardware / Re: USX keyboard layout
« Last post by Alfredo Fernández Díaz on March 22, 2023, 08:31:58 pm »
Hi, in case it's not too late to join the party...

What confused me is that the key in the upper left corner of the keyboard did nothing at a prompt, but it works in word processing programs. There are two missing characters (left and right single quotes) and a few ways of typing characters don't work, but the characters can be typed by other means. So there you have it, the USX keyboard.

The reason why the USX keyboard layout you tried works differently at a prompt and word processing programs (which I assume are PM applications) is because text sessions and PM use different implementations of any given keyboard layout, and it turns out both versions of the MCP2 "USX" differ from the one in the image in different ways:
-The MCP2 / ArcaOS 5.0.7 USX layout has combining- and non-combining versions of the acute accent and dieresis reversed wrt what you can find in the image (key to the left of Enter, with 4 symbols on it).
-Additionally, characters (dead keys) do not work in the VIO implementation, though there is no technical reason for that.

-As an extra, the MCP2 USX yields ƒ for Alt+Gr and ª for AltGr+K both in PM and VIO implementations.

As for the 'missing' left and right single quotes, these characters are present in some OS/2 codepages (f.e Win1252/1004, which Windows defaults to), while not in others (f.e. 850, which OS/2 typically defaults to). So if you try and type them in an OS/2 program you get them if typing while using CP1004, but you get nothing if running under CP850. PM vs VIO is not relevant regarding this, as codepages are the same.

[...] (usx) which is not supported under OS/2. Only US International (ux) can be configured.
This is not completely accurate. You can't configure USX as the system keyboard layout from the Keyboard object like you can do with UX, because it is not listed there, but as Daniel mentioned before, you can do it from a command prompt or f.e. a program object that runs "keyb usx", with the limitations I listed above.

I don't know if ArcaOS ships with support drivers that can handle newer keyboard layouts?
Newer keyboard layouts can be added to OS/2 and thus to ArcaOS, although this is not trivial (but not related to 'drivers' either). Sufficient interest might spark the inclusion of tools to handle such new layouts, though.

There are also hints of USY and USZ keyboards in the files that don't seem to actually exist as if someone stopped work suddenly. Or I could be totally wrong...
You are about "USY" and "USZ" keyboards: there is no such thing. This is the full list of keyboard layouts defined in the MCP2 KEYBOARD.DCP file, with some additional data:

Name/def|available CPs (and layers) by keyboard type; 1 = 100+ keys, 0 = 80+
----------------------------------------------------------------------------
AR 238   1: 437, 850, 864(2); 0: 437, 850, 864(2)
   470   1: 437, 850, 864(2)
BA 234   1: 850, 852
BE 120   1: 437, 850, 859, 1004; 0: 437, 850
BG 442   1: 850, 855(2), 915(2)
BR 274   1: 437, 850, 1004
   275 * 1: 437, 850, 1004
BY 463   1: 850, 866(2), 1125(2), 1131(2)
CA 445   1: 437, 850, 1004
CF 058   1: 850, 863; 0: 850, 863
CZ 243   1: 850, 852
DE 453   1: 437, 850, 1004
DK 159   1: 850, 1004; 0: 850
EE 454   1: 850, 922
FR 120   1: 437, 850, 1004
   189 * 1: 437, 850, 859, 1004; 0: 437, 850
GK 220   1: 437, 813(2), 850, 869(2)
   319 * 1: 437, 813(2), 850, 869(2)
GR 129   1: 437, 850, 1004; 0: 437, 850
HE 212   1: 437, 850, 862(2); 0: 437, 850, 862(2)
HR 234   1: 850, 852
HU 208   1: 850, 852
IS 197 * 1: 850, 861, 1004; 0: 850, 861
   458   1: 850, 1004
IT 141 * 1: 437, 850, 1004; 0: 437, 850
   142   1: 437, 850, 1004
LA 171   1: 437, 850, 1004; 0: 437, 850
LT 456   1: 850, 921(2)
LV 455   1: 850, 921(2)
MK 449   1: 850, 855(2), 915(2)
NL 143   1: 437, 850, 1004; 0: 437, 850
NO 155   1: 850, 865, 1004; 0: 850, 865
PL 214 * 1: 850, 852
   457   1: 850, 852
PO 163   1: 850, 860, 1004; 0: 850, 860
RO 446   1: 850, 852
RU 441   1: 850, 866(2), 1125(2), 1131(2)
   443 * 1: 850, 866(2), 1125(2), 1131(2)
SF 150F  1: 437, 850, 1004; 0: 437, 850
SG 150G  1: 437, 850, 1004; 0: 437, 850
SK 245   1: 850, 852
SL 234   1: 850, 852
SP 172   1: 437, 850, 1004; 0: 437, 850
SQ 452   1: 437, 850
SR 450   1: 850, 855(2), 915(2)
SU 153   1: 437, 850, 859, 1004; 0: 437, 850
SV 153   1: 437, 850, 859, 1004; 0: 437, 850
TH 191   1: 850, 874(2); 0: 850, 874
TR 179 * 1: 850, 857
   440   1: 850, 857
UA 465   1: 850, 866(2), 1125(2)
UK 166 * 1: 437, 850, 1004; 0: 437, 850
   168   1: 437, 850
US 103 * 1: 437, 850, 852, 857, 862, 864, 866, 1004, 1125, 1131; 0: 437, 850
   DV    1: 437, 850, 1004
   DVL   1: 437, 850, 1004
   DVR   1: 437, 850, 1004
   X     1: 437, 850, 859, 1004
UX 103   1: 437, 850, 859, 1004
Pages: [1] 2 3 ... 10