Remember what Microsoft did to OS/2? They changed Windows 3.1 to windows 3.11 and broke the ability for OS/2 to run windows 3.11. They did this in a manner that simply changed a few things so it would no longer act as a Hosted virtual operating system under the virtual dos mode of OS/2. No other reason to change anything other than to make it non functional under Warp. They can and will do the same. They don't even need to change much in the operating system. They can do so with a simple update to.net or office and achieve the same results.
OS/2 could have supported all the Win 32 stuff in Windows 95/98/me as well, but IBM knuckled under to Microsoft and it never got published (code was available).
One other area of concern is how will third party software produces react to a support call when the client tells them they are running under lindows rather than Windows? In the past with OS/2, when you had an issue with a third party package, you got the standard rutine "We don't support our package under anything but windows products".
In other words, if the support staff of the third party software vendors can take an easy way out, they will...
There is something to be said about an end user getting help with a windows problem from a neighbour who is familiar with windows. However that same help resource is currently not available for Lindows......
I wish them (and anyone who has the balls to take on Microsoft and the general industry....), however IBM could not do it in 1995.....
And in my opinion OS/2 was far ahead technically than either the current Linux or Windows.... Even today there are features in Warp that are not yet realised in either Linux or windows....
OS/2 was by far the only operating system that came close to rocking the windows boat.....
Slashdot Mirror
Remember what Microsoft did to OS/2? They changed Windows 3.1 to windows 3.11 and broke the ability for OS/2 to run windows 3.11. They did this in a manner that simply changed a few things so it would no longer act as a Hosted virtual operating system under the virtual dos mode of OS/2. No other reason to change anything other than to make it non functional under Warp. They can and will do the same. They don't even need to change much in the operating system. They can do so with a simple update to .net or office and achieve the same results.
OS/2 could have supported all the Win 32 stuff in Windows 95/98/me as well, but IBM knuckled under to Microsoft and it never got published (code was available).
One other area of concern is how will third party software produces react to a support call when the client tells them they are running under lindows rather than Windows? In the past with OS/2, when you had an issue with a third party package, you got the standard rutine "We don't support our package under anything but windows products".
In other words, if the support staff of the third party software vendors can take an easy way out, they will...
There is something to be said about an end user getting help with a windows problem from a neighbour who is familiar with windows. However that same help resource is currently not available for Lindows......
I wish them (and anyone who has the balls to take on Microsoft and the general industry....), however IBM could not do it in 1995.....
And in my opinion OS/2 was far ahead technically than either the current Linux or Windows.... Even today there are features in Warp that are not yet realised in either Linux or windows....
OS/2 was by far the only operating system that came close to rocking the windows boat.....