Windows Media Player 11 for XP due by end of June

What’s missing from Windows Media Player 11?

CNET is reporting that Microsoft plans to release an updated version of Windows Media Player for Windows XP within the next couple of months. It’s the same code, more or less, that will go into Windows Vista when it’s released at the end of this year:

Microsoft is on track to release a Windows XP version of Windows Media Player 11 before the end of June, the company confirmed last week.

Microsoft has been uncharacteristically tight-lipped about the XP incarnation. The company briefly demonstrated it at the Consumer Electronics Show in January but has said little since. Microsoft has said the XP version won’t have all the features of its Vista sibling, but the company won’t say which features will be excluded. The company also has yet to offer a public test version of the software.

What’s missing? A Microsoft document that was briefly available for public download last week has some answers – and raises a few new questions:

When running on Windows XP, the following Windows Media Player 11 features are not available:

  • Playing content (including DRM) on your PC from another PC or device
  • Viewing content from the Vista Media library on other PCs or digital devices, such as Tivo
  • Playback of High Value video content
  • Shell integration with Windows Media Player
  • Content Indexer change notification to sync My Music and WMP library
  • DVD Fullscreen playback enhancements
  • DRM Transcode
  • High quality video streaming over home networks
  • Media foundation for playback

A lot of the missing features are related to streaming DRM-protected content from a PC with Media Center features to other devices, especially modern extenders like the Xbox 360. Based on screen shots I’ve seen, the XP version of WMP 11 will have the much-improved interface of its Vista sibling. Will it be able to handle extra-large media libraries as quickly as the Vista version? Stay tuned.

I’d rather be right than first

Over the weekend, Dwight Silverman paid me an enormous compliment, placing this site in his list of six favorite tech sites. In his write-up, he said, “The only thing wrong with Ed Bott’s Windows Expertise site is that he doesn’t post often enough.”

I plead guilty, but with an explanation. I try very hard to avoid posting anything here until I’m confident it’s right. That means I don’t idly pass along links to the latest hot news, because more often than not that news turns out to be, well, wrong. And I sometimes take a while to digest the news, because I think people who visit this site expect an in-depth analysis, not just a snap judgment.

Two cases in point:

Over the past few days, I could have picked up and passed along any of several seemingly authoritative reports from various Windows rumor sites that a new interim build of Windows Vista was going to be released to beta testers today. (No links necessary. If you follow this stuff, you already know who I’m talking about.) One site went so far as to post the exact time when build 5365 was due to be released – 1:00 PM EST – along with a list of the changes included in it.

They were wrong. In fact, I think they were pulling this stuff out of their … Sorry, let me start over. I think they were just guessing, and if a new build had appeared today within a few hours of their prediction, they could find a good excuse for the discrepancy in timing and claim a scoop. Instead, they just look silly. As do the many sites that reprinted that bogus prediction. If I had followed the herd and posted a link to one of those sites, I would have been guilty of passing along suspect information without checking it out, and you would have had every right to drop your estimation of how trustworthy and reliable I am. Glad I passed.

Now, I am reasonably certain that a new build of Windows Vista will be available for technical beta testers in the next couple of days. In fact, I’ve been cleaning out partitions and rearranging data files for the past three days in preparation for that new build. I’ll let you know when it’s here, and I’ll pass along some screen shots.

Example #2: Remember that Windows Vista Product Guide that briefly appeared on a Microsoft-affiliated website last week before being unceremoniously yanked? I was able to download it in the brief window during which it was available. Over the weekend, I picked some interesting details out of the product matrix at the front of the document, details I haven’t seen published anywhere else.

You can read the first of two parts summarizing my findings at Ed Bott’s Microsoft Report over at ZDNet. (I should have the second part ready tomorrow.)

And as soon as I can whip the HTML into shape, I’ll have a few tables summarizing the differences between different Windows versions, which will be posted right here.

Sometimes the technical press and blogosphere have a short attention span. They swarm over a story when it’s hot, and then move on to the next hot topic within a few hours or days. Sometimes it pays to wait a week or two and see what the real story is.

Signs of cluefulness at Dell

If you’ve read this site for the past year or two, you know I’m not a big fan of Dell. I’ve had too many bad experiences (documented here, here, here, and here, with follow-ups here, here, here, and here).

So I wasn’t surprised last month when I had major problems getting a broken Dell laptop repaired. The motherboard graphics had failed, and the warranty specified that it was eligible for next-day on-site service. I’ll spare you the gory details – let’s just say that it took 19 phone calls and 27 days for a repair person to arrive at my office.

