logobossparts

• How To Use Crossover On Chromebook

User modeWhen installed as a single user, the CrossOver environment will be set up forone account only. Only that user will be able to install and use Windowsapplications.If you are installing CrossOver on a personal computer for private use, youshould use this installation mode. It is the easiest, simplest, and safestinstallation method.File locations.The CrossOver application will be installed in /cxoffice. Windows applications andconfiguration files will be placed in /.cxoffice.How to install.Log in as the user who will be using CrossOver and locate the installationscript.

It will usually be called install-crossover-18.0.0.bin but mayhave a different name, especially if you downloaded it. Once you have foundthe installer, run it as follows:$ sh install-crossover-18.0.0.bin. Shared modeShared mode allows you to install CrossOver so that each user on the systemcan install and run the Windows software of his or her choosing.

Each userwill have their own set of private.If you are installing CrossOver for use by multiple users, you should use thisinstallation mode. New users are easy to add, and corrupt or unwantedWindows environments can be easily erased or replaced.File locations.The CrossOver application will be installed in /opt/cxoffice. Each user's bottles will beplaced in /.cxoffice.How to install.Log in as root and locate the installation script.

It will usually be calledinstall-crossover-18.0.0.bin but may have a different name. Once youhave found the installer, run it as follows:# sh install-crossover-18.0.0.binOnce the installation completes, click Exit. Now,when a user runs CrossOver for the first time they will be able to installWindows software using the Windows software installation wizard.

Contents.1 Introduction 1.1 Overview / About 1.1.1 Purpose of this document and intended audienceThis document, called the Wine User Guide, is both an easy installation guide and an extensive reference guide. This guide is for both the new Wine user and the experienced Wine user, offering full step-by-step installation and configuration instructions, as well as featuring extensive reference material by documenting all configuration features and support areas.1.1.2 Further questions and commentsIf, after examining this guide, the, and other relevant documentation there is still something you cannot figure out, we would love to hear from you. The section contains several mailing lists and an IRC channel, all of which are great places to seek help and offer suggestions. If you are particularly savvy, and believe that something can be explained better, you can file a or yourself.1.1.3 Content overview / Steps to takeIn order to be able to use Wine, you must first have a working installation. This guide will help you to move your system from an empty, Wineless void to one boasting a fresh, up to date Wine install. The first step, illustrates the various methods of getting Wine's files onto your computer. The second step, shows how to customize a Wine installation depending on your individual needs.

The final step, covers the specific steps you can take to get a particular application to run better under Wine, and provides useful links in case you need further help.1.1.4 Quick startThe process of installing and running Wine can be summarized as follows:.Get a distribution as indicated in and see the page. For the casual or new user the simplest is to get a packaged version for your distribution.Optionally configure Wine using the command. Wine should work without any additional configuration options.To test your installation run the Wine notepad clone using the wine notepad command.Check the Wine for specific instructions or steps required to install or run your application.Run Wine using the command.The first command you will run will be to install an application. Typically something like wine /media/cdrom/setup.exe or the equivalent path might be used to install an application from CD.1.2 What is Wine? 1.2.1 Windows and LinuxDifferent software programs are designed for different operating systems, and most won't work on systems that they weren't designed for. Windows programs, for example, won't run in Linux because they contain instructions that the system can't understand until they're translated by the Windows environment.

How To Use Crossover On Chromebook

Linux programs, likewise, won't run under the Windows operating system because Windows is unable to interpret all of their instructions.This situation presents a fundamental problem for anyone who wants to run software for both Windows and Linux. A common solution to this problem is to install both operating systems on the same computer, known as “dual booting”. When a Windows program is needed, the user boots the machine into Windows to run it; when a Linux program is then needed, the user then reboots the machine into Linux.

This option presents great difficulty: not only must the user endure the frustration of frequent rebooting, but programs for both platforms can't be run simultaneously. Having Windows on a system also creates an added burden: the software is expensive, requires a separate disk partition, and is unable to read most filesystem formats, making the sharing of data between operating systems difficult.1.2.2 What is Wine, and how can it help me?Wine makes it possible to run Windows programs alongside any Unix-like operating system, particularly Linux. At its heart, Wine is an implementation of the Windows Application Programing Interface (API) library, acting as a bridge between the Windows program and Linux. Think of Wine as a compatibility layer, when a Windows program tries to perform a function that Linux doesn't normally understand, Wine will translate that program's instruction into one supported by the system. For example, if a program asks the system to create a Windows pushbutton or text-edit field, Wine will convert that instruction into its Linux equivalent in the form of a command to the window manager using the standard X11 protocol.If you have access to the Windows program source code, Wine can also be used to recompile a program into a format that Linux can understand more easily. Wine is still needed to launch the program in its recompiled form, however there are many advantages to compiling a Windows program natively within Linux.

For more information, see the Winelib User Guide.1.2.3 Wine featuresThroughout the course of its development, Wine has continually grown in the features it carries and the programs it can run. # make uninstallThis command will require root privileges, and should remove all of the Wine files from your system. # ln -s libodbc.so.1.0.0 /usr/lib/libodbc.so # /sbin/ldconfigThe last step in configuring this is to ensure that Wine is set up to run the built-in version of odbc32.dll, by modifying the DLL configuration. This built-in DLL merely acts as a stub between the calling code and the Unix ODBC library.If you have any problems then you can use WINEDEBUG=+odbc32 command before running Wine to trace what is happening. One word of warning: some programs actually cheat a little and bypass the ODBC library.

For example the Crystal Reports engine goes to the registry to check on the DSN. The fix for this is documented at unixODBC site where there is a section on using unixODBC with Wine.4.3.6.2 Using Windows ODBC driversNative ODBC drivers have been reported to work for many types of databases including MSSQL and Oracle. In fact, some like MSSQL can only be accessed on Linux through a Winelib app. Rather than just copying DLL files, most ODBC drivers require a Windows-based installer to run to properly configure things such as registry keys.In order to set up MSSQL support you will first need to download and run the mdactyp.exe installer from Microsoft. In order to configure your ODBC connections you must then run CLICONFG.EXE and ODBCAD32.EXE under Wine. You can find them in the windowssystem directory after mdactyp runs.

Compare the output of these programs with the output on a native Windows machine. Some things, such as protocols, may be missing because they rely on being installed along with the operating system.

If so, you may be able to copy missing functionality from an existing Windows installation as well as any registry values required. A native Windows installation configured to be used by Wine should work the same way it did when run natively.Types successfully tested under Wine:DB TypeUsefulnessMS SQL100%Please report any other successes to the mailing list.5 Troubleshooting / Reporting bugs 5.1 What to do if some program still doesn't work?There are times when you've been trying everything, you even killed a cat at full moon and ate it with rotten garlic and foul fish while doing the Devil's Dance, yet nothing helped to make some damn program work on some Wine version. Don't despair, we're here to help you. (in other words: how much do you want to pay?)5.1.1 Verify your Wine configurationLook at the output from wine -version to make sure you're running a recent version of Wine. Launch winecfg and look over the settings to make sure you have settings that look normal. Look in /.wine/dosdevices to make sure your c: points to where you think it should.5.1.2 Use different Windows version settingsIn several cases can help.5.1.3 Use different startup pathsThe following sometimes helps, too:. wine x:fullpathtoprg.exe.

wine /.wine/drivec/full/path/to/prg.exe. cd /.wine/drivec/full/path/to/ && wine prg.exe5.1.4 Fiddle with DLL configurationRun with WINEDEBUG=+loaddll to figure out which DLLs are being used, and whether they're being loaded as native or built-in.

Then make sure you have proper native DLL files in your configured C:windowssystem32 directory and fiddle with DLL load order settings at command line or with winecfg.5.1.5 Check your system environment!Just an idea: could it be that your Wine build/execution environment is broken? Make sure that there are no problems whatsoever with the packages that Wine depends on (gcc, glibc, X libraries, OpenGL (!).)5.1.6 Use different GUI (Window Manager) modesInstruct Wine via winecfg to use either desktop mode, or normal managed mode. That can make a lot of difference, too.5.1.7 Check your app!Maybe your app is using some kind of copy protection? Many copy protections currently don't work on Wine.

Some might work in the future, though. (the CD-ROM layer isn't really full-featured yet).5.1.8 Reconfigure WineSometimes Wine installation process changes and new versions of Wine account on these changes.

This is especially true if your setup was created long time ago. Rename your existing /.wine directory for backup purposes. Use the setup process that's recommended for your Wine distribution to create new configuration.

Use information in old /.wine directory as a reference. Later you can remove the new /.wine directory and rename your old one back.5.1.9 Check out further informationThere is a really good chance that someone has already tried to do the same thing as you. You may find the following resources helpful:. Search to check for any tips relating to the program. If your specific version of the program isn't listed you may find a different one contains enough information to help you out. can be useful depending on how you use it.

hosts an IRC channel for Wine. You can access it by using any IRC client such as HexChat.

The settings you'll need are: server, irc.freenode.net, port, 6667, channel, #winehq. If you have a program that requires a redistributable runtime to be installed, e.g. For mfc42.dll, Visual Basic and so on, can be used to supply this. Note, these components are subject to their own license and are not part of the Wine project. The WineHQ or may also help. The wine-devel mailing list may be appropriate depending on the type of problem you are experiencing.

If you post to wine-devel you should be prepared to do a little work to help diagnose the problem. Read the section below to find out how to debug the source of your problem. If all else fails, you may wish to investigate commercial versions of Wine to see if your application is supported.5.1.10 Debug it!Finding the source of your problem is the next step to take. There is a wide spectrum of possible problems ranging from simple configurations issues to completely unimplemented functionality in Wine. The next section will describe how to file a bug report and how to begin debugging a crash. For more information on using Wine debugging facilities be sure to read the.5.2 How To Report A BugSee.6 Glossary BinaryA file which is in machine executable, compiled form: hex data (as opposed to a source code file).

DistributionA distribution is usually the way in which some “vendor” ships operating system CDs (usually mentioned in the context of Linux). A Linux environment can be shipped in lots of different configurations: e.g. Distributions could be built to be suitable for games, scientific applications, server operation, desktop systems, etc. DLLA DLL (Dynamic Link Library) is a file that can be loaded and executed by programs dynamically. Basically it's an external code repository for programs. Since usually several different programs reuse the same DLL instead of having that code in their own file, this dramatically reduces required storage space. A synonym for a DLL would be “library”.

EditorAn editor is usually a program to create or modify text files. There are various graphical and text mode editors available on Linux.Examples of graphical editors are: nedit, gedit, kedit, xemacs, gxedit.Examples of text mode editors are: joe, ae, emacs, vim, vi. In a terminal, simply run them via: $ editorname filename Environment variableEnvironment variables are text definitions used in a Shell to store important system settings.

In a bash shell (the most commonly used one in Linux), you can view all environment variables by executing: setIf you want to change an environment variable, you could run: export MYVARIABLE=mycontentFor deleting an environment variable, use: unset MYVARIABLE GitGit is a fast version control system, originally written for use with large repositories, such as the Linux Kernel source. See the Git chapter in the Wine Developers Guide for detailed usage information. PackageA package is a compressed file in a distribution specific format. It contains the files for a particular program you want to install. Packages are usually installed via the dpkg or rpm package managers. Rootroot is the account name of the system administrator.

In order to run programs as root, simply open a Terminal window, then run. #prompt, whereas '$' indicates a normal user account. ShellA shell is a tool to enable users to interact with the system. Usually shells are text based and command line oriented. Examples of popular shells include bash, tcsh and ksh. Wine assumes that for Wine installation tasks, you use bash, since this is the most popular shell on Linux.

Shells are usually run in a Terminal window. Source codeSource code is the code that a program consists of before the program is being compiled, i.e. It's the original building instructions of a program that tell a compiler what the program should look like once it's been compiled to a Binary.

TerminalA terminal window is usually a graphical window that one uses to execute a Shell. If Wine asks you to open a terminal, then you usually need to click on an icon on your desktop that usually shows a big black window. Wine assumes you're using the bash shell, so if your terminal happens to use a different shell program, simply type bash in the terminal window.