Just found out this videos, so simply he explained.
Love and Aloneness
Being in Love
Sunday, October 04, 2009
Sunday, August 30, 2009
CS 1.6 Server Setup : Quick and Easy
Sometimes a bad thing drives a good thing. So when i was banned from ALVB i was really angry and i decided to setup my own server. Although i knew very well that no way i can host it for 24x7. Still i tried. And i cant explain to you how much happy i was the first time few guys came to my server.
Now there is no more ban on me on ALVB and i am a reguler player there. Still that one time ban is the reason for something good that i did.
Few days ago a SE7EN asked me for help that he wants to setup his own server. I shared my experience with him and i felt really good when he told me that he now has his own server.
So if you also want to setup your own CS 1.6 server just follow the steps below. Enjoy!!!
::Server Setup::
1. Copy your current CS 1.6 setup to another folder. This will reduce the number of files you need to download
e.g. c:\CSserver
2. Download and save HLDSUpdateTool.exe under your new folder
3. Run the HLDSUpdateTool.exe using the below command. Don't forget the ending DOT, it means your game folder is current folder where all files will be downloaded
C:\CSserver>hldsupdatetool -command update -game cstrike -dir .
4. Once it says update is completed, delete all .DLL files in C:\CSserver
C:\CSserver>del *.dll
5. Go to your CS 1.6 game folder from where you have copied previously. Copy all .DLL files and paste in current folder. This will solve your protocol 48 problem.
6. In your desktop create a shortcut to hlds.exe in C:\CSserver folder and name it as something like "CS 1.6 Server Console"
7. Right click on the new shortcut and edit the target as below. This will start your server with Dust2 map and that also in console mode
"C:\CSserver\hlds.exe" -game cstrike +map de_dust2 -console
Do not use -autoupdate option or your DLL files may get updated and you will get protocol error again.
8. Double click on the new created shortcut to start your new server
9. Start your CS 1.6 game using your old shortcut and connect to your local IP which is for me 192.168.1.2
10. Tell your friend your public IP address
www.whatsmyip.com
::Troubleshooting::
1. Friend gets message that server is Lan only.
S: In console run the command below.
sv_lan 0
Or you can set this command in your server.cfg file under cstrike folder so that you don't have to do this every time you start the server.
2. You or friend is getting Protocol error while connecting to the server.
S: Follow the replace .DLL step (Server Setup Step 5)
Labels:
counterstrike,
game,
howto,
server
Saturday, June 16, 2007
Google, customized
I am a fan of Google not just because it has a very powerful search engine but also due to the wonderful ideas it comes out with. One of its many interesting services is the Custom Search Engine which is a customized version of Google's original search engine which someone can customize according to his/her needs. Although i knew about this service a long time ago, but i had not the proper knowledge to use or rather understand the usefulness of this great service. When i was really in need of something like this i understood how much it can help me.
So, i decided to try my hands on it and now i have two CSEs (i am not talking about my highest technical qualification :D) fully customized to search only what i require from Google and strip out everything useless.
So here they are...
Java Developer's Search Engine
Network Administration Student's Search Engine
The buttons on the side telling you "Add to Google" is another interesting service by Google called iGoogle which also helps me many ways.
The main feature of this service is Collaboration i.e. anyone can customize this search engine. Suppose some one is expert in Network Administration so he can add sites with more useful information to the include list, add sites with mainly ads to the exclude list etc. And the greatest thing is that the person does not need my permission for doing all this. isn't is great? now you can also customize this search engines and add your own findings from the internet to make this CSE more information rich.
But i am never a gentle man when it comes to testing, so after creating them i decided to test them and the result was really nice. For example try to search for "database" on both CSEs and see how much the results are varying.
So, go on try these CSEs and hey don't forget to add sites that you think are really usefull for these CSEs.
Wednesday, March 21, 2007
Manually Deploying A New Tomcat Web Application ...continue
As promised in my last post, i will describe the process of writing and deploying servlets on Tomcat.
Servlets are java classes which can handle HTTP request and send dynamic response back to the client. Unlike JSP pages, servlets have to be compiled by the developer, wherese JSP pages are first transformed to servlet source files by JSP engine and then compiled to servlet classes by the servlet engine. The advantage of servlet over JSP is they need no compilation time for first time as required by JSP pages.
When deploying a Servlet class we have to put the class file in pre-defined "classes" directory which has to be under the "WEB-INF" directory. We can also put the source file there.
Here is a simple servlet source file, save it as HelloServlet.java under "WEB-INF\classes" directory.
import java.io.*;
import java.text.*;
import java.util.*;
import javax.servlet.*;
import javax.servlet.http.*;
/**
* The simplest possible servlet.
*
* @author Put Your Name Here
*/
public class HelloServlet extends HttpServlet {
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws IOException, ServletException
{
response.setContentType("text/html");
PrintWriter out = response.getWriter();
out.println("<html>");
out.println("<head>");
out.println("<title>Hello World Servlet</title>");
out.println("</head>");
out.println("<body>");
out.println("Hello World!, I am a servlet");
out.println("</body>");
out.println("</html>");
}
}
Before compiling the servlet we have to set our CLASSPATH correctly. To compile a servlet, the JAR file "servlet-api.jar" containing the required classes has to be in our classpath. It is generally found at "common\lib" directory under Tomcat installation directory. We can either set it in our environment variable or we can declare it in command-line.
Now, we will goto command prompt and compile the servlet using the following command.
This will generate a class file "HelloServlet.class" in the same directory. But, the work is still not over. We have to inform Tomcat about this servlet through our applications configuration file which is "web.xml".
<servlet>
<servlet-name> HelloServlet </servlet-name>
<servlet-class> HelloServlet </servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>HelloServlet</servlet-name>
<url-pattern>/Hello</url-pattern>
</servlet-mapping>
The contains of <servlet></servlet> tags define a servlets name ands its corresponding class by using the <servlet-name> and <servlet-class> tag. The contains of <servlet-mapping></servlet-mapping> tags define the URL which is mapped to the servlet class. It is required because when a client request a servlet class, it cannot be directly send to the client. So when a client request an URL which point to a servlet Tomcat server executes the servlet for the client and send the output back to the client. The <servlet-name> is used for identifying the servlet and the <url-pattern> tag is used to inform Tomcat that when any request for this URL arrives, executes this servlet and send its output back to the client.
Now, we are ready to test the servlet. Start Tomcat server and point our browser to the URL http://localhost:8080/app1/Hello.
import java.text.*;
import java.util.*;
import javax.servlet.*;
import javax.servlet.http.*;
/**
* The simplest possible servlet.
*
* @author Put Your Name Here
*/
public class HelloServlet extends HttpServlet {
public void doGet(HttpServletRequest request, HttpServletResponse response)
throws IOException, ServletException
{
response.setContentType("text/html");
PrintWriter out = response.getWriter();
out.println("<html>");
out.println("<head>");
out.println("<title>Hello World Servlet</title>");
out.println("</head>");
out.println("<body>");
out.println("Hello World!, I am a servlet");
out.println("</body>");
out.println("</html>");
}
}
Before compiling the servlet we have to set our CLASSPATH correctly. To compile a servlet, the JAR file "servlet-api.jar" containing the required classes has to be in our classpath. It is generally found at "common\lib" directory under Tomcat installation directory. We can either set it in our environment variable or we can declare it in command-line.
Now, we will goto command prompt and compile the servlet using the following command.
D:\tomcat5\webapps\app1\WEB-INF\classes>javac -classpath %CLASSPATH%;D:\tomcat5\common\lib\servlet-api.jar HelloServlet.java
This will generate a class file "HelloServlet.class" in the same directory. But, the work is still not over. We have to inform Tomcat about this servlet through our applications configuration file which is "web.xml".
So, add the following lines in web.xml between the tags <web-app></web-app>.
<servlet>
<servlet-name> HelloServlet </servlet-name>
<servlet-class> HelloServlet </servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>HelloServlet</servlet-name>
<url-pattern>/Hello</url-pattern>
</servlet-mapping>
The contains of <servlet></servlet> tags define a servlets name ands its corresponding class by using the <servlet-name> and <servlet-class> tag. The contains of <servlet-mapping></servlet-mapping> tags define the URL which is mapped to the servlet class. It is required because when a client request a servlet class, it cannot be directly send to the client. So when a client request an URL which point to a servlet Tomcat server executes the servlet for the client and send the output back to the client. The <servlet-name> is used for identifying the servlet and the <url-pattern> tag is used to inform Tomcat that when any request for this URL arrives, executes this servlet and send its output back to the client.
Now, we are ready to test the servlet. Start Tomcat server and point our browser to the URL http://localhost:8080/app1/Hello.
Tuesday, March 20, 2007
Manually Deploying A New Tomcat Web Application
Tomcat is the first choice for all students,like me, who have started learning JSP or servlet. But again like me, many students finds it hard to get started with it as there is no in-built tool for deploying a new application in Tomcat. So in this post i am sharing my little experience on starting a new Tomcat web-application.
First of all we have to be familier with the directory structure of tomcat. In my computer Tomcat 5.5 is installed at D:\tomcat5. Under it there are 9 directories.
a) bin - all executables and the main starting point of Tomcat server
b) conf - all configuration files
c) log - all Tomcat log files
d) temp - for temporary use by Tomcat
e) common - all common use compiled java classes
f) server - all classes required to run the Tomcat server
g) shared - all classes shared by Tomcat and any other web-applications
f) work - used by Tomcat as its working directory, all applications are served form this directory
g) webapps - default folder to store web applications
among the above said, we are mainly interested in the last directory i.e. webapps.
To start a new application create a new folder under the webapps directory. Lets say we want start a application named "app1". So create a directory "app1" under "webapps". Then put all the JSP and HTML files under it.
Now at least one more directory need to be created under "webapps" and it has to be named "WEB-INF". The "WEB-INF" directory should contain a XML file named web.xml which is used as the configuration file of our appliocation. Here is a minimum web.xml file.
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
<display-name>Welcome to Tomcat</display-name>
<description>
Welcome to Tomcat
</description>
<welcome-file-list>
<welcome-file>
index.jsp
</welcome-file>
</welcome-file-list>
</web-app>
Save this as web.xml under the "WEB-INF" folder. Now we will create a JSP test page.
Save the following lines as "index.jsp" under "app1" directory.
<html>
<head>
<title>Testing Tomcat</title>
</head>
<body>
<% out.println("Hello, World! I am a JSP Page"); %>
</body>
</html>
So, after all this our directory structure should be like this
D:\tomcat5
- webapps
- app1
- index.jsp
- WEB-INF
- web.xml
Now start Tomcat and locate our browser to the address "http://localhost:8080/app1/"
Wrintng and deploying a servlet requires a little more work. So to keep things simple i will describe that in another post.
Wednesday, December 20, 2006
What Matrix Persona are you?
What Matrix Persona Are You?

