The Active Network
ActiveWin Anonymous | Create a User | Reviews | News | Forums | Advertise | VBA in Excel | Users Online: 0  
 

neowin.net

Amazon.com

  *  

  Microsoft Longhorn, 3GIO to change PC rules
Time: 11:13 EST/16:13 GMT | News Source: | Posted By: Alex Harris

A source close to Intel and Microsoft's plans tell us that plans are well advanced for the successor to Windows XP. But the source, who works for a third party vendor, tell us that Microsoft will make the bold – perhaps foolhardy step – of making Longhorn incompatible with all previous operating systems. And the introduction of 3GIO at the same time will also upset the third party applecart and probably end users too.

Although Longhorn does not officially debut until spring 2004, it's expected that in autumn next year, both Intel and Microsoft will give strong indications of their plans. The reason for making the OS non-backward compatible is that both Intel and Microsoft believe that only by taking this radical step can they give a huge impetus to the PC business.

Read Only Comments
Return to News
  Displaying Comments 1 through 8 of 8
  This is an archived static copy of ActiveWin.com.
#1 By 531 (208.212.83.68) at Friday, June 28, 2002 12:07:56 PM
Who's forcing you? Why is it that you think you need to upgrade to the newest and shiniest OS if the one you have works?

#2 By 61 (65.32.168.97) at Friday, June 28, 2002 12:08:43 PM
Great, another troll.

You aren't being forced to upgrade to Longhorn, you can keep your XP, your WinMe, your Win2k, whatever it is you have.

Why don't you come up with something decent to say? I'm really getting sick of you people.

#3 By 7754 (216.160.8.41) at Friday, June 28, 2002 12:58:55 PM
This article seems to imply that *everything* about this new OS would be incompatible with previous versions... all applications would have to be rewritten? You can't run Longhorn and any other Windows OS on the same network? I don't think so.... But, I can foresee new hardware that will run only Longhorn. I also doubt that Longhorn would not run on older hardware--why would MS cut themselves off from the money that would come in from those that would upgrade their OS?

#4 By 415 (199.8.71.121) at Friday, June 28, 2002 01:13:28 PM
Give it up already, it's the freakin Inquirer!

It's 95% bogus!

#5 By 2459 (24.206.97.178) at Friday, June 28, 2002 01:19:42 PM
I also don't see how Longhorn would break all compatability. Sure, on the hardware side, MS is pushing for legacy-free designs (not a bad thing), but one of NT's greatest features is its ability to maintain compatability with multiple environments by including them as subsystems. NT has maintained 16-bit Windows, DOS, POSIX, and OS/2 compatability this way.

#6 By 10 (63.21.16.190) at Friday, June 28, 2002 02:59:26 PM
I think this is actually a good idea, u still have stubborn and retarded network admins out there who still insist on running 95 and 98 machines...get with it people! Now before u all come at me with reasoning behind this, any argument is still weak, if u are a business u have to plan for this in your budget, it's just the way things work. Innovation is neccessary to move into the future.

#7 By 3339 (65.198.47.10) at Friday, June 28, 2002 04:56:45 PM
I thought that between the security initiatives, and then the addition of Cairo, and now with this Palladium, it was clear that MS was in fact doing this. I know specifically Allchin said that Cairo was coming full in Blackcomb (but with the pushbacks and Gates saying it all has to happen with Longhorn) that app compatibility would be broken in order to take advantage of the new file system, and that this may or may not happen with the interim Longhorn release that would include "parts" of the new file system. Well, that being the case, it seems like the additions to Longhorn and the make or break attitude of it combined with Palladium would produce these results.

In the very least it seems the new file system and Palladium trust requirements would either require code changes to the apps and files or some compatibility layer to support these files.

#8 By 7754 (216.160.8.41) at Friday, June 28, 2002 05:56:48 PM
Sodajerk, from all reports I've heard, the compatibility layer is already there--an NTFS "driver" for the new filesystem. In fact, it's already in use in Exchange 2000 via the Installable File System.

My bet is that most apps will definitely be compatible, and that they will only have to be tweaked or rewritten if they wish to take advantage of the new features. And, I think that some of the features of the new filesystem (the manner of indexing, etc.) will be available whether the apps take advantage of them or not.



 

  *  
  *   *
 
replica watches