Tamil News Live Online HD

Tamil News Live Online HD

How to Recover deleted sticky notes on windows

Most of us take important notes and reminders on the "Sticky Notes" feature available in most of the windows operating system. One of the missing feature is, we can't save the sticky notes data. This will lead to accidental deletion of data/notes. If we accidentally hit the 'X' button, the note will get deleted and the data is gone. I'm one among who experienced this situation. 

Now, Is there a way to recover the deleted information? 

The answer is "Yes" :)

Below are the two methods from where we can recover the deleted data/Information.

Method 1 (Recommended)

1. Navigate to the %AppData%\Microsoft\Sticky Notes\ directory
2. Right click on StickyNotes.snt
3. Select Restore Previous Versions
4. This will pull the file from your latest restore point, if available
5. Reboot

Method 2

1. Open  %AppData%\Microsoft\Sticky Notes\StickyNotes.snt 
2. Open with Notepad application
3.  Recover the required content from the file (Hard way) :)

Cheers!!

--
Sam

Base64 Encoding and Decoding in C

 

Base64 is a method of encoding arbitrary data as plain ASCII text. It is one of the techniques employed by the MIME standard to send data other than plain text. Base64 encoding takes three bytes, each consisting of eight bits, and represents them as four printable characters in the ASCII standard. It does that in essentially two steps. 

The first step is to convert three bytes to four numbers of six bits. Base64 only uses 6 bits. The 64 characters are 10 digits (0 to 9), 26 lowercase characters (a to z), 26 uppercase characters (A to Z) as well as '+' and '/'.

For example, the three bytes are 155, 162 and 233, the corresponding bit stream is 100110111010001011101001, which in turn corresponds to the 6-bit values 38, 58, 11 and 41.

These numbers are converted to ASCII characters in the second step using the Base64 encoding table. The 6-bit values of our example translate to the ASCII sequence "m6Lp".

• 155 -> 10011011
• 162 -> 10100010
• 233 -> 11101001

• 100110 -> 38
• 111010 -> 58
• 001011 -> 11
• 101001 -> 41

• 38 -> m
• 58 -> 6
• 11 -> L
• 41 -> p

This two-step process is applied to the whole sequence of bytes that are encoded. If the size of the original data in bytes is a multiple of three, everything works fine. If it is not, we might end up with one or two 8-bit bytes. For proper encoding, we have to append enough bytes with a value of '0' to create a 3-byte group. The Base64 uses '=' as a padding character.

Sample C Program

The following program in C can be used for Base64 Encoding and Decoding.

Code: Base64EncodeDecode.c

/*
 ============================================================================
 Name        : Base64EncodeDecode.c
 Author      : Sam Ernest Kumar
 Version     :
 Copyright   :
 Description : Base64EncoderDecoder in C, Ansi-style
 ============================================================================
 */

#include <stdio.h>
#include <string.h>
#include <stdlib.h>

/* Macro definitions */
#define TABLELEN        63
#define BUFFFERLEN      128

#define ENCODERLEN      4
#define ENCODEROPLEN    0
#define ENCODERBLOCKLEN 3

#define PADDINGCHAR     '='
#define BASE64CHARSET   "ABCDEFGHIJKLMNOPQRSTUVWXYZ"\
                        "abcdefghijklmnopqrstuvwxyz"\
                        "0123456789"\
                        "+/";
/* Function prototypes */
int Base64Encode(char *input, char *output, int oplen);
int encodeblock(char *input, char *output, int oplen);
int Base64Decode(char *input, char *output, int oplen);
int decodeblock(char *input, char *output, int oplen);
/* Its always better to move the macros and function prototypes to a header file */

int decodeblock(char *input, char *output, int oplen){
   int rc = 0;
   char decodedstr[ENCODERLEN + 1] = "";

   decodedstr[0] = input[0] << 2 | input[1] >> 4;
   decodedstr[1] = input[1] << 4 | input[2] >> 2;
   decodedstr[2] = input[2] << 6 | input[3] >> 0;
   strncat(output, decodedstr, oplen-strlen(output));

   return rc;
}

int Base64Decode(char *input, char *output, int oplen){
   char *charval = 0;
   char decoderinput[ENCODERLEN + 1] = "";
   char encodingtabe[TABLELEN + 1] = BASE64CHARSET;
   int index = 0, asciival = 0, computeval = 0, iplen = 0, rc = 0;

   iplen = strlen(input);
   while(index < iplen){
      asciival = (int)input[index];
      if(asciival == PADDINGCHAR){
         rc = decodeblock(decoderinput, output, oplen);
         break;
      }else{
         charval = strchr(encodingtabe, asciival);
         if(charval){
            decoderinput[computeval] = charval - encodingtabe;
            computeval = (computeval + 1) % 4;
            if(computeval == 0){
               rc = decodeblock(decoderinput, output, oplen);
               decoderinput[0] = decoderinput[1] =
               decoderinput[2] = decoderinput[3] = 0;
            }
         }
      }
      index++;
   }

   return rc;
}

int encodeblock(char *input, char *output, int oplen){
   int rc = 0, iplen = 0;
   char encodedstr[ENCODERLEN + 1] = "";
   char encodingtabe[TABLELEN + 1] = BASE64CHARSET;

   iplen = strlen(input);
   encodedstr[0] = encodingtabe[ input[0] >> 2 ];
   encodedstr[1] = encodingtabe[ ((input[0] & 0x03) << 4) |
                                 ((input[1] & 0xf0) >> 4) ];
   encodedstr[2] = (iplen > 1 ? encodingtabe[ ((input[1] & 0x0f) << 2) |
                                              ((input[2] & 0xc0) >> 6) ] : PADDINGCHAR);
   encodedstr[3] = (iplen > 2 ? encodingtabe[ input[2] & 0x3f ] : PADDINGCHAR);
   strncat(output, encodedstr, oplen-strlen(output));

   return rc;
}

int Base64Encode(char *input, char *output, int oplen){
   int rc = 0;
   int index = 0, ipindex = 0, iplen = 0;
   char encoderinput[ENCODERBLOCKLEN + 1] = "";

   iplen = strlen(input);
   while(ipindex < iplen){
      for(index = 0; index < 3; index++){
         if(ipindex < iplen){
            encoderinput[index] = input[ipindex];
         }else{
            encoderinput[index] = 0;
         }
         ipindex++;
      }
      rc = encodeblock(encoderinput, output, oplen);
   }

   return rc;
}

int main(void) {
   int rc = 0;
   char input[BUFFFERLEN + 1] = "";
   char encodedoutput[BUFFFERLEN + 1] = "";
   char decodedoutput[BUFFFERLEN + 1] = "";

   printf("Enter a string: \n");
   scanf("%s", input);

   rc = Base64Encode(input, encodedoutput, BUFFFERLEN);
   printf("Base64 Encoded value: %s\n", encodedoutput);

   rc = Base64Decode(encodedoutput, decodedoutput, BUFFFERLEN);
   printf("Base64 Decoded value: %s", decodedoutput);

 return rc;
}

--

Sam

How to check if your antivirus is working properly?

Here is a simple method to check if your antivirus program is working properly or not. Follow the steps below.

Open Notepad and copy the text given below.

X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

Save file as "checkantivirus.com" including quotation-marks. (not necessary to be same as this file name, but save it in extension .com

Seconds after saving this file, your Anti-Virus should come with the message that this file is infected with virus asking permission for its deletion/clean.

This file is secure and it’s not going to infect your computer in any way. It is a standard text developed by the European Institute for Computer Anti-virus Research (EICAR). Every Anti-Virus is programmed to load this file as a virus.

If your Anti-Virus will not detecting this file as a virus, then you should probably find some other Anti-Virus up to date. It means that your PC might already being infected from viruses and your current Anti-Virus does not recognize them.

--
Sam

Will the Earth blackout in 2013?

If you’ve had your fill of apocalyptic scenarios, earthquakes, volcanoes and global warming, here comes a new threat which may wipe out the world in 2013. Imagine a scene from any of Hollywood’s disaster films. An eerie scene where mobile phones go on the blink, GPS is knocked out, TVs go blank and the world is plunged into chaos.

Looks like disaster flicks aren’t too removed from reality since all this could well be the potential result of a gigantic solar storm, according to a new report by NASA. The report, a warning, says Earth and space are coming together in a way that’s new to human history. A solar storm, which is essentially violent eruptions in the sun, can eject destructive radiation and charged particles into space.  These are closely connected to magnetic fields – which are hazardous for satellites and space stations.

There are reports of a geomagnetic storm sparked by a huge solar flare that swept over the Earth in 1859. Telegraph wires shorted out and set houses on fire. A brilliant aurora was seen in Hawaii—so bright that  "people could read newspapers by [its] red and green glow." Scientists predict  that in May 2013, the sun’s solar cycle will peak at about the same level as in 1859. (This content courtesy a post on Gawker.com)

High-tech systems are critical for life as we know it today. Everything that we depend on and take for granted – air travel, GPS navigation, banking services (even a credit card transaction uses a satellite) and emergency radio communications – can all be knocked out by intense solar activity. To get an idea of scale, a massive solar storm could result in 20 times more damage than the devastation caused by Hurricane Katrina which hit south-eastern US in August 2005. The storm killed 1,800 people and caused damages worth $81 billion. Some good news is that some of the damage and destruction can be avoided with warning of an impending solar storm. There is technology to put satellites in ‘safe mode’ and disconnect transformers to protect them from destructive electrical surges.

The task of accurately forecasting a solar storm lies with the National Oceanic and Atmospheric Administration (NOAA) of the US. "Space weather forecasting is still in its infancy, but we’re making rapid progress," said Thomas Bogdan, director of NOAA’s Space Weather Prediction Center in Colorado. The key for Bogdan lies in NASA and NOAA collaborating. "NASA’s fleet of heliophysics research spacecraft provides us with up-to-the-minute information about what’s happening on the sun. They are an important complement to our own GOES and POES satellites, which focus more on the near-Earth environment."

Says Bogdon, "I believe we’re on the threshold of a new era in which space weather can be as influential in our daily lives as ordinary terrestrial weather." So far, we’ve been lucky to escape any big solar storms.  I guess we could send Bruce Willis (a la Armageddon) to save us from the Sun in true Hollywood style. But then I would rather wait for NASA and NOAA to save us from space weather.

Source: yahoo

--
Sam

writing Bug free C code

The C language provides a minimal, efficient framework. A key to writing bug-free code is learning from your mistakes. Designing a module right the first time saves time. Programming without a goal is like a sailboat without a sail. You drift. Never reinvent the wheel. Always code what to do, not how to do it. As a general rule, try to keep functions under one page.

Always review changes before checking source code back in. An API must be designed right the first time because changes to an API are costly. Before you can write bug-free code, you must have a bug-free, rock-solid base. Provide a code wrapper around all system calls. Use macros as an aid to porting so that your code base does not change at all. Try to hide how something works to provide an abstraction that aids.

Macro names should be in uppercase. Macros beginning with an underscore are to be used only in other macros, not explicitly in source code. New data types should be in uppercase. New data types must be declared with a typedef statement, not a macro definition. Variables should be named using Hungarian notation. Hungarian notation allows you to know a variable's data type without seeing the data declaration. Functions should be named using the module/verb/noun convention. Think twice and do once.

If I had eight hours to chop down a tree, 

I'd spend six hours sharpening my axe.  -- AbrahamLincoln

--

Sam

A Leader Should Know How to Manage Failure

Question: Could you give an example, from your own experience, of how leaders should manage failure?

APJ Abdul Kalam: Let me tell you about my experience. In 1973 I became the project director of India 's satellite launch vehicle program, commonly called the SLV-3. Our goal was to put India 's "Rohini" satellite into orbit by 1980. I was given funds and human resources -- but was told clearly that by 1980 we had to launch the satellite into space. Thousands of people worked together in scientific and technical teams towards that goal.

By 1979 -- I think the month was August -- we thought we were ready. As the project director, I went to the control center for the launch. At four minutes before the satellite launch, the computer began to go through the checklist of items that needed to be checked. One minute later, the computer program put the launch on hold; the display showed that some control components were not in order. My experts -- I had four or five of them with me -- told me not to worry; they had done their calculations and there was enough reserve fuel. So I bypassed the computer, switched to manual mode, and launched the rocket. In the first stage, everything worked fine. In the second stage, a problem developed. Instead of the satellite going into orbit, the whole rocket system plunged into the Bay of Bengal . It was a big failure.

That day, the chairman of the Indian Space Research Organization, Prof. Satish Dhawan, had called a press conference. The launch was at 7:00 am, and the press conference -- where journalists from around the world were present -- was at 7:45 am at ISRO's satellite launch range in Sriharikota [in Andhra Pradesh in southern India ]. Prof. Dhawan, the leader of the organization, conducted the press conference himself. He took responsibility for the failure -- he said that the team had worked very hard, but that it needed more technological support. He assured the media that in another year, the team would definitely succeed. Now, I was the project director, and it was my failure, but instead, he took responsibility for the failure as chairman of the organization.

The next year, in July 1980, we tried again to launch the satellite -- and this time we succeeded. The whole nation was jubilant. Again, there was a press conference. Prof. Dhawan called me aside and told me, "You conduct the press conference today."

I learned a very important lesson that day. When failure occurred, the leader of the organization owned that failure. When success came, he gave it to his team. The best management lesson I have learned did not come to me from reading a book; it came from that experience.

Source: This is from Former President of India APJ Abdul Kalam at Wharton India Economic forum, Philadelphia , March 22,2008

--

Sam