Get Paid To Promote, Get Paid To Popup, Get Paid Display Banner

Friday, April 13, 2012

Android C2DM — Client Login key expiration

[This post is by Francesco Nerieri, engineering team lead for C2DM — Tim Bray]

In the upcoming weeks, some of the older Client Login authentication keys will expire. If you generated the token you’re currently using to authenticate with the C2DM servers before October 2011, it will stop working.

If the response from the C2DM servers contains an Update-Client-Auth header, you’ll need to replace the current token with the one included in the header.

  // Check for updated token header
String updatedAuthToken = conn.getHeaderField(UPDATE_CLIENT_AUTH);
if (updatedAuthToken != null && !authToken.equals(updatedAuthToken)) {
log.info("Got updated auth token from datamessaging servers: " +
updatedAuthToken);
serverConfig.updateToken(updatedAuthToken);
}

We suggest that you start using the Update-Client-Auth response header to update tokens regularly, as keys will expire periodically from now on. For example, have a look at the Chrome to Phone service hosted on code.google.com; this code takes care of authenticating via Client Login and then sending a message:

Alternatively, you can manually generate a new Client Login token now and replace the one currently in use. ClientLogin can be used with any application that can make an HTTPS POST request. The POST request should be structured as a form post with the default encoding application/x-www-form-urlencoded, like this:

POST /accounts/ClientLogin HTTP/1.0
Content-type: application/x-www-form-urlencoded

accountType=GOOGLE&Email=johndoe@gmail.com&Passwd=north23AZ&service=ac2dm

If the POST succeeds, the response contains the authorization token, labeled "Auth", which is your new token. You could even do this from the command line:

curl -d \
"accountType=HOSTED_OR_GOOGLE&Email=johndoe@gmail.com&Passwd=north23AZ&service=ac2dm" \
https://www.google.com/accounts/ClientLogin | \
grep Auth

If your request fails or if you are prompted for captchas, please read ClientLogin for Installed Applications. And of course, if you updated your code to use the Update-Client-Auth header after the keys had expired, then you will first need to manually generate a new token.

Have fun with C2DM!

Thursday, April 12, 2012

New Seller Countries in Google Play

Over the past year we’ve been working to expand the list of countries and currencies from which Android developers can sell their products. Starting today, developers in Czech Republic, Israel, Poland, and Mexico can sell priced applications and in-app products on Google Play, using their local bank accounts for payments. Welcome developers!



If you develop Android apps in one of the new countries and want to get started selling them, visit play.google.com/apps/publish and set up a new Google Play developer account. Once you’ve uploaded your apps, you can price them in any available buyer currencies, publish, and then receive payouts and financial data in your local currency.



If you are based in Israel or Mexico and are currently selling apps through an AdSense merchant account, you will need to migrate your apps to a new Google Play developer account in your local currency. Watch for an email that provides complete information on the migration process and timeline.



Additionally, we encourage developers everywhere to visit the Developer Console as soon as possible to set prices for their products in the currencies of these new countries. Stay tuned for more announcements soon as we continue to roll out our new billing infrastructure to buyers and sellers throughout the world.



Join the discussion on

+Android Developers



Tuesday, April 10, 2012

Accessibility: Are You Serving All Your Users?

[This post is by Joe Fernandez, a technical writer for developer.android.com who cares about accessibility and usability. — Tim Bray.]

We recently published some new resources to help developers make their Android applications more accessible:

“But,” you may be thinking, “What is accessibility, exactly? Why should I make it a priority? How do I do it? And most importantly, how do I spell it?” All good questions. Let’s hit some of the key points.

Accessibility is about making sure that Android users who have limited vision or other physical impairments can use your application just as well as all those folks in line at the supermarket checking email on their phones. It’s also about the Mom over in the produce section whose kids are driving her to distraction, and really needs to see that critical notification your application is trying to deliver. It’s also about you, in the future; Is your eyesight getting better over time? How about that hand-eye coordination?

When it comes down to it, making an application accessible is about having a deep commitment to usability, getting the details right and delighting your users. It also means stepping into new territory and getting a different perspective on your application. Try it out: Open up an application you developed (or your all-time favorite app), then close your eyes and try to complete a task. No peeking! A little challenging, right?

How Android Enables Accessibility

One of main ways that Android enables accessibility is by allowing users to hear spoken feedback that announces the content of user interface components as they interact with applications. This spoken feedback is provided by an accessibility service called TalkBack, which is available for free on Google Play and has become a standard component of recent Android releases.

Now enable TalkBack, and try that eyes-closed experiment again. Being able to hear your application’s interface probably makes this experiment a little easier, but it’s still challenging. This type of interaction is how many folks with limited vision use their Android devices every day. The spoken feedback works because all the user interface components provided by the Android framework are built so they can provide descriptions of themselves to accessibility services like TalkBack.

Another key element of accessibility on Android devices is the ability to use alternative navigation. Many users prefer directional controllers such as D-pads, trackballs or keyboard arrows because it allows them to make discrete, predictable movements through a user interface. You can try out directional control with your apps using the virtual keyboard in the Android emulator or by installing and enabling the Eyes-Free Keyboard on your device. Android enables this type of navigation by default, but you, as a developer, may need to take a few steps to make sure users can effectively navigate your app this way.

How to Make Your Application Accessible

It would be great to be able to give you a standard recipe for accessibility, but the truth of the matter is that the right answer depends on the design and functionality of your application. Here are some key steps for ensuring that your application is accessible:

  1. Task flows: Design well-defined, clear task flows with minimal navigation steps, especially for major user tasks, and make sure those tasks are navigable via focus controls (see item 4).

  2. Action target size: Make sure buttons and selectable areas are of sufficient size for users to easily touch them, especially for critical actions. How big? We recommend that touch targets be 48dp (roughly 9mm) or larger.
  3. Label user interface controls: Label user interface components that do not have visible text, especially ImageButton, ImageView, and EditText components. Use the android:contentDescription XML layout attribute or setContentDescription() to provide this information for accessibility services.

  4. Enable focus-based navigation: Make sure users can navigate your screen layouts using hardware-based or software directional controls (D-pads, trackballs and keyboards). In a few cases, you may need to make UI components focusable or change the focus order to be more logical.

  5. Use framework-provided controls: Use Android's built-in user interface controls whenever possible, as these components provide accessibility support by default.

  6. Custom view controls: If you build custom interface controls for your application, implement accessibility interfaces for your custom views and provide text labels for the controls.

  7. Test: Checking off the items on this list doesn’t guarantee your app is accessible. Test accessibility by attempting to navigate your application using directional controls, and also try eyes free navigation with the TalkBack service enabled.

Here’s an example of implementing some basic accessibility features for an ImageButton inside an XML layout:

<ImageButton
android:id="@+id/add_note_button"
android:src="@drawable/add_note_image"
android:contentDescription="@string/add_note_description"/>

Notice that we’ve added a content description that accessibility services can use to provide an audible explanation of the button. Users can navigate to this button and activate it with directional controls, because ImageButton objects are focusable by default (so you don’t have to include the android:focusable="true" attribute).

The good news is that, in most cases, implementing accessibility isn’t about radically restructuring your application, but rather working through the subtle details of accessibility. Making sure your application is accessible is an opportunity to look at your app from a different perspective, improve the overall quality of your app and ensure that all your users have a great experience.

Monday, April 9, 2012

A Faster Emulator with Better Hardware Support

[This post is by Xavier Ducrohet and Reto Meier of the Android engineering team. — Tim Bray.]

The Android emulator is a key tool for Android developers in building and testing their apps. As the power and diversity of Android devices has grown quickly, it’s been hard for the emulator keep pace.

Today we’re thrilled to announce several significant improvements to the emulator, including a dramatic performance upgrade and support for a broader range of hardware features, notably sensors and multi-finger input.

Added GPU Support

The system image we’re shipping today has built-in GPU support (Android 4.0.3 r2). With Android’s growing reliance on using the GPU to improve performance, the difference is significant. In the video below, the emulator is still interpreting ARM instructions; the performance boost is the effect of putting the GPU to work.


As a bonus, since we’re now supporting OpenGL ES 2.0, your OpenGL games can now run inside the emulator.

Please note that there are a lot of GPUs out there, and we haven’t tested all of them for this beta release, so let us know if you have feedback or encounter issues.

More Hardware Feature Emulation

The hardware features of mobile devices are a significant part of what makes them a unique platform for development, so we’re also pleased to announce that in addition to the camera support we added last year, it’s now possible to use a tethered Android device to supply inputs for sensors and multi-touch input.

We’re working on providing emulator support for more hardware features including Bluetooth and NFC.

Improved CPU Performance

We’ve also improved the CPU performance of the Android emulator. Hardware floating point operation has been available for system images since Ice Cream Sandwich (Android 4.0), allowing CPU operations to be emulated roughly twice as quickly.

Last week’s r17 developer tools release included x86 system images and host drivers (available through the SDK Manager), allowing the emulator to access the host CPU natively and offer significantly faster execution.

This video shows a CPU-bound application on two emulators running the same system image, one with virtualization, one without.

Building a modern emulator

Because the Android platform allows deep interaction between applications, and with system components, we need to provide an emulator with a complete system image. Our emulator virtualizes a complete device: hardware, kernel, low-level system libraries, and app framework.

Of course, the system being emulated typically has an ARM CPU; historically, we’d been emulating those instructions in software, and that worked OK until the advent of tablet support with additional animations and complexity in Android 3.0.

The missing pieces were the completion of Android x86 support, and the GPU support in last week’s release of SDK Tools r17. This works by funneling the OpenGL ES 2.0 instructions from the emulator to the host OS, converted to standard OpenGL 2.0, and running natively on the host GPU.

Conclusion

The Android ecosystem has a lot of devices in many different form factors. Developers need a good way of testing these apps without having to own everything out there and a fast, rich Android emulator is immensely helpful.

We hope that these new improvements will make the emulator a more useful tool in your development and testing, and look forward to improving it further for you.

Tuesday, April 3, 2012

The Gmail Public Labels API

[This post is by Nadav Aharony, a product manager on the Android team — Tim Bray]

We’re rolling out new developer features for the Gmail Android app: It now includes a public ContentProvider that you can use to retrieve label data. You can use this to access up-to-date unread counts for specific accounts’ inboxes and labels.

To use the API, the Gmail app needs to be at version 2.3.6 or higher on Froyo or Gingerbread; 4.0.5 or higher on Honeycomb and ICS. Before using it, be sure you first check the Gmail app version; we’ve provided a handy GmailContract.canReadLabels(Context) method to help with this. Your app will need the com.google.android.gm.permission.READ_CONTENT_PROVIDER permission.

Finding the Gmail accounts set up on the device

The Labels API needs a valid Gmail account to build a query for per-label information. Assuming the GET_ACCOUNTS permission, the AccountManager can be used to fetch this information:

// Get the account list, and pick the first one
final String ACCOUNT_TYPE_GOOGLE = "com.google";
final String[] FEATURES_MAIL = {
"service_mail"
};
AccountManager.get(this).getAccountsByTypeAndFeatures(ACCOUNT_TYPE_GOOGLE, FEATURES_MAIL,
new AccountManagerCallback() {
@Override
public void run(AccountManagerFuture future) {
Account[] accounts = null;
try {
accounts = future.getResult();
if (accounts != null && accounts.length > 0) {
String selectedAccount = accounts[0].name;
queryLabels(selectedAccount);
}

} catch (OperationCanceledException oce) {
// TODO: handle exception
} catch (IOException ioe) {
// TODO: handle exception
} catch (AuthenticatorException ae) {
// TODO: handle exception
}
}
}, null /* handler */);

Getting and accessing existing labels

Once you’ve got the email account, you can get a ContentProvider URI to query against. We've provided a simple support class called GmailContract.java for constructing the URI and defining the columns and relevant constants.

You can access any label, predefined or user-defined. The predefined labels include (you have to use symbolic constants rather than these strings, see below):

  • Priority Inbox

  • Starred

  • Chats

  • Sent

  • Drafts

  • All mail

  • Spam

  • Trash

To obtain a Cursor with information for all labels in an account, your app can either query this URI directly or use a CursorLoader. Here’s an example:

Cursor c = 
getContentResolver().query(GmailContract.Labels.getLabelsUri(selectedAccount),
null, null, null, null);

You can query and watch for changes on a single label by storing the URI value in the GmailContract.Labels.URI column from the cursor data.

The NAME value for pre-defined labels can vary by locale, so don’t use GmailContract.Labels.NAME. Instead, identify pre-defined labels like Inbox, Sent or Drafts using the String value in the GmailContract.Labels.CANONICAL_NAME column. Here’s an example:

// loop through the cursor and find the Inbox
if (c != null) {
final String inboxCanonicalName = GmailContract.Labels.LabelCanonicalName.CANONICAL_NAME_INBOX;
final int canonicalNameIndex = c.getColumnIndexOrThrow(GmailContract.Labels.CANONICAL_NAME);
while (c.moveToNext()) {
if (inboxCanonicalName.equals(c.getString(canonicalNameIndex))) {
// this row corresponds to the Inbox
}
}
}

If you choose to use a CursorLoader, it will keep the label counts up to date as they change over time.

Sample App

You can find a sample app that makes use of the new API here. The app provides a basic readout of label and message-count information.

People care about their incoming mail; we’re looking forward to seeing what you do with access to this information. We’re also open to suggestions as to how to improve and extend this new API.

Thursday, March 29, 2012

Making the Android Developer Console work for your whole team

[This post is by Ellie Powers, a product manager on the Google Play team. — Tim Bray]

As your apps have gotten more successful, more people have joined your team. Today, we’re making it easier to work together on analyzing and managing your published Android apps. Sharing passwords is generally a bad idea; so as of now, there’s no need to do that for the Android Developer Console — everyone can use his or her own Google account.



