Easy WINDOWS commands at your finger tips

CONTROL: opens the control panel window

CONTROL ADMINTOOLS: opens the administrative tools

CONTROL KEYBOARD: opens keyboard properties

CONTROL COLOUR: opens display properties.Appearance tab

CONTROL FOLDERS: opens folder options

CONTROL FONTS: opens font policy management

CONTROL INTERNATIONAL or INTL.CPL: opens Regional and Language option

CONTROL MOUSE or MAIN.CPL: opens mouse properties

CONTROL USERPASSWORDS: opens User Accounts editor

CONTROL USERPASSWORDS2 or NETPLWIZ: User account access restrictions

CONTROL PRINTERS: opens faxes and printers available

APPWIZ.CPL: opens Add or Remove programs utility tool

OPTIONALFEATURES: opens Add or Remove Windows component utility

DESK.CPL: opens display properties. Themes tab

HDWWIZ.CPL: opens add hardware wizard

IRPROPS.CPL: infrared utility tool

JOY.CP: opens game controllers settings

MMSYS.CPL: opens Sound and Audio device Properties. Volume tab

SYSDM.CPL: opens System properties

TELEPHON.CPL: Opens phone and Modem options

TIMEDATE.CPL: Date and Time properties

WSCUI.CPL: opens Windows Security Center

ACCESS.CPL: opens Accessibility Options

WUAUCPL.CPL: opens Automatic Updates

POWERCFG.CPL: opens Power Options Properties

AZMAN.MSC: opens authorisation management utility tool

CERTMGR.MSC: opens certificate management tool

COMPMGMT.MSC: opens the Computer management tool

COMEXP.MSC or DCOMCNFG: opens the Computer Services management tool

DEVMGMT.MSC: opens Device Manager

EVENTVWR or EVENTVWR.MSC: opens Event Viewer

FSMGMT.MSC: opens Shared Folders

NAPCLCFG.MSC: NAP Client configuration utility tool

SERVICES.MSC: opens Service manager

TASKSCHD.MSC or CONTROL SCHEDTASKS: opens Schedule Tasks manager

GPEDIT.MSC: opens Group Policy utility tool

LUSRMGR.MSC: opens Local Users and Groups

SECPOL.MSC: opens local security settings

CIADV.MSC: opens indexing service

NTMSMGR.MSC: removable storage manager

NTMSOPRQ.MSC: removable storage operator requests

WMIMGMT.MSC: opens (WMI) Window Management Instrumentation

PERFMON or PERFMON.MSC: opens the Performance monitor

MMC: opens empty Console

MDSCHED: opens memory diagnostics tools

DXDIAG: opens DirectX diagnostics tools

ODBCAD32: opens ODBC Data source Administrator

REGEDIT or REGEDT32: opens Registry Editor

DRWTSN32: opens Dr. Watson

VERIFIER: opens Driver Verifier Manager

CLICONFG: opens SQL Server Client Network Utility

UTILMAN: opens Utility Manager

COLORCPL: opens color management

CREDWIZ: back up and recovery tool for user passwords

MOBSYNC: opens Synchronization center

MSCONFIG: opens System Configuration Utility

SYSEDIT: opens System Configuration Editor (careful while using this command)

SYSKEY: Windows Account Database Security management (careful while using this command)

What You can do with SATRT--> RUN box

Control Panel

Windows utility and applications

Disk management

Connection management

Miscellaneous commands

JAVAWS: View the cover of JAVA software (if installed)

AC3FILTER.CPL: Opens the properties AC3 Filter (if installed)

FIREFOX: Mozilla launches Firefox (if installed)

NETPROJ: allow or not connecting to a network projector (For Vista only)

LOGOFF: closes the current session

SHUTDOWN: shut down Windows

SHUTDOWN-A: to interrupt Windows shutdown

%WINDIR% or %SYSTEMROOT%: opens the Windows installation

%PROGRAMFILES%: Opens the folder where you installed other programs (Program Files)

%USERPROFILE%: opens the profile of the user currently logged

%HOMEDRIVE%: opens the browser on the partition or the operating system is installed

