Fora

Trouble installing CC3+ from ProFantasy

Stuck on installer attempting to install VS C++ 2017

Autor Odpowiedzi
Azhrei Sunday 29 November 2020 at 8:42
AzhreiAnonymous

Hey all.

First, thanks for working on this project!  I'm excited to get a 32-bit Windows app running on macOS Catalina (64-bit only OS).  The Crossover app appears to be capable of this, but the WineHQ folks say their solution is terrible and won't be rolled into WineHQ (although they will produce their own solution, probably in Wine 6.0).

Anyway, this means I need to find a way to do this using PlayOnLinux/PlayOnMac.  I have POM installed and running on my MacBook pro (8-core Intel, 32GB of RAM) but the installer for CC3+ craps out with an error:

CC3+ Installer error message

Being the industrious person I am (!), I grabbed the VC_redist.x86.exe from Microsoft in order to install the redistributable files separately, thinking that maybe this installer would then skip the attempt to install the runtime DLLs itself and thus progress to the next step.  However, this also fails, but differently.  Here is the contents of the playonlinux.log file:

% tail -f playonlinux.log 

[11/29/20 02:36:50] - Running wine- /Users/franke/Downloads/ProFantasy CC3+/VC_redist.x86.exe (Working directory : /)

tee -a "$WINEPREFIX/playonlinux.log"

++ tee -a /Users/franke/Library/PlayOnMac//wineprefix/ProFantasy/playonlinux.log

001d:err:plugplay:process_IOService_Device object 0x15403

001d:err:plugplay:process_IOService_Device object 0xad07

001d:err:plugplay:process_IOService_Device object 0x15107

001d:err:plugplay:process_IOService_Device object 0x15007

001d:err:plugplay:process_IOService_Device object 0x14d07

001d:err:plugplay:process_IOService_Device object 0xb207

001d:err:plugplay:process_IOService_Device object 0xb507

001d:err:plugplay:process_IOService_Device object 0x14a07

001d:err:plugplay:process_IOService_Device object 0xb907

001d:err:plugplay:process_IOService_Device object 0xbb07

001d:err:plugplay:process_IOService_Device object 0xbd07

001d:err:plugplay:process_IOService_Device object 0xbf07

001d:err:plugplay:process_IOService_Device object 0x14507

001d:err:plugplay:process_IOService_Device object 0x14307

001d:err:plugplay:process_IOService_Device object 0x14107

001d:err:plugplay:process_IOService_Device object 0xc307

001d:err:plugplay:process_IOService_Device object 0x13d07

001d:err:plugplay:process_IOService_Device object 0xc707

001d:err:plugplay:process_IOService_Device object 0xca07

001d:err:plugplay:process_IOService_Device object 0x13a07

001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x13a0b

001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x13a0f

001d:err:plugplay:process_IOService_Device object 0x1380f

001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x13813

001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x13817

001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0x1381b

001d:err:plugplay:process_IOService_Device object 0xce13

001d:err:plugplay:process_IOService_Device Unable to create plug in interface for USB deviceobject 0xce17

001d:err:plugplay:process_IOService_Device object 0x1370b

001d:err:plugplay:process_IOService_Device object 0xd103

001d:err:plugplay:process_IOService_Device object 0xd203

001d:err:plugplay:process_IOService_Device object 0x13303

001d:err:plugplay:process_IOService_Device object 0x13203

0009:fixme:heap:RtlSetHeapInformation 0x0 1 0x0 0 stub

This program tried to use a DOMDocument object, but

libxml2 support was not present at compile time.

0009:fixme:ole:CoCreateInstanceEx no instance created for interface {2933bf81-7b36-11d2-b20e-00c04f983e60} of class {f6d90f11-9c73-11d3-b32e-00c04f990bb4}, hres is 0x80004001

0009:fixme:ver:GetCurrentPackageId (0x33fd04 0x0): stub

 
At this point, I'm stumped.  I tried modifying the bash/manual_install and lib/wine.lib scripts to add some debugging output, but my commands don't even appear to be executed.  I am a bit concerned that the value of "$PWD" appears to be "/", since trying to write there would obviously cause permission issues, but since my debugging statements appear to be ineffective...  I don't know what the next step is.
 
Please help me, Obiwan Kenobi.  You're my only hope. ????
Azhrei Monday 30 November 2020 at 4:49
AzhreiAnonymous

I may have solved this myself.

I found a bunch of guides written by booman which describe the libraries that he needed to install in order to make a variety of different games work properly.  So I took the common ones that appeared in many of the guides (these guides are circa 2012-2014!) and told POM that I wanted to install some extra libraries while doing the Manual Installation.

Unfortunately, corefontsdxfullsetup, msxml6, and vcrun2019 weren't enough.  (The first two are from the guides, and the last one is because of the error message in the OP).  That was discouraging, but I read that many games don't consider some of their requirements to really be requirements because any common Windows system nowadays is already going to have them.  So I went back and turned on anything that I thought might be relevant:  dotnet480 (the most recent right now), both mfc40 and mfc42, all of the msvc* pieces, all of the msxml* pieces, both tahoma installers, and all of the vcrun* installers.

I'm sure that was tremendous overkill, but I'm not going to take the time to figure out which ones are actually required -- disk space is cheap and my free time is not. ????

After I'd clicked Next a few times, I was able to browse to the location of the downloaded CC3PlusSetup394.exe and select it.  This time the install process went perfectly!

I didn't know which pieces needed shortcuts, but I did see some *.lnk files (a Windows shortcut) and a hex dump of the content told me that fcw32.exe is the main application, so I created an entry for that one and then executed it.  Viola!

The only thing extra that I did was to select the program in POM and click Configure, then the Wine tab, then Configure Wine.  From here I changed the screen resolution from 96dpi to 120dpi because my eyes are too old to see the font clearly.  (And man, the default system menu font is UGLY!)

I plan to write this up in AsciiDoc and keep the page on my web site.  I'll link to it from here when it's done.  Maybe some intrepid soul will write a script for Campaign Cartographer 3+!

Azhrei Monday 14 December 2020 at 1:02
AzhreiAnonymous

Now I seem to be having issues opening file choosers.  I hadn't tried many things in CC3+ prior to installing CD3, so I can't say if it's specifically related to my attempt to install CD3 but I think it's not.

Anyway, I'm now receiving a page fault whenever a file chooser opens, such as by using File > New..., selecting a predefined template, and clicking Next, as shown:

wine: Unhandled page fault on read access to 0x00000024 at address 0x1007:0x0925cd98 (thread 006d), starting debugger...

This is clearly a problem in Wine, but the scripts for installing software are black boxes to me, so I'm not sure how to try a newer version of Wine.

I will continue to report any progress I make here.  Thanks for reading this far. :)