Play Windows games on Linux with Crossover

 

CrossOver Games is an addition to the popular CrossOver series. Unlike other CrossOver products, which are aimed primarily at office productivity applications, CrossOver Games focuses on the stability of installing Windows games on Linux (and Mac OSX). As the same as PlayOnLinux, CrossOver Games provides a click and install method that makes it simple for anyone to use. The latest version of CrossOver Games has already tested to work with more than a hundred Windows games, including the popular World of Warcraft, Half-Life2 and Counterstrike.

Crossing over

When it comes to playing the games, Crossover Games is relatively straightforward to use. And in comparison to getting certain SecuROM titles to work on Windows, it can be considerably easier. But your first step has to be a check for compatibility.

Crossover hosts an online database that lists around 200 games titles that are known to work, and a few that don't. Compatibility is graded by gold, silver and bronze awards, and if your game wins any of these, you should be able to play it through without too much difficulty. Crossover judges compatibility against its own very high standards, and tries to be completely truthful about the faithfulness of a working game.

what is Master boot record and LILO ?

Master boot record and LILO

What is the master boot record (MBR) and why does LILO erase the old boot loader? Every hard drive has a
top space called the MBR where the BIOS will try to load an operating system. Every system has its own
loader. DOS has DOS-MBR, Windows NT has the NTLDR and Linux has LILO.
When you install LILO, you can install it in the MBR or in a boot record for the Linux partition. If you want
to keep your current boot loader, you can select the Linux partition, and make sure it is the active partition in
fdisk. This way you will be able to boot to LILO, and then boot the old loader from the MBR.
If you plan on only using Linux on your system, you can tell LILO to boot right into Linux and not display a
"boot:" prompt, and you can install it in the MBR.

Master boot record (MBR) is a type of boot sector popularized by the IBM Personal Computer.It consists of a sequence of 512 bytes located at the first sector of a data storage device such as a hard disk. MBRs are usually placed on storage devices intended for use with IBM PC-compatible systems.

The MBR may be used for one or more of the following:

• Holding a partition table which describes the partitions of a storage device. In this context the boot sector may also be known as a partition sector.
• Bootstrapping an operating system. The BIOS built into a PC-compatible computer loads the MBR from the storage device and passes execution to machine code instructions at the beginning of the MBR.
• Uniquely identifying individual disk media, with a 32-bit disk signature, even though it may never be used by the operating system.

do you ever heard of a Live CD ?



Ubuntu 11.04 Beta 2 system running from a live CD,
 with the new Unity desktop environment



A live CD, live DVD, or live disc is a CD or DVD containing a bootable computer operating system. Live CDs are unique in that they have the ability to run a complete, modern operating system on a computer lacking mutable secondary storage, such as a hard disk drive. Live USB ,flash drives are similar to live CDs, but often have the added functionality of automatically and transparently writing changes back to their bootable medium.

Origin of Linux live CDs

Although early developers and users of distributions built on top of the Linux kernel were able to take advantage of cheap optical disks and rapidly declining prices of CD drives for personal computers, the Linux distribution CDs or "distros" were generally treated as a collection of installation packages that must first be permanently installed to hard disks on the target machine.

However in the case of these distributions built on top of the Linux kernel, the free operating system was meeting resistance in the consumer market because of the perceived difficulty, effort, and risk involved in installing an additional partition on the hard disk, in parallel with an existing operating system installation.

The term "live CD" was coined because after typical PC RAM was large enough and 52x speed CD drives and CD burners were widespread among PC owners, it finally became convenient and practical to boot the kernel, run X11, a window manager and GUI applications directly from a CD without disturbing the OS on the hard disk.

This was a new and different situation for Linux than other operating systems, because the updates/upgrades were being released so quickly, different distributions and versions were being offered online, and especially because users were burning their own CDs.

The first Linux-based 'Live CD' was Yggdrasil Linux first released in beta form 1992~1993 (ceased production in 1995), though in practice its functionality was hampered due to the low throughput of contemporary CD-ROM drives. DemoLinux, released in 1998, was the first Linux distribution specially designed as a live CD.

The Linuxcare bootable business card, first released in 1999, was the first Live CD to focus on system administration, and the first to be distributed in the bootable business card form factor.

As of 2010, Finnix (first released in 2000) is the oldest Live CD still in production.Knoppix, a Debian-derived Linux distribution, was released in 2003, and found popularity as both a rescue disk system and as a primary distribution in its own right.

