yasir - Technology News

Name: Syed Yasir

Bio: Syed Yasir Hashmi is a tech guru working in the industry for the last 12 years.

Posts by yasir:

What is Commercial off the Shelf (COTS)?

November 5th, 2012

1.0 Abstract

All desktop side and server side software are COTS as they come with wide range of features and options that they fit into all the demanding needs of versatile customers. COTS products are adopted by using built-in configuration mechanism that allow the functionality of the system to be tailored to specific customer needs.

2.0 Definitions

COTS:

“A commercial-off-the-shelf (COTS) product is a software system that can be adapted to the needs of different customers without changing the source code of the system.”

3.0 Introduction

Software reuse based on COTS has become increasingly common. The vast majority of new business information processing systems are now built using COTS rather than using an object-oriented approach. Although there are often problems with this approach to system development (Tracz, 2001), success stories (Baker, 2002; Balk and Kedia, 2000; Brownsword and Morris, 2003; Pfarr and Reis, 2002) show that COTS-based reuse reduces effort and the time to deploy the system.

There are two types of COTS product reuse, namely COTS-solution systems and COTS-integrated systems.

COTS-solution systems consist of a generic application from a single vendor that is configured to customer requirements.

COTS-integrated systems involve integrating two or more COTS systems.

COTS can be either software or hardware

Software:

Operating Systems (UNIX, Windows/NT, OS2)

Databases (Oracle, Sybase)

Graphics Packages (Motif, ??)

Hardware:

Busses (VME, PCI, cPCI)

Processors (Motorola, HP, Sun, Intel)

Disk Drives (Western Digital, Red Rock)

Peripherals (Printers, Monitors, Keyboards, etc.)

There are many areas where COTS successfully replaced traditional custom software examples are

– Space Shuttle (non-mission-critical systems)

– Missile Guidance systems

– Military ground based and shipboard sensors (radar, sonar)

– Industrial control and monitoring systems

– telecommunications

– Air traffic control

Benefits

This approach to software reuse has been very widely adopted by large companies over the last 15 or so years, as it offers significant benefits over customized software development:

1. As with other types of reuse, more rapid deployment of a reliable system may be possible.

2. It is possible to see what functionality is provided by the applications and so it is easier to judge whether or not they are likely to be suitable. Other companies may already use the applications so experience of the systems is available.

3. Some development risks are avoided by using existing software. However, this approach has its own risks, as I discuss below.

4. Businesses can focus on their core activity without having to devote a lot of resources to IT systems development.

5. As operating platforms evolve, technology updates may be simplified as these are the responsibility of the COTS product vendor rather than the customer.

Problems

Of course, this approach to software engineering has its own problems:

1. Requirements usually have to be adapted to reflect the functionality and mode of operation of the COTS product. This can lead to disruptive changes to existing business processes.

2. The COTS product may be based on assumptions that are practically impossible to change. The customer must therefore adapt their business to reflect these assumptions.

3. Choosing the right COTS system for an enterprise can be a difficult process, especially as many COTS products are not well documented. Making the wrong choice could be disastrous as it may be impossible to make the new system work as required.

4. There may be a lack of local expertise to support systems development.

Consequently, the customer has to rely on the vendor and external consultants for development advice. This advice may be biased and geared to selling products and services, rather than meeting the real needs of the customer.

5. The COTS product vendor controls system support and evolution. They may go out of business, be taken over, or may make change that cause difficulties for customers.

3.1 History

In 1994, then Secretary of Defense William Perry well recognized the potential for commercial products in the Directorate of Defense and authored what has come to be known as the “Perry Memo.” Entitled Acquisition Reform – Mandate for Change, Perry asserted that business policies that once made sense were no longer applicable to current technologies. Commercial-off-the-shelf, or COTS would become an integral part of DoD procurement.

With a COTS item – already built – the government cannot monitor the build process, nor should it. For example, Dell computer hardware is widely used in the DoD. Think of what a waste of time, money, and really how downright silly it would be for DoD program managers to monitor operations at a Dell facility. And so, milspecs cannot apply; they simply do not make sense (Carter & Perry, 1999). Rather, the government puts forth performance-based requirements, and then the program manager finds a COTS product that meets those needs.

4.0 References

1- Software Engineering 9^th Edition by Sommervillie Page 440-445

