I recently got a 64-bit Windows 7 computer at home and notice a compatibility problem with my IEMax scripts for Internet Explorer, available at http://EmpowermentZone.com/IEMax.exe (or .zip for a manual install) The scripts make use of a registration-free COM server that I created with VBScript and JScript code in a Windows Script Component file called HomerJax.wsc, which is also separately available at http://EmpowermentZone.com/HomerJax.zip The HomerJax COM object is instantiated via the JAWS GetObject function, using a technique described in the following article: Doctor Scripto's Script Shop: Windows Script Components Have a COM-ing Effect http://technet.microsoft.com/en-us/library/ee692823.aspx User feedback from Win64 users of my scripts led me to think that this technique would work on my new computer, but so far, it does not. I have Googled extensively for an answer, but not found one. Can anyone confirm whether this technique does or does not work on 64-bit Windows? I am guessing that the reason it does not work is because JAWS is a 64-bit process on that platform, so this technique would require 64-bit COM support. However, it is my understanding that Microsoft did not port that part of the Windows Script Host to 64-bit. I am guessing that the technique depends on runtime evaluation of the VBScript and JScript code by the COM server with the ProgID "MSScriptControl.ScriptControl.," which was not ported to 64-bit. If anyone has info to share on this topic, I'd appreciate it. Jamal __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts