Url's Not Working

I have installed the new update of desktopx and now my url links wont come up. Says I have mistype the address which I didnt. Thanks
4,851 views 6 replies
Reply #1 Top
which url links? from objects you created or links supplied in a theme? i just went into builder mode, new object - url - put in a url, double clicked and it went to it.
did you check to make sure the url didn't get changed or scrambled when you updated?
Reply #2 Top
Objects that I created they were working fine for 3 months.
Links with https:// work fine but links that start with http:// wont open
unless one window is already open.

Thanks


Posted via WinCustomize Browser/Stardock Central
Reply #3 Top
Its not just you. Unless an IE6 window is already open the message "windows cannot find....mywebinfo... and a blank explorer window is displayed.

This seems to come and go. I can't figure it out...

Tom
Reply #4 Top
Weird. Didn't try it with no window open - so when I did it, FF just opened a new tab. But as of a week or so, when I first go online I get a message that the page request was refused (& start page comes up blank), check my proxy settings - however when I click 'home' the page loads.

Now I wanna try it with no windows open when I get home.
Reply #5 Top
I beleive this is strictly a IE6 problem or SP2, cos I have experienced this same thing on and off since I upgraded to SP2. I periodically have to go into file types and click on transfer, gopher and hyper text protocols under IE6 and reactivate them. It is the same thing on my husbands computer. Sometimes when I click on a link or something from within a program it will bring up my browser and go to the page, but at the same time a warning pops up saying windows can not find the url, make sure it is corect. I have become use to it now.
Reply #6 Top
It's a scripting problem. I don't know what this Stardock install actually did ... but go to MS's Download Center and look for Windows Script 5.6 The Stardock install corrupted something major. This MS file fixed the problem on my machine. Oh, the problem also affected my NAV installation.