%HOMEPATH%: opens the currently logged user C: \ Documents and Settings \ [username]

%TEMP%: opens the temporary folder

VSP1CLN: deletes the cache for installation of the service pack 1 for Vista

IPCONFIG: list the configuration of IP addresses on your PC (for more information type IPCONFIG/? in the CMD menu)

INETCPL.CPL: opens internet properties

FIREWALL.CPL: opens windows firewall

NETSETUP.CPL: opens network setup wizard

DISKMGMT.MSC: opens disk management utility

CLEANMGR: opens disk drive clean up utility

DFRG.MSC: opens disk defragmenter

CHKDSK: complete analysis of disk partition

DISKPART: disk partitioning tool

EPLORER: Opens windows Explorer

IEXPLORER: Opens Internet explorer

WAB: opens Contacts

CHARMAP: opens Character Map

WRITE: opens WordPad

NOTEPAD: opens Notepad

CALC: opens Calculator

CLIPBRD: opens Clipbook Viewer

WINCHAT: opens Microsoft Chat Interface

SOUNDRECORDER: opens sound recording tool

DVDPLAY: run CD or DVD

WMPLAYER: opens Windows Media Player

MOVIEMK: Opens untitled Windows Movie Maker

OSK: opens on-screen Keyboard

MAGNIFY: opens Magnifier

WINCAL: opens Calendar

DIALER: opens phone Dialer

EUDCEDIT: opens Private Character Editor

NDVOL: opens the mixer volume

RSTRUI : opens Tool System Restore (For Vista only)

%WINDIR%\SYSTEM32\RESTORE\rstrui.exe: opens Tool System Restore (for XP only).

MSINFO32: Opens the System Information

MRT : launches the utility removal of malware.

Taskmgr : Opens the Windows Task Manager

CMD: opens a command prompt

MIGWIZ: Opens the tool for transferring files and settings from Windows (Vista only)

Migwiz.exe: Opens the tool for transferring files and settings from Windows (for XP only)

SIDEBAR: Open the Windows (Vista only)

Sigverif : Opens the tool for verification of signatures of files

Winver : Opens the window for your Windows version

FSQUIRT: Bluetooth Transfer Wizard

IExpress opens the wizard for creating self-extracting archives. Tutorial HERE

MBLCTR: opens the mobility center (Windows Vista only)

MSRA : Opens the Windows Remote Assistance

Mstsc : opens the tool connection Remote Desktop

MSDT: opens the diagnostic tools and support Microsoft

WERCON: opens the reporting tool and solutions to problems (for Vista only)

WINDOWSANYTIMEUPGRADE: Enables the upgrade of Windows Vista

WINWORD : opens Word (if installed)

PRINTBRMUI : Opens migration wizard printer (Vista only)

Read more...

Delete Browsing History without opening IE

Create a batch file which has the following command and run the batch file from your desktop.

To use these commands, just run them from the command line, the start menu search box in vista, or a batch file.

RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 8

RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 2

RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 1

RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 16

RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 32

RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 255

RunDll32.exe InetCpl.cpl,ClearMyTracksByProcess 4351

Delete All - "Also delete files and settings stored by add-ons"

Delete All

Passwords

Form Data

History

Cookies

Temporary Internet Files

For XP and Vista

Read more...

SPRING with and without XML

com.check;

import

org.springframework.beans.factory.BeanFactory;

import

org.springframework.beans.factory.xml.XmlBeanFactory;

import

org.springframework.context.annotation.AnnotationConfigApplicationContext;

import

org.springframework.core.io.ClassPathResource;

import

org.springframework.core.io.Resource;

/**

* @author rkesava

* */

public

