Fresh install via SDC = No Go

Header says it all. Connection only works when taking the download - file and setting mpc up. I guess there is someting missing in the sdc setup.
4,037 views 13 replies
Reply #1 Top
Anybody home ?
Reply #2 Top
What build are you at now?
I have 2.32.397 Build 129 and have no issues. Server is U.S. Chicago.


Posted via WinCustomize Browser/Stardock Central
Reply #3 Top
Server is U.S. Chicago.

Where are you getting the server info?
Reply #4 Top
There is a SDC update today 06-Mar-06. After updating, I have Version 2.32.397 build 129
Reply #5 Top

Where are you getting the server info?


look under 'internet' in settings - I think. I'm not at home.

Reply #6 Top
I'm not at home.

Windows Classic, huh?
Reply #7 Top
Huh ? What does the version of SDC have to do with it ?

Again in maybe more clear words : I have uninstalled Multiplicity on a secondary machine where it was proper functioning before. Then after a registry cleaning and wiping of the folder and a reboot I wanted to re-install the thing from SDC. The install went right, and Multiplicity was running, but the primary was not able to connect to the secondary (installed from sdc) machine. Only after uninstalling again and an install from the downloaded full file (link obtained from e-mail with registered apps via support-page) and an update via sdc the thing works.
Reply #8 Top
Huh ? What does the version of SDC have to do with it ?


It appeared that you were having trouble with SDC

Fresh install via SDC = No Go


No mention of Multiplicity
Header says it all. Connection only works when taking the download - file and setting mpc up. I guess there is someting missing in the sdc setup.


No mention of Multiplicity. (But MCP is the Master Control program for lots of Stardock apps and is set from SDC.)

Again in maybe more clear words : I have uninstalled Multiplicity on a secondary machine where it was proper functioning before. Then after a registry cleaning and wiping of the folder and a reboot I wanted to re-install the thing from SDC. The install went right, and Multiplicity was running, but the primary was not able to connect to the secondary (installed from sdc) machine. Only after uninstalling again and an install from the downloaded full file (link obtained from e-mail with registered apps via support-page) and an update via sdc the thing works.


Much more information to work with. This would have made a better first post.

So you are up and working after reinstalling on both PCs from the last production build and upgrading to the lastest beta?


Posted via WinCustomize Browser/Stardock Central
Reply #9 Top
Yes. And I didn't write "MCP" but "MPC" And why should I post in the Multiplicity forum if I wanted to speak about another program ?
Reply #10 Top
Yes. And I didn't write "MCP" but "MPC" And why should I post in the Multiplicity forum if I wanted to speak about another program ?


You posted in ThinkDesk, not Mutiplicity.
You reffered to downloading, something SDC does and MP doesn't
You used the term MPC. It's very similar to MCP and your use of MPC is the first time I have heard Multiplicity to with that acronym.

Glad you resolved your problem.


Posted via WinCustomize Browser/Stardock Central
Reply #11 Top
I resolved mine, nevertheless there seems to be a problem with the build on sdc. So it would be good someone at Stardock would look into it.
Reply #12 Top
Carl, I thought I'd clarify my confusion on forum categories. I don't use one of the specialized SD or WC browsers for the forums, but surf in with Opera (&, in the past, IE). With these browsers, the posts in the Stardock Support category are all mixed together. I seldom look to see which subcategory a thread was entered into, so I jumped to conclusions, based on on how I read your post-- sorry for answering the wrong question!
Reply #13 Top
Well, I think we resolved the confusion now.