Thousands of online accounts are hijacked every day. Enable 2-step verification to protect your account.

Accounts Help

Help articles Google Help Forums

Getting started with 2-step verification How it works How it works » How you sign in with 2-step verification Setup Setting up backup options Signing in using application-specific passwords Turning off 2-step verification Common issues More on 2-step verification Print this guide How it works Why you should use 2-step verification 2-step verification adds an extra layer of security to your Google Account by requiring you to have access to your phone – as well as your username and password – when you sign in. In addition to your username and password, you'll enter a code that Google will send you via text or voice message upon signing in. 2-step verification drastically reduces the chances of having the personal information in your Google account stolen by someone else. Why? Because hackers would have to not only get your password and your username, they'd have to get a hold of your phone.

Google can send you a text message if you ever forget your password. Learn more

Find Complete Information about your Computer in single click

If you were required to find the complete information about your system like the OS installed, Memory, Service Pack, Computer Model, Processes running, RAM information, Disk utilization etc what would you have done? I am sure it would take quite some time for you to find all these. Here is a cool tool that I came across recently called Computer Info Tool that does everything for you and you don’t need to manually find the information yourself, as it will list everything for you and display them in a window. All you need to do is just click and run it. The tool is actually a .hta file and is not a tool to install. Hta file is a directexecutable script that on running gives you the results. This Computer Info Tool is also an executable script that has been saved as .hta file for you to double click and execute it directly. Features: • Lists all the important computer information like OS installed, Memory, Service Pack, Computer Model, Processes running, RAM information, Disk utilization, Hard Disk information, Processor information, User accounts and other things. • Moreover, you can also either shutdown the system, restart, kill any process or generate this report in a sheet easily. • Free code to use and share. I have saved the code and created the .hta file for you to use directly. Now what you all need to do is just download the package from link below, extract the hta file and click to run it whenever you need. Download Computer Info Tool

How to Make (and Sustain) a Good First Impression Every Time

