Firefox 3 Release & Stardock Site Compatibility
Jul 30, 2008 12:59

Firefox 3.0 goes final and is scheduled for release on Tuesday, June 17th.

There are currently known incompatibilities between Firefox 3 and many of our sites and forums. For the most part, the sites function properly, but have formatting issues. A specific example are the login & password fields to log into these forums. In Firefox 3, instead of both being on the same line, they are stacked vertically.

We will be addressing these visual issues in time. Please do NOT post threads on the forums pointing out Firefox 3 site issues. They will be deleted. We are aware of the problems and will work as quickly as we can to resolve them.

Until posted otherwise, the only version of Firefox our sites support at the moment is Firefox 2.

Possible major issues with impulse

By Posted May 10, 2008 15:18:40

Hiya gang:

I have been using Impulse for a while now and I have found the following problems with Vista x64 SP1.

1. Impulse have problems with application installations. For the longest time I couldn't get Iconpackager, bootskin or LogonstudioVista working. They would get installed but running them does nothing, or causes a error saying that the app needs to be closed.

As soon as I switched to SDC and updated LogonStudioVista and Iconpackager that I installed using SDC started to work!

Maybe Impulse's Installer isn't handling file permissions correctly?

2. This may NOT be a impulse issue only: Conflict between NOD32 and Windowblinds installation (possibly related to the installation issue that I mentioned in problem #1 above). Whenever I upgrade windowblinds using impulse some actions of the installer will be blocked by NOD32. (File operations that done after the system is rebooted after an update).

To be able to install WB, I had to disable both the NOD32 service and its startup GUI. It is rather annoying.

I have been using both WB and NOD32 for years now, and only after I switched to impulse in vista 64-bit did I ran into problems like this.

3. Minor problem: Impulse doesn't have the fine file installation path control that SDC have. For example:

If Object Desktop Apps I want the installation path to be:

Program Depot(x86)\My Stardock\Object Desktop\

I can do this using SDC by specifying the installation path for OD to be:

Program Depot(x86)\My Stardock\Object Desktop\

However, I cannot do the same if I am using Impuse

if I use the same path that I used in SDC (Program Depot(x86)\My Stardock\Object Desktop\) then the actual installation path will be.

Program Depot(x86)\My Stardock\Object Desktop\Stardock\Object Desktop\

I have not found a way around this yet, is there one?

thanks

0 Karma 4 Replies 3 Referrals
May 10, 2008 18:11:38
2. This may NOT be a impulse issue only: Conflict between NOD32 and Windowblinds installation (possibly related to the installation issue that I mentioned in problem #1 above). Whenever I upgrade windowblinds using impulse some actions of the installer will be blocked by NOD32. (File operations that done after the system is rebooted after an update).

To be able to install WB, I had to disable both the NOD32 service and its startup GUI. It is rather annoying.

I have been using both WB and NOD32 for years now, and only after I switched to impulse in vista 64-bit did I ran into problems like this.

Impulse + Object Desktop Ultimate + Nod32 3.0.xxx.x + Windows Vista Ultimate 32-bits and Windows XP Pro 32-bits = All works fine without any problem.
June 15, 2008 08:42:47

3. Minor problem: Impulse doesn't have the fine file installation path control that SDC have. For example:
If Object Desktop Apps I want the installation path to be:
Program Depot(x86)\My Stardock\Object Desktop\
I can do this using SDC by specifying the installation path for OD to be:
Program Depot(x86)\My Stardock\Object Desktop\

However, I cannot do the same if I am using Impuse
if I use the same path that I used in SDC (Program Depot(x86)\My Stardock\Object Desktop\) then the actual installation path will be.
Program Depot(x86)\My Stardock\Object Desktop\Stardock\Object Desktop\
I have not found a way around this yet, is there one?


This kind of obnoxious 'we want our name on your computer' crap is extremely annoying, particularly since SDC let you have very flexible control over install folders. If I install all my games into \games, for instance, I don't want a giant tiered 'stardock' folder in there. Sorry guys; I want to be able to choose where I put things. Isn't Impulse supposed to be less annoying than Steam?
June 15, 2008 10:33:33

I have been using Impulse for a while now and I have found the following problems with Vista x64 SP1.

1. Impulse have problems with application installations. For the longest time I couldn't get Iconpackager, bootskin or LogonstudioVista working. They would get installed but running them does nothing, or causes a error saying that the app needs to be closed.

As soon as I switched to SDC and updated LogonStudioVista and Iconpackager that I installed using SDC started to work!

Maybe Impulse's Installer isn't handling file permissions correctly?






Bootskin is a XP application

To be able to install WB, I had to disable both the NOD32 service and its startup GUI. It is rather annoying.


You should exclude WB of what NOD32 check or/and allow Impulse on the firewall. IF your firewall block Impulse i'm pretty sure almost all the problems came from this.

However, I cannot do the same if I am using Impuse


Yes you can, just click the Stardock logo then preference/folders. Take a look
Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.
June 15, 2008 15:27:20

lol nice haha
Stardock Forums v1.5.3112.18688
© 1995-2008 Stardock Corporation. All rights reserved.
All times are EST. The time is now 22:53:38
Server Load Time: 00:00:00.0000015   Page Render Time: