6 Free Tools To Help You Run Windows Applications On Linux

6 Free Tools To Help You Run Windows Applications On Linux

When switching from Windows to a more secured Linux operating system, you may come up with many difficulties. Like for example you might not find the applications you needed for doing your daily work. Although you can find any and all the replacements of a Windows application on Linux, there is a way through which you can run your favorite Windows application on your Linux operating system. Here we have compiled a list of 6 free tools that will help you run your favorite Windows application on a Linux system or help you to run virtual PC on any Operating System.

You are welcome to share if you know more free tools that will help you run your favorite Windows application on a Linux 

Wine

Wine is an Open Source implementation of the Windows API on top of X, OpenGL, and Unix. Think of Wine as a compatibility layer for running Windows programs. Wine does not require Microsoft Windows, as it is a completely free alternative implementation of the Windows API consisting of 100% non-Microsoft code, however Wine can optionally use native Windows DLLs if they are available. Wine provides both a development toolkit for porting Windows source code to Unix as well as a program loader, allowing many unmodified Windows programs to run on x86-based Unixes, including Linux, FreeBSD, Mac OS X, and Solaris.

VirtualBox

VirtualBox is an x86 virtualization software package, originally created by German software company innotek, now developed by Sun Microsystems as part of its Sun xVM virtualization platform. It is installed on an existing host operating system; within this application, additional operating systems, each known as a Guest OS, can be loaded and run, each with its own virtual environment. Supported host operating systems include Linux, Mac OS X, OS/2 Warp, Windows XP or Vista, and Solaris, while supported guest operating systems include FreeBSD, Linux, OpenBSD, OS/2 Warp, Windows and Solaris.

Qemu

QEMU is a generic and open source machine emulator and virtualizer. When used as a machine emulator, QEMU can run OSes and programs made for one machine (e.g. an ARM board) on a different machine (e.g. your own PC). By using dynamic translation, it achieves very good performances. When used as a virtualizer, QEMU achieves near native performances by executing the guest code directly on the host CPU. A host driver called the QEMU accelerator (also known as KQEMU) is needed in this case. The virtualizer mode requires that both the host and guest machine use x86 compatible processors.

Bochs

Bochs is a highly portable open source IA-32 (x86) PC emulator written in C++, that runs on most popular platforms. It includes emulation of the Intel x86 CPU, common I/O devices, and a custom BIOS. Currently, Bochs can be compiled to emulate a 386, 486, Pentium/PentiumII/PentiumIII/Pentium4 or x86-64 CPU including optional MMX, SSEx and 3DNow! instructions. Bochs is capable of running most Operating Systems inside the emulation including Linux, DOS, Windows® 95/98 and Windows® NT/2000/XP or Windows Vista. Bochs was written by Kevin Lawton and is currently maintained by this project.

rdesktop

rdesktop is an open source client for Windows Terminal Services, capable of natively speaking Remote Desktop Protocol (RDP) in order to present the user’s Windows desktop. Supported servers include Windows 2000 Server, Windows Server 2003, Windows Server 2008, Windows XP, Windows Vista and Windows NT Server 4.0. Rdesktop currently runs on most UNIX based platforms with the X Window System, and other ports should be fairly straightforward.

Xen

The Xen® hypervisor, the powerful open source industry standard for virtualization, offers a powerful, efficient, and secure feature set for virtualization of x86, x86_64, IA64, PowerPC, and other CPU architectures. It supports a wide range of guest operating systems including Windows®, Linux®, Solaris®, and various versions of the BSD operating systems. The Xen hypervisor is a unique open source technology, developed collaboratively by the Xen community and engineers at over 20 of the most innovative data center solution vendors, including AMD, Cisco, Dell, HP, IBM, Intel, Mellanox, Network Appliance, Novell, Red Hat, SGI, Sun, Unisys, Veritas, Voltaire, and Citrix. Xen is licensed under the GNU General Public License (GPL2) and is available at no charge in both source and object format. Xen is, and always will be, open sourced, uniting the industry and the Xen ecosystem to speed the adoption of virtualization in the enterprise.

Five Desktop Tools To Create Excellent Windows Environment

Five Desktop Tools To Create Excellent Windows Environment

 

There are many desktop tools out there for every type of computer users, but getting by good ones and free is not that easy. That is why I am sharing Five Desktop Tools To Create Excellent Windows Environment. Read each entry in the list and see which one suits your needs best.

You are welcome if you want to share desktop tools that our readers/viewers may like. 

File Repair

File Repair software is a powerful tool to repair your corrupted files. It scans the damaged file and extracts maximum data from it to a new usable file. You can repair word documents, excel spreadsheets, zip, rar, selected video formats, pdf, etc.

Cryogenic FileSplitter

This is a simple application written in C# by which you can split large files into several pieces to transfer them easily over Internet. With its unique “Drag and Drop” feature, you can split or join .001 files easily.

USBFlashCopy

USBFlashCopy is a small Windows utility to back up your flash drives and storage cards on the fly. It runs in the background and copies files from inserted media to a safe location on your hard drive. USBFlashCopy copies only newer or updated files, you can optionally keep old versions of the files.

Appnimi ZIP Password Unlocker

Appnimi ZIP Password Unlocker is designed to let you search for passwords of protected ZIP files. This program guarantees the most complicated passwords recovery. Appnimi ZIP Password Unlocker allows to search for the password of the protected ZIP file using Brute Force algorithm. After recovering the password it will extract the files to a destination folder.

Driver Magician Lite

Driver Magician Lite is freeware, it identifies all the hardware in the system, extracts their associated drivers from the hard disk and backs them up to a location of your choice. Then when you format and reinstall/upgrade your operating system, you can restore all the “saved” drivers just as if you had the original driver diskettes in your hand

Learning Basic Unix Commands Videos Downlaod

Learning Basic Unix Commands 

Are you a Linux newbe? Ever sat in front of a Linux Konsole and felt a little lost, or perhaps frightened? Well, you 
never have to feel that way again thanks to Brian and Kevin from WiBit.Net We have put together a reat combination of Linux commands ordered in somewhat of importance and complexity. After watching these videos you will have the knowledge that is needed in order to operate a Linux Konsole with a newly found sense of confidence. 










Video 1 : Getting Help 
Video 2 : Filesystem Navigation 
Video 3 : File Creation 
Video 4 : File Viewing & Searching 
Video 5 : File Manipulation 
Video 6 : Basic Konsole Programs 
Video 7 : Unix Shell Programming 

Download - (46 Mb) 

Windows Server 2003 MCSE training videos

Windows Server 2003 MCSE training videos have been developed by a few of the best Microsoft trainers

Video Contents:-

01) Windows Server 2003 - Active Directory Installation
02) Windows Server 2003 - Active Directory Users and Computer Management
03) Windows Server 2003 - DHCP Client Configuration
04) Windows Server 2003 - DHCP Server Address Leases
05) Windows Server 2003 - DHCP Server Configuration
06) Windows Server 2003 - DNS Server Configuration
07) Windows Server 2003 - DNS Server Forwarder Configuration
08) Windows Server 2003 - File Server & Shadow Copy
09) Windows Server 2003 - IIS Server Configuration
10) Windows Server 2003 - IIS Server Installation
11) Windows Server 2003 - Logging into an Windows Server 2003 Domain
12) Windows Server 2003 - Mail Server Installation
13) Windows Server 2003 - Mail Server Test
14) Windows Server 2003 - Print Server Configuration
15) Windows Server 2003 - RAS Server Configuration
16) Windows Server 2003 - Streaming Media Server Installation
17) Windows Server 2003 - Streaming Media Server Configuration I
18) Windows Server 2003 - Streaming Media Server Configuration II
19) Windows Server 2003 - Terminal Server Installation
20) Windows Server 2003 - Terminal Server Usage
21) Windows Server 2003 - WINS Server

windows 2003 domain configuration Videos to Download

windows 2003 domain configuration Videos to Download

Howto_configure_RAID1_in_Windows_Server_2003

RAID_5__explained

RAID_levels_0__1__and_5.mp4

How_to_Install_and_Configure_FTP_in_Windows_2003.mp4

Backup_e_Restore_AD_w2003.mp4

Brodcade_Switch__configuration.mp4

Installing_Microsoft_Exchange_Server_2003_-_Windows_Server_2003_R2.mp4

How_to_Backup_Active_Directory___DNS_with_NTBACKUP.mp4

Installing_Active_Directory_-_Windows_Server_2003_R2.mp4

How_to_Backup_Active_Directory___DNS_with_NTBACKUP.mp4

Installing_Active_Directory_-_Windows_Server_2003_R2.mp4

RemoteFX.flv.mp4

Add_domain_child_into_Forest_root_domain.mp4

How_To_Install_and_Configure_RRAS_NAT_amp_amp_VPN.mp4

Add_domain_child_into_Forest_root_domain.mp4

Install_and_Configure_Domain_Name_System__DNS__on_Windows_Server_2003_for_Internal_Website.mp4

Child_Domain__.mp4

How_To_Create_SQL_Failover_Cluster.mp4

SAN_vs._NAS.mp4

How_To_Zone_Brocade_Switch_for_Use_with_Fiber_Channel_Storage.mp4

AD_Schema_and_Operations_Master_Roles.mp4

8_How_to_Create_Mandatory_Profile_for_Windows_Server_2003.mp4

Domain_Name_System__DNS__How_It_Works.mp4

GPO_User_Configuration_Policies.mp4

How_to_Remove_Delegated_Control_from_Users_on_Windows_Server_2003.mp4

Microsoft_Management_Console.flv

Configure_Roaming_and_Mandatory_Profiles.mp4

How_To_Add_a_Group_Policy_in_Windows_2003_Active_Directory.mp4

SQL_Server_2005_cluster_using_windows_2003__and_virtual_server_2005_R2.mp4

FSMO_Roles.AVI

DHCP_configuracion.mp4

MICROSOFT_EXCHANGE_Configuration.mp4

Monitoring_Performance.avi.mp4

How_To_Set_Up_a_Windows_Server_Cluster.mp4

How_to_Recover_an_Active_Directory_object.mp4

Local_User_and_Group_Management.flv

Configure_Active_Directory_Windows_2003.mp4

How_To_Manage_Trust_Relationships_Between_Domains_Quick__anp_Simple.mp4

Install_Configuration_DNS_with_Primary_Zone_-_Windows_Server_2003.mp4

Hi Friends please click on ads if you satisfy's from here......!

Implementing a Two Node Cluster with Windows 2003 Enterprise 2

Link 1 

Windows 2003 Cluster Setup

I will not explain every step for installing a Windows 2003 Cluster. For detailed information click the following link.
I will show you only a few pictures.

Figure 1: Create a new Cluster

The Windows 2003 Cluster administrator after successful installation.

Figure 2: Cluster Administrator

Exchange 2003 Cluster Setup

Before we install Exchange 2003, we must create a MS-DTC (Distribution Transaction Coordinator) resource.
In Windows 2003, Microsoft recommends installing the DTC as a separate Cluster Group containing a Physical Disk, Network Name and IP address resource and then adding the MSDTC resource to the cluster group.
For more in formation how to setup the MS-DTC in a Windows 2003 Cluster, read the following Knowledge Base article.
The second step is to install Exchange 2003 and all required hotfixes on each node. You MUST install Exchange one after the other. After installing Exchange, you can deploy Exchange 2003 SP1 on every cluster node. For more information on how to deploy Exchange 2003 SP1 into a cluster environment read the following article.
Once the Exchange 2003 binaries have been installed on the cluster Node we can now create an Exchange Virtual Server.
The Exchange Virtual Server creation process is much the same as for Exchange 2003. First we need to create a cluster group for the Exchange Virtual Server. The group must have at least one physical disk resource, at least one IP address resource, and a network name resource. The network name resource must have a dependency on the IP address resources in the cluster group.
When all resources are online, we must create the System Attendant resource. The System Attendant Resource (SA) creates all the other Exchange 2003 cluster resources automatically.
To do this, right click the Exchange 2003 cluster group and choose New Resource and then choose the Microsoft Exchange System Attendant. You must name the SA.

Figure 3: Exchange System Attendant

Add the Nodes that will be possible owners of the System Attendant Resource. A possible owner is a node in the cluster on which the resource can be brought online. These Nodes will also be added as a possible owner of all the other Exchange resources that are automatically created. A Node must be specified as a possible owner of a resource in order for us to failover to that Node.

Figure 4: Possible owners of the EVS

You must set the dependencies on the System Attendant Resource. The dependencies are the following:

• Network Name resource
• All disk resources (that Exchange 2003 should use - this includes Mount Point disks which will contain Exchange 2003 data)

Figure 5: SA – Resource dependencies

Like a normal Exchange installation you must select the administrative group where the Exchange virtual server is created.

Figure 6: Chose the administrative Group for the EVS

Within the chosen Administrative Group you now have to choose a Routing Group where the Exchange Virtual Server will be located when more than one Routing Group exists at the time of EVS creation. You can change the server location in the Routing Group after installation.

Figure 7: Select the routing group for the EVS

Please read the wizard's summary carefully.

Figure 8: Exchange 2003 Wizard summary

Click Finish to start the creation process. This may take a while because the setup process actually creates all Exchange 2003 cluster resources. When the process is complete you will see the following message:

Figure 9: DONE

The following picture shows the Cluster Administrator tool after EVS installation. Note that all Exchange resources are NOT online.

Figure 10: Cluster Administrator after EVS installation

Exchange 2003 no longer creates a POP3 and IMAP cluster resource. This is part of Microsoft's Trustworthy initiative and it is also true for a “normal” Exchange 2003 installation.
Next, we have to bring the System Attendant resource online. To do so, right click the EVS System Attendant and click “Bring Online”.

Figure 11: You have to bring the System Attendant Online.

Exchange 2003 Resource dependencies

Microsoft has changed the Exchange 2003 resource dependencies to allow a faster failover/failback.

In Exchange 2000 there are the following dependencies:IP Address > Network Name > System Attendant
Physical Disk > System Attendant
Routing Engine > System Attendant
Information Store  > System Attendant
MTA > System Attendant
MS Search > Information Store
POP3 > Information Store
SMTP > Information Store
IMAP4 > Information Store
Beginning with Exchange 2003 Microsoft has changed the Resource dependencies:IP Address > Network Name > System Attendant
Physical Disk > System Attendant
Routing Engine > System Attendant
Information Store  > System Attendant
MTA > System Attendant
MS Search > System Attendant
POP3 > System Attendant
SMTP > System Attendant
IMAP4 > System Attendant

Link 1 

Implementing a Two Node Cluster with Windows 2003 Enterprise

What is a cluster – a definition!

A cluster is a group of computers, called nodes that function as a single computer/system to provide high availability and high fault tolerance for applications or services.  Windows 2003 Servers can participate in a cluster configuration through the use of Cluster Services. If one member of the cluster (the node) is unavailable, the other computers carry the load so that applications or services are always (with a small interruption) available.
All nodes of the cluster use a Shared Disk – an external disk or disk subsystem which is accessible for all nodes through SCSI (2 Nodes) or Fibre Channel (more than 2 nodes). All data will be stored on the shared disk or an external disk subsystem (for example Exchange databases).
Every node has a local Exchange 2003 installation with a unique configuration for every cluster node. Each Cluster with Exchange 2003 has at a minimum one Exchange Virtual Server (EVS). An EVS is the logical node that will be used for all cluster operations. An EVS contains an IP address, network name, physical disk and an application.
A cluster can be …

• Active/Active or
• Active/Passive

Microsoft recommends only Active/Passive clusters – I will give you the reason later.
The number of cluster nodes supported by Windows 2003 Enterprise and Datacenter is 8 nodes. Windows Server 2003 Standard and Web Editon doesn’t support a Cluster.
In an Active/Passive cluster - If one node in the cluster fails, the active cluster failover to another node which becomes Active. This is called Failover. If the failed node is back online, a Failback can be manually initiated or automatically configured in the Cluster Group properties.
Every cluster node must have two network interfaces. One network interface for the cluster communication called the private LAN and one network interface called the public LAN. You can link a cluster with two nodes with a simple cross link cable. If more than two nodes exist in the cluster you have to use a dedicated switch / hub.
The private NIC is used for the Heartbeat communication (Cluster communication). A Heartbeat is much like a ping which can be used to test if the other cluster node is still available. If the heartbeat fails, the Failover process occurs.

Clustering changes with Exchange 2003 SP1

In versions before Exchange 2003 SP1, regardless of the number of cluster nodes you could only have one instance of a Public Folder store that is associated with the MAPI folder tree.
In Exchange 2003 SP1, the Exchange development team added the ability to have multiple MAPI Public Folder databases on a single multi node cluster.
This support was added because the Exchange team saw that Outlook 2003 cached mode puts a greater load on Public Folders like the Outlook Address Book (the OAB will be loaded offline at the client). With the help of multiple Public Folder stores the load can be spread across these folders. This allows a better client performance.

Why Active/Active cluster is not recommended

Active / Active cluster is not recommended because of Virtual memory (VM) fragmentation.
When two instances of the information store is running in one memory space, it might be possible that sufficient VM does not exist to bring the resource online during a failover/failback.
For more information see here:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;816893
There are three main concepts which reduce virtual memory fragmentation:

• Decrease the number of dynamic allocations when the system is started
• Increase the size of the virtual address space
• Allocate similar size allocations from common regions of memory

Exchange Server 2003 Cluster Requirements

• Microsoft Windows 2000 Advanced Server (up to two nodes)
• Windows 2000 Datacenter Server (up to four nodes)
• Windows 2000 must have SP3 + 329938 hotfix or SP4
• Windows Server 2003, Enterprise Edition (up to eight cluster nodes)
• Windows Server 2003, Datacenter Edition (up to eight cluster nodes)
• Hardware on cluster HCL
• Windows 2000 - Check lists for cluster service installation
  http://go.microsoft.com/fwlink/?LinkId=266
• Windows Server 2003 – http://go.microsoft.com/fwlink/?LinkId=17219
• Microsoft Distributed Transaction Coordinator (MSDTC) installed

Exchange Server 2003 Cluster Setup Changes

• Block removal of node if an EVS is running on the cluster
• The /disasterrecovery switched is blocked
• Prevent Exchange 2003 from being first non-legacy server in a Exchange 5.5 site
• By default, POP3 and IMAP4 resource not created (as part of the Trustworthy Computing initiative from Microsoft)
• Cluster service account doesn’t requires Exchange full admin rights
• IPSEC is now supported between front-end servers and back-end clusters

Exchange Server 2003 Cluster Disk Changes

Windows 2003 clusters now support Volume Mount points to overcome the limits of traditional drive letter assignments. This new feature is very useful for four and eight node Exchange clusters because the traditional drive letter assignment in Exchange was very limited in cluster environments when multiple storage groups and stores where used.

Windows 2003 Cluster Setup

I will not explain every step for installing a Windows 2003 Cluster. For detailed information click the following link.
I will show you only a few pictures.

Figure 1: Create a new Cluster

The Windows 2003 Cluster administrator after successful installation.

Figure 2: Cluster Administrator

Follow the Link for continuation