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 ... 65

The HL-5470DW isn't a supported model in ArcaOS 5.0.6...


Not all the features are supported, but to say it is NOT supported is incorrect.

Heck, the old IBM PSCRIPT driver will work...but again, as per my post above some printer features will not.

Hi Greggory,

:DI'm about to buy Blue Lion! Does anyone have an experience with a Brother HL-5470DW High-Speed Laser Printer?

Or used the drivers below. I hope it works I picked it up for only $26 bucks !!!...

Yeah, you can't go wrong for that price!!!

Indeed, I have been using this very printer in OS/2 for a couple of years now. What I am about to explain is specific to getting native PSCRIPT based drivers configured. I have not tried to install CUPS and compare the results.

To start off with, here are a couple of existing threads on our forum that detail the specific "issues" and fixes, so instead of a copy/paste just take a look at these:

1) Anyone successfully using Brother HL-5470dw? =>,902.0.html

2) How to find or extract a Postscript printer driver? =>,1684.0.html

3) Printer advice =>,1554.msg15255.html

The following section is from my post in #3 above, where you'll also find the matching fixed-up PPD's in case you want to give the native PSCRIPT drivers a chance:

So here are the setups I currently have in-place, all these relate to the Printer=>Properties window:

1) OUTPUT PORT (field names below match the dialog-box you will see)
LPD server = static IP I assigned to my printer
LPD printer = BINARY_P1

Port name = SLPR1
Print Timeout = 60 secs

Performance = LPRPORTD Compatible (I was never able to get the 'High Performance' setup working)

2i  => PSCRIPT
I used the IBM PSCRIPT v 30.800 driver here, but first I imported the 5470DW PPD file into that driver. This allowed me to have the various printer specific features available in the printer driver. This is also where I ran into some problems, especially around the print resolution. For example, trying to use HQ1200 always caused PSCRIPT driver to crash. So by default, I have my printer set to 1200. I simply like my high-quality print and using 600 just doesn't appeal.

2ii => PSPRINT
I also setup the PSPRINT driver, similar setups to PSCRIPT, my goal here was to find out if the changes Alex included in PSPRINT would create a better result. This, amongs other things, allows your print jobs to include fonts (support for embedded TrueType fonts) with each output.

I did not see much difference, as a result, I am using the IBM PSCRIPT driver nearly 100% of the time.

That is my 2nd Brother printer and I have been very happy with it, even though I am forced to run in 1200 dpi and cannot use the HQ1200 (which really is not that big of a deal actually as I simply do not print big enough of a volume to start seeing a hit to the toner use. I get about 3 yrs and 6500 pages per regular TN750 toner cartridge).


I lowered the setting to 2560 (which is what I used to run some time ago) so I'm curious if this will impast stability in any way.

Regardless, I responded to Steven on our Testers List suggesting that in the TRP output file we split out the process specific DLLs from the high-memory, and therefore system-wide DLLs.

Either way, I also reverted back to 202 kernel because 203 was certainly causing me problems here. As you commented in your post though, my testing being done outside of AOS is only relevant to a certain extent.

However, with all due respect I have to disagree with your "'s a shame you don't properly test on ArcaOS..." comment. I think AOS is missing a huge opportunity by relegating two AOS pathways to the back of the queue, those being:

1) Software Subscription - this was initially in place, I am not sure if that offering exists anymore
2) Upgrade Path - I'm not certain how many stand-alone users can, or are willing to completely start with a clean-slate approach, that being a fresh re-install and the unenviable attempt to bring the relevant data over to the new system

I will say this again, and I have been very open about this: if I have to re-install from scratch, I will probably depart from our beloved OS/2 platform and carry on elsewhere. There simply is that much accumulated content I currently have, where it would make no sense to re-create all of it. It is much easier to build a new cutting-edge solution and replicate my existing OS/2 install within a much simpler, faster and much less pain.

In fact I wish there was a sub-team focused on doing the sort of testing I regularly do: see if the currently delivered changes still work on the "old" OS/2 config, as well as perhaps even introducing additional functionality. Heck, this could be entirely volunteer driven effort since the subset of the AOS functionality that could continue to filter out under the 'Software Subscription' option is a much smaller and managable bucket, and those releases could remain completely outside of the main AOS code-base trunk, thus would have very little impact on the pure AOS stuff.

So I'm using Dave's excellent FF 49.5 update (Sec #2 I think?). Pretty rock solid, although there does appear to be a slight regression in terms of saving certain types of files, where the tmp location FF uses never re-names the file to the final filename and instead keeps it in that *.*.part format. Anyways, no biggie, I know about it (normally happens when I d/l any Google Photos grouping of files and it's actually a ZIP file that's built).

Alright, but that's not the reason why I'm posting.

I just had one of these rare crashes, FF trapped and I found the following in the TRP file:

Code: [Select]

 Exception Report - created 2021/06/26 10:30:47

 LIBC: Killed by SIGSEGV

 Hostname:         NEUROBOX
 OS2/eCS Version:  2.45
 # of Processors:  6
 Physical Memory:  3199 mb
 Virt Addr Limit:  3072 mb
 Exceptq Version:  7.11.5-shl BETA8 (Jun  1 2020 18:37:02)


 Exception C0000005 - Access Violation

 Process:  G:\APPS\TCPIP\FIREFOX\FIREFOX.EXE (02/21/2021 11:47:09 72,434)
 PID:      5C (92)
 TID:      01 (1)
 Slot:     C3 (195)
 Priority: 200

 Module:   XUL
 Filename: G:\APPS\TCPIP\FIREFOX\XUL.DLL (02/21/2021 11:52:25 39,789,052)
 Address:  005B:BAB6EF7E (0001:02D2EF7E)
 Cause:    Attempted to read from 00000010
           (not a valid address)


 Failing Instruction

 BAB6EF6E  TEST EBP, EBP         (85ed)
 BAB6EF70  JZ   0xbab6f0b0       (0f84 3a010000)
 BAB6EF76  MOV  [ESP], EBP       (892c24)
 BAB6EF79  CALL 0xbab6b080       (e8 02c1ffff)
 BAB6EF7E >MOV  EAX, [EAX+0x10]  (8b40 10)
 BAB6EF81  MOV  EAX, [EAX+0x20]  (8b40 20)
 BAB6EF84  MOV  ECX, [EAX+0x10]  (8b48 10)
 BAB6EF87  TEST ECX, ECX         (85c9)


 EAX : 00000000   EBX  : 0013D14C   ECX : 20C68FCC   EDX  : BA8CEA04
 ESI : 3F549020   EDI  : 0013D0BC
 ESP : 0013D090   EBP  : 20C68EE0   EIP : BAB6EF7E   EFLG : 00210206
 CS  : 005B       CSLIM: FFFFFFFF   SS  : 0053       SSLIM: FFFFFFFF

 EAX : not a valid address
 EBX : read/write memory on this thread's stack
 ECX : read/write memory allocated by LIBCN0
 EDX : read/exec  memory at 0001:02A9CA04 in XUL
 ESI : read/write memory allocated by LIBCN0
 EDI : read/write memory on this thread's stack


 Stack Info for Thread 01

   Size       Base        ESP         Max         Top
 00100000   00140000 -> 0013D090 -> 000CE000 -> 00040000


...but much further down when I see the list of DLLs that process was "aware" of I find the following:

Code: [Select]

 DLLs accessible from this process
BRWSRCMP b7d49000 0001c000 02/21/2021 11:53:01    108,314 G:\APPS\TCPIP\FIREFOX\BROWSER\COMPONENTS\BRWSRCMP.DLL
 LGPLLIBS b7d79000 0000f000 02/21/2021 11:46:07     75,290 G:\APPS\TCPIP\FIREFOX\LGPLLIBS.DLL
 MOZSQLT3 b7d99000 0009d000 02/21/2021 11:46:07    520,683 G:\APPS\TCPIP\FIREFOX\MOZSQLT3.DLL
 XUL      b7e49000 03c2d000 02/21/2021 11:52:25 39,789,052 G:\APPS\TCPIP\FIREFOX\XUL.DLL
 LGPLLIBS bba89000 0000f000 11/17/2020 00:43:25     74,292 G:\APPS\TCPIP\THUNDERBIRD\LGPLLIBS.DLL
 MOZSQLT3 bbaa9000 00098000 11/17/2020 00:43:15    510,726 G:\APPS\TCPIP\THUNDERBIRD\MOZSQLT3.DLL
 LDAP60   bbb69000 00020000 11/17/2020 00:48:04    119,571 G:\APPS\TCPIP\THUNDERBIRD\LDAP60.DLL
 XUL      bbb99000 03c7d000 11/17/2020 00:52:28 41,160,984 G:\APPS\TCPIP\THUNDERBIRD\XUL.DLL

You'll note that the very same DLLs are showing up that are actually loaded by either FF or THUNDERBIRD.

I was always under the impression that with the Mozilla suite of applications this should never be the case, meaning: the process will have visibility to it's own DLLs, which FF does, but would not see same named DLLs that were loaded by another process.

The above conclusion is based on the comments in both the FF and TB readmes that state the following:

Note:  Starting with Firefox 45.9.0 GA, it is not necessary to set LIBPATHSTRICT
       manually or using the Run! utility for it as this is done automatically
       by firefox.exe when loading XUL.DLL and other Mozilla DLLs.

So am I just misunderstanding what the TRP file shows as far as the listing of the DLLs being accessible by the process goes?

I did NOT expect FF to have any visibility to TB's DLLs, or vice versa.

If something needs to be done about this, there is always the option to use the README suggested program object parameter of:

Parameters:         /c set LIBPATHSTRICT=T & seamonkey.exe "%*"

...although I have not tried that approach yet, easy enough to do though.

Networking / Re: Universal Naming Convention (UNC) on Samba?
« on: June 21, 2021, 02:11:38 pm »
Hi Doug,

Looks like Dave's answer is, unfortunately correct.

For Darius:

UNC =  \\machineName\shareName

machineName originally was a netbios name.  ShareName was a shared resource on machineName, i..e a drive or a directory.

Right, I got that. My NAS maps to and is present in LMHOSTS file as well. My expectation was that the Samba client would automatically show all shares that are present, sort of similar to what smbtree shows, albeit with actual contents listed. That may have been too wide of a sweep though! lol

It would appear that as of right now the UNC resolution, when attempting to access Samba shares, does not work on our platform. ('ls' did not work either)

Networking / Re: Universal Naming Convention (UNC) on Samba?
« on: June 20, 2021, 12:46:20 am »
I think you have to use an URL such as,
Code: [Select]
smb://NAS/publicAnd NAS has to be resolvable, through DNS (host file) or the WINS thingy.

So 'dir smb://nas/public' Dave???

Nah, no go...NAS is resolvable, I have an entry in HOSTS as well as lmhosts, here is what I get:

Code: [Select]
[G:\]dir smb:\\nas\public

The volume label in drive G is OS2.
The Volume Serial Number is 45B6:75C3.

SYS0123: A file name or volume label contains an incorrect character.

...and the forward-slash version of it just produces multiple SYS1003 errors ( The syntax of the command is incorrect.).

Networking / Re: Universal Naming Convention (UNC) on Samba?
« on: June 20, 2021, 12:24:09 am »
Hey Doug!

Do you mean as in "dir \\nas"?

..where 'nas' is my local nas box?

In that case, from CLI it does NOT work.

Now consider that I have all my Samba shares mapped through NetDrive, as such, I can readily get to them through the typical drive mapping.

When it comes to Samba specific client though, here is what a 'smbtree' returns on my system:

Code: [Select]
Enter HOME\dariusz's password:
        \\WINMAIN                       WINMAIN
                \\WINMAIN\C$                    Default share
                \\WINMAIN\ADMIN$                Remote Admin
                \\WINMAIN\Printer2              Microsoft XPS Document Writer
                \\WINMAIN\SamsungPhotoPrinter   Samsung SPP-2040 Series
                \\WINMAIN\print$                Printer Drivers
                \\WINMAIN\IPC$                  Remote IPC
        \\NAS                           NSA325
                \\NAS\IPC$              IPC Service ("NSA325")

But if the Samba client approach is A-OK for you, than I would say the UNC naming convention would work.

Applications / Re: patched PmMerge
« on: June 18, 2021, 03:21:47 pm »
So is there a possibility for us to do some kind of a TRACE on this?

I have no idea how to do that.  In archive sub dir  you  can find previous ver  of pmmerge   -  you can try to find last good for your system.
I understand and can appreciate that. Thank you!

FYI, I repeated my tests with other applications, found out that each time I opened a PM app the WPS become frozen. CAD Pop-up followed by a Re-boot got me out.

Applications / Re: patched PmMerge
« on: June 17, 2021, 04:59:04 pm »
My follow-up question was asking how else you think we could track down what's causing the problem?

pls suggest  what  should I do to repeat you case on my comp ?

Honestly I wish I could provide a suggestion, but given that I'm running a dual-screen setup here with SNAP drivers, whatever PMMERGE DLL is managing, which I believe is the majority of the Presentation Manager calls that are most likely closely interacting with the display drivers, I suspect can only be debugged on my specific hardware.

So is there a possibility for us to do some kind of a TRACE on this?

I am at a loss, but you had asked for feedback, so I provided my results. I will have a little more time later today so let me re-deploy that DLL and see if any other applications cause the same issue.

Applications / Re: patched PmMerge
« on: June 17, 2021, 02:29:16 pm »
I haven't tried any other apps yet since I figured I would report this first and test any other specifics you might be interested in?

Nothing special, just observe  what has improved  and what has degraded.
Well, what my report was intended to convey is the fact that using the patched pmmerge.dll no longer provides a working system. So that in my book would be a major degradation.

My follow-up question was asking how else you think we could track down what's causing the problem?

Applications / Re: hard hangs
« on: June 16, 2021, 07:25:55 pm »

The biggest increase in stability I encountered was when I made the move from HPFS386 to JFS. Not that inherently there is anything wrong with HPFS386, but I was running over 12 separate partitions (due to the 64G limit) and that just seemed to make things very lock-up prone.

I am now running 7 partitions, of which 2 are small maintenance ones and have very few, if any, lock-ups that appear to co-incide with any sort of disk access.

What configuration are you running with?

Applications / Re: FreeRDP - we have options!!!
« on: June 15, 2021, 03:46:44 pm »
Thanks Dariusz for posting this good content. If you ever want to write a further article or tutorial, we can post it on the OS2World wiki.

Let's also remember to send the appreciation to Andrey Vasilkin (digi) for his OS/2 software and ports...

Would be very happy to do so. In fact I have been conversing (and testing) with Andrey for some time now the Application specific functionality. I had promised him to write up a document that details the setups since there are a couple of different ways to just starting such a session, i.e. start a NEW session, or connect to an existing session?

Anyways, this is still in WIP, fell behind a bit and I need to get back to it. Once I have a draft and Andrey is happy with it I would happily share.

Regarding sponsoring...absolutely I would encourage this. I have already done so myself, and as with all such situations continue to support the developers who continue to bring solutions to our platform!

Applications / Re: FreeRDP - we have options!!!
« on: June 15, 2021, 03:42:08 pm »
Hi Mike,

...I propose to check the example MSOFFICE.CMD you shall find in the installation folder of FreeRDP.
I just adjusted the path and login information to my configuration and it worked.
In this case I could start MS Office in my AOS. I assume same will be working also for the browser...

This is a great starting point.

I am curious though, in your setup, is the Office connection coming up in a full 'remote session' or are you using this as a stand-alone application through the 'Application Server' functionality?

I ask because when I started to look at FreeRDP I had originally not realized that the 'Application Server' component is needed to establish just application sessions. Some Win OS versions have that 'Application Server' function built-in, most do not. If your Win OS install does not you must use another solution, such as the Thinstuff software.

More than happy to try alternative solutions though, which is why I'm curious regarding how that is working on your end.


Roderick, everyone...

Again I am looking for numbers to estimate how big our community roughly but it will always be a gamble to a large extend.
The 500 users was based on the IP numbers from Netlabs. But how accurate that is ? But I never stated we have 500 private users left. Read the other postings for the rest of the details...

So why don't we set up a honey-pot of sorts and use a different approach to uniquely identify the hardware that's running OS/2?

My understanding is that ANPM does exactly that. They use dmidecode to pull an OEM string that identifies the hardware, my understanding is that this is the UUID field value (not 100% sure, but someone could verify).

So here is what that looks like on my machine:

Code: [Select]
Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: MSI
        Product Name: MS-7640
        Version: 1.0
        Serial Number: To Be Filled By O.E.M.
        UUID: 00000000-0000-0000-0000-6C626D50A7A8
        Wake-up Type: Power Switch
        SKU Number: To Be Filled By O.E.M.
        Family: To Be Filled By O.E.M.

Take a look at the full dmidecode dump (see attachment). What would simplify this is having a front-end web page that spells out how the end-user should do this, and we're talking literally a simple 1-5 step process, or simply accepts the UUID value that the user extracts out of the dmidecode dump.

Heck, dmidecode has an option to literally pull just the UUID, that being: "dmidecode --string system-uuid".

Applications / Re: FreeRDP - we have options!!!
« on: June 15, 2021, 02:06:37 pm »
Hi Lutz!

...But doing the same by means of my WPS-icon nothing happenes at all. No Firefox starting up, no error in the log file. For a fraction of a second the icon gets shaded, then nothing.

Do I have to meet some special prerequisites on that Win7-machine?...

That is correct, you need an Application Server component to run on the Win side of things so that FreeRDP can connect to just that particular application you specify.

Here is what I specifically noted in my original post above:

...In order to be able to serve that application on the HOST side you need to run a Win Server OS, such as 2008, etc., basically something that has the Terminal Server (Remote Desktop Services) component up and running. So what is one to do if this is not an option?

Well, there is an alternative. Take a look at Thinkstuff (, and in particular their XP/VS Terminal Server. There are several options available as far as the licensing configuration. The lightest option is the 'Lite' configuration, and at $39.99 USD that's a pretty low-entry to a viable way of "running" (double-quotes there b/c you're NOT really running it locally, this is not ODIN, rather only serving the display) most Winx applications locally on your OS/2 box....

I purchased the thinstuff application server and deployed it on my win7-pro setup. Works perfectly!!! To be honest I'm surprised there isn't a much bigger group of OS/2 folks who are jumping at this becuase in a typical multi-os LAN install this is such an easy solution. I do realize that not everyone will have multiple OS installs however.

For my part I am routinely running the Win version of Firefox whenever I happen to hit a site which our version of Firefox can't handle...and there are many many more of such sites these days.

Beyond that I have a couple other apps that I'm working with in order to better take advantage of the functionality Andrey ported to our platform.

If there is one complaint I have about FreeRDP it is that it consumes a LOT of shared memory. In fact, once a session is started it'll easily eat up over 100MB, eventually after a day or so that'll grow to about 200M at which point in time things start shutting down here as shared memory is completely used up. I run my box 24x7 so there isn't a regular once-a-day shut-down that cleans things up for me.

In comparison to this the RDesktop app (also ported by Andrey) doesn't have this memory issue, however it also does NOT implement the Application server client functionality. As such it is best suited for a full session use, which is how I use it most often.

Pages: [1] 2 3 ... 65