Why are 74% of business computers still running XP

Page 2 of 7 FirstFirst 1234 ... LastLast

  1. Posts : 123
    WinXP / Win 7 / Win 8.1 64bit Dual Boot
       #10

    IMHO and experience its all about "The Money". Most small to medium size companies don't have the extra cash to replace XP at this point in time.
      My Computer


  2. Posts : 1,487
    Windows 7 x64 / Same
       #11

    JonM33 said:
    Love Windows 7 said:
    We reported yesterday that Microsoft had extended downgrade rights for Windows XP from Windows 7, but the reason seems to stem from the fact that a reported 74% of work PCs are still running Windows XP.

    This seems odd given that it was also recently reported that 50% of business either have or are ready to upgrade to Windows 7. So what’s the anomaly and what’s causing the problem?

    More info here: Why are 74% of business computers still running XP? | Windows 7 News
    Applications. There are a lot of businesses still using Windows XP because of application compatibility. It's what happens with poor programming.
    Not true. Older software often doesn't work on newer systems because the newer systems have dropped support for older software/technologies.

    To "chalk it up" to "poor programming" is asinine.
      My Computer


  3. Posts : 565
    Windows 7 Home Premium x64
       #12

    Win7User512 said:
    Not true. Older software often doesn't work on newer systems because the newer systems have dropped support for older software/technologies.

    To "chalk it up" to "poor programming" is asinine.
    I speak from experience of working for companies that would not upgrade to Windows 7 because of JUST that. Call it asinine, but they were the ones stuck with the incompatible software.

    Poor programming is for the in-house software that is developed. These people program the software to require local Administrators group membership of all things.
      My Computer


  4. Posts : 1,487
    Windows 7 x64 / Same
       #13

    JonM33 said:
    Win7User512 said:
    Not true. Older software often doesn't work on newer systems because the newer systems have dropped support for older software/technologies.

    To "chalk it up" to "poor programming" is asinine.
    I speak from experience of working for companies that would not upgrade to Windows 7 because of JUST that. Call it asinine, but they were the ones stuck with the incompatible software.

    Poor programming is for the in-house software that is developed. These people program the software to require local Administrators group membership of all things.
    You speak from limited experience. To base your blanket conclusion on "poor programming" is absurd.

    Just because the in-house software you are familiar with was crap doesn't mean everyone's is.

    That is like saying an ASP.NET 1.1 is not compatible with a hypothetical IIS 10.0 is due to "poor programming" when it is really due to change in technology.

    Why do you imagine Windows 9.x apps don't run or run poorly on 7?

    Hint: Microsoft has changed a lot of the code and design models in between.
      My Computer


  5. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #14

    hoganth said:
    IMHO and experience its all about "The Money". Most small to medium size companies don't have the extra cash to replace XP at this point in time.
    Bingo and that goes for local and state governments, too.
      My Computer


  6. Posts : 1,487
    Windows 7 x64 / Same
       #15

    CarlTR6 said:
    hoganth said:
    IMHO and experience its all about "The Money". Most small to medium size companies don't have the extra cash to replace XP at this point in time.
    Bingo and that goes for local and state governments, too.
    I think another component to that is need. Many systems run fine as they are.

    Too many people think that there is only one reason, when it is a multitude. Some more important than others to different people.
      My Computer


  7. Posts : 11,990
    Windows 7 Ultimate 32 bit
       #16

    In the business world, need is equated to money. "Yes, we need to upgrade; but we can make do. We don't have the money to upgrade 25 computers and six of them would have to be replaced to run Win 7." Or variations of this.
      My Computer


  8. Posts : 351
    Windows 7 x64 (RTM via MSDN)
       #17

    Win7User512 said:
    JonM33 said:
    Win7User512 said:
    Not true. Older software often doesn't work on newer systems because the newer systems have dropped support for older software/technologies.

    To "chalk it up" to "poor programming" is asinine.
    I speak from experience of working for companies that would not upgrade to Windows 7 because of JUST that. Call it asinine, but they were the ones stuck with the incompatible software.

    Poor programming is for the in-house software that is developed. These people program the software to require local Administrators group membership of all things.
    You speak from limited experience. To base your blanket conclusion on "poor programming" is absurd.

    Just because the in-house software you are familiar with was crap doesn't mean everyone's is.

    That is like saying an ASP.NET 1.1 is not compatible with a hypothetical IIS 10.0 is due to "poor programming" when it is really due to change in technology.

    Why do you imagine Windows 9.x apps don't run or run poorly on 7?

    Hint: Microsoft has changed a lot of the code and design models in between.
    The reason many Win9X programs don't run on Win7 x64 is simply that they contain 16-bit code and/or made use of assembler code for perfomance. However, I have a few Win 3.1 programs I wrote that run on Win 7 x32 just fine (I can use Win7 x64, but need XP Mode). By following standard coding practices, they work. They are simple programs written in VB 3, but the point is, I followed the proper API's available at the time, and MS is quite adept at making things pretty backwards compatible. JonM33 is correct in that programs written properly to the API have a very good chance of being compatible.

    However, going outside the standard API, or using nifty programming tricks to eek out that last Mhz will often break that backwards compatiblity. That's not necessarily a bad thing, as better performance is good, but it does cause heartache and teeth-nashing later.

    PhreePhly
    Last edited by PhreePhly; 13 Jul 2010 at 19:14. Reason: spelling
      My Computer


  9. Posts : 34
    Windows 7 Home Premium x64
       #18

    We are still an XP Pro company, with a couple thousand employees. I can tell you, for our company, the main reason is support of lagacy information systems. We use some very antiquated software, I think our gas measurement techs still run some DOS-based stuff actually.

    It is not a matter of money for most large companies, truly.

    Believe it or not, our IT group is finally rolling out IE8 later this month.
    Last edited by s3v3n us3r; 13 Jul 2010 at 19:21. Reason: additional comment
      My Computer


  10. Posts : 1,487
    Windows 7 x64 / Same
       #19

    PhreePhly said:
    Win7User512 said:
    JonM33 said:

    I speak from experience of working for companies that would not upgrade to Windows 7 because of JUST that. Call it asinine, but they were the ones stuck with the incompatible software.

    Poor programming is for the in-house software that is developed. These people program the software to require local Administrators group membership of all things.
    You speak from limited experience. To base your blanket conclusion on "poor programming" is absurd.

    Just because the in-house software you are familiar with was crap doesn't mean everyone's is.

    That is like saying an ASP.NET 1.1 is not compatible with a hypothetical IIS 10.0 is due to "poor programming" when it is really due to change in technology.

    Why do you imagine Windows 9.x apps don't run or run poorly on 7?

    Hint: Microsoft has changed a lot of the code and design models in between.
    The reason many Win9X programs don't run on Win7 x64 is simply that they contain 16-bit code and/or made use of assembler code for perfomance. However, I have a few Win 3.1 programs I wrote that run on Win 7 x32 just fine (I can use Win7 x64, but need XP Mode). By following standard coding practices, they work. They are simple programs written in VB 3, but the point is, I followed the proper API's available at the time, and MS is quite adept at making things pretty backwards compatible. JonM33 is correct in that programs written properly to the API have a very good chance of being compatible.

    However, going outside the standard API, or using nifty programming tricks to eek out that last Mhz will often break that backwards compatiblity. That's not necessarily a bad thing, as better performance is good, but it does cause heartache and teeth-nashing later.

    PhreePhly
    Actually you confirmed my argument.

    At the same time, when technology changes some stuff simply doesn't work, despite best practices.

    Coding in best practices gets you the longest shelflife of software. BUT when Windows 20 comes around and they say "hey, no support for Windows 7 API" then it must be redone.
      My Computer


 
Page 2 of 7 FirstFirst 1234 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 15:57.
Find Us