Change Pen Drive Icon

Change Drive Icon

1. Open Notepad
   [Start – All Programs – Accessrious – Notepad]
2. Copy the below Code and paste it in to Notepad
   

   [Autorun]
   icon=icon.ico

   
   
   (icon=icon.ico   => in this ico file required)
   
   
3. Then go to “Save as…”
   [File – Save as…]
4. Type File name : autorun.inf
5. Save the file to your Flash drive
6. Find a Icon file
   Extension should be .ico , as an example icon.ico Sometimes .ico part may hide
7. Copy your icon.ico file to Flash Drive
8. To see the result, unplug the Flash Drive and plug it again
9. Open My Computer

Read More

Choose Best Java IDE

Choose Best Java IDE:

-Every Java developer desires a programming editor or IDE that may assist with the grungier elements of writing Java and victimization category libraries and frameworks. Deciding that editor or IDE can best suit you depends on many things, together with the character of the comes below development, your role within the organization, the method employed by the event team, and your level and skills as a software engineer. extra issues are whether or not the team has standardized on tools, and your personal preferences.

-IDE can parse source code because it is written, giving it a syntactic understanding of the code. this enables advanced options like code generators, auto-completion, refactoring, and debuggers. Here are the best-of-breed Java IDES.

1. Eclipse: Open Source (Free)

-Eclipse could be a free IDE that has taken the Java industry by storm. Built on a plugin design, Eclipse is very protrusile and customizable. Third-party vendors have embraced Eclipse and square measure more and more providing Eclipse integration. Eclipse is constructed on its own SWT user interface library. Eclipse excels at refactoring, J2EE support, and plugin support. the sole current weakness of Eclipse is its lack of a Swing or SWT user interface designer.

-The eclipse platform provides tool developers with final flexibility and management over their technology.

-Advantage:

-IDE appearance wonderful, across all systems, and it's quite responsive...great interface overall!

-ability to format to your line wrapping dimension.

-easy to share code between projects

-refactoring support ascends from heaven

-pasting code formats code automatically!

-editor tabs may be affected around with drag-and-drop.

-amazing management over the info of java ASCII text file, which may be saved as a profile.

-very tiny project-specific footprint on directory tree (.project, .classpath).

-package read has terribly nice filtering skills, for what to show/not show (can currently filter closed packages, select operating set).

-Disadvantage: 

-doesn't come with native servlet/J2EE aware plugins (you have to configure a plugin, such as lomboz, webtools or myeclipse).

-no "soft" line wrapping (only exhausting wrapping by provision the format command).

-cannot produce new buffer while not making coupled file.

2. Netbeans: Open Source (Free)

-Netbeans could be a free IDE backed by Sun Microsystems. it's the most competition of Eclipse. Netbeans is constructed on a plugin design, and it's respectable third-party merchant support. the most advantage of Netbeans over Eclipse is Netbean's glorious graphical user interface designer. It includes syntax light and language support for Java, JSP, XML/XHTML, visual design tools, code generators, ant and CVS support.

-Advantage:

-creating custom tag libraries was terribly simple, step by step method easy (once I knew wherever to look).

-code formatting/reindent task (located in context menu), particularly nice for XML/XHTML.

-very nice code completion engine, never appears too aggressive, terribly thorough in what it includes, esp jsp.

-can specify default request parameters once testing a page.
the whole Tomcat integration module is superb!.

-HTTP monitor integration terribly nice, again, a part of integration with servlet engine, A++.

-can move around tabs, i like this (tabs additionally do not wrap to next line, big plus).

-very acceptable IDE layout.

-validate JSP is extremely useful and quite informative...tells you specifically what's missing.

-anti-aliased text in editor.

-can right-click file and "Save as template..." that is very nice for JSP content pages

-very nice database browser, manipulator, simple to setup.
method/field navigator as a get box could be a nice plan on main UI, do not take up area.

-very responsive and fast UI.

-Disadvantage:

-no refactoring or refactoring templates (try/catch, rename field, etc...).

-wierd problems with "mounting" core libraries, causes errors and features to not work properly, like code completion...the whole "mounting" issue is extremely strange.

-new file wizards too minimial.

-limited management over data format of java ASCII text file (though the defaults will not kill you and it will reformat nicely).

-Very troublesome (for newbies impossible) to feature a daily ol' jar file to a project. each mechanism appears to figure against you.

3. IntelliJ IDEA : Proprietary

-IntelliJ plan could be a industrial IDE with a loyal following that swear by it. it's glorious J2EE and interface support. it's protractile via plugins. Its standout feature is that the outstanding refactoring support.

-It provides a strong combination of increased development tools, including: refactoring, J2EE support, Ant, JUnit, and CVS integration. prepackaged with Associate in Nursing intelligent Java editor, writing help and advanced code automation tools, plan permits Java programmers to spice up their productivity whereas reducing routine time overwhelming tasks.

Read More

Top Eclipse Keyboard Shortcuts for Java Programmer

This tutorial is regarding Eclipse keyboard shortcuts, this list is by no suggests that complete and that i can counsel you guys to share eclipse shortcuts listed apart from here to create this additional helpful. Eclipse is that the most used Java development IDE and knowing Eclipse shortcuts not solely improve your productivity however additionally causes you to additional economical. you'll have longer for belongings you prefer to do. victimization keyboard shortcuts additionally helps to impress colleagues and shows that you just have an honest hold on tools you used for Java Development. If you're a Java developer, World Health Organization use Eclipse as its main IDE for all secret writing, development, and debugging purpose, then I additionally counsel you to require a glance at The Java Developer's Guide to Eclipse, 2 Edition, one among the simplest book to find out a way to use Eclipse from Java programmer's perspective.

Useful Eclipse Keyboard Shortcuts for Java Programmers:

1)      Ctrl + Shift + T for finding class even from jar

2)      Ctrl + Shift + R for finding any resource (file) including config xml files

3)      Ctrl + 1 for quick fix

4)      Ctrl + Shift + o for organize imports

Eclipse Shortcut for Quick Navigation

In this section, we will see some eclipse keyboard shortcut which helps to quickly navigate within the file and between file while reading and writing code in Eclipse.

7) Ctrl + o for quick outline going quickly to method

9) Alt + right and Alt + left for going back and forth while editing.

12) Alt + Shift + W for show in package explorer

13) Ctrl + Shift + Up and down for navigating from member to member (variables and methods)

15) Ctrl + k and Ctrl + Shift +K for find next/previous

24) Go to a type declaration: F3, This Eclipse shortcut is very useful to see function definition very quickly.

Eclipse Shortcut for Editing Code

These Eclipse shortcuts are very helpful for editing code in Eclipse.

5) Ctrl + / for commenting, uncommenting lines and blocks,

6) Ctrl + Shift + / for commenting, uncommenting lines with block comment,

8) Selecting class and pressing F4 to see its Type hierarchy

10) Ctrl + F4 or Ctrl + w for closing current file

11) Ctrl+Shirt+W for closing all files.

14) Ctrl + l go to line

16) Select text and press Ctrl + Shift + F for formatting.

17) Ctrl + F for find, find/replace

18) Ctrl + D to delete a line

19) Ctrl + Q for going to last edited place

Miscellaneous Eclipse Shortcuts

These are different Eclipse keyboard shortcuts which doesn’t fit on any category but quite helpful and make life very easy while working in Eclipse.

20) Ctrl + T for toggling between supertype and subtype

21) Go to other open editors: Ctrl + E.

22) Move to one problem (i.e.: error, warning) to the next (or previous) in a file: Ctrl +. For next, and Ctrl +, for the previous problem

23) Hop back and forth through the files you have visited: Alt + ← and Alt + →, respectively.

25) CTRL+Shift+G, which searches the workspace for references to the selected method or variable

26) Ctrl+Shift+L to view listing for all Eclipse keyboard shortcuts.

27) Alt + Shift + j to add Javadoc at any place in java source file.

28) CTRL+SHIFT+P to find closing brace. Place the cursor at the opening brace and use this.

29) Alt+Shift+X, Q to run Ant build file using keyboard shortcuts in Eclipse.

30) Ctrl + Shift +F for Autoformatting.

Here is the nice image to remember these useful Eclipse shortcuts for Java programmers:

Read More

Android Debug Bridge (adb) Wireless Connection Debugging Over Wi-Fi

We mostly connect our Android device to our computers with a USB cable for debugging purposes. It is possible to use adb over a wifi connection.

Step 1:
Make sure both your adb host computer and Android device are on the same Wifi network.

Step 2:
Connect the device to the host computer with a USB cable.

Step 3:
Set the target device to listen for a TCP/IP connection on port 5555.
Restart adb in tcpip mode with this command:
 - $ adb tcpip 5555
 - restarting in TCP mode port: 5555

Step 4:
Disconnect the USB cable from the target device.

Step 5:
Find the IP address of the Android device.

Step 6:
Connect to the device, identifying it by IP address.
 - adb connect <Your device ip address>

- $ adb connect 192.168.1.100:5555
-connected to 192.168.1.100:5555

Ex:

Read More

How To Write A Simple Batch (.bat) File

Batch files are the computer handyman’s way of getting things done. They can automate everyday tasks, shorten the required time to do something, and translate a complex process into something anyone could operate.

Since automation programs like AutoHotKey exist, many people have never written or taken the time to understand bat files, and many don’t even know what they do.

In this article, I’m going to show you how to write a simple batch file and present some basics that a user will need to understand when writing one. I’ll also provide you with a few resources for learning to write batch (.bat) files in case you’d like to go further.

Let’s say that you frequently have network issues; you’re constantly getting on thecommand prompt and typing in things like “ipconfig” and pinging Google to see what the problem is. After a while you realize that it would be a bit more efficient if you just wrote a simple BAT file, stuck it on your USB stick, and used it on the machines you troubleshoot.

Step 1: Create A BAT File

Create a new text document on your desktop. Double click the file – it should be blank inside. Now, go to file>save as, and in the “Save As” window, input a name for your BAT file and then add a “.bat” on the end (without the quotes). My file was named testBAT.bat

Step 2: Learn Some Quick Code

If you know how to run commands in the command prompt, you’ll be a wiz at creating BAT files because it’s the same language. All you’re doing is telling the command prompt what you want to put in through a file, rather than typing it every time you run the command prompt. This saves you time and effort; but it also allows you to put in some logic (like simple loops, conditional statements, etc. that procedural programming is capable of conceptually).

There are SEVEN simple commands I want to familiarize you with for this program. Commands are NOT case sensitive, so don’t worry about that.

TITLE - The Window name for the BAT file.

ECHO - the “print” statement for BAT files. Anything following the word ECHO will be displayed in the command prompt as text, on its own line.

ECHO OFF – BAT writers typically put this at the beginning of their files. It means that the program won’t show the command that you told it to run while it’s running – it’ll just run the command. I’d recommend that after you run this test program, you try removing this line from your code to see what happens.

PAUSE - This outputs the “press any key to continue…” message that you’ve seen all too many times. It’s helpful because it pauses the BAT file execution until the user tells it to go again. If you don’t put this in your program, everything will speed by and end before you can see it. People typically put this in BAT files to give the user a chance to review the material on the screen before continuing.

CLS - Clears the DOS window (helpful if things get too cluttered!).

IPCONFIG – Outputs a lot of network information into your DOS box (network admins have dreams solely based off this command).

PING - Pings an IP, letting you know if your computer was able to contact it. This command also returns the latency (ping time) and by default pings three times.

Step 3: Do Some Quick Logic

We need to plan our program out. Any good programmer will think about the general framework of their program before they dash into things – it prevents them from making logic mistakes that are hard to back out of.

For this program, we want to check the computer’s network/internet settings with an “ipconfig /all” command, and then review that information by giving the user time to read everything. Afterwards, we want to ping google.com to figure out if we really truly have access to the internet. We’ll pause the program after this as well, because we want to know for sure that they saw it.  OK. Very simple program, very simple logic. Let’s write some code.

Step 4: Write Your BAT File

Right click your BAT file and click “edit” to bring up Notepad. The whole document should be blank – ready for some epic programmer input.

Rather than walking you line by line through the code (it’s extremely short) I’m going to use a code comment (example–   CODE  ::Comment) to let you know what we just did.I’m putting the actual code in bold to make things a bit easier to process.

Start Code:

ECHO OFF 

::CMD will no longer show us what command it’s executing(cleaner)

ECHO As a network admin, I’m getting tired of having to type these commands in! Hopefully, this saves me some time in the long run. 

:: Print some text

IPCONFIG /ALL 

:: Outputs tons of network information into the command prompt

PAUSE 

:: Lets the user read the important network information

PING www.google.com 

:: Ping google to figure out if we’ve got internet!

ECHO All done pinging Google. 

::Print some text

PAUSE 

:: Give the user some time to see the results. Because this is our last line, the program will exit and the command window will close once this line finishes.

Read More

Set Video as Desktop Wallpaper

Set Video as  desktop wallpaper :

Set any  video on your desktop wallpaper then try that step, that possible using vlc player... 

Read More

14 Mistakes that will kill your independent development shop

1: Coding yourself out of business

• High-quality code is vital to independent developer success, but heads-down coding is a job, not a business.
• To be certain, you should always be thorough, with an eye toward delivering the best code you can. But make sure you have something else in the pipeline to work on when you’re done.
• When coding, it’s all too easy to focus only on the work in front of you. In fact, it’s far more efficient to devote yourself to coding than it is to task-switch between development, marketing, sales, planning, administration, and so on. But that’s exactly what you will have to do to succeed. Billable work pays the bills, but finding more work keeps your business afloat. 

2: Forgetting that you are your brand

• You may not realize it starting out, but even if you are working solo as an outside contractor with only one client, you have a brand, and that brand is you. Remember: A brand is a promise of quality and consistency, and though it can stand for whatever you think is important as a developer, it must be precise.
• How you present yourself, your work, your team, and your development philosophy is the bedrock of your brand, and it should be reflected in all facets of your business, from your website to your business card to how you discuss your work with a casual acquaintance on a day off. If you are vague or inconsistent, your business will suffer.
• Too often, independent software developers define their business by a tool or fad. Brands built around tools quickly become commodities -- would you rather hire a “Java shop” or an “expert in enterprise applications systems development”? Brands built around the latest trends can be lucrative, temporarily, but they too quickly become commodities.
• The more specific you can be about your work and what you stand for, the easier it is to distinguish yourself from others, and the easier it is to identify and locate potential clients. More important, establishing a clear brand makes it easier for potential clients to identify and locate you.

3: Trying to be everything to everybody

• Customer satisfaction is essential to your success as an independent developer, but trying to please everybody can sink your business quickly. It causes you to spread your resources too thin, in the end pleasing no one.
• This doesn’t mean you shouldn’t go the extra mile to serve clients to the best of your ability, or never take on work outside of your comfort zone. But pay attention to the limits of your abilities and resources. Overcommitting or signing up for work you can’t complete to the level your customers expect can quickly poison your business.
• Instead, be diligent about logging your work, so you can be accurate in estimating your bandwidth when special requests arise. Increment your experimentation into new areas rather than promise to deliver big, merely because you know you can learn new tools quickly. Remember -- you have a business to run, and mastering tech to the level of your brand takes time away from paying work.

4: Targeting the wrong market

• Small businesses struggling to grow out of manual systems may seem like the ideal client for your fledgling independent software business; after all, they stand to reap the greatest benefits from automation. But they can also be the least trusting of technology and outsiders, and their cash flow may not be consistent enough to afford your services.
• Targeting the “right” market is more art than science, but one vastly oversimplified maxim is to seek a combination of fit, finance, and fearlessness. Finding the best fit for your services is a complex, volatile process of ambitions, problems, needs, skills, gaps, benefits, and timing. There is likely to be no external signals for these, so you have to talk to a lot of people in various industries and organizations to find out. As you are doing this, you can assess the financial issue -- if an industry or organization can’t afford your services, the whole process is pointless. 
• Gauging “fearlessness” is more of a gut instinct. Do the players in your targeted market have the organizational courage to see your partnership through? Software systems change business operations; for many industries, and many organizations, change is scary. Don’t get lost chasing timid leads.  

5: Failing to identify the true project "champion"

• Every software project has a “champion” (or “patron” if you prefer). This is the person with the authority to write the checks to pay for your work and the will to defend your project internally to ensure it succeeds. It is essential to identify this person and cultivate a meaningful relationship, where possible.
• All too often the champion is not present, revealed, or even mentioned in consultative meetings. Worse, department heads or senior executives often insist they have the authority and budget to get the project done, when in fact that is not the case.
• Always look at who signs the checks. In some companies, department managers have discretionary budgets and are indeed the champion of their projects. In other companies, executives higher up the chain -- sometimes more than one -- are the true, hidden champions; their approval is required for project expenditures.
• It’s not unusual, especially in smaller, privately held businesses, for the company president to be presented as the project champion, but in reality the CFO or company owner has to sign the checks. Don’t be fooled into thinking you have a stronger commitment than you actually have.

6: Failing to establish (and maintain) a sales pipeline

• Selling custom software development is a slow, consultative process. Prospects may know they have a problem, but they may not be sure they really want to solve it. After all, the decision to adopt a custom solution can change the direction and foundation of an entire business; the bigger the business, the longer it takes to decide and turn. Even highly qualified, eager referrals from happy clients can take several months to close.
• This means you must always add prospects to your sales pipeline. You must also always measure time spent and results. These numbers are crucial to keeping your pipeline flowing.
• Suppose you need one client to support your business for half a year, and you can close one sale in six months for every 600 prospects you encounter. In this simplistic example, fewer than 100 prospects entering your pipeline every month could mean trouble.
• In reality, the numbers are more complicated, but the structure of the pipeline remains the same: prospects in, time elapsed, sales out. Always be tracking time to qualify, time to close, average deal size, and close percentages. Use these numbers to project future income from the current pipeline. Subtract future costs and allow for projects (and income) ending. This will give you a leading indicator: If the resulting number is negative or trending downward, you are at risk of insufficient cash flow unless you add more clients to the pipeline.

7: Failing to diversify your client base

• Most independent software developers get their start with one main client. This can be a great way to strike out on your own, but beware attempting to maintain a business this way. When that one client has a hiccup, you’ll be scrambling -- or out of business.
• The other downside of having one main client is that they may start thinking of you as “staff augmentation” instead of “valued business partner,” with demands going up and respect going down simultaneously. Three medium clients are better than one large one. Twenty small clients may be better still, as it is highly unlikely that a majority of them will suddenly stop at once.
• Think of it this way: One client is a job; multiple clients, with diverse revenue streams, comprise a business.

8: Failing to account for taxes and overhead

• Most ISVs are LLCs or S-Corps, both of which are “pass-through” companies in the United States. This means you have to account for and pay estimated taxes as you go, and usually even more at the end of the year; nothing is deducted for you. Even if you pay yourself a salary, your finances can still get complicated and surprising at the end of the year. A good CPA can help, but it takes consistent financial discipline to stay current.
• Nothing can sink your business like inattention to taxes.

9: Playing fast and loose with collections and cash flow

• Most independent development shops run “lean,” as in “very little cash buffer to fall back on.” This can turn a minor payment issue into a layoff-inducing company crisis.
• The fact is, clients don’t always pay on time; this is normal, and it helps the relationship to be flexible. But if you notice a pattern -- unexplained delays, administrative misplacement of invoices, waiting on someone to sign checks, and so on -- the client may be having internal problems they aren’t telling you about.
• This may be a temporary issue, but it could last long enough to put you under water if you’re not prepared for the possibility. Do your best to keep a buffer and pay close attention to collections. Understand the client’s payment process, who is involved, and how long it takes; investigate immediately if the pattern starts to quaver.

