My pc is screwed up

For some reason after installing what I think was some widget my pc is screwed up. For example in IE, javascript commands to open new windows wont work. Style sheets in IE dont show. My windows search tool doesnt show up. My norton system security does not display any information. Norton System Works wont run any of the applications such as the norton defragmenter tool. It seems something with scripting has been disabled. However I downloaded a programm which enables or disables scripting on windows. And disabled and renabled scripting and i still have the same problem.
Also I reset my internet explorer to its default settings and even checked to make sure scripting was enabled in IE and it is.
Any ideas on how to resolve this?

Thanks.
Jeff
3,719 views 4 replies
Reply #1 Top
Here is a thread that addresses possible fixes (see comments #2 and #5 for good possible fixes).

Also, here is the Windows Script download page Link

Download and install if the items in thread comments #2 & #5 do not fix the issue.

You may also want to clear the cache by deleting the DesktopX and IconX folders located in "C:\Documents and Settings\USERNAME\Local Settings\Application Data\Stardock" folder. For more on this procedure, you can see my mini tutorial here Link

I hope this helps.
Reply #3 Top
The scriptgen program seem to fix everything. Of course I am not sure why. Everything was working before, does that mean that the program somehow got removed originally?

Jeff
Reply #4 Top
It would probably be a bright idea to include the thread link, eh?

Here it is Link

Comment #2 refers to an issue that was previously seen with IconPackager version 3 and a .dll file that has since been removed. I would say this was not the issue based on Windows Script fixing the problem.

Comment #5 outlines the steps to manually re-register two script ".dll" files - both of which are reset by installing the Windows Script file.

I am not a coder, so do not know why the script engine goes sideways - but I suspect that an association is changed in some way that disables the ability to call the correct script engine for a given script - in this case it seems to be the JScript and VBScript that is affected.

Sorry I forgot the link, and I am glad the issue seems to be fixed.

Note - it could be a case of the particular widget you used was created in a way that is incompatible with your system, so you might just steer clear of that widget.