Android SDK tools update failure: solved

While updating through Eclipse, if you get error:

Installing Android SDK Platform-tools, revision 9

Failed to rename directory

and warning:

-= warning! =- A folder failed to be renamed or moved. On Windows this typically means that a program Is using that Folder (for example Windows Explorer or your anti-virus software.) Please momentarily deactivate your anti-virus software. Please also close any running programs that may be accessing the android-installation-path/tools directory, 

follow these steps:

• Close Eclipse and close all instances of windows explorer in which the\android-sdk-windows\tools folder was opened.
• Copy tools directory to some other tools_copy directory.
• Run android.bat from there.
• After update is over delete temp_tools directory (kill adb.exe if not able to delete the folder)

you can also try these (didn't work for me:()

• Close Eclipse and close all instances of windows explorer in which the\android-sdk-windows\tools folder was opened 
• Now run the AVD Manager independently as follows: 
• Open a command prompt 
• Go to the directory where android SDK is installed at, and then its tools subdirectory 
• Run android.bat 
• At this point, update just as you would if you were running the AVD Manager from within Eclipse (make sure the proxy settings are mentioned if you are behind the proxy). 

VLC player on Fedora: solved

While installing VLC player on Fedora 10 I ran into following error:
rpm -ivh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
Retrieving http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-stable.noarch.rpm
warning: /var/tmp/rpm-tmp.mBuC1o: Header V3 RSA/SHA256 signature: NOKEY, key ID 16ca1a56
error: Failed dependencies:
    system-release >= 12 is needed by rpmfusion-free-release-12-3.noarch

I got over it by changing into this:
rpm -ivh http://download1.rpmfusion.org/free/fedora/releases/10/Everything/x86_64/os/rpmfusion-free-release-10-1.noarch.rpm

if it is other than x86_64, replace it with either of i386, ppc or ppc64 depending on your system architecture.To check your system architecture, run this:
#arch

The problem here was probably 'coz latest release of rpmfusion does not support pre versions of Fedora 12.

wifi on linux : solved

Finally got wifi up on linux.. Have been trying from 2 days reading tutorials and downloading drivers.. All you guys trying the same on FC distributions(I'm using FC10), on Dell(dual  boot),

follow these steps[...]

Errors welcome:) 

• Download the driver file from DRIVER
• Extract the exe file using unzip.

[root@localhost trial_wifi_varsha]# unzip dell.exe

• Need to follow ndiswrapper instructions if you see any errors while you using ndiswrapper.

          (NDISwrapper is a free software driver wrapper that enables the use of Windows XP drivers for network devices on Unix-like operating systems.)

            [root@localhost trial_wifi_varsha]# ndiswrapper -i DRIVER_US/bcmwl5.inf
            [root@localhost trial_wifi_varsha]# ndiswrapper -l
             bcmwl5 : driver installed
            device (14E4:4315) present

• [root@localhost trial_wifi_varsha]# ndiswrapper –m

module configuration information is stored in /etc/modprobe.d/ndiswrapper.conf

            ( -m writes  an alias for wlan0 (default wireless device) into module  configuration file so that ndiswrapper kernel module  is  loaded automatically when this interface is used.)

•  [root@localhost trial_wifi_varsha]# depmod -a
(so that the correct module dependencies will be available immediately after booting the system.)
• [root@localhost trial_wifi_varsha]# modprobe ndiswrapper

• edit /etc/modprobe.conf

(manually add the alias into /etc/modprobe.conf)

[root@localhost trial_wifi_varsha]# vim /etc/modprobe.conf

add this line: alias wlan0 ndiswrapper

• Configure network manager System>Administration>Network to get associated with the Access Point or manually configur using following commands.

1. To list the Access Points available.

[root@localhost trial_wifi_varsha]# iwlist wlan0 scan

2. Configure to get associated with one of the AP:

Assuming you want to use the ESSID named MyEssid:

Ø  No encryption

 # iwconfig wlan0 essid "MyEssid"

Ø  WEP

using an hexadecimal key:

 # iwconfig wlan0 essid "MyEssid" key 1234567890

using an ascii key:

 # iwconfig wlan0 essid "MyEssid" key s:asciikey

Ø  WPA/WPA2

  (might get this error!                       

Error for wireless request "Set Encode" (8B2A) : SET failed on device wlan0 ; Invalid argument.)

You need to edit the /etc/wpa_supplicant.conf file as described in WPA_Supplicant. Then, issue this command:

 # wpa_supplicant -B -Dwext -i wlan0 -c /etc/wpa_supplicant.conf

This is assuming your device uses the wext driver. If this does not work, you may need to adjust these options. Check WPA_Supplicant for more information and troubleshooting. 

3. Finally, provide an IP address to the network interface.

for DHCP,

# dhcpcd wlan0

Or
for static IP.

# ifconfig wlan0 192.168.0.12

# route add default gw 192.168.0.1

4. Regardless of the method used, you can check if you have associated successfully as follows:

[root@localhost trial_wifi_varsha]# iwconfig wlan0

wlan0     IEEE 802.11g  ESSID:"MyEssid" 

Mode:Managed  Frequency:2.412 GHz  Access Point: 00:1B:57:EC:4A:27  

Bit Rate=54 Mb/s   Tx-Power:32 dBm  

RTS thr:2347 B   Fragment thr:2346 B  

Encryption key:”the key!” Security mode:restricted

Power Management:off

Link Quality:70/100  Signal level:-51 dBm  Noise level:-96 dBm

Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0

Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Blogger Static Home page

To make a static start page add this code just after <body> tag n before main-wrapper

<b:if cond='data:blog.url == data:blog.homepageUrl'> 

   <div id='startpage'>

    <!-- Start Page-->

    </div>

<b:else/> 

     <div id='main-wrapper'>

        <b:section class='main' id='main' showaddelement='no'>

        <b:widget id='Blog1' locked='true' title='Blog Posts' type='Blog'/>

        </b:section>

      </div>

</b:if>

Oracle thin driver on Eclipse

1.      Add jar files

In Eclipse, after creating a new project -> right click on projname-> properties -> select Java Buildpath-> Add External Jars-> jar file path -> Ok

Jar file pathàC:\oraclexe\app\oracle\product\10.2.0\server\jdbc\lib

2.      Start adding new class file

To use the DriverManager class to create connection objects, you need to know how to make a connection URL that provides access information to the Oracle server. The Oracle connection URL for the thin client-side driver ojdbc14.jar has the following format:

jdbc:oracle:thin:[user/password]@[host][:port]:SID

jdbc:oracle:thin:[user/password]@//[host][:port]/SID

  user - The login user name defined in the Oracle server.

  password - The password for the login user.

  host - The host name where Oracle server is running.

         Default is 127.0.0.1 - the IP address of localhost.

  port - The port number where Oracle is listening for connection.

         Default is 1521.

  SID  - System ID of the Oracle server database instance.

By default, Oracle Database 10g Express Edition creates one database instance called XE.

Ex:       try {

                                      Connection con=null;

                                      Class.forName("oracle.jdbc.driver.OracleDriver");

                                      con=DriverManager.getConnection(

                                        "jdbc:oracle:thin:@localhost:1521:XE",

                                        "system",

                                        "password");

                                      Statement s=con.createStatement();

                                      s.execute("insert into emp values('attr1')");

                                      s.close();

                                      con.close();

                   } catch(Exception e){e.printStackTrace();}