VBScript Runtime Error.
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object Hello, The above is the error I get when I attempt to run the RegSrch.vbs from Bill's Way. http://billsway.com/ This is a tool I have long used. As far as I can determine this error is confined to my using it. I have checked this http://support.microsoft.com/default.aspx/kb/194801 but do not know if is relevant. I would appreciate any suggestions as to how I might resolve this issue. Thanks. Ben. |
VBScript Runtime Error.
When did the problem start? What changes have you made to your system
since you last used RegSrch.vbs? If the problem is recent, consider using system restore and rolling your system back to a checkpoint created around the time you were last able to run RegSrch.vbs without problem. You might want to consider downloading and reinstalling Windows Script however that isn't particularly easy for those running Win Me. The latest version of Windows Script is v5.7 however this doesn't install on Win Me and Microsoft withdrew v5.6 for Win 9x systems on the grounds that they no longer support Win 9x operating systems. You may need to use Google to find a copy of 5.6 for Win 9x that you can download and install. -- Mike Maltby Ben B wrote: Microsoft VBScript runtime error '800a01ad' ActiveX component can't create object Hello, The above is the error I get when I attempt to run the RegSrch.vbs from Bill's Way. http://billsway.com/ This is a tool I have long used. As far as I can determine this error is confined to my using it. I have checked this http://support.microsoft.com/default.aspx/kb/194801 but do not know if is relevant. I would appreciate any suggestions as to how I might resolve this issue. Thanks. Ben. |
VBScript Runtime Error.
Hello Mike,
I found a download of Windows Script v5.6 he:http://www.macropool.com/en/download/scripting.html installed it and all is well. I would like to understand about this component and I wonder if you could tell me where it is located on my system so I might have a look at the items comprising it and to see what I may have deleted. The major change, made yesterday, was the deletion of an installed freeware 'Instant Lock' (ilock). I said 'Yes to all' during the deletion and now wonder about that choice. Here. http://pcwin.com/Utilities/Security_...LOCK/index.htm Appreciate hearing from you, Mike. Ben. "Mike M" wrote in message ... | When did the problem start? What changes have you made to your system | since you last used RegSrch.vbs? If the problem is recent, consider using | system restore and rolling your system back to a checkpoint created around | the time you were last able to run RegSrch.vbs without problem. | | You might want to consider downloading and reinstalling Windows Script | however that isn't particularly easy for those running Win Me. The latest | version of Windows Script is v5.7 however this doesn't install on Win Me | and Microsoft withdrew v5.6 for Win 9x systems on the grounds that they no | longer support Win 9x operating systems. You may need to use Google to | find a copy of 5.6 for Win 9x that you can download and install. | -- | Mike Maltby | | | | Ben B wrote: | | Microsoft VBScript runtime error '800a01ad' | ActiveX component can't create object | | Hello, | | The above is the error I get when I attempt to run the RegSrch.vbs | from Bill's Way. http://billsway.com/ | | This is a tool I have long used. As far as I can determine this error | is confined to my using it. | | I have checked this | http://support.microsoft.com/default.aspx/kb/194801 but do not know | if is relevant. | | I would appreciate any suggestions as to how I might resolve this | issue. | | Thanks. | | Ben. | |
VBScript Runtime Error.
Hello Mike,
I will do the same (install /uninstall ilock) and post back. I notice that vbscript.dll was created on my system today's date Thanks. Ben. "Mike M" wrote in message ... | Ben, | | It would appear that uninstalling ilock might have uninstalled or removed | one of the files used by Windows Script. I'm pleased to read that | reinstalling WS v5.6 has resolved the problem. | | Sorry I don't have the time at the moment to see if I can replicate the | problem with ilock (install and then uninstall) but will try later tonight | or perhaps tomorrow. | -- | Mike Maltby | | | | Ben B wrote: | | Hello Mike, | | I found a download of Windows Script v5.6 | he:http://www.macropool.com/en/download/scripting.html installed | it and all is well. | | I would like to understand about this component and I wonder if you | could tell me where it is located on my system so I might have a look | at the items comprising it and to see what I may have deleted. | | The major change, made yesterday, was the deletion of an installed | freeware 'Instant Lock' (ilock). I said 'Yes to all' during the | deletion and now wonder about that choice. Here. | http://pcwin.com/Utilities/Security_...LOCK/index.htm | | Appreciate hearing from you, Mike. | |
VBScript Runtime Error.
Hello Mike,
I installed/uninstalled several times. The only thing I am certain of, in consequence, is that Instant Lock is implicated. However precisely what happens is beyond my comprehension. All I know is that I must re-intall Windows Script (mentioned in my first post) to be able to run RegSrch (or re-install Instant Lock which has the same effect). The file scrrun.dll is the one for which confirmation of deletion is required when uninstalling - however that .dll remains on my system as does vbscript.dll after the uninstall (using Add/Remove). However the folder Instant Lock remains in Program Files with two items in it - configuration.ini (0KB) and scrrun.dll.(148KB) I discover also that the scrrun.dll in the Instant Lock Program folder (5.6.0.8820) is a different version to the one in Windows (5.6.0.8825) and that the deletion of the former causes the error. Also that VBSCRIPT.DLL is 5.6.0.8825 which baffles me completely (can two files with different names have the same version number?). I look forward to your explication, Mike. bg Ben. "Ben B" wrote in message ... | Hello Mike, | | I will do the same (install /uninstall ilock) and post back. | | I notice that vbscript.dll was created on my system today's date | | Thanks. | | Ben. | | "Mike M" wrote in message | ... | | Ben, | | | | It would appear that uninstalling ilock might have uninstalled or removed | | one of the files used by Windows Script. I'm pleased to read that | | reinstalling WS v5.6 has resolved the problem. | | | | Sorry I don't have the time at the moment to see if I can replicate the | | problem with ilock (install and then uninstall) but will try later tonight | | or perhaps tomorrow. | | -- | | Mike Maltby | | | | | | | | Ben B wrote: | | | | Hello Mike, | | | | I found a download of Windows Script v5.6 | | he:http://www.macropool.com/en/download/scripting.html installed | | it and all is well. | | | | I would like to understand about this component and I wonder if you | | could tell me where it is located on my system so I might have a look | | at the items comprising it and to see what I may have deleted. | | | | The major change, made yesterday, was the deletion of an installed | | freeware 'Instant Lock' (ilock). I said 'Yes to all' during the | | deletion and now wonder about that choice. Here. | | http://pcwin.com/Utilities/Security_...LOCK/index.htm | | | | Appreciate hearing from you, Mike. | | | | |
VBScript Runtime Error.
Ben,
Only a partial answer as I haven't yet had a chance to play with ilock. Installing Windows Scripting installs/updates the following files: jscript.dll, scrobj.dll, scrrun.dll, vbscript.dll, wshext.dll and wshom.ocx - all version 5.6.0.8825 except for jscript.dll which is v 5.6.0.8831 with the files located in Windows\System and wscript.exe which is located in the ..\Windows folder. All of these files are protected against deletion or being overwritten by Win Me's system file protection mechanism (SFP). cscript.exe in the windows\command folder (it is a DOS command) is also updated to v5.6.0.8825, this file is not protected by SFP. In addition the install uses scr56en.inf and the catalogue scr56en.cat, the latter including the information required to allow the updated files to be installed rather than blocked by SFP. Also that VBSCRIPT.DLL is 5.6.0.8825 which baffles me completely (can two files with different names have the same version number?). There is no reason why multiple files should not have the same version number, in fact, it makes sense to me that those in the same package do have the same number. The reason why jscript.dll is version 5.6.0.8513 rather than 5.6.0.8825 is that the file was further updated as part of the KB917344 hotfix (MS06-023: Vulnerability in Microsoft JScript could allow remote code execution). The original version of Windows Scripting 5.6 in an out of the box Win Me install is v5.6.0.6626 I can't for the moment confirm why removing the older version of scrrun.dll from the ilock folder causes problems but am assuming that when ilock is installed it makes a change to the registry which redirects registry calls to scrrun.dll to the copy in the ilock programs folder rather than the correct copy which is in the windows\system folder. I note that, without ilock installed the registry contains eight links to the copy of scrrun.dll in the windows\system folder. It is these entries that I suspect installing ilock amends (it really shouldn't) and that on uninstalling it does not restore the values to their original settings data. Such behaviour is totally unacceptable and something which XP and alter try to prevent by allowing side by side installs whereby particular applications can use specific copies of a link library whilst leaving other applications to continue using the system version. I hope this makes some sense. If not loop to the beginning and try again. vbg Apologies for typos and grammar, it's been another trying day. :-( -- Mike Maltby Ben B wrote: Hello Mike, I installed/uninstalled several times. The only thing I am certain of, in consequence, is that Instant Lock is implicated. However precisely what happens is beyond my comprehension. All I know is that I must re-intall Windows Script (mentioned in my first post) to be able to run RegSrch (or re-install Instant Lock which has the same effect). The file scrrun.dll is the one for which confirmation of deletion is required when uninstalling - however that .dll remains on my system as does vbscript.dll after the uninstall (using Add/Remove). However the folder Instant Lock remains in Program Files with two items in it - configuration.ini (0KB) and scrrun.dll.(148KB) I discover also that the scrrun.dll in the Instant Lock Program folder (5.6.0.8820) is a different version to the one in Windows (5.6.0.8825) and that the deletion of the former causes the error. Also that VBSCRIPT.DLL is 5.6.0.8825 which baffles me completely (can two files with different names have the same version number?). I look forward to your explication, Mike. bg |
VBScript Runtime Error.
Hello Mike,
Thank-you for the post. Based on it I have explored the matter further and, with my limited understanding, I found as follows: 1. Installing Instant Lock causes changes to be made in the registry whereby at least this item, scrrun.dll, originally showing data C:\Windows\scrrun.dll becomes data C:\Program Files\instant lock\scrrun.dll. There are eight instances (as you told me) in the Root directory where this data is thus modified. 2. The Instant Lock version number of scrrun.dll is 5.6.0.8820. The Windows version is 5.6.0.8825. 3. Using the Add\Remove Program option results in the Instant Lock's removal GUI which asks for confirmation about the removal of scrrun.dll and, no matter whether Yes or No is clicked, the uninstall results in all items, except the scrrun.dll, being removed from the Instant Lock folder. The registry root directory entry, for scrrun.dll, remains unchanged (data C:\Program Files\instant lock\scrrun.dll). 4. At this point RegSrch.vbs is still working. 5. The deletion of the Instant Lock folder and content (scrrun.dll) renders RegSrch.vbs useless. The registry entry for scrrun.dll still points to C:\Program Files\instant lock\scrrun.dll 6. The installation of Windows Script v 5.6 changes the registry entry for scrrun.dll to point to C:\Windows\System\scrrun.dll with the result that RegSrch.vbs again works as expected. **************************************** Granted, Mike, my way of describing what 'I have found' is the language of a computer illiterate. Please excuse. The "assumptions" you made in your last post to me are absolutely correct - of course they are. vbg I am, as always, deeply appreciative of the care you take in your posts; and the opportunity you give, to one such as myself, to explore a little below the surface and see a fraction more. With my thanks, and very best wishes, Mike, Ben. P.S. I am going to stay with WinME but I always acknowledge the superiority of XP. I was, I suspect, in the market marginally early. In anycase, clearly WinME will always challenge me sufficiently to keep me thinking! Cheers. "Mike M" wrote in message ... | Ben, | | Only a partial answer as I haven't yet had a chance to play with ilock. | | Installing Windows Scripting installs/updates the following files: | jscript.dll, scrobj.dll, scrrun.dll, vbscript.dll, wshext.dll and | wshom.ocx - all version 5.6.0.8825 except for jscript.dll which is v | 5.6.0.8831 with the files located in Windows\System and wscript.exe which | is located in the ..\Windows folder. All of these files are protected | against deletion or being overwritten by Win Me's system file protection | mechanism (SFP). | cscript.exe in the windows\command folder (it is a DOS command) is also | updated to v5.6.0.8825, this file is not protected by SFP. | In addition the install uses scr56en.inf and the catalogue scr56en.cat, | the latter including the information required to allow the updated files | to be installed rather than blocked by SFP. | | Also that VBSCRIPT.DLL is 5.6.0.8825 which baffles me completely (can | two files with different names have the same version number?). | | There is no reason why multiple files should not have the same version | number, in fact, it makes sense to me that those in the same package do | have the same number. The reason why jscript.dll is version 5.6.0.8513 | rather than 5.6.0.8825 is that the file was further updated as part of the | KB917344 hotfix (MS06-023: Vulnerability in Microsoft JScript could allow | remote code execution). The original version of Windows Scripting 5.6 in | an out of the box Win Me install is v5.6.0.6626 | | I can't for the moment confirm why removing the older version of | scrrun.dll from the ilock folder causes problems but am assuming that when | ilock is installed it makes a change to the registry which redirects | registry calls to scrrun.dll to the copy in the ilock programs folder | rather than the correct copy which is in the windows\system folder. I | note that, without ilock installed the registry contains eight links to | the copy of scrrun.dll in the windows\system folder. It is these entries | that I suspect installing ilock amends (it really shouldn't) and that on | uninstalling it does not restore the values to their original settings | data. Such behaviour is totally unacceptable and something which XP and | alter try to prevent by allowing side by side installs whereby particular | applications can use specific copies of a link library whilst leaving | other applications to continue using the system version. | | I hope this makes some sense. If not loop to the beginning and try again. | vbg Apologies for typos and grammar, it's been another trying day. :-( | -- | Mike Maltby | | | | Ben B wrote: | | Hello Mike, | | I installed/uninstalled several times. | | The only thing I am certain of, in consequence, is that Instant Lock | is implicated. However precisely what happens is beyond my | comprehension. All I know is that I must re-intall Windows Script | (mentioned in my first post) to be able to run RegSrch (or re-install | Instant Lock which has the same effect). | | The file scrrun.dll is the one for which confirmation of deletion is | required when uninstalling - however that .dll remains on my system | as does vbscript.dll after the uninstall (using Add/Remove). However | the folder Instant Lock remains in Program Files with two items in it | - configuration.ini (0KB) and scrrun.dll.(148KB) | | I discover also that the scrrun.dll in the Instant Lock Program folder | (5.6.0.8820) is a different version to the one in Windows | (5.6.0.8825) and that the deletion of the former causes the error. | | Also that VBSCRIPT.DLL is 5.6.0.8825 which baffles me completely (can | two files with different names have the same version number?). | | I look forward to your explication, Mike. bg | |
VBScript Runtime Error.
Ben,
So very much as I expected. Such install behaviour is that of malware and viruses. No application should ever hijack a system file in the way that ilock apparently does in this case. As for staying with Win Me, if it does what you want then why spend money on changing? I only mentioned XP because it has a mechanism that allows two versions of the same file to be in memory at the same time meaning that there is no need for an application to hijack or modify a system file if that file doesn't quite meet the application's needs. All the application has to do is place a copy of the modified file in the application's folder (as ilock does here) and this will always be used by the application in preference to the system copy and thus no registry changes are required. In Win Me, which only allows one copy of a file to be in memory, whichever of the two files is loaded first will be the one used hence why ilock alters the registry so as to ensure that its copy is the always the one used. ilock does this because system file protection prevents it modifying the copy if the file in the windows\system folder. ilock then compounds the problem by not undoing the registry changes when it is uninstalled. -- Mike Maltby Ben B wrote: Hello Mike, Thank-you for the post. Based on it I have explored the matter further and, with my limited understanding, I found as follows: 1. Installing Instant Lock causes changes to be made in the registry whereby at least this item, scrrun.dll, originally showing data C:\Windows\scrrun.dll becomes data C:\Program Files\instant lock\scrrun.dll. There are eight instances (as you told me) in the Root directory where this data is thus modified. 2. The Instant Lock version number of scrrun.dll is 5.6.0.8820. The Windows version is 5.6.0.8825. 3. Using the Add\Remove Program option results in the Instant Lock's removal GUI which asks for confirmation about the removal of scrrun.dll and, no matter whether Yes or No is clicked, the uninstall results in all items, except the scrrun.dll, being removed from the Instant Lock folder. The registry root directory entry, for scrrun.dll, remains unchanged (data C:\Program Files\instant lock\scrrun.dll). 4. At this point RegSrch.vbs is still working. 5. The deletion of the Instant Lock folder and content (scrrun.dll) renders RegSrch.vbs useless. The registry entry for scrrun.dll still points to C:\Program Files\instant lock\scrrun.dll 6. The installation of Windows Script v 5.6 changes the registry entry for scrrun.dll to point to C:\Windows\System\scrrun.dll with the result that RegSrch.vbs again works as expected. **************************************** Granted, Mike, my way of describing what 'I have found' is the language of a computer illiterate. Please excuse. The "assumptions" you made in your last post to me are absolutely correct - of course they are. vbg I am, as always, deeply appreciative of the care you take in your posts; and the opportunity you give, to one such as myself, to explore a little below the surface and see a fraction more. With my thanks, and very best wishes, Mike, Ben. P.S. I am going to stay with WinME but I always acknowledge the superiority of XP. I was, I suspect, in the market marginally early. In anycase, clearly WinME will always challenge me sufficiently to keep me thinking! Cheers. |
All times are GMT +1. The time now is 03:13 AM. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Win98Banter.com