Categories
Uncategorized

Deploying Vista: More with Mark Russinovich on Springboard Live

Questions on deploying Vista?  See the first Springboard Live clip using Silverlight, presented by our own Mark Russinovich…

Join Mark Russinovich and a panel of experts for a discussion on adopting Windows Vista into a desktop infrastructure. The panel features subject-matter experts and IT pros from around the world who have tackled Windows Vista deployment—hear about the challenges, workarounds, and tips & tricks they have learned along the way.

And see this month’s spotlight page, “Still on the Fence with Windows Vista?” which takes a look at why now is “a good time to take another look at Windows Vista and what the adoption process has to offer.”

Springboard on TechNet is a collection of tools and resources that may help you better understand deployment of Microsoft products and get answers and insightful guidance from professionals and the community.

You can also view the streaming video in Windows Media Player via the link below.

View in Windows Media Player

Tags: Microsoft, Mark Russinovich, tips, Vista, Windows.

Categories
Uncategorized

PC problems: Upgrade or buy a new one? Suggestions from the Seattle Times

Patrick Marshall of The Seattle Times addresses whether it’s worth fixing a computer with issues, or if it’s a better idea to just get a new PC. Plus a few additional tips on maintaining your computer.

Patrick Marshall writes for The Seattle Times today has an article where he is asked his opinion on whether it’s worth fixing a computer with issues, or if it’s a better idea to just get a new PC. Marshall recommends what to do next when a computer slows down… and whether to upgrade or buy a new PC…

“You’ve raised two of the most frequently asked questions I get: Why is my computer slowing down? Should I upgrade or buy a new computer?

The most common causes of sudden slowdowns in performance are…

  1. insufficient memory for the applications you’re running,
  2. an overfull or fragmented hard drive,
  3. a misbehaving application or
  4. a virus or hacker.

“So how do you figure out which malady you’re suffering from? Windows provides a number of tools to help diagnose the problem. First, you’ll want to call up the Task Manager. [note: see How to use Windows Task Manager and Windows Task Manager on Wikipedia] Right-click in your system bar along the bottom of the screen and select Task Manager. Next, click on the Performance tab in the utility that pops up. You’ll get a display of how much memory is being used and how much your CPU is in use. If your memory usage is above 80 percent, you’ll want to explore what is eating up your memory. You can do this by clicking on the Processes tab. If you find that all the memory is being used by legitimate applications, you may want to consider adding memory.”

Good suggestions.

I’ll add, from the Microsoft Windows XP product page, see the section on 5 ways to speed up your computer

Follow these quick guidelines to maintain your computer and keep it running smoothly.

  1. Free up disk space
  2. Speed up access to data
  3. Detect and repair disk errors
  4. Protect your computer against spyware
  5. Learn all about ReadyBoost

One of the (usually!) easiest upgrades you can consider is increasing your computer’s memory, particularly if you determine that you don’t have enough system memory.  On the remaining Windows XP computer at home, we have 1GB of memory installed; on Windows Vista, we have configurations operating with 1GB, 2GB and 4GB.  And my main (older) Mac has 1GB of memory.  There are several tools to help you navigate the upgrade process, and I personally like the Crucial Memory System Scanner which “automatically analyzes your computer memory information and suggests an upgrade that’s guaranteed compatible.”

And defragmenting your hard drive may help your hard drive be more efficient at accessing and saving files.  To start Disk Defragmenter in Windows, click on the Start button, and navigate to the Programs folder and open the Accessories folder.  There, you’ll see the System Tools folder where you can select “Disk Defragmenter.”  In managing your hard drive, consider adding another drive or upgrading your drive to a larger model particularly if you have less than 10-15 percent free space on your main hard drive.

And of course, back up your files on your computer.

More info is also available on the Windows Help and How To site on Microsoft.com.

Tags: Microsoft, customer support, tips, customer service, Windows.

Categories
Uncategorized

Engadget notices Fujitsu’s new F-A50 all-in-one PC

Post this in the “ooh, I want one” category.