The account that you use today to sign into the Android Developer Console will become the account owner; only the account owner can manage access to the Console. The account owner can email an invitation to anyone; when they accept it, they’ll need to use a Google account to sign in.



Different people in your team do different jobs, so when you invite someone to your Android Developer Console, you’ll be able to specify what access they need. Today, you can limit access per-user to financial reports. In the future, we’ll give you more fine-grained control over access to the Console. For details, see Account owner and user access.



We hope this helps your team collaborate more easily. If you have any issues, feel free to get in touch via the Developer Help Center.



Join the discussion on

+Android Developers



Thursday, March 22, 2012

New Sales Reports on Google Play



[This post is by Debashish Chatterjee, Krishna Atkuru, and Ellie Powers of the Google Play Publisher Site team. —Dirk Dougherty]



For app publishers, complete and timely sales reporting is incredibly useful for managing a business on Google Play. Today we are introducing a new financial tool — Estimated Sales Reports — to give you visibility over ongoing product sales and help you support customers between payout cycles.



The new sales reports show you complete transaction details of recent sales and refunds for all products in your developer account, including both in-app products and paid apps. Each report is a cumulative for the current payout period, updated nightly with the details of recent transactions. As customers complete purchases and their accounts are charged (or refunds are applied), the new transaction details are appended to the Estimated Sales Report. Depending on account timezone differences, transactions appear on the estimated sales report within 2 days of completion. Finally, at the close of the monthly payout cycle, the current Estimated Sales Report is archived and a new report is created for the next cycle.





You can access current or past sales reports from the “Merchant Reports” section of the Developer Console. The Estimated Sales Reports are downloadable CSV (comma-separated values) files, so you can analyze the data using any tools you choose, in the same way as you've been doing for payout reports. The sales reports list the same details as payout reports — buyer and order, product, device information, amount, currency of sale, and more — except without final payment details. This makes it easier for you to reconcile recorded sales against your actual payouts. Estimated sales reports are available with data starting February 1, 2012.



We’ve also taken this opportunity to rename our existing “Merchant Sales Reports” to Monthly Payout Reports, to better reflect their content.



Together with the application statistics introduced last month, the Estimated Sales and Monthly Payout Reports give you a more complete view of your products’ download and sales activity over time. We hope you’ll find them useful. As always, please feel free to give us feedback through the Developer Help Center.



Join the discussion on

+Android Developers



Wednesday, March 21, 2012

Updated SDK Tools and ADT revision 17

Today we are releasing an update to the SDK Tools and the Eclipse plugin. Revision 17 brings a lot of new features and bug fixes in various areas such as Lint, the build system as well as the emulator.

Lint is a static checker which analyzes Android projects for a variety of issues around correctness, security, performance, usability and accessibility, checking your XML resources, bitmaps, ProGuard configuration files, source files and even compiled bytecode. It can be run from within Eclipse or from the command line.
New for r17:

  • Added check for Android API calls that require a version of Android higher than the minimum supported version. You can use the new @TargetApi annotation to specify local overrides for conditionally loaded code. For more information, read here.
  • Added over 40 new Lint rules for a total of over 80, including checks for performance, XML layouts, manifest and file handling. For a full list read here.
  • Added ability to suppress Lint warnings in Java code with the new @SuppressLint annotation, and in XML files with the new tools: namespace prefix and ignore attribute. For more information, read here.
  • Improved HTML and XML reporting and Eclipse integration. For more information, read here.

We’ve also made improvements to the build systems for Eclipse and Ant:

  • Added strict dependency support for 3rd party Jar files. You can read more information here.
  • Added support for custom views with custom attributes in libraries. Layouts using custom attributes must use the namespace URI http://schemas.android.com/apk/res-auto instead of the URI that includes the app package name. This URI is replaced with the app specific one at build time.
  • Added a feature that allows you to run some code only in debug mode. Builds now generate a class called BuildConfig containing a DEBUG constant that is automatically set according to your build type. You can check the (BuildConfig.DEBUG) constant in your code to run debug-only functions such as outputting debug logs.

The emulator is seeing some big improvements as well:

  • Thanks to contributions to AOSP from Intel, the emulator now supports running x86 system images in virtualization mode on Windows and Mac OS X. This allows the emulator running at near native speed. The drivers are available through the SDK Manager. Read more here.
  • After adding webcam support and sensor emulation, we are adding experimental support for Multi-Touch input through a tethered Android device. (Read more here)

Finally, we are also releasing an updated Support Library with the following improvements:

  • ShareCompat provides easy helper classes for both sending and receiving content for social sharing apps.
  • NavUtils and TaskStackBuilder provide cross-version support for implementing the Android Design guidelines for navigating within your app including the action bar's "Up" button.
  • NotificationCompat.Builder provides a compatibility implementation of Android 3.0's Notification.Builder helper class for creating standardized system notifications.
  • A new Library Project adds support for GridLayout back to API level 7 and higher.

You can get more information about these changes in the SDK Tools Release Notes and ADT Release Notes.

Tuesday, March 13, 2012

Unifying Key Store Access in ICS

[This post is a group effort by Tony Chan, Fred Chung, Brian Carlstrom, and Kenny Root. — Tim Bray]

Android 4.0 (ICS) comes with a number of enhancements that make it easier for people to bring their personal Android devices to work. In this post, we’re going to have a look at the key store functionality.

Back in Android 1.6 (Donut), a system key store was added for use by VPN. Although this was later expanded to support WiFi authentication, applications weren’t able to access it.

In the past, it was common practice for apps to maintain their own key store if they needed to authenticate a secure SSL web server, or authenticate the user to a server via a client certificate. While this works, it can present manageability issues in an enterprise environment where multiple certificates may be shared across a number of apps such as Email and Browser.

New in ICS: KeyChain

To bridge the gap in ICS, there’s a new API named KeyChain that regulates application access to the system key store and allows users to grant application access to the credentials stored there. Additionally, this API enables applications to initiate installation of credentials from X.509 certificates and PKCS#12 key stores.

