Linked by Thom Holwerda on Mon 2nd Feb 2009 21:23 UTC
Thread beginning with comment 346915
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2005-08-02
At the U where I work, my division was selected shortly after Vista rolled out to test it. This is due to the fact that we have our own dedicated IT department and can give campus IT an idea of what they will face when they roll out software system wide. (For example, we were the guinea pigs for Office 2007.)
We discovered that we cannot run Vista in house because it doesn't work with several mission critical programs we use. We also discovered that the State Higher Education System cannot switch to Vista because it doesn't work with a System Wide mission critical program (a legacy program so old it dates from before the days of standard keyboard commands). (As an aside, this program is roundly hated by anybody who has to use it, but only now, because the vendor can't make it work with Vista is the vendor working on an upgrade.)
Because of those programs, we must stick with XP.