NerdPlanet's e-learning Blog
Nerdplanet's Blog is an elearning community site which is created to help people who have a passion about computers and in a confused state in choosing the right direction to follow for obtaining the right knowledge. Here we focus mainly on providing Tutorials on Operating systems (Windows /Linux), Networking (Routers/Firewall Configuration) and programming, which would help people to understand the basics clearly and to help them further to learn advanced concepts. We also guide people who are in need of materials to learn but who could not afford to pay a price for it. We do this because we believe that Knowledge is power and the Knowledge should be free!. This would help to build a healthy community of IT Professionals.
Archive for the ‘Tutorials’ Category

Here in this tutorial i am going to discuss about how to use wget to download files from rapidshare easily.
I am writing this tutorial because when i wanted to download multiple files from rapidshare i found the
easiest way was to use wget than any other material. Also there wasn’t any tutorial available which
clearly explains step by step process. So i thought this piece of information might be useful for many users.
Here I am going to explain how to use it in linux systems and for windows users i am planning to write
another tutorial separately.

####################################################################
NOTE: This procedure works only if you have a RAPIDSHARE PREMIUM ACCOUNT. if you dont have one
this tutorial is not for you. Use it at your own risk.
####################################################################

First Step:-

The first step is to analyze how a rapidshare download works. The concept behind it is for every download
it needs a session authenticated user cookie which refers to the users rapidshare premium account. so we
are going to see how to download the cookie first from rapidshare site.

The command for downloading the cookie from rapidshare site is:-

Linuxidiot@Nerdplanet ~]$ wget --no-check-certificate --save-cookies cookies.txt --post-data="login=$username&password=$password" https://ssl.rapidshare.com/cgi-bin/premiumzone.cgi

As you can see from the above command there are two variable which you have to pass and they are
$username= rapidshare username
$password= rapidshare password
Read the rest of this entry »



You have finally gotten all of the bugs out of that special program that has kept you in seclusion for the past several weeks. It does exactly what you want it to do, and you are ready to impress someone with it. You beg your boss to take time from his busy schedule for a session with your Apple, and after ten minutes of routine data entry, your program is nearing its flashy finale.

The next question appears: “How many sides on an octogon?” As your boss enters
“e..i..g…”, you stifle, “Not that key, you dummy, the ‘8′”. Too late… The Apple has already responded with a “TYPE MISMATCH” message and shut your program. One purpose of an “error trap” or “error handling routine” is to help prevent such embarrassing situations. Your Apple’s BASIC interpreter already has several built-in error traps which were designed to protect the system from your unreasonable requests, such as attempts to divide by zero or to exceed to system’s capacity (”STRING TOO LONG”, “OVERFLOW”, “FORMULA TOO COMPLEX”, “OUT OF MEMORY”). Fortunately for many applications, these traps can be avoided by
using the ONERR GOTO…..POKE 216,0 commands. ONERR GOTO… disables the system’s internal error handling routine and, upon encountering an error, transfers program processing to a statement defined by the GOTO statement, typically a replacement error handling routine of your design. The POKE 216,0 command reinstates the system’s error handling routine.

For many beginning programmers, disabling the system’s error handling routine, only to replace it with one that you must design and which uses some of your precious RAM memory seems like lunacy. The major reason for doing so is that most of the errors to which the system reacts need not be fatal to your run. The computer views these errors as fatal because the contexts in which they may occur are so diverse that the only general solution that ensures protection to your computer is to terminate your run. However, within your program the context within which an error may occur can often be much more narrowly defined, and nonfatal solutions may be developed. Some of these solutions are described below.

Read the rest of this entry »



This is my first tutorial and excuse if my english is bad. Here am going to show you the step by step process of configuring vnc server in a rpm based linux distribution (redhat/centos/fedora/suse). I am writing this tutorial because when I started learning linux, first thing I wanted was to configure a VNC server so that I can get used to linux working from a windows machine. And I really had a bad experience in the beginning to configure it.

First thing we needed to do was to install the VNC Server if its not already installed.

To check whether the vnc server and client was not installed you can execute the code mentioned below which will tell you the vnc server and client package was installed or not. In my case its already installed.

linuxidiot@CentOS-Box$ rpm -qa| grep vnc
vnc-4.0-8.1
vnc-server-4.0-8.1

Here the linuxidiot refers to the user in the system CentOS-Box, If its not installed already then we can go ahead and install the vncserver and client package.But before that you need to have root access to install an rpm package, so make sure you know the credentials for the root user . And Vncserver and client packages can be found in the rpm folder in the redhat distribution installation cds

linuxidiot@CentOS-Box$ su root
linuxidiot@CentOS-Box$ ********
root@CentOS-Box#

Note: The change ‘# ’symbol from ‘$’ in the terminal which means that you have the root privilleges. From now am going to provide only the commands prefixed with ‘#’ symbol. All you have to do is just follow the instruction as root user.
Read the rest of this entry »