Ecomstation 22 Iso Download

Jul 16, 2018 - EComStation Screenshot,,, and other various developers OS family Working state Current Source model 2.1 / May 20, 2011; 6 years ago. An anonymous reader writes 'Yes, those OS/2 Warp bastards just don't want to quit.Today the eComStation 2.2 beta live CD was released for public download. There is also this positive review from TechRepublic, and OS/2 Zelots partying/ranting at their community sites.'

Those of us who do support on systems from many different clients really don't wonder why they still exist. HURD is one thing; we don't really wonder why it's stillborn. OS/2, or more specifically eComStation, is something else entirely. OS/2 has a history of commercial support, which means it's also got a history of applications with support. Kirby and the crystal shards rom. Support means that people used those applications, on the OS, in a business capacity.

Think of OSes like: SCO, DOS, and yes, OS/2. Just because the OS, and application, support goes away doesn't mean those applications aren't still needed.

There are a LOT of applications out there which were written one-off, for a single client in a specific role. The companies that wrote them may not even be in business anymore, but the application still works and the the cost of So people are running their applications on legacy operating systems, sometimes on some pretty janky hardware (I once saw an old box with IDE controllers on a proprietary IDE RAID controller - with half the RAID consisting of CF cards on adapters). Maybe they've managed to virtualize the platform, or partially virtualize it (such as when there's a hardware platform to the application, requiring COM port bridging to the guest so that a USB to COM adapter can be used to interface with a proprietary reader/etc. - you get the point). No, it's not an ideal business scenario, and there are certainly situations where a lot can go wrong, ruining your day.

But There are a lot of these companies, which means there's a special use case for support. Or just in-house people needing to upgrade things to keep as much of their stack compatible as they can. So yeah, there is still a need for such legacy platforms. Just because it's not shiney and new doesn't mean it's lacking a valid business case. Just because the OS, and application, support goes away doesn't mean those applications aren't still needed. And what is needed is for those applications to be portable to begin with, so that when your OS or architecture dies you don't have to go vainly crawling after it hoping that it will come back to life, keeping it on life support and praying that it does not completely expire. And anyone who is now having to keep OS/2 going either fucked up or is following someone who fucked up, and didn't follow this simple principle.

When you find out that the software only runs on one OS, you're supposed to t. It's there - heard of [sourceforge.net]? Essentially, it consists of the L4 microkernel, which has multiple personalities riding over it - a Presentation Manager personality, a win16 personality, a win32 personality and a neutral personality. The last one is the native personality that provides the microkernel services to all the overriding subsystems. This is somewhat similar to IBM's Workplace OS that they were trying to do in the 90s to give PPC a native OS of its own, except that instead of the slow Mach 3 micr. A nice benefit is that OS/2 remains (moderately) updated for other users.

There are more nice benefits. Like the unrivaled WPS, the unrivaled DOS capabilities, the ever growing linux friendliness (meanwhile we have CUPS, qt4, and rpm working).

Best of all is the unrivaled peace of mind after 20 years of internet access without malware threat. And please don't believe the FUD about not running on modern hardware. The eCS 2.1 machine I'm writing this comment on consists of an N68C-GS FX mb with Athlon 64 X2, PCIe graphics, SATA and PATA HDDs, and 1600*1200 display. It also works with. Back in the day I co-developed a set of tools that off loaded costly mainframe development to relatively inexpensive OS/2 workstations.

Code was synchronized between the two platforms with a full execution environment for each developer rather than the single shared environment they had on the mainframe. For those of you interested in such things, it was a CICS/COBOL/DB2 application being developed. At the time, Windows 3.1 would have been the only alternative and it couldn't even come close to what OS/2 w.