Что такое расширение файла MAC

WineBottler 1.7.52

by |

WineBottler 1.7.52 is a major update which sports some thrilling new features.

Runs on OS X El Capitan

Probably the most important feature is the update to run on OS X El Capitan. In Apples proven one-two-combination, after the visual fixes in OS X Yosemite, we could expect a major cleanup in OS X El Capitan. Apple did this with security on its mind, so the proverb “There is the Easy Way and Then There is the Right Way” smacked the lazy dev in the face, once again.

First, Apple got rid of LD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH. Forcing us to “otool -L” and “install_name_tool -change” thru all the bins and libs of Wine to use proper @rpath relative paths for all Wine related libraries. The result is, of course, a correct linking through out the app — thank you Apple. I guess somebody has to kick you once a while to come up with proper solutions.

Then Apple implemented App Transport Security which forces us to use secure connections for interactions between Apps and web services – or to disable it. For now it is disabled in WineBottler, but I’m working hard on offering SSL connections to get this right. After all it is all about security and privacy.

Further there where some GUI/multithreading glitches (Toolbar and FilePicker dialog) that lead to crashes on El Capitan and the new requirements that have been sorted out.

Saves up to 92% harddrive-space

Yep, this one sounds to good to be true… right? But here we go:
A clean Wine prefix weights in about 35mb. But Wine requires big add ons like gecko (for Webservices, 50mb) and mono (for .net Apps, 200mb) by default. They might not be needed by your app, but blow up an empty prefix up to 300mb. These two add ons can now be excluded: down 84%.

Further we added an option, to remove the “c:\users” directory when shipping an app. Wine will automatically add new users, when the app is run on a clients Mac.
Then you can automatically remove installer files (.msi) from your prefix before shipping – if they are no longer needed.

Lastly, we have optimized how WineBottler runs your prefixes. To this point, WineBottler will copy a prefix from the App to the folder ~/Application Support. This approach allows us to install Apps to restricted System folders, or Codesign them, without breaking the signature or having to give read and write access to the app, since the App works in the users Applications Support folder. We stick to that design, but we no longer copy, but link the files to ~/Application Support. Changes files will break the link and replace it with the new file. Unchanged files will only take up some bites, instead of a complete copy, saving nearly 50% of disk-space. THIS FEATURE IS STILL VERY NEW AND IN TESTING! So I’m more than happy to hear from you.

Thank you very much!

Listening to Dabu Fantastic playing on MusicBee 2.5 on WineBottler on OS X El Capitan.

As usual: head over to winebottler.kronenberg.org and grab your copy .




Метод 1

С помощью программы WINE

  1. 1

    Откройте сайт WineBottler.

    Имейте в виду, что некоторые программы не работают с WINE. Если EXE-файл не запускается в WINE, воспользуйтесь эмулятором Boot Camp (читайте следующий раздел).

    Его адрес: . У WINE богатый функционал, но WineBottler включает интерфейс, который облегчает использование программы.

  2. 2

    Нажмите «WineBottler 1.8-rc4 Development».

    Если вы работаете с системой, выпущенной до версии OS X Capitan, нажмите кнопку «WineBottler 1.6.1 Stable».

    Эта кнопка отобразится посередине экрана; на ней вы найдете значок в виде зеленой стрелки.

  3. 3

    Когда появится запрос, нажмите Download (Скачать). Откроется окно с рекламой.

  4. 4

    Нажмимте SKIP AD (Пропустить рекламу). Эта ссылка отобразится в правом верхнем углу экрана через пять секунд.

    • Не щелкайте по окну с рекламой. Дождитесь, когда появится кнопка SKIP AD (Пропустить рекламу).
    • Если вы пользуетесь блокировщиком рекламных объявлений, заранее отключите его.
  5. 5

    Дождитесь, когда WineBottler будет загружен. Если процесс скачивания WineBottler не запустится в течение пяти секунд, нажмите «WineBottlerCombo_1.8-rc4.dmg».

  6. 6

    Установите WineBottler. Для этого дважды щелкните по установочному файлу WineBottler, а затем перетащите значки «Wine» и «WineBottler» в синюю папку «Программы».

  7. 7

    Дважды щелкните по EXE-файлу. Откроется выпадающее меню.

  8. 8

    В меню выберите Open with (Открыть с помощью). Эта опция находится в верхней части меню.

  9. 9

    Нажмите Wine. Вы найдете эту опцию во всплывающем окне слева или справа от выпадающего меню. Откроется окно с предупреждением.

  10. 10

    Удостоверьтесь, что возле опции «Run directly in» (Запустить в) стоит флажок. Если это не так, щелкните по значку в виде круга слева от опции «Запустить в ».

  11. 11

    Нажмите Go (Запустить).

    Если EXE-файл не запускается с помощью WINE, воспользуйтесь следующим методом.

    Это голубая кнопка, которая находится в нижнем правом углу окна с предупреждением. Если EXE-файл поддерживается WINE, он будет запущен.

