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 4 ... 65
Applications / Re: patched PmMerge
« on: June 14, 2021, 03:00:37 am »
Hello OS4USER,

Any one brave to test ?  :)
... a problem to report.

So during the boot the normal BLUE screen right before transition to WPS happens is missing, the displays actually go black as if the video signal is cut off, then by the time both displays come back I go straight into the WPS Desktop. Normally this only happens after the BLUE screen pops up, a little clock-icon after and than WPS is up.

Weird, but OK so far.

The problem is that attempting to run Lucide right after (repeated this twice) gives me a non-responsive WPS. Only CAD-Helper gets me out of the problem, the Re-boot option that is.

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?

FYI, this is a 4.52 SMP setup (6-core AMD CPU), 202 kernel, latest ACPI, SNAP drivers, dual-screen (1920x1200 x 2).


Web applications / Re: QT5 simplebrowser
« on: June 08, 2021, 02:04:11 pm »
Paul, everyone...

...I for one am a little tired of the constant calls for sponsorship of bww - and the non-mention of other folks who continue to put effort into OS/2 development...

That's an excellent point.

All my $$$ contributions, with the exception of the previous AN/AOS Software Subscription or application specific purchases like NetDrive, PMMail, or OpenOffice, have gone to individual authors. These are usually the smaller $20-25 range "injections" into the "system", since I figured most of us still do OS/2 for the sheer challenge/love/joy of it, and long gone are the days of making profits. So I feel like that approach recognizes the on-going individual contributions.

Now, on the subject of the QT framework based browser I will say the following: it is very dishartening for me to see that BWW and AN appear to be un-willing to work on this major undertaking together, or at least that's my perception today.

Sigurd brings up an excellent point: if AN is NOT providing any sponsoring, why is that?

Look, I will turn the tables on this. I have been participating in the AOS Testers List for some time now. The stuff I can test I do, and I always do it very thoroughly, but to do so it takes time. Granted, one cannot participate in all the testing efforts, heck the latest wave of UEFI is a perfect example of this (I simply lack the hardware), but whatever I can test I certainly spend the time to do so. We all know the old saying "time is money", and it's absolutely my choice to continue to donate to on-going AOS developments, but in some ways it is a certain kind of investment, no?

Therefore, it sure would be nice to see AOS provide a somewhat intangible ROI on that time donation and get behind the idea of getting us a more recent Web engine, after all, vast majority of today's "day to day" computing has moved almost entirely into the web space.

Anyways, much speculation here and we are all guessing to an extent, but perhaps what would help is some clearing of the air by our major platform players?

Networking / Re: Arcamapper (SAMBA) loses connection
« on: May 28, 2021, 07:50:43 pm »
Dave and Lutz,

Quote from: Dave Yeo
... [EAs] need to be turned on, forget exactly but IIRC, both in the kernel and in the EXT4 build as well as in /etc/fstab.
Does this mean, that for turning the EAs off it is neccessary to do this in the fstab-file as well?

Well, I don't have no fstab-file at all in my whole AOS-system. But I did find a file called smb.conf. I inserted the line "ea support = no" and here we go! PMView now works fine!

Sorry for not being clear, I was talking about turning on EAs on your NAS, if needed, not OS/2.

But you do NOT need to disable EAs on your NAS box...what I was talking about in my above post was literally disabling the EAs support in your NetDrive/ArcaMapper connection setup.

You have the option right there to literaly say "this connection/share does NOT support EAs", which means that regardless of what the OS/2 application tries to do with EAs such functions will not be supported by the share where your media is stored.

The outcome of this approach is that only your OS/2 box does NOT see EAs on the NAS, even if that NAS supported EAs with whatever filesystem it's using.

Networking / Re: Arcamapper (SAMBA) loses connection
« on: May 28, 2021, 03:47:44 am »
Hi Paul,

Hi Dariusz,

If you can capture debug logs (create a stub file x:\ndpsmb.dbg in the root of your boot drive) I'd like to try and fix this...

I appreciate the offer, but I'm pretty sure you have tried to help with this before, as on off-shoot to the AOS testers-list discussion, and we found that the ndpsmb.dbg wasn't showing anything. I thought your conclusion was that it may be one of the libraries that NetDrive is using and since there is no access to their source code not much could be done to debug further.

Having said that, I'm more than happy to try this again. Let me know what debug levels you want me to set and I'll let this thing run.

Networking / Re: Arcamapper (SAMBA) loses connection
« on: May 28, 2021, 03:40:19 am »
Hi Andreas,

Dariusz, you've opened a thread here about your connection loss. Do you have tested if the issue persists with the files Alex has mentioned?

Well, I do have:

