kkkwj

Join Date 09/2004

Theme mgr errors on Logonstudio part of skin suites

Hi, when I try to download theme suites that include a logon skin, the theme manager always comes up and says it had an error "downloading or installing" the logon skin. I really doubt it's the suites (they are by experienced people, and all suites trigger the error). When I reinstall Logonstudio it says "Logonstudio is no more registered as the default logon editor..." and I type Yes, make yourself the default logon editor. I've downloaded and reinstalled logonstudio a couple of times, rebooted N times, and tried everything else that I know. Even searched google. Yet.... the problem persists on my new XP SP2 machine... If it helps any, I'm a registered user who paid his money, so I don't think there are licensing issues involved. Would anyone here have some ideas that I might try? Thanks in advance.

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

I just opened it. Restored to default XP, it said okey dokey done and closed. Ran it from the start menu and it came back up and I set it back to random selection. Once you make it your default logon editor, immediately trying applying one that's in the list.

Successfully updated karma reason!

Hi, I can successfully reproduce your results (and could do so before I posted, too). The issue is not whether logonstudio works--it obviously does on my machine. Instead, the issue is that when I am in the Theme manager, and apply/download or apply-from-the-list a theme suite, the theme manager says there was a problem in "downloading or applying" the logonstudio part of the suite---even if the suite is in the list on my machine. Then it continues to apply the rest of the stuff in the suite with no problem. Thanks for your reply--I'm sure you know more than me about this issue. But the error still occurs, even after I followed the process you described.

Posted via WinCustomize Browser/Stardock Central

Successfully updated karma reason!

I'm sure you know more than me

nope, just keeping this active for now until someone comes along.
I've had trouble with thememgr before. i don't use it to download, just to apply. i download the suites and double click them to install or use Firefox to 'open with' when I download

Successfully updated karma reason!

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.

Very interesting to avoid using the theme mgr for downloading; that's what I was doing. Also I tried downloading and installing using the wincustomize browser (paid edition), with the same results.

I received an error just now "Can't find ../program files/wincustomize/logonstudio/LaSTCobalt_logon_/Theme.ini. Looking in my folders, I see that file (along with all others in lastcobalt) under ../wincustomize/themes/Last.. So I wonder why the theme manager is looking under logonstudio when it put the downloaded files under ../win../themes? Very odd.

I will try downloading and double clicking to install the theme now.

Successfully updated karma reason!

So I wonder why the theme manager is looking under logonstudio when it put the downloaded files under ../win../themes? Very odd.

because that's where it's supposed to look. by default logons go here: C:\Program Files\WinCustomize\LogonStudio

Successfully updated karma reason!

Agreed, ../wc/logonstudio//Theme.ini is where it looks for other logon work that I have downloaded as separate logon skins. But when TM downloads a suite, it appears to put the suite under the wc/themes directory, not wc/logonstudio. So it seems to me that TM puts the files in one place (wc/themes/*), and then looks for them in another place (wc/logonstudio/*), and gives me an error. Weird. I'm at a loss to explain or theorize what's going on. TM must treat theme logon skins different than it treats standalone logon skins, I guess.

Successfully updated karma reason!

In the end I copied the files under winc/logonstudio/themes/ to winc/logonstudio/, thereby bypassing the unwanted "themes" token in the directory pathname. This workaround lets theme manager install the downloaded themes properly, because it can find the files that it needs. (Only guessing here, but if this was my software I'd say that the left hand theme-downloader guy puts the logon files in the wrong place under logon/themes dir, so the TM right hand theme-setter guy can't find them.) All my stardock software is from fresh installs off the net (renewed subscription), so it looks to me like there's a small problem in the code...

Successfully updated karma reason!

So it seems to me that TM puts the files in one place (wc/themes/*

I only have 2 themes there. the 2 i got when i subscribed.
all my other themes are located at: C:\Program Files\Stardock\Object Desktop\ThemeManager\Themes

Successfully updated karma reason!

starkers

Join Date 05/2004

+1153

So I wonder why the theme manager is looking under logonstudio when it put the downloaded files under ../win../themes? Very odd.

because that's where it's supposed to look. by default logons go here: C:\Program Files\WinCustomize\LogonStudio

I had similar problems and noticed that not all logons in LogonStudio were being displayed in ThemeManager's menu for logons....I just clicked the add button to include all logons present and it resolved the issue. For some reason, ThemeManager does not always detect new LogonStudio additions and they have to be added manually as per above. If the LogonStudio document you are looking for appears not to be present in the search box, select it from the menu in LogonStudio and export to another folder, double click it to overwrite and then move it back to the LogonStudio folder. A bit of a workaround, yes, but it works for me.

Successfully updated karma reason!

Thanks for this input, but it sounds like your workarounds are solving a different problem. In my case, TM downloads a _suite_, and puts the logon part of the suite in dir wincustomize/logonstudio/themes//.

But then when the same TM tries to apply the suite, it looks in wincustomize/logonstudio/, and gives an error. It should be smart enough to look in the same place that it stored the files...

My fix was to manually copy the files from the logonstudio/themes//* directory to the logonstudio//* directory, so that TM could find them.

It seems to me from reading your post that you post a solution for the case where I download a logonstudio file by itself, and TM can't find it. So you explain going into LS, exporting, and moving it back so TM can find it. This situation is somewhat different than my own.

But your blues and fix contribute more evidence to the theory of weirdness in file downloading/recognizing between LS and TM, for sure.

Successfully updated karma reason!

starkers

Join Date 05/2004

+1153

But then when the same TM tries to apply the suite, it looks in wincustomize/logonstudio/, and gives an error. It should be smart enough to look in the same place that it stored the files.

As far as I understand it, when you download a suite, the individual components still go to their respective folders and are accessed by TM via the theme file it creates to apply them all with one click. I may be wrong, however, and hopefully someone more knowledgable than I will correct me if I am.

The thing is, I think it's a communication problem between TM and LogonStudio, somewhere...maybe also in how Logonstudio installs and registers new screens....ie, if it doesn't register correctly, TM cannot see or apply it. I have no problem with TM recognising wb's, boots, icons, cursors and etc, just logons, and the workaround I posted has been the only way for me to get TM to include logons when applying the suite.

I'm far from being an expert, so hopefully someone with a better understanding can help resolve this glitch

PS: for any of the powers that be who are reading this, we need another smiley...a praying to the heavens one

Successfully updated karma reason!

kkkwj i understand what you mean I've been saying it for a while...
When installing a suite TM installs the logon into WinCustomize\LogonStudio\Themes\BlahBlah
When it then attempts to apply the logon it looks for it in WinCustomize\LogonStudio\BlahBlah

I've tried some registry editing to correct it but as yet no luck. I'll be back if I figure it out.

Successfully updated karma reason!

Just a guess dragonmage, I don't use TM, but from what you just said..couldn't you just copy the logons from WinCustomize\LogonStudio\Themes to WinCustomize\LogonStudio also, so they are in both folders? A bit of a hassle, but easier than editing the reg.

Successfully updated karma reason!

Ok everyone prepare to slap yourselves in the forehead...

I was looking to hard for the fix the whole time. All you have to do is go into LogonStudio go to Options and change the Logon Path to C:\Program Files\WinCustomize\LogonStudio\Themes . Then just remember to install any logons that you download seperately into there. Theme Manager installs them there when you download suites already.

Successfully updated karma reason!