Slashdot Mirror
Wait For Windows 7 SP1, Support Firm Warns Users
CWmike writes "Users should wait for Microsoft to work out the bugs in Windows 7 before jumping on the new OS, computer support company Rescuecom said on Friday. 'From the calls we're getting, as well as our own experience in the past with all Microsoft's operating systems, we're recommending that people stick with their time-tested OS and wait for the dust to settle,' said Josh Kaplan, president of Rescuecom. Citing a litany of reasons, ranging from the risk of losing data during an upgrade to tough economic times, Kaplan urged Windows users to put off upgrading to Windows 7 or buying a new PC with the operating system pre-installed. 'There are some compelling reasons for both businesses and home users to move to Windows 7,' Kaplan said, 'so we're saying "just wait for a bit."' Upgrading an existing machine — whether it's running the eight-year-old Windows XP or the much newer Vista — is particularly risky, he added, especially if users haven't taken time to make a full backup before they migrate their machines. Some users have found that out first hand. Among the top subjects on Microsoft's support forum is one that has put some PCs into an endless reboot loop when their owners tried to upgrade from Vista to Windows 7. Microsoft has not yet come up with a solution that works for all the users who have reported the problem, sparking frustration."
I say get Windows 7 now, if you have a reason. If you have a new computer get it with 7 for sure. Get it for an old computer if there's a reason you want it (like DirectX 10/11 support or something) and your computer is reasonable (at least a dual core with 2GB RAM).
We have been deploying it here at work and it works great. It is a solid and fast OS. App compatibility is extremely good, even with our squirelly engineering apps.
But then seriously, how is this guy's story "news for nerds" any more than my anecdote? I would think nerds would be capable enough of doing testing to determine if 7 is right for their environment and then deploying it if appropriate.
What's new? This is always the recommendation. It has never not been the recommendation to jump on a Windows product as soon as it's been released by a support firm. Is it just posted here to give Slashdot readers a space to vent their Windows 7 thoughts on?
Beware: In C++, your friends can see your privates!
While no initial release is perfect (and nor is any currently deployed system), this seems like FUD to me. Win7 is small enough of a difference from Vista (and that's a good thing) that there's relatively few surprises switching to it. There's no major driver model change and real world app compatibility testing has been in progress for almost a year now.
I hear this every time a new version of Windows comes out. While it may be good policy for businesses to buy time to test the OS, develop training materials, and fix any application problems, it isn't as big of a deal for consumers, and articles like this come off as anti-Microsoft FUD.
There is always risk in upgrading to a new operating system, especially if you don't have much experience with it. That shouldn't stop you from waiting for the service pack.
My Sysadmin Blog
These Mac ads remind me of a politician who has nothing good to say about his own policies and platform, so he spends his time badmouthing the other candidates. I make it a point never to vote for those kinds of politicians.
Actually, Vista is on SP2 currently... so you should be calling Windows 7 "Vista SP3".
Do what thou wilt shall be the whole of the Law
AUMHA Discussion: Should I Use a Registry Cleaner?
[excerpt]
Mark Russinovich wrote:
No, even if the registry was massively bloated there would be little
impact on the performance of anything other than exhaustive
searches (ed. of the registry itself).
On Win2K Terminal Server systems, however, there is a limit on the
total amount of Registry data that can be loaded and so large
profile hives can limit the number of users that can be logged on
simultaneously.
I haven't and never will implement a Registry cleaner since
it's of little practical use on anything other than Win2K
terminal servers and developing one that's both safe and
effective requires a huge amount of application-specific
knowledge.
[/excerpt]
It's a very interesting read, that's just one of the many security
and computer experts that chimed in on the issue.Overall, the
consensus is No, you should not use a registry cleaner. Period.
A few end-users howl contrary.
I'll go with the expert's advice that aren't trying to sell or promote crapware.