In a perfect world, friendships, relationships, and business contacts would all develop naturally and blossom exactly how you'd like, but that's not the world we live in. In reality, we're all busy people, and relationships take work—work that sometimes slips our mind. Rather than leave it all to chance, here are a few things that can help you leave a great first impression, and form that into a lasting relationship. How First Impressions Work People often say "you never get a second chance to make a first impression", and that's actually quite true—which is why it's so important to start on the right foot. In fact, one popular study showed that those impressions can form in just a few seconds: Consider one study in which untrained subjects were shown 20- to 32-second video-taped segments of job applicants greeting interviewers. The subjects then rated the applicants on attributes such as self-assurance and likability. Surprisingly, their assessments were very close to those of trained interviewers who spent at least 20 minutes with each applicant. What semblance of a person—one with a distinct appearance, history and complex personality—could have been captured in such a fleeting moment? Not only that, but after they're formed, those impressions become pretty set in stone.PsychCentral notes that even if you were to contradict someone's first impression of you, it would only apply in that particular context. So, if you had a bad interview with your new boss, don't expect to change his perception of you too easily. You may have been very likable at the office's holiday party, for example, but when you step back into the office environment his first impression will still reflect how he thinks of you (though he'll probably like you more in the context of office parties). So, you want to make sure you get it right on that first meeting, since that impression can be hard to turn around. How to Make Sure Your First Impression Is a Good One So, knowing that, how do you make the best first impression possible? Everyone's different, and while you don't want to be too formulaic, there are definitely a few things you'll want to keep in mind that should universally help show you in a positive light. Be On Time: If this first impression is to be made at a scheduled meeting—like a job interview, perhaps—it should go without saying that tardiness will not work in your favor. Do whatever it takes to be on time. CareerBuilder.com suggests arriving five to ten minutes early—any earlier than that and the person you're meeting might feel rushed and you might look desperate. If you're early, just stop off at a nearby coffee shop to collect your thoughts. Dress and Groom Yourself Accordingly: Also among the obvious is to make sure you look presentable whenever you meet someone new. That means dressing up for a job interview, or putting on nice, clean, situation-appropriate clothes for social situations. It isn't difficult and itdoesn't have to cost you much, either, so there's no excuse for wearing the same clothes you wore to mow the lawn today. When in doubt, err on the side of more formal. Being underdressed is worse than being overdressed. Photo by buddawiggi. Be Aware of Your Body Language: Your body language says a whole lot on a first meeting. If you're nervous, you're probably going to look more introverted or disinterested than you actually are. Smile, try to keep from fidgeting, and adopt an "open" posture—that means no crossed arms or crossed legs. A nice tilt of the head can also be the difference between looking bored and actually being interested. If all that sounds like too much to think about at once, personal development weblog The Positivity Blog recommends you do one thing: just act like you're meeting a good friend. If you just imagine that the person you have just met and are talking to is one of your best friends you'll probably adjust unconsciously and start to smile, open up your body-language to a very friendly and warm position and reduce any nervousness or weirdness in your tone of voice and body language. Don't overdo it though, you might not want to hug and kiss right away. MSN offers another helpful tip: mirror the body language of the person you're talking to. Generally, that should help you capture the tone of the meeting in your own body language. You don't want to go overboard, obviously—no Groucho Marx impressions, please—but watching them can provide some hints. While you're at it, you'll probably want to check out the formula for the scientifically perfect handshake. Since it's the first thing you usually do when meeting someone, it can have a big impact on their first impression of you. Use Their Name: Find a time to use the person's name in conversation. Again, you don't want to overdo it and say their name at the end of every sentence, but a few uses will not only make the meeting more personable, but it'll help you remember their name for later on. Don't Talk About Yourself Too Much: Job interviews may be somewhat exempt from this rule, but generally, you want to be careful of taking over the conversation. Sociologist Charles Derber calls this "conversational narcissism", and you probably don't even realize that you're doing it: The quality of any interaction depends on the tendencies of those involved to seek and share attention. Competition develops when people seek to focus attention mainly on themselves; cooperation occurs when the participants are willing and able to give it. I highly recommend you read up on conversational narcissism over at weblog The Art of Manliness—they've done a good job of summarizing some of Derber's views. People love talking about themselves, and if you can strike a good balance between them and you during a conversation, they're likely to form a more positive impression and find you charming. Photo by bpsusf. Don't Be Afraid to Show Your Flaws: While you don't want to tell someone your whole life's story (especially the more intimate details), you don't need to look perfect. Showing some of your little flaws will not only make you look honest, but you'll look a little less robotic, too. Plus, if you're in a job interview, you won't perform the fatal flaw ofpresenting "fake weaknesses". Be Prepared: Lastly, remember that first impressions can happen anywhere, even when you don't expect it. These rules don't just apply to premeditated job interviews; they apply to everyone you meet, whether it be at a social gathering or just a trip to the grocery store. As such, make sure you always carry yourself as you would in those situations. Otherwise, you never know what you might miss out on. This is also a good point to make sure your internet personality matches the one you'd like to project. Make That Impression Last The last step, of course, is keeping up that good impression. Whether you're turning that new acquaintance into a business contact, friend, or your boss, there are a few things you can do to make them remember you fondly. Keep a Database of Contacts: It's a sad fact of life, but a lot of us are very "out of sight, out of mind"—if someone isn't a close friend or coworker, you can easily forget about them and that relationship will fizzle. I usually separate different groups of people into different databases, too—my Google contact list is mostly personal friends and family, while work contacts stay in a completely separate address book so they don't get mixed up. I also make sure to add new people as soon as I get their business cards, with a few notes on where and how I met them, when applicable. These databases do two things: they help you remember who those acquaintances are so you don't seem forgetful, and for the closer friends, they help you remember to contact them if you haven't seen them in awhile. Which brings us to the next step: Touch Base Regularly: Once you've got a good database going, make sure you keep in contact with those people. Again, technology can help a lot with this: set up calendar reminders for regular phone calls or text messages, and use social networking to keep up with older friends and acquaintances. Every week or so, go through your contacts and see if there are any friends or family members you haven't talked to in a while. You don't need to go crazy—not everyone will appreciate an hour-long impromptu phone calls—but a simple Facebook message asking what's going on in their life can mean a lot to some people. Obviously, the form of communication depends on the person; your grandma would probably prefer some more direct interaction. Photo by Scott Raymond. Reciprocate: This is very important, and is often forgotten in many relationships—both work-related and social. It's easy to get in the "networking" mindset, where every person you meet could be of value to you later on—but don't remember that you are also of value to them. If someone does something for you—whether it's a new acquaintance helping you out with a task at work, or your friend offering up their own talents for you—make sure to ask if there's anything you can do in return. Even if there isn't, they'll remember that you asked. The key in all of this is showing your appreciation for that other person. Whether you do it in a big way or a small way, they'll remember that you care, and their perception of you will be that much better. Never forget any of the "first impression" tips, either—just because you form a closer relationship with someone doesn't mean you can stop listening or start being late. Lastly: Be Realistic Remember, though, that you don't need to keep up an active relationship with everyoneyou meet. Not everyone is an ideal close friend or business contact, so you need to make sure you're spending time on those that actually matter. Quality is more important than quantity, and it doesn't make you a bad person to say that—after all, you can only maintain relationships with so many people at once. All of these things are pretty easy to do, though, so it doesn't hurt to make a good first impression whenever possible. The more you put yourself out there, the more natural it will become.

How to Build a Chrome Extension

Google Chrome is the best web browser around right now, and part of Chrome's appeal is owed to its excellent extensions. The good news: It's not that hard to get started making your own Chrome extensions. In this guide, we'll take you from the most simple Hello World extension (no HTML or JavaScript knowledge required) to a more complex RSS-fetching extension to get you started down your path as a Chrome-extension-making guru. I released my first Chrome extension—a Google Music power-up extension called Music Plus—this summer, followed by a simpler Lifehacker Notifier extension that monitors Lifehacker's RSS feed, displays notifications of new posts in HTML 5 popups or badges, and so on. Today, we'll walk through how to make your first and simplest Hello World Chrome extension, then we'll make a light version of the Lifehacker Notifier extension that fetches an RSS feed and displays feed items in a popup window when you click your extension's button. So let's get extending! Note: While the Hello World extension requires zero knowledge of JavaScript or HTML (and, frankly, you could have a lot of fun with just that if you wanted), this second half of this post requires an understanding of both. To make it to the end of the post, some experience will be necessary. We've also previously shown you how to build a Firefox extension, so if Firefox is more your speed, you may want to check out that guide. What You Need to Know Before You Start If you're comfortable putting together a web site—that is, you know a little HTML and are familiar with JavaScript—you can make a Chrome extension. If you're new to HTML and JavaScript, our beginner's guides for learning to code and how to make a web site are great starting points. Beyond those two core competencies, there's really nothing special you need to know. Chrome extensions are delightfully easy to make if you've ever spent any time making web pages or hacking away with JavaScript, and even if you're only a beginner in those arenas, you can probably pull off a Chrome extension. So let's do just that. Our Project: From "Hello World" to RSS Fetcher For the purpose of this guide, we're going to start with a "Hello World" extension. If you're new to programming, the classic "Hello World" program is a rite of passage for getting started with any language, framework, or project, and its goal is simply to create something capable of outputting the text "Hello World". After we finish our "Hello World" project, I'll walk you through the basics of making an RSS fetching extension along the lines of the Lifehacker Notifier extension for Chrome. Basically this extension adds a button to your toolbar, monitors Lifehacker's RSS feed, and displays our posts in a handy drop-down. It also shows a popup when a new post appears and displays an unread badge on the extension button. So let's get started. Manifest.json: The Cornerstone of Your Chrome Extension Every Chrome extension consists of, at minimum, a file called manifest.json, which defines the basics of your extension—its name, description, version number, what kind of extension it is (there are a handful of different things a Chrome extension can do, which we'll talk more about below), the permissions it needs to run (e.g., what web sites it needs access to), and so on. So let's get started. Create a new folder—let's name it Hello World—and, using your favorite text editor, create a new text file called manifest.json. Copy and paste the following code into it: { "name": "Hello World!", "version": "1.0", "description": "My first Chrome extension.", "browser_action": { "default_icon": "icon.png" } } The name, version, and description are all pretty self-explanatory, butbrowser_action is something new! The browser_action property tells Chrome that we're making an extension that will add a button to the toolbar. So far, all we've done is assign an icon to that button. Basically you're telling Chrome that your extension has an icon, called icon.png, and that it's located in the same folder as yourmanifest.json file. Of course, you don't have an icon.png file in your Hello World folder just yet, so let's fix that. Download this tiny image (via) and copy it to your Hello World folder. We haven't done much yet, but you've actually already made something you can test out, so let's do that. Point Chrome to chrome://extensions/, tick the Developer mode checkbox at the top-left of that window, then click the Load unpacked extension button. Point Chrome to your Hello World folder, click Select or OK (varies by operating system), Chrome will load up your stub of an extension, and you should see your little globe icon appear in your Chrome toolbar thusly: If you try clicking your Hello World button, however, you'll notice it does an unsurprising amount of nothing. Let's fix that. Creating a Browser Action, or, Wouldn't It Be Nice if That Button Did Something? Open up your manifest.json file and add a popup action that points to an HTML file called popup.html, like so: { "name": "Hello World!", "version": "1.0", "description": "My first Chrome extension.", "browser_action": { "default_icon": "icon.png", "popup": "popup.html" } } Note: The filenames don't matter as long as you're pointing Chrome to the right files—you could call it helloworld.html in manifest.json as long as you also named your file helloworld.html. Speaking of, you now need to create popup.html. So, once again, create an HTML file called popup.html and save it in your Hello World folder. Inside popup.html, simply add the text "Hello World!" (In theory you'd want to put some valid HTML markup in there, but it's not strictly necessary, so we're going to skip it here.) Make sure you've savedmanifest.json andpopup.html, head back tochrome://extensions/, click the expand icon next to the Hello World extension in the Extension list, then click the Reload link (pictured at right). Chrome will reload the extension using your updated code. Now click the button and get ready for the money shot! Achievement unlocked! You've Hello World-ed your first Chrome extension. Nice work. Now let's take things up a notch. (If you had any trouble along the way, download my working Hello World.zip and compare it with yours.) Where Do We Go From Here? So Chrome can add buttons to your toolbar, you can click those buttons, and something can happen. Neato! You could stop your extension development here and have plenty of fun installing extensions on your friends' computers—add a little HTML image markup in place of the "Hello World!" text and you've unlocked a prankster's delight! Imagine the possibilities. Your unsuspecting friend clicks an alluring new button and—slam, goatse! Or toss in a YouTube video and... RICKROLL! (Or don't do this. Your friends won't thank you, but they might if they knew what you weren't subjecting them to.) Impressing your friends with your sparkling sense of humor will only take you so far, though. You've probably seen the basic click-button-show-drop-down behavior in tons of different Chrome extensions before. But you've also seen extensions that perform very different tasks. If you take a gander at the Chrome Extension Developer's Guide, you'll see the familiar Browser Actions at the top of the list, but you'll also notice a ton of other things your extension can do, from creating desktop notifications or adding a keyword to the omnibox to creating an options page or performing actions that modify specific web pages. When you're ready to dive deep into extension development, you'll want to page through the developer documentation to get a feel for what your extension might take advantage of. You may also want to take a look at the manifest.json documentation to get a feel for some of your other options available to your manifest.json file. For now, we're going to dive a little deeper into the browser actions. It's time to make yourself an RSS-reading and -notifying Chrome extension. So let's do it. It's Time to Next Level This Hog Now that you've safely navigated from zero to Hello World, we're going to pick up the pace a little. The "Hello World" extension didn't use a lick of JavaScript (apart from the JSON), and we didn't actually write any HTML, either. This section will rectify that. First, let's take a look at the new and improved manifest.json we'll use for this extension: { "name": "RSS Fetcher", "version": "0.1", "description": "Keep up with the latest from [example.com].", "icons": { "16" : "images/icon.png", "48" : "images/48.png", "128" : "images/128.png"}, "homepage_url": "http://insert_web_site_here.com/", "background_page": "background.html", "permissions": [ "http://insert_base_rss_url_here.com/*" ], "browser_action": { "default_icon": "images/icon.png", "default_title": "[INSERT WEB SITE NAME HERE] Fetcher", "default_popup": "popup.html" } } Let's quickly walk through what's new here. First, you'll notice I've added icons. These are the icons that will display as the extension's icon in various places, including the Extensions page of your browser and in the Chrome Web Store should you decide to distribute your work. homepage_url points to whatever site you want to associate with the extension you've written. background_page is an HTML page that will run in the background constantly, allowing you to maintain a certain state or perform regular actions for different parts of your extension. In our extension, the background page will poll the RSS feed to see if anything new has been pushed to the feed. permissions tells Chrome what special permissions you need access to. Chrome sandboxes extensions so they don't have access to all your browsing activity unless they request it (and you allow it). The permissions property allows you to set exactly what permissions you need. In our case, we need permission to load an RSS feed from a root URL, and we want to be able to create HTML 5 notifications when new items arrive. You'll have noticed that our manifest.json file also calls for a lot of new files and folders, so instead of requiring you to set them all up yourself, you can download a basic, working version of this code that fetches from the Lifehacker RSS feed here. (I've decided to include the images I used in the Lifehacker Notifier extension, but obviously you can swap out whatever images work for you.) You'll also notice that I've included jQuery. If you're unfamiliar with jQuery, it's a JavaScript framework that makes doing a lot of things in JavaScript insanely easier. If you do anything on the web with JavaScript and you're not interesting in rebuilding the wheel and you are interested in saving a lot of time, you should learn to use jQuery. (Also, lucky you! The very cool web site Codeacademy just released an introductory guide to jQuery.) This all may seem like it got complicated really quickly, but the main difference between our Hello World extension and this more complex RSS Fetcher is actually quite simple: Our popup.html file will now contain HTML and some JavaScript. Together, they'llactually do things beyond displaying "Hello World!" every time you click the button. The other thing sets Chrome extension development apart from your everyday HTML and JavaScript is the Chrome extension APIs, which provide access to all kinds of functions that blur the line between your extension and the browser. So let's try a few basics. How Our New Popup.html Works The new popup.html file in our RSS fetching extension works like this: When you click the extension's button, it loads popup.html. When that loads, it passes a call tobackground.html, asking it to fetch our RSS feed. Once background.html has successfully fetched the feed, it passes the feed's XML back to popup.html, which then parses the feed into some friendly HTML, which it then displays inside the popup. Message Passing Between Background.html and Popup.html Because of various security sandboxing going on in Chrome, some parts of your extension can't access the same APIs or information that other parts of your extension can. To get around this, one common technique you'll need to employ in your Chrome extensions involves passing messages and data back and forth between different parts of your extension. To demonstrate the basics of how this works, I've put the method that fetches the RSS feed into background.html, and I call it from popup.html. Inbackground.html, you'll notice the fetch_feed method: function fetch_feed(url, callback) { var xhr = new XMLHttpRequest(); xhr.onreadystatechange = function(data) { if (xhr.readyState == 4) { if (xhr.status == 200) { var data = xhr.responseText; callback(data); } else { callback(null); } } } // Note that any URL fetched here must // be matched by a permission in // the manifest.json file! xhr.open('GET', url, true); xhr.send(); } It's a very basic function that takes a URL and a callback function as parameters, fetches the feed, then passes it to the callback function. To listen to the other parts of your extension, we add this code: function onRequest(request, sender, callback) { if (request.action == 'fetch_feed') { fetch_feed(request.url, callback); } } // Wire up the listener. chrome.extension.onRequest.addListener(onRequest); The last line, which uses the wonderfully useful chrome.extension API, tells the page to listen to requests from other parts of the extension. When it receives one, it's going to pass it to the onRequest function. As you can see, the onRequest function then checks to see if the request is asking for an action that it knows how to handle (in this case, a request to fetch a feed), and if it does, it calls that function. Now let's jump over to the popup.html file. When it loads, the page is entirely empty. This is what kicks off changing that: $(document).ready(function() { fetch_feed(); }); Our fetch_feed method then fires off this request: function fetch_feed() { chrome.extension.sendRequest( {'action' : 'fetch_feed', 'url' : 'http://lifehacker.com/index.xml' }, function(response) { display_stories(response); } ); } As you might have guessed, chrome.extension.sendRequest sends out the request to other parts of your extension that may be listening. And as we know,background.html is listening for this exact request! So our request bounces frompopup.html to background.html, which fetches the feed, then passes it back topopup.html, which then calls a function called display_stories, passing with it the response from background.html. The display stories function (which I won't step through here but which you can see in the source) then uses a little jQuery and JavaScript to parse the XML feed and render the stories in the popup. Do you see how unbelievably easy this is??? I kid. Once you get the hang of it, though, making Chrome extensions actually is very easy, and very fun. (Obviously the complexity varies depending on what you want to make.) If you're comfortable with HTML and JavaScript (oh, and I guess CSS if you want to make it pretty), you can do so much, and the learning curve is pretty gentle. So go forth, intrepid coders, and make thee some awesome extensions! Troubleshooting You're great at everything (go you!), but you're going to stumble from time to time, particularly with your JavaScript. You'll find two invaluable tools to help debug. The first isconsole.log, which is a JavaScript method that writes text, objects, or whatever you pass it to Chrome's JavaScript console so you can catch where things may have gone wrong. The second is Chrome's awesome Developer Tools—and more specifically, the JavaScript console and DOM inspector. You can pull up the console for your popup by right-clicking your extension's button and selecting Inspect popup. Likewise, you can pull up the Developer Tools for background.html by clicking the background.htmllink in the expanded view of the extension in chrome://settings/extensions. Helpful Resources All of my Chrome extension-building knowledge comes from Google's very thorough documentation and good ol' fashioned World Wide Web searches when I'd get stuck. So you should certainly check out: The Official Google Chrome Extensions Developer's Guide: It's the starting point for everything you need to know, lays our all the various extension APIs you may want to use, and so on. If you know what kind of extension you want to make, I'd highly recommend taking an hour or so, reading through the docs, and taking notes/saving links whenever you stumble upon something that sounds like you'll need it to accomplish your extension goal. Stack Overflow's Google Chrome Extension tag page is filled with great Q&As regarding Chrome extension development. If you're stumped by something, give StackOverflow a search, give the web at large a search, and if you can't find the answer, try posting your question to Stack Overflow. It's awesome. Get Coding So, enough of this starter guide. Time for you to roll up your sleeves and do some extension development of your own. If you've got any questions, or just want to share what extensions you're planning to make, let's hear it in the comments.