1) 'samba-client.i686 - 4.11.12-0.oc00' installed here
2) NetDrive, which shows FileSystemDriver 3.028
3) Samba NetDrive plug-in
Vendor:          netlabs
Revision:        3.07.2
Date/Time:       18 Sep 2020 14:19:55

However, this is all running on an OS/2 Warp 4.52 SMP setup, so since it's not AOS I normally test what's being released on the AOS testers-list in terms of general usability, when requested to do so. I will report bugs only if the testing request seeks feedback in non-AOS installs as well.

In the case of Samba updates that has been the process, which is why I have been providing feedback through the list.

This is a bit of a fuzzy area because AN for the most part wants feedback that's specific to AOS installs, which I do not blame them for. That is the software stack they can control and when an issue is reported they can presumably replicate and troubleshoot appropriately. In fact there is a very stringent policy in place that says: do NOT report stuff if you are NOT running AOS.

Subsequently, other than troubleshooting here, or through some one-off email exchanges I have not logged official AOS bugs for this. I continue to test new releases, accept the risk, and if anyone that's not on the AOS path asks questions about this stuff I tend to provide my feedback.

So the short answer is: if the stuff Alex is testing with is core to AOS install and is NOT available as a RPM package, most likely I am NOT testing with these.

Networking / Re: Arcamapper (SAMBA) loses connection
« on: May 28, 2021, 02:01:10 am »
...One thing that may be worth mentioning - I have EA Support turned off for all my shares on the NAS, precisely because ext* doesn't support them to the extent OS/2 assumes. If the EAs are indeed a problem, you might be better off turning them off when mounting the share, because most programs are capable of recognizing when EAs are unavailable and acting accordingly. OTOH, if they think EAs are supported and they aren't (adequately), then I could see some things running into problems...

The approach Alex described is precisely what I have been doing on my NAS box, that being ZyXel NSA325v2 for at least a couple of years now.

I have EA support shut-off in my NetDrive NAS share mappings, that has never caused me a problem with programs like PMView, etc. In fact, our entirl PHOTO library has been migrated to the NAS, and all of these photos, as well as videos are easily accessible.

I will say the following though:

1) PMView can be configured so that when you attempt to OPEN a folder on the NAS, PMView will not attempt to create icons which are then stored in the EA...still, on my system even if I had this setting enabled and my NAS does NOT support EAs, this has never been a problem

2) Lutz, I have a situation very similar to what you describe as far as the disconnect issue goes. My NAS is mapped right at boot time...stays connected, then eventually that connection dies. I have been attempting to troubleshoot and debug this pretty much since I deployed the NAS here. No luck so far. This has remained constant through multiple releases of the Samba client, etc.

In fact what I ended up doing is to write a REXX script which is scheduled to run every 15 mins to check whether the NAS folders are still accessible. If they are not, the NetDrive control program (NDCTL.EXE) is gracefully shut-down and re-started. Following this the NAS stuff is visible once again.

Since implementing this approach I have NOT had a situation yet where I found my NAS unreachable when I needed to use it.

...As you say a 64 bit version of OS/2 is a dream, I have to ask 'what advantage would a 64 bit OS have over a 32 bit one for everyday usage?'...

This comment right here that ivan made is the key point when I look at the future roadmap and the direction I wish to pursue.

For everyday use there really is no 64-bit requirement that I can think of. Sure, maybe if you needed to run a massive database server, or perhaps handled huge data files (OK, sometimes a massive TIFF or JPG file will cause a problem on my machine here, especialy if I already have a few days of runtime on it and the memory has been throughly chewed up), but otherwise, we should be quite alright living in 32-bit world!

Not to take a different direction here with this conversation, but once AN is done getting us the capability to run on new bare-metal I honestly wish they could spent some time on addressing the stuff that always turns out to be the weakness, shared memory...I've got to believe there is a way to technically do "garbage collection" and/or prevent the fragmentation to start off with.

Rich made an excellent point.

I just went through a purchase of a brand spankin' new PC for my son, who is away attending school. Now the machine he was using at home wasn't all that old: Asus Prime X470-Pro, AMD Ryzen7 2700 CPU, Samsung 970 Pro M.2 NVMe drive, etc.

Guess that I have "acquired" that hardware (having easily convinced my son to "upgrade") I absolutely intend to take a shot at moving my OS/2 install into that new world.

Point being, our OS/2 still has some legs left in it...yeah, it'll take a little more care than normal/usual, but results can be achieved and this wouldn't have happened had AN not pursued the changes to AOS they did pursue.

I for one am more excited by what's been delivered over the past 6 months then the stuff I've seen over the last 5 years.