Since 2003, the popularity of live CDs has increased substantially, partly due to Linux Live scripts and remastersys which made it very easy to build customized live systems. Most of the popular Linux distributions now include a live CD variant, which in some cases is also the preferred installation medium.

Uses

While some live CDs are designed to "demo" or "test drive" a particular operating system (usually Linux or another free or open source operating system), there are live CDs made for many different uses.

Although some live CDs can load into memory in order to free the optical drive for other uses, loading the data off a CD-ROM is still slower than a typical hard drive boot, so this is rarely the default with large live CD images, but for smaller live CD images loading the filesystem directly into RAM can be highly practical. Loading the filesystem image into RAM can provide a significant performance boost as RAM is several orders of magnitude faster than a hard drive.

Also, since RAM has no moving parts, a system running from a live CD loaded into RAM can run with improved power efficiency.Experienced users of the operating system may also use a live CD to determine whether and to what extent a particular operating system or version is compatible with a particular hardware configuration and certain peripherals, or as a way to know beforehand which computer or peripheral will work before buying. 

Users may also use a live CD to troubleshoot hardware, especially when a hard drive fails, and more generally as a recovery disc in case of problems. Some live CDs can save user-created files in a Windows partition, a USB drive, a network drive, or other accessible media.

A few additional uses include:

• installing a Linux distribution to a hard drive
• testing new versions of software
• listing & testing hardware
• system repair and restoration
• high security/non-invasive environment for a guest
• cracking/stealing passwords
• network security testing
• being the primary or backup operating system for any computer
• quick and simple clustering of computers 
• computer forensics
• playing video games
• providing a secure server platform where crucial files cannot be permanently altered
• providing a secure, reliable platform for the performance of high-vulnerability tasks such as internet banking;
• Internet kiosks, which can be brought back to their original state by a reboot

Thematic Live CDs

Several live CDs are dedicated to specific type of applications according to the requirements of thematic user communities. These CDs are tailored to the needs of the applications in subject including general knowledge, tutorial, specifications and trial data too.

Some of these topics covers sub topics, e.g. IT administration breaks down to firewall, rescue, security, etc. type of live CDs. In some cases a particular LiveDVD covers more than one topic.

Live CD software appliances

Packaging a software appliance as an installable live CD can often be beneficial as a single image can run on real hardware in addition to most types of virtual machines.

This allows developers to avoid the complexities involved in supporting multiple incompatible virtual machine images formats and focus on the lowest common denominator instead.

Typically after booting the machine from the live CD, the appliance will either run in non-persistent demo mode or install itself, at the user's request, to an available storage device.

Mounting without burning

The files on a live CD ISO image can be accessed in Microsoft Windows with a disk image emulator such as Daemon Tools, or in Unix variants by mounting a loop device.

After mounting the live CD's filesystem, software on the live CD can be run directly (I.e., without booting) by chrooting into the live CD's mounted filesystem.

A live CD ISO image can also be mounted by Virtual Machine software such as VirtualBox and VMware Workstation or can be converted to a Live USB using SYSLINUX. Tools such as UNetbootin can automate this process.

Common traits

Some live CDs come with an installation utility launchable from a desktop icon that can optionally install the system on a hard drive or USB flash drive. Most live CDs can access the information on internal and/or external hard drives, diskettes and USB flash drives.

Generally live CDs are booted from read-only media, requiring either copying to rewriteable media (i.e. a hard drive) or complete remastering to install additional software; however, there are exceptions such as Puppy Linux which has the ability to save files to the live CD itself or other multisession media, allowing users to carry data, and more importantly, added programs and customized settings, along with them on optical disc.

Most live CDs are based on Linux,

as this was the operating system that had the most to gain by offering free trials and demonstrations without regard to sales or copyright. Now others are using the term live CD for other operating systems, such as 

OpenSolaris, BeleniX and others based on Solaris. Other "live" operating systems include AmigaOS 4, FreeBSD, FreeDOS, Mac OS, Microsoft Windows, OS/2, ReactOS, NetBSD, OpenBSD, MINIX 3, Plan 9 from Bell Labs, and MorphOS.

The first personal computer operating system on a CD to support "live" operations might have been the AmigaOS, which could be booted from CD on an Amiga CDTV in 1990.

Earlier examples of live OS are of course the operating systems used from floppy, and most widely spread is DOS.

