Archive for March 6th, 2012

How to Install Windows Applications on Linux Using Wine

Today you can run many Windows software from Linux native using Wine or one of the many virtualization tools such as VMWare.

There are so many new developments regarding how to apply Wine to run Windows programs on Linux that we are now updating this entire page contents. In the mean time you may find it beneficial to visit: http://www.wine-reviews.net/ and http://frankscorner.org/ for Wine help.

Many readers also found it helpful to first review our introductory article: Windows to Linux: A Hand Holding Guide.

This page is brought you by the folks at Really Linux.

For those with dual boot systems, this simple introductory article shows you a way to run a few of your basic Windows programs from Linux. But there is much more and so please come back to re-read the revised article. This Tip is Rated Intermediate.

Free Tool for running Windows Programs in Linux called WINE
WINE is available for free download from the project website you can access by clicking here. (For Windows users, you should make sure to get in your download the three files needed for running WINE properly: winerpm, updated wine.conf, user.dat file.)

A lot of work and many hours of effort have paid off, and Linux users actually can download and install a free emulator that runs many Windows programs without any issue under Linux.

In some cases, you do still need Windows installed on the same machine, since otherwise, there is no way to “install” your Windows software that sometimes may require a specific Windows install utility to run. Currently WINE is tuned for Windows98 and Windows 2000 programs.

Wine Example
If you’ve followed the very first step above and downloaded and installed WINE on your Linux machine, then you are ready to try running a Windows program from Linux.

Notice that this is just a very brief sample of how Wine can be used to run a basic Windows application. Details will be provided in our updated Wine page.

Check to see that the WINE program is truly installed by typing the command: locate wine You should see a list of files with WINE.
Be sure you have properly mounted your Windows drive. If you don’t know how then click here for brief help.
Edit the file /etc/wine.conf by changing the line under [Drive C] to read exactly: Path=/mnt/win
Save the edited wine.conf file and then make sure you also copy the file user.dat to your Windows directory c:/windows/profiles/
If you plan on running a game or other program that uses your midi then Linux midi-sequencer needs to be installed
Now type: cd “/mnt/win/Program Files/Accessories” then type: wine ./calc.exe
This will run Windows Calculator on your Linux! You can load any other programs by using similar commands, adjusting for directory names and file names as needed.
A few tips. First of all disregard all of the detailed error information that may be displayed while you run Wine. Only on occasion do these error messages help you troubleshoot why a program does not run under WINE.

Second, many programs will not run properly under WINE unless your LINUX has been configured for sound and graphics. There are lots of details to this we can not explain breifly here. You can contact us or read up on details from your Linux installation guide.

Finally, remember that you need to type the commands exactly as they appear, for instance when using long directory names you need to have begin and end ” marks. When you try to run a program you should include the leading ./ infront of the executable program name.

WINE Doesn’t Run What You Need
There are times when the application you wish to use requires more specific graphical or environment controls. Although Wine is very capable with most applications, and the internet has a lot of good Wine resources, you may find the need to choose one of the other products that either run Linux as a virtual machine, or create an emulation mode for running your application. We recommend you review the following:VMWare and also Win4Lin websites. These companies have made a lot of progress for folks like you!

Easily run Windows apps on Linux with CrossOver Linux

I was running Windows, and before it came along, MS-DOS, applications on Unix and Linux for ages. It was never especially easy, but experts could do it. With CodeWeavers’ latest CrossOver Linux, though, it’s become so easy that anyone should be able to do it.

Now, if all your desktop needs are already being met by Linux applications, you don’t need to worry with Crossover. But, if like many of us, you still want to use Quicken for your banking or you’re stuck with a Web site that refused to work with any Web browser except Internet Explorer, then Crossover Linux 8 is for you.

CrossOver Linux is built on top of the open-source project Wine. This is an implementation of the Windows API (application programming interface) on top of the Unix/Linux operating system family. As far as any given program is concerned, it’s running on Windows so you don’t have to tweak the applicaton itself to run on Linux. Wine is a very active project, with 16 years of development behind it. In other words, this program has been better-tested for Windows compatibility than almost any native Windows operating system.

