CrossOver Support - Community Forums

Hi,

I'm trying to run CalMAN (namely version CalMAN v3.5.2) through Crossover. The program seems to install just fine, but when I try to start the application, its icon only quickly flashes in the dock and it fails to start. However, I do not get any sort of error messages. How could I try to figure out why it fails to start? What could be done to make it work?

Thanks

Some general tips for running unsupported apps can be found here:

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

If you're handy with reading error logs, you'll find an installation log inside

Library/Application Support/Crossover/bottles/[bottlename]/drive_c/windows/temp

However, the 'bounces on dock and then disappears' error is typically indicative of missing components required by the application's launcher. There's usually not much that can be done for unsupported apps in these situations, I'm afraid.

Hi,

I will have a peek at the demo of this (in linux) sometime today
when I get a spare moment or two...

Cheers!

Hi,

Test of the version 3.6 demo of CalMAN ;

Requires the installation of microsoft MDAC modern package into same bottle.

[show-stopper]==> Requires .NET 3.0 or better (I believe the 3.6 demo was
expecting to find .NET 3.5 or .NET 3.5 SP1) -- exactly which .NET your copy
of CalMAN v3.5.2 is expecting is hard to say ; in crossover, maximum supported
.NET version is 2.0 SP1 -- I believe it requires .NET 3.0+ -- you might try
installing .NET 2.0 / 2.0 SP1 just to check but it may not help...

Cheers!

Thank you for your replies Jack and Don!

Don, I tried installing microsoft MDAC first, then I installed CalMAN into the same bottle (winxp). After that I tried to launch CalMAN to see if anything goes differently, but it did not. Then I went on to install .NET 2.0 SP1 into the same bottle. Unfortunately it did not help either. CalMAN still fails to start. Obviously it would require a newer version of the .NET.

Does anybody know whether newer versions of .NET will be supported any time soon?

Hi,

I don't exactly know what the situation is with .NET 3.0 - Caron
posted the following observation around a month ago...quote;

"The last I checked, .Net 3.5 was around six months to a year away
(and that was about two months ago). It is moving higher on our
priority list and I have assigned this ticket to the bug to further
push that priority."

I don't know for sure, but I imagine .NET 3.0 is on round-about
the same schedule.

@Jack -- do you know the exact answer here?

CHeers!

I searched this site and found out that .NET 3.0 and 3.5 are awarded bronze medals.
Nevertheless, I wasn't able to install either of them. The installation just jams. However,
it was written on the forum under Microsoft .NET Framework 3.0 (Thread: .Net 3.0 = silver?)
that someone was able to get 3.5 Compact to install. I tried it, and the installation seemed
to work. Installing .NET 3.5 Compact didn't help with CalMAN though. I guess it must be
because, contary to how it seems to go, it doesn't get installed successfully. Or then the
Compact version is just not enough or 3.5 is not new enough after all for CalMAN.

Too bad if .NET 3.0 and 3.5 won't be supported for a while.

Don, do you have any experience with .NET 3.5 Compact? Should it work?

justin case wrote:

I searched this site and found out that .NET 3.0 and 3.5 are awarded
bronze medals.
Nevertheless, I wasn't able to install either of them. The
installation just jams. However,
it was written on the forum under Microsoft .NET Framework 3.0
(Thread: .Net 3.0 = silver?)
that someone was able to get 3.5 Compact to install. I tried it, and
the installation seemed
to work. Installing .NET 3.5 Compact didn't help with CalMAN though.
I guess it must be
because, contary to how it seems to go, it doesn't get installed
successfully. Or then the
Compact version is just not enough or 3.5 is not new enough after
all for CalMAN.

Too bad if .NET 3.0 and 3.5 won't be supported for a while.

Don, do you have any experience with .NET 3.5 Compact? Should it
work?

Not that I know of, but then no...I haven't tried it myself. I have seen a
couple of threads around about .NET 3.5 Compact helping things to get running,
but nobody's saying it actually works (same can be said for .NET 3.0 in wine
installed via winetricks - although it installs fine and sometimes enables a
program to move on, it is known .NET 3.0 isn't working properly)....I believe
once .NET 3.0 -is- running properly under crossover/wine, a lot of pain will be
eased in many app/game situations...

Cheers!

I tried installing .NET 3.5 Compact into the same bottle with CalMAN but it did not help.
However, in the meanwhile I got the following link from the makers of CalMAN.
Software requirements for CalMAN are stated at http://www.spectracal.com/requirements.html

According to the page, CalMAN would only need .NET Framework 2.0 but, in addition,
DirectX 9.0c or DirectX 10 as well.

Nevertheless, after installing .NET Framework 2.0 SP1, DirectX 9.0c and CalMAN into
the same bottle, CalMAN still fails to start (it bounces on the Dock and the disappears).

Does the abovesaid need for DirectX give you any new ideas why CalMAN doesn't run?
What else would it require then?

I tried reading the logg but unfortunately I am too unfamiliar with wine to understand
it adequately.

Hi Justin,

Hmm....I see the requirements list USB 1.1/2.0 ...what immediately
springs to mind there, is the software is trying to use ActiveX in
some way, which reaches fairly deep into windowsOS and a lot of the
time requires a 'real' running windows kernel to work...which of
course, we don't have in wine ;)

If you can somehow ascertain whether or not this is the case (perhaps
email CalMAN support?), it would be the very next thing in my list ;
a lot of the time, ActiveX is a bit of a show-stopper in wine...

Cheers!

@ Don: the timeline for more complete .NET 3.0 support is, at this point, ideally inside of a year, but I don't think it will be 6 months from the point that Caron quoted.

@ Justin: if you could capture a log of the program failing to launch and then email it into to info@codeweavers.com, it may point to the exact spot in the code that's failing. To generate such a log, go to Program>Run Command, select the CalMAN bottle, browse to the launcher .exe for the program, and then under "debug options" set "create a log file", and check "+seh" and "+tid". Click on "run", specify the save location for the log, and then "save". This will launch CalMAN (which will presumably immediately crash). Send in that log file with a note that it should be directed to Jack, and a link to this forum thread. Thanks!

Thanks for your suggestions. It would be very kind of you Jack if you could view the log file. Maybe I could contact the makers of CalMAN after the log, hopefully, has revealed what the exact problem is.

Jack, I did as you adviced me to. I got the following result. "The command ... returned 255." StdOut: nothing, StdErr: nothing, and a log file of 4 kB was formed. I hope "255" is not a sign of an error. Anyway the log file does contain readable information. I will send it as you requested.

Thanks!