class SumRunner {public static void main(String args[]) {/* Spring IoC Without XML */

System.

System.

System.

AnnotationConfigApplicationContext context =

SummaryConfig.

GameSummary gsA = context.getBean(

System.

System.

System.

GameSummary gsP = context.getBean(

System.

System.

out.println(" ================ ");out.println(" This is to call the SPRING resources without an XML configuration" );out.println(" /* Spring IoC Without XML */ "); new AnnotationConfigApplicationContext(class);"gameSummaryBean", GameSummary.class);out.println(gsA);out.println(" ================ ");out.println(" /* Spring IoC Without XML but with Properties */ ");"gameSummaryBeanWithProperties", GameSummary.class);out.println(gsP.toString());out.println(" ================ ");/* Spring IoC with XML */

System.

System.

Resource resource =

BeanFactory beanFactory =

GameSummary gsX = (GameSummary) beanFactory.getBean(

System.

System.

System.

GameSummary gsY = (GameSummary) beanFactory.getBean(

System.

System.

}

}


package com.check;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
@Configuration
public class SummaryConfig {
 @Bean
 public GameSummary gameSummaryBean() {
  return new GameSummary();
 }
 @Bean
  public GameSummary gameSummaryBeanWithProperties() {
    GameSummary gs = new GameSummary();
     gs.setClientChoice("paper");
     gs.setServerChoice("rock");
     gs.setResult("win");
     return gs;
  }
}

public

String[]

String[]

}

}

}

}

}

}

}

}

}

}

}

summary.xml

<?xml version="1.0" encoding="UTF-8"?>

<beans xmlns="http://www.springframework.org/schema/beans"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:aop="http://www.springframework.org/schema/aop"

xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd">

<bean id="gameSummaryBean" class="com.check.GameSummary" />

<bean id="gameSummaryBeanWithProp" class="com.check.GameSummary" >

<property name="clientChoice" value="paper2"/>

<property name="serverChoice" value="rock2"/>

<property name="result" value="win2"/>

</bean>

</beans>


