To run Toolbox on Mac, use a Windows emulator. Toolbox for Mac has been customized to make it act more like a Mac application when it is run under an emulator.
This is the best that can be done for Mac at this time. Years of programmer time have gone into multiple attempts to make a native Mac version of Toolbox, but none of them have come to completion.
For an Intel Mac, there are several Windows emulators available. The least expensive emulators use Linux Wine.
WineBottler is free and does not require a Windows license. It is downloadable from WineBottler. It runs on Mac operating sysems 10.5 and later.
CrossOverMac is another Wine based emulator. It is not free, but it has some support. CrossOverMac is available from CodeWeavers.
Other emulators run a full version of Windows on the Mac. Parallels Desktop or VMWare Fusion are two of that type. The other emulators cost significantly more, plus they require a Windows license, which is not needed for Wine based emulators.
The Wine based emulators have a problem with the display looking wrong if Windows rendering is used. So there is a ToolboxMacWine.exe program that solves the Wine display problem. If you need Windows rendering, you should run the ToolboxMac.exe program and an emulator that runs a full version of Windows.
Do not try to use the Windows Toolbox installer under an emulator. Instead, use the Toolbox package for Mac.
To install Toolbox for Mac, place the Toolbox for Mac package zip file in your Applications folder and double click it to expand it. The result will be a folder named Toolbox. Inside the folder you will see a file named Toolbox.exe, which is the file that will be run by the emulator.
To install Toolbox under WineBottler, install and run WineBottler. Select the file Toolbox.exe as the file to install. Turn on the check box option for "Copy only". If you are using a non-Roman script or any font that requires Windows rendering, then scroll down the list of files to "usp10" and turn on its check box. If you don't know whether you need it, it won't hurt to include this in the install. Click on "Install". Enter a name such as "Toolbox" in the "Save As" box. Navigate the "Where" location to your Applications folder. It will take some time. When it is done, it will say "Prefix created successfully". The result will be an app named Toolbox in your Applications folder. It will have a red Toolbox icon.
To run Toolbox, double click the Toolbox icon. The first time you run it, you will see messages saying it is being prepared to run, but after the first time, it will run very quickly. Toolbox will give a message saying "You must specify the full pathname of the project file". Click OK and Toolbox will run, but with no project open. Choose Project, Open and navigate to the .prj file of your Toobox project. Click Open and your project should open. Under WineBottler Toolbox cannot remember the last project you had open, so you will have to do Project, Open every time you run Toolbox. To save having to do that, you may want to leave Toolbox running with your project open all the time. It regularly saves everything, so it is no harm to keep it running continuously.
The Toolbox package for Mac contains an upgraded version of Toolbox which has been modified to make it more usable on the Mac under Windows emulators. One change is that all of the Ctrl+click combinations have been changed to Shift+click. On emulators Ctrl+click is used for right click. So this change eliminates the conflict between the two different uses of Ctrl+click. Another change is to change Exit on the file menu to Quit, and to give it the standard Mac shortcut key of Command+Q. A number of Command shortcut keys have been changed to become Mac standard shortcuts, or to avoid conflicts with Mac standard shortcuts. The shortcuts are all shown on Toolbox menus, so you can see the details there.On Windows, Toolbox uses right click for jumps. On Mac some emulators can be set to make Cmd+click do right click. But on some, like WineBottler, that doesn't seem to work. The best alternative is to use the Cmd+J shortcut for jump. One difference is that right click jumps from the location of the mouse pointer, whereas Cmd+J jumps from the location of the insertion point cursor. So you have to click in the word you want to jump from to put the insertion point in it and then do Cmd+J to jump.
In spite of our efforts to make Toolbox act like a standard Mac program, there are a number of ways in which it has a different look and feel. The most obvious is that the Toolbox menu is not on the top of the screen. The emulator menu may be up there, and the Toolbox menu is in smaller print at the top of the Toolbox window. Another difference is that scroll bars do not look like Mac. A general difference is that in Toolbox all the subwindows are inside a large, general window, rather than being separate windows on the desktop.
One thing to be aware of is that the outer Toolbox window can have scroll bars. If you drag an inner window past the edge of the outer window, a scroll bar will appear on the edge of the outer window. To get rid of those scroll bars, scroll to the far left and top, and drag all windows left and up until they don't overlap the right or bottom edge.
If you bring in a project from another machine, you may find that the outer window is taller than your screen. If you can't see the lower right corner, you can't drag it. One way to overcome this problem is to click the green spot on the upper left corner of the main window. This will bring the window fully onto your screen. If you then close Toolbox and open it again, both choices of the green spot will fit on your screen.
One key combination you may need to learn is that Function+delete does forward delete. Forward delete is necessary to join two interlinear line sets into one if you want to adjust the line breaks of interlinear text by hand. You may also sometimes need to use the Function key to get function keys and to get home, end, page up and page down.
One limitation of using a Windows emulator is that Mac native non-Roman keyboards do not work. The way to work around that is to use a Toolbox internal keyboard for special keys. See Keyboard Definitions in the help file for information on how to do this.
Another limitation is that Mac native rendering for non-Roman scripts does not work. This means that some of the non-Roman fonts provided with the Mac do not render correctly.