From: Joe_MR on
One more note: this code works on another machine running Win7 64-bit / IE8.
So it seems to be an issue on this machine, but I can't figure out what. All
Add-Ins have been disabled, settings checked, etc. VBScript appears to be
disabled / broken, and I haven't been able to figure out how to re-enable /
fix it.

Thank you.

[ Joe Mosher ]

"Joe_MR" wrote:

> I'm having the exact same problem. We have an app that is not working on a
> customer's Win7 64-bit laptop. In debugging, we created a very small HTML
> page that is as follows:
>
> <HTML>
> <BODY onLoad="alert('hello world!')">
> <script type="text/vbscript">
> document.write("Looks like VBScript is working!")
> </script>
> This is my test page.
> </BODY>
> </HTML>
>
> The alert message pops up; it seems javascript is working. The "Looks like
> VBScript is working" message appears OK if we open the HTML in 64-bit IE8 but
> not in 32-bit. Re-registering VBSCript.DLL as Matthew mentioned does not
> help. Disabling add-ins does not help (including running the "no add-in"
> version from System Tools.)
>
> Appreciate any suggestions anyone can provide.
>
> Thank you.
>
> [ Joe Mosher ]
>
> "Ian Dendle" wrote:
>
> > We have a windows 7 x64 machine - a fresh install.
> >
> > We created a <script language="vbscript"> tag inside a web page, with a
> > simple window.alert call.
> >
> > In the 64 bit IE, it works. In 32-bit IE, it doesnt.
> >
> > Tried to unregister and re-register the vbscript.dll in the syswow64 folder,
> > but not luck.
> >
> > Security configuration is the same between versions.
> >
> > Has anyone seen anything similar?
> >
> > Any help would be greatly appreciated.
> >
> > Kind Regards,
> > Matthew Dendle
> >
> >
From: Joe_MR on
Thank you, Mayayana. Do you have any suggestions as to what may cause this
or what to try to get it working? I'm kind of at a loss here.

Thank you.

[ Joe Mosher ]

"Mayayana" wrote:

> ..vbs is not the same as IE scripting. The association
> for VBS is WScript. That's the host. In IE, IE is the
> host. Likewise with vbscript.dll. That ships as part
> of WSH. I doubt it has any connection to the IE script
> interpreter.
>
> | Have you discovered a solution to this yet? I've so far had no luck with
> | anything I have tried. I don't have access to the PC with the problem
> this
> | afternoon but one thing I just came across that I plan to try tomorrow is
> | this:
> |
> |
> http://www.nilpo.com/2009/07/windows-xp/restoring-vbs-vbscript-script-file-file-associations/
> |
> | Have you tried this? If so, did it have any effect?
> |
> | Thank you.
> |
> | [ Joe Mosher ]
> |
> | "Ian Dendle" wrote:
> |
> | > We have a windows 7 x64 machine - a fresh install.
> | >
> | > We created a <script language="vbscript"> tag inside a web page, with a
> | > simple window.alert call.
> | >
> | > In the 64 bit IE, it works. In 32-bit IE, it doesnt.
> | >
> | > Tried to unregister and re-register the vbscript.dll in the syswow64
> folder,
> | > but not luck.
> | >
> | > Security configuration is the same between versions.
> | >
> | > Has anyone seen anything similar?
> | >
> | > Any help would be greatly appreciated.
> | >
> | > Kind Regards,
> | > Matthew Dendle
> | >
> | >
>
>
> .
>
From: Mayayana on
| Do you have any suggestions as to what may cause this
| or what to try to get it working? I'm kind of at a loss here.
|

Sorry, but I don't have a copy of any Win64 to test on.
I haven't worked with it to speak of. I can't imagine why
IE32 would act differently from IE64, except maybe in
terms of plugins that might only be installed for one or
the other. If I had to guess I'd say that the problem is
probably elswhere .... a faulty path or some such.


From: Ian Dendle on
Hello All,

Thank you for your responses. I still have no idea what is happening on
this machine. Has anyone else had any luck?

Kind Regards,

Matt

"Mayayana" wrote:

> | Do you have any suggestions as to what may cause this
> | or what to try to get it working? I'm kind of at a loss here.
> |
>
> Sorry, but I don't have a copy of any Win64 to test on.
> I haven't worked with it to speak of. I can't imagine why
> IE32 would act differently from IE64, except maybe in
> terms of plugins that might only be installed for one or
> the other. If I had to guess I'd say that the problem is
> probably elswhere .... a faulty path or some such.
>
>
> .
>
 | 
Pages: 1
Prev: .Forms - how?
Next: output to cmd with | symbol