2- http://www.ippa.ws/IPPC2/PROCEEDINGS/Article_5_Baron.pdf

Related Technology News:

No Comments "

Alternate mark inversion (AMI)

November 2nd, 2012

Alternate mark inversion (AMI)

Alternate mark inversion (AMI) is a digital transmission technique in which binary values are sent by three voltage states.

’0′ bits by a voltage of 0 volts.
’1′ bits by a voltage of +V volts or -V volts alternatively

In AMI, zeros are represented by 01 during each bit cell

Ones are represented by 11 or 00, alternately, during each bit cell

A logical “0″ is represented by 0 volts; A logical 0 is represented by no symbol

A logical 1 by pulses of alternating polarity.

The alternating coding prevents the build-up of a D.C. voltage level down the cable.
A logical “1″ is represented by either a positive voltage or a negative voltage so that each alternate “1″ is represented by a voltage level that is the opposite of that which represented the previous “1″.

The result is a digital waveform that has zero DC voltage on the line.

AMI (Alternate Mark Inversion) is a synchronous clock encoding technique which uses bipolar pulses to represent logical 1 value.

AMI Data Encoding

Line-code type used on T1 and E1 circuits.
AMI requires that the sending device maintain ones density. Ones density is not maintained independent of the data stream. Sometimes called binary coded alternate mark inversion
Typically implemented as a RZ code
Little or no DC content in signal
Lacks transparency particularly during long sequences of binary ‘0’

Related Technology News:

No Comments "

Encoding Schemes

November 2nd, 2012

Encoding Schemes

Code Name : NRZ-L

Binary Code : 11001011

Code Definition:

Non-Return-to-Zero Level

“One” is represented by one level
“Zero” is represented by another level lower the one but not zero.

Code Name : NRZ-I

Binary Code : 11001011

Code Definition:

Non-Return-to-Zero Inverse

“One” is represented by no change in level
“Zero” is represented by change in level.

Signal

Code Name : RZ

Binary Code : 11001011

Code Definition:

Return-to-Zero

“One” is represented by positive to zero
“Zero” is represented by negative to zero

Code Name : Manchester

Binary Code : 11001011

Code Definition:

Manchester encoding uses an inversion at the middle of each bit interval for both synchronization and bit representation.

A negative to positive transition represent binary 1 and a positive to negative transition represent binary 0.

The rising edge in the centre of the data bit indicates either a logic ’1′ or alternatively a logic ’0′.

Code Name : AMI

Binary Code : 11001011

Code Definition:

Alternate mark inversion (AMI) is a digital transmission technique in which binary values are sent by three voltage states.

’0′ bits by a voltage of 0 volts.
’1′ bits by a voltage of +V volts or -V volts alternatively

Code Name : Differential Manchester

Binary Code : 11001011

Code Definition:

A 1 bit is indicated by the absence of a transition at the start of the interval.
A 0 bit is indicated by the presence of a transition.
No transition during the interval indicates no signals are present.

Related Technology News:

No Comments "

Differential Manchester encoding

November 2nd, 2012

Differential Manchester encoding:

Encoding in which

(a) data and clock signals are combined to form a single self-synchronizing data stream,

(b) one of the two bits, i.e., “0″ or “1″, is represented by no transition at the beginning of a pulse period and a transition in either direction at the midpoint of a pulse period, and

(c) The other is represented by a transition at the beginning of a pulse period and a transition at the midpoint of the pulse period.

In differential Manchester encoding, if a “1″ is represented by one transition, a “0″ is represented by two transitions, and vice versa.

In differential Manchester encoding, the transition at the middle of the bit is used only for synchronization. The bit representation is defined by the inversion or no inversion at the beginning of the bit.

Mid-bit transition is ONLY for clocking.
1 = absence of transition at the beginning of the bit interval
0 = presence of transition at the beginning of the bit interval
Differential Manchester is both differential and bi-phase.
The coding is the opposite convention from NRZI.

Used in 802.5 (token ring) with twisted pair.

Related Technology News:

No Comments "

What is Cyclic Redundancy Check (CRC)

November 2nd, 2012

CRC has been an integral part of the computer industry for quite some time. The actual implementation of CRC is quite simple, especially from within 4th Dimension. However, the concept behind CRC is less straightforward.

