Free AV for Vista beta testers

If you’re experimenting with Windows Vista Beta 2, you’ve probably already noticed that many antivirus programs are incompatible. Computer Associates has just announced that it’s offering a free one-year subscription to eTrust EZ AntiVirus for Vista beta testers. I’ve installed it here and it appears to be working just fine.

I tried posting this entry using the new Publish to Blog feature in Word 2007. No luck. It’s able to communicate with the WordPress back end, but the posts just go off into the ether, never to be seen again. Bummer.

Update: Trend Micro has a free Vista-compatible beta version of its PC-Cillin software, too.

It’s so easy to slip

Via PCWorld.com comes a report that Windows Vista might not be ready in January after all:

The operating system was due to be launched this year but in March the company said it wouldn’t get broad release until January 2007. Ballmer said Wednesday that the planned January launch may slip further based on feedback from a beta release program and the product road-maps of hardware vendors.

“We think we are on track for shipping early in the year. We’ve talked about the month, but we get a chance to critically assess all of the feedback we’ll get from this beta release then confirm or move [the launch date] a few weeks,” he said at a news conference in Tokyo.

We’ll see. Until we’re within the six-month window, I take any tentative date with a grain of salt.

The headline, of course, is an homage to the late, great Lowell George. The definitive version of “Easy to Slip” is on Little Feat’s 1972 release, Sailin’ Shoes. Sadly, it is not on Waiting for Columbus, which is possibly absolutely the greatest live album ever.

Vista Beta 2, up close and personal

Over at ZDNet, I’ve put together a gallery of 30 screen shots digging deep into Vista Beta 2. I’ve dug up some stuff I guarantee you won’t see anywhere else.

For instance, there’s the new Performance Diagnostic Console, which is like Task Manager’s Performance tab on steroids.

Eb_vista_beta2_118_crop

If you’ve got questions about Vista Beta 2, post a comment here or in the Talkback section at ZDNet. I’ll do my best to follow up.

How not to publish a correction

Over the weekend, a blog I had never heard of before (msblog.org) got a lot of publicity for passing along an unsubstantiated and highly questionable rumor that supposedly listed the retail prices that Microsoft is going to attach to Windows Vista.

According to this list, the prices of Windows Vista were going to be obscenely high, with typical prices of $500–1000. The list originally appeared on a German site and was picked up with no questioning by author Dennis Fraederich. Trouble is, it didn’t pass the smell test, with obvious errors and some internal problems that should have been obvious to anyone who looked at it for more than five seconds.

And now, the folks at msblog.org have simply deleted the contents of the original post, changing its headline to read “Post pulled due to public flaming.” The comments from readers are gone, too, available only to administrators of the site.

Now, there’s an interesting strategy. Get something wrong? Don’t correct it. Don’t retract it. Don’t apologize. Don’t respond to your critics. Just pull the post, hide the comments, and pretend it never happened, even though a few dozen other sites have already reprinted the bogus information and posted links to the original article.

Look, anyone can make a mistake. And it’s easy to get caught up in the frenzy to post something that appears to be a juicy scoop. But if you want to be taken seriously as a news source, you have to be willing to take your lumps when you get it wrong. Deleting the post is gutless and a complete disservice to your readers.

Am I going to listen to anything else these people have to say? No. Their credibility is now in negative territory.

Everything you wanted to know about User Account Control

I’ve got a pair of posts up at ZDNet that deal with the controversial User Account Control (UAC) feature in Windows Vista. Due to an unfortunate editing error, a big chunk of the second post was inadvertently left out of the original post (which was Slashdotted). So if you read that second post and found it a little fuzzy, well, go back and take another look.

Eb_uac_file_operation_3

The conclusion to this three-part series lists ways you can work around UAC (some safe, some stupid and – alas – already widely publicized). I’ll also offer Microsoft some suggestions on how to make this feature work better in Vista’s final release.

If you’re thinking of playing with evaluating Windows Vista Beta 2 when it’s released to the public (maybe sooner than you think), be sure to save a link to this page.

