10 ms·
OsFree project: OS/2 Replacement
- peter_d_sherman 7y agoWould love to see an Open Source OS/2!
- deleted 7y ago[deleted]
- hvs 7y agoProbably won't happen. Companies have been willing to buy the IP and support it (Serenity Systems with eComStation, Arca Noae with ArcaOS) because there are legacy installations of OS/2 that need to be supported (and are willing to pay). To get a sense of the companies that still need OS/2 support, see this list from Arca Noae: Advantech, Austria Agie Charmilles SA, Switzerland Bowe, Bell & Howell, U.S.A. Canadian Coast Guard, Canada Colgate Palmolive, U.S.A. Dematic North America, Luxembourg Federated Insurance, U.S.A. Johnson and Johnson, U.S.A. Pepsi Co., U.S.A. Roos Instruments, U.S.A. Siemens AG, Germany Trainitalie, F.S., Italy Universal Instruments Corp, U.S.A. Whirlpool Corporation, U.S,A, http://ecomstation.com/index.phtml http://ecomstation.com/index.phtml https://www.arcanoae.com/arcaos/ https://www.arcanoae.com/arcaos/
- zozbot234 7y agoRumor has it that OS/2 or a compatible system is still needed to boot up some legacy IBM mainframes, the OS/2 box is used as a kind of system console.
- unixhero 7y agoYes, it uses ThinkPad laptops to coordinate the bootup of the machine, in the past these ran OS/2. Beautiful.
- cptnapalm 7y agoRaises hand I have a Multiprise 3000 and this is true for me, or would be if I could get the software that will actually bring up the mainframe hardware.
- skissane 7y agoThat was true for IBM mainframes manufactured prior to 2005. The hardware management console computer (kind of like BIOS setup on steroids) was a PC running OS/2. Models since 2005 have used Linux instead, although the management app on Linux was designed to duplicate the visual look of OS/2 (to make existing users feel more comfortable.) I remember around 2006 or so, watching a service technician replace some faulty hard disk drives in an enterprise SAN. He opens up the front door, and out of this compartment he slides a laptop computer which runs some management software. From the look of the user interface, it appeared to be running Windows 3.1.
- chiph 7y agoOne of the reasons why the original OS/2 source wasn't made available by IBM was that there are a lot of 3rd party libraries in it. Many from companies that no longer exist, or firms that have been acquired several times, so it's just too hard to get the release signatures.
- zozbot234 7y agoIt would be interesting to see a Wine-like compatibility layer for OS/2 applications. It could even be included in Wine itself, seeing as there are quite a few analogies between Win16/Win32 and OS/2.
- lordleft 7y agoOS/2 always intrigued me because it looked like a strange cousin of Windows; it so clearly shared the design language (and some actual code) with that family of operating systems.
- Yoric 7y agoWell, the Windows NT family (which includes Windows 2000, Windows XP, Windows 7, Windows 10) is a descendant of OS/2. In fact, Windows NT 3.1 was basically a reskinned OS/2. I remember fond days of playing several MSDOS games at once under OS/2 (Elite: Frontier and Colonization, iirc) while Windows 95 failed to play any of them :)
- jmspring 7y agoYep, the schism between IBM and Microsoft let to the two products. I preferred OS/2 and workplace shell at the time. Heck, I was using OS2 up until 2000ish. Then got sucked into the land of BSD. I still have a vm floating around of OS/2 Warp so I could play the original Galactic Civilizations from Stardock
- pjmlp 7y agoOne of the few things I missed was not getting SOM instead of COM, but we have UWP now, and the DCOP / AIDL / gRPC variants. And the UI had more powerful concepts, but I guess too advanced for most users.
- llarsson 7y agoPlease write about some of these UI features, I would love to hear about it! I never got to play with it, because it demanded a much better computer than I had.
- guessbest 7y agoI think the GP was referring to features that were advanced for the day, but these days we take for granted, like a system control panel controlled entirely through a GUI rather than any text files like Autoexec.bat and config.sys
- jchw 7y agoThey mention their own bootloader called freeldr. Interestingly, this is the same name as ReactOS’s bootloader. I assume it’s just a coincidence, but since I know OS/2 and NT share some common lineage, I do wonder if there’s any relation. A bit of searching didn’t seem to clear it up. Anyone have a clue?
- JPLeRouzic 7y agoIt's a long time since I do not follow this topic, but I think Freeldr is (was?) an independent project. I think also it was introduced in Reactos at the end of the 0.2.x branch. For example it was not used in Captive Reactos and pre-2005 versions. http://git.jankratochvil.net/?p=reactos.git;a=blob_plain;f=loaders/dos/loadros.asm;hb=HEAD http://git.jankratochvil.net/?p=reactos.git;a=blob_plain;f=l... Though I may be entirely wrong.
- peatmoss 7y agoSeems like a challenging project. I remember OS/2 fondly, and I remember (and have heard tales of) its stability. Still, I have read stories that claim the source code was a hot mess of hacks and liberally sprinkled assembly code. Apart from “hacks and glory” (which for the record is a fine justification), I don’t imagine that this project would have a lot of utility. While some old ATMs and some other legacy applications run on OS/2, I’d guess that attaining the degree of compatibility needed to satisfy those applications would be an extremely tall mountain to climb. I think there are a lot of us who remember computing of the 1990s and early 2000s fondly as being a time where you could discover an operating system that was new or novel in some way. Combine that with the fact that computers felt less laggy, and mostly used the same UI across applications (looking at you electron), and I share the nostalgia. I guess what I’m saying is that an OSS OS/2 is cool, and its authors should have songs sung about them, but this isn’t the right foundation to build a modern OS on.
- kitd 7y agoI spent about 7-8 years developing on OS/2. It lent itself to being tinkered and tailored in a much more developer-friendly way than most OSes. The rexx scripting was pervasive. There were meaningful file object attributes that could be extended and used per app. The SOM model was a bit clunky but very powerful (I went on to work with its designer later in my career). It had a bunch of powerful compilers that left all the Windows competitors for dust. And of course it looked great for a windowed GUI at the time.
- guessbest 7y agoWhen did you develop for it? I remember 89 to 95 being the heyday of OS/2, when if you wanted to get your Windows 3.1 machine on the network, you pretty much had to use OS/2 or Novell to host the network.
- kitd 7y agoThis was approx 1990-1998. I was working for an actuarial partnership. Our software generated customer-specific actuarial FORTRAN code, with the generator and UI in C. We used the Watcom compilers for both ends of the pipeline. They were top class, and still available AIUI.
- rietta 7y agoAh OS/2 Warp. The OS I got grounded over because I reformatted the family 486 and lost some of my parents files. I truly thought I was setting up dual boot. I was so naive at the time.
- dschuler 7y agoThat's funny, the exact same thing happened to me!
- unixhero 7y agoMe too! It DID say it managed to do this, however it didn't work.
- tecleandor 7y agoMy dad thankfully had all his documents on floppies... :P :)
- ttul 7y agoI humbly apologize to the Santa Clara library for doing the same thing in the late 1990s..
- twooclock 7y agoThis brings back memories! I was part of TVT (translation and verification team) for os/2 in 1996. Still remember how developers were supplying fresh builds to install and verify. We were a bunch of people from all over the world trying to do our best and localize os/2, but you could hear the boat sinking - windows was just too good - which is a pitty since from technical standpoint os/2 was better. I have to check I sill might have some cds from that era...
- pdonis 7y ago> windows was just too good - which is a pitty since from technical standpoint os/2 was better. I grumbled about this through a fair part of the 1990s. I ran Warp for a while and programmed for it as well as for Windows 3.1 and Windows NT 3.5; on the machine I had at the time there were Windows 3.1 programs that actually ran better on OS/2's compatibility layer than they did in native Windows.
- twooclock 7y agoTrue. One thing I remember is that it had shortcuts which were introduced only in win95. Unfortunately its UI was not very intuitive. Not to mention one had to pay for it when win 3.1 was widely available for free at your local pirate.
- agumonkey 7y agoThere are similar stories but with Wine. Something about OS API being better in linux, making programs run better in Wine.
- betamaxthetape 7y ago> I have to check I sill might have some cds from that era... I know that the Internet Archive (https://archive.org/ https://archive.org/) are always willing to host CD images for their software collection. They accept uploads from anyone, but Jason Scott (@textfiles on twitter and HN) is their software curator if you need assistance.
- dang 7y agoRelated from 2015: https://news.ycombinator.com/item?id=10335103 https://news.ycombinator.com/item?id=10335103
- zwieback 7y agoWhen I was in university (Fraunhofer, actually) we built a optical metrology machine (CMM) and the SW was based on OS/2 1.2, which had reliable threading and was generally rock solid compared to Windows. Linux was not a thing yet. After graduating I moved to the US and got my first job due to my OS/2 experience. The company I worked for had a Mac/PC network bridge product (TCP was not a thing on PCs yet) and we were contracted by IBM to write LAN Server for Macintosh, basically the Mac/AppleTalk server for OS/2. Good memories.
- jdmg94 7y agoas a frontend developer, I salute you sir, that shit sounds INSANE.
- zwieback 7y agoSalute right back - frontend is seen by everyone all the time. The systems stuff is in the back where nobody sees so it's often pretty ugly.
- watersb 7y agoAs someone who supported software and Mac/PC networks in the 90s, and someone who has done frontend development since 1995, I have a keen appreciation of the irony here.
- muterad_murilax 7y agoHow old is this project?
- tetraca 7y agoPretty old. I want to say I built their website back in 2008 or so (they changed the logo and color scheme but it seems to still use dokuwiki and the base templates I built out), and it was definitely going on longer than that.
- Koshkin 7y agoAccording to the whitepaper, one of the (original) goals is/was to create various "personalities", including that of Linux, OS/2 being the "base" personality. http://osfree.org/doku/en:docs:general:index http://osfree.org/doku/en:docs:general:index
- jdmg94 7y agoMost of Latin America's banks have banking systems on OS/2, maybe this project can get some traction with the spanish speaking demographic
- cesarb 7y agoThe largest and oldest bank here in Brazil migrated all of its ATMs and branch manager desktops from OS/2 to Linux a decade ago; the other large banks I know of in Brazil seem to use Windows for desktops (and probably also their ATMs). I don't know about other countries, but it wouldn't surprise me if their banks have also migrated to something other than OS/2.
- Stranger43 7y agoI think that was true pretty much everywhere. I was at the help desk for an large Scandinavian bank doing the late 00ies and they were running virtual OS/2 instances on nearly every windows pc in order to support an custom app, and still had a few front desks(or whatever the window where the bank teller sits is called) with dedicated OS/2 hardware. The biggest problem here was sourcing dot matrix printers as the software used as the front desk software only worked with a few models of no longer in production printers. A few years after i left i heard rumors of an transformation project to get rid the legacy interfaces, part of which had been on going for a decade(as an old school java application) by the time i left for greener pasture, but i would not be surprised if that project it is still not complete yet, nor would i be to hear of retail banks that never bothered with any investment to replace OS/2 based apps.
- mdaniel 7y agoFor the "show me the code" folks: https://github.com/osfree-project https://github.com/osfree-project
- GnarfGnarf 7y agoI developed for OS/2 in the 90's. OS/2 was 5 years ahead of Microsoft Windows, and offered full 32-bit processing long before Windows did. However, OS/2's strength was also its weakness. OS/2 was developed from scratch, and was not encumbered by a legacy of DOS compatibility, 16-bit applications, and drivers like Windows was. This enabled IBM to innovate radically and more quickly. The application I wrote for my client was a multi-threaded program, written paradoxically with Microsoft's Programmer Workbench, the character-based precursor to Visual Studio. However, this freedom from legacy code also meant there were few applications available for OS/2, and the only drivers were for IBM printers. OS/2 eventually disappeared in spite of its technological superiority at the time. IBM's development environment was called C-Set, and, despite being a 32-bit compiler, was inferior to Programmer's Workbench. For instance, after a compilation, if you double-clicked on an error message, it would open up the source code in a separate editor window, in a proportional typeface. You could not trigger a compilation from this window. You had to make your change, save & close, then go back to the compiler window. Awkward. There was no Resource Workshop for designing dialog boxes visually. You had to write all the statements in a text editor, and wouldn't see the appearance until compiling and running the program. This slowed down development. While debugging, I recall trying to step into the GUI part of the application code. This locked up the computer so bad we had to re-install OS/2, a tedious process requiring 22 diskettes. The IBM documentation was so inscrutable that even for ver. 2 of OS/2, we had to refer to Microsoft's ver. 1 manuals. IBM's support gave an interesting insight into OS/2's downfall. My client had an expensive OS/2 support contract with IBM. The client contacts were two guys in the PC support section. When I required technical support to answer some obscure and specialized questions about OS/2, it didn't make sense to get these guys involved, even though they were supposed to be the only official go-between with IBM. So I called IBM with the client's authorization, and impersonated one of the support techs. After a few calls I slipped and used my name. The IBM guy was livid and tore a strip of me, saying that as an independent contractor, I had no business blah blah. Here I was just trying to get a customer up & running.
- PopeDotNinja 7y agoI worked on an IT helpdesk at an insurance company for the summer in 1996. I had to support IBM PS/2 PCs that would tri-boot Windows 3.1, OS/2 Warp, and Dos. No one operating system had all of what they needed. Funny side story: They had a token ring network, and in the network room, there weren't enough physical network ports for all of the employees. Every morning someone would call the helpdesk to say their computer was couldn't access the network, I'd look at the N network cables, find one that without lights to indicate that cable was in use, unplug the inactive one, and plug in the cable of the person w/o access. It turned out on most days enough people called in sick or were on vacation that we could get everyone who needed a connection wired up :)
- Koshkin 7y agoThere was something cool and sweet about the MS-DOS command prompt simplicity (compared to UNIX) and the OS itself being single-user with a (limited) multi-tasking capability. I have always dreamed of a true 32-bit continuation of it, and OS/2 seemed to have promised to be that, but something happened along the way...
- ChicagoDave 7y agoOS/2 was tied to the PS/2 hardware and IBM had it way over priced. We had one in the office and when we needed a new card for a peripheral, we realized it was never going to cut it compared to compatibles.
- ogre_codes 7y agoOS/2 was not tied to the PS/2 hardware. Unless there was some specific version of it. It was reasonably compatible with a fairly wide range of hardware. (Roughly comparable to Linux desktop at various times)
- ChicagoDave 7y agoMaybe I'm remembering "guilt by association". IBM was pushing the PS/2 line very hard because they wanted the compatible hardware to die and they assumed everyone would still trust them. I don't remember ever trying to install OS/2 anywhere else.
- ogre_codes 7y agoThe early versions of Citrix were based on OS/2, we used it to run a FoxPro based DOS app over our WAN for quite a few years. For the time it was a pretty innovative/ performant way to run apps over low bandwidth.
- steQ 7y agoA nice reading about OS/2 histoty https://arstechnica.com/information-technology/2019/11/half-an-operating-system-the-triumph-and-tragedy-of-os2/ https://arstechnica.com/information-technology/2019/11/half-...