The KeyChain API is rather simple. To install a key store or a certificate, you retrieve an install intent, supply the raw bytes of the credentials, and use the intent to launch a system installation dialog. If it’s a keystore, as in the example below, you’ll need provide the data in PKCS#12 format, and the user will have to know the PKCS#12 password.

  byte[] keystore = . . (read from a PKCS#12 keystore)

Intent installIntent = KeyChain.createInstallIntent();
installIntent.putExtra(KeyChain.EXTRA_PKCS12, keystore);
startActivityForResult(installIntent, INSTALL_KEYSTORE_CODE);

The install intent launches a system dialog that prompts the user to enter the password for the keystore.

This can also be used for installing organizational CA certificates which will then be trusted by all applications to authenticate to non-public servers with certificates issued by the same CA.

In ICS, Android no longer requires a separate password to protect the system credential storage. Rather, it uses the screen lock password for this purpose, and the Android Device Administration API can be used for central policy enforcement. This means, for example, that the screen lock password can’t be removed as long as the secured credentials remain on the device.

Accessing System Key Store Credentials

Once the system key store is configured, the KeyChain API offers functions such as requesting a client certificate for authenticating with an SSL server. The first time an application requests access, the user is prompted with a list of available certificates and can select one to grant access to that certificate to the application. If the user chooses to allow access to a certificate, a string alias name for the certificate is returned to the application. The application can then use the alias to access the certificate in the future without further user involvement.

The code below illustrates how an application can prompt the user to select a credential alias and grant access to the application. KeyChain will remember this selection such that the same application can save the credential alias selection and have access to the same certificate in future. For example, the Email application for ICS has implemented this feature in its Server Settings screen.

  KeyChain.choosePrivateKeyAlias(this,
new KeyChainAliasCallback() {

public void alias(String alias) {
// Credential alias selected. Remember the alias selection for future use.
if (alias != null) saveAlias(alias);
}
},
new String[] {"RSA", "DSA"}, // List of acceptable key types. null for any
null, // issuer, null for any
"internal.example.com", // host name of server requesting the cert, null if unavailable
443, // port of server requesting the cert, -1 if unavailable
null); // alias to preselect, null if unavailable

Once an application has been granted access to the certificate, it can access the private key through the getPrivateKey() method. It is worth noting that as with any PrivateKey objects, the application should not make assumptions about the encoding. For example, on some implementations the PrivateKey object may just be an opaque representation of a key stored in a hardware key store.

Here’s a sample code snippet that demonstrates the use of private key retrieved from the key store for signing:

    PrivateKey privateKey = KeyChain.getPrivateKey(context, savedAlias);
if (privateKey != null) {
...
Signature signature = Signature.getInstance("SHA1withRSA");
signature.initSign(privateKey);
...
}

A common use of the private key is for SSL client authentication. This can be implemented by using an HttpsURLConnection with a custom X509KeyManager that returns the PrivateKey retrieved from the KeyChain API. The open source Email application for ICS uses KeyChain with an X509ExtendedKeyManager. To learn more, have a look at the source code (in SSLUtils.java).

This API provides a unified way to access the system key store credentials. If your application uses client certificates (take note: enterprise email client or web browser developers) you should definitely look into the KeyChain API for your next update!

Pc Partner Intel 845 series Driver

Compatibility:
Intel 845 series including / 845G/ 845GL/ 845GV/ 845GE/ 845E/ 845PE
Intel 848P

On-board AGP Display Driver (845G, 845GL, 845GV and 845GE)
Download : Direct | Mirror

_______________________________
Intel Chipsets Driver

Intel INF Installation Utility
Download : Direct | Mirror

Intel Application Accelerator
 Download : Direct | Mirror

USB 2.0 ICH4/ ICH5 INF Package
Download : Direct | Mirror
(this is not the driver but txt files since the USB 2.0 installed automatically in windows xp)
Normally for mainboard socket 478 the usb 2.0 located at the rear panel of your desktop.

_________________________
AC 97 Codec Sound

ALC650 AC 97 Codec Driver
Download : Direct | Mirror

ALC100 / ALC 201A AC 97 Codec Driver
Download : Direct | Mirror

___________________________
Onboard LAN Driver Download

Intel 82562 Lan
Download : Direct | Mirror

NS Lan (DP83815)
Download : Direct | Mirror

Realtek 8139/ 8100
Download : Direct | Mirror

Sunday, March 11, 2012

Compaq Presario V3616AU Windows 7 Driver

The drivers below listed base on the specification and i didn;t test it yet. So, leave your feedback on the comment section below. V3616AU is in V3000 series notebook, so the drivers below tested with several V3000 AMD model and i believe it will work with others v3000 amd model too.

CHIPSET
NVIDIA Chipset (AMD Model)
(Will install chipset, LAN/Ethernet driver and coprocessor)
Download

For Nvidia chipset: Step to install: right click select PROPERTIES select compatibility - select win vista, the right click and select run as admin.

STORAGE
Intel matrix storage manager for windows 7: (intel only)
Download (intel site)
Download (mediafire)


DRIVER BELOW IS FOR BOTH AMD AND INTEL
 AUDIO
Conexant High-Definition SmartAudio 221 Driver
Download
or Download

MODEM:
HDAUDIO Soft Data Fax Modem with SmartCP
Download
or Download

GRAPHIC:
if you have nvidia graphic:
NVIDIA GeForce 8M Series GS Graphics/Video Driver
Download (32-bit)
Download (64-bit)

If the Nvidia Driver didn't work read here.

If you ave intel graphic:
Mobile Intel 965 Express Chipset Family Video Driver
Download (32-bit)
Download (64-bit)

ETHERNET/LAN
Marvell Yukon 88E8039 PCI-E Fast Ethernet Controller Driver (intel only)
(applicable for win vxp/vista/7 32-bit and 64-bit)
Download

WIRELESS:
There are 2 wireless Driver, select base on your specs or test which work for you.

1. Broadcom Wireless LAN Driver for Microsoft Windows 7
Download

2. Intel PRO/Wireless Drivers for Microsoft 7
Download

HP WWAN Broadband Wireless Drivers
(originally vista drivers) 
Download

BLUETOOTH:
Support Software for HP Integrated Module with Bluetooth Wireless Technology (Microsoft Windows 7)
Download

WEBCAM:
HP Webcam Driver
Download

Step to install: right click select PROPERTIES select compatibility - select win vista, the right click and select run as admin.

Cyberlink YouCam Software
Download

TOUCHPAD
ALPS Touchpad Pointing Device Driver
Download

HP Quicklaunch Button
Download (direct)
Download (HP)

CARD READER:
 Ricoh 5-in-1 Card Reader Host Controller and Driver for Microsoft Windows 7 (32-bit and 64-bit)
Download
or
Download

For the audio if you have problems installing the driver, get the hardware ID and post it in the comments section.

Wednesday, March 7, 2012

Sony Vaio VGN-FW Series VGN-FW4ZTJ/H (PCG-3H1M) Windows 7 Driver

This post is a reply for the following request:


If you search form sony site for PCG-3H1M you will get 'product not found', this is because the right model for PCG-3H1M is different such as Sony Vaio VGN-FW Series VGN-FW4ZTJ/H, so look carefully on the back stickers normally it state the right model.
example:

Sony Vaio PCG-3H1M / VGN-FW41J

To make it easier for you and for me, write all the information provided on the stickers including ref num etc.

SATA DRIVER

Intel Sata driver registry patch - 080619a
Also available through VAIO Update32 bits 371.24 Kb 27/10/2009

Intel Sata driver registry patch - 080619a
 Also available through VAIO Update64 bits 371.24 Kb 27/10/2009

_______________________

7UPG_Wireless LAN Driver (Intel)_32 32 bits
 2.14 Mb 22/10/2009

7UPG_Wireless LAN Driver (Intel)_64 64 bits
2.72 Mb 22/10/2009
 ________________________

GRAPHIC
There are 2 applicable graphic which is inel and ATI.

7UPG_Graphics Driver (ATI)_32 32 bits
106.37 Mb 22/10/2009

7UPG_Graphics Driver (ATI)_64 64 bits
110.5 Mb 22/10/2009

7UPG_Graphics Driver (Intel)_type1_32 32 bits
25.29 Mb 22/10/2009

7UPG_Graphics Driver (Intel)_type1_64
64 bits 26.3 Mb 22/10/2009


ETHERNET
Download and read the installation instruction for Ethernet at the end of the post.
Select 64 and 32 bit base on your specs.

7UPG_Ethernet Driver (Marvell)_32 32 bits
357.89 Kb 22/10/2009

7UPG_Ethernet Driver (Marvell)_64 64 bits
 416.86 Kb 22/10/2009

BLUETOOTH
7UPG_Alps Bluetooth driver 32 / 64 bits
 57.74 Mb 22/10/2009


AUDIO DRIVER
(Install both audio and HDMI Driver)

Audio driver - 6.0.1.5886
 Also available through VAIO Update32 / 64 bits 139.66 Mb 27/10/2009

7UPG_Audio Driver (Realtek)32 / 64 bits
98.01 Mb 22/10/2009

7UPG_Audio Driver (Realtek) HDMI 32 / 64 bits
 8.8 Mb 22/10/2009

INSTALLATION NOTE:

7UPG_Ethernet Driver (Marvell)_32 32 bits and 64 bits

1. Unzip the driver folder.
2. Open device manager by click start and type DEVMGMT.MSC and press enter.
3. A device manager will open, look for Ethernet/Network controller marked with yellow.
4. Right click and select update driver.
5. Select Browse My Computer For driver software.
6. Click browse and point to the driver folder we extracted earlier.
7. Next and continue with on screen installation.

Tuesday, March 6, 2012

Introducing Google Play



[This post is by Kenneth Lui, Android Developer Ecosystem. —Dirk Dougherty]

For more than a year we’ve been focused on expanding the reach, content, and monetization opportunities of Android Market. We started by extending the store to users on the web and then went on to add books, movies, and music. The number of people who have visited, registered, and downloaded from the store has been amazing.



Today we’re launching Google Play, an integrated destination for apps, books, movies, and music, accessible to users on Android devices and to anyone on the Web. As part of this launch, Google Play replaces and extends Android Market — users everywhere can now find their favorite apps and games in Google Play, with other digital content, all in one place.



We believe that with a strong brand, compelling offerings, and a seamless purchasing and consumption experience, Google Play will drive more traffic and revenue to the entire ecosystem.



We’ll be investing in the brand to bring Google Play to as many people as possible, and we’ll also invest in the latest digital content to keep Google Play fresh, relevant, and engaging. Apps and games remain the core of Google Play, so we’ll continue investing in new ways to connect users with their favorite apps, and developers with new customers.







As we grow and promote Google Play around the world, we’ll be marketing your apps and games at the same time. Our policies have not changed and our goal is still the same — to create a great, open marketplace for distributing Android apps.



Google Play is built on the same infrastructure as Android Market, so the transition for users and developers will be seamless. Users can sign into their existing accounts with the same credentials as before and purchase content using the same payment methods. As a developer, there’s no change needed to your published products and you can continue to use the same publishing tools to put your app in front of hundreds of millions of Android users. If your app was in Android Market yesterday, it’s in Google Play today.



We’ll be rolling out Google Play to devices in a phased OTA update, starting today and continuing over the days to come. With the update, the Android Market app will upgrade to the Play Store app and the Music, Videos, and Books apps will upgrade to Play Music, Play Movies, and Play Books. This update is for devices running Android 2.2 or higher, and users on other devices will continue to have the same access to your apps as before.



You can start sending customers to your products in Google Play right away. Check out the updated “Get it on Google Play” badges and look for an email with more details on the transition. In the meantime, you can check out the Google Play web site at the link below and join the discussion on +Android Developers.



http://play.google.com

Monday, March 5, 2012

Android Apps Break the 50MB Barrier

Android applications have historically been limited to a maximum size of 50MB. This works for most apps, and smaller is usually better — every megabyte you add makes it harder for your users to download and get started. However, some types of apps, like high-quality 3D interactive games, require more local resources.

So today, we’re expanding the Android app size limit to 4GB.

The size of your APK file will still be limited to 50MB to ensure secure on-device storage, but you can now attach expansion files to your APK.

  • Each app can have two expansion files, each one up to 2GB, in whatever format you choose.

  • Android Market will host the files to save you the hassle and cost of file serving.

  • Users will see the total size of your app and all of the downloads before they install/purchase.

On most newer devices, when users download your app from Android Market, the expansion files will be downloaded automatically, and the refund period won’t start until the expansion files are downloaded. On older devices, your app will download the expansion files the first time it runs, via a downloader library which we’ve provided below.

While you can use the two expansion files any way you wish, we recommend that one serve as the initial download and be rarely if ever updated; the second can be smaller and serve as a “patch carrier,” getting versioned with each major release.

Helpful Resources

In order to make expansion file downloading as easy as possible for developers, we're providing sample code and libraries in the Android SDK Manager.

  • In the Google Market Licensing package, an updated License Verification Library (LVL). This minor update mostly adds the ability to obtain expansion file details from the licensing server.

  • From the Google Market APK Expansion package, the downloader service example. The library makes it relatively simple to implement a downloader service in your application that follows many of our best practices, including resuming downloads and displaying a progress notification.

Because many developers may not be used to working with one or two large files for all of their secondary content, the example code also includes support for using a Zip file as the secondary file. The Zip example implements a reasonable patching strategy that allows for the main expansion file to “patch” the APK and the patch file to “patch” both the APK and the main expansion file by searching for asset files in all three places, in the order patch->main->APK.

Expansion File Basics

Expansion files have a specific naming convention and are located in a specific place for each app. As expansion files are uploaded to the publisher site, they are assigned a version code based upon the version of the APK that they are associated with. The naming convention and location are as follows:

Location: <shared-storage>/Android/obb/<package-name>/
Filename: [main|patch].<expansion-version>.<package-name>.obb
Example: /sdcard/Android/obb/com.example.myapp/main.5.com.example.myapp.obb

Expansion files are stored in shared storage. Unlike APK files, they can be read by any application.

Downloading and Using the Expansion Files

When the primary activity for the app is created, it should check to make sure the expansion files are available. The downloader library provides helper functions (for example the “Helpers” class in the code below) to make this easy.

boolean expansionFilesDelivered() {
// get filename where main == true and version == 3
String fileName = Helpers.getExpansionAPKFileName(this, true, 3);
// does the file exist with FILE_SIZE?
if (!Helpers.doesFileExist(this, fileName, FILE_SIZE, false)) {
return false;
}
return true;
}

If the file does not exist, fire up the downloader service with DownloaderClientMarshaller.startDownloadServiceIfRequired(). The downloader will perform an LVL check against the server. This check will deliver the names of the files, file sizes, and the file URLs.

Once that check has been completed, it will begin downloading the files. You don’t have to use our download solution, but you might want to because we:

  • Include a notification UI that provides progress and estimated completion time in layouts customized for ICS and pre-ICS devices

  • Resume large files safely

  • Handle redirection with appropriate limits

  • Run in the background as a service

  • Pause and resume downloads when WiFi is not available

Enjoy! We can’t wait to see what kinds of things developers do with this! For more information about how to use expansion files with your app, read the APK Expansion Files developer guide.

[This post wasn’t actually written by anyone, but bashed out by a posse of engineering and product-management people. Heavy bashers included Dan Galpin, Ilya Firman, Andy Stadler, Michael Siliski, and Ellie Powers.]

Wednesday, February 29, 2012

Android Design V2: Now with stencils

[This post is by Android designer Alex Faaborg, on behalf of the entire User Experience team. —Tim Bray]

When we initially released Android Design, by far the number one request we received was for us to release stencils as well. The fine folks on the Android User Experience team are pleased today to release some official Android Design stencils for your mockup-creating pleasure.

With these stencils you can now drag and drop your way to beautifully designed Ice Cream Sandwich (Android 4.0) applications, with grace and ease. The stencils feature the rich typography, colors, interactive controls, and icons found throughout Ice Cream Sandwich, along with some phone and tablet outlines to frame your meticulously crafted creations.

Currently we have stencils available for those venerable interactive design powerhouses Adobe® Fireworks®, and Omni® OmniGraffle® and we may expand to other applications® in the future. The source files for the various icons and controls are also available, created in Adobe® Photoshop®, and Adobe® Illustrator®. Here are the downloads.

We’ll be updating these stencils over time so, as always, please send in your feedback!

Happy mockup making,
— Your friendly Android Design Droids

Tuesday, February 28, 2012

New App Stats for Publishers on Android Market



If you've published an app on Android Market, you’ve probably used Application Statistics to help tune your development and marketing efforts. Application Statistics is a set of dashboards in the Developer Console that shows your app’s installation performance across key dimensions such as countries, platform versions, device models, and others. Today we are making Application Statistics even more powerful for publishers, adding new metrics, new ways to analyze your data, and a redesigned UI that’s much easier to use.

First, we are adding important new installation metrics to the dashboards. You can now see your installations measured by unique users, as well as by unique devices. For user installations, you can view active installs, total installs, and daily installs and uninstalls. For devices, you can see active installs as well as daily installs, uninstalls, and upgrades.



Along with the new metrics, we’re also introducing two new data dimensions — Carrier and App Version. You can use them to track your app’s installation trends across mobile operators or monitor the launch metrics of specific app updates.



To give you visibility over your installation data over time, we’re adding timeline charts for all metrics and dimensions. At a glance, these charts highlight your app’s installation peaks and longer-term trends, which you can correlate to promotions, app improvements, or other factors. You can even focus in on data inside a dimension by adding specific points (such as individual platform versions or languages) to the timeline.



Finally, we’re bringing you all of the new metrics, dimensions, and timelines in a completely redesigned UI that is faster, more compact, and easier to use. Each dimension is now displayed in dedicated tab, making it easier to click through your stats daily or as often as needed. If you track your stats in another tool, we’re also adding an export capability that lets you download your stats in a single CSV file.



Check out the new Application Statistics next time you visit the Android Market Developer Console. We hope they’ll give you new insight into your app’s user base and installation performance. Watch for related announcements soon — we are continuing to work on bringing you the reporting features you need to manage your products successfully on Android Market.



Please feel free to share any new insights or tips on +Android Developers!

Monday, February 20, 2012

Compaq Presario CQ40-641TU Windows XP Driver

NOTE: Install according to order given

First Install  Netframework: (require for Quick Launch Installation).
Net framework 2.0
Download

Compaq  Presario CQ40-641TU BUTTON Driver
HP  Quick Launch Buttons
Download

INTEL CHIPSET:
Compaq  Presario CQ40-641TUCHIPSET Driver (xp, vista, 7)
INF Update  Utility - Primarily for Intel® 5, 4, 3, 900 Series Chipsets
Download(mediafire)

STORAGE
Intel matrix storage manager:
Download  (intel site)
Download  (mediafire)

GRAPHIC
Compaq Presario CQ40-641TU Graphic XP Driver
if you have intel graphic:
Mobile Intel  45 Express Chipset Family Graphics Driver
Intel graphic  accelerator 4500MHD
Download

If  you have Nvidia graphic:
NVIDIA GeForce G 103M/ G 105M Graphics  Driver (186.81 WHQL XP 32-bit)
Download

FOR NVDIA: if  resulting in error use modded driver below:
Download
3-step  process to install:
1. Download driver, double click and select  extract,
2. Download modded INF and replace original INF in  extracted folder,
3. Install and  reboot.

======================================
AUDIO:
Compaq  Presario CQ40-641TU Windows XP Driver
===================================== 
Install MS-UAA first:
both ms-uaa sp33867 and kb888111 are  similar files.
Windows XP SP2: Download   (SP33867.exe)
Download  (KB888111)
Windows XP SP3: Download  (KB835221)

Then restart, and install AUDIO Drivers:

IDT  - High Definition Audio Codecs (SP39671)
Download  (ftp)
Download  (mediafire)
===========================
or try this drivers reported work in xp
SP41500 Download  (ftp)
               Download  (mediaifre)

SP41616  Download(ftp)
                 Download  (mediaifre)
===========================
First install your audio.
Installing the Audio normally resulting in error, ignore it and proceed  by manually install the drivers:

Download and install the driver, you will get the error while  installing.
Perform the below steps to fix the issue.
1. Click on Start and select Run. Now type devmgmt.msc and press enter.
2. Right click on "Audio device on High Definition Audio Bus" and click  Update driver.
3. Select "Install from a list or specific location".
4. Click Next. Then select "Don't search, I will choose the driver to  install".
5. Click Next and then select "Sound, video and game controller" from  the list.
6. Click Next and then click Have Disk.
7. Click Browse C:\swsetup\sp39671 folder and select the .inf   file and click open and Continue with the onscreen instructions.

Fo instruction with pictures read here:
Manually  install Audio Drivers.

MODEM
High-Definition Audio (HDA)  Modem Installer and Driver
Download

WIRELESS:
Compaq  Presario CQ40-641TU Wireless XP Driver
=====================================
Choose  one of the wireless driver base on your specs, if you dont know, just  try each driver (there are no risk and will not harm your system)
---------------------------------------------------------
Broadcom:  Download

if  error try newer version -
Broadcom BCM9431HMG
Broadcom: Download

Intel:  Download
(requires  windows installer 3.0 installed first)
=================

BLUETOOTH:
Compaq  Presario CQ40-641TU XP Bluetooth Driver
HP Integrated Module with  Bluetooth Wireless Technology
Download

WIRELESS  SOFTWARE
HP Wireless Assitant:
Download

ETHERNET:
Compaq  Presario CQ40-641TU LAN/Ethernet Driver
Realtek RTL8102E Family  PCI-E Fast Ethernet NIC
  Download(direct)  or Download

CARD  READER
Compaq Presario CQ40-641TUCard Reader Driver
JMB38X  Card Reader Host Controller
Download

TOUCHPAD
Compaq  Presario CQ40-641TU Touchpad Driver
ALPS Touchpad
Download

Synaptics  Touchpad
Download
Download

WEBCAM
Compaq  Presario CQ40-641TU XP Webcam Driver
Cyberlink youcam software  2.0
Download

LIGHTSCRIBE:
Lightscribe  system software
Download

If  you have 7 unknown device:
Unknown devices:
Download

Unzip  files, open folder and right click at machine.inf, select install.

Sunday, February 19, 2012

AMD High-Definition Graphics Driver 8.861.1.2000

AMD High-Definition Graphics Driver
Date: 2011-11-18
Version: 8.861.1.2000
Size:  160.18M
File Name:  SP54988
Download: Direct | Mirror

Drivers including:

-ATI Graphic Driver
-South Bridge SB7xx and SB8xx
-AMD SMBus device
-HDMI
-USB30 HUB driver
- AHCI SATA Controller 7.12.0.7701

Compatibility

Microsoft Windows 7 (32-bit), Microsoft Windows 7 Home Basic (32-bit), Microsoft Windows 7 Home Premium (32-bit), Microsoft Windows 7 Professional (32-bit), Microsoft Windows 7 Enterprise (32-bit), Microsoft Windows 7 Ultimate (32-bit), Microsoft Windows 7 Starter (32-bit), Microsoft Windows 7 Home Basic (64-bit), Microsoft Windows 7 Home Premium (64-bit), Microsoft Windows 7 Professional (64-bit), Microsoft Windows 7 Enterprise (64-bit), Microsoft Windows 7 Ultimate (64-bit), Microsoft Windows 7 (64-bit)

Fixes and enhancement

- Prevents software conflicts with Symantec Norton Internet Security 2012.

Supported Product

AMD M880G with ATI Mobility Radeon HD 4250
AMD Radeon HD 6250 Graphics
AMD Radeon HD 6290 Graphics
AMD Radeon HD 6310 Graphics
AMD Radeon HD 6320 Graphics
AMD Radeon HD 6370M
AMD Radeon HD 6470M
AMD Radeon HD 6490M
AMD Radeon HD 6600M Series
AMD Radeon HD 6650M
AMD Radeon HD 6730M
AMD Radeon HD 6750M
AMD Radeon(TM) HD 6380G
AMD Radeon(TM) HD 6480G
AMD Radeon(TM) HD 6520G
AMD Radeon(TM) HD 6620G
SUMO 9640
SUMO 9642

Realtek High-Definition (HD) Audio Driver 6.0.1.6461

Realtek High-Definition (HD) Audio Driver
Date: 2011-11-18
Version: 6.0.1.6461
Size: 115.61M
File name: SP54986
Download : Direct | mirror

Compatibility:

Microsoft Windows 7 (32-bit), Microsoft Windows 7 Home Basic (32-bit), Microsoft Windows 7 Home Premium (32-bit), Microsoft Windows 7 Professional (32-bit), Microsoft Windows 7 Enterprise (32-bit), Microsoft Windows 7 Ultimate (32-bit), Microsoft Windows 7 Starter (32-bit), Microsoft Windows 7 Home Basic (64-bit), Microsoft Windows 7 Home Premium (64-bit), Microsoft Windows 7 Professional (64-bit), Microsoft Windows 7 Enterprise (64-bit), Microsoft Windows 7 Ultimate (64-bit),Microsoft Windows 7 (64-bit),

Microsoft Windows XP Professional, Microsoft Windows XP Home Edition, Microsoft Windows XP Media Center, Microsoft Windows XP, Microsoft Windows Embedded Standard 7

Fixes and Enhancement:

- Fixes an issue where the system displays an error message and delays opening the Games folder. - Fixes an issue where the system emits an unintended noise when the Enable OmniSound Exp and Bass Back Exp options are enabled during audio playback.

 - Fixes an issue where the stereo mix feature is disabled after the Realtek Audio Driver has been installed.

Acer Aspire 5742 Windows 7 Driver

Supported Operating system : Windows 7 32-bit, Windows 7-64 bit.

INTEL CHIPSET INSTALLATION (Motherboard)
There are 4 essential driver which is Intel chipset, AMT, AHCI and Turbo Boost)

