CrossOver Support - Community Forums

Now here's the first thing I am doing. I'm trying to install Tarot Commercial Edition on my Mac.

I get this error after registering the software.

Any ideas if this is happening because of the software itself or CrossOver?

When I click ok, the window just closes. So if I was to download this file from somewhere.. where would I put it, or how else can I get this to work?

Hi,

Have a read of the following thread - it gives you some idea
of what you'll need to do to get around that error;

http://www.winehq.org/pipermail/wine-users/2009-October/062186.html

It's probably impossible for anyone to check the app directly, as
it's related to registration -- if there were a demo available that
also required registration, it'd be easier to look at...

Cheers!

This is what I got from Matrix.

[b]Errors Involving VSOCX:
Rename the Vsocx32.ocx file that is in your C:\Windows\System32 folder to Vsocx32.old

If you are running a 64bit version of Windows you need to go to
c:\windows\syswow64 instead.

Click on the link below to download the new file.
http://astrologysoftware.com/download/tech/VSOCX.exe

Save it to your desktop and then run it from there. It will automatically install the file for you in the right system folder.

Once the install is complete reboot your computer and try the program again.[/b]

I was able to install the program but the error persists.

Don, there is a demo download, Tarot Demo Download

I tried

1. Copy pasing the vsocx.ocx into the winxp bottle
2. Installing Active X software into the bottle.

Nothing. Same error. Matrix support says that till date Tarot Commercial has never run on a Windows Simulator.

Can anyone think of ANYTHING at all that may work?

Did you register vsocx.ocx? Did you install odbc (mdac) as the thread suggested?

Duplicate post, sorry.

I installed the exe into the bottle. No registration was asked for..

I used your command in the Run line.. this is the error message.

[i]The command regsvr32 VSOCX32.OCX returned 1.

StdOut: Failed to load DLL VSOCX32.OCX

StdErr:[/i]

And this on the terminal:

[i]static-70:drive_c Ishani$ regsvr32 VSOCX32.OCX
Failed to load DLL VSOCX32.OCX[/i]

Also since this is my first attempt at CrossOver, would like to thank you for your patience in advance and ask if I need to install anything else... because all that in that thread about Winetricks was a little.. Hebrew to me.

I'm trying something. Seeing this software uses IE style browsing, let me install IE into the bottle.

Not happening. If you can tell me a way past that "Failed to load dll" message, I shall be grateful.

Ok installed everything, reinstalled program, SAME error.

Grrr.... I am going to the corner to sulk, see you if I EVER come out of there.

...I should've been a bit clearer about winetricks...

Winetricks uses abbreviated target names, but most (not
all) targets have equivalents in Crossover - for example,
the command 'winetricks vcrun2005' is equivalent to
installing the Microsoft Visual C++ 2005 Redistributable
package from within the 'Runtime Support Components'
area of the cxinstaller GUI, the other targets will be
fairly self-obvious to a 'windows power user'...

...oh, mfc40.dll may be the exception there ; it's provided
by the c4p profile available from the vcrun2003 C4 page;

http://www.codeweavers.com/compatibility/browse/name/?app_id=8036

Never use/look for 'winetricks gecko' ; this is 'cxhtml engine'
to us, but there a couple of ways of presenting that. We also have
4 distinct targets for IE -- IE 6, IE 7 & mshtml6 , mshtml 7 ;
they are all different and provide different levels of functionality.
If you look at the 'Libraries' tab in the Wine Configuration GUI
(also check for an app profile entry in the Applications tab first),
you can see which related -native- win32 dlls are being used, and
any others where we are using the wine builtin versions instead.
Again, if you know windows really well, you'll know what dll does
which function...blablabla...I won't bother detailing it ;)

...if the app absolutely needs dcom98, you should probably be
using a win98 bottle profile ; if that were the case, IE6 instead
of IE7...etc and so forth ; you're basically trying to recreate
the windows environment as the win32 app expects to find it...

...windows error messages can be, for the most part, about as
useful as ashtrays on a motorbike - as we're not an emulator
and therefore not running any 'real' windows kernel, it's fairly
easy to provoke a win32 error message that has nothing to do with
the actual problem...ie; the windows error of 'cannot load some.dll'
might be disclosed in Crossover debuglogs as 'cannot load some.dll
because someother.dll on which it depends cannot be found'...or
such and similar -- if some win32 doesn't run 'out of the box',
the quickest way to find out why (and perhaps what is needed), is
via running the app with debugging turned on...see;

http://www.codeweavers.com/support/wiki/SubmitTechSupportLog

One can use those instruction to create debuglogs, and examine same
to determine what's going on - not all the available debug channels
are presented in checkbox fashion, hence the 'Other:' stringbox
widget. You can enter one (or more) debug channels here to look at
specific areas of interest...a more complete list of the available
debug channels is over at winehq...see;

http://wiki.winehq.org/DebugChannels?action=show&redirect=winedebug

If you know windows well, it's fairly self apparent what channels
you want to be looking at. Going through the resultant logfiles may
appear arduous at first, but, if you know what you're looking for,
it's fairly easy to grep the lines you're after...ie; debug output
lines starting with 'warn:' or 'err:' are going to be of immediate
interest. As exampled in the thread I linked to, some many times the
'missing pieces' as it were, are not identified by plaintext filename,
instead they will be identified by windows registry CLSID/GUID significs,
which I probably don't need to explain to you either <grin>...typically
my first debug pass uses +seh,+trace,+ntdll,+loaddll or such ; that
gives me a pretty good first glance at the 'lay of the land' as it were.

Hope this helps...

Cheers!

Tried again.

Created new WinVista Bottle. Copied vsocx.ocx into C drive. Installed IE7. Installed MDAC update with OLE support. Then when I tried to install Tarot all went well, but screen froze at this point.

What else do you think may be needed?

Edit: Don I just saw your post, will go try everything there too! :) And thank you for being so awesome.

Hmm, I had asked the people who made Tarot Commercial for help, and they say they had tried to get the software to work with Wine but the programmers gave up there was just too much missing for the software to work.
The issues I am having now are the same issues they were having three years ago.

So I guess, against what I would like to do, I'll give up on this one, and rate it "Known not to work". :(