Monday, June 8, 2009

Windows Vista's biggest problem

Windows Vista has two main problems which are the following:--

1. Driver problems
Since Windows Vista's launch, the drivers have been a big issue. Lots of hardware components (old and new) had no drivers for Windows Vista or, even if they had, their quality was very poor. One of the most prominent examples is Nvidia. When the GeForce 8800 graphic cards were launched, they were labeled as "Designed for Windows Vista". It is only natural that many people asumed the graphic cards would work well with this operating system. Unfortunately that was not the case, as the Nvidia drivers had lots of issues. There were numerous posts on Nvidia's official forums commeting the bad state of the drivers. Some users even built internet pages such as nvidiaclassaction.info to gather evidence for a class action suit.
Since then, Nvidia worked hard on the Windows Vista drivers and released many new and improved versions. However, their latest driver - Forceware version 158.24 - still has plenty of issues. For example, popular games such as World of Warcraft have low frame rates while others crash during play or have corrupted textures.

Nvidia is not the only company that has these issues. Other big hardware manufacturers such as Creative, renown for their sound cards and sound systems, have similar problems. When Windows Vista was launched, their drivers were mostly in beta stages. Even though they released so called "final versions", their drivers had plenty of issues. Lots of users complained on the official forums and, after a while, Creative announced the ALchemy Project - a project that aims to offer complete DirectSound3D support for Sound Blaster X-Fi products in Windows Vista. Unfortunately, old sound cards such as the Audigy 2 series are not yet supported. Due to lots of users' request, they started the development of ALchemy for Audigy sound cards. However, according to Creative, this products will be offered as a "low-cost" upgrade.

2. Application compatibility
Drivers are not the only problem. Lots of applications do not work either on the new Microsoft operating system. That's because many software developers created applications that function only if the user has full administrative privileges. With the introduction of UAC (User Access Control) and other system changes, lots of old applications have problems. The most prominent example of an application that was incompatible with Windows Vista is iTunes. Whenever the Windows Vista "Safely Remove Hardware" feature was used, it corrupted the user's iPods, requiring a full restore. Also, iTunes text and graphics had display issues with Windows Vista. However, upgrading to iTunes v7.2 or higher solves these issues.

Thursday, June 4, 2009

Microsoft Disclose Office and Exchange 2010

At it's virtual press conference on 15 April, Microsoft is back on the new version of its Office productivity suite, Office 2010 now known and not Office 14. Besides this detail, the publisher insisted on its willingness to include its applications in its SaaS strategy, which is software plus services.The components of the office suite (Word, Excel, PowerPoint) expected for next year will be accessible both through a traditional thick client, a web browser or mobile phone. Microsoft talking about ubiquity, since user should have access to his office by the way he chooses.

Support for PDF and ODF:--
It may therefore choose between three web browsers on the market. The editor explained to have worked on interoperability by making its web applications also compatible with Safari or Firefox. Also in the field of interoperability, Office 2010 natively support ODF and PDF formats.

To access the online applications, Microsoft ensures that the installation of the Silverlight plug-in will not be necessary. Nevertheless, it allows the user to have better reporting and access to certain functions like being able to zoom in on a document. If Silverlight is not imposed, usability of web applications Microsoft still seems to depend on it. But it is more especially on the new version of its mail server, and client, Outlook 2010, Microsoft released more details, particularly in terms of functionality.

RMS rules to prevent data leakage:--
Launched in beta April 15, Exchange 2010 should be commercially available by fall. Among the novelties, the administrator should be able to count on an improvement in performance with SATA (Microsoft have worked on ensuring the management of I / O). Exchange 2010 also allows the delegation of rights.

An administrator will be able to authorize a service company to perform certain operations, like create an account due to a recruitment. A delegation to the user also takes place, allowing it through a Web interface to create such groups. On security, Exchange 2010 will feature centralized archiving, not only locally on the client. Strand protection and data leakage is covered by rules RMS (Right Management Services) at the transmission of messages. RMS model can also be applied to key words.

Exchange 2010 will be accompanied by a new Outlook mail client. The new Outlook 2010 are divided into three main categories: information management, voice mail, collaboration.

Wednesday, June 3, 2009

Repair Windows Vista update problems using CheckSUR

The Windows Vista Check for System Update Readiness (CheckSUR) tool will try to fix certain Windows Update installation failures. System resources, such as file data, registry data, and even in-memory data, can develop inconsistencies during the lifetime of the operating system. These inconsistencies may be caused by various hardware failures or by software issues. In some cases, these inconsistencies can affect the Windows Servicing Store, and they can cause a Windows Vista update to fail. When the update fails, it blocks the user from installing updates and service packs.

When Windows Update detects inconsistencies that are related to system servicing in system files or in the registry, Windows Update offers CheckSUR as an available update package. The package titles are as follows :--
• Update for Windows Vista (http://support.microsoft.com/kb/947821)
• Update for Windows Vista for x64-based Systems (http://support.microsoft.com/kb/947821)

Note This Windows Update or Automatic Update package will only be offered if such inconsistencies have been detected on the system. CheckSUR should run automatically after it has been installed from Windows Update.
To manually install and run CheckSUR, follow these steps :--

1. Click Start , click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
2. In the User Account Control dialog box, click Continue.
3. Type reg add HKLM\COMPONENTS /v StoreCorruptTimeStamp /t REG_SZ /d “0″ /f, and then press ENTER.
4. Type reg delete HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\CheckSUR\, and then press ENTER.
5. Download and then install CheckSUR from the Microsoft Download Center.
6. As soon as the file has been successfully downloaded, double-click the file to install and run CheckSUR.

We recommend that you restart your computer after you run CheckSUR to make sure that any changes take effect. Additionally, you must try to reinstall any software updates that previously could not be installed. If CheckSUR detected and fixed the cause of the failures, these updates will now install successfully. CheckSUR creates a log file that captures the issues, if any exist, that were found or fixed. The log file will be located at %WINDIR%\Logs\CBS\CheckSUR.log.

CheckSUR is run by Windows Update after you install KB947821. Windows Update can take as long as 10 to 15 minutes to complete this scan. The time may be significantly longer on some computers. However, the Windows Update progress bar is not updated while this process is running, and it will not move. This means that the Windows Update progress bar may indicate that it is 0 percent complete, or 20 percent complete, and so on, for some time. This behavior is expected, and you should not cancel the update. If you cancel the update, some problems may not be identified, and this package may have to run again.