You can use Wine alone to run Windows programs, but it requires a fair amount of technical expertise. With CrossOver, you don’t need to be an expert.

CrossOver Linux delivers automated Windows application installation and technical support. If you’d rather just run your Windows application, and not worry over whether it will run better in Windows 98 or XP mode, CrossOver Linux, which sells for $39.95 for a single-user license or $69.95 for a multi-user license, is well worth the money. I know this for a fact, because I’ve bought CrossOver licenses myself.

I put this latest version of CrossOver to the test on two different PCs. The first is my main Linux desktop on which I run MEPIS 8, a Debian Linux. This is a Dell Inspiron 530s, powered by a 2.2GHz Intel Pentium E2200 dual-core processor with an 800MHz front side bus, 4GB of RAM, a 500GB SATA drive, and an Integrated Intel 3100 Graphics Media Accelerator.

I also tried CrossOver 8 on my Ubuntu 9.04 desktop. This is an older Gateway 503GR running Ubuntu 8.04. It comes with a 3GHz Pentium 4 CPU, 2GB of RAM, an ATI Radeon 250 graphics card, and a 300GB SATA drive. Neither machine is close to being state of the art, but they both have more than enough resources to run Linux, CrossOver Linux, and multiple Windows and Linux programs at the same time.

CrossOver 8 will run on any modern Linux. It comes in versions for 32-bit and 64-bit Debian and Ubuntu Linux-based distributions and for 32-bit Red Hat, Mandriva, and SUSE distributions. In addition, there’s a distribution agnostic version, which will install on any up-to-date Linux. While I didn’t test it out to any real extent, I did find that CrossOver seemed to work just fine on Fedora 11 and openSUSE 11.1. No matter what version of Linux you run, CrossOver will do fine on all three of the popular Linux interfaces: GNOME, KDE 3, and KDE 4.

Installing Windows applications with it is mindlessly simple. You just pick, which popular Windows application you want to install and either start the download or pop in the CD or DVD. You can also install Windows applications, which haven’t been tested throughly. Some, such as my favorite HTML editor, Fookes Software NoteTab, run more than well enough to be useful.

CrossOver already supports though a large number of popular Windows applications. The list includes Office 97 to 2007, Quicken, Internet Explorer, and QuickTime. The multi-user version also comes with support for Windows games like World of Warcraft and, my personal favorite, Guild Wars. Since I play Guild Wars competitively, I can assure you that, much as I like Linux, I wouldn’t be running a Windows game on it if the game wasn’t as responsive on Linux as it is on Windows.

This particular version of CrossOver also comes with new support for Internet Explorer 7 and Quicken 2009. It also includes many fit, polish, and performance enhancements.

While CrossOver can’t run every Windows program, and you will find glitches from time to time in some others, it really does make it possible to run the most often needed Windows applications without having to pay for Windows. I must also add, that in some cases, such as with Quicken, I’ve found CrossOver to be more compatible with the popular finance program than Microsoft’s own Vista has been.

Not sure if it will work for you? Judge for youself. You can download a free 30-day trial version of CrossOver Linux. Finally, I must mention that CodeWeavers also offers CrossOver Mac, which brings the same functionality to Intel-powered Macs. I use this to Quicken for Windows on a Mac, since, for reasons that only Quicken’s maker Intuit might know, the Mac and Windows versions of Quicken use incompatible data formats.

Running windows .exe file formats over Linux or Mac

as we all are aware of the fact that .exe files are executable files for windows environment only and linux supports .rpm and mac supports .dmg extensions for executable files to be run. but here is an alternative solution for all of these OS’s which gives the solution of running .exe files on your most likly Operating system as well …
the options are
1. using free Wine
2. using commercial Wine
-> using crossover (Developed on top of Wine)
-> using BORDEAUX (Developed on top of Wine)
3. using VMware
4. using Oracle virtualBox

We will be discussing all of these solutions in our up comming blogs so keep updating and happy sourcing …

i was able to get/ update this must names only if any of you have other names please update me using Comments..

