Skip to main content

NVidia GeForce Go 7400 graphics for Windows 7.

NOTE : "nv_disp" and "drivers" Files are different for 32bit and 64bit. Make sure you download the right files
Here below is the link for 64bit and right below I have updated for 32bit windows 7 OS

As I got my system upgraded to Windows 7 Utimate.
I was facing issue getting my NVidia GeForce Go 7400 graphics card detected.
All I got was "Standard VGA Graphics Adapter" which is like "1024x768" !! .. really lame resolution.
Then I went to NVidia Site to download the latest driver but was not so useful.

Below is the solution we found and it works !!! :)

http://www.laptopvideo2go.com/drivers/win7x64/196.21/disclaimer
Download the driver and INF file from here.

Here are the steps :)
1. Download and extract.
2. Copy and replace the INF.
3. Install and reboot.
Walla thats it and my laptop is up and running some nice graphics (Aero and all the graphics goods .. ) with descent Resolution.

My Machine info..
Sony VAIO VGN-C25G
NVidia GeForce Go 7400 graphics card.
OS - Windows 7 Ultimate 64bit.
UPDATED : This solution works with 32bit too - TESTed it today :).
Here is the link for windows 7 32bit - http://www.laptopvideo2go.com/drivers/win7x32/197.55/disclaimer
Thanks to Hafeez... :)
Labels:

Comments

  1. UnknownDecember 2, 2010 at 4:14 AM

    thanks bro it worked ...do you have other drivers because i have updated my vgn-c25g to win 7 64 bit but cant find the drivers

    ReplyDelete
  2. AnonymousMarch 28, 2011 at 7:39 AM

    im new to this and cant find out how to copy and replace the inf plz help

    ReplyDelete
  3. AnonymousMarch 28, 2011 at 7:56 AM

    nevermind i found out how. thank you! i can finaly play games after 4 weeks of looking for help after the upgrade

    ReplyDelete

Post a Comment

Popular posts from this blog

Cloudera Manager - Duplicate entry 'zookeeper' for key 'NAME'.

We had recently built a cluster using cloudera API’s and had all the services running on it with Kerberos enabled. Next we had a requirement to add another kafka cluster to our already exsisting cluster in cloudera manager. Since it is a quick task to get the zookeeper and kafka up and running. We decided to get this done using the cloudera manager instead of the API’s. But we faced the Duplicate entry 'zookeeper' for key 'NAME' issue as described in the bug below. https://issues.cloudera.org/browse/DISTRO-790 I have set up two clusters that share a Cloudera Manger. The first I set up with the API and created the services with capital letter names, e.g., ZOOKEEPER, HDFS, HIVE. Now, I add the second cluster using the Wizard. Add Cluster->Select Hosts->Distribute Parcels->Select base HDFS Cluster install On the next page i get SQL errros telling that the services i want to add already exist. I suspect that the check for existing service names does n
2 comments
Read more

Zabbix History Table Clean Up

Zabbix history table gets really big, and if you are in a situation where you want to clean it up. Then we can do so, using the below steps. Stop zabbix server. Take table backup - just in case. Create a temporary table. Update the temporary table with data required, upto a specific date using epoch . Move old table to a different table name. Move updated (new temporary) table to original table which needs to be cleaned-up. Drop the old table. (Optional) Restart Zabbix Since this is not offical procedure, but it has worked for me so use it at your own risk. Here is another post which will help is reducing the size of history tables - http://zabbixzone.com/zabbix/history-and-trends/ Zabbix Version : Zabbix v2.4 Make sure MySql 5.1 is set with InnoDB as innodb_file_per_table=ON Step 1 Stop the Zabbix server sudo service zabbix-server stop Script. echo "------------------------------------------" echo " 1. Stopping Zabbix Server &quo
1 comment
Read more

Access Filter in SSSD `ldap_access_filter` [SSSD Access denied / Permission denied ]

Access Filter Setup with SSSD ldap_access_filter (string) If using access_provider = ldap , this option is mandatory. It specifies an LDAP search filter criteria that must be met for the user to be granted access on this host. If access_provider = ldap and this option is not set, it will result in all users being denied access. Use access_provider = allow to change this default behaviour. Example: access_provider = ldap ldap_access_filter = memberOf=cn=allowed_user_groups,ou=Groups,dc=example,dc=com Prerequisites yum install sssd Single LDAP Group Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = memberOf=cn=Group Name,ou=Groups,dc=example,dc=com Multiple LDAP Groups Under domain/default in /etc/sssd/sssd.conf add: access_provider = ldap ldap_access_filter = (|(memberOf=cn=System Adminstrators,ou=Groups,dc=example,dc=com)(memberOf=cn=Database Users,ou=Groups,dc=example,dc=com)) ldap_access_filter accepts standa
Post a Comment
Read more