IIS had locked a file when syncing earlier in the week. This has already been addressed. Reinstall now and you'll be all set.
Nakor
After unregistering it, you would need to reboot to make sure it's cleared. And that you could delete it. But, if it unregistered, it'll not load on reboot, so it's, as they say, "mostly harmless". The IP update today will remove the regkey for that file, same as unregistering it. Still needs a reboot to take effect. Kris
I have checked both the standalone IP installers and the ones on SDC, iprepair.dll is no longer being included, though you may have it from a previous install. I will see about making an update to specifically remove it. This will also work: Start / Run / cmd.exe regsvr32 /u "C:\program files\stardock\object desktop\iconpackager\iprepair.dll" Reboot and the dll will no longer be locked (or loading) and can be removed if desired.
The Mac version (for use as a secondary) is running internally. Should have a beta available before too long.
Upon further inspection, you had 2 account records under that email. I expect you'll find things are sorted when you try next. If not, see the above, please.
Sorry, I thought we had sorted these. What version of Stardock Central? Help / About. Tools / Settings / General / Installation / enable Log activation errors to file. Restart SDC. Attempt to update/activate. Check for an activate.log in the GalCiv2 dir and please send that to [email protected]. Kris
Afraid not, Lucas.
I have spread the DNS server love around to more machines. It's possible our primary DNS servers in California are timing out somehow. If you get to a point where things are 404'ing (rather than site-specific error messages), please try Start / Run / cmd.exe and try to ping the server in question to see if your DNS resolves it. e.g. [c:\]ping www.joeuser.com Pinging www.joeuser.com [66.28.24
I have spread the DNS server love around to more machines. It's possible our primary DNS servers in California are timing out somehow. If you get to a point where things are 404'ing (rather than site-specific error messages), please try Start / Run / cmd.exe and try to ping the server in question to see if your DNS resolves it. e.g. [c:\]ping www.joeuser.com Pinging www.joeuser.com [66.28.242.
I think we found and fixed this over the holiday weekend. It wasn't showing up for everyone, but some people reported being unable to drag items around on ObjectDock. The fix is an updated iprepair.dll that's part of IP 3.00a (which I've made available via Stardock Central or use the page at stardock.com/support to be resent the full download link). You'll need a reboot after installing it. Failing that, Start / Run / regsvr32.exe /u "c:\program files\stardock\object desktop
I think we found and fixed this over the holiday weekend. It wasn't showing up for everyone, but some people reported being unable to drag items around on ObjectDock. The fix is an updated iprepair.dll that's part of IP 3.00a (which I've made available via Stardock Central or use the page at stardock.com/support to be resent the full download link). You'll need a reboot after installing it. Failing that, Start / Run / regsvr32.exe /u "c:\program files\stardock\object desktop
I think we found and fixed this over the holiday weekend. It wasn't showing up for everyone, but some people reported being unable to drag items around on ObjectDock. The fix is an updated iprepair.dll that's part of IP 3.00a (which I've made available via Stardock Central or use the page at stardock.com/support to be resent the full download link). You'll need a reboot after installing it. Failing that, Start / Run / regsvr32.exe /u "c:\program files\stardock\object desktop
I think we found and fixed this over the holiday weekend. It wasn't showing up for everyone, but some people reported being unable to drag items around on ObjectDock. The fix is an updated iprepair.dll that's part of IP 3.00a (which I've made available via Stardock Central or use the page at stardock.com/support to be resent the full download link). You'll need a reboot after installing it. Failing that, Start / Run / regsvr32.exe /u "c:\program files\stardock\object desktop
I think we found and fixed this over the holiday weekend. It wasn't showing up for everyone, but some people reported being unable to drag items around on ObjectDock. The fix is an updated iprepair.dll that's part of IP 3.00a (which I've made available via Stardock Central or use the page at stardock.com/support to be resent the full download link). You'll need a reboot after installing it. Failing that, Start / Run / regsvr32.exe /u "c:\program files\stardock\object desktop
Ironically, one of the comments we frequently get is how approachable the UI is. What did you find offputting? And what went wrong in your initial config that gave you some trouble? The linux version is not a high priority atm (it won't be part of 1.1). Hope you'll see the OS X beta before the end of July and we'll work from there.
Updates past that initial CD are liable to be a different story. That said, the activation will generate a code you can email to have it activated on other machines. And once it's activated, so long as you have the sig.bin for that machine (and don't reinstall your OS), you're set. If you want the game on your home machine, your work machine, the laptop, the tablet pc, and the PC you're "storing" at your cousin's house, nothing's going to say "BOO". When your serial is on a
jreynol2, please try and learn how to play with others during a beta. And mind your timezones. Kris
While it's too soon to tell, given the timeframes for Apple's switch to Intel processors, one may find that new virtualization/hypervisor bits will be part of their OS. Which, granted, would still mean you would need to be running Windows somewhere rather than a native port, but RAM's cheap, especially if you're using it for a game to begin with. We'll see...
The file in question is part of Stardock Central, but I don't believe the new IP builds use it. At least, I can't seem to find it being used here when installing on fresh machines. Reinstall SDC on top of itself from http://storage.stardock.com/files/sdcentral_setup.exe and see if that sorts things. Will check with the developer.
There are 4 potential files in question. The .iptheme or .iconpackage files have the information for what icon goes where from their corresponding .ICL file (or loose icons). The .ip file is a zip of those content files for packaging, to keep things smaller and bound up in 1 file for downloads. When you create an icon package under Package Builder mode (the View menu) and save it, you're saving the .iconpackage and .icl. From the File menu, you can use the Zip option to package a sel
I think it was recursing the skin dirs, which may or may not be necessary if the dir inherits the permissions. I'll look at it, I did change something there, but when testing on fresh installs with limited skins, didn't notice a problem. My bad.
It was setting the permissions on the WindowBlinds/IP folders so that Limited users would have access to them. I'll see what it was showing, it's fine. It's part of Windows. It's technically been running on fresh installs for 6+ months, apparently I changed something and it's showing itself more.
x64 support is on the list for the future, but I don't have a date yet.
x64 support is on the list for the future, but I don't have a date yet.
And more practical day-to-day than a boat.