Chapter 1

ABSTRACT

For numerous reasons, you may need to access system hardware information. For example, when you have created software and you want to put a lock on that software. One of the most efficient ways to do so is to get one of the IDs of a piece of hardware in the target machine and then plan your software so that it can just work with the computer that has the same ID. Since some hardware IDs (and not all of them) is unique, you have very simply created a lock! This project Advanced System Information explains how, from within a Microsoft Visual Studio 2008 application, you can retrieve information about the hardwares and other configuration which is embedded in the system. This information may include hardware information, data storage information, memory information, system information, network information, user accounts and security information. In Hardware information we can retrieve the trivia about hardware component embedded in the system like the Processor, Bus, and Sound device and so on. In Data storage information we can obtain the details about the Disk Drives, Logical Disk and so on. In Memory information we can retrieve the information regarding different types of memories like Cache memory, Physical memory and other memory details of the system. In System information we can acquire the details of the system about the Registry, System Drivers and so on. In Network information we retrieve the information regarding clients, network protocol and so on. And finally in User accounts and Security information we can retrieve the particulars about the System User, Account and so on. This software is very user friendly so that one can see the particulars of each and every hardware units without the help of control panel. This can be implemented by using the Microsoft Visual Studio 2008 in .NET framework 2.0 which is compatible with Windows XP and later versions by using the c# as front end.

Chapter 2
2. INTRODUCTION:
Sometimes you need some specific information about your Windows computer. Like when you're talking with someone in tech support. They ask you how much RAM you have, or what size hard drive, or what version of Windows and you just aren't sure. For those times, or in case you're just curious, there's a handy utility called Advanced System Information that will tell you all you need to know. Advanced System Information entails the management of the physical and other components of computers and computer networks, from acquisition through disposal. Common business practices include request and approval process, procurement management, life cycle management, redeployment and disposal management. A key component is capturing the financial information about the hardware life cycle which aids the organization in making business decisions based on meaningful and measurable financial objectives. Advanced System Information is designed with an aim to create user - friendly

environment which is used to make the information about the configuration of particular system by the code and implementation of the tools. So user can easily get the information about the system whenever need to check our configuration details.

2.1 OBJECTIVES:
Hardware is a general term for the physical artifacts of a technology. It may also mean the physical components of a computer system, in the form of computer hardware. Hardware historically meant the metal parts and fittings that were used to make wooden products stronger, more functional, longer lasting and easier to fabricate or assemble. Modern computers based on integrated circuits are millions to billions of times more capable than the early machines, and occupy a fraction of the space. Simple computers are small enough to fit into mobile devices, and can be powered by a small battery.

Personal computers in their various forms are icons of the Information Age and are what most people think of as "computers". However, the embedded computers found in many devices from MP3 players to fighter aircraft and from toys to industrial robots are the most numerous. A computer is a programmable machine that receives input, stores and automatically manipulates data, and provides output in a useful format. Mechanical examples of computers have existed through much of recorded human history. The main objective of this project Advanced System Information, is to retrieve the information of the hardware and other information which is embedded in the system within the fraction of seconds

2.2 EXISTING SYSTEM:

In the existing system, Since all the informations are computerized, if any enquires or doubts in any details regarding the hardware information we have to search it through the control panel or by any other way. It takes more time and more work load to finish our searching. In the existing system, if we want to retrieve the information of the entire hardware one at time which is embedded in the system is more complicated. For the non technical people it is difficult to search the information through the control panel or by using the coding. In the existing system, we have the hardware information alone but not all information such as memory, data storage, networking and so on as one system software.

2.3 PROPOSED SYSTEM:

In the proposed system, The proposed system needs less time to retrieve the hardware information from the system.

 The proposed system provides not only the hardware information alone but it provides detailed information regarding the system, memory, network, data storage and so on. Since the informations are computerized, if any enquires or doubts in any details we can easily go through it by using this system. The proposed system has the option to check all the information of a particular system by using this software. The proposed system is very user friendly so that anyone can use this software to review the details of the system.

Provides in-depth information of your computer hardware, storage, memory, network,

security, system.

2.4 SCOPE:
This document will be used throughout the subsequent development phases to ensure the successful development of the product. System Information the developer uses it, and it acts as the basis for validating the final delivered system. This document characterizes the software requirements (both the functional and non-functional) of the system agreed upon by the system, It may be referred in case of confusion or inconsistence, in terms of usability, the scope their easy visibility of the hardware informations. The document should be made available for reference on demand. In future, if any changes are to be made in the requirements specification, it must undergo a change approval process.

Chapter 3
3. PROFILE:
This chapter gives the detailed information about the hardware and software requirement used in this project.

3.1 HARDWARE SPECIFICATIONS:

Processor Main memory Cache memory Processing speed Hard disk drive Floppy disk drive Monitor

: : : : : : :

Dual-core 256MB RAM 512KB 600 MHz 40 GB 1.44 MB 14 SVGA Color

3.2 SOFTWARE SPECIFICATION:

Operating System Front End

: :

Windows XP Professional C#.net

3.3 SYSTEM DESCRIPTION:

THE .NET FRAMEWORK: The .NET Framework is a multi-language environment for building, deploying, and running XML Web services and applications. It consists of three main parts UNIFIED PROGRAMMING CLASSES The framework provides developers with a unified, object-oriented, hierarchical, and extensible set of class libraries (APIs). Currently, C++ developers use the Microsoft Foundation Classes and Java developers use the Windows Foundation Classes. The framework unifies these disparate models and gives Visual Basic and JScript programmers access to class libraries as well. By creating a common set of APIs across all programming languages, the common language runtime enables cross-language inheritance, error handling, and debugging. All programming languages, from JScript to C++, have similar access to the framework and developers are free to choose the language that they want to use. C#.NET: C# (pronounced "see sharp")is a multi-paradigm programming language encompassing imperative, declarative, functional, generic, object-oriented (class-based), and component-oriented programming discipline. It was developed by Microsoft within the .NET initiative and later approved as a standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270). C# is one of the programming languages designed for the Common Language Infrastructure. During the development of the .NET Framework, the class libraries were originally written using a managed code compiler system called Simple Managed C (SMC). In January 1999, Anders Hejlsberg formed a team to build a new language at the time called Cool, which stood for "C-like Object Oriented Language". Microsoft had considered keeping the name "Cool" as the final name of the language, but chose not to do so for trademark reasons. By the time the .NET project was publicly announced at the July

2000 Professional Developers Conference, the language had been renamed C#, and the class libraries and ASP.NET runtime had been ported to C#. C#'s principal designer and lead architect at Microsoft is Anders Hejlsberg, who was previously involved with the design of Turbo Pascal, Embarcadero Delphi (formerly CodeGear Delphi and Borland Delphi), and Visual J++. In interviews and technical papers he has stated that flaws in most major programming languages (e.g. C++, Java, Delphi, and Smalltalk) drove the fundamentals of the Common Language Runtime (CLR), which, in turn, drove the design of the C# language itself. James Gosling, who created the Java programming language in 1994, and Bill Joy, a co-founder of Sun Microsystems, the originator of Java, called C# an "imitation" of Java; Gosling further claimed that "[C# is] sort of Java with reliability, productivity and security deleted." Klaus Kreft and Angelika Langer (authors of a C++ streams book) stated in a blog post that "Java and C# are almost identical programming languages.

DESIGN GOALS: The ECMA standard lists these design goals for C#:

C# language is intended to be a simple, modern, general-purpose, object-oriented programming language.

The language, and implementations thereof, should provide support for software engineering principles such as strong type checking, array bounds checking, detection of attempts to use uninitialized variables, and automatic garbage collection. Software robustness, durability, and programmer productivity are important.

The language is intended for use in developing software components suitable for deployment in distributed environments.

Source code portability is very important, as is programmer portability, especially for those programmers already familiar with C and C++.

Support for internationalization is very important.

FEATURES: By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure (CLI). Most of its intrinsic types correspond to value-types implemented by the CLI framework. However, the language specification does not state the code generation requirements of the compiler: that is, it does not state that a C# compiler must target a Common Language Runtime, or generate Common Intermediate Language (CIL), or generate any other specific format. Theoretically, a C# compiler could generate machine code like traditional compilers of C++ or Fortran. Some notable distinguishing features of C# are:

There are no global variables or functions. All methods and members must be declared within classes. Static members of public classes can substitute for global variables and functions.

Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable shadowing is often considered confusing by C++ texts.

C# supports a strict Boolean datatype, bool. Statements that take conditions, such as while and if, require an expression of a type that implements the true operator, such as the boolean type. While C++ also has a boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to bool, allowing a to be an int, or a pointer.

