PowerPC application (Microsoft Word for Mac 2004) running on OS X for Intel in Rosetta | |
Developer(s) | Apple Inc. |
---|---|
Operating system | Mac OS X 10.4.4–10.6.8 (Intel) macOS Big Sur 11.0–present (ARM) |
Type | PowerPCbinary translation (original version) Intel binary translation (Rosetta 2) |
Website | www.apple.com/asia/rosetta/ |
Rosetta is a dynamic binary translator developed by Apple Inc. for macOS, an application compatibility layer between different CPU architectures. It gives developers and consumers a transition period in which to update their application software to run on newer hardware.
Many default installations of Mac and Linux do not come with a compiler installer, so you will need to install one separately. (Note that the following only applies if you have administrator rights to your machine. If you do not, talk to your sysadmin regarding the installation of a compiler.) Rosetta requires a compiler with C11 support. Download Rosetta Stone TOTALe - (Mac 10.6.8) Download Rosetta Stone Language Learning - (Mac 10.7 or higher) Installation Steps: Once downloaded, double click the update.exe to begin the installation. Installation steps: Once downloaded, double click the Rosetta Stone.dmg. Then double click the Rosetta Stone.pkg to begin installation.
The first version of Rosetta, introduced in 2006, allows PowerPC applications to run on Intel-based Macs. The second version, introduced in 2020, is a component of macOS Big Sur to aid in the Mac transition to Apple Silicon from Intel processors.[1] The name 'Rosetta' is a reference to the Rosetta Stone, the artifact which enabled translation of Egyptian hieroglyphs.[2]
Rosetta[edit]
Mac transition to Intel processors |
---|
Apple released the first version of Rosetta in 2006 when it changed the instruction set architecture of the Macintoshplatform from the PowerPC to the Intel processor. It was initially included with Mac OS X v10.4.4 'Tiger', the version that was released with the first Intel-based Macs, and allows many PowerPC applications to run on certain Intel-based Mac computers without modification. Rosetta is based on QuickTransit technology.[3] It has no graphical user interface, which led Apple to describe Rosetta as 'the most amazing software you'll never see'.[4] Rosetta is not installed by default in Mac OS X v10.6 'Snow Leopard', but can be retained as an option via the installer or Apple Software Update.[5] Rosetta is neither included nor supported in Mac OS X v10.7 'Lion' or later, which therefore cannot run PowerPC applications.[5]
Rosetta translates G3, G4, and AltiVec instructions, but not G5 instructions. Although most commercial software for PowerPC-based Macs were compatible with these requirements, any applications that relied on G5-specific instruction sets had to be modified by their developers to work on Rosetta-supported Intel-based Macs. Apple advised that applications with heavy user interaction but low computational needs (such as word processors) would be best suited to Rosetta, while applications with high computational needs (such as AutoCAD, games, or Adobe Photoshop) would not.[6]
Rosetta also does not support the following:[7]
- The Classic environment, and thus any non-Carbon application built for Mac OS 9 or earlier
- Code that inserts preferences into the System Preferences pane
- Applications that require precise exception handling
- Screen savers
- Kernel extensions and applications that depend on them
- Bundled Java applications or Java applications with JNI libraries that cannot be translated
- Java applets in Rosetta-translated applications, meaning that a native Intel web browser application, rather than a legacy PowerPC version, must be used to load Java applets
The reason for Rosetta's reduced compatibility compared to Apple's earlier 68k emulator for PPCs lies within its implementation. Rosetta is a user-level program and can only intercept and emulate user-level code. By contrast, the 68k emulator accesses the very lowest levels of the OS by being at the same level as, and tightly connected to, the Mac OS nanokernel on PPC Macs, which means that the nanokernel is able to intercept PowerPC interrupts, translate them to 68k interrupts (then doing a mixed mode switch, if necessary), and then execute 68k code to handle the interrupts. This allows lines of 68k and PPC code to be interspersed within the same fat binary.
Rosetta 2[edit]
Mac transition to Apple Silicon |
---|
Rosetta 2 is included as of macOS Big Sur to aid in the Mac transition to Apple Silicon from Intel processors.[1][8] In addition to the just-in-time (JIT) translation support available in Rosetta, Rosetta 2 includes support for translating an application at installation time.[9]
See also[edit]
- Universal binary – combined PPC/Intel applications that run natively on both processors
- Fat binary § Apple's fat binary – combined PPC/68k application that ran on older Macintoshes
References[edit]
- ^ abWarren, Tom (June 22, 2020). 'Apple is switching Macs to its own processors starting later this year'. The Verge. Retrieved June 22, 2020.
- ^Core Duo iMacs debut speedy new chipsArchived March 3, 2012, at the Wayback Machine
- ^'The brains behind Apple's Rosetta: Transitive'. CNET News.com. June 8, 2005. Archived from the original on July 14, 2014. Retrieved July 4, 2007.
- ^'Rosetta'. Apple. Archived from the original on November 16, 2010. Retrieved September 5, 2011.
- ^ abAppleInsider Staff (February 26, 2011). 'Mac OS X Lion drops Front Row, Java runtime, Rosetta'. AppleInsider. AppleInsider, Inc. Archived from the original on April 29, 2014. Retrieved February 27, 2011.
- ^'Rosetta'(PDF). Universal Binary Programming Guidelines, Second Edition. Apple. Archived from the original(PDF) on August 3, 2012. Retrieved September 5, 2011.
- ^'What Can Be Translated?'(PDF). Universal Binary Programming Guidelines, Second Edition. Apple. Archived from the original(PDF) on August 3, 2012. Retrieved September 5, 2011.
- ^Mayo, Benjamin (June 22, 2020). 'Apple announces Mac architecture transition from Intel to its own ARM chips, offers emulation path'. 9to5Mac. Retrieved June 23, 2020.
- ^WWDC2020 Keynote. Apple Inc. June 22, 2020. Event occurs at 1h39m37s.
It translates the apps when you install them, so they can launch immediately and can be instantly responsive. And Rosetta 2 can also translate code on the fly when needed.
External links[edit]
- Apple Rosetta Web site at the Wayback Machine (archived January 7, 2011)
- Transitive Corporation web site at the Wayback Machine (archived September 14, 2008)
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Rosetta_(software)&oldid=980887467'
- 1Microsoft Windows
- 3Linux
- 3.1064 Bit Considerations
Microsoft Windows
Download the installer,then double-click the installer icon.
Install options
You can set install options by clicking the 'Advanced' button on the configuration screen.The options are:
- Program directory - where BOINC's program files will be stored.
- Data directory - where BOINC's data files will be stored. This will be a hidden directory; its location is shown in the BOINC start up messages.
- Use BOINC screensaver - Use the BOINC screensaver for the current user.
- Service install - Run project applications under an unprivileged account. This provides increased protection against faulty applications, but it prevents BOINC from using your GPU, and it may cause graphics to not work with older applications.
- Allow all users on this computer to control BOINC - If selected (public mode), all users can control BOINC (attach/detach projects, etc.). If not selected (private mode), the only users who can control BOINC are: the installing user, members of the Administrator group, and members of the 'boinc_users' group. When other users run the BOINC Manager, they'll be shown a dialog saying to contact the administrator to add them to the 'boinc_users' group.
Running BOINC invisibly
To run BOINC invisibly, choose the 'Service install' option,then delete the BOINC shortcut from the Start/Programs/BOINC and Start/Programs/Startup menus(locate BOINC in each menu, right-click, select Delete).You can still run the BOINC Manager by going to C:Program FilesBOINCand double-clicking on boincmgr.exe
Error recovery
If you get an error error 1714 - the old installation can't be removed when installing a new version of BOINC:
- Reinstall the previous version.
- Uninstall the previous version.
- Install the new version again.
Mac OS X
- Download the installer.
- If your browser has not already done so, expand the zip archive by double-clicking on it in the Finder.
- Double-click on the BOINC Installer application to run the installer, then follow the prompts.
- Close the installer when it is finished. This will automatically launch the BOINC Manager.
- If you want BOINC to be your screen saver, open System Preferences from the Apple menu. Select Desktop & Screen Saver and select BOINCSaver.
- The default location for data directory of BOINC is
/Library/Application Support/BOINC Data
. You may want to exclude this folder from Time Machine backup system to prevent increase of backup data size.
Several tools for Mac OS X are available to:
- Automatically run BOINC as a daemon or system service at boot time.
- Improve security for stand-alone clients.
- Prevent BOINC Manager from launching automatically when selected users log in.
Linux
The recommended way to install the BOINC client on Linux is to use the package management system of your Linux distribution. If the BOINC client does not exist for your distribution, please open an issue in github. Note that there are two packages, one for the BOINC Client and another for the BOINC Manager, which can be installed separately. Only the client is required but it is likely that the manager is wanted as well unless the client is to be managed from a remote host.
Debian
Open a terminal and enter the following command:
sudo apt-get install boinc-client boinc-manager
Ubuntu
Use the software centre to install the BOINC manager or following instructions for Debian.
Fedora
Open a terminal and enter the following command:
sudo dnf install boinc-manager
Redhat/CentOS
To Ensure that the EPEL repository is enabled, open a terminal and enter the following command:
Open a terminal and enter the following command:
sudo yum install boinc-client boinc-manager
Hint: When detection of GPUs and VirtualBox doesn't work, disable SELinux. See https://linuxize.com/post/how-to-disable-selinux-on-centos-8/ for more info on that.
Building from Source
The source code for BOINC can be obtained from the github repository. This can be done with the following command:
wget https://github.com/BOINC/boinc/archive/master.zip
It can the be built with the following commands
Alternatively a specific version (gitbranch and gittag) can be downloaded with the following command:
wget https://github.com/BOINC/boinc/archive/${gitbranch}/boinc-client-${gittag}.tar.gz
Running BOINC using Docker
A Docker image containing the BOINC client can be downloaded from here:https://hub.docker.com/r/boinc/client/
You can run this image using Docker on any 64-bit Intel computer (Linux, FreeBSD, Mac, or Windows).
The image contains only the client.You can control it using a BOINC GUI running locally or remotely.
Using a bootable image
You can download a bootable image containing Linux and the BOINC client,write it to a USB stick, and boot from it.Currently one such image is available:PADOLF@home is based on Debian.It includes the 7.8.3 BOINC client and GUI, and has recent video drivers for AMD and Nvidia GPU support.Note: this is provided by volunteers, not by BOINC.
The Berkeley Installer
The Berkeley installer is available directly from the BOINC project.It is a self-extracting archive.This type of installation requires that you be familiar with the UNIX command-line interface.The download files have names like
boinc_7.2.23_i686-pc-linux-gnu.sh
.Here is an example.The archive is downloaded to the desktop.It is then moved to the home directory (~).Finally BOINC is unpacked and installed.All of this can be done within a regular user account; root privileges are not needed.
This creates a directory called BOINC/ under the home directory containing the following files:
- boinc
- The BOINC core client.
- boincmgr
- The BOINC Manager.
- boinccmd
- A command line tool for controlling a running core client.
- run_client
- A script that cd's into the BOINC directory and runs the core client.
- run_manager
- A script that cd's into the BOINC directory and runs the manager.
![Mac Mac](/uploads/1/1/7/8/117836604/316709095.jpg)
To start the client manually enter the following terminal commands:
![Stone Stone](/uploads/1/1/7/8/117836604/824844897.png)
The BOINC working directory can be moved elsewhere as you like, and can even be renamed.One common choice is ~/.boinc,since files and directories with names that begin with 'dot' do not show up by default in Unix directory listings.Whatever the name, everything related to the BOINC client is contained within that directory,and you should always run the client and the manager from that working directory.
Build BOINC from source
You can build the BOINC client from source.Keep in mind that BOINC consists of both client and server software.To run BOINC on your computer you only need to build the client software.
Instructions for building BOINC from source are in a separate developer's wiki.Start with these pages:
There is additional documentation on other web sites:
- Installing and Running the BOINC client on Unix (from Spy Hill) - how to install and configure the client once you have built it
64 Bit Considerations
If you are running 64 bit Linux, you might have a problemwith projects that issue 32 bit applications rather than 64 bit applications.To allow 32 bit applications to run on 64 bit Linux you must install 32 bit versions of certain shared libraries.The names of the packages containing the 32 bit libraries is different for each distro.
N.B. The commands given below are executed in a terminal window. To open, hit the key combination Ctrl+Alt+T. The sudo commands could ask for a password [yours] to temporarily give admin installation rights for the needed libraries. [Default], closing the terminal or leave the terminal idle for 15 minutes will revoke these rights again.
Fedora
Three packages are required for 64 bit compatibility.
Name | Description |
---|---|
compat-libstdc++-296.i686 | Compatibility 2.96-RH standard C++ libraries |
compat-libstdc++-33.i686 | Compatibility standard C++ libraries |
compat-libstdc++-33.x86_64 | Compatibility standard C++ libraries |
Install all 3 packages at once, by opening a terminal and typing:
Ubuntu
Four packages are required for 64 bit compatibility (Read whole section before applying).
Name | Description |
---|---|
ia32-libs | description is unavailable |
libstdc++6 | description is unavailable |
libstdc++5 | description is unavailable |
freeglut3 | description is unavailable |
Install all 4 packages at once with the following steps:
- Open a terminal.
- Enter (with a space between every library name, or copy the line as-is, and right-click in terminal to paste)
If the above fails to get 32 bit work on e.g. World Community Grid or to at all install, these sets work on newer Linuxes [those in italic are optional]
or alternate for Test4Theory:
The changes will not take effect until the client/daemon has been restarted. This too can be done in terminal, e.g. on Ubuntu with
The ClimatePrediction.net (CPDN) project only has 32bit applications, so they require 32bit compatibility libraries.
For Debian Stretch and Buster, the following command should work to ensure 32 bit compatibility with cpdn apps:
For 64bit Ubuntu 19.10, the following command should work to ensure 32 bit compatibility with cpdn apps:
For 64bit Ubuntu 18.04 and 19.04, the following command should work to ensure 32bit compatibility with cpdn apps:
Rosetta Installer Mac Download Softonic
For Redhat/CentOS/SciLinux 6, the following command should work to ensure 32 bit compatibility with cpdn apps:
For Redhat/CentOS/SciLinux 7, the following command should work to ensure 32 bit compatibility with cpdn apps:
FreeBSD
- go to /usr/ports/net/boinc-client/, open the Makefile in a text editor
- change the
CONFIGURE_ARGS=--disable-server
as follows:- on 32 bit FreeBSD change it to
CONFIGURE_ARGS=--disable-server --with-boinc-platform=i686-pc-freebsd --with-boinc-alt-platform=i686-pc-linux-gnu
- on 64 bit FreeBSD change it to
CONFIGURE_ARGS=--disable-server --with-boinc-platform=x86_64-pc-freebsd --with-boinc-alt-platform=i686-pc-linux-gnu
- on 32 bit FreeBSD change it to
- do make install clean
- if you receive an error like 'ELF 0 ....', make sure you have installed
- /usr/ports/emulators/linux_base-fc4 or higher
- sysctl kern.elf32.fallback_brand=3
How To Download Rosetta Stone
There is additional information on installing, configuring and running BOINC on FreeBSD.
Retrieved from 'https://boinc.berkeley.edu/w/?title=Installing_BOINC&oldid=6406'