Unlike previous operating systems on optical media, though, Linux and OS/2 "live CDs" were specifically designed to run without installation onto other media like a hard disk drive. The live CD concept was meant to promote Linux and showcase the abilities of the free, open source operating system on conventional personal computers with Microsoft Windows already installed.

On a PC, a bootable Compact Disc generally conforms to the El Torito specification. Many Linux based live CDs use a compressed filesystem image, often with the cloop compressed loopback driver, or squashfs compressed filesystem, generally doubling effective storage capacity, although slowing application start up

The resulting environment can be quite rich: typical Knoppix systems include around 1,200 separate software packages. Live CDs have a reputation for supporting advanced auto-configuration and plug-and-play functionality. This came out of necessity to avoid requiring the user to configure the system each time it boots and to make it easily usable by those who are new to the operating system.

Technique

A read-only file system, such as on a CD-ROM has the drawback of being unable to save any current working data. For this reason, a read-only file system is often merged with a temporary writable file system in the form of a RAM disk. Often the default Linux directories "/home" (containing users' personal files and configuration files) and "/var" (containing variable data) are kept in ramdisk, because the system updates them frequently. Puppy linux has a savable layer so if you choose to, the next time you boot you can resume (pick right back up again) from where you left off. Each time the CD boots, it looks for the file and then uses it if it has the right name.

In modern live CDs, a read-only file system is merged with ramdisk using transparent techniques such as UnionFS, AuFS or EWF. In MS-DOS and OS/2 systems, ramdrive.sys, can be loaded at boot for this purpose. Boot loaders like syslinux can boot ISO files from USB memory devices.

Live CDs have to be able to detect and use a wide variety of hardware (including network cards, graphic cards etc.) in realtime. This is easily achieved nowadays by udev, hotplug, hal, udisk etc.. which is a common part of all distributions based on Linux kernel 2.6.

Boot code

During live CD initialization, a user typically may resort to using one or more boot codes to change the booting behavior. These vary from distribution to distribution but can most often be accessed upon first boot screen by one of the function keys.

How to Creating a New Partition in Linux

In most Linux systems, you can use the fdisk utility to create a new partition and to do other disk management operations.

Note: To be able to execute the commands necessary to create a new partition on Linux, you must have the root privileges.

As a tool with a text interface, fdisk requires typing the commands on the fdiskcommand line. The following fdisk commands may be helpful:

Options	Description
m	Displays the available commands.
p	Displays the list of existing partitions on your hda drive. Unpartitioned space is not listed.
n	Creates a new partition.
q	Exits fdisk without saving your changes.
l	Lists partition types.
w	Writes changes to the partition table.

To create a new partition on Linux

1. Start a terminal.
2. Start fdisk using the following command:/sbin/fdisk /dev/hdawhere /dev/hdastands for the hard drive that you want to partition.
3. In fdisk, to create a new partition, type the following command:n
   • When prompted to specify the Partition type, type p to create a primary partition or e to create an extended one. There may be up to four primary partitions. If you want to create more than four partitions, make the last partition extended, and it will be a container for other logical partitions.
   • When prompted for the Number, in most cases, type 3 because a typical Linux virtual machine has two partitions by default.
   • When prompted for the Start cylinder, type a starting cylinder number or press Return to use the first cylinder available.
   • When prompted for the Last cylinder, press Return to allocate all the available space or specify the size of a new partition in cylinders if you do not want to use all the available space.
   By default, fdisk creates a partition with a System ID of 83. If you’re unsure of the partition’s System ID, use the
   l
   command to check it.
4. Use thewcommand to write the changes to the partition table.
5. Restart the virtual machine by entering therebootcommand.
6. When restarted, create a file system on the new partition. We recommend that you use the same file system as on the other partitions. In most cases it will be either the Ext3 or ReiserFS file system. For example, to create the Ext3 file system, enter the following command:/sbin/mkfs -t ext3 /dev/hda3
7. Create a directory that will be a mount point for the new partition. For example, to name it data, enter:mkdir /data
8. Mount the new partition to the directory you have just created by using the following command:mount /dev/hda3 /data
9. Make changes in your static file system information by editing the /etc/fstab file in any of the available text editors. For example, add the following string to this file:/dev/hda3 /data ext3 defaults 0 0In this string /dev/hda3 is the partition you have just created, /data is a mount point for the new partition, Ext3 is the file type of the new partition. For the exact meaning of other items in this string, consult the Linux documentation for the mount and fstab commands.
10. Save the /etc/fstab file.