Thanks

How to Uninstall APK Files from Android Device Emulator

In our previous tutorial “How to Install APK Files on Android Device Emulator” we described how to install step-by-step an APK package on the emulator. Today we want to briefly cover how to remove already installed applications.

Note: Google explains that in short here: http://code.google.com/android/intro/installing.html#uninstalling

To perform this operation you would need (how logical) the emulator itself, which is shipped with Android SDK. Once again, you don’t need Eclipse development environment neither for installing and testing of Android applications nor to remove it from the emulator.

Ok, so you have a working SDK with emulator. In the SDK’s main directory (in the last how-to we called it “$SDK_ROOT”) there is the folder called “tools”. You need to start the console terminal (“Start -> Run… -> type ‘cmd'” for Windows PCs). Type-in the following command: adb shell rm data/app/$APK where $APK is the name of the APK file. For example if you want to uninstall the Snake game, you should type this: adb shell rm data/app/Snake.apk

That’s it. Now you can install your Favourite APK again 🙂

How to Install APK Files on Android Device Emulator

In this tutorial we want to explain how to install APK-files to an Android device emulator. Thus you will be able to test already now all new application which will start to appear soon. When the actual Android-powered devices will appear (approximately beginning of 2008), they must be also compatible with already available till then applications.
For the whole experiment you will need two things:
a Windows, Mac OS X (intel) or Linux (i386) powered computer
the Android Software Development Kit (SDK).
You do not need Eclipse or Eclipse-plugin the Android Development Tools (ADT). The last two are required for the software development for Android, but are not necessary for application evaluation on emulator.
At first let’s go and download the Android SDK, which may be obtained here: http://code.google.com/android/download.html
Follow the instruction, described in the topic “Installing SDK” from the Google manual, which is located here: http://code.google.com/android/intro/installing.html#installingsdk
For your convenience we copied the relevant steps here:
-=-=-=-=-=-=-=- Extracted from Google manual -=-=-=-=-=-=-=-
Installing the SDK
After downloading the SDK, unpack the .zip archive to a suitable location on your machine. For the rest of this document, we will refer to the directory where you installed the SDK as $SDK_ROOT.
Optionally, you can add $SDK_ROOT/tools to your path:
On Linux, edit your ~/.bash_profile or ~/.bashrc file. Look for a line that sets the PATH environment variable and add the full path to your $SDK_ROOT/tools to it. If you don’t see a line setting the path, you can add one:
export PATH=${PATH}:
On a Mac, look in your home directory for .bash_profile and proceed as for Linux. You can create the .bash_profile, if you haven’t already set one up on your machine.
On Windows, right click on My Computer, and select Properties. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path under System Variables, and add the full path to the tools/ directory under $SDK_ROOT to it.
Adding $SDK_ROOT/tools to your path lets you run Android Debug Bridge (adb) and the other command line tools without needing to supply the full path to the tools directory. Note that, if you update your SDK, you should remember to update your PATH settings to point to the new location, if different.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=–=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Now navigate to the $SDK_ROOT/tools directory and execute the file ’emulator.exe’. This is the Android emulator itself. Wait couple of minutes until it loads. Now you must see the home screen of Android – wallpapers with snowy mountains on the background and the navigation bar below.
Enjoyed? Ok! Let’s continue. Download and save locally a APK-file which you want to install/evaluate on the emulator. We recommend to save the APK file directly in the $SDK_ROOT/tools directory.
Note: APK probably stands for “Android package”. It’s an application distribution unit in the Android environment. If you are coming from the Windows Mobile world, think of APK as of CAB-files.
Ok, now start the console (“Start -> Run… -> type ‘cmd'” for Windows computers). Type-in the following command: adb install $APK where $APK is the name of the APK file. For example: adb install Snake.apk
If you receive a “path not found” error, then you probably either didn’t add path to the $SDK_ROOT/tools directory to your system PATH settings or the application you are trying to install is not in the $SDK_ROOT/tools directory.
If all went without errors then you should be seeing your newly installed APK on the emulator.

Enjoy Android!

%d bloggers like this: