So I thought I would summarize my experience with this particular approach to working around our platform issues, one of them being a badly out-of-date web browser.
Some of you may be aware of the excellent FreeRDP (
http://os2.snc.ru/product-freerdp.html) port that Andrey Vasilkin has made available. I have been using his previous version of the RDesktop (
http://os2.snc.ru/product-rdesktop.html) for a while now. When he made the FreeRDP available I jumped at it because it offered something significant: the ability to run a remote APPLICATION as if it was a local app.
Now let me detail some of the pre-requisites because this isn't one of these solutions that everyone can use. But, if you have a Winx box running on your LAN (or even WAN) you certainly could deploy this approach.
In short, if you have such a Windows installation accessible to you, you can serve a particular APPLICATION on that HOST machine. FreeRDP is the client side of the RDP solution that will allow you to effectively just RDP to that single application the host is sharing. This is the key difference between something like RDesktop, which does a whole session sharing where the whole Win Desktop is available. As much as sometimes that's the preferred way to access, at other times this introduces a significant amount of overhead.
Subsequently, with FreeRDP you can certainly be a single-click away from having access to a Firefox 'whatever version' you need that you have running on that remote HOST, and it being served up locally on your OS/2 WPS literally as if it was just another PM window.
BUT
...there is of course a caveat that comes with this.
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 (
https://www.thinstuff.com/products), 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.
So how did this pan out for me?
My Windows server is a Win7 Pro 64-bit box. I installed the Lite version of the ThinStuff's 'XP/VS Terminal Server' and was able to configure a WPS object that invokes the Firefox browser on that Win7 machine and serves it out locally on my OS/2 box.
This is on a LAN (so pretty quick) and even watching YouTube videos that actually works. There are some audio issues I'm encountering, intermittend drop-outs, etc., but video and audio is already a heavy application, so the mere fact that I can get to numerous web-sites while still directly in front of my OS/2 screen is great!!!
Anyways, for what it's worth, there is an alternative some of us may be able to use.