tag:blogger.com,1999:blog-7657761807600529222024-03-20T02:39:49.798-07:00TechperienceSagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.comBlogger13125tag:blogger.com,1999:blog-765776180760052922.post-79030795545747224102011-09-04T05:03:00.000-07:002011-09-04T05:03:23.246-07:00Fixing Orphanes Users in SQL Server<br />
<B> What is an orphaned User? </B><br />
A database user for which the corresponding SQL Server login is undefined or is incorrectly defined on a server instance cannot log in to the instance. Such a user is said to be an orphaned user of the database on that server instance. A database user can become orphaned if the corresponding SQL Server login is dropped. Also, a database user can become orphaned after a database is restored or attached to a <b>different instance </b>of SQL Server. Orphaning can happen if the database user is mapped to a SID that is not present in the new server instance. SQL Server manages the SIDs for SQL Server logins so there is no guarantee that the new login has the same SID as the original login did. Then when you restore your database, the users in that database are expecting SIDs that are not there and the next thing you know you have orphaned users. Just a note, this does not occur with Windows Logins because the SID is controlled by Windows or Active Directory. Unless you drop and re-create the user in Windows, the SID of an Active Directory user will be the same on all SQL Servers and hence your user accounts see the SID they are looking for.<br />
<br />
<b>How do you fix the problem without dropping and re-creating the user and messing up the permissions in the process?</b><br />
By using a stored procedure called sp_change_users_login that you can use to fix orphaned users. This procedure can do several things; it can tell you which users are orphaned, it lets you fix an orphaned user manually, and it can attempt to automatically fix your issues.<br />
<br />
<b>Detecting orphaned users:</b><br />
USE <database_name>;<br />
GO; <br />
sp_change_users_login @Action='Report';<br />
GO;<br />
Note: sp_change_users_login cannot be used with SQL Server logins that are created from Windows.<br />
<br />
<b>Fixing a particular Orphaned User:</b><br />
Run sp_change_users_login with the UPDATE_ONE action and tell SQL Server the name of my orphaned user and the name of the appropriate login.<br />
EXEC sp_change_users_login 'UPDATE_ONE','name_orphanedUser','name_appropriateLogin'<br />
<br />
<b>Fixing Orphaned Users Automatically:</b><br />
This procedure should be created in the Master database. This procedure takes no parameters. It will remap orphaned users in the current database to EXISTING logins of the same name. This is usefull in the case a new database is created by restoring a backup to a new database, or by attaching the datafiles to a new server. <br />
<br />
IF OBJECT_ID('dbo.sp_fixusers') IS NOT NULL<br />
BEGIN<br />
DROP PROCEDURE dbo.sp_fixusers<br />
IF OBJECT_ID('dbo.sp_fixusers') IS NOT NULL<br />
PRINT '<<< FAILED DROPPING PROCEDURE dbo.sp_fixusers >>>'<br />
ELSE<br />
PRINT '<<< DROPPED PROCEDURE dbo.sp_fixusers >>>'<br />
END<br />
<br />
GO<br />
<br />
CREATE PROCEDURE dbo.sp_fixusers<br />
<br />
AS<br />
<br />
BEGIN<br />
<br />
DECLARE @username varchar(25)<br />
<br />
DECLARE fixusers CURSOR <br />
FOR<br />
<br />
SELECT UserName = name FROM sysusers<br />
WHERE issqluser = 1 and (sid is not null and sid <> 0x0)<br />
and suser_sname(sid) is null<br />
ORDER BY name<br />
<br />
OPEN fixusers<br />
<br />
FETCH NEXT FROM fixusers<br />
INTO @username<br />
<br />
WHILE @@FETCH_STATUS = 0<br />
BEGIN<br />
EXEC sp_change_users_login 'update_one', @username, @username<br />
FETCH NEXT FROM fixusers<br />
INTO @username<br />
END<br />
<br />
<br />
CLOSE fixusers<br />
DEALLOCATE fixusers<br />
END<br />
go<br />
IF OBJECT_ID('dbo.sp_fixusers') IS NOT NULL<br />
PRINT '<<< CREATED PROCEDURE dbo.sp_fixusers >>>'<br />
ELSE<br />
PRINT '<<< FAILED CREATING PROCEDURE dbo.sp_fixusers >>>'<br />
go<br />
<br />
Congratulations! Orphaned users are Fixed.Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0tag:blogger.com,1999:blog-765776180760052922.post-23843554845056137492011-09-02T05:36:00.000-07:002011-09-02T05:36:07.295-07:00Configuring Database Mail in SQL Server 2008 R2Database mail enables an instance of SQL server to send outbound e-mail messages. <br />
<br />
For using Database mail feature in SQL server, one has to enable database mail feature by running the following query: <br />
<i><br />
EXEC sp_configure "Database Mail XPs",1<br />
GO<br />
reconfigure with override</i><br />
<br />
The next step would be to Configure Database Mail. For this, <br />
<ul>Connect to the instance of SQL server. Open Management node -> right click on Database Mail -> Configure. You will get welcome screen.
Click Next. (There's nothing to do on the Welcome screen). In case you didnt enable the feature of Database Mail, it shows you a pop up asking you to enable it. Click "ok". If you did enable it earlier, it just takes you to the next page of the dialog.</ul><ul>Click Set up(assuming you're installing it for the first time) -> Next.</ul><ul>Specify Name for the profile and Click on ADD for configuring e-mail. </ul><ul>You need an SMTP account for this. Fill in your account details. Also select your authentication mode and fill in the required details.</ul><ul>Click ok and then click Next -> Finish.</ul><ul>The final page shows all your configurations and gives message of completion. Click Close.</ul>Now you are ready to test your Database Mail.<br />
Right Click on Database Mail and click on send Test Mail. Enter the recepient's email address and hit send mail. Verify that you have recieved it. <br />
Congratulations. You are all set to start using this wonderful service.<br />
<br />
<br />
Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com1tag:blogger.com,1999:blog-765776180760052922.post-45500636590277645882011-03-31T07:40:00.000-07:002011-03-31T07:53:30.220-07:00Installing Maven on FedoraMaven: Maven is a software project management and comprehension tool. Based on the concept of a Project Object Model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.<br /><br />System Requirements:<br /><br /> JDK:<br /><br /> 1.5 or above (this is to execute Maven - it still allows you to build against 1.3<br /> and prior JDK's).<br /><br /> Operating System:<br /><br /> No minimum requirement. On Windows, Windows NT and above or Cygwin is required for<br /> the startup scripts. Tested on Windows XP, Fedora Core and Mac OS X.<br /><br />Installation: <br /><br />1) Download maven from : http://maven.apache.org/download.html <br />You could use the latest release. <br /><br />2) Unpack the archive where you would like to store the binaries. I am assuming you know how to do that. A directory called "apache-maven-3.0.x" will be created.<br /><br />3) Add the bin directory to your PATH. In the terminal type : export PATH=/usr/local/apache-maven-3.0.x/bin:$PATH <br />You may be asked to perform this operation as root.<br /><br />4) Make sure JAVA_HOME is set to the location of your JDK. If you have JDK already, you would have done it at the time of installing it. If you don't have it, you need to download and install it.<br /><br />5) Run "mvn --version" to verify that it is correctly installed. <br />If correctly installed the output will be similar to the following: <br /><br />[root@localhost /]# mvn --version<br />Apache Maven 3.0.3 (r1075438; 2011-02-28 23:01:09+0530)<br />Maven home: /home/jayati/Download/apache-maven-3.0.3<br />Java version: 1.6.0_18, vendor: Sun Microsystems Inc.<br />Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0/jre<br />Default locale: en_US, platform encoding: UTF-8<br />OS name: "linux", version: "2.6.30.10-105.2.23.fc11.i586", arch: "i386", family: "unix"<br /><br />Congratulations! You have successfully installed Maven.Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0tag:blogger.com,1999:blog-765776180760052922.post-65569198891905909872010-09-06T06:21:00.002-07:002010-09-07T09:47:17.734-07:00Installing Apache MahoutTo start, you need to install the following prerequisites:<br /><br /> * JDK 1.6 or higher<br /> * Ant 1.7 or higher<br /> * If you want to build the Mahout source, Maven 2.0.9 or 2.0.10<br /><br />You also need this article's sample code (<a href="http://www.ibm.com/developerworks/apps/download/index.jsp?contentid=426950&filename=j-mahout.zip&method=http&locale=">Download</a>), which includes a copy of Mahout and its dependencies. Follow these steps to install the sample code:<br /><br /> 1. unzip sample.zip<br /> 2. cd apache-mahout-examples<br /> 3. ant install<br /><br />Step 3 downloads the necessary Wikipedia files and compiles the code. The Wikipedia file used is approximately 2.5 gigabytes, so download times will depend on your bandwidth. It also uncompresses the files. You need to have 10 GB of free space.<br />Occasionally, there may be an error. <br />You can try commenting the lines of download of 2.5 GB of wiki pages and download them separately with the link given. Then ant install will give you build failed. Do not worry. A folder named Wikipedia would have been created in the apache-mahout-examples directory. If not, create one. Place the downloaded content of wikipedia file there. Do ant install again. Now those files already downloaded will just uncompress and it will take about half an hour. Depending upon your system configuration, this may vary. The result will be installation of mahout.Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0tag:blogger.com,1999:blog-765776180760052922.post-60423166271908402972010-09-05T23:10:00.000-07:002010-09-05T23:20:53.479-07:00Installing antFirst, Please make sure you have the Latest jdk. Currently java1.6 with update 21 would be required. <br />Now download ant from http://ant.apache.org/<br />The binary edition of Ant is shipped with 3 different compression formats:<br /><br /> 1. .zip - Recommended compression format for Windows, can also be used on other platforms. Supported by many programs and some operating systems natively.<br /> 2. .tar.gz - Uses the tar program to gather files together, and gzip to compress and uncompress.<br /> 3. .tar.bz2 - Uses the tar program to gather files together, and bzip2 to compress and uncompress..<br /><br />Choose the format that is best supported for your platform. <br />Next step would be to extract the folder and place in the directory.<br />Set environmental variables JAVA_HOME to your Java environment, ANT_HOME to the directory you uncompressed Ant to, and add ${ANT_HOME}/bin (Unix) or %ANT_HOME%/bin (Windows) to your PATH.<br /><br /><B> Setting up environment Variables.</B><br />From the Start Menu, select Start > Settings > Control Panel.<br />Double-click System to open the System Properties window.<br />On the Advanced tab, select environmental variables .<br />Modify each environmental or system variable.<br />Set the PATH environment variable to include the directory where you installed the Ant bin directory:<br /><br /> 1. Find the PATH environment variable in the list. If PATH is not listed, click on New under the System variables section.<br /> 2. Type %ANT_HOME%\bin;%JAVA_HOME%\bin;<br /> Important: If there are other variables listed, create a new variable separated by a semicolon. Ensure there are no spaces before or after the semicolon.<br /><br />Set the ANT_HOME environment variable to the directory where you installed Ant:<br /><br /> 1. Click on New under the System variables section.<br /> 2. Type ANT_HOME in the variable name field.<br /> 3. Type the location where you extracted your ant in the variable value field.<br /><br />Set the JAVA_HOME environment variable to the directory where you installed the J2SE SDK application:<br /><br /> 1. Click on New under the System variables section.<br /> 2. Type JAVA_HOME in the variable name field.<br /> 3. Type C:\j2sdk1.4.2_13 in the variable value field.<br /><br />Done!<br />You've just installed ant. To check, open command prompt and type ant -version.<br />If it shows you the version of ant you installed, everything went on fine.<br />Congrats.Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0tag:blogger.com,1999:blog-765776180760052922.post-38972588789405433192010-08-27T07:37:00.000-07:002010-08-27T07:54:33.854-07:00Using Subeclipse Behind Proxy ServerI loaded the subeclipse plug-in in my eclipse. But it just wouldn't work. I realized this was due to the proxy server I was using. I had configured the proxy settings in Eclipse but surprisingly subeclipse doesn't take proxy from eclipse. Servers in the windows file have to be configured to do the same. Here's how...<br /><ul><br /><li>Open the servers file in your favorite text editor. For this, in RUN type %APPDATA%\Subversion\servers and press Enter. A dialog box appears asking you via which program you would like to open it. Click on any text editor.</li><br /><li>Scroll to the end of the file. You'll see a Global Section. In the Global section of the file uncomment http-proxy-host and http-proxy-port (and user name and password in case you are using it) and give the required values. That is where the subeclipse will take the settings to connect to the internet from.</li><br /><li>Now go back to the SVN Repository view in Eclipse and refresh the repository.</li><br /></ul>Congrats! It's done.Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0tag:blogger.com,1999:blog-765776180760052922.post-46607361703287742912010-07-09T04:02:00.000-07:002010-07-09T04:17:16.432-07:00Changing From one Drive to another in Command LineA quick post to document what came as a little surprising to me. <br /><br />While using the Command line in Windows Vista Professional, I wanted to change my working directory from C to D. Any amateur would say just type D;\ but guess what, that didn't work for me. <br /><br />A little googling gave me the solution. I needed to use /d flag.<br /><br />y:\>cd /d x:\Folder1\Folder2<br />x:\Folder1\Folder2><br /><br />Good Luck!Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0tag:blogger.com,1999:blog-765776180760052922.post-7253081925910033822010-07-08T22:30:00.001-07:002010-07-08T22:56:54.108-07:00App Engine Deploy Error 409: SolutionWhen deployment of an application through App Engine fails and you try to deploy it again, an error is encountered:<br /><br /><span style="font-style:italic;">Unable to update app: Error posting to URL: https://appengine.google.com/api/appversion/create?app_id=jayati3644=1&<br />409 Conflict<br />Another transaction by user jayati07 is already in progress for this app and major version. That user can undo the transaction with appcfg.py’s “rollback” command.<br />See the deployment console for more details</span><br /><br />Documentation given is not much help. But it's easy to do. Here's how...<br /><br />Execute the appcfg.cmd(for Windows) appcfg.sh(for Linux) in the bin directory of your Appengine installation. These instructions are for the Java SDK. For a python one, you may use appcfg.py. Appengine is usually installed in the plugins directory of eclipse(if you are using Eclipse) or wherever you downloaded it. <br /><br /><span style="font-weight:bold;">APPENGINEDIR/bin/appcfg.sh rollback /YOURAPP/war</span><br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhHODJ0Pp4Mok_2bnt1AEOLTf_ClBdxg2v-DRgNnzeH8_HmXK7D_yTUoCsAZMYhq9IciUlqO-LN3iHC04zuKn1Od4ONHuAfUEfvCnP49GQg0BabFz83Q_8bfrqXvnqwWDepuHTmGkvLJfNY/s1600/rollback.jpg.bmp"><img style="cursor:pointer; cursor:hand;width: 320px; height: 246px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhHODJ0Pp4Mok_2bnt1AEOLTf_ClBdxg2v-DRgNnzeH8_HmXK7D_yTUoCsAZMYhq9IciUlqO-LN3iHC04zuKn1Od4ONHuAfUEfvCnP49GQg0BabFz83Q_8bfrqXvnqwWDepuHTmGkvLJfNY/s320/rollback.jpg.bmp" border="0" alt=""id="BLOGGER_PHOTO_ID_5491780638795433682" /></a><br /><br />You will get output similar to the one in this screenshot. Now you are free to deploy as you want.Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com4tag:blogger.com,1999:blog-765776180760052922.post-31147058286823113012010-06-13T11:55:00.000-07:002010-06-13T12:13:44.508-07:00Google Web Tool Kit on NetBeans IDEhttp://code.google.com/webtoolkit/overview.html<br /><br />Google Web Toolkit (GWT) is a development toolkit for building and optimizing complex browser-based applications. For Starting a project using GWT, you need the following:<br />1. You will need the Java SDK version 1.5 or later. If necessary, download and install the Java SE Development Kit (JDK) for your platform. Mac users, see Apple's Java developer site to download and install the latest version of the Java Developer Kit available for Mac OS X.<br />I had a Netbeans 6.8 installed so used it. This post is dedicated to using GWT on Netbeans.<br />2. Apache Ant is also necessary to run command line arguments. If you don't already have it, install Apache Ant. <br /><br />Download the Google Web Tool Kit Software Development Kit (gwt-2.0.3.zip) and unzip it to gwt-2.0.3 in your working folder. GWT-SDK does not have an installer application. All the files you need to run and use the SDK are located in the extracted directory. <br /><br />For using GWT on Netbeans, you have to download and install a plugin for netbeans : gwt4nb from https://gwt4nb.dev.java.net/. Optionally, you can download and install it directly from IDE's plugin Manager:<br />Chooze Tools>Plugins.<br />In the Dialog Box click on the available plugins tab and type gwt in the search box on the top-right side. The plugin would appear. Click on the check Box beside it. And click on the install button. The plugin gets installed. Click on close.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgHXhia7-q4omLC3QfrtZ8sQG8jcURE0epqh4STxXWTuEJKP148HM915Oq-XMp2WevkDejC4CvXxnFUQrU9jRcQJN6O5PAzy6oy4SyzueMXGt9EcraNtjiO6aiChFsWOoSeEjCgjOdpvN9N/s1600/1.png"><img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 220px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgHXhia7-q4omLC3QfrtZ8sQG8jcURE0epqh4STxXWTuEJKP148HM915Oq-XMp2WevkDejC4CvXxnFUQrU9jRcQJN6O5PAzy6oy4SyzueMXGt9EcraNtjiO6aiChFsWOoSeEjCgjOdpvN9N/s320/1.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5482338072233563410" /></a><br />The next step is to Create the Source Structure of a GWT Application:<br />The source structure of the application you create must include the GWT JAR files, the GWT module project configuration file, as well as some standard artifacts such as the Java entry point. Since you are using an IDE, you should not need to manually create all these files. Instead, let a wizard do the work for you. Specifically, the final panel of the New Web Application wizard is very useful in the context of creating a GWT application.<br />1.Choose File > New Project (Ctrl-Shift-N; ⌘-Shift-N on Mac). Under Categories, select Web (or Java Web). Under Projects, select Web Application. Click Next. <br />2.In step 2, Name and Location, type HelloGWT in Project Name. You can also specify the location of the project by typing in a path on your computer in Project Location field. Click Next. <br />3.In the Server and Settings step, select any server that you have registered in the IDE. If you included Tomcat or GlassFish when installing the IDE, they display in the drop-down list. <br /><br />To register a server in the IDE, click the Add button to open a wizard that guides you through the registration process. <br />4.Specify the Java version you are using. Click Next. <br />Note: This tutorial supports GWT version 1.5 and higher. GWT 1.4 does not support Java EE 5, so if you are using this version you must also set the Java EE Version to 1.4. Otherwise, for example, Java EE 5 annotations will cause compilation errors.<br />5.In the Frameworks step, select GWT. <br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtYgB1aYQV-JtioZz3_-6YMq1K727wDrIFsoMTYE7-7HRNsLi9zghDrjeKSpjkGZ_SxTOq9jf1ZcXpioUCusv7-hRudtO7N5lo88eASRYh3C5kK5DThwfO9RYd7ZCcXmHoMai1qybgZ-hM/s1600/3.png"><img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 291px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtYgB1aYQV-JtioZz3_-6YMq1K727wDrIFsoMTYE7-7HRNsLi9zghDrjeKSpjkGZ_SxTOq9jf1ZcXpioUCusv7-hRudtO7N5lo88eASRYh3C5kK5DThwfO9RYd7ZCcXmHoMai1qybgZ-hM/s320/3.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5482336256607415138" /></a><br />When you select the GWT framework, the following fields become available: <br />1) GWT Installation Folder: Specify the path to the folder where you downloaded the Google Web Toolkit at the start of this tutorial. If an incorrect path is specified, a red error message displays and you are not able to complete the wizard. <br />2) GWT Module: Specifies the name and location of the project module that the IDE will generate when you complete the wizard. The project module is an XML file that configures a GWT application. For example, it is used to specify the class instantiated by GWT when the module is loaded. Note that this field in the wizard also determines the main package of the application. By default, the main package is org.yournamehere and the project module is Main. For purposes of this tutorial, leave the default entries unchanged. <br />Click Finish. The IDE creates the HelloGWT project. The project contains all of your sources, libraries, and project metadata, such as the project's Ant build script. The project opens in the IDE. You can view its file structure in the Files window and its logical structure in the Projects window.<br /><br /><a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTexNBwzxh9EHr9I8DnOQeRMR6Cd8W1aZuxL8-6QMis0yy7NFhvzyZ6OluTwyb1jOX2fOMQL-G0EJW_8gLU0uV3ZiIUjq1hnj4DlTLgcV7v3_FhsRcxSDOt3-cwJTbGomWjSxsiPu21Ooj/s1600/2.png"><img style="float:left; margin:0 10px 10px 0;cursor:pointer; cursor:hand;width: 320px; height: 182px;" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiTexNBwzxh9EHr9I8DnOQeRMR6Cd8W1aZuxL8-6QMis0yy7NFhvzyZ6OluTwyb1jOX2fOMQL-G0EJW_8gLU0uV3ZiIUjq1hnj4DlTLgcV7v3_FhsRcxSDOt3-cwJTbGomWjSxsiPu21Ooj/s320/2.png" border="0" alt=""id="BLOGGER_PHOTO_ID_5482336248299974530" /></a><br />In the Projects window, right-click the project node and choose Run. The application is built and a web archive (WAR) is created. It is deployed to the server. The server starts, if it is not running already. Your computer's default browser opens and the welcome page of the application is displayed. <br />Click the button and the text below it disappears. <br />We have got GWT working on Netbeans and have seen how a sample project can be deployed. Now you are free to play with this fantastic tool! <br />So Long...Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0tag:blogger.com,1999:blog-765776180760052922.post-75469075845482676462010-06-09T22:26:00.000-07:002010-06-10T03:49:29.952-07:00Link 'em All!I'd like to dedicate this post to something that had me bothered some time back.<br /><br />I personally am on quite a number of social netoworking sites: Facebook, Twitter, LinkedIn, Orkut and more recently gmail has come up with a new feature called as Buzz!! There are a lot more but this post ain't about the over exploitation of the social needs of a social animal. It's an irony that the connectedness on-line is leaving rest everything disconnected, but I'd just save it for another discussion. <br /><br />Managing all of accounts singlehandedly and maintaining a presence on all can drive one nuts. A great way of making this happen without losing much time and energy is "Linking 'em All". <br /><br /><span style="font-weight:bold;"><PART 1></span><br />Let's start by linking Twitter and Facebook. There are several applications using which one can do the same. The most recommended(by me ;)) is Selective Tweets. Through this one can update one's facebook status with one's latest tweet. The advantage of this application is you can control which tweet gets updated as your facebook status. <br /><br />1) Click to open <a href="http://apps.facebook.com/selectivetwitter/">Selective Tweets.</a><br />2) Click Allow.<br />3) Enter your twitter username in the Text box. <br />4) Click save.<br />P.S. : If you're currently using the Twitter application or other application to update your status, remember to remove or disable it so that it doesn't keep updating with all your tweets.Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0tag:blogger.com,1999:blog-765776180760052922.post-30585788906586979942009-10-02T11:57:00.000-07:002009-10-02T12:11:06.777-07:00Play *.rm Files With Windows Media PlayerWindows Media Player does not support Real audio and video files, and real networks does not release any patch for WMP. Thanks to competition between Microsoft and Real networks. But, Real has released a patch for other media players. So, let's use this patch for playing real video and audio files.<br /><br />1- Go to sourceforge.net website and download RealMedia Splitter from guliverkli Project. To download directly go to:<br /><a rel="nofollow" href="http://sourceforge.net/project/showfiles.php?group_id=82303&package_id=87719" target="_blank">http://sourceforge.net/project/showfiles.p...ackage_id=87719</a><br /><br />2- Extract zipped file and copy "realmediasplitter.ax" to your system directory:<br />Win9x: c:\windows\system<br /> WinXP: c:\windows\system32<br /><br />3- Click Start > Run > and type “regsvr32 realmediasplitter.ax” and then click Ok.<br /><br />4- Run your Windows Media Player, select “any file(*.*)” from file type field and open a *.rm file. Windows Media Player will display an error message that the selected file has an extension that is not recognized by Windows Media Player, but it still might be able to play it. Select check box and press ok.<br /><br />Congratulations.Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0tag:blogger.com,1999:blog-765776180760052922.post-77087579566576170062009-09-19T09:30:00.000-07:002009-09-19T09:42:46.718-07:00Broadband Connection In Fedora<span style="font-size:100%;"><span style="font-family: arial;">Usage of lan most at all times being infeasible, I'd like to introduce the configuration of broadband connection on Fedora (works for other distributions as well).<br /></span></span><ol><li>Right click on the network icon on the top panel and click on "Edit Connections..."</li><li>In the "DSL" tab, press "Add" button.</li><li>Give the connection name as per preference.<br /></li><li>Give Username and Password given by the provider and name of the Service you are using(mine was BSNL).</li><li>No need to make any further changes in any of the tabs. Click on apply.</li><li>Observe that the connection name appears on the menu that shows connections configured when you click the network icon.<br /></li><li>Click on the connection you just created.<br /><br /><span style="font-size:100%;"><span style="font-family: arial;"> Congrats! You are connected to the internet. Happy surfing!</span></span></li></ol>Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com1tag:blogger.com,1999:blog-765776180760052922.post-58641295418476733292009-08-29T23:00:00.000-07:002009-08-30T00:26:45.638-07:00Removing Kernels in Fedora<span style="font-family: arial; color: rgb(102, 51, 102);font-family:'times new roman';font-size:100%;" class="Apple-style-span" > <p style="margin-bottom: 0in; font-style: normal; font-weight: normal; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"> </span></p><p style="margin-bottom: 0in; font-style: normal; font-weight: normal; widows: 2; orphans: 2;" align="left"> <span><span><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);">Whenever you update your system, new available kernels get installed and the preexisting ones do not automatically give way to the new ones. This eats up a lot of memory. Here's how to remove them.</span></span></span></span></p><p style="margin-bottom: 0in; font-style: normal; font-weight: normal; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);"><br /></span></span></span></p> <p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);">In terminal(Main Menu > System Tools > Terminal) enter the following command to get the full release version of the kernel.</span></span></span></p> <p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><b><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);"><br /></span></span></b></span></p><p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><b><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);"># rpm -q kernel</span></span></b></span></p> <p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);"><br /></span></span></span></p><p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);">to remove a version enter:</span></span></span></p> <p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><b><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);"><br /></span></span></b></span></p><p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><b><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);"># rpm -e kernel-version</span></span></b></span></p> <p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);"><br /></span></span></span></p><p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);">using the rpm command will also clean up your grub.conf.</span></span></span></p> <p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);"><br /></span></span></span></p><p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><span class="Apple-style-span"><span class="Apple-style-span" style="color: rgb(102, 0, 0);">CAUTION: Keeping the old kernel is for backup if something goes wrong. So, be careful.</span></span></span></p><p style="margin-bottom: 0in; widows: 2; orphans: 2;" align="left"><span class="Apple-style-span"><br /></span></p> <p></p> </span>Sagacityhttp://www.blogger.com/profile/06658243588452863972noreply@blogger.com0