10: Hiring people before you have (enough) paying work for them

• A chief concern when going independent is knowing when it’s time to no longer go it alone. While staying lean at the expense of adding help is the norm for some, it’s nearly as easy to overestimate the scope or certainty of new projects and bring on eager, even inexpensive talent to help. After all, the only way to grow is to grow, right?
• But this can increase your overhead significantly without increasing your revenue -- in terms of both budget and time. Changing processes to accommodate new head count, training new hires, managing workloads -- it can quickly derail your ability to close sales and deliver the quality your customers have come to expect. Hire cautiously.

11: Thinking there are shortcuts to sales success

• Most developers who go independent do it to solve problems, write code, and deliver results. They may not enjoy marketing and sales activities, but these activities can’t be ignored -- and I do not recommend that you outsource them completely, at least not initially.
• There are no shortcuts to sales that work reliably, and each technique and tool alters your process in ways both subtle and gross. Long shots happen, but don’t bet the farm on them; instead focus on steady, reliable, refinable systems that you thoroughly understand.
• Evaluate each marketing/sales tactic and tool with the same critical eye you would use when deciding to adopt a new programming language or IDE. Play with it, run some tests and benchmarks, consider how it impacts everything else you’re doing, and resist the urge to change directions too frequently. Even the most reliable, time-tested, surefire sales techniques take time and tweaking to work, so set realistic expectations and timelines, and be wary of abandoning existing systems before you understand them. If you hopped on the latest programming trend every month, you’d never finish anything and would quickly go out of business. The same applies to marketing/sales tools and trends.
• Like it or not, there is no escaping the basic marketing/sales education process, learning curve, and effort. Go talk to prospects. There’s no other way to learn this aspect of your business.

12: Failing to document, refine, and automate processes and systems

• Processes and documentation may seem like the stuff of slow, dinosaur companies -- they may even be the chief reasons you left your corporate job -- but the truth is, an efficient independent software business depends on them.
• Chances are you already have processes you have followed, repeated, and refined for years. Some you may have even taught, directly or indirectly, to others. Do yourself a favor: Write them down, discuss and refine them often, and automate wherever possible.
• Automation is your bread and butter. You probably extol the virtues of automation to your clients all day long. But your own internal systems are manual or nonexistent. This makes results somewhat unpredictable; worse, it wastes your time -- and for an entrepreneur, time is the most critical nonrenewable resource.
• Manual or hacked-together systems are fine to start with, but don’t stay satisfied with them. Removing tedious, repetitive work reduces friction across all processes.
• Look first at where most of your nonproductive time goes, and automate that. “Automation” in this sense includes all options, from fully automatic software systems that do everything for you while you sleep, to virtual assistants to personal assistants to outsourcing specialists and any combination of the above.

13: Dropping the ball when it comes to support

• Poor support is a major reason why clients change service providers. The less support needed, the better, but being known for excellent support is pure gold -- not just because it maintains customer relationships after sales and delivery, but because outstanding support turns your customers into evangelists.
• This doesn’t only mean fixing problems in the middle of the night. It means helping clients understand every facet of your solution, teaching them how to perform tasks and fixes themselves, and providing all of the information they need to remain confident they made the right choice for their business’ future.
• Because that’s what you build for your clients: their future. You may not have to live in it for long, but they do. Support their decision and vision, and reinforce and reassure them. There is no such thing as “not my problem.”

14: Becoming a bottleneck to your own success

• When you go it alone, every decision is important, and because it’s your business, you’re on the hook to make every one of them. As your company grows, the decisions mount -- which projects to pursue, how to juggle workloads, where to investigate new leads -- and they can quickly dam up and destroy the company.

Read More