indonesia

Download NVIDIA Quadro/Tesla Driver 276.14 WHQL

Sabtu, 08 Oktober 2011

It wasn't too long ago that NVIDIA released its newest Beta desktop and notebook display driver for GeForce and ION graphics, but now the company has brought forth a different software package, for the Quadro and Tesla product series.

The NVIDIA Quadro/Tesla Driver Release 276.14 WHQL is the latest installment of the enterprise-aimed software.

It does several things, not the least of which is adding 10-bit Greyscale support through DVI for Windows 7 (medical displays are one example where this helps).

Another useful thing is the implementation of G-Sync, which allows Direct3D application to synchronize back buffer presents across more than one GPU in a system, or even multiple systems, for both full-screen and multi-window programs.

Furthermore, the package installs a new OpenGL path rendering API, which allows OpenGL applications to render high-quality 2D and text.

Furthermore, the R275 ODE 'Optimal Drivers for Enterprise’ drivers are installed, as is the NVIDIA WMI service.

One will also benefit from updated NVIDIA Control Panel options to both the display and workstation sections.

All these and more are offered on top of the already existing support for CUDA 4.0, OpenGL 4.1, DirectX 11 and the Open Computing Language (OpenCL) 1.0 (this final asset is present only on the Quadro FX Series x700 and newer, as well as the FX4600 and FX5600).

These features are described in detail on the download pages listed below, so enterprise users who own a Quadro or Tesla product, or an NVS series, need only follow the appropriate links to the full list of changes.

NVIDIA Quadro/Tesla Display Driver 276.14 WHQL for XP
NVIDIA Quadro/Tesla Display Driver 276.14 WHQL for Vista/Windows 7 NVIDIA Quadro/Tesla Display Driver 276.14 WHQL for Vista64/Windows x64

Explaining the Configurations Uranus and Mercury

Astronomers have been struggling to explain numerous odd properties displayed by Mercury and Uranus for many years now, but leading theories were just discredited over the past few days. Now, astronomers begin to search for new explanations of what actually happened.

This line of inquiry is very difficult to push forward, since obtaining answers would require a deep understanding of how the solar system looked like in its earliest days, when the planets were just forming. This is obviously impossible to figure out in minute detail.

In other words, the way the solar system and its planets look like now was decided more than 4 billion years ago. The thing that puzzles experts most about Mercury is its large iron core, which lies close to the surface, Similarly, they cannot explain why Uranus lies at a steep angle while orbiting the Sun.

In the past, scientists have proposed that a huge portion of Mercury's crust may have been stripped away following a monumental cosmic collision that involved another protoplanet in the early solar system.

The same type of event may have contributed to tilting Uranus' axis in orbit, forcing the gas giant to exhibit its current weird looks. But these scenarios fell in 2011, as new data became available for study.

The NASA Mercury Surface, Space Environment, Geochemistry and Ranging (MESSENGER) space probe provided data that utterly contradict the impact theory for the solar system's innermost planet.

As for Uranus, the thing that drove the final nail through the previous theory's coffin was the discovery that its moons still orbited in its equatorial plane. If an impactor had slammed the gas giant, then the moons would have had no reason to be in this position.

According to University of California in Santa Barbara (UCSB) physicist Stanton Peale, the impact hypothesis also can't explain why Pluto's moons orbit so weirdly around the dwarf planet. At a recent convention, astronomers proposed new explanations for the oddities these space bodies display.

Harvard University planetary scientist Sarah Stewart said that Mercury could have been impacted by another object in a manner that allowed it to retain the volatile compounds MESSENGER discovered.

The announcement was made a joint meeting of the European Planetary Science Congress and the Division for Planetary Sciences of the American Astronomical Society, ScienceNow reports.

French astronomer Alessandro Morbidelli, who is based at the Observatoire de la Côte d'Azur in Nice, also presented new data to indicate what kind of impact may have modified the entire Uranian system the way it did.

“You only lose volatiles if they somehow can get separated from the heavier, more refractory elements. For instance, our own moon is low in volatile elements because it slowly coalesced from a churning, hot disk of material surrounding the Earth,” Stewart says.

“But in the case of Mercury, the impact debris cooled pretty quickly, so most of the potassium and sulfur was preserved,” the expert adds, thus explaining MESSENGER's readings.

In turn, Morbidelli proposed that Uranus was indeed affected by a collision, but argued that the event occurred significantly earlier in time than first calculates. At the same time, changing this planetary system required multiple impacts.

“In the early days of the solar system, there may have been many hundreds of protoplanets drifting around in the system's outer regions. Giant collisions were, of course, more likely to occur very early on,” the astronomer concluded.

Microsoft Security Essentials 2.1 Updated to Resolve Chrome False Positive

free download Microsoft Security Essentials 2.1 has been updated in order to resolve a false positive involving Google’s open source browser, Chrome.

At the end of September 2011, MSE 2.1 began incorrectly detecting Chrome as malware, notifying users that they were infected with PWS:Win32/Zbot.

Microsoft Security Essentials 2.1 recommended that users remove the newly identified piece of malicious code, and deleted Chrome for those that agreed to get rid of PWS:Win32/Zbot.

Furthermore, the Redmond company’s free security solution for Windows also blocked installations of Chrome, warning users that their machines were at risk of infection from PWS:Win32/Zbot.

Once users began complaining about the issues they were coming across with Microsoft Security Essentials and Chrome, the software giant confirmed the problem and reacted quickly to resolve it.

The signatures of Microsoft Security Essentials were updated, and provided that the refresh is installed, Chrome is no longer detected as PWS:Win32/Zbot.

“On September 30th, 2011, an incorrect detection for PWS:Win32/Zbot was identified and as a result, Google Chrome was inadvertently blocked and in some cases removed. Within a few hours, Microsoft released an update that addresses the issue,” the company said.

“Signature versions 1.113.672.0 and higher include this update. Affected customers should manually update Microsoft Security Essentials with the latest signatures. After updating the definitions, reinstall Google Chrome. We apologize for the inconvenience this may have caused our customers.”

It sounds like this was simply a case of false positive due to incorrect virus signatures. According to AV-Test, Microsoft Security Essentials is one of the top security solutions worldwide efficiency-wise.

This means that MSE usually has a very low number of false positives, false warnings and false blockings, zero in fact, the vast majority of the time.

Here is what MSE 2.1 was thinking it was detecting instead of Chrome: “PWS:Win32/Zbot is a password-stealing trojan that monitors for visits to certain websites. It allows limited backdoor access and control and may terminate certain security-related processes,” Microsoft said.

Release Date: September 8, 2011 GOM Player 2.1.33.5071 (8.74MB)

System Requirements

Microsoft Windows 98SE, Me, 2000, XP, 2003, Vista or Windows 7
Intel-compatible CPU P3 or greater Minimum amount of RAM recommended by the operating system in use 20MB Hard Drive Space.
Some videos may require the newest version of DirectX or Windows Media Player.
Recommended settings may change according to different types of video files.
Modify 'Deadlock problem' occasionally happened when you shut down the player.
Improve Vorbis audio decoder performance.

FREE DOWNLOAD GOM

Camera (10) Version V5.8.54000.206 ASUS k42

Jumat, 07 Oktober 2011

Description Azurewave Camera Driver
Azurewave Camera Driver for WIN7 32 bit

1. Please refer to below FAQ to check your camera's PID code and install the driver correctly:

http://support.asus.com/Search/KDetail.aspx?SLanguage=en&no=DACB9270-6382-BC3B-5B91-50900D9F0041&t=2FREE DOWNLOAD