Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
IBM Operating Systems

ArcaOS 5.1.0 (OEM OS/2 Warp Operating System) Now Available (arcanoae.com) 46

Slashdot reader martiniturbide writes: ArcaOS 5.1.0 is an OEM distribution of IBM's discontinued OS/2 Warp operating system. This new version of ArcaOS offers UEFI compatibility allowing it to run in modern x86 hardware and also includes the ability to install to GPT-based disk layouts.

At OS2World the OS/2 community has been called upon to report supported hardware, open source any OS/2 software, make public as much OS/2 documentation as possible and post the important platform links. OS2World insists that open source has helped OS/2 in the past years and it is time to look under the hood to try to clone internal components like Control Program, Presentation Manager, SOM and Workplace Shell.

This discussion has been archived. No new comments can be posted.

ArcaOS 5.1.0 (OEM OS/2 Warp Operating System) Now Available

Comments Filter:
  • by iAmWaySmarterThanYou ( 10095012 ) on Saturday September 02, 2023 @04:53PM (#63817724)

    It was very pretty and looked and felt a lot better than the Windows of the time but my hardware was very low end so it took about 30 minutes to boot up but it did run ok after that.

    It's too bad IBM screwed up the OS wars so badly and so gravely misunderstood the PC market. OS/2 was waaaaay nicer than Windows even with a 30 minute boot up time on my garbage system.

    • by demon driver ( 1046738 ) on Saturday September 02, 2023 @05:21PM (#63817780) Journal

      It's too bad IBM screwed up the OS wars so badly and so gravely misunderstood the PC market. OS/2 was waaaaay nicer than Windows even with a 30 minute boot up time on my garbage system

      Yes. And the Workplace Shell continues to be the very best – by at least one order of magnitude – OS GUI I've seen until today in terms of ergonomics, functionality, configurability and extendability, all those nice Linux Desktop Environments included. Many of which, by the way, already are so much better than Windows up to and including Windows 11, the only advantage of which is that, for a change, it does look quite nice.

      Now I would agree that IBM's being unaccustomed to marketing directed to tiny little personal computer end users didn't help, but it wasn't just that. As part of a competition case against Microsoft (that Microsoft lost), testimony came up that Microsoft had blackmailed IBM, effectively forcing IBM's software division to stop marketing OS/2 to end users, lest Microsoft would stop selling Windows to IBM's hardware division. Of course it's hard to know for sure, but as that was before OS/2 became able to really challenge Windows, it might have been the crucial nail in the coffin.

    • yep I was still a dev back in those days and we thought it was awesome, BUT, the resource usage of it made us realise pretty quickly it was destined for niche or death, we spent a couple of grand on upgrading each workstation just to make it usable and that is not something the market was ever going to want to do.
      • by dryeo ( 100693 )

        I know, ran it on a 386/33 with 4 MB's of ram. Currently with SeaMonkey, Thunderbird and a Chrome based browser running,

        total physical memory: 12,169 MB
        accessible to system: 3,241 MB
        additional (PAE) memory: 8,928 MB

        resident memory: 180 MB
        available virtual memory: 1,133 MB

        vailable process memory:
        Private low memory: 352 MB
        Private high memory: 1,572 MB
        Shared low memory: 244 MB
        Shared high memory: 287 MB

        It's the shared low memory that causes the system to become unstable when it goes below 10 MB or so

      • I too was an OS/2 dev back in the day. Yes it was sluggish but that same code on modern hardware would scream. Too bad MS sabotaged it in favor of Windows. MS instead bet its future on NT. We know how that went.
    • by circusnews ( 618726 ) <steven@s[ ]ensantos.com ['tev' in gap]> on Saturday September 02, 2023 @06:15PM (#63817930) Homepage

      The killer feature for OS2 was the experimental API for off-loading tasks to a server. It was possible to have a beefy OS2 or IBM server and allow for much lower-powered workstations to hand discrete compute jobs off to the server and then have the results seamlessly handed back to the client. I had a client that used this for a particular database. This allowed the OS2 boxes to run the application at some 20x the speed of the identical boxes running Windows.

      The same client has a testing version of Lotus circa 1992 that used this API and was amazing for its time. It was also possible to use this to have the same spreadsheet worked on by up to 20 people at the same time. For the time, this was mind-blowing stuff.

      • The killer feature for OS2 was the experimental API for off-loading tasks to a server. It was possible to have a beefy OS2 or IBM server and allow for much lower-powered workstations to hand discrete compute jobs off to the server and then have the results seamlessly handed back to the client
         
        I mean, you just described DCOM, which Windows had since NT4/Win95

        • by dryeo ( 100693 )

          The killer feature for OS2 was the experimental API for off-loading tasks to a server. It was possible to have a beefy OS2 or IBM server and allow for much lower-powered workstations to hand discrete compute jobs off to the server and then have the results seamlessly handed back to the client

          I mean, you just described DCOM, which Windows had since NT4/Win95

          And was a rip off from distributed SOM, just like COM was a bad rip off of SOM.
          The Windows 95 interface was just a bad copy of the WPS, just like the Win 3.x (NT 3.x) interface was a bad copy of the OS/2 1.x interface. Even Internet Explorer go its idea of being a DLL that any application could use from OS/2's Web Explorer, mostly a big DLL so any program could use it to display HTML. released as part of the IAK (Internet Access Kit) included with Warp v3 in 1994.

          • Cool story, bro. Irrelevant to the current topic being discussed.

            You do know that Microsoft created OS/2 with IBM, right? How much of that "copied" stuff was just less about borrowing and more about using their developed IP from the OS/2 join venture?

            • by dryeo ( 100693 )

              Seems that SOM came with OS/2 V2, after the divorce and was solely an IBM thing, though through licensing agreements MS likely had rights to it.
              Things like the OS/2 v1.x graphical interface likely were mostly developed by MS, still the OS/2 Progman and Fileman equivalents were much better then the Win 3.x versions, free floating windows and such, forget the proper terms.

        • Yes, but for the time, it actually worked on OS2, where it didn't work on the Windows boxes of the time.

  • by demon driver ( 1046738 ) on Saturday September 02, 2023 @05:29PM (#63817804) Journal

    ... to get the Workplace Shell back, on an up-to-date operating system with lavish software support (which leaves about three, of which OS/2-eComStation-ArcaOS isn't one). No other OS UI I've seen over the last 40 years comes even close.

  • OS/2 Was awesome! (Score:3, Insightful)

    by Marthis ( 1949724 ) on Saturday September 02, 2023 @06:21PM (#63817940)
    Esp for running multi-line BBS w/ FIDONet...Maximus BBS software was the bomb back then!
  • by jonwil ( 467024 ) on Saturday September 02, 2023 @06:24PM (#63817954)

    Maybe someone should start a project similar to the ReactOS Windows clone project but aiming to clone OS/2.

    • by dryeo ( 100693 ) on Saturday September 02, 2023 @08:28PM (#63818122)

      The ReactOS people originally wanted to support OS/2 as the NT kernel was capable, unluckily no OS/2 developers were interested. The OS/2 development environment was much like a herd of cats.
      At this point the problem would be the remaining 16 bit code in OS/2, just won't work in a 64 bit environment so some low level things would have to be rewritten and there's few capable developers and those aren't interested.
      The real shame is that the OS/2 PPC code seems to have been lost, at one time it was hoped that it would be open sourced. It was pure 32 bit C (and perhaps some C++) code written to be portable.

  • Applications is where its at. Operating systems don't make any sense.

    • by dryeo ( 100693 )

      Yep, stick in the floppy and turn the machine on and your application runs until you turn the machine off and stick in a different floppy and repeat the procedure.

      • Arguably the better user experience. Assuming every computer is compatible and has no extra hardware or unusual extensions.

        • by dryeo ( 100693 )

          In a way, it is how I first used a computer, an Apple //. Still I came to a point where I found myself wishing to run more then one application at a time, even if only 2 editors or a calculator. Later I wanted to have something running in the background such as terminator downloading a file while I did something else, which was about the time I discovered OS/2. With only 4MB of ram on a 386, I first used it as a DOS replacement and it was wonderful having multiple DOS or Win 3.1 sessions all multitasking. W

          • I went the DESQview route. I was able to host my small BBS and continue to use my 486 for general programming and word processing without a hitch. Gaming was a little bit beyond DESQview's capabilities in most but all cases.

    • Developers developers developers...
  • How is it that on a 486/25 16MB I could have Word in one window, be playing Wing Commander in another window, and format a floppy disk in another window, and move the windows, without a single stutter?

    But now with a Zen2/3400 64GB machine with 8 real cores and Linux 6 I can copy a file to a USB drive from shell and dragging a window locks up refresh for 10-20 seconds pretty much every time?

    OS/2 did something right that Linux doesn't.

    BeOS did it right on PPC too.

    • by dryeo ( 100693 )

      Part of it was being tuned as a client rather then a server. By default OS/2 would give the foreground application a slight priority and IO boost making it feel much more responsive.

    • Part of it is that USB really sucks on the host side. Also, Linux inherited a lot of Unix baggage that make asynchronous file operation cumbersome and rarely implemented correctly. On the plus side, your Linux box likely has 400-1000 tasks running without you even realizing how much crap it has been doing behind the scenes.

  • If the OS/2 Warp thing was something IBM was setting up for a short term fail, to get IBM out from under the antitrust thumb. I think they were hoping for Microsoft to get crushed by the Feds so that they (IBM) were the only ones left standing.
    • Re: (Score:3, Insightful)

      by Anonymous Coward
      it was simply Arrogance, At the time IBM didn't understand the PC market and also thought they couldn't possibly lose as they had been so used to coming out on top the idea that they would fail while their upstart contractor MS would pound them was just unthinkable.
  • by Saffaya ( 702234 ) on Sunday September 03, 2023 @01:18AM (#63818444)

    "offers UEFI compatibility allowing it to run in modern x86 hardware and also includes the ability to install to GPT-based disk layouts"
    Now, can they do the same for Windows 2000?
    I'd be really interested in buying that.

  • They want 140 USD for a system that has no software and no hardware support. Wow, this would sell like sand in desert.
  • We wrote the sample code for a database that IBM was going to release. Even the very alpha versions of the dev environment were stable like nothing else.

Life is a whim of several billion cells to be you for a while.

Working...