 |
|
Page 1 of 2 | |
|
|---|
BigDogBigFeet
Reply #2 Wednesday, August 13, 2008 3:08 PM
Reply #2 Wednesday, August 13, 2008 3:08 PM
If I understand this system from the many posts I've read they are the same release. Impulse is new, it resides on new servers, hence all apps sown in Impulse have slightly different release version numbers and dates.
As to your question does 3.5 work better than 3.49 without hosing something (since both the SDC version and the Impulse version 3.5 are the same) what's your experience tell you?
And by the way, 3.50.060 on Impulse is not a beta release.
Download it and install it. It's working fine here. I use Impulse.
As to your question does 3.5 work better than 3.49 without hosing something (since both the SDC version and the Impulse version 3.5 are the same) what's your experience tell you?
And by the way, 3.50.060 on Impulse is not a beta release.
Download it and install it. It's working fine here. I use Impulse.
eieio
Reply #3 Wednesday, August 13, 2008 8:30 PM
Reply #3 Wednesday, August 13, 2008 8:30 PM
Thanks BDBF. If I understand right, you installed with Impulse rather than SDC? And had no issues?
I knew there was a good chance that they both were the same release (although the large variation in dates seems damn odd), but about the same time that many posts were being made about the third set of numbers having no significance (I read them also), an Iconpackager release came out to fix an activation issue and, yep, only the third set of numbers changed ... which kind of shot that guideline all to hell.
The biggest concern I had, and wanted feedback on, was if installing from Impulse had any adverse effects.
The date thing was secondary, but with such a recent date, I wondered if the Impulse update might have just been released on 8-05-08 making it a brand spanking new release possibly fixing some bug from SDC's 4-08-08 release.
Anyone know if this is the case?
There have been more than a few posts where someone updated with Impulse and it did something weird which didn't happen if one updated with SDC ... having SKS5 uninstalled when updating SKS6 for one. And didn't IR's Vista woes trace back to using Impulse to install rather than SDC?
Anyway, too many irons in the fire right now to blindly go, etc. without a bit of feedback with those who have gone ahead.
I knew there was a good chance that they both were the same release (although the large variation in dates seems damn odd), but about the same time that many posts were being made about the third set of numbers having no significance (I read them also), an Iconpackager release came out to fix an activation issue and, yep, only the third set of numbers changed ... which kind of shot that guideline all to hell.
The biggest concern I had, and wanted feedback on, was if installing from Impulse had any adverse effects.
The date thing was secondary, but with such a recent date, I wondered if the Impulse update might have just been released on 8-05-08 making it a brand spanking new release possibly fixing some bug from SDC's 4-08-08 release.
Anyone know if this is the case?
There have been more than a few posts where someone updated with Impulse and it did something weird which didn't happen if one updated with SDC ... having SKS5 uninstalled when updating SKS6 for one. And didn't IR's Vista woes trace back to using Impulse to install rather than SDC?
Anyway, too many irons in the fire right now to blindly go, etc. without a bit of feedback with those who have gone ahead.
BigDogBigFeet
Reply #4 Thursday, August 14, 2008 2:59 AM
Reply #4 Thursday, August 14, 2008 2:59 AM
Oh I just noticed when actually checking some DX themes I have some master themes from jef that 3.5 does break some things. I thought these would be fixed but, they aren't.
1. System tray function is no longer supported. Just a blank empty tray and system tray is no longer a valid DX object in builder.
2. It no longer correctly loads and displays wallpapers. All you'll get is a solid backgound image instead of the nice custom wallpaper that is included with a DX theme.
3. It erroneously returns a read past end of file error in martin's scripts. I've noticed this in the weather scripts.
I'm sure there's more yet to be discovered. I've sent an email to support on these. I'm also looking for an earlier version to install of DX that doesn't have all these issues. Requested that from support as well.
1. System tray function is no longer supported. Just a blank empty tray and system tray is no longer a valid DX object in builder.
2. It no longer correctly loads and displays wallpapers. All you'll get is a solid backgound image instead of the nice custom wallpaper that is included with a DX theme.
3. It erroneously returns a read past end of file error in martin's scripts. I've noticed this in the weather scripts.
I'm sure there's more yet to be discovered. I've sent an email to support on these. I'm also looking for an earlier version to install of DX that doesn't have all these issues. Requested that from support as well.
RomanDA
Reply #5 Tuesday, August 19, 2008 3:23 PM
Reply #5 Tuesday, August 19, 2008 3:23 PM
Good luck BigDog... let us know if you get some fixes on the way.
Wizard1956
Reply #6 Tuesday, August 19, 2008 3:48 PM
The walls have been applying fine for me,I recently dl'd Q's CounterElement(both) and Gef's Destruction V2, both with walls,with no problems.PDJ's RadioWave also works as it should,with the wall supplied with it.
I also assigned walls to some of PDJ's other work with no problems.
Vista 32 bit,btw.
I usually delete the taskbar due to the non-functioning systray and use the one from the WB I'm using at the time.
Reply #6 Tuesday, August 19, 2008 3:48 PM
It no longer correctly loads and displays wallpapers. All you'll get is a solid backgound image instead of the nice custom wallpaper that is included with a DX theme.
The walls have been applying fine for me,I recently dl'd Q's CounterElement(both) and Gef's Destruction V2, both with walls,with no problems.PDJ's RadioWave also works as it should,with the wall supplied with it.
I also assigned walls to some of PDJ's other work with no problems.
Vista 32 bit,btw.
I usually delete the taskbar due to the non-functioning systray and use the one from the WB I'm using at the time.
gef
Reply #7 Tuesday, August 19, 2008 4:08 PM
Reply #7 Tuesday, August 19, 2008 4:08 PM
I'm using version 3:50:059 from Impulse. OS Vista Ultimate.
Wallpaper loads OK but as stated, systray does not. Martin's scripts do seem to work for me though.
I tend to use right-click which does support the systray.
Wallpaper loads OK but as stated, systray does not. Martin's scripts do seem to work for me though.
I tend to use right-click which does support the systray.
Murex
Reply #9 Tuesday, August 19, 2008 9:23 PM
Reply #9 Tuesday, August 19, 2008 9:23 PM
I have been slowly working on a DXtheme using Vista Ultimate. I noticed the lack of system tray in objects properties. I just loaded an old theme of mine and exported the system tray as a OBJ pack then imported it into the new theme and it seems to work ok..
Version 3.50.060
Version 3.50.060
BigDogBigFeet
Reply #10 Saturday, August 23, 2008 8:15 AM
Reply #10 Saturday, August 23, 2008 8:15 AM
Okay, to let everyone know what was up with my DX. First, I'm on XP SP3 and the system tray should work. It wasn't so I did an uninstall and aftear backing up my themes, widgets and objects wiped the DesktopX subdirectory. Wanted to make sure I had a fresh clean install and I got the system tray working again. Yea!
As far as background wallpapers there is some sort of bug either in Windows or DX where it wasn't handling the file path correctly. I had a path that looked like this for the DX current theme.
C:\Documents and Settings\HP_Administrator.BIG-DOGS-PC.000\Local Settings\Application Data\Stardock\DesktopX\CurrentTheme
Notice the folder name used as the Account Name "HP_Administrator.BIG-DOGS-PC.000" HP and Windows did this from a system restore since a folder with the name "HP_Administrator" already existed. I found the problem when examining the wallpaper changing script in one of jef's themes. This script had always worked before.
Sub Object_OnStateChange(state)
If state="Command executed" Then
System.SetWallpaper Object.Directory & "vista-1.bmp", 3
End If
End Sub
So, I substituted a file path "K:\Wallpapers\vista-1.bmp" for the Object.Directory and DX changed the wallpaper without a hitch. I remember reading a few months back beware of using periods in folder names because it can cause issues.
So, I setup a new User Account, got my desktop all fixed up, loaded up DesktopX and it was displaying wallpapers flawlessly again. My new current theme path is:
C:\Documents and Settings\Big Dog\Local Settings\Application Data\Stardock\DesktopX\CurrentTheme
And everything is working again. Sent in an explanation of all this to support. This was one tough one for me to debug what was happening. But I found it.
As far as background wallpapers there is some sort of bug either in Windows or DX where it wasn't handling the file path correctly. I had a path that looked like this for the DX current theme.
C:\Documents and Settings\HP_Administrator.BIG-DOGS-PC.000\Local Settings\Application Data\Stardock\DesktopX\CurrentTheme
Notice the folder name used as the Account Name "HP_Administrator.BIG-DOGS-PC.000" HP and Windows did this from a system restore since a folder with the name "HP_Administrator" already existed. I found the problem when examining the wallpaper changing script in one of jef's themes. This script had always worked before.
Sub Object_OnStateChange(state)
If state="Command executed" Then
System.SetWallpaper Object.Directory & "vista-1.bmp", 3
End If
End Sub
So, I substituted a file path "K:\Wallpapers\vista-1.bmp" for the Object.Directory and DX changed the wallpaper without a hitch. I remember reading a few months back beware of using periods in folder names because it can cause issues.
So, I setup a new User Account, got my desktop all fixed up, loaded up DesktopX and it was displaying wallpapers flawlessly again. My new current theme path is:
C:\Documents and Settings\Big Dog\Local Settings\Application Data\Stardock\DesktopX\CurrentTheme
And everything is working again. Sent in an explanation of all this to support. This was one tough one for me to debug what was happening. But I found it.
WeatherBound
Reply #12 Saturday, August 23, 2008 10:09 AM
I will give this a try. I hope it works for me too.
Reply #12 Saturday, August 23, 2008 10:09 AM
I have been slowly working on a DXtheme using Vista Ultimate. I noticed the lack of system tray in objects properties. I just loaded an old theme of mine and exported the system tray as a OBJ pack then imported it into the new theme and it seems to work ok..
Version 3.50.060
Version 3.50.060
I will give this a try. I hope it works for me too.
BigDogBigFeet
Reply #13 Tuesday, August 26, 2008 7:02 PM
Thanks for the workaround. I'm doing the same now in XP SP3.
Reply #13 Tuesday, August 26, 2008 7:02 PM
I have been slowly working on a DXtheme using Vista Ultimate. I noticed the lack of system tray in objects properties. I just loaded an old theme of mine and exported the system tray as a OBJ pack then imported it into the new theme and it seems to work ok..
Version 3.50.060
Version 3.50.060
Thanks for the workaround. I'm doing the same now in XP SP3.
Lumic
Reply #14 Wednesday, October 8, 2008 7:02 AM
Reply #14 Wednesday, October 8, 2008 7:02 AM
While we can work around the SysTray creation problem, it is hard to then edit the SysTray properties because we have to use an earlier version of DX (i.e. have one computer with old DX, or if you're like me with one computer you can't change it at all).
Hopefully Stardock fixes this. DesktopX 3.5 was released quite a while ago...can't they do a minor update?
Murex
Reply #15 Monday, November 17, 2008 9:42 AM
Reply #15 Monday, November 17, 2008 9:42 AM
Thanks for the workaround. I'm doing the same now in XP SP3.
Your welcome glad I could help.
I am still using the system tray object from one of my older themes in Vista and it is still working fine. Apparently system tray will work in vista it's just a matter of getting stardock to work on the problem.
Murex
Reply #16 Monday, November 17, 2008 9:51 AM
Reply #16 Monday, November 17, 2008 9:51 AM
SinTactics
While we can work around the SysTray creation problem, it is hard to then edit the SysTray properties because we have to use an earlier version of DX (i.e. have one computer with old DX, or if you're like me with one computer you can't change it at all).
Hopefully Stardock fixes this. DesktopX 3.5 was released quite a while ago...can't they do a minor update?
Hopefully Stardock fixes this. DesktopX 3.5 was released quite a while ago...can't they do a minor update?
Not sure what you mean it's hard to edit the system tray or why you need to use an older version of DX. I am using the latest version and am able to edit system tray fine. You may need to bring up your object list and edit it from there.
Lumic
Reply #17 Saturday, January 17, 2009 2:51 AM
Reply #17 Saturday, January 17, 2009 2:51 AM
Is there a later version than 3.5? My DX does not have any SysTray support.
Tailsgirl
Reply #18 Saturday, January 17, 2009 3:00 AM
Reply #18 Saturday, January 17, 2009 3:00 AM
I don't think so Sin, I think 3.5 is the latest 
_Martin_
Reply #19 Wednesday, January 21, 2009 9:29 AM
Reply #19 Wednesday, January 21, 2009 9:29 AM
Would be delighted to see if/when DX4 is eventually coming out. It's been promised for soooo long, and there are quite a few bugs in the version we are left with.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 1 of 2 | |
|
|---|
Reply #1 Wednesday, August 13, 2008 6:59 AM