Print 96 comment(s) - last by KamiXkaze.. on Jul 15 at 12:08 AM

Microsoft suggests disabling ReadyBoost until SP1
Microsoft plans numerous fixes including an update to ReadyBoost

Microsoft officially launched Windows Vista for volume licensing on November 30. The company also simultaneously launched Office 2007 giving Microsoft a 1-2 punch in the realm of operating systems and productivity suites.

"These are game-changing products," said Microsoft CEO Steve Ballmer at the launch. "It’s an incredible step forward for business computing in a year of unprecedented innovation from Microsoft. We expect that more than 200 million people will be using at least one of these products by the end of 2007."

Microsoft followed up with the retail launch of both products two months later on January 30. Both software products were made available in over 70 countries and over 40,000 retail locations.

Windows Vista is not even a year old, but Microsoft is already orchestrating the launch of Service Pack 1 (SP1) Beta 1 for the week of July 16. Many companies will not even touch a new Microsoft operating system until the first service pack is released, so the quick rollout of SP1 isn't totally unexpected.

According to ZDNET's Mary Jo Foley, SP1 will RTM in November after just four months of testing. Microsoft will also release Windows Server 2008 at the same time.

Expected updates/fixes included with SP1 will be a revised Desktop Search, faster file copying and shutdown speeds, support for SD Advanced Direct Memory Access, enhancements to BitLocker Drive Encryption and Extensible Firmware Interface (EFI) support on x64 machines.

There will also be changes made to Windows ReadyBoost. There have been numerous complaints around the web concerning ReadyBoost and resuming from S3/S4 sleep. Sluggish performance on resume can be attributed to numerous writes to 'Readyboost.sfcache' on the ReadyBoost storage device.

According to Microsoft’s Robert Hensing, "[ReadyBoost] uses an AES 128 key that is generated once per OS start (the data in the file on the thumb drive is encrypted with this key) . . . the key isn't persisted anywhere (i.e. it lives in memory only) and so apparently when you sleep / hibernate - the key goes bye bye and thus you need to rebuild your 2GB ReadyBoost cache on your USB disk when you resume again."

Hensing continues, "Vista realizes that it needs to regenerate the ReadyBoost cache as soon as it wakes up and loads the USB drivers and realizes the ReadyBoost drive is plugged in and it starts helpfully doing this as soon as it can . . . ya know - while the OS is trying to page all that memory back into my 2GB of system RAM as well and generally restore the OS to a working state  . . . sigh . . ."

The changes made to ReadyBoost in SP1 will ensure that cache data is reused during S3/S4 sleep so that 'Readyboost.sfcache' is not repopulated on resume.

Comments     Threshold

This article is over a month old, voting and posting comments is disabled

By kilkennycat on 7/9/2007 5:03:43 PM , Rating: 2
... (whether financial-incentive, technical or both) to 3rd-party developers for the release of Vista patches for existing mature XP applications. Many 3rd-party developers are not providing patches for existing fully-functional XP applications to run on Vista without errors and are delaying any Vista upgrades until their next full product refresh, for which they will charge mucho, mucho $$$ .... Adobe is a classic example. And many peripheral hardware developers ( e.g Matrox) have stated categorically for even their latest product line that they have no intention of supporting Vista unless there is a ground-swell of customer-feedback to force them to do so. And since much of this hardware/apps works just fine under XP, where is this ground-swell going to come from?? Classic Chicken 'n Egg. Seems as if the only way for Microsoft to break the Vista log-jam with key 3rd party developers is to offer a cash incentive and full technical support such that a Vista upgrade for existing applications is at least a cash-neutral prospect for the developer.

The fundamental problem for Microsoft is that XP is far more stable than any previous MS operating system and XP applications when fully debugged at the application level run extremely well. Thus no developer or customer incentive to upgrade... expecially in government departments with widespread 3rd-party software deployment under XP --- where a major upgrade to a new OS requires many months (or years) of time and money reinvestment in test and validation. If Vista had a user-selectable 100%-compatible XP mode, then Microsoft would have successfully built an applications-bridge for the OS, but Microsoft took their usual too-arrogant view of their OS development and burnt all such bridges when they developed Vista. And the OS-security issues in XP overblown by the media (and MS themselves in pushing Vista) have turned out to be low on the customer-priority list. Far lower than ensuring existing applications continue to work flawlessly regardless of OS change.

By TomZ on 7/9/2007 5:15:10 PM , Rating: 2
In my experience, I haven't come across any XP apps or drivers (with one exception) that I couldn't get to run properly in Vista using the compatibility settings.

The one driver exception I found is a Netgear driver for a non-Vista supported network card, and I think they updated their driver to specifically check the operating system, and it quits immediately upon seeing Vista. The previous version of the same driver worked fine in Vista.

I think that the real problem is that many software and hardware vendors see the potential windfall in basically forcing customers to upgrade their software and/or hardware to newer versions for Vista. So they tell customers their current hardware and/or software doesn't support Vista, and ask them to buy new hardware and/or upgrade to newer software versions. Even though in most cases, the older stuff would actually work fine in XP compatibility mode.

By RaisedinUS on 7/9/2007 11:26:32 PM , Rating: 2
I have had Vista since the business release. I installed it on a separate drive to play with. I have a lot of broadcast software, audio software that I paid a bit for that won't work well with Vista. SAM broadcaster and fleximusic are but a few programs that just don't play nice with Vista. Sam works fine until you try to use your mic, then all you get is a garbled mess. Several of my DJ's have had the same experience.
I won't completely change over until either the programs are updated to work properly or I can afford to buy the Vista versions of the programs.Maybe the SP will help. That being said, I have no problems with Vista.

By sxr7171 on 7/10/2007 4:08:56 AM , Rating: 2
It's like the circle of life.

"I'm an Internet expert too. It's all right to wire the industrial zone only, but there are many problems if other regions of the North are wired." -- North Korean Supreme Commander Kim Jong-il

Copyright 2016 DailyTech LLC. - RSS Feed | Advertise | About Us | Ethics | FAQ | Terms, Conditions & Privacy Information | Kristopher Kubicki