1. Chipset
Chipset Driver Intel 9.1.1.1024 2.3 MB 08/18/2010
 Download | Mirror (32 and 64-bit)

2. AHCI
SATA AHCI Driver Intel 9.6.2.1001 10.0 MB 08/18/2010
Download | Mirror (32 and 64-bit)

3. AMT
Intel iAMT Driver Intel 6.0.0.1179 5.3 MB 08/18/2010
Download | Mirror (32 and 64-bit)

4. Turbo Boost
Turbo Boost Driver Intel 1.2.0.1002 1.1 MB 08/18/2010
Download | mirror (32 and 64-bit)


AUDIO
Audio Driver Realtek 6.0.1.6141 95.8 MB 08/18/2010
Download | Mirror (32 and 64-bit)


BLUETOOTH
There are 4 drivers for bluetooth, by type only atheros and broadcom, choose base on your specs, if you don;t know which to install, try which work for you. I recommend to choose no 2 and 3.

1. Bluetooth Driver for Windows 7 SP1 Atheros 6.18.0624.0302 199.9 MB 04/12/2011
 Download | Mirror (64-bit)

2. Bluetooth Driver Broadcom 6.3.0.5900 59.0 MB 08/18/2010
 Download | Mirror (32 and 64-bit)

3. Bluetooth Driver Atheros 6.27.0521.0302 65.4 MB 08/18/2010
Download | Mirror (32 and 64-bit)

4. Bluetooth Driver (3.0) Broadcom 6.3.0.6000 59.0 MB 10/19/2010
Download | Mirror (64-bit)



CAMERA/WEBCAM
Choose base on your specs, normally all driver provide the generic driver for CAM input, the difference only in stability and aps.

1. Camera Driver Suyin 5.3.36.1 7.3 MB 01/27/2011
Download | Mirror (32 and 64-bit)

2. Camera Driver Chicony 1.1.199.107 3.7 MB 01/27/2011
Download | Mirror (32 and 64-bit)

3. Camera Driver liteon 1.0.5.2 6.0 MB 01/27/2011
Download | Mirror (32 and 64-bit)



CARD READER
Card Reader Driver Realtek 6.1.7600.30122 8.3 MB 08/18/2010
Download | Mirror (32 and 64-bit)


LAN/ETHERNET
LAN Driver Broadcom 14.0.1.0 10.8 MB 08/18/2010
Download | Mirror (32 and 64-bit)


TOUCHPAD
Install both driver

Touchpad Driver Synaptics 14.0.19.0 29.5 MB 08/18/2010
Download | Mirror (32 and 64-bit)

Touchpad Driver ELANTECH 7.0.6.5 37.9 MB 08/18/2010
Download | Mirror (32 and 64-bit)