Метод 2

С помощью эмулятора Boot Camp

  1. 1

    Найдите (скачайте, купите) установочный файл Windows. Эмулятор Boot Camp поддерживает Windows 8/8.1/10.

    Установочный образ (ISO-файл) Windows можно скачать с сайта компании Microsoft.

  2. 2

    На компьютере под управлением Mac OS X откройте папку «Утилиты». Для этого щелкните по значку в виде лупы в верхнем правом углу экрана, в строке поиска введите «Утилиты» (без кавычек), а затем щелкните по папке «Утилиты».

  3. 3

    Дважды щелкните по значку Boot Camp. Он похож на серый значок жесткого диска.

  4. 4

    Следуйте инструкциям на экране.

    Если вы устанавливаете Windows с USB-накопителя, вам будет предложено вставить его во время описанного процесса.

    Выберите установочный файл Windows и диск, на который будет установлена система Windows. Затем перезагрузите компьютер.

  5. 5

    Дождитесь, пока компьютер перезагрузится. Когда вы закончите настраивать Boot Camp, вам будет предложено перезагрузить компьютер. Затем на экране отобразится мастер установки Windows.

  6. 6

    Выберите раздел «BOOTCAMP».

    Если вы устанавливаете Windows с помощью ISO-файл, Boot Camp создаст разделы в автоматическом режиме.

    Сделайте это в том случае, если вы устанавливаете Windows с USB-накопителя.

  7. 7

    Следуйте инструкциям на экране. Процесс зависит от устанавливаемой версии Windows, но когда он будет завершен, компьютер перезагрузится (так же, как при настройке Boot Camp).

  8. 8

    Зажмите клавишу ⌥ Option, когда компьютер перезагрузится. Откроется окно менеджера загрузки.

  9. 9

    Отпустите клавишу ⌥ Option, когда откроется окно менеджера загрузки. В этом окне отобразятся все диски, с которых можно загрузить компьютер.

  10. 10

    Щелкните по значку «Boot Camp», а затем нажмите клавишу ⏎ Return. На компьютере загрузится операционная система Windows.

  11. 11

    Найдите и дважды щелкните по EXE-файлу. Так как загрузилась система Windows, EXE-файлы можно запускать с помощью двойного щелчка по ним.

How to Run Windows Software on a Mac With WineBottler

To get started, download WineBottler. Be sure to download a version that works on your release of Mac OS X. When this article was written, that meant OS X El Capitan and Yosemite users needed to download version 1.8.

Open the downloaded DMG file. Drag and drop both Wine and WineBottler applications to your Applications folder to install them, just like you would any other Mac application. You can then launch WineBottler from your Applications folder.

WineBottler lists a number of different programs you can easily install. For example, you could install various versions of Internet Explorer if you needed to test websites with them on your Mac. The Windows version of Steam is available, and which could allow you to run some Windows-only games on your Mac. Choose any of these options and WineBottler will automatically download, install, and configure these applications for you.

The installed application will appear under “On My Mac” in the WineBottler window. You can uninstall them from here, if you like. Click an application and it will launch in a window, receiving its own icon on your dock.

To run another application that doesn’t appear in the WineBottler list, you can simply download it, then right-click or Ctrl-click its .exe file to select Open With > Wine.

