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 ... 88
Setup & Installation / Re: CUPS tripped up SeaMonkey and Firefox
« on: February 10, 2024, 02:55:12 pm »
...Press CTRL-P and in the printing dialog box, change your printer to no printer or IBMNULL, close the browser and retry. If it works, repeat with SeaMonkey.
If it doesn't work, report how far along you got, we may have to edit your prefs.js file.
Of course the simplest is if you have a backup from before you played with printing, if so if so, let me know and I'll explain how to replace prefs.js

Dave's right on the money here if you can start the application in safe mode.

I believe the actual config preference that points to the ACTIVE printer (basically the last selected one) is "print_printer", so if the applications are unusable it may be necessary to look for that in prefs.js and adjust it there accordingly.

In my case, here is what that looks like in prefs.js:

Code: [Select]
user_pref("print_printer", "PSPRINT.Brother HL-5470DW");

You will see other printers listed in your prefs.js, you could simply pick a value that represents such a valid printer and put that into the "print_printer".

For example, the above printer is actually defined as:

Code: [Select]
user_pref("print.printer_PSPRINT.Brother HL-5470DW.printer_description", "Brother HL-5470DW BR-Script3 OS (PSPRINT)");

If that does not work, it may be possible to just set that to a NULL value, perhaps just "", but I haven't tried that.

Setup & Installation / Re: CUPS tripped up SeaMonkey and Firefox
« on: February 09, 2024, 11:38:03 pm »
...Pete, after reboot with the CUPS daemon removed from the Startup folder, trying to start SeaMonkey still gives the same error.

...Yes, the failures are indeed registered in popuplog.os2; here are the results of the latest attempts to start SeaMonkey and Firefox:


02-09-2024  22:43:10  SYS3175  PID 0092  TID 0001  Slot 0086
P1=00000001  P2=00000001  P3=XXXXXXXX  P4=XXXXXXXX 
EAX=00000000  EBX=1731887c  ECX=5ad1e9f0  EDX=00000000
ESI=173187e4  EDI=00000000 
DS=0053  DSACC=d0f3  DSLIM=5fffffff 
ES=0053  ESACC=d0f3  ESLIM=5fffffff 
FS=150b  FSACC=00f3  FSLIM=00000030
GS=0000  GSACC=****  GSLIM=********
CS:EIP=005b:5e117d4b  CSACC=d0df  CSLIM=5fffffff
SS:ESP=0053:0013ff64  SSACC=d0f3  SSLIM=5fffffff
EBP=0013ff70  FLG=00010293

PSPRINT.DRV 0002:000107c7


Aha...I think I know the root cause here, or at least a worthy attempt to fix this.

I have encountered this before while attempting to remove a FXPrint printer setup.

It would seem the application stores the printer selection from the last time you used that printer. However, if that printer is now no longer defined/present, the application may not gracefully handle that and it may subsequently crash.

This was some time ago, but I think I ultimately editted either the app INI settings, or the OS2.INI file for this specific application. By "editted" I mean I removed the reference to that printer which no longer existed on my system.

So in your case, given that Seamonkey is the culprit, check the appropriate entries that might reference the printer. the meantime I'll scratch my head a little more to remember the specific of what I had encountered...

Applications / Re: libxml2 v2.11.5
« on: February 04, 2024, 11:15:47 pm »

Excuse me for butting in but what is the difference between the i686 to pentium4 versions of any DLL and why is there the two versions?

The packages are built with CPU specific optimizations, and those will differ between i686 and P4. In particular for the P4 CPUs the focus is on using the MMX, SSE and SSE2 instruction set.

Keep in mind that this whole approach is applicable to multiple GCC compilation options, be it '-mtune' or '-march', and there are always the more generic options that just focus on generating either FASTER code, or SMALLER code.

Networking / Re: Updated Samba Client
« on: February 04, 2024, 12:09:53 am »
Client 20240127 seems to work fine... here and still getting a TRAP-D.

...not sure what else to try, but msg Andrey, I've worked with him on a few issues in the past and he's really good & I'm guessing he'll give this things a try!

No answers, but perhaps some more info to simplify the troubleshooting:

1) MS Info on Default Input Locales =>

2) FreeRDP issue tracker - 'Option to use the local keyboard layout' =>

- this is NOT quite what you are trying to do, but some of the comments reference the type of functionality that I think you are aiming to have