Hi Dariusz, before monitors supported EDID, you really did have to set things up manually for your monitor, and depending on the monitor specs you entered, the screen object would have shown the possibilities I assume. I only had a VGA monitor back in the Warp v3 days and don't remember the screen object... are right...I do recall those days after all. My first OS/2 video card (which would have been OS/2 v3) was actually a Cirrus Logic shipset card...but heck, those drivers are long gone from my machine.

Dave's suggestion is probably the best-fitting driver package you're going to find. I'd give that a shot...

...The default display parameters for the OS are VGA 640x480 256 colors.  I know the Genoa card can do better and was trying to find a better resolution and bit depth.  But, as I say, I am not very experienced with the OS and don't really know what's possible or how to achieve it.  I thank you all for your help.


So I'm curious, when the WPS (Work Place Shell) comes up and you see your OS/2 Desktop, are you able to select the "OS/2 System => System Setup => Screen" object?

I have had SNAP deployed here for some years now so I am not 100% sure, but I am nearly certain that this is the standard OS/2 "screen-setup" object. If that objects exists on your machine, you should be able to open it up and select a higher resolution and colour depth. Of course these will be driven by the system's ability to recognize the display montior hardware, but it's worth a try in order to avoid getting stuck with the ancient VGA resolution.

| SciTech SNAP Graphics for OS/2 requires a version of OS/2 Warp 3 or
| later in order to run. More importantly, it requires at least Warp 3
| with FixPak 35, or Warp 4 with FixPak 5 installed.

Right...and per Charles' original post (although the BOLD is my add), where he stated:

...I am completely inexperienced ("noob") with OS/2 but I installed V3 on a '586 VLB machine and had a running system until I tried to install a video driver for the Genoa Windows VGA 24 VLB video card...

the suggestion to deploy SNAP should provide a viable and hopefully better result.

Here is something else you could try: head on back to Hobbes and d/l the SNAP video drivers. Here is the direct link to the ZIP file =>

Given that your video chipset is an older one I'm not sure if that last public version of SNAP supports it, but the README will most likely point it out.

The benefit with these drivers is that they simply have additional capabilities to help you deal with different monitor formats, resolutions, etc.

Worst case if SNAP does not work, is that you repeat the same VGA Recovery process that you had just gone through.

Hey Charles,

Probably the quickest way to get back to a working system is by forcing the VGA mode at boot-up.

Here is what you need to do:

1) Re-boot the machine
2) when the white rectangle pops-up in the top LEFT corner of the screen (during early boot stage) you hit ALT+F1
3) you now should be looking at a menu that has several choices, select option 'V' I think (if I remember correctly), this will force the box to book in VGA mode

Try it and let us know what happens.

Hi Doug,

...I don't know if you can make shadows of file system objects stored on media that doesn't support EAs.  If the shadow is stored in OS2.INI then you probably can.

Yes, this works. I have the "Documents" directory off of my NAS showing on my OS/2 Desktop as a Shadow object. As long as I connect successfully to the NAS (which is done during boot through NetDrive) that object will be 'live' by the time WPS comes up.

Your idea on how to use the WPS Shadow functionality is precisely what I wanted to do.

Hardware / Re: OS/2 on Virtualbox with 8 COM ports
« on: May 07, 2021, 03:08:43 am »

Hi. First time here and first post. I am the CTO of a hardware design company (Est 1985) in Canada and have strong design experience with PCI, PCIe and USB products.
Sam came to our company many moons ago when he resided in Michigan (IBM), just prior to us becoming a supplier to PictureTel who used our ISA adapter (back then) on OS/2. It was the industry's first jumperless I/O adapter.
Kumar Bhatia
Axxon (OEM) Inc.

No's been many many years since we talked, but say around the early to mid-90's I would stop by once in a while at your shop and just talk pure computing stuff, or better yet, the field of Artificial Neural Networks. Not sure if you recall, but during my first visit to your location I remember asking to speak to the president as the business name, Axxon, was just so darn close to the AXON of the ANN fame (and well, the biological build we all have within us), which was my field of study (thesis work) for my last year of undergrad at UofGuelph.

Anyways...a bit of a memory lane walk there, and welcome to our forum. We have just a couple of OS/2 users from Windsor on here, and as both Martin and Neil pointed out, this forum is largely focused on grass-roots type of discussion around our platform.

ArcaNoae on the other hand is the leader in the commercial space today, and I for one would hope they might need the sort of solution you can provide. Lewis will be able to answer this I believe.

Either way, would love to catch-up...heck, I remember you telling me about the assembler work you guys were doing at that time, most of it device driver software if I recall?

Pages: 1 [2] 3 4 ... 65