Run it and see what difference it makes by running SPRING with an XML and without and XML. class GameSummary {private String clientChoice, serverChoice, result;private java.util.Date date = null;choices = { "rock", "paper", "scissors" };results = { "win", "lose", "tie" };public GameSummary() {public String getClientChoice() {return clientChoice;public void setClientChoice(String clientChoice) {this.clientChoice = clientChoice;public String getServerChoice() {return serverChoice;public void setServerChoice(String serverChoice) {this.serverChoice = serverChoice;public String getResult() {return result;public void setResult(String result) {this.result = result;public java.util.Date getDate() {return date;public void setDate(java.util.Date date) {this.date = date;public String toString() {return "clientChoice = " + clientChoice + ": serverChoice = " + serverChoice + ": result=" + result + ": date=" + date;out.println(" This is to call the SPRING resources with an XML configuration" );out.println(" /* Spring IoC with XML */ "); new ClassPathResource("summary.xml");new XmlBeanFactory(resource);"gameSummaryBean");out.println(gsX);out.println(" ================ ");out.println(" /* Spring IoC with XML with Properties */ ");"gameSummaryBeanWithProp");out.println(gsY);out.println(" ================ ");

package

Read more...

Hack USB drive

FOR ENABLING
1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate and then click the following registry key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesUsbStor
4. In the details pane, double-click Start.
5. In the Value data box, type 4, click Hexadecimal (if it is not already selected), and then click OK.
6. Exit Registry Editor.

FOR DISABLING

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate, and then click the following registry key:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesUsbStor
4. In the right pane, double-click Start.
5. In the Value data box, type 3, click Hexadecimal (if it is not already selected), and then click OK.
6. Quit Registry Editor.

Read more...

Integrating SAS

The SAS support team has a very good collection and design for integrating SAS with various clients like JAVA , .NET , web services etc.,

http://support.sas.com/rnd/itech/doc9/dev_guide/dist-obj/winclnt/windotnet.html

The samples code base provides many sample codes which you can download and customize it.

http://support.sas.com/kb/?nh=100&la=en&qm=3&ct=51000&qt=offering:"INTTECH"+contenttype:"sample"+"SAS+Integration+Technologies"+

Enjoy integrating SAS.

Read more...

CSS compression and Image Optimization

1.    Introduction

There have been many instances where we have struggled to increase performance of the web site because in practical situation,

·                  applications become very complex with tons of JavaScript’s and huge CSS

files and

·                  downloading that information takes time if the bandwidth is low.

Here we can increase the performance using the ideas below without changing any code.

2.    Installation Procedure

Improving the engineering design of a page or a web application usually yields the biggest savings and that should always be a primary strategy.

With the right design in place, there are many secondary strategies for improving performance such as minification of the code.

The goal of JavaScript and CSS minification is always to preserve the operational qualities of the code while reducing its overall byte footprint (both in raw terms and after gzipping, as most JavaScript and CSS served from production web servers is gzipped as part of the HTTP protocol).

The YUI Compressor is JavaScript minifier designed to be 100% safe and yield a higher compression ratio than most other tools.

The YUI Compressor is written in Java (requires Java >= 1.4) and relies on Rhino to tokenize the source JavaScript file.

It starts by analyzing the source JavaScript file to understand how it is structured. It then prints out the token stream, omitting as many white space characters as possible, and replacing all local symbols by a 1 (or 2, or 3) letter symbol wherever such a substitution is appropriate (in the face of evil features such as with, the YUI Compressor takes a defensive approach by not obfuscating any of the scopes containing the evil statement).

The CSS compression algorithm uses a set of finely tuned regular expressions to compress the source CSS file. The YUI Compressor is open-source, so don't hesitate to look at the code to understand exactly how it works.

3.    ANT build script for compression

1.     Download and Copy the following YUI Compressor jar file into the ANT LIB folder

2.      Change the following properties in the build.properties file

1. javascript.compress=true
2. jsp.compress=true

3.      Here is the sample ANT target to do the compression change the directories according to your needs.

            <target name="compressjsandcss" depends="init">

                                <taskdef name="yui-compressor" classname="net.noha.tools.ant.yuicompressor.tasks.YuiCompressorTask"/>

                                                <mkdir dir="${web.build.dir}/war/cssmin" />

                                                <mkdir dir="${web.build.dir}/war/jsmin" />

                                                <!-- invoke compressor -->

                                                <yui-compressor

                                                    warn="false"

                                                    munge="true"                                  

                                                    preserveallsemicolons="false"

                                                    fromdir="${web.build.dir}/war/css"

                                                    todir="${web.build.dir}/war/cssmin">                          

                                                </yui-compressor>

                                                <yui-compressor

                                                    warn="false"

                                                    munge="true"                                  

                                                    preserveallsemicolons="false"

                                                    fromdir="${web.build.dir}/war/js"

                                                    todir="${web.build.dir}/war/jsmin">                            

                                                </yui-compressor>

                                                <copydir dest="${web.build.dir}/war/js" src="${web.build.dir}/war/jsmin" includes="**/*.js" forceoverwrite="true" />

                                                <copydir dest="${web.build.dir}/war/css" src="${web.build.dir}/war/cssmin" includes="**/*.css" forceoverwrite="true" />    

                                <delete>

                                                <fileset dir="${web.build.dir}/war/cssmin" includes="**/*.css"/>

                                </delete>

                                <delete>

                                                <fileset dir="${web.build.dir}/war/jsmin" includes="**/*.js"/>

                                </delete>                              

                </target>

4.    Other techniques of compression

a.    Compressing the JSP pages

JSP pages when compressed are a real boom to the performance of a page

I use regular expression to achieve this.

                <target name="compressjsp" depends="init">             

                                <echo>+------------------------------------------------------------+</echo>

                        <echo>+           Cleaning the JSP files                            +</echo>

                        <echo>+CAT View module name = ${web.build.dir}/war/jsp             +</echo>

                                <echo>+------------------------------------------------------------+</echo>

                                <replaceregexp flags="g" byline="true">

                                  <regexp pattern="&amp;&gt;\n+&amp;&lt;"/>

                                  <substitution expression="&amp;&gt;&amp;&lt;"/>

                                                <fileset dir="${web.build.dir}/war" includes="**/*.jsp"/>

                                 </replaceregexp>

                                <replaceregexp match="\s+" replace=" " flags="g" byline="true">

                                                    <fileset dir="${web.build.dir}/war" includes="**/*.jsp"/>

                </replaceregexp>                                

                </target>

b.    Stripping white spaces in  a Javascript file

             <target name="stripWhiteSpace" depends="init">

                                <echo>+------------------------------------------------------------+</echo>

                        <echo>+           Cleaning the JSP files                            +</echo>

                        <echo>+CAT View module name = ${web.build.dir}/war/jsp             +</echo>

                                <echo>+------------------------------------------------------------+</echo>

                    <replaceregexp match="\s+" replace=" " flags="g" byline="true">

                      <fileset dir="${web.build.dir}/war" includes="**/*.jsp"/>

                    </replaceregexp>                 

                    <replaceregexp match="&amp;&gt;\n+&amp;&lt;" replace="&amp;&gt;&amp;&lt;" flags="g" byline="true">

                      <fileset dir="${web.build.dir}/war" includes="**/*.jsp"/>

                    </replaceregexp>   

                 </target>

c.    Stripping Line Breaks

         <target name="stripLineBreaks" depends="init">

         <copy todir="${web.build.dir}/war" overwrite="true">

           <filterchain>

             <striplinebreaks/>

           </filterchain>

           <fileset dir="${web.build.dir}/war">

             <include name="**/*.jsp"/>

           </fileset>

         </copy>

        </target>

d.   Deleting Blank Lines

        <target name="noblanklines" depends="init">

        <fileset dir="${web.build.dir}/war" includes="**/*.jsp"/>

        <filterchain>

        <tokenfilter><ignoreblank/></tokenfilter>

        </filterchain>

        <replaceregexp flags="g" byline="false"> 

                        <regexp pattern="\r\n[\s]*\r\n[\s]*\r\n"/> 

                        <substitution expression="&#13;&#10;&#13;&#10;"/> 

                        <fileset dir="${web.build.dir}/war" includes="**/*.jsp">                                           

                        </fileset> 

        </replaceregexp> 

                        <replaceregexp flags="g" byline="false"> 

                        <regexp pattern="\r\n[\s]*\r\n[\s]*\r\n"/> 

                        <substitution expression="&#13;&#10;&#13;&#10;"/> 

                        <fileset dir="${web.build.dir}/war" includes="**/*.js">                                             

                        </fileset> 

        </replaceregexp>                                

        </target>

5.    Backup Plan.

1.      If there is an issue in any of the above techniques ensure that the build.properties has the parameters set to “false”.

Read more...

Agile SCRUM and Pragmatic Agile development

Agile Scrum - An Overview

Many of us have experienced projects that drag on much longer than expected and cost more than planned. Companies looking to improve their software development processes are now exploring how Agile can help their Enterprise more reliably deliver software quickly, iteratively and with a feature set that hits that mark.  While Agile has different "flavors", Scrum is one process for implementing Agile.

So what is Agile?
According to Wikipedia, Agile software development is a conceptual framework for software engineering that promotes development iterations throughout the life-cycle of the project.  

Simply put, Agile allows your team to identify the most critical features of the software that can be completed within a short time frame (normally 1 to 2 months), and it delivers a complete build with this set of limited features as the first iteration.

Once that is done, you can move those features to production or continue on to the next iteration. 

By breaking the releases into shorter stints, it allows you to gain quicker releases and to capture return on investment more quickly by putting the working (but limited) features into production sooner. 

This is in stark contrast to the more traditional "Waterfall" approach, where you design all features upfront, code each one, test each one, then move into production. 

Agile projects are iteratively released to production months where Waterfall projects normally span a year or more before they are released to production.

So what is Scrum?
Scrum is process of implementing Agile, where features are delivered in 30 day sprints. 

Scrum borrows its name from Rugby,  where a sprint is the process of stopping play, then vigorously playing until the sprint ends and a new one begins. 

The same idea applies here, where you define the requirements for a 30 day sprint and work on them with vigor for 30 days without being sidetracked by other things or having things re-prioritized.  

A specific feature is not recognized as being completed until it is analyzed, designed, coded, tested, re-factored and documented. 

At the end of the 30 day sprint, most features defined in the 30-day sprint should be completed. 

If some did not get finished (because of being underestimated), the uncompleted features can be moved to a later sprint. 

A sprint is considered successful if all the completed features have high quality and can be put into production (or beta) upon ending the sprint.

Do Team Member Responsibilities Change?
Managing Scrum development requires a major change in how teams work together. 

In traditional Waterfall development, teams normally have

·         a project sponsor,

·         a project manager,

·         analysts,

·         designers,

·         programmers,

·         testers, and

·         documentation specialists. 

Each team member has specific duties which normally do not overlap and they have a specific reporting structure (most team members report to the project manager).

With Scrum, you have just 3 team roles and they are normally limited to 7 or less individuals (however, you can have multiple Scrum teams in sets of 7 or less):

• Product Owner - This is the person that identifies and prioritizes the features that will appear in a 30 day sprint.  This is normally the CEO, CTO, or some other high level stakeholder that ultimately is responsible for shaping the roadmap of their product.
• ScrumMaster - The ScrumMaster is akin to the Project Manager in Waterfall environments, but does not manage the team deliverables at a micro level.  Instead, this person is responsible for ensuring that the 30 day sprint stays on course, no new features are added to the sprint, code inspection, and ensuring everyone plays by the rules.
• The Team - With Waterfall, a team consists of analysts, designers, testers and documentation specialists.  With Scrum, each team member is empowered and expected to self-manage themselves and to participate in all duties needed to deliver a feature.  This includes analysis, design, coding, testing and documentation.

So how does Scrum Work on a Day-by-Day Basis?

Scrum begins with an 8 hour Scrum Kickoff Meeting. 

The Scrum Kickoff meeting is divided into (2) 4 hour segments, where you first determine what features are desired for the 30 day sprint. 

The last 4 hours are used to provide rough estimates for the items identified for the sprint. 

If the estimates exceed the available resources, the features are prioritized and less important features are dropped from the sprint. 

An important component of Scrum is using a time-box approach, where meetings and events have a definite time period (e.g. no more than 8 hours for the kickoff meeting) and this time-box is strictly enforced. 

Once the features are locked in for the 30-day sprint, no changes are allowed (new features can not be introduced until the next sprint). 

When estimating features for a sprint, the estimates must include time for analysis, design, coding, testing, re-factoring, and documentation. 

A feature is not considered complete until all those things are done.

Each day, a Daily Scrum Meeting is held to determine how the features are progressing.  The meeting is no longer than 15 minutes, and each team member is asked 3 questions:

• What have you accomplished since the last Daily Scrum Meeting?
• What will you do before the next Daily Scrum Meeting?
• Is there anything that is impeding your progress (and remedies are discussed)?

From a programmer's perspective, Scrum development is a new paradigm which is very empowering but does require them to follow specific rules:

• Code is only checked out for the duration needed to complete a feature.  No exceptions.  Most code will be checked in daily, as most features are broken down into small feature sets.
• Time must be entered daily.   For each feature, you will have estimated hours, actual hours and hours remaining to complete the feature.  This information must be updated at the end of every day so that the ScrumMaster can determine if the release progress is trending as required.
• Programmers are not allowed to be pulled off on tangent projects, they must stick to the features they have been assigned for the sprint.
• All team members must attend the Daily Scrum Meeting and must be on time.
• Code is compiled and deployed to a test server daily. Teams can use automated build tools to speed up this process.  Automated tests should be run against the daily releases to discover any issues introduced by the release.

Once a Scrum 30 day sprint is completed, all features that were completed can then be moved to a beta or production environment.  Following the sprint is a Retrospective (post mortem), where team members discuss and document things that went well and things that can be improved upon in the next sprint.

There are many other things that needs to be defined, formulated and practiced like

·         Team Composition - how teams work together

·         Understanding the SCRUM rules – no.of hours , estimates up in front, enter time daily, daily builds, no new requirements etc.,

·         Product Backlogs - set the goal for the sprint and prioritize product backlog items to determine which ones can fit within the sprint

·         Daily meetings

·         Reporting and Metrics

·         Retrospectives

·         Tailoring SCRUM to your project

More to follow

Read more...