Microsoft settles IBM antitrust claims

TalkBack 16 of 153:

Next »

« Previous

• Thread View
• Flat View

What? Have you heard of a company called Borland or Lotus?

Both of these companies had embraced OS/2 and had development tools available from early including Java Beans from Lotus and an entire suite of products from Borland including the first 32-bit compliers in Pascal, Turbo Pascal, Pascal with OOP, Turbo C?C++, Borland C/C++, Delphi, Paradox, The Borland RAD suite, etc,.

IBM itself made the same suite it used in-house available to Warp programmers including IBM Visual Object C/C++ (or whatever it was called) and other visual object compilers and every Warp 3 came with REXX and NetREXX was a free download. IBM made many SDK's available as did Lotus Dev. Corp. Lotus Dominos on Warp was much faster than Dominos in WinNT.

I used the Borland suite and simultaneously developed (on OS/2) for OS/2, DOS, Win16 and Win32. How you could not do it amazes me.

When I got my Warp 3 I had the IBM Works suite, Lotus Organiser, Lotus Notes, Lotus Java Beans, Borland Turbo pascal with OOP for OS/2 (multi-platform compilation), Borland C/C++ for OS/2 (multi-platform compilation) alonf with every Win app that I had before on WFW3.11 including FoxPro, DBaseIV, Borland Turbo C/C++ (DOS, Win16, Win32), WordStar, WordPerfect, MSOffice 6.0 and many others.

I stopped using the native Win apps since I was using OS/2 to extend my native OS/2 app through OOP and increase the functionality and usefullness of my DOS apps through named pipes and semaphores, etc.

Support for OS/2 never started to wane until the MS hype (i.e., lies) about Win95 and its capabilities (still being promised in Longhorn).

[quote]IBM was trying to impose too many restrictions on MS basically trying to squash NT[/quote]

IBM was trying to get MS to honour their agreement to do what IBM paid them to do and what was stipuloated in their collaborative agreement and the Win-OS/2 license agreement.

IBM was also trying to get a true multitasking OS to market as they promised the customer wher MS was screwing with OS/2 while developing Win3.x for profit and WinNT in the background.

IBM wasn't trying to squash WinNT. WinNT was to be OS/2 3.0 that IBM paid MS to develop but MS instead started to develop WinNT with the IBM funds and refused to develop OS/2 3.0.

So IBM took control of OS/2 and created what MS was paid to creat in the first place. In the mean time, since IBM had a license to use Win-OS/2 (32-bit) in OS/2, MS decided to re-write a new Win32 sub-system that IBM had no license for and use it in the next Windows, Win95 and WinNT4.0.

The problem now was that WinNT 3.x took a different path (closer to the older incarnations of OS/2) than Win9x (closer to classic Windows/DOS) and the two platforms had incompatability issues with running apps. MS killed WinNT all by themselves without help from IBM who only wanted MS to do what they were commissioned and paid to do.

OS/2 never belonged to MS. It belonged to IBM but IBM paid MS to do the development. MS took the ideas IBM brought to the table and put them in a whole new product (WinNT) designe dspecifically to compete with the people who commissioned them to make OS/2.

MS was the one trying to squash OS/2, not the other way around. IBM lived up to their end of the bargain and aided in the development of Win3.x, HPFS and NTFS.

Posted by: The King's Servant   Posted on: 07/01/05 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Virtualization: Architectural Considerations And Other Evaluation Criteria VMware Of the many approaches to x86 systems virtualization available in the ... Download Now
• The True Costs of Virtual Server Solutions VMware In an economic environment that is repeatedly heralding the message "do ... Download Now
• Key Strategies for Federal Agencies - Safe and Cost Effective Migration for Legacy Hardware GovConnection The federal government has mandated that federal agencies reduce energy ... Download Now