C# disallows this "integer meaning true or false" approach on the grounds that forcing programmers to use expressions that return exactly bool can prevent certain types of common programming mistakes in C or C++ such as if (a = b) (use of assignment = instead of equality ==).

In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the welldefined null value; it is impossible to obtain a reference to a "dead" object (one which has been garbage collected), or to a random block of memory. An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack.

WINDOWS MANAGEMENT INSTRUMENTATION (WMI): Windows Management Instrumentation (WMI) is a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification. WMI is Microsoft's implementation of the Web-Based Enterprise Management (WBEM) and Common Information Model (CIM) standards from the Distributed Management Task Force (DMTF). WMI allows scripting languages like VBScript or Windows PowerShell to manage Microsoft Windows personal computers and servers, both locally and remotely. WMI is preinstalled in Windows 2000 and newer OSs. It is available as a download for Windows NT[1], Windows 95 and Windows 98.[2] PURPOSE OF WMI: The purpose of WMI is to define a non-proprietary set of environment-independent specifications which allow management information to be shared between management applications. WMI prescribes enterprise management standards and related technologies that work with existing management standards, such as Desktop Management Interface (DMI) and SNMP. WMI complements these other standards by providing a uniform model. This model represents the managed environment through which management data from any source can be accessed in a common way. FEATURES: 1. Automation interfaces: Because WMI comes with a set of automation interfaces ready to use, all management features supported by a WMI provider and its set of classes get the scripting support for free out-of-the box. Beyond the WMI class design and the provider development, the Microsoft development and test teams are not required to create, validate and test a scripting model as it is already available from WMI. 2. .NET Management interfaces: Because the System.Management namespace
[5]

relies on the

existing COM/DCOM plumbing, the created WMI provider and its set of WMI classes becomes automatically available to all .NET applications independently of the language used (e.g. C#, VB.NET). Beyond the WMI class design and the provider development, like for scripting, the Microsoft development and test teams are not required to create, validate and test new assemblies to support a new namespace in the .NET Framework as this support is already available from WMI for free.
9

3. C/C++ COM/DCOM programming interfaces: Like most components in Windows, COM/DCOM programmers can leverage the features of the provider they develop at the COM/DCOM interfaces level. Like in previous environments (scripting and .NET Framework), a COM/DCOM consumer just needs to interact with the standard set of WMI COM interfaces to leverage the WMI provider capabilities and its set of supported WMI classes. To make all management information available from the native APIs, the WMI provider developer just needs to interact with a set of pre-defined WMI COM interfaces. This will make the management information available at the WMI COM level automatically. Moreover, the scripting COM interface object model is very similar to the COM/DCOM interface object model, which makes it easy for developers to be familiar with the scripting experience. 4. Remoting capabilities over DCOM and SOAP: More than simply offering local COM capabilities, as management is all about remoting, WMI offers the DCOM transport. In addition, SOAP transport will be available in Windows Server 2003 R2 through the WS-Management initiative lead by Microsoft, Intel, Sun Microsystems and Dell. This initiative allows to run any scripts remotely or to consume WMI data through a specific set of interfaces handling SOAP requests/responses. The advantage for the WMI provider developer is that when he exposes all his features through WMI, Windows Remote Management/WS-Management can in turn consume that information as well (embedded objects in WMI instances are not supported in Windows Server 2003 R2. It is however a target for Vista). All the layering to WS-Management and the mapping of the CIM data model to SOAP comes for free out of the WMI/WS-Management solution. In the event DCOM must be used, implementing DCOM requires the presence of a proxy DLL deployed on each client machine. As WMI is available in the Windows operating system since Windows 2000, these issues are eliminated. 5. Support for Queries: WMI offers support for WQL queries out of the box. This means that if a provider is not designed to support queries, WMI supports it by using an enumeration technique out of the provider. LISTVIEW CONTROL IN ASP.NET 3.5: ListView is a new databound control that is shipped with ASP.Net 3.5. ListView control is similar to GridView, Repeater, and DataList which helps us to display a table of data with awesome additional features. We can use repeater control whenever we need to display the data in a custom
10

format, as opposed to only tabular view in GridView control. The Repeater control lacks in certain features like edit, update and paging. Using GridView control it is possible to Edit/Update/Delete data but with a big limitation on the layout of the data display. There is no single control available in earlier versions of asp.net that accommodates all the above features. The introduction of ASP.Net 3.5 answers this with the new ListView control. FEATURES OF LISTVIEW CONTROL:

Can define our own template/Layout/Structure for the data display. Edit/Update/Delete capabilities on the data displayed. Built-in support for inserting new row. Built-in support for sorting Supports databinding via DataSource Controls including LINQ DataSource controls. Paging via DataPager control, which can be part of ListView control or can be kept outside the

control. Means, DataPager can be kept at any part of page as opposed to GridView where the built-in paging is packed with the control itself.

11

Chapter 4
3.ANALYSIS
SYSTEM ANALYSIS: The first step in developing anything is to state the requirements. This applies just as much to leading edge research as to simple programs and to personal programs, as well as to large team efforts. Being vague about your objective only postpones decisions to a later stage where changes are much more costly. The problem statement should state what is to be done and not how it is to be done. It should be a statement of needs, not a proposal for a solution. A user manual for the desired system is a good problem statement. The requestor should indicate which features are mandatory and which are optional, to avoid overly constraining design decisions. The requestor should avoid describing system internals, as this restricts implementation flexibility. Performance specifications and protocols for interaction with external systems are legitimate requirements. Software engineering standards, such as modular construction, design for testability, and provision for future extensions, are also proper. Many problems statements, from individuals, companies, and government agencies, mixture requirements with design decisions. There may sometimes be a compelling reason to require a particular computer or language; there is rarely justification to specify the use of a particular algorithm. The analyst must separate the true requirements from design and implementation decisions disguised as requirements. The analyst should challenge such pseudo requirements, as they restrict flexibility. There may be politics or organizational reasons for the pseudo requirements, but at least the analyst should recognize that these externally imposed design decisions are not essential features of the problem domain. A problem statement may have more or less detail. A requirement for a conventional product, such as a payroll program or a billing system, may have considerable detail. A requirement for a research effort in a new area may lack many details, but presumably the research has some objective, which should be clearly stated. Most problem statements are ambiguous, incomplete, or even inconsistent. Some requirements are just plain wrong. Some requirements, although precisely stated, have unpleasant consequences on
12

the system behavior or impose unreasonable implementation costs. Some requirements seem reasonable at first but do not work out as well as the request or thought. The problem statement is just a starting point for understanding the problem, not an immutable document. The purpose of the subsequent analysis is to fully understand the problem and its implications. There is no reasons to expect that a problem statement prepared without a fully analysis will be correct. The analyst must work with the requestor to refine the requirements so they represent the requestors true intent. This involves challenging the requirements and probing for missing information. The psychological, organizational, and political considerations of doing this are beyond the scope of this book, except for the following piece of advice: If you do exactly what the customer asked for, but the result does not meet the customers real needs, you will probably be blamed anyway. FEASIBILITY STUDY: A feasibility study is a high-level capsule version of the entire System analysis and Design Process. The study begins by classifying the problem definition. Feasibility is to determine if its worth doing. Once an acceptance problem definition has been generated, the analyst develops a logical model of the system. A search for alternatives is analyzed carefully. There are 3 parts in feasibility study. Operational feasibility: Question that going to be asked are Will the system be used if it developed and implemented. If there was sufficient support for the project from the management and from the users. Have the users been involved in planning and development of the Project. Will the system produce poorer result in any respect or area? This system can be implemented in the organization because there is adequate support from management and users. Being developed in C# so that, the necessary operations are carried out automatically.

13

Technical feasibility: Does the necessary technology exist to do what is been suggested Does the proposed equipment have the technical capacity for using the new system? Are there technical guarantees of accuracy, reliability and security? The environment required in the development of system is any windows platform The observer pattern along with factory pattern will update the results eventually The language used in the development is c#.

Financial and economical feasibility: The system developed and installed will be good benefit to the organization. The system will be developed and operated in the existing hardware and software infrastructure. So there is no need of additional hardware and software for the system. MODULES: In this project we have six modules. They are: Hardware Data storage System Memory Network User Account and Security

MODULE DESCRIPTION: Module #1: Form Name : Get Hardware Information Objective Description : To display the hardware information :

14

In this module, the user has to select the hardware utility tab first, and then select any desire hardware components from the list box. In list box we have many computer hardware components such as processor, sound device, battery, serial port and so on. After selecting the hardware component, it automatically shows all the details regarding the hardware. For example, if we select the hardware component as processor then it show the details of the processor which is embedded in the system such as like its version, system name, role, processor id, system creation, manufacturer, Name and so on. Module #2: Form Name : Get Hardware Information Objective Description : To display the data storage information :

In this module, the user has to select the data storage utility tab first, and then select any desire derive or directory. In list box we have many data storage options such as logical disk, disk drive, and tape drive and so on. After selecting the derive or directory from the list box, it automatically shows all the details regarding the selected item. For example, if we select the data storage as disk drive then it shows the details of the disk drive which is in the system such as its device ID, size, and status and so on. Module #3: Form Name : Get Hardware Information Objective Description : To display the memory information :

In this module, the user has to select the memory utility tab first, and then select any desire memory key from the list box. In list box we have memory such as memory device, cache memory, physical memory and so on. After selecting the memory key, it automatically shows all the details regarding the memory.

15

For example, if we select the memory as cache memory then it show the details of the cache memory which is in the system such as block size, speed, and type and so on.

Module #4: Form Name : Get Hardware Information Objective Description : To display the system information :

In this module, the user has to select the system utility tab first, and then select any desire system information key from the list box. In list box we have many available key for system such as system device, system drive, system desktop and so on. After selecting the system component, it automatically shows all the details regarding the system key. For example, if we select the system key as system driver then it show the details of the system driver which is in the system such as Aavmker4, Abiosdsk, abp480n5 and so on.

Module #5: Form Name : Get Hardware Information Objective Description : To display the network information :

In this module, the user has to select the network utility tab first, and then select any desire networking key from the list box. In list box we have many networking components such as network client, network connections, network protocol and so on. After selecting the network component, it automatically shows all the details regarding the network key. For example, if we select the network key as network protocol then it show the details of the network protocol which is in the system such as MSAFD TCP/IP, MSAFD UDP/IP, RSVP UDP Service provider and so on.

Module #6:
16

Form Name : Get Hardware Information. Objective Description : To display the user Account and security information :

In this module, the user has to select the user account and security information utility tab first, and then select any desire key from the list box. In list box we have much information key regarding user account and security such as system user, user account, and log event and so on. After selecting the key from the list box, it automatically shows all the details regarding the user account and security. For example, if we select the user account and security key as system users then it show the details of the system users which are in the system such as group component and part component so on.

17

Chapter 5

5. IMPLEMENTATION
CODING STANDARDS: Coding is the process of converting the design specification into source code. C#.NET has been used to implement this project. Although the time spent in coding will be comparatively less when the total system development time is considered this phase cannot be underestimated. Insufficient effort in the coding phase will affect both the testing and maintenance phase heavily. Program should be written in easily readable and understandable way. Programs readability is very important in bug fixing and also maintenance. Hence the developer should adopt a standard to ensure readability and easy maintenance of ones programs. Throughout the coding phase these standards were strictly followed. NAMING CONVENTIONS: General Conventions: Variables: For readability, the variable names are composed of number of words. Hungarian notation is used in naming the controls. In-line comments are used to explain complicated code. Descriptive names are used for all variables, procedures and constants. Multiword identifiers are internally distinguished by capital letters. Enough spacing is used to separate the statements have been followed to increase readability The name of variable, functions or procedures have been abbreviated if they are too long.

18

Methods: The same conventions like that of variables have been followed for methods also. User-Defined Datatypes: User-defined data types such as classes are composed of number of words. They start with a lower case letter. Each following word in the name begins with an upper case. Comments: Documentation of program using comments is an important tool that helps to make the code more readable. God readability ensures maintainability of the code and hence reduces the total development cost. Comments should hence be used throughout the code. They should be meaningful and redundant. TESTING: Testing is a major consideration in software development and maintenance. It is a major quality control measure used during software development. It is basic functions to detect errors in the software. Testing accounts for the largest technical effort in the software development process. Testing begins at the module level and work towards the integration of the entire computer based systems. The goal of testing is to uncover requirement, design, and errors in the system consequently; different levels of testing are used. Testing and debugging are different activities that any testing strategy includes debugging strategy. Software testing must accommodate low level test that are necessary to verify that a small source code segment has been correctly implemented as well as high level that validate major system functions, against customer requirements. No testing is complete without the verification and validation. The goals of verification and validation activates are to access and improve the quality of work products generated during the development and modification of the software. Whenever a system is developed it is hoped that it perform properly. In practice, how ever, some error always occurs. The main purpose of testing an

19

Information system is to find the error and correct them. A successful test is one, which fine an error. The main objectives are: To ensure that during operation the system will perform as per specification. To make sure that the system meets user requirements during operation. To verify that the control incorporated in the system function as intended. To see that correct input are fed into the system and the operations are correct To make sure that during the operations incorrect input processing and output will be deleted.

System testing is a comprehensive valuation of the program, manual procedure and computer operated control. System testing is a process of checking if the developed system is working according to the original objectives and requirements. All tests need to be conducted in accordance to the test cases. This will ensure that the test coverage meets the requirements and the testing is done in systematic manner. Testing Methods: While testing the System by using the test data, errors were found and corrected. Thus a series of test was performed for the Proposed System before the System was ready for implementation. The various methods used for testing the System are: Unit Testing: Unit testing is used for testing the smallest unit at software design. It is a code (white box testing) level test and we have done functionality test also. An acceptance test is done to verify the validity and reliability of the system. Proper training for the users is critical for the successful performance of the system. A test report is maintained to study the performance range and accuracy of the system. A test report is maintained to study the performance range and accuracy of the system. Integration Testing Unit Testing System Testing

20

Integration Testing: The major concern of integration testing is developing and incremental strategy that will limit the complexity of the entire actions among components as they are added to the system, developing and implementation and integration schedules that will make the module available when needed, and designing test case that will demonstrate the viability of the evolving system. System Testing: The Objectives of System testing is to find defects that are attributable to the behavior of the System as a whole, rather than the behavior of individual components, and to test that the software functions as a Complete System. This Level of testing is different from integration testing in that the tests are concerned with the entire System, not just the interactions between components. Other than System functionality and behavior, System testing may include testing configuration, throughput, security, resource utilization and performance. The System testing was tested against the System Requirements to see if all the requirements are met and whether the System performs as specified by the requirements. The System testing was done after designing all the modules and forms in the System. In the unit testing error may occur due to incompatibility. Implementation: The final and the important phase in the System Life Cycle is the Implementation of New System. The term Implementation has different meaning, ranging from conversation of basic application to complete replace of a Computer System. The procedures are virtually the same. Implementation includes all those motives that take place to convert from old System to new System. The new System may totally replace existing manual or automated Systems or it may be major modification to an Existing System. The method of implementation and time are scaled to be adopted is found out initially. Next the System is tested properly and at the same time the users are trained in new procedure. Proper implementation is essentially to provide a reliable System to meet organizational using the new System, but it will prevent improper installation.

21

The implementation involves the following things: Careful planning Investigation of the System and Constraints Design the Methods to achieve the change over Training the staff in the phase Evaluation of the change over method

22

Chapter 6
RESULTS AND DISCUSSION

FORM DESIGN:

23

RESULTS:

24

25

26

27

28

29

30

31

32

33

34

35

CHAPTER 7
CONCLUSION
This system is flexible and any amendment can be made easily. This software is designed for the specific need of the organization and is found to work effectively and efficiently. The major advantage of the system is fastness, accurate information and reducing manpower and time involved. This tool is being implemented and is found to replace the existing manual system effectively. The tool is implemented in various systems and tested for inter-operate ability and scalability. This software is very user friendly so that one can see the particulars of each and every hardware units without the help of control panel.

FUTURE ENHANCEMENT
A system is said to be a good system, only when it is adaptable to changes. This system can be enhanced and any modifications can be done easily. In todays technology, system information and other information are major aspects of the everyday IT operations. Now a day, the dawn of computing system has been essential element of properly managed computing system. In future, this tool will be upgraded by adding features of the networking technologies, system components, security and so on which will be useful to retrieve the information very easily. This system can be enhanced to retrieve the information even the developers of the software, utility of the system and also the extended to retrieve the information of the software which is installed in the system.

36

BIBLIOGRAPHY
REFERENCE:

1. VISUAL STUDIO C#.NET -Vijay Mukhi, First Indian Edition 2001 2. VB.NET UNLEASHED -Stephen Walther, First Indian Edition 2002 3. THE COMPLETE REFERENCE VB.NET -Johan, Third Edition

4. http://www.codersource.net/microsoft-net.aspx

5. http://www.csharphelp.com/2006/12/c-tutorial-for-beginners/

6. http://www.microsoft.com

37