What is CRC?

A CRC performs a mathematical calculation on a block of data and returns a number that represents the content and organization of that data. The idea is to have the CRC return a number that uniquely identifies the data. We can think of CRC as being the operation that generates a “fingerprint” for a block of data. The actual number, or fingerprint, that is used to identify the data is called a checksum. The following picture, shows the flow of a CRC.

By comparing the checksum of a block of data to another block of data’s checksum, we can determine if the data is an exact match or not. CRCs are mostly performed when transferring files from one location to another. Depending on the medium by which files are transferred, errors to data may occur during the transmission. In mission critical applications, it may be especially important to know that files are valid and reliable. Most networking protocols use CRCs to verify data received is the same as the data that was sent.

Verifying transmitted information, sending and receiving records, modifying files and records, and verifying emails between 4D databases, are a few of the reasons for which a 4D Developer would want to use CRC. Knowing how a CRC is implemented will also pave the way to understanding how to incorporate encryption into our databases.

Polynomials

CRC arithmetic is referred to in the mathematical world as “polynomial arithmetic module two”. CRC arithmetic addresses basic mathematical operations on binary numbers. CRC arithmetic does not have any carry or borrow operations, which makes calculations on large amount of data very efficient. Fortunately, adding, subtracting, multiplying, and dividing binary numbers is very straightforward.

Addition and subtraction in CRC arithmetic are identical. The bitwise operator XOR is equivalent to adding or subtracting. We know how to XOR values, which means you know how to add and subtract in CRC arithmetic. The following example is nothing more than two binary numbers being XORed.

Multiplication in CRC arithmetic is straightforward as well. The steps for CRC multiplication are the same as in regular long multiplication, with two specific rules: calculations are OR (not XOR) and there are no carries. We will not be using multiplication in CRCs, however, here is an example.

CRC division is more difficult to grasp because you must know when one binary number goes into another. A number is only as significant as the position of the leftmost 1 bit. For example, 0110 is less than 1001. The following example is actually a simple representation of a CRC. The remainder would be the actual checksum for the data.

Role of Divisor

we can choose a divisor that is to be used in the CRC calculation. The divisor in a CRC calculation is called the polynomial, or poly. In the case of CRCs, the poly is nothing more than a binary number. It gets its name because the number represents a polynomial with binary coefficients. For example:

1*(x⁷)+0*(x⁶)+0*(x⁵)+1*(x⁴)+1*(x³)+0*(x²)+1*(x¹)+1*(x⁰) = 10011011

Polys come in various sizes. The more popular polys use 16 or 32 bit lengths. The length of a poly is determined by the position of the leftmost 1 bit.

There are many popular polys in use, or you can create your own. However, some polys are better at identifying errors or differences in data than others. With this in mind, it’s a good idea to use one of the more time-tested polys than one you create.

Role of Remainder

Our CRC word is simply the remainder, i.e., the result of the last 6-bit exclusive OR operation. Of course, the leading bit of this result is always 0, so we really only need the last five bits. This is why a 6-bit key word leads to a 5-bit CRC. In this case, the

CRC word for this message string is 00010, so when I transmit the message word M I will also send this corresponding CRC word.When you receive them you can repeat the above calculation on M with our agreed generator polynomial k and verify that the resulting remainder agrees with the CRC word

A popular 32 bit polynomial is (0x04C11DB7), which is used in PKZip, Ethernet and FDDI. By searching on the Internet, you can find more polys that you can use in your CRCs.

CRC16

Example:

Initial CRC value:	1111 1111 1111 1111
Byte to process:	0101 1010

The Most used CRC polynomials

The 16-bit polynomial is known as the "X25 standard", and the 32-bit polynomial is the "Ethernet standard", and both are widely used in all sorts of applications.  (Another common 16-bit key polynomial familiar to many modem operators is 11000000000000101, which is the basis of the "CRC-16" protocol.)  These polynomials

are certainly not unique in being suitable for CRC calculations, but it's probably a good idea to use one of the established standards, to take advantage of all the experience accumulated over many years of use.

Following is a list of the most used CRC polynomials