WineBottler allows you to quickly execute the .exe directly, if you like. You can also choose to install the application in a Mac .app file created by WineBottler.

If you choose to convert it to an OS X application bundle, you will be taken to the Advanced screen in WineBottler. Provide the .exe file used to install the application and you can install it as an .app using the options here. Depending on  the application, you may need various third-party libraries from the Winetricks list, DLL override options, or runtime arguments here to make it work.

However, that often isn’t necessary–just executing .exe files directly with Wine should generally work.

If you can’t get an application working, you should perform a web search for its name and “wine” or “winebottler” for tips on what advanced functions you might need.

Bear in mind that WineBottler is best if you have a single program or handful of programs that work well. If you plan on testing out a lot of software or you use software that Wine doesn’t support well, you’ll have a much better time just running it in a virtual machine. These offer more or less guaranteed compatibility with Windows software on a Mac.


  • › Windows 10’s Tablet Mode May Be Replaced With the Desktop
  • › How to Quickly Switch Between Gmail Accounts on Android, iPhone, and iPad
  • › How to Use the chmod Command on Linux
  • › How Writers Can Use GitHub to Store Their Work
  • › How to Easily Recycle the Old Electronics You Can’t Sell

How to Use WineBottler to Launch Windows Programs and Open .exe files on Mac

Wine is an open-source app, so other developers have used its free source code to build more advanced OS X apps for running .exe files. WineBottler is a Wine-based wrapper for adapting games and programs to run natively on Mac OS X El Capitan and Sierra. The emulator has received positive user reviews mainly for its ability to convert Windows apps into .dmg files. The utility’s users can run web browsers like Internet Explorer or Microsoft Office programs on their Mac with Wine-based compatibility layers. If you are a reader, who wonders “Do I need to access third-party libraries or runtime arguments to run .exe files?”, the answer is “Yes”. However, most applications can be executed without a custom digital “opener.” Here’s what needs to be done to setup and use WineBottler on an Apple machine.

The app installation is a fairly straightforward drag and drop procedure. It should be kept in mind, however, that the downloaded disk image consists of two files both of which should be transferred to the Application folder. Once you have installed WineBottler, click on the Create Custom Prefixes tab on the left. Customize the installation by selecting the file you want to install and checking the Self-Contained box. A self-contained app can be executed even on those Macs that do not have WineBottler. Skip the step if you don’t want to run the app on other machines. If a file you want to install is executable, check the Copy Only box. It is also necessary to put a tick in the Silent Install box and click on the Install button. At some point during the installation process, a Windows installer will appear. Then, follow the on-screen instructions. Then, choose the start file and click the OK button. Be careful and select the proper item, which will be opened every time the app is launched. If you fail to specify the correct start file, repeat the installation process. All Windows programs installed on the Mac can be found by clicking on the On My Mac tab.

After following the instructions above, the Windows program can be opened just like any other Apple app. It is also possible to run executable files without installing them on the Mac with the help of WineBottler. To this end, control-click the file and use the Open With option to run it with WineBottler. Then click on the Go button. Note that depending on the type of a program, you may need extra libraries, DLL override options, or runtime arguments to run it. Therefore, if you can’t execute a Windows program, conduct a quick web search using its name as a part of the search query to find out how to make it work.

Bottom Line

There are two main ways of running Windows apps on Mac OS X: using virtual machines or special emulators like WineBottler or Wineskin. The use of emulators is less resource-consuming, which is especially important for those intending to run heavy games on their Mac. However, if you are planning on running multiple apps and not sure whether they are compatible with WineBottler, it is better to stick to virtual machines.

Share this post with friends!

Why Third Party Applications Exist

Users want to run applications and sometimes a change to Wine can cause an application to work, but this change cannot be incorporated into Wine for some reason. For example, the change may break Wine for other applications and/or platforms. As such changes to Wine must meet some level of QA. If the change is a dirty hack to Wine’s source code that allows an application to run, then the change may end up within Wine’s source code only after it has been properly fixed.

