BC+KM in Wine results in C++ runtime crash: SOLVED [apparently]

[Ambassador]

Right after I installed BC in wine, I added the 1.1 Patch.  On first opening, it crashed with the C++ debugging error that occurs during BC startup sometimes.  Trying again, BC opened perfectly.  I then installed KM 1.0 without making any changes to the prior-1.1 install.  Now BC will not open at all without give the C++ debugging error.  I tried deleting the "options.cfg" file in the the BC directory, but still no luck.  Any ideas?

==SPECS==
Xubuntu 8.10 "Hardy"
Wine 1.0 RC3 for Ubuntu 8.10 "Hardy"
Dell Latitude C810
Pentium III Mobile
Nvidia Geforce2 Go
512 MB Ram

[MLeo]

Rebooting?

Though that usually clears the DX type of errors.

Can you give me a screenshot of the actual error?

[Ambassador]

Just tried rebooting; still not working.

Screenshot included.

[MLeo]

That looks exactly like something I sometimes generate when I do sys.exit(), never did figure that out (well, I know why, but that's irrelevant here, in fact, I was trying to force it to quit while it was doing important stuff).

In this case, I'd nearly say it could be a bug in the WINE emulation.

If you install BC again, to a different location, does that work?
Meaning, can you reproduce it?

[Ambassador]

I'm not sure what do you mean.

You want me to reinstall BC in a different folder?

[MLeo]

Create a seperate install, you can just install it as many times as you want to.

[Ambassador]

And you just want a clean install (with/without patch) for basis?

[MLeo]

With patch.

It's just to make sure it's something in KM or not.

[Ambassador]

I have a backup BC folder on the computer.  Can I use this instead of a full reinstallation (for time)?

[MLeo]

Yeah, that will work fine.

[Ambassador]

Very well then.  I can't try it today, but I will try it tomorrow and post the results.

[Ambassador]

Ok, amazing update :shock: :

I wasn't able to install the BC Patch 1.1 into the backup directory since I already installed it in the other install.  I try changing the registry to see if I could bypass this, but it was to no avail.  I then tried renaming the KM 1.0 BC directory "Bridge Commander 2" and putting the other BC directory (renamed "Bridge Commander") into the Activision directory, but the patch still refused to install.  I tested the backup BC directory with BC 1.0, and it opened no problem.  Then, just out of curiousity, I tried to again open the KM 1.0 BC install.

It opened with no error!

I tried opening it a few more times in case it was just a fluke.  Still worked!

So apparently, if you use BC in Wine and come across a C++ debugging error after upgrading to KM 1.0, simply rename your BC directory to something else.  Of course, I can't say 100% that that will actually work, since I also had restarted the laptop a bunch before trying this, and I also deleted this section of the registry when I was trying to make the patch work:

Code: [Select]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Activision\Star Trek: Bridge Commander\V1.1]
"CD"="[CD path]"
"Comments"="Star Trek: Bridge Commander Patch"
"DisplayValue"="1.1"
"INSTALLEXEPATH"="[Path to STBC.exe]"
"INSTALLPATH"="[Path to BC folder]"
"Publisher"="Activision Publishing, Inc."


[MLeo]

I have been able to reinstall the patch any number of times, and to different directories (even to one without BC at all).

[Ambassador]

Well, when I tried to do install, it gave me a message saying that it was already installed.  After my registry modifications, the path installer then complained that it couldn't detect a valid BC install.

I wonder why yours doesn't do that.

[Ambassador]

So MLeo, do you the problem is completely solved or not?

[MLeo]

It seems rather random, so I can't tell.


About the patch, it asks me for an install directory.