I remember reading something, somewhere, that things like colors took up too much space in the runtime, and in order to keep the download small, they were jettisoned.
Loading user information from Channel 9
Something went wrong getting user information from Channel 9
Loading user information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Last month, I was working on an Excel file that contains about 0.7 million VLOOKUP() formulas over 4000 and 48000 rows ranges. Opening on my machine takes over 2 hours with 100% CPU usage and any editing was painfully slow. Such operation can easily suck up the power of your server. (In the end I rewrite the file to use VBA instead and the calculation completed within 5 seconds.)
Make sure that calculation options is set to manual, if you are making changes to data related to vlookups. I can't underestimate the importance of this.
@Bass: I wish someone would figure out how to make a trackpad work right in Windows. Apple has a great trackpad, but it just doesn't work on a Mac running Windows.
I'm not sure what it is, but there seems to be something fundamentally wrong with Windows, in regards to trackpads.
RDP seems to work well enough. Although, I haven't tried parallels, I would image that it wouldn't mess with native experience.
@00010101: Other people's money.
I kind of figured as much.
What I was trying to convey, was the idea that people didn't switch their OEM solution from XP to an embedded version of Windows due to the wide variety of offerings.
It's hard enough getting technical support for strange compatibility issues with normal windows, let alone some strange mishmash of windows components hobbled together to form some new embedded variety of Windows.
I think that Microsoft created too much confusion in the embedded world of Windows. How many variants of embedded windows have been produced and retired in the XP timeframe? My guess is quite a few.