CRC-12: X^12+X^11+X^3+X^2+X+1
CRC-16: X^16+X^15+X^2+1
CRC-CCITT: X^16+X^12+X^5+1
CRC-32: X^32+X^26+X^23+X^22+X^16+X^12+X^11+X^10+X^8+X^7+X^5+X^4+X^2+X+1

The CRC-12 is used for transmission of streams of 6-bit characters and generates 12-bit FCS. Both CRC-16 and CCRC-CCITT are used for 8 bit transmission streams and both result in 16 bit FCS. The last two are widely used in the USA and Europe respectively and give adequate protection for most applications. Applications that need extra protection can make use of the CRC-32 which generates 32 bit FCS. The CRC-32 is used by the local network standards committee (IEEE-802) and in some DOD applications.

32-bit CRC

The ITU-TSS has defined a 32-bit CRC too. Its formula is: G(x)=x²⁶+x²³+x²²+x¹⁶+x¹²+x¹¹+x¹⁰+x⁸+x⁷+x⁵+x⁴+x²+x¹+1=0

Related Technology News:

No Comments "

Component Based Software Engineering (CBSE)

October 30th, 2012

1.0 Abstract

A component is an independent software unit that can be composed with other components to create a software system. The process of implementing such independent components into the system is called CBSE. Components should be documented, independent, deploy able, compos able and compact able.

2.1 Definitions

CBSE:

“CBSE is the process of defining, implementing, and integrating or composing loosely coupled, independent components into systems”.

Component:

“A software element that conforms to a standard component model and can be independently deployed and composed without modification according to a composition standard.”

Models:

“A component model is a definition of standards for component implementation, documentation and deployment”.

Examples of component models are: EJB model (Enterprise Java Beans), COM+ model (.NET model), Corba Component Model. The component model specifies how interfaces should be defined and the elements that should be included in an interface definition

3.0 Introduction

An individual software component is a software package, a Web service, or a module that encapsulates a set of related functions (or data).

All system processes are placed into separate components so that all of the data and functions inside each component are semantically related (just as with the contents of classes). Because of this principle, it is often said that components are modular and cohesive.

With regard to system-wide co-ordination, components communicate with each other via interfaces. When a component offers services to the rest of the system, it adopts a provided interface that specifies the services that other components can utilize, and how they can do so. This interface can be seen as a signature of the component – the client does not need to know about the inner workings of the component (implementation) in order to make use of it. This principle results in components referred to as encapsulated. The UML illustrations within this article represent provided interfaces by a lollipop-symbol attached to the outer edge of the component.

Customers are demanding more dependable software that is delivered and deployed more quickly. The only way that we can cope with complexity and deliver better software more quickly is to reuse rather than re-implement software components.

Essentials of component-based software engineering

1. Independent components that are completely specified by their interfaces. There should be a clear separation between the component interface and its implementation.

This means that one implementation of a component can be replaced by another, without changing other parts of the system.

2. Component standards that facilitate the integration of components. These standards are embodied in a component model. They define, at the very minimum, how component interfaces should be specified and how components communicate.

Some models go much further and define interfaces that should be implemented by all conformant components. If components conform to standards, then their operation is independent of their programming language. Components written in different languages can be integrated into the same system.

3. Middleware that provides software support for component integration. To make independent, distributed components work together, you need middleware support that handles component communications. Middleware for component support handles low-level issues efficiently and allows you to focus on application-related problems. In addition, middleware for component support may provide support for resource allocation, transaction management, security, and concurrency.

4. A development process that is geared to component-based software engineering.

You need a development process that allows requirements to evolve, depending on the functionality of available components.

Design Principles for CBSE

Underlying CBSE are sound design principles that support the construction of understandable and maintainable software:

1. Components are independent so they do not interfere with each other’s operation.

Implementation details are hidden. The component’s implementation can be changed without affecting the rest of the system.

2. Components communicate through well-defined interfaces. If these interfaces are maintained, one component can be replaced by another, which provides additional or enhanced functionality.

3. Component infrastructures offer a range of standard services that can be used in application systems. This reduces the amount of new code that has to be developed.

Characteristics of Component

Standardized

Component standardization means that a component used in a CBSE process has to conform to a standard component model. This model may define component interfaces, component metadata, documentation, composition, and deployment.

Independent

A component should be independent—it should be possible to compose and deploy it without having to use other specific components. In situations where the component needs externally provided services, these should be explicitly set out in a ‘requires’ interface specification.

