Thursday, February 22, 2007

My Experience with Virtual Operating System Software

    NOTE: This topic I am considering as an opening for those who doesn’t know about Virtualization Softwares.

   In fact my relation with VMware and other Virtualization Softwares started long back, around 3-5 years back. In my early days of studies me and some of my friends shared amounts to subscribe for Computer Related Magazines like Digit and PC Quest. From one of them I got the information about the Virtualization Softwares and later I found a demo version of the software.

  At that time I was a regular user of Virtual CD software which simulates a CD/DVD Rom. When I installed and checked the VMware software for the first time I was actually shocked to see that the whole Computer is made to a virtual One. Everything from Bios, Hard Drive, CD/DVD etc were put up from scratch. If one wants to use a virtual Operating System we should start from scratch just like purchasing and installing a physical computer. Create a new PC, and then create a Hard Disk, create required Memory, create Soundcard, Ethernet Card, create Partitions, and install Operating Systems and so on. But all these things which are created will be virtual only.

VMware® Showing it’s Settings and Hardware Configurations.

   The complete Hard Disk including all its partitions and disk space allocated in Virtual OS will be a single file or Folder in our Physical Hard Disk Partition. Even it is not required to allocate actual disk space in the physical Hard Disk. Memory is taken from the original RAM. System devices like soundcard are mapped from original Host PC. Some devices like Ethernet Cards are completely virtual and it creates Virtual Device Drivers in Host Operating System for that. Even a complete Virtual BIOS is there for this virtual operating System.

VMware® Showing its Bios Configuration – Note that this Bios is completely virtual and no hardware associates with it.

  When considering from the networking point of view, we can see the virtual systems just like any physical PC from the network. I remember one incident that occurred during our College days where our Lab Administrator came and asked for Laptop that is bought into College LAB without permission.

Apart from these initial enjoyments with the help of technology later I found the Virtual PCs are useful for many purposes like understanding networking and checking out demo versions because if we use our original Operating System for installing a demo or beta versions we will be messing up our Operating System itself. The greatest benefit I got with VMware is the ability of installing Server and going through many of the network management features like Domain Administration and Windows Server Management. This I cannot even think about without Virtualization software since we need multiple PCs for that. Also Advanced features like physical rollback of complete data is available with Virtual PCs. This helps us to bring back our virtual Operating Systems into an old stage completely even without a trace of old files or registry. It in fact rollbacks the whole virtual Hard Drive into an old point.

VMware® showing its booting up of Windows XP® Virtual Operating System.

Two major companies that have their virtualization products in market are VMware® ( and Microsoft®. (Virtual PC 2007).

Tuesday, February 6, 2007

Installing Windows Vista SDK - Hand Book

Windows Vista or .Net 3.0 development is one of the upcoming promises from Microsoft. It is still in beta stage and expected to be released on first quarter of 2007. We are working upon the VISTA SDK since last February.
In my office I found many of the team members are facing problems in installing the windows Vista SDK (.Net 3.0 SDK). What I usually does is to go into their systems and help them out to find the related sites and solve the problems. when I asked them to look into documentation for installation instructions it seems to be much complicated....especially for freshers.
I think there may be a lot of persons who are looking for a hand book where they can easily find most of the details related to installation of SDK. Those who are in need can look down for details regarding installation of SDK.


System Requirements:

Supported Operating Systems:

Windows Server 2003; Windows Server 2003 R2 Standard Edition (32-bit x86); Windows Server 2003 R2 x64 editions; Windows Server 2003 Service Pack 1; Windows Server 2003 x64 editions; Windows Vista; Windows XP Service Pack 2.

Hard disk space. Disk drive with a minimum of 2.0 GB of free space.

Knowledge in Topics:

Knowledge in .Net framework 2.0.
Knowledge in Windows Applications (for understanding WPF section)
Knowledge of Generics in .Net 2.0.

Windows Vista SDK RTM.

Web Setup: You require iInternet connection for every installation:

Offline Installer: This you can install in disconnected mode. This may be useful if you have to install in multiple machines or low Internet speed or offline install.


If you want to download the windows SDK your windows registration must be a valid one. Microsoft will check it out windows registration validity with Windows Genuine Validation Tool before proceeding to installation page.

The .NET Framework 3.0 tools and samples contained in this SDK are designed to work on Windows Vista or on Windows XP SP2 and Windows Server 2003 SP1 with the .NET Framework 3.0 Runtime Components installed. If you do not have the .NET Framework 3.0 components installed, some samples, tools, and other SDK functionality will not work properly on the down-level operating systems.

.Net Framework 3.0 Beta

Web Setup: You require Internet connection for every installation:

Offline Setup: This you can install in disconnected mode. This may be useful if you have to install in multiple machines or low Internet speed or offline install.

32 Bit:
64 Bit:

Windows Workflow Foundation Extensions for Visual Studio(You require this to be installed to enable VS 2005 IDE with Workflow foundation features)

Windows Communication Foundation and Windows Presentation Foundation Extensions for VS 2005:(You require this to be installed to enable VS 2005 IDE features)

XMLNotePad - a tool for managing XAML and XAML documents outside Visual Studio

Install Order:

1) install .Net Framework 3.0
2) install Extensions for WPF,WCF and WF;
3) if you want to study .Net 3.0 detail you can download and install the SDK. It contains all the documentation and samples
4) XMLNotepad is required only if you works extensive on WPF.

Note: Visual Studio Express Editions are not compatible with SDK.