CrossOver Support - Community Forums

My church uses "ChurchWindows" to manage membership and finances. I'd like to run it at home to try out features, but I have a Mac.

I tried installing it under CrossOver Professional (10.1.1) and got a message"

"Church Windows requires that your computer is running with atleast(sic) 512 MB of virtual memory"

That doesn't make much sense. I have lots more physical memory than that.

I'm running MacOS 10.6.8. Could 64-bit mode be a problem?

I tried to find some kind of CrossOver option for this, but couldn't find anything.

Anyone have suggestions?

Hi,

...possibly -- although the error message differs slightly, the issue -might-
be the same as what I outlay in the thread below ;

http://www.codeweavers.com/compatibility/browse/name/?app_id=8879;forum=1;msg=104632

... just follow those instructions, replacing bottlename where appropriate.
Do however be warned, such is considered to be a bit of a 'gruesome hack',
in as much as in my experimentation, the registry key invocation actually
breaks things, and once in place you cannot install anything else into the
bottle. For example, with the above game, I had to install it once, apply
the registry key to get it to start. to then discover it needed directx
(which wouldn't install ;), so, delete that bottle and create a new one,
install the game & directx then apply the registry key as the last step...

...it may be, your app will be subject to the same scenario...ie; only
after you get it to start, do you discover it needs corefonts or something
else... OR ... you might have to do this a few times to identify what other
runtime dependencies are required (if any) before the program proper starts.
Usually win32 apps check memory requirements fairly early on in the piece,
and so you have to clear that hurdle before you find out what else it needs...

..hope that helps - let us know how you get on =)

Cheers!

Well, thanks for the suggestion, but no joy.

Here's what I did. The first time I tried to install, it created a bottle, but the install failed with the "virtual memory" error. That left the bottle, but nothing installed.

So I tried your procedure to install "virtualmemory.reg" in that bottle, then tried to install again. No luck. Same error.

I wasn't completely convinced that that virtualmemory.reg went anywhere. Should I have seen it on the list?

Do I need to create the bottle first and populate it with some basic items first before installing the software from CD? I suspect it will be a long process figuring out which items are needed.

...ahh, ok, that info changes the picture a little ; it's the
actual -installer- failing, not so much the app software itself,
correct? If so, I've misconstrued your situation slightly...

...you would need to ascertain a couple of things ; firstly, when
installing from cd, sometimes it's better not to pick the disc
itself, but rather, take the 'choose an installer' option, and
navigate to the actual software's installer/setup exe (if it exists),
and running that instead. If you don't do this, the 'autorun.inf'
file on the disc will be executed, and it may be that process causing
the problem...

..ummm.....the other possibility, one supposes, is that there could be
disc based DRM (copy protection) incorporated into the disc release,
in which case you might be sunk...

..easiest way to check that (and worth doing anyhow), is copying the
entire disc contents from the cd into a directory somewhere, and running
the setup program from there ; definitely worth a shot...

..also, in the 'runtime support components' area of the cxinstaller GUI.
you will see the windows installer 2.0 package - some installers need that
pre-installer into a bottle, before the app's installer will actually run...

...try these things, keep us posted...

Cheers!

Still no luck. I copied the disk to a folder and installed from the setup.exec. I got the same result.

I tried both with the bottle that was created the first time, and with a new winxp bottle.

CrossOver said there was a debug log, but it's Greek to me.

Oh, yeah. I also tried the "windows installer 2.0" thing. It said it was only compatible with a Win98 bottle, and the application insists on at least Win2000.

...okay, if nothing else, it's being consistent ;) ... umm..

..have a read of the following documentation.. ;

http://www.codeweavers.com/support/wiki/mac/mactutorial/submittechsupportlog

...we've tried most of the easy stuff, and it appears you've
isolated setup.exe as being the exe hoisting the error -- create
a new bottle, and then follow the procedures outlined above,
to run setup.exe directly (rather than taking the normal install
route). You will see in the debuglog GUI, a stringbox titled 'Other:'
and in this area enter...

+trace,+loaddll

...and generate the logfile as per the instructions. Once you have
said debuglog, upload it to some public repo (pastebin, rapidshare,
google..) and post back the URL for same and I'll have a look at
what's going on -- it may be a fruitless venture, but it never hurts
to look ...

Cheers!

OK, tried that. I ran the setup.exe from the CD, as a command.

For what it's worth, the final dialog box said:

The command "/Volumes/CW 14.10/Install/setup.exe" returned 67.

Command error text:

***** Sat Oct 22 12:10:26 2011
Starting: '/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/bin/cxavscan' '/Volumes/CW 14.10/Install/setup.exe'

CXConfig->read(/Applications/CrossOver.app/Contents/SharedSupport/CrossOver/etc/CrossOver.conf)
Found no anti-virus tool

The log should be here.

...thanks, but I'm afraid the news is not good...

trace:seh:raise_exception code=c0000005 flags=0 addr=0x432953dd ip=432953dd tid=001c
trace:seh:raise_exception  info[0]=00000001
trace:seh:raise_exception  info[1]=00800000
trace:seh:raise_exception  eax=00000000 ebx=000005e0 ecx=00000000 edx=00000000 esi=00000001 edi=00800000
trace:seh:raise_exception  ebp=0033dc08 esp=0033db80 cs=0017 ds=001f es=001f fs=1007 gs=0037 flags=00010246
trace:seh:call_vectored_handlers calling handler at 0x439fe120 code=c0000005 flags=0
trace:seh:call_vectored_handlers handler at 0x439fe120 returned ffffffff
err:msi:ITERATE_Actions Execution halted, action L"LaunchConditions" returned 1603

...the first 7 lines of that stanza recurs throughout the log, always returning
a bad address, until finally it hits the msi error ... my guess is thread 001c
is some install condition set in the msi installer, which fails and leads to
msi error 1603 -- unfortunately, there is no succinct cause for that error ; it
can be triggered by any number of things,... including wine itself...

... if it were me, the next thing I'd do is try this with wine-1.0.1, as there
was a regression with msi at some stage which I know isn't apparent with that
wine version. It looks like it may require IE7 in the same bottle, and although
I don't see it calling for it, .NET 2.0 (or the lack thereof) can cause this
error as well....

...unfortunately, the authors of this software no longer offer a trial version
(they once did), so I'm afraid you're on your own with this -- you can try the
suggestions above (a new bottle with IE7 & .NET 2.0 installed into it), but I
doubt that'll be the end of it. Checking an older version of wine may be a fight
on the Mac you don't want to get into, but that's the problem when one doesn't
have the software to check themselves =) ...

...if you exhaust all options, possibly the only way the software will run on
your Mac, is via emulation software or booting Windows...

Cheers!

I tried installing IE7 and .Net 2.0. I still get the same error when I run setup.exe. (The failure is after the "simulated reboot.)

Oh, well, thanks for your help. Some things are just too complicated. :)

You can ask to get a "Free Church Windows Working Trial."
http://churchwindows.infosaic16.com/shop/custom.aspx?recid=51

But I'd understand if there's a limit to how far you want to pursue this. It would have been convenient to be able to run the software, but it won't make a huge difference in my life if I can't.

...well, nothing ventured, nothing gained -- I don't mind looking
at problematic apps ; a lot of the time, that limit is not having
the actual software to torment -- in that regard, thanks for the
link, but me thinks they might have issues shipping it to where I
am in .AU ; we'll see what happens when whoever sees my entry =)

.AU as in Oz? Maybe I'll bring you a copy next summer. Well, June to be less ambiguous. :)