VGA/GRAPHIC
There are 3 type of graphic which is INTEL, NVIDIA and AMD. Choose base on your specs, normally you can see it written in the sticker on you laptop. (AMD refer to ATI graphic). For Nvidia Install physix (no 1) and driver no 2. There are 2 version for intel graphic, you can choose any version to install.

VGA Driver (Physx) NVIDIA 9.10.0514 24.6 MB 12/15/2011
 Download | Mirror (32 and 64-bit)

VGA Driver NVIDIA 8.17.12.8564 371.0 MB 12/15/2011
Download | Mirror (32 and 64-bit)

VGA Driver AMD 8.741.0.0000 241.1 MB 08/18/2010
Download | Mirror (32 and 64-bit)

VGA Driver Intel 8.15.10.2182 77.6 MB 07/12/2011
Download | Mirror (32 and 64-bit)

VGA Driver Intel 8.15.10.2125 77.4 MB 08/18/2010
Download | Mirror (32 and 64-bit)

Support:
How to check driver in win 7

Wireless LAN
There are 2 driver for wireless Atheros and Broadcom (for broadcom there are 2 version available).

Wireless LAN Driver Atheros 9.2.0.439 11.6 MB 12/22/2011
Download | Mirror (32 and 64-bit)

Wireless LAN Driver Broadcom 5.100.82.95 33.6 MB 10/18/2011
 Download | Mirror (32 and 64-bit)