You are Neo, from "The Matrix." You display a perfect fusion of heroism and compassion.
Take this quiz!
Sunday, November 12, 2006
Tux got an X-35
Few days ago RedHat Inc. gets a nasty blow from Database Major Oracle Corp. Oracle announces that it will provide support for RedHat products for half the price of RedHat. Oracle says it has 7,000 employees in support services alone while Red Hat says it employs a companywide total of 1,800. After this news stock price of RedHat shares have fallen half of that before.
But, Dennis Kekas, director of North Carolina State University's Network Technology Institute, which has a close relationship with Red Hat, said the company will have no trouble thriving in the ever-expanding open source market. "There's a lot of room out there for a lot of players to participate in the open source movement," Kekas said. "Red Hat's just too sophisticated and too strong to be threatened. They have built such a strong reputation."
Fox News: http://www.foxnews.com/story/0,2933,225925,00.html
In another strategic play Microsoft CEO Steve Ballmer said that his sales team will offer its corporate customers a chance to license its Windows operating system as part of a package offering maintenance and support for Novell's Suse Linux platform. Apparently, the goal is to make Linux interoperable with Windows and perhaps move some apps onto the Linux platform. Microsoft agreed not to sign a similar agreement with any other Linux distributor for three years. Microsoft's pact with Novell dealt a blow to other Linux distributors such as market leader Red Hat Inc. For this agreement Microsoft will make two separate up-front payments totaling $348 million to Novell.
It seems that Steve Ballmer has a better foresight then Bill Gates, that's why he has been able to take the decision inspite of the fact that in 2004, Novell reached a $536 million settlement with Microsoft over antitrust complaints in Europe and then sued its rival again in the United States. The U.S. suit alleged that Microsoft withheld technical information about Windows that Novell needed for its word processing program WordPerfect which has been sold to Microsoft.
Fox News: http://www.foxnews.com/story/0,2933,227297,00.html
Both this news reflects the increasingly important role of Linux open-source software in corporate computing systems. About 20 percent of corporate America relies on some form of Linux. Because it's available for free, Linux software long has been has been a source of consternation for Microsoft, which makes most of its money from the sale of its proprietary software. As now major software companies are eager to providing support for Linux, many problems that previously made the advancements of Linux in the market slower will be removed. Such a problem was regarding technical information about various Hardwares from manufacturer's which is required for developing Linux device drivers. It is just a start and we don't have to wait very long when every server system will be powered by Linux including major part in Desktop market.
But, Dennis Kekas, director of North Carolina State University's Network Technology Institute, which has a close relationship with Red Hat, said the company will have no trouble thriving in the ever-expanding open source market. "There's a lot of room out there for a lot of players to participate in the open source movement," Kekas said. "Red Hat's just too sophisticated and too strong to be threatened. They have built such a strong reputation."
Fox News: http://www.foxnews.com/story/0,2933,225925,00.html
In another strategic play Microsoft CEO Steve Ballmer said that his sales team will offer its corporate customers a chance to license its Windows operating system as part of a package offering maintenance and support for Novell's Suse Linux platform. Apparently, the goal is to make Linux interoperable with Windows and perhaps move some apps onto the Linux platform. Microsoft agreed not to sign a similar agreement with any other Linux distributor for three years. Microsoft's pact with Novell dealt a blow to other Linux distributors such as market leader Red Hat Inc. For this agreement Microsoft will make two separate up-front payments totaling $348 million to Novell.
It seems that Steve Ballmer has a better foresight then Bill Gates, that's why he has been able to take the decision inspite of the fact that in 2004, Novell reached a $536 million settlement with Microsoft over antitrust complaints in Europe and then sued its rival again in the United States. The U.S. suit alleged that Microsoft withheld technical information about Windows that Novell needed for its word processing program WordPerfect which has been sold to Microsoft.
Fox News: http://www.foxnews.com/story/0,2933,227297,00.html
Both this news reflects the increasingly important role of Linux open-source software in corporate computing systems. About 20 percent of corporate America relies on some form of Linux. Because it's available for free, Linux software long has been has been a source of consternation for Microsoft, which makes most of its money from the sale of its proprietary software. As now major software companies are eager to providing support for Linux, many problems that previously made the advancements of Linux in the market slower will be removed. Such a problem was regarding technical information about various Hardwares from manufacturer's which is required for developing Linux device drivers. It is just a start and we don't have to wait very long when every server system will be powered by Linux including major part in Desktop market.
Subscribe to:
Posts (Atom)

