View Single Post
  #8  
Old October 2nd 07, 02:09 AM posted to microsoft.public.windowsme.setup
Ben B[_3_]
External Usenet User
 
Posts: 5
Default 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
|