Ho-hum. More of the same, right?

So imagine my surprise when I received a call last week from Dell headquarters. This executive had reviewed my file and was calling to (a) apologize profusely and (b) find out exactly what happened so they could fix the broken process.

We exchanged a few e-mails, and I sent along notes from some of my previous horrifying support experiences. A day or two later I received a note from this executive’s assistant, offering me a fairly substantial no-strings-attached coupon as a “gesture to make amends.”

Now, Dell didn’t track me down because I’ve posted my complaints on this site. In this case, the issue that led to the call was one I hadn’t written about at all, and this executive didn’t seem to know anything about me except that I was an unhappy Dell customer.

This is a first for me, and it’s enough to make me take a fresh look at Dell. I’m still cautious, and it will take years for the company to earn back the trust they’ve lost. But at least they’ve taken a first step.

I’d be very interested to hear from anyone else who has had an unexpectedly good experience with Dell lately.

Yet another silly set of Windows tweaks

Dwight Silverman takes a closer look at some XP tweaks that made it to the front page of Digg and says, Don’t Digg that XP tweak. His conclusion bears repeating:

It’s not a great idea to apply random tweaks you spot on the Web to your system, even if you spot them on a high-profile tech site such as Digg. Get a second opinion by doing some searching, and do some research at sites such as XP Myths.

Dwight’s absolutely right. Many so-called Windows tweak sites are filled with misinformation. (See the prefetch myth for a prominent example.) I’m certain the people who pass this stuff along are well-meaning, but they don’t understand the internals of memory management, and so they’re easily misled. They’re convinced that there’s some secret group of Registry settings that can magically improve performance (one Microsoft engineer called this the “make rocket go now” urban legend).

In particular, Dwight wonders whether it’s OK to enable a Registry change to the DisablePagingExecutive setting. Here’s my take:

For the average person, making a chance to the DisablePagingExecutive setting is like trying to perform a lobotomy on yourself with a pair of knitting needles.

What this setting does is to prevent drivers and kernel code from being written to the pagefile. Now, think this through logically. If you’re running so many programs that you exceed the amount of physical memory in your system and you start up a new program or process, the operating system has to move some program code and data out of memory and into the pagefile to make room for the bits you just requested. You could let the OS make intelligent choices about which bits to swap. Or you could constrain it by saying, “Don’t ever swap this type of code out.” If you enable this tweak, you limit the flexibility of the OS and force it to throw something else out, which in this case is one of the other programs you’re running. That increases the delay you’ll encounter when you switch back to the other app.

This setting is provided for use in servers, where administrators run a limited and well-known set of applications and need to debug or tune for performance in a controlled environment. Using it in a workstation is asking for trouble.

In general, I recommend against trying to change the way Windows memory management works. It’s a system. Tweaking one aspect of it runs the risk of destabilizing the entire system. It’s also worth noting that this setting has been around since the Window NT era. Now, Microsoft’s engineers are obsessive about performance. They know that reviewers will put a stopwatch to every new release, and so they tune and tune and tune to get the memory paging system working effectively. If this setting really made a difference in performance, don’t you think it would be enabled already?

If you’re really concerned about performance, the smartest thing you can do is monitor memory usage in your environment. If you’re consistently exceeding the amount of physical RAM in your system, either do less (shut some programs down before running memory-intensive applications) or install more memory.

Everything you wanted to know about BCDEdit

Microsoft has published a typically exhaustive FAQ that explains how to use the new Boot Configuration Data Editor (Bcdedit.exe). The Boot Configuration Data store replaces boot.ini, the text file that manages startup settings for older versions of Windows, including Windows XP. This command-line utility is strictly propellerhead stuff. If you run one version of Windows Vista, as most people will, you’ll never need to see or work with the BCD store.

If you set up a multi-boot system with two or more versions of Windows Vista, you’ll need to use Bcdedit to change the startup menu so you can see which version is which. (By default, each entry gets the same descriptive text, which makes it less than useful.)

The easiest way to change the boot menu entry is to do so for the current operating system, like this. Remember, these intructions are only for Windows Vista:

  1. On the Start menu, click All Programs, open the Accessories folder, and then right-click Command Prompt.
  2. Choose Run As Administrator. (If you skip this step, you’ll be running as a regular user and won’t be allowed to change the BCD store.)
  3. In the Command Prompt window, type the following command:

    bcdedit /set {current} description “your menu description

    Note that those are curly braces in the parameter after /set, and you should of course replace the italicized text with whatever you want to display for the actual startup menu text.

To edit menu descriptions for an operating system choice other than the current one, you need to find the GUID for that entry and substitute it in the parameter after /set. It’s much easier just to boot into the other OS and use the same command to reset that description.

Spam of the day

These days, spammers salt their messages with random assortments of text – “word salads” – to help them slip past spam filters. But this message, which arrived in my Inbox this morning, takes the practice to a new level that’s almost art. An excerpt:

When the skyscraper daydreams, a blood clot over the bartender sweeps the floor. Indeed, a polar bear around the squid cooks cheese grits for a diskette near the insurance agent. A righteous prime minister hesitates, and the salad dressing goes to sleep; however, some cab driver bestows great honor upon a short order cook inside the dust bunny.

I had an interesting revelation today as I watched the pre-workout instructions on my new Stott Pilates DVD. I like cereal with strawberry flakes in it. I don’t like exercise. Specifically abstract crap about sensing how muscles I don’t even know about are sliding around on my back. I don’t enjoy it, but I use my hamster wheel – correction Orbitrak elliptical machine – often in order to stay in shape. Partly out of vanity and partly out of an evolved addiction to the way exercise improves overall well-being and generally not feeling like garbage. Probably, I’m getting old. Definitely, I’m losing patience.

Sometimes a ski lodge living with an inferiority complex goes to sleep, but the crank case always gives lectures on morality to the cab driver! Furthermore, a dirt-encrusted inferiority complex beams with joy, and a wisely greasy garbage can learns a hard lesson from some customer from a ski lodge. Any graduated cylinder can lazily pee on a short order cook for a scythe, but it takes a real fraction to make love to a tomato over the cough syrup. The hockey player earns frequent flier miles, and another fundraiser from a chain saw plays pinochle with a cheese wheel.

A few of those lines could easily have been on  Highway 61 Revisited.

No, I didn’t click the link in the message, so I have no idea what they were selling. I’m guessing it had something to do with exercise equipment.

Robert X. Clueless

Mark Stephens, the PBS pundit who goes by the pseudonym Robert X. Cringely, is modestly famous for his bomb-throwing anti-Microsoft screeds. He’s also famous for being flat-out wrong, often, even when it comes to his own professional credentials. His latest column, A Whole New Ball Game, reaches new heights of misinformation. Here’s a snippet:

Last week, a Microsoft data security guru suggested at a conference that corporate and government users would be wise to come up with automated processes to wipe clean hard drives and reinstall operating systems and applications periodically as a way to deal with malware infestations. What Microsoft is talking about is a utility from SysInternals, a company that makes simply awesome tools.

This is pure horseshit. One surefire indicator that something is rotten in this particular pulpit is that Mark’s … oops, sorry … Bob’s column contains no links. In fact, his columns never link to any external sources of information. Isn’t it remarkable that someone who writes a weekly column for the Internet never links to anyone else? If you want to actually check the facts about something Mark/Bob has written, you have to go dig it out yourself.[*] In this case, the quote is from a presentation at the InfoSec World conference by Mike Danseglio, program manager in the Security Solutions group at Microsoft. The story was originally reported by Ryan Naraine of eWeek. (Read the whole thing here, and see some additional remarks of mine here.)

Did Danseglio really say that corporate and government users should “periodically” wipe and reimage systems? No, not at all. He said that’s the most effective way to deal with a system that has been compromised by a rootkit or an infestation of some advanced spyware programs. And he’s right. When you let someone else take over your operating system, it’s not your PC anymore. You could spend hours or days trying to find and remove all traces of the intruder, but you’d never know for sure whether you were successful.

So, wipe and reimage as a last resort. But the smart, safe strategy that Danseglio recommends is prevention. In fact, if you click to the second page of the eWeek story, you read this conclusion:

According to Danseglio, user education goes a long way to mitigating the threat from social engineering, but in companies where staff turnover is high, he said a company may never recoup that investment.

“The easy way to deal with this is to think about prevention. Preventing an infection is far easier than cleaning up,” he said, urging enterprise administrators to block known bad content using firewalls and proxy filtering and to ensure security software regularly scans for infections.

That’s good advice, and it’s consistent with the “defense in depth” strategy that the Microsoft Security Response Center has been advising for years. But you’d never know that if you read only Cringely, who preaches to an audience that’s eager to sop up anti-Microsoft propaganda, no matter how ill-founded or factually challenged.

And then there’s this:

The crying shame of this whole story is that Microsoft has given up on Windows security. They have no internal expertise to solve this problem among their 60,000-plus employees, and they apparently have no interest in looking outside for help. I know any number of experts who could give Microsoft some very good guidance on what is needed to fix and secure Windows. There are very good developers Microsoft could call upon to help them. But no, their answer is to rebuild your system every few days and start over. Will Vista be any better?

Given up on Windows security? Yeah, I guess Windows XP SP2, Windows Defender, Windows Live OneCare, Microsoft Client Protection, and the many security improvements built into Windows Vista don’t really exist. No internal expertise? That’s ludicrous, as anyone who’s spent even 10 minutes with the Windows team would know. No interest in looking outside for help? As Scoble points out, all you have to do is look at the attendee list of Microsoft’s BlueHat Security Briefings to know that conclusion is not supported by any facts.

Or you could just look at the by-line. If it says Cringely, you know it’s wrong.

Update: Dwight Silverman is skeptical about some unrelated parts of the same Cringely column.

[*] As some commenters point out, a separate page, unmentioned in the original column, includes a link to the eWeek article. I’m a little baffled at the idea that a columnist who writes a weekly column for the web hasn’t learned how to create hyperlinks. It is 2006, after all. But technically, he did provide a link to this article, if you know where to look.

If the MacOS is so great, why do I need Windows…?

Charlie Owen takes note of the buzz surrounding the Apple Boot Camp announcement and asks the logical question:

If the MacOS is so wonderful why do I need to even consider running Windows?

I can think of a couple of good, non-snarky answers.

Some people genuinely prefer the Mac interface (pick your reason: it’s better looking than Windows XP, it’s more secure, your friends like it). But given the demand to make a binary choice, they pick Windows because the productivity software they want or need is only available for Windows.

If you think the Mac OS is wonderful, but you’re also a gamer, you’ve got no choice but to live in two worlds.

Maybe I don’t think the OS is all that wonderful, but the hardware is slick and stylish. If I don’t care about paying a premium, I might be willing to buy, say, a Mac Mini and run Windows Media Center on it. (Personally, I think the AOpen Mini PC would be a better choice, but hey …)

Welcome, Macsurfer visitors! Be sure to also read these posts:

A better Windows than Windows?

Apple’s Boot Camp is just the start

Dual-boot, no; virtualization, yes

 

The slow death of the English language

My erstwhile[*] PC Computing colleague John Montgomery, now at Microsoft, has a wonderful eulogy on words that the PC industry, led by Microsoft, has killed. One of my favorites: 

Community. A word now utterly without meaning, community used to be have connotations of people connecting with other people who have like interests. Now it means a Web site. I’m hoping this one will be able to be reborn.

The whole thing is worth reading, especially if you’re a PC marketing type wondering how not to debase the English language any further. It’s also entertaining if you’re a once or former editor or a high-tech blogger desperately trying to avoid writing like a hack.

[*] Alas, the word erstwhile is hopelessly misused these days. It properly means “in the past” or “former” but is all too often confused with esteemed. John happens to be both.

As an aside… Back when the Internets were just a gleam in Al Gore’s eye, I wrote an essay on Microspeak, the curious blend of jargon, slang, and groupthink that characterizes conversation around Redmond. It’s lost to the ages, but a bit of Googling turned up this mid-1990s-vintage page that has a lot of the same material.

If you spend any amount of time at Microsoft, you’ve probably noticed that many Softies, when asked a question, begin their answer with “So…” What’s up with that?

Yes, Windows Media Center runs on Intel-based Macs

PC World’s Harry McCracken has some questions about Apple’s new Boot Camp software, which lets Intel-based Macs run Windows XP. Like: “Does Boot Camp let you run Windows Media Center?”

Microsoft’s Sean Alexander has some answers:

MCE (and an unreleased player) are running like champs.  I’m hearing reports of Vista running as well.  Battery life still stinks compared to my sony but hey, this is a desktop replacement riight?

Windows Vista running on Apple hardware? The mind boggles:

Venkman: This city is headed for a disaster of biblical proportions.
Mayor: What do you mean, biblical?
Ray: What he means is Old Testament, Mr. Mayor… real Wrath-of-God-type stuff. Fire and brimstone coming down from the skies.
Venkman: Rivers and seas boiling!
Egon: 40 years of darkness, earthquakes, volcanos.
Winston:The dead rising from the grave!
Venkman: Human sacrifice, dogs and cats, living together… mass hysteria!

PC World also has more details on the new $50 virtualization software from Parallels, which claims to allow Intel-based Macs to run Windows XP, several flavors of Linux, and even OS/2 Warp in a virtual machine without dual-booting.

Update: Screen shots and more info about Parallels Workstation 2.1 Beta for Mac OS X. Because it’s currently in beta, it’s free to use.