Code: [Select]
ofreerdp.exe /u:xxxx /p:xxxx /w:2100 /h:1800 /kdb:de /v:m92p or any other value I tried for /kdb including /kbd:0x409 does not. :-(

Could it be that you need to spec out the "lang" part of this as well?:

Code: [Select]
ofreerdp.exe /u:xxxx /p:xxxx /w:2100 /h:1800 /kdb:0x407,lang:0x407 /v:m92p

This should set both the keyboard layout AND language to be used. I'm assuming here both IDs are the same value for German setup.

Hey Andi,

I've tried FreeRDP to connect to different Linux boxes. It works but using FreeRDP the Linux host uses EN keyboard layout. All my Linux boxes does have German keyboards attached and work as expected when I'm sitting in front of them. My OS/2 system has a German keyboard too. But when I connect from my OS/2 system a Linux host via FreeRDP they get the English keys instead the German ones...

So I picked this up from an on-line FreeRDP User Manual (, and while it's specficially calling out the use of xfreerdp, perhaps it works on our port as well:

Code: [Select]
xfreerdp .../kbd:0x409

where "/kbd:0x409" is they remote session keyboard layout you want to use, and in the case of non-EN setups you can use one of these:

Code: [Select]
Keyboard Layouts
0x00000401 Arabic (101)
0x00000402 Bulgarian
0x00000404 Chinese (Traditional) - US Keyboard
0x00000405 Czech
0x00000406 Danish
0x00000407 German
0x00000408 Greek
0x00000409 US

Looking at our port, I see the following option showing up:

Code: [Select]
                                  Keyboard related options:* layout: set the
                                  keybouard layout announced to the server*
                                  lang: set the keyboard language identifier
                                  sent to the server* fn-key: Function key
                                  value* pipe: Name of a named pipe that can
                                  be used to type text into the RDP session

So it would at least appear like you should be able to set this. Give it a try and see if that helps?

Networking / Re: Updated Samba Client
« on: February 02, 2024, 05:04:11 pm »

Latest Netdrive Plugin:
Latest smbcl419.dll:

I seem to be having an awful time with these.

Pulled the NetDrive and client ZIPs, deployed and re-booted.

TRAP-D on bootup, and this is even after I scaled back my massive 1G JFS cache, etc, etc.

Not sure what else to tell ya here, appreciate the work you do though.

Networking / Re: ArcaMapper and Network Protocols
« on: February 02, 2024, 01:34:39 am »

...Still need some help though, Guys and Gals - mount connection is VERY slow (30 seconds), and accessing the subdirectories by clicking them in the resource is slow as well (about 30 seconds). Have attached the log.ndpsmb and log.smbc as .txt files, to see if you have any bright ideas...

Not sure if this contributing, but the following occurs every 10 secs:

Code: [Select]
MEMORY-ALPHA2024/01/31 15:55:04.43: 4 3:  session setup ok. Sending tconx <archive> <********>

and I'm thinking there is parameter somewhere that controls how long a share cache can exist? So perhaps if you have this set to 10 secs. it's driving this.

For what it's worth, I've attached my smb.conf, used for client side purposes as I do not run the server on my OS/2 box.


After all, hard to beat the 3840x1200 Desktop real-estate!  8)
I did it a while ago and quite using SNAP and dual-head. I'm happy with my 42,5" 3840x2160 monitor and don't wanna switch back to two monitor setups although I used it more than a decade. The slightly higher DPI is not a problem for me. But yes a curved 42-46" monitor would be even better.

Alright man, "spill the beans"...what's the combo we need to consider?

1) video card
2) connectors (display, video card, cabling)
3) motherboard/CPU
4) Panorama settings

Anything else I'm forgetting?


...As for SNAP over Panaroma:  I am currently using a dual head/monitor setup - with a dual head kvm for switching between a Win7 machine and AOS machine (the previous one that died.)  I would like to keep the dual head setup.  Hence my fixation on SNAP.  I would be willing to buy any video card needed to run SNAP to keep the dual head setup.  But I suspect all video cards with chipsets supported by SNAP will be old enough to not have GOP/UEFI support...

Like you, I am also stuck (by choice) with the SNAP approach given my desire for multi-head config.

After all, hard to beat the 3840x1200 Desktop real-estate!  8)

...until perhaps someone reports that they got one of the curved giant screens working in our OS/2 bubble, and therefore we have some kind of a map re: product, connector options, Panorama config, etc.

Applications / Re: Scroll-able Command Line Window
« on: January 27, 2024, 10:55:43 pm »
...Changed to the following

/k MODE 80,102

Close and now open the prompt window.  You should see the scroll bar.  If the Window is too wide, change the 80 to 70 or 60...

Yes, but this simply expands the TOTAL window buffer to 102 vertical lines. It is not a continuous buffer that allows you to scroll all the way back to the start of the session.

For that functionality I would recommend MESHELL as well.

Applications / Re: AcpiDaemon start
« on: January 27, 2024, 10:52:20 pm »
Hmm...always had it in CONFIG.SYS, never tried in startup.cmd, but I am not experiencing the sort of issues you are seeing.

Networking / Re: ArcaMapper and Network Protocols
« on: January 27, 2024, 10:49:00 pm »

1) If you include 'client max protocol = NT1' in smb.conf, is there a difference?

Further on this topic, you could try setting 'ntlm auth = yes' to force just the use of NTLMv1 authentication protocol. I say this because I see the following in the log:

Code: [Select]
[2024/01/26 11:52:44.426000,  5] ../../auth/credentials/credentials_ntlm.c:182(cli_credentials_get_ntlm_response)
  NTLMSSP challenge set by NTLM2

which to me means: yup, it's trying to use NTLMv2 authentication.

In fact, 'ntlm auth' and 'lanman auth' go hand-in-hand, both need to be set to 'no' in order to force NTLMv1.

2) Do you have 'name resolve order =' line in your smb.conf?

This has previously caused me some issues as I wasn't able to resolve my lan hostnames and needed to use their static IP addresses. It's been a while though and today things work fine here with the following setting:

'name resolve order = lmhosts host wins bcast'

Above comments based on my reading of O'Reilly's "Using Samba" 3rd ed, 2007 (yup, a little old).

Networking / Re: Updated Samba Client
« on: January 27, 2024, 09:40:33 pm »

...On a different subject - on directories with windows exe files, the WPS blocks while apparently it tries to determine the icons for the files. If the files are large it can take a very long time (minutes - like it reads the whole file) to display and free the WPS...

That has always been the bahaviour I've seen on my end.

In particular, I have my general software library on the NAS, which easily serves all the individual PC installs, but that is a set of directories I generally stay away from viewing on my OS/2 machine for the very reason you mentioned.

It's like the whole EXE has to be read in order for ANY info to actually show.

Pages: [1] 2 3 ... 88