Of interest as I run off to a meeting (thanks, Bill, for the ping). Fujitsu’s F-A50 all-in-one escapes a terrible, terrible heritage from Engadget’s Paul Miller…

Hey, it’s still not the most svelte of all-in-one PCs, but given its predecessors we’ll really take whatever we can get. The Fujitsu F-A50 rocks a 16:9 16-inch display running at 1366 x 768, with a base that allows for adjustable height and angles for the PC. Unfortunately, 16:9 is about as wild as things get around here, with Core 2 Duo T8100 processor, Intel GM965 integrated graphics and so forth. WiFi is built-in, which is always nice to see on a desktop PC, and there’s even a PC card slot for expansion. The whole shebang weighs in at 12 pounds, and goes on sale in Japan on May 17th for around $1,300. [Via Engadget Spanish]

Categories
Uncategorized

Windows XP SP3 Released to PC Manufacturers, System Builders

Yesterday we announced the release to manufacturers (RTM) of Service Pack 3 (SP3) for Windows XP, and as noted on Computerworld…

“Windows XP has released to manufacturing,” said Chris Keroack, the service pack’s release manager, in a message posted to a TechNet support forum Monday at around 1 p.m. EDT. “Windows XP SP3 bits are now working their way through our manufacturing channels to be available to OEM and enterprise customers.”

If you are an IT systems administrator, developer, or if you’re no stranger to installing updates from the DLC, you will be able to update XP systems to SP3 next week when SP3 is released on the Download Center, or as an optional download on Windows Update. 

For consumers, you’ll start to see XP SP3 distributed via Automatic Update in early summer.

Categories
Uncategorized

Another look at the year 2038 problem

I was asked last week (again) for guidance I could give (being involved in time in one way or another, in addition to my day job) on how Microsoft products may be impacted by the 2038 issue. 


As I noted in January, the Year 2038 problem (as defined by the Wikipedia entry)…



“The year 2038 problem (also known as “Unix Millennium bug”, “Y2K38,” “Y2K+38,” or “Y2.038K” by analogy to the Y2K problem) may cause some computer software to fail before or in the year 2038. The problem affects Unix-like operating systems, which represent system time as the number of seconds (ignoring leap seconds) since 00:00:00 January 1, 1970.[1] This representation also affects software written for most other operating systems because of the broad deployment of C. On most 32-bit systems, the time_t data type used to store this second count is a signed 32-bit integer. The latest time that can be represented in this format, following the POSIX standard, is 03:14:07 UTC on Tuesday, January 19, 2038. Times beyond this moment will “wrap around” and be represented internally as a negative number, and cause programs to fail, since they will see these times not as being in 2038 but rather in 1901. Erroneous calculations and decisions may therefore result.


Some people believed that the bulk of issues would surface on January 19, 2008, the date when new 30-year mortgages and bonds could be impacted.  In fact, much of the impact would have been seen years ago given that there are many financial instruments with a greater than 30 year life span: some mortgages and bonds extend out 40 years, and there are Japanese and English mortgages that can span close to a century.


From what I understand (thanks to the education from Geoff, Shay and several folks in DevDiv), information on how to mitigate the year 2038 bug was included in our Y2K response in the late 1990’s.  And Microsoft has provided guidance and statements on our various web sites, as impacts have generally been product specific for older products no longer in support (unless otherwise indicated in a supporting KB article).


In general…


  • currently supported core OS and mainstream support products operate as designed and with no known negative impact with regards to the 2038 unless otherwise noted.
  • SYSTEMTIME has no problems and can go until the year 30,827.
  • 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.
  • Difficulties will be found were developers use C/C++ time_t, which will run out in 2038.

Programs that are compiled with VC8 or newer and do not define _USE_32BIT_TIME_T are immune to Year 2038 problems caused by time_t, assuming that they do not contain bugs themselves (casting a time_t to an int and back will truncate it). I’m told by the Developer division that…


For more references…



Hope this helps.

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


Delicious Bookmark this on Delicious Bookmark and Share