Thursday, February 16, 2012

Compaq Presario B1200 Windows XP Driver

Install both Windows Installer and .Netframework first.

Windows Installer 3.1
Size : 2.5 MB Windows Installer-KB893803-v2-x86.exe
Download

Microsoft .Net Framework 2.0
Size: 22.4 MB  (requirement to install HP quick launch button)
Download

Chipset
Intel Chipset Installation Utility for ICH8
size: 1.81 MB
Download | Mirror

Graphic
Intel Graphics Media Accelerator X3100
Size: 13.76 MB win2k_xp14371
Mirror
(no direct link available, but you can download this file from Intel website by search for win2k_xp14371.)

Wireless:
Broadcom Wireless LAN
Size: 6.9 MB 6.20E
Download | Mirror

LAN/Ethernet
Broadcom Ethernet driver version 10.24.0.0.
Size: 13.0 MB 1.00 rev A
Download | Mirror

Modem
Agere Systems HDA Modem
Size: 12.63 MB (Originally for vista but reported work with xp)

Download | Mirror

Bluetooth:
Software and Drivers for HP Integrated Module with Bluetooth Wireless
Size: 39.31 MB 4.00 I
Download | Mirror
______________________________
Driver - Audio
(Install according to order)

Microsoft Universal Audio Architecture (UAA) Bus Driver for High Definition Audio (sp32646)
Size: 35.50 MB
Download | Mirror

Restart after Installation , Then install audio

ADI SoundMAX High-Definition (HD) Audio Driver for Microsoft Windows XP
Size: 6.78 MB 5.10.1.5210
Download | Mirror
__________________________________

Drivers - Input, keyboard and button devices

Synaptics Touchpad
Size: 24.26 MB
Download | Mirror

HP Quicklaunch Button
Size: 19,65 MB
Download | Mirror

Acer Aspire 5730 Windows Xp Driver

Model: Acer 5730
Operating system : Windows XP 32 -bit Windows XP 64-bit (x86/x64)

All driver compatible with 32-bit and 64-bit, except MODEM AGERE separate link added for 64-bit.

Chipset
Intel Chipset Driver
8.7.0.1007 2.1 MB 2009/01/15
Download | Mirror

AHCI
Intel SATA AHCI Driver
8.2.0.1001 53.8 MB 2009/01/15
Download | Mirror

Audio
Realtek Audio Driver
5.10.0.5618 42.5 MB 2009/01/15
Download | Mirror

Bluetooth
Broadcom Bluetooth Driver
5.1.0.3300 96.6 MB 2009/01/15
Download | Mirror

CardReader
Realtek Card Reader Driver
3.0.1.3 5.7 MB 2009/01/15
Download | Mirror

TouchPad
 Synaptics Touchpad Driver
11.0.2.0 25.1 MB 2009/01/15
Download | Mirror

VGA
Intel VGA Driver
6.14.10.4969 20.0 MB 2009/01/15
Download

Camera
 Bison Camera Driver
 7.96.701.14 6.8 MB 2009/01/15
Download | Mirror

 Suyin Camera Driver
 5.8.33.501 5.6 MB 2009/01/15
 Download | Mirror

Lan
 Marvell LAN Driver
 10.55.3.3 1.0 MB 2009/01/15
 Download | Mirror

Modem
 Agere Modem Driver
 2.1.87.0 711.7 KB 2009/01/15
 Download | Mirror
Download | Mirror (64-bit)

Modem
 Conexant Modem Driver
 7.62.0.0 1.7 MB 2009/01/15
 Download | Mirror

Wireless LAN
Atheros Wireless LAN Driver
5.3.0.45 2.7 MB 2009/01/15
 Download | Mirror

Broadcom Wireless LAN Driver
 4.170.25.12 4.1 MB 2009/01/15
Download | Mirror

Intel Graphic version 6.14.10.4969 Windows XP Driver

Type : Chipset Driver
Name :Intel VGA Driver
Verson: 6.14.10.4969
Sizwe: 20.0 MB
Date: 2009/01/15
Operating system: Windows XP
Applicable model : Acer

Download

(please read the privacy policy page)

Driver Revision: PV 14.36.0.
 Package: 51654

Graphics:  6.14.10.4969
HDMI Audio: 5.10.0.1044                                                    


July 17, 2008

NOTE:  This document refers to systems containing the
following Intel chipsets:

Intel(R) G43 Express Chipset
*    Intel(R) G45 Express Chipset
*    Intel(R) Q43 Express Chipset
*    Intel(R) Q45 Express Chipset
*    Intel(R) G33 Express Chipset
*    Intel(R) G35 Express Chipset
*    Intel(R) G965 Express Chipset
*    Intel(R) Q33 Express Chipset
*    Intel(R) Q35 Express Chipset
*    Intel(R) Q963 Express Chipset
*    Intel(R) Q965 Express Chipset
*    Mobile Intel(R) GL960 Express Chipset
*    Mobile Intel(R) GLE960 Express Chipset
*    Mobile Intel(R) GM965 Express Chipset
*    Mobile Intel(R) GME965 Express Chipset 
*    Mobile Intel(R) GL40 Express Chipset
*    Mobile Intel(R) GM45 Express Chipset
*    Mobile Intel(R) GM47 Express Chipset