CrossOver Support - Community Forums

After about 12 hours of multiple reinstalls (about 3 hours per install) to get latest demo crossover onto a fully patch current model snow leopard macbook pro, I can run quicken, if I plan ahead.

The caveats:
-Takes 20 minutes or so to initialize bottle each time it is started
-20 mins to launch quicken from run command
-Won't save link to program in the program menu (I did define a place for it)
-10/15 mins between click to open of task man and config tools in crossover
-20 min shutdown when done crossover

It is snappy and fast while running quicken, and once the crossover tools are open they work fine too.

The big problem during my install was an old version of X11 from a PPC Tiger machine was on my machine. I removed old x11, and removed all of Crossover and pref files after than first install, put the snow leopard x11 and latest combo updater before reinstall.

When it is stalled during the waiting, no resources are being used, its just like a timeout is waiting to elapse. Z is mapped correctly. There doesn't look to be any mapping to missing USB thumb drives. Hmm, what else, don't know but not usable right now.

Don't get the impression it is supposed to be like this.

There is something very wrong, that is for sure. Running a PPC version X11 under Rosetta (the PPC->Intel translation engine) may explain why it's very slow. I'm really curious how you were even able to install the PPC version of X11 at all. I can tell you that even on a first generation Mac Mini (1.67 ghz Core Duo) with Snow Leopard that even large things like MS Office (more than one component running at a time) run almost as fast as they do on a windows box. I'd make sure that you've removed completely the PPC X11 and download the most current version from Apple. Also, what kind of Mac is this? (I'm wondering if this is a real Mac or a hackintosh, since I've heard of issues with hackintoshes running slow with X11).

Its a current model Macbook Pro.
Migrate tool brought the X11 app over from my tiger PPC machine. I never knew it was there until poking around for why crossover wouldn't work. Its why during the first install a missing X11 flag wasn't thrown.
I never got the first install with the old X11 to run, would just lock and have to force quit repeatedly. 2nd install was a dud too, I had clicked install IE during the quicken install. I left it for 5 hours and it didn't do anything, force quit, uninstall everything.
The quicken app is very fast once it starts, just takes over 30 mins to get it to start each time I need it.
I removed X11 by dragging the app out and searching for pref files. The snow leopard x11 app runs fine as far as I can tell.

I can't help you with a solution, but I can assure you that the performance you are seeing is very wrong. I use Quicken a lot; I start it from the dock and it takes about 20 seconds to get to the password screen, including loading CrossOver. I didn't do anything special with it when installing, since it was the first time I'd used CrossOver at all.

Good luck with finding a solution.

I wonder if there is a log file I can look at to see what is hanging during the process?

There is, this might vary a bit--I'm recalling this from memory on a Linux setup..but it should give you a good start. Open the CrossOver application by it's self (found in Applications) and select from the menu "run windows command" select the bottle quicken is installed in and then select the quicken binary. You should also be able to select logging there and a file to save it to. I'd avoid selecting too many options to start with then run the app and the close it once it starts. Then look at the log. Good luck.

My log file contains a few lines more than these errors but the forum notes say to truncate:

err:process:__wine_kernel_init boot event wait timed out
fixme:exec:SHELL_execute flags ignored: 0x00000100
fixme:ole:TLB_ReadTypeLib Header type magic 0x00905a4d not supported.
err:ole:TLB_ReadTypeLib Loading of typelib L"C:\Program Files\Quicken\QWUTIL.dll" failed with error 0
err:ole:TLB_ReadTypeLib Loading of typelib L"C:\Program Files\Quicken\QWUTIL.tlb" failed with error 2

I don't have any file called QWUTIL in that folder so it must just be a mistake in the quicken install script. I'm guessing its the first error causing all my problems.

See this post, seems you might need an additional package, msls31.

http://www.codeweavers.com/support/tickets/browse/?ticket_id=753363

That package is incompatible with my bottle. I read the link and they don't seem to have the same problem. Crossover itself is what is terribly slow, any of the functions from initializing to control panel settings for a bottle take forever to launch, then run fine once they do. Just like quicken, takes forever to launch, then runs fine.

All right, this sounds exactly like your problem!

http://www.codeweavers.com/support/tickets/browse/?ticket_id=801945

Close but not exactly, and all my drive mappings are there. Went through that post before I asked for help. An hour on google got me no where.

Another update, when launching the bottle config app within bottle manager, one and sometimes two wineloader processes take up 97-99% of my CPU within activity monitor for the 3-5 minutes while waiting for it to launch.

Something's very wrong here...when you do the above, do you see anything in console.app about it?

Ok I rebooted my Mac, started Crossover and checked the console. Only error messages related to crossover are:

10-11-25 8:59:02 PM [0x0-0x151151].com.codeweavers.CrossOver[2728] locate_gui.sh:error: $HOME must be set correctly and be writable for --scope private
10-11-25 8:59:02 PM [0x0-0x151151].com.codeweavers.CrossOver[2728] locate_gui.sh:error: try 'locate_gui.sh --help' for more information
10-11-25 8:59:02 PM [0x0-0x151151].com.codeweavers.CrossOver[2728] Use of uninitialized value in string eq at /Applications/CrossOver.app/Contents/SharedSupport/CrossOver/lib/perl/CXMenuShortcut.pm line 12.