In theory, any third party application here is essentially a temporary workaround until underlying bugs in Wine can be fixed properly. As wine improves, parts or all of these third party applications may become obsolete or incompatible with Wine (at least until the third party provides a suitable update).

WineBottler 1.8-rc4

by |

Yep… Wine is turning final to a new stable!

… and so is WineBottler.
After the dust of the major changes in WineBottler 1.7.52 have settled, this one comes only with minor fixes and improvements.
The most important might be the rebinding of the CMD-key. As 80% have voted on having the CMD-key doing the work of the CTRL-key, this feature is on by default, now.
A big thank you flies out to Tobias B. on directing my head to it :).

Looking at a fracture in MERLIN PACS Viewer on WineBottler on OS X El Capitan.

As usual: head over to winebottler.kronenberg.org and grab your copy .


… no, it’s not my shoulder. Txs for asking.

64-bit support with WineBottler 4.0.1

by |

Keep me goinggive me coffee!

We Love Bitcoins



64-bit – Driven by need

With 64-bit only macOS Catalina around the corner and therefore the imminent loss of 32-bit, I had to sort out my toolchain where Wine is still playing a major role.
I therefore rebased my build-environment on macOS High Sierra and XCode 9.4.1. That is the last combination where I can compile both architectures of Wine in one run. As Clang 32-bit is already removed in macOS Mojave. I was able to install the command line tools of XCode 9.4.1 on it, but in the end, I opted for a clean solution. As the already heavy bending of environment variables to build self-contained versions of Wine got to an all-new level with multiple versions of XCode installed :).
But moving up to High Sierra has its price. The new builds will only run on machines with High Sierra or newer. (Let me know if you still need to run WineBottler on older versions of macOS, it might be possible to move one or two incarnations back. Possibly not as far as the now really outdated WineBottler 2.0 or WineBottler 1-8 did. They were still built on OS X 10.6.8 and had a spectacular range of OS versions supported :D).

16-bit, 32-bit and 64-bit

Back to today: The new builds of Wine for WineBottler come as shared WoW64 builds. They feature the 32-bit and the 64-bit Wine. Even 16-bit programs still work with the current setup. Further, the builds do include Mono (which was already bi-arch) and both architectures of Gecko.

WineBottler 4.0.1 64-bit Settings

I did some groundlaying work to include 64-bit support into WineBottlers app-building, already: You can easily select the correct operating-system / architecture combination. But things need to get a little bit smarter still to manage the two possible that are required. I still consider this build preliminary work. Id est I did not test the setup with macOS Catalina, yet. But I plan on moving all my 32-bit Windows-based programs to their 64-bit counterparts anyway, so I\’m not concerned with 32-bit too much.


Finally, we have landed some UI fixes, too. They remove glitches on macOS Mojave, especially in Darkmode. Further, we have addressed missing icons and problems when selecting the exe to be run.

WineBottler 4.0.1 running 16-bit Bang Bang!WineBottler 4.0.1 running 64-bit FireFox

Look out for the new builds at winebottler.kronenberg.org

Cheers Mike

Типы файлов MAC

Ассоциация основного файла MAC


Формат файла: .mac
Тип файла: MacPaint Image

Файл MAC является формат растрового изображения по умолчанию используется MacPaint, приложение картины для операционной системы Mac. MAC файлы поддерживают только черно-белую графику.

Создатель: Apple
Категория файла: Файлы растровых изображений
Ключ реестра: HKEY_CLASSES_ROOT\.mac

Программные обеспечения, открывающие MacPaint Image:

Apple QuickTime Player, разработчик — Apple

Совместимый с:


Corel Presentations X8, разработчик — Corel

Совместимый с:


MacPaint, разработчик — Apple

Совместимый с:


Lemkesoft GraphicConverter, разработчик — Lemkesoft

Совместимый с:


CorelDRAW Graphics Suite, разработчик — Corel

Совместимый с:


Ассоциации других файлов MAC


Формат файла: .mac
Тип файла: Macro Script File

Файл MAC содержит макросы, связанные со многими программного обеспечения, таких как Microsoft Dynamics GP, Minitab, SmartWare и т.д.

Создатель: SmartWare Corporation
Категория файла: Файлы разработчика

Программы, открывающие файлы Macro Script File :

DataFlex, разработчик — Data Access Worldwide

Совместимый с:


Minitab, разработчик — Minitab Inc

Совместимый с:


SmartWare, разработчик — SmartWare Corporation

Совместимый с:



In the past, Wine’s native Mac driver still needed a good deal of work so running Wine on macOS required installing an X11 server too. This is no longer necessary, but there are still some features missing from the Mac driver (see the to-dos on the macOS page) so you still might want to run Wine with the X11 driver.

According to Wikipedia, from v10.3 (Panther) to v10.7 (Lion) of macOS, Apple at least included a Mac-compatible X11 server as an optional install. However, since v10.8 (Mountain Lion), Apple has stopped providing its own release of the X11 server and advises all users to download the newest version of a compatible X11 server directly from upstream.

During setup, the upstream XQuartz disk-image will replace /usr/X11 (which is in most PATH variables) with a symlink to /opt/X11 (where it installs the files). However, if you upgrade your release of macOS, this symlink may get clobbered, leading to fatal errors in X11 programs. Reinstalling XQuartz will repair the link automatically, or you can manually restore it with:

sudo ln -s /opt/X11 /usr/X11

If you have a supplementary package manager, you might also be able to grab XQuartz (or an equivalent port of the vanilla xorg server):

On homebrew, you can grab XQuartz from the related Caskroom repo:

brew install Caskroom/cask/xquartz

On MacPorts, you can get fresh ports of either the xorg-server (stable X11 server), xorg-server-devel (development X11 server), or xorg (full X11 system) packages. For example:

sudo port -v install xorg-server


Once you have Xcode and a version of the X11 server (not required but highly recommended), you need to grab both the build and runtime dependencies for Wine. While you can just run Wine’s configure script and keep installing libraries that it complains are missing, using a package manager will save you a lot of trouble and keep your system cleaner.

The main caveat with the various macOS package repos is that you do not want to mix them. Once you’ve decided to use one, stick with it, and if you decide to switch to a different one, it’s probably best to uninstall all of your old packages first, then reinstall them with the new system.

The subsections below describe ways you can get just the necessary dependencies for Wine. If you want, you can always just install the appropriate wine package, which will pull in all the other packages you need. At that point, you can either uninstall just the wine package, or keep it and run your own build from within its directory.


On MacPorts, to get all the dependencies for Wine, both build and runtime, you just want to use the rdepof: query (short for «recursive depends of») with the install command. Unless you definitely want the stable release of Wine, use the wine-devel package to get the most up-to-date dependency list:

sudo port -v install rdepof:wine-devel +universal

Please Note: If you’re running macOS High Sierra you need to install XCode9 & XCode Command Line Tools 9, not the default versions from the App Store.
If you’re running macOS Mojave it’s not possible for MacPorts to build the required dependancies as the version of XCode’s SDK only includes 64Bit headers so it’s not able to compile 32Bit code without workarounds.

Building from Source

Now with the dependencies installed, you will use almost the same procedure as described on the Building Wine page. You should be able to run ./configure and make with the same parameters as on another system.

Note: In the past on macOS, it was necessary to point to libraries and headers installed through the package managers too. However, recent versions of all the major package managers should either automatically add to your PATH variable or create symlinks into /usr/local.

You can configure your build directory to compile with clang like so:

./configure CC="clang" CXX="clang++" CFLAGS="-std=gnu89 -g"

Please Note: While Wine can be compiled using XCode on macOS (Compiling with XCode10 requires MacOSX10.13.sdk & setting min version to 10.7) , however compiling wine64 will have problems with regedit and other components so its better to cross-compile using Docker (instructions for this will be added later)

Running a Custom Build

When installing Wine from source on macOS, you may need to make some quick configuration changes.

After compiling Wine from source, you can install it into /usr/local with make install, but it’s highly recommended that you run it from the build directory.

Depending on how you installed XQuartz, you might see fatal errors in X11 when you try to run your own build of wine from the command-line. This is due to XQuartz installing into the /opt/X11/ directory and creating symlinks to /usr/X11/, neither of which is typically checked by the macOS dynamic linker. There are a couple of workarounds for this:

The first is to add the usr/X11/lib directory to the DYLD_FALLBACK_LIBRARY_PATH environment variable. You can do this when invoking wine like so:

DYLD_FALLBACK_LIBRARY_PATH="${DYLD_FALLBACK_LIBRARY_PATH}:/usr/lib:/usr/X11/lib" wine program_name.exe

The other method is to create symlinks to the libraries in usr/X11/lib/ from inside /usr/local/lib:

cd /usr/local/lib
sudo ln -s /usr/X11/lib/*

However, this second approach is more tedious to undo and may be more fragile in some situations.

You might need to tweak the actual directories in your list, but you can avoid the tedium of typing the list every time by setting it in one of your shell config files (e.g. .profile, .bash_profile, or .bashrc):


Current Third Party Applications

The applications below should work with the latest Wine and are still being maintained.


The Crossover series of products are a repackaging with added patches to support more applications and added interfaces on top of WineHQ.


DOSBox is an emulator for legacy x86 PCs, which is particularly useful for old MS-DOS programs since they often used hardware in rigid ways (e.g. using CPU clock cycles directly for timing). Wine uses DOSBox for its virtual 8086 mode (for more details, see Wine Wiki’s DOSBox page).


This module allows unix windows managers to generate crisp desktop icons from the icons embedded in Windows executables.


A Python-based GUI tool that provides managing of registry keys for Wine.


Lutris is an open gaming platform for Linux. It helps you install and manage your games in a unified interface. This support includes managing Windows games (run via Wine).


A tool which is aiming on making it easy for the user to install Windows software, like World of Warcraft, Adobe Photoshop, Guild Wars and much more.


A tool made by the same team as PlayOnLinux but for Mac user.


A tool for installing games, applications, and various redistributable runtimes, e.g. mono, dcom98, fonts. Workarounds to Wine bugs are run automatically. (See also the Winetricks page on this wiki.

WineBottler (for Mac OS X)

A tool to install and run pre- or custom configured apps. It comes with precompiled wine and allows to create fully self-contained .app bundles.

Unofficial Wineskin (for Mac OS X)

Create wrappers used to make ports that work like Native macOS applications. Uses Winehq portable releases, bundles all needed dylibs and binarys for use with winetricks, always downloads the current version of winetricks.

PortingKit (for Mac OS X)

Using Wineskin technology, Porting Kit can install games and apps compiled for Microsoft Windows in macOS. It’s free, it’s simple, it’s the Porting Kit.


A Qt GUI for Wine. It will help you manage wine prefixes and installed applications.

WineD3D for Windows

A DirectX 1-11 to OpenGL wrapper based on WineD3D.

How to Download Wine on a Mac

RELATED: 5 Ways to Run Windows Software on a Mac

There are several ways to get Wine on a Mac. The official project website at WineHQ now provides official builds of Wine for Mac OS X. However, those aren’t necessarily the best option. These Wine binaries allow you to run Windows software, but don’t provide any helpful graphical tools for installing and setting up common applications, so they’re best for advanced users already familiar with Wine.

Instead, you should probably consider one of the third-party projects that take the Wine source code and build a more convenient interface on top of it, one that helps you quickly install and configure common applications. They often perform tweaks that you’d have to perform by hand if you were using the barebones Wine software. They include their own Wine software, too, so you only have to download one thing.

Third-party tools include WineBottler, PlayOnMac, and Wineskin. There’s also the free Porting Kit, which makes installing classic games easy, and the commercial CrossOver Mac, which is the only application here you have to pay for. We’ll be using WineBottler for this tutorial, as it seems like the most popular option among Mac users. It can create Mac .app bundles for Windows programs. The other third-party applications will work similarly, though some (like CrossOver and Porting Kit) may be much more streamlined for the apps they actually support—so if you’re looking to run a specific game, it may be worth checking to see if the other apps support that game for easy setup.

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *