Categories
Uncategorized

Is the Microsoft Wireless Entertainment Desktop 8000 too much? It depends…

Last year I posted an entry on how to choose the best computer which included an article by Mike Himowitz, columnist at the Baltimore Sun.  Himowitz wrote the article “Sticker tells shopper key parts of a laptop” which covers “the specific components of a portable PC.”

Overall, I like Mike’s advice: I’ve found it to be direct and to the point, with few sidetracks.

Microsoft Wireless Entertainment Desktop 8000Last week, I walked by the new Microsoft Wireless Entertainment Desktop 8000 at the Microsoft Company Store.  I use the Wireless Laser Desktop 4000 at work and at home with the comfort curve key layout, and I thought that it would be a nice addition to our home Media Center set up.  Heck, the 8000 would look great on the desk of our home office, too.  The web site touts that the 8000 is “designed to make it easier than ever to control PC media from your desk, your lap–or even from the comfort of your couch.”

Opening the paper this morning, I found that Himowitz has a review of the Microsoft Wireless Entertainment Desktop 8000 reprinted in today’s Seattle Times (originally from his article in the Sun, “Tinkling these keys isn’t worth $260“).

“Reality check — $260 for a keyboard and mouse? That’s almost four times as much as I spent for the wireless combo I use with the computer that’s hooked up to our HDTV set. What could you possibly get for that much money?

“As it turns out, you get the same thing you get when you buy a Mercedes instead of a Camry: more luxury and styling and gimmicks. There’s a somewhat bigger payoff for couch potatoes, but is it enough to justify almost $300?”

In short, Mike said that the answer is no.

Unlike Mike’s experience, where had trouble getting used to the Comfort Curve key layout after more than a week of use, I find that the design is my preferred layout.  After I used the keyboard for about a month, I found that the design fits my hands quite nicely. In fact, I have difficulty going back to a laptop after spending time working on my desktop system.

Mike asked the real question, and offers his answer:

“But are all these features worth close to $300?

“Bottom line: I wouldn’t pay that much. But if you (a) have the money, (b) think you can get used to this lap-friendly, wireless keyboard and (c) want it packaged with a superb laser mouse, you won’t be disappointed.”

Once again, I agree with Mike. $300 is a lot for a keyboard and mouse, even if you do have the money.  It’s certainly a nice improvement over the older (and retired) Microsoft Remote Keyboard for Windows XP Media Center

Wireless Entertainment Desktop 7000There are several other Comfort Curve design mouse and keyboard sets available, including the equally svelte Wireless Entertainment Desktop 7000 (which CNET reviewed and ranked sightly lower than the 8000).  I think that the backlit keyboard and four USB Ports make the 8000 a better choice for a home theatre, but the 7000 is a good addition to any Media Center setup for the US$129 street price I’ve seen recently.  For home office use, the Wireless Laser Desktop 4000 and Wireless Laser Desktop 6000 are both good, affordable choices.

CNET has a review of the 8000 mouse and keyboard bundle, giving it a 7.0 out of 10, highlighting that the system is rechargeable, and easy-to-use with smart backlighting.  But CNET disses it for being “expensive…” and for having a “clunky recharging station.”

I’m still thinking about that investment… so far I have not brought one home, as elegant as it is.  But with a street price of around $249, it’s nearing what I consider a reasonable premium over the 7000.  If you’ve invested a hefty sum into a Media Center PC and home theatre setup, the 8000 is probably a small portion of the overall cost of the setup.  And it could be an easy to appreciate premium: with your remote control, the keyboard and mouse are pieces that you use with your Media Center system nearly every day.

Tags: tips, Windows Vista, Media Center, hardware, keyboard, mouse, Mike Himowitz.

Categories
Uncategorized

Windows Vista SP1 Update now available to MSDN, TechNet subscribers, with download links

As noted on the  MSDN Subscriptions WebLog and TechNet Plus… the Windows Vista SP1 update is now available to MSDN and TechNet subscribers. 


Proof that Microsoft does listen and respond. 😉


MSDN



We heard you.

Look for it in the Top Downloads list by end of week, on http://msdn2.microsoft.com/subscriptions

Feb 14 0900 (PDT) – NOW LIVE. Happy Valentines Day!


TechNet Plus- Vista SP1 available for Download:


We have posted the SP1 Update release for download through the Top Downloads section on http://technet.microsoft.com/subscriptions.


[Added 2/15/08]: I just saw that Mike Nash’s post on Mike Nash’s post on the Windows Vista Blog was updated with download links…


Here are the direct links for subscribers…



Tags: Microsoft, Customer Service, Customer Support, Windows Vista, SP1, MSDN, TechNet.

Categories
Uncategorized

Your questions: “when should I use Sleep and Hibernate modes on Windows?”

I get the question a lot on sleep vs. hibernate (and as noted in a recent post), and it came up today in a discussion. 

“I’m confused by the different selections I have in the Start menu… when should I use Sleep and Hibernate to turn off my computer?”

In Sleep (or standby), you’ll see that the computer is generally off, with a trickle of power keeping the computer’s memory powered.  When you use your PC throughout the day, but leave for extended periods (lunch, meetings, even overnight), Sleep is a good choice.  And (depending on your model) all it takes is a mouse movement or keyboard tap to wake the computer up. 

One of the reasons I also have a UPS on my main desktop at home is that I use Sleep most often, and if the computer loses power, the work you may have open but not yet saved will be lost.  And on our notebooks at home (and at the office) we use Sleep given that the computer’s battery acts like a mini UPS and generally has enough power to keep the memory alive. (Note that we generally keep the notebooks connected to a power supply as well.)

When I leave for the weekend, I often use Hibernate on my PCs at the office and at home.  In this state, the PC’s complete memory state (the contents of RAM) is saved by writing to the hard disc and the computer powers down.  When you turn the computer back on (recovering from hibernation) via the hibernation file, you start up where you left off.

This from TechNet:

When a PC starts up, Windows Vista performs many processing tasks in the background, returning control to the user much sooner than previous versions of Windows. Even this short wait happens less frequently than before, because instead of shutting down the computer to save power, users can use the new Sleep state, the default state for turning off computers running Windows Vista. Sleep combines the resume speed of Standby mode with the data protection and low power-consumption characteristics of Hibernate. When entering the Sleep state, Windows Vista records the contents of memory to the hard disk, just as it would with Hibernate. However, it also maintains the memory for a period of time, just as Windows XP maintains the memory in Standby mode. Windows Vista enters and recovers from Sleep state in seconds, and while the system sleeps, power consumption is extremely low.

The most significant benefit of Sleep is simplicity; users don’t have to choose between using Standby or Hibernate because Sleep offers the best of both.

As a follow up, here’s a little more information on Sleep and Hibernate modes in the OS, as the Productivity Portfolio weblog has a good post that describes the Windows XP power schemes.

More info:

Click here for more on fast sleep and resume in Windows Vista.

Click here to learn how to use your computer efficiently and to save energy by activating Sleep mode for your monitor.

Also see this Search on Live.com for more on sleep and hibernate in Microsoft Windows.

Tags: performance, tips, Windows Vista, notebook, hardware, hibernate, sleep, customer experience.

Categories
Uncategorized

Of interest: Windows Vista isn’t just blue, it now comes in (red)

You may be used to seeing the Windows Vista user experience in a shade of blue. (Well, it looks blue.)

Now it comes in red.

image

Nick on the Windows Vista blog has a post on an announcement with Dell and (RED), to be made this at Davos. 

You can see for yourself on the Microsoft Windows Vista site and read more…

“Windows and Dell have joined (RED) to help eliminate AIDS in Africa. When you buy a Dell (PRODUCT) RED PC with Windows Vista Ultimate (PRODUCT) RED, Windows and Dell will jointly contribute $50 to $80, depending on the product, to The Global Fund to fight AIDS in Africa.

“Co-founded by U2’s Bono and Bobby Shriver, Chairman of DATA (Debt, AIDS, Trade Africa), (RED) is an innovative and sustainable way businesses and consumers can work together to change the world.  It is a business model, not a charity. Working with (RED), companies create special versions of their products with the (PRODUCT) RED brand. When consumers choose to buy (PRODUCT) RED, a portion of the profits goes directly to The Global Fund to help eliminate AIDS in Africa.”

Of interest: info on the Windows Vista blog about the new packaging for Windows Vista and Office 2007.

Categories
Uncategorized

Forget Y2K, DST and Time Zones: this weekend, it’s the Y2.038K bug

This weekend will mark another interesting milestone in Time and Date, oone that actually doesn’t occur for thirty more years, in 2038.  

Also known as the ‘Friday the 13th’ bug, the 2038 issue is due to the way 32-bit systems note time in seconds rather than by an actual coded date.  The full impact will be felt on January 19, 2038, when systems many not work accurately, or even crash.  The initial wave of the challenge would likely impact customers in the financial sector, particularly those with (pardon the pun) an interest in long term products (mortgages, investments, bonds) with maturity dates post Jan 19, 2038.  But those with longer maturity instruments would’ve seen an impact years ago.

As this involves dates and times, Wyn asked today about this impact, as this smacked of an issue similar to what we saw last year with the various DST and time zone changes around the world… 


“I have not found too much on this and I am not sure if anything is know or being done to avoid the problem…”


Good question.  I asked several of our product groups if any of our products will be impacted by the date.

A nod of thanks to Geoff for noting this MSDN article from way back in 1998, “All Ready for 2000 and the Euro? What About 2038?” (September 7, 1998).  If Y2K did anything for the industry, it was to spur an analysis of any date and time issues that could impact the operating system and software products…



First it was Y2K. Then the Euro conversion. And now, as if the Y2K and Euro problems weren’t bad enough, there’s the year 2038 bug. Dr. GUI got a letter from Mahmoud Saleh alerting him (reminding him, actually) of a similar problem that will face C and C++ programmers in coming years: we can call it the Y2.038K bug.

The problem stems from the common definition of the time_t as an integer containing the number of seconds since midnight, January 1, 1970. Most C/C++ runtime libraries define time_t as a long int. On most systems, long int is 32 bits, which means that we’ve got a range of 2^31-1 (2,147,483,647) seconds—until sometime on January 18, 2038. (Assuming Dr. GUI’s Windows CE Palm-size PC has it right, that’s a Monday. Figures.) When the clock rolls over, it’ll be back to the ’70s for everyone. Get your leisure suits ready ‘cuz you’ll be catching Boogie Fever and Nixon will be President again. Four more years indeed!

Anything that uses time_t is also in trouble. That includes the time_b structure (not commonly used, anyway) and, very unfortunately, the MFC CTime class. Code that uses time_t, directly or indirectly, will need to be changed sometime before you start dealing with dates after 1/18/2038. (Note that if your program deals with, say, 40-year bonds, you’re in trouble today.)


As Geoff pointed out, SYSTEMTIME has no problems and can go until the year 30,827, and FILETIME, a 64-bit integer (two DWORDs representing LOW and HIGH values) since January 1, 1601 (Julian).  It too can represent a 30,000 (or 60,000 unsigned) year interval.  From the MSDN article:


…the Win32 SYSTEMTIME structure… stores the year part of the date as a 16-bit integer, and the Win32 FILETIME structure, which stores the date as the number of 100-nanosecond intervals since 1601. The problem is that neither of these structures have many supporting functions.

Better yet is to use the automation DATE object. DATE is typedef’ed as double, so there are 53 bits of precision—enough for your program’s lifetime. The whole part of the double number represents the number of days since midnight, December 30, 1899. (Negative numbers are before 12/30/1899.) The absolute value of the fractional part represents the time in the day: midnight is zero, noon is 0.5, etc. You can convert the automation DATE objects to other formats with various variant API functions.


Overall, the advice is that if you have custom applications you might want to check to see if they are using C/C++ time_t, which will run out in 2038.  Just as I noted previously on how Windows handles historical events, you might want to check any custom or ‘home-grown’ line of business applications that use time_t.  Looking quickly at Windows, the core OS appears to run just fine with dates far into the future. 

I will have to check one of my old Apple systems at home running (quite reliably, I might add) System 9, which according to Apple, is good up until February 6, 2040; the current Mac OS up until 29,940… Windows will be accurate for an additional 887 years after the latest Mac release fails, but I’m sure Apple will have an update long before 29,940 rolls around. 😉 

(Interesting factoid that stuck in my mind: in the H. G. Wells classic novella, The Time Machine, the hero of the story travels to the year 802,701 A.D.  I’m hopeful in that future, the downfall of mankind will have nothing to do with the failure of the modern OS to cope with dates past the 301st century.)

For more information, please see these articles courtesy of a quick MSDN search

Tags: Apple, Microsoft, Vista, Windows, Time, 2038.