It said it put in all the shortcuts for links to the programs but they aren't in the bottle manager program list.

Nothing of note re WINE entries

Around the same time the following errors popped up:
10-11-25 9:00:19 PM com.apple.WindowServer[63] Thu Nov 25 21:00:19 xxxxxxxxxxxxx-MacBook-Pro.local WindowServer[63] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
10-11-25 9:00:26 PM com.apple.launchd.peruser.502[100] (com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
10-11-25 9:00:34 PM com.apple.launchd.peruser.502[100] (com.apple.Kerberos.renew.plist[121]) Exited with exit code: 1

I removed and reinstalled Crossover. When dragging the icon to install, console threw a dozen or so similar messages like this:

10-11-25 10:07:58 PM diskimages-helper[538] Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin: dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:
/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/VirtualPCDiskImagePlugin: mach-o, but wrong architecture

Always talking about wrong architecture.

Ok have solved all the console errors during install. I had VirtualPC on my Tiger install for a brief time 6 years ago, it left a library after uninstall that was moved by the migration assistant to my new Snowleopard machine.

The error took me to this apple thread http://discussions.apple.com/thread.jspa?threadID=1428784 which pointed me to the file to remove.

I'll update later how this affects my install.

Hum, I'm going go out on a limb and say you replaced a PPC machine and that you migrated your data with a lot of left-over PPC binaries. Virtual PC is a PPC only app, and that plus the PPC X11, I'm thinking that the only thing that may fix this, is a clean install with a selective migration of data. What did you use to migrate your data? CarbonCopy? TimeMachine? Manual copy?

Yup, as stated used Apple migration assistant. I had spent a lot of time deleting PPC apps right after the migration. It moved all the apps over. Clean reinstall isn't gonna happen, I'm just reinstalling Crossover now to see if that one library was the problem.

Well, 3 hours more wasted, fresh install, no improvement. I think I'm done with this software. I don't have time to refresh my snow leopard install, reinstall everything and try again with a chance of the same result.

truaxd wrote:

Hum, I'm going go out on a limb and say you replaced a PPC machine
and that you migrated your data with a lot of left-over PPC
binaries. Virtual PC is a PPC only app, and that plus the PPC X11,
I'm thinking that the only thing that may fix this, is a clean
install with a selective migration of data. What did you use to
migrate your data? CarbonCopy? TimeMachine? Manual copy?

I'd need agree - going by the error messages, other stuff I've read around
the place, it seems like the OS update amd/or app migration is totally
bonkers...if it were me and I had the option, blow it all away and total
reinstall....migrate needed data back into the working construct later...

Cheers!

Mac wrote:

Well, 3 hours more wasted, fresh install, no improvement. I think
I'm done with this software. I don't have time to refresh my snow
leopard install, reinstall everything and try again with a chance of
the same result.

I understand, I'd never be able to do a clean install on my wife's machine for instance, it would be days worth of work. At this point I would recommend opening a formal ticket, even if you are using a demo version. The support team may have seen something like this before and might be able to help. Just don't expect a response until Monday since most of the support team is enjoying the long holiday weekend in the USA. Good luck!

I have a couple of ideas:

1) Migration Assistant has a weird habit of creating your home folder such that your user account is not its owner. Instead, it is owned by root and permissions are set to give your user account complete access permissions. Ordinarily, this would be fine for most software, but it can sometimes cause grief for CrossOver, which digs into the low-level details of things more than most software.

To check, try:
ls -ld@e ~
To fix, try:
sudo chown -R <username> ~<username>
For example, for me it would be:
sudo chown -R ken ~ken

2) Likewise, you may own your home folder, but your user account may not have write permissions to it. Instead, your user account may be a member of a group, and the group has write permissions to your home folder. That too would be revealed by the above "ls" command.

The fix for this would be:
chmod -R u+w ~

3) For some reason, the HOME environment variable is not being set, or is being unset, or is being set to something other than your home folder. Unfortunately, it's no good using Terminal to check this, because a command shell has its environment created in a completely different way than a GUI app launched from the Finder or Dock.

The most likely culprit in this case would be ~/.MacOSX/environment.plist. That file, if it exists, contains key-value pairs that get translated into environment variables for your login session. Some third-party programs may edit this file in an inappropriate manner, leaving environment variables busted. Check for that file and make sure it doesn't define HOME.

If none of the above help, please do open a support ticket by replying to the email you should have received after downloading the trial (or email info@codeweavers.com if you no longer have that email).

That has helped solve most of the problems, my ownership of home was not setup right.

Your tips one and two have solved it completely! 5 secs to launch, links saving correctly, apps within manager are launching in time with their progress bar!

Thank-you very much! Now I get to try this this out finally. I followed up and there is a bunch of ghost group ownerships from migrating from tiger in my permissions. Its part of the migration assistant apparently.

I'm glad that helped. Sorry for the earlier inconvenience.