What is Microsoft Office Live?

So I go away for a few days, and while I’m away, Microsoft announces Microsoft Office Live. The first few reports I read last night hinted that this was a hosted version of Microsoft Office, but that’s not what this sounds like at all:

Microsoft Office Live will provide your company with its own domain name, Web site, and e-mail accounts for free.

Additionally, Microsoft Office Live will offer you and your employees expert business management applications, such as customer, project, and document management tools, and a security-enhanced private Web site—affordably managed and maintained by Microsoft—where you can work together and share information with your employees, customers, suppliers, and contractors.

This sounds more like a hosted version of SharePoint, with lots of little extras:

A complete set of tools for managing time, tasks, projects, and company data that integrates with your existing Microsoft Office programs…

If I’m reading this right, it’s essentially an intranet for companies that aren’t big enough to have their own IT staffs.

A beta version is set to launch in early 2006.

Antispyware emerges, slowly, from the Wild West

After months of work, the Anti-Spyware Coalition has published its final Definitions and Supporting Documents. A draft of this document was posted for public comment last July. The final version is far more complete and has a useful matrix that illustrates how fuzzy the definition of some unwanted software can be. Is this just a bunch of hot air, or is the start of some real progress?

The document starts off with a pretty good summary of the problem:

Spyware has quickly evolved from an online nuisance to one of the most dire threats facing the Internet. As users struggle to maintain control over their computers, many find themselves trapped in a cyclical battle against programs that install themselves without warning, open dangerous security holes and reinstall themselves after they’ve been deleted. The worst of these programs allow online criminals to hijack users’ sensitive personal information at will. Even the most benign variants can slow computers to a crawl by wasting their processing power to provide unwanted “services.” Compounding the problem are the sophisticated ploys spyware developers use to install their programs on unsuspecting users’ computers. Spyware distributors often rely on security holes, clever cons, opaque “bundling” arrangements and other unsavory practices to spread their unwanted payload. As the threat has grown, so has the need to mount a coordinated defense against these unwanted programs and their adverse effects.

There’s also a Glossary, a document with advice for end users (“Safety Tips for Fighting Spyware”), and a process document for resolving vendor disputes.

This document is a consensus statement from a lot of companies that have economic interests in fighting spyware and not making the kind of mistakes that will get one or all of them sued into oblivion. It’s easy to say that “most folks … know spyware when they see it,” but that defense won’t hold up in court.

This document isn’t a magic bullet, and its publication isn’t going to make a single bit of difference in the average end user’s experience with this plague – at least not immediately. As Mike at TechDirt editorialized:

It’s not clear, from the description, how useful these guidelines really are. It took them five months to basically say surreptitious installs are really bad and tracking cookies aren’t quite so bad. That was pretty clear before — so it’ll be interesting to see what the various anti-spyware firms actually do with these guidelines, and if it makes any kind of a difference.

That’s right, but in my opinion it underestimates the importance of the process by which this document was produced. The coalition includes some really big names in the computing industry (Dell, Microsoft, AOL, Yahoo), all the major security companies, a strong legal component (Samuelson Law, Technology & Public Policy Clinic at Boalt Hall, UC Berkeley School of Law), and a number of public interest groups from the U.S. and Canada. It was produced after a period of public comment (neatly summarized in this PDF document.) That combination produces pretty powerful legal cover, especially when a spyware vendor tries to bully a small security software provider with threats of lawsuits.

Most of the online commentary I’ve seen so far dismisses this document as an exercise in futility. I haven’t seen any of the online commentators mention that there are at least two more steps in the process. Next up is a risk model description that defines the lines between acceptable and unacceptable behaviors along with risk and consent factors that a security provider can use to make actionable decisions when those behaviors are detected. A draft for public comment is available here, with comments open until November 27, 2005.

Up until now, the battle between sleaze merchants and the anti-spyware community has been fairly ad hoc, with the purveyors of crapware acting like roving gangs and most security companies playing the role of vigilantes. Building a solid legal framework is an important step, not just to get rid of this problem but to protect the rights of people who fight this stuff.

Building this kind of legal framework takes time, a fact that can be frustrating to people who just want to wipe out the spyware. For now, at least, you’re still responsible for your own online safety.

Q&A: Is this license legal?

Q: I bought a box full of computer stuff at an auction yesterday. It contained a (what appears to be) retail copy of XP home edition (version 2002) including product key (sticker still attached to the manual). Right now I’m running Me on a custom built pc (900mhz athlon) that did NOT come with any os discs or recovery software. I meet the system requirements for running Windows XP, but… will I be able to reformat my hd and install this operating system? Any advice would be greatly appreciated.

A: Yes, you will be able to install that operating system. The real question is whether you will be able to activate it over the Internet. If that product key has never been used, or if was last activated more than 120 days ago, then you probably will be able to activate. If the key has recently been used on another computer (one owned or controlled by the person from whom you bought the computer), then your online activation request will be rejected and you’ll have to talk to a representative on the phone and convince that person that you legitimately own the license.

I’m not a lawyer, so I can’t give you definitive advice on this. There are specific provisions in the Windows XP license agreement for transferring ownership. But in your case the practical concerns of activation are more important.

[Updated to correct error in grace period for activation. See the comments for more details.]

A new feature: Q&A

I get a lot of comments on this site every week, and lately it’s dawned on me that many of those comments are actually questions. I usually try to answer the question with a follow-up comment, if I can. But that means that the question and answer reach only a tiny percentage of the people who actually visit here.

So, beginning today, I have a new policy – and a new feature. If I find a question in the comments, I’ll answer it in a Q&A post, where everyone can see it and follow up on it.

And don’t feel like you have to leave a comment if you have a question. I’m also going to create an Ask Ed form and e-mail alias where you can send me questions. Those will appear in the sidebar along the right.

Coming up next, the first installment.

Podcast alert

I’ll be a featured guest on Ian Dixon’s Media Center Show this week. And don’t let the title fool you. Although we talk about Media Center, we also talk about Windows Vista and Office 12, so there should be something for everyone. We recorded it a couple weeks ago, and my short-term memory isn’t what it used to be, so it should be just as much of a surprise to me as it is to you.

You can listen to the show here. I did make one small mistake: I started Ed Bott’s Windows Expertise in December 2002, not 2003.

Tip of the day: Troubleshoot mysterious crashes

What does it mean when your system restarts for no apparent reason, or when you experience frequent program crashes and file corruption? The problem might not be with Windows at all. These baffling symptoms can be the result of a bad memory chip.

If you suspect you might have a failing memory module, Microsoft has a free downloadable memory test program that you can use:

The Windows Memory Diagnostic tests the Random Access Memory (RAM) on your computer for errors. The diagnostic includes a comprehensive set of memory tests. If you are experiencing problems while running Windows, you can use the diagnostic to determine whether the problems are caused by failing hardware, such as RAM or the memory system of your motherboard. Windows Memory Diagnostic is designed to be easy and fast. On most configurations, you can download the diagnostic, read the documentation, run the test and complete the first test pass in less than 30 minutes.

To run Windows Memory Diagnostic, you must reboot your computer with the disk or CD-ROM on which you installed Windows Memory Diagnostic in the drive. After the reboot, Windows Memory Diagnostic will load and its interface will appear. After loading, the first test pass will begin, using the default standard test suite, and continue until complete, unless Windows Memory Diagnostic is either paused or exited. Once the first test pass is complete, Windows Memory Diagnostic will begin a second test pass using the same settings as before. Windows Memory Diagnostic will continue to run test passes until you exit.

If you find a problem, try pulling the suspected memory chip and running with reduced memory for a short time. If the problems vanish, replace the memory.

Protect your privacy with Word documents

I’m hunkered down working on an updated version of Special Edition Using Office 2003 (this edition will be aimed specifically at people using the Student-Teacher Edition).

In the process of working on one chapter about Word, I ran across the Remove Hidden Data add-in. It’s a must-have for anyone who shares or published Word documents. It’s easy to use and very good at stripping personal and confidential information from Word documents.

The woes of external USB hard disks

Alex Scoble writes about a friend who is using an array of external drives to manage a large media collection. It sounds like he’s having some of the same problems Thomas Hawk has reported:

Additionally, iTunes would stop playing after a while for no apparent reason. Only fix for the problem that I could find was to go into Device Manager and disallow XP from turning off the USB hub subsystems, which it does to save power. So far it sounds like that has worked.

Personally, I think the decision to use SATA drives and then connect them via a USB connection was ill-advised. External USB drives are acceptable for some applications, but I’ve seen and heard of enough problems in demanding digital media applications that I recommend strongly against using them. External SATA is the only way to go.

Alex also throws in an aside:

Trust me when I say that his system definitely requires the use of high quality MP3 or lossless audio files. The crappy 128kbit MP3s you get off of Napster or the Apple iTunes store definitely won’t cut it.

Amen.

Tip of the day: Troubleshoot slow startups, part 3

One of the core principles of effective troubleshooting is that degradation in performance almost always has a proximate cause. Find that cause, reverse it, and you restore performance to its previous, acceptable level.

When trying to track down that elusive proximate cause, the most important thing you can do is ask a simple question: What changed?

When did the problem start? Did you install a new program, device, or driver? Did Windows or a third-party program update itself? Did you experience a power failure? If you can reliably say that your system was performing properly on Wednesday but began misbehaving on Thursday, you may be able to use System Restore to undo system-level changes. If that works, you can try to figure out what happened so that you can prevent it from happening again.

Two key principles to follow when troubleshooting:

  1. Stay alert. If you notice your computer slowing down or behaving in an out-of-the-ordinary way, investigate the cause as soon as possible. Don’t install any additional software or make any system changes until you’ve figured out the problem.
  2. Don’t automatically assume that the first or most obvious change you think of is the proximate cause of your problem. If you installed a patch via Windows Update, that may or may not be the cause of your current problems.

In the next two installments, I’ll explain how to use diagnostic tools to zero in on the precise problem.