Composable

For a component to be composable, all external interactions must take place through publicly defined interfaces. In addition, it must provide external access to information about itself, such as its methods and attributes.

Deployable

To be deployable, a component has to be self-contained. It must be able to operate as a stand- alone entity on a component platform that provides an implementation of the component model. This usually means that the component is binary and does not have to be compiled before it is deployed. If a component is implemented as a service, it does not have to be deployed by a user of a component. Rather, it is deployed by the service provider.

Documented

Components have to be fully documented so that potential users can decide whether or not the components meet their needs. The syntax and, ideally, the semantics of all component interfaces should be specified.

3.1 History

The idea that software should be componentized – built from prefabricated components – first became prominent with Douglas McIlroy’s address at the NATO conference on software engineering in Garmisch, Germany, 1968, titled Mass Produced Software Components. The conference set out to counter the so-called software crisis. McIlroy’s subsequent inclusion of pipes and filters into the Unix operating system was the first implementation of an infrastructure for this idea.

Brad Cox of Stepstone largely defined the modern concept of a software component. He called them Software ICs and set out to create an infrastructure and market for these components by inventing the Objective-C programming language. (He summarizes this view in his book Object-Oriented Programming – An Evolutionary Approach 1986.)

IBM led the path with their System Object Model (SOM) in the early 1990s. As a reaction, Microsoft paved the way for actual deployment of component software with OLE and COM. As of 2010 many successful software component models exist.

3.2 Difference to consider

Many people consider Component based as object oriented model but as a matter of fact Component based creation was motivated by designers’ frustration that object-oriented development had not led to extensive reuse, as had been originally suggested.

Single object classes were too detailed and specific, and often had to be bound with an application at compile time. You had to have detailed knowledge of the classes to use them, and this usually meant that you had to have the component source code. This meant that selling or distributing objects as individual reusable components was practically impossible.

Components are higher-level abstractions than objects and are defined by their interfaces. They are usually larger than individual objects and all implementation details are hidden from other components.

4.0 References

1- Software Engineering 9^th Edition by Sommervillie Page 453-468

2- Software Engineering a practitioner approach 5^th Edition By Roger Pressman Page 749-771

3- http://en.wikipedia.org/wiki/Component-based_software_engineering

4- http://www.iist.unu.edu/www/docs/techreports/reports_old/report330.pdf

Related Technology News:

No Comments "

Computer Aided Software Engineering – CASE

October 18th, 2012

1.0 Abstract

CASE provides software process support by automating some process activities and by providing information about the software that is being developed. The main purpose of case tools is to decrease the cost / development time and increase quality of software. As these tools are not free their use is limited.

2.1 Definition

CASE:

Computer Aided Software Engineering (CASE) is the scientific application of set of tools and methods to a software system which is meant to result in high quality, defect free and maintainable software products.

Tools:

Computer-Aided software engineering (CASE) tools are a set of programs and aids that assist analysts, software engineers, and programmers during all phases of the system development life cycle

3.0 Introduction

Computer Aided Software Engineering is the name given to software used to support software process activities such as requirement engineering, design, program development and test. CASE tools therefore include design editors, data dictionaries, compilers, debuggers, system building tools and so on.

CASE tools can be divided into two main groups – those that deal with the first three parts of the system development life cycle (preliminary investigation, analysis, and design) are referred to as Front-End CASE tools or Upper CASE tools, and those that deal mainly with the Implementation and Installation are referred to as Back-End CASE tools or Lower CASE tools.

The major reason for the development of CASE tools was to increase the speed of the development of systems. By doing so, companies were able to develop systems without facing the problem of having business needs change before the system could be finished being developed. Quicker installation also allowed the companies to compete more effectively using its newly developed system that matched its current business needs.
In a highly competitive market, staying on the leading edge can make the difference between success and failure.
CASE tools also allowed analysts to allocate more time to the analysis and design stages of development and less time coding and testing. Previous methods saw only 35% of the time being spent of analysis and design and 65% of the time being used to develop code and testing. CASE tools allowed analysts to use as much as 85% of the time in the analysis and design stages of the development. This resulted in systems that more closely mirrored the requirement from the users and allowed for more efficient and effective systems to be developed.
By using a set of CASE tools, information generated from one tool can be passed to other tools which, in turn, will use the information to complete its task, and then pass the new information back to the system to be used by other tools. This allows for important information to be passed very efficiently and effectively between many planning tools with practically no resistance. When using the old methods, incorrect information could very easily be passed between designers or could simply be lost in the shuffle of papers.