Best line of the day so far, Vista division

InfoWorld’s Tom Sullivan:

In a report sure to make its customers glad they pay so much for consulting services, Gartner analysts went way out on a limb and said that Microsoft will miss its target shipping date for Windows Vista by one quarter. The analysts also said that “Microsoft can’t accurately predict [shipping dates] more than a few months out.” That last statement is probably fair, but if Microsoft can’t, how can Gartner?

Not to mention that Gartner has a really lousy track record with its predictions.

More protection than you really need?

Thomas Lee has been a Windows beta tester for, oh, a gazillion years. His take on User Account Control (formerly User Account Protection, or UAP) is typical of longtime Windows users:

There are some other things about [build] 5365 I hate – particularly UAP. The concept of forcing users to run with relatively low privaleges is a great one. But the implementation is Vista is just plain lame. As I’m setting up the system, the entire screen goes black for 2-3 seconds (a visual sensation similar to what we saw when XP blue-screened) then a silly dialog box pops up – I click Accept – the screen goes black for another 2-3 seconds, and I can carry on. It’s very, very annoying – sufficiently so that I’m going to just log on with admin privaleges. It’s easier and far less intrusive. Sadly, while I like the concept, MS has made a poor job of the implementation. Of course, mileage may vary on this – but I doubt many IT Pros will even come close to liking this implementation. We’ll see.

I’ve published some screen shots of the latest UAC implementation at ZDNet. More to follow.

Vista versions: maybe not so confusing after all

Am I the only person who’s actually happy about the mix of Windows Vista versions that Microsoft plans to offer next year? If you’re considering buying a new Windows PC, I believe your decision-making process will actually be simpler when Windows Vista hits the street than it is today. And if you’re planning to upgrade a PC you already own, you’ll find way more flexibility than you have with Windows XP.

I realize that flies in the face of conventional wisdom. One comment I read over and over again is that somebody looking for a new PC or a Windows upgrade has it so simple today, and those marketing morons at Microsoft are going to go screw it up for everybody by introducing all these confusing new packages. That conventional wisdom starts to break down the moment you look at it for more than about, oh, five seconds.

Last week I published a series of posts at ZDNet that address the widely held idea that Microsoft is making the biggest marketing blunder since New Coke by introducing too many versions. (I put together a table that clearly shows what’s in each version as well as two columns that explain the consumer features and the business features you’ll find in each upgrade.)

The core of the “Vista is too confusing” argument is that Vista has seven versions and XP only has two. Windows buyers will be paralyzed with indecision as they contemplate which version of Windows should go on their new PC. Oh, really? Look more closely.

Continue reading “Vista versions: maybe not so confusing after all”

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.

Want a Vista-ready PC? Skip the sticker

Last week, Microsoft announced that it will change its PC logo program so PC makers can flag computers that are capable of running Windows Vista. Of course, tech websites are falling all over themselves to find a snarky take on the “Vista Capable” program:

PC World’s Harry McCracken: “Next month, new PCs will show up with stickers identifying them as being ‘Windows Vista Capable.’ But ‘Capable of Running Certain Versions of Windows Vista, But Maybe Not Stupendously Well’ might be a more accurate designation, it seems.”

Engadget: “[F]or the general consumer, the Vista Capable badge only means it’ll support the baseline version, Home Basic Edition — which we’ll be promptly ignoring, thankyouverymuch — and may not do fun things like run Aero or be able to use more ‘advanced’ Vista features like HDCP. Normally this is the part where we’d get a little huffy and suggest Microsoft do it this way or that, but we’re starting to feel we’re in a little too deep here, you know?”

RealTechNews: “It’s not going to be available until 2007, but heck, if you can’t get the OS, will stickers do?”

Snark is fun, but the question is real. Should you buy a new PC, or should you wait? And who can make sense of the official Microsoft guidelines?

In a post on my ZDNet blog today, I’ve laid out my three simple rules for buying a new Vista-ready PC. No sticker required. (Hint: For starters, don’t buy a cheap PC.)

Go read it.