3.1 History

Initially Dr. Hassan Sayani floated the idea of automated system development which later supported by Daniel Tiechroew, who developed tools like PSL/PSA. This tool provided the power of meta-meta model.

The term CASE was originally coined by software company Nastec Corporation of Southfield, Michigan in 1982 with their original integrated graphics and text editor GraphiText, which also was the first microcomputer-based system to use hyperlinks to cross-reference text strings in documents—an early forerunner of today’s web page link. GraphiText’s successor product, DesignAid, was the first microprocessor-based tool to logically and semantically evaluate software and system design diagrams and build a data dictionary.

CASE tools were at their peak during 90’s while IBM was the market leader but after the death of IBM’s mainframe these CASE tools also ended or purchased by Computer Associates.

In 90’s CASE tools that could be used in the entire life cycle of the software development paradigm were also introduced. These included project management tools and cost calculators that made it possible to predict the resources and time scheduled of software in development. This was introduced to address some of the issues that had earlier resulted in the software crisis.

Some of the CASE tools built during this period include powerful tools such as Microsoft Project, Visual Basic and Perceps.

Some of the CASE tools that have been recently developed have been improved versions of the late 90s programs such as, Macromedia Studio MX, Microsoft Visual Studio.NET and Project Server 2003.

3.2 Classification

CASE classification helps us understand the types of CASE tools and their roles. There are three prospective where we can differentiate these tools

1- Functional Prospective

Tools are classified according their specific function

2- Process Prospective

Tools are classified as per process activities they support

3- Integration Prospective

Tools are classified as according to how they are organized into integrated units that provide support for one or more process activities.

3.3 CASE Tools

Tools can be divided into many categories. From planning prospective to reengineering, from version control to documentation you will find CASE tools. So it is out of my scope to discuss each type here. Allow me to list tools that I would like to suggest:

ERWIN by logic Works
Excelerator II by Intersolv
MS Visio
UML Tutor
MetaMill
Visual Paradigm for UML

Tool selection is totally dependent on your requirement and environment you are working on.

4.0 Future Developments

The future of CASE tools depends upon how they react to current developmental needs. Efforts are underway to reduce code from 40-70% and also inclusion of voice for documentation purposes.

Related Technology News:

1 Comment "

Samsung Pays Apple $1 Billion Sending 30 Trucks Full of 5 Cents Coins

October 7th, 2012

Rumors have it that this morning more than 30 trucks filled with 5-cent coins arrived at Apple’s headquarters in California. Initially, the security company that protects the facility said the trucks were in the wrong place, but minutes later, Tim Cook (Apple CEO) received a call from Samsung CEO explaining that they will pay $1 billion dollars for the fine recently ruled against the South Korean company in this way.

the funny part is that the signed document does not specify a single payment method, so Samsung is entitled to send the creators of the iPhone their billion dollars in the way they deem best.

Lee Kun-Hee

This dirty but genius geek troll play is a new headache to Apple executives as they will need to put in long hours counting all that money, to check if it is all there and to try to deposit it crossing fingers to hope a bank will accept all the coins.

Lee Kun-hee, Chairman of Samsung Electronics, told the media that his company is not going to be intimidated by a group of “geeks with style” and that if they want to play dirty, they also know how to do it.

You can use your coins to buy refreshments at the little machine for life or melt the coins to make computers, that’s not my problem, I already paid them and fulfilled the law.

A total of 20 billion coins, delivery hope to finish this week.

Let’s see how Apple will respond to this.

Related Technology News:

1 Comment "

How to delete services in Windows

June 10th, 2012

There is a common problem faced by many professionals while installing software like oracle database, when there is a need to delete a service Windows does not provide an easy way. But here we will discuss a command which will delete the service.

We can use SC.exe to delete the un wanted services. We can create and delete services through this command.

To delete a service:

Click on START then click on RUN and then enter CMD to open Microsoft Command Console.

Enter command:

Here “yourservername” is name of your computer.

“Servicename” is the service which you want to delete.

sc yourservername delete servicename

For instance, sc \\yasir-comp delete myservice

Below is the Microsoft help of all SC functions:

DESCRIPTION:
SC is a command line program used for communicating with the
NT Service Controller and services.
USAGE:
sc [command] [service name] …

The option has the form “\\ServerName”
Further help on commands can be obtained by typing: “sc [command]”
Commands:
query———–Queries the status for a service, or
enumerates the status for types of services.
queryex———Queries the extended status for a service, or
enumerates the status for types of services.
start———–Starts a service.
pause———–Sends a PAUSE control request to a service.
interrogate—–Sends an INTERROGATE control request to a service.
continue——–Sends a CONTINUE control request to a service.
stop————Sends a STOP request to a service.
config———-Changes the configuration of a service (persistant).
description—–Changes the description of a service.
failure———Changes the actions taken by a service upon failure.
qc————–Queries the configuration information for a service.
qdescription—-Queries the description for a service.
qfailure——–Queries the actions taken by a service upon failure.
delete———-Deletes a service (from the registry).
create———-Creates a service. (adds it to the registry).
control———Sends a control to a service.
sdshow———-Displays a service’s security descriptor.
sdset———–Sets a service’s security descriptor.
GetDisplayName–Gets the DisplayName for a service.
GetKeyName——Gets the ServiceKeyName for a service.
EnumDepend——Enumerates Service Dependencies.

Hope this will resolve your problem regarding deleting services in windows environment.

Related Technology News:

2 Comments "

Useful Google Search Commands

May 17th, 2012

Google is a sea of knowledge and to find the required result sometime things didn’t went as per our needs. So there are few Google useful Search Commands which can prove very useful for getting the required Fish out of Google

1. Site:

The Google site command will show you all the URL’s within the domain you specify. This allows you to see all of the pages that Google has indexed within your site. Not only will this command show you the exact URL’s that are indexed but it will also give you the total number of pages that are indexed by Google. Just type in the Google search, site:yourdomain.com to get this information.

2. Related:

This is probably one of my favorite Google commands for link building purposes. If you type in related:yourdomain.com, the search results will show you a wide range of related websites that contain the same keywords as your site. This is helpful when it’s time to find relevant websites for link building.

3. cache:

The cache:yourdomain.com will show you all of the URL’s from your site that Google currently has in it’s cache from the last time it crawled and indexed your site.

4. Allintitle:

The allintitle command, allintitle:wood working will show you all of the URL’s that contain both of those keywords in the title of a web page.

5. AllinURL:

The command, allinURL:wood working is similar to the allintitle command except that it looks for and will show you results of that keyword in a domain only.

6. Link:

The link command is one of the more popular and useful commands. If you search for link:petfood.com, Google will show you a good majority of the webpages that have links pointing to the specified domain.

7. Info:

The info command will show you information about a particular domain. The information such as Google cache, webpages that are similar, webpages that link to your domain, webpages that you link to and webpages that actually contain your domain name listed. So this is almost a one-stop-shop for a few of the most useful Google commands.

8. Define:

Another cool command for link building – if you’re looking for related websites for a particular keyword, you can type in quotation marks around your keyword like this: “The Cooking Wiki”, and a list of websites will show that contain that exact keyword.

9. 1+1

You can use Google as calculator to quickly get the result just write your mathematical question like 5+6788/887*99098 and boom you will get your result in no time.

10- Conversion:

Google is also very useful tool for unit conversion. You can convert Miles in Kilometers, Fahrenheit to Celsius etc. For example type in search bar “90 kilometers in miles” and you will get your result.

Hope these commands will improve your search experience with Google

Related Technology News:

No Comments "

Technology News as it Happens.

Posts by yasir:

What is Commercial off the Shelf (COTS)?

Alternate mark inversion (AMI)

Encoding Schemes

Differential Manchester encoding

What is Cyclic Redundancy Check (CRC)

32-bit CRC

Component Based Software Engineering (CBSE)

Computer Aided Software Engineering – CASE

Samsung Pays Apple $1 Billion Sending 30 Trucks Full of 5 Cents Coins

How to delete services in Windows

Useful Google Search Commands

News Just In

Daily Technology Quote

About Author