Scripting 5.6 and WSHOM.OCX

[Jerry]

Hello,,,, :)

And, first Thanks your for your Time, Help, and Advise.

In this area many users cannot upgrade from W95 for many
valid reasons and they wish to use the Scripting 5.6 from
Microsoft (scr56en.exe). For a test situation a W95
machine with the Internet Explorer 5.5 Service Pack 2 was
the beginning. Scripting 5.1 was installed from the
delivery of IE 5.5 SP 2. IE 5.5 SP2 and Scripting 5.1
works as expected and is registered as reported with no
decrepencies related to DEPENDS.EXE using the 5.1
WSHOM.OCX.

The situation from a download and execution of scr56en.exe
will not get past the registration using the WSHOM.OCX.
The following occurs during execution of scr56en.exe:

o All files (DLLs, EXE, etc.) are delivered
as expected for 5.6
o When the execution of scr56en.exe starts to register
Scripting using the WSHOM.OCX the following error
occurs:

"Error registering the OCX c:\windows\system\wshom.ocx"

An immediate reboot produces the following:

|-----------------------------------------|
|"Windows Update" |
|-----------------------------------------|
|"An error occurred loading: |
| "c:\windows\system\wshom.ocx" |
|"The file may not have been installed or |
|it has been corrupted." |
|-----------------------------------------|

Using regsvr32.exe to try and make the wshom.ocx reset the
registry file produced the following:

1. Running regsvr32.exe c:/windows/system/wshom.ocx
produced the following:

Load Library["c:\windows\system\wshom.ocx"] failed
GetLastError returns 0x0000001f

2. Running regsvr32.exe -r wshom.ocx produced the same
error as in 1 above.

Based on the Error 0x0000001f a ConrolPanel/System reports
no device errors.

Using the new 5.6 WSHOM.OCX to un-register does not
succesfully un-register the Scripting.

However, using the older 5.1 WSHOM.OCX to un-register
Scripting does the un-register properly and removes all
related Scripting files.

With the registry clean from Scripting and Scripting files
removed even a re-execution of scr56en.exe produces the
same results as above.

The FAQs define that Scripting 5.6 will deliver to a W95
System. Also, other tables from TECHNET and MSDN Scripting
areas show the things (Methods, etc.) that are
immplemented in 5.6 and for which versions of systems
(W95,W98,NT, 2000, etc.). And all is understood.

As mentioned in other discussions the use of scr56en.exe
on a W95 machine has been successful.

If anyone has seen this situation it would be GREAT to
understand what I am not doing that I need to do.

AND, Thanks for your Time, Help, and Advise.

Jerry

[petal]

Hi Jerry

I've been searching around for similar errors to try and help on this. The
commonest suggestion is that there is a missing/incorrect DLL - possibly,
although DEPENDS shows no missing DLL, there may be a missing entry point or
something? I'm not a programmer so don't know the right terminology. On that
basis, a couple of new suggestions:

1) try RegDrop from http://www.addisonsw.com/ - haven't used it myself, but
maybe it'll do what it says on the tin (informative errors).

2) "open the ocx file with QuickView (right-click within Explorer) and look
in the "Imported-Name Table (Link-Time Imports)" section. This will list
required dll's." - if you can find a working box, compare DLL versions
(maybe try copying over from W98?)

3) hack it with notepad to see internal references - on my W2K box usual
suspects are there (ADVAPI32, SHELL32, KERNEL32, USER32, OLE32, OLEAUT32,
MPR, SCRRUN, MSVCRT)

3) "replace comcat.dll version 5.0 with 4.71 (copied from another box)..."

4) try an updated version of MSVCRT.DLL (latest W95 version from
http://www.microsoft.com/windows95/downloads/contents/WURecommended/S_WUServicePacks/MFCLibrary/Default.asp)

5) try installing a Visual Studio or recent Office product to see if this
will provide the necessary updates...

regards
petal

[Jerry]

Hello Petal,,,,:)

Every suggestion made below (1-5) looked so promising that
it seemed at least one would help solve the problem. And,
I appologize for such a lengthy report.

Each item was tried in succession and the W95 registration
of WSHOM.OCX still produces the same errors as mention in
the first Email.

Item 1 (RegDrop) was downloaded and executed with
WSHOM.OCX, but the error was no more informative than
the ....0x0000001f error for the Windows reqistry update
using the WSHOM.OCX file.

Item 2 using QuickView on WSHOM.OCX did not find any
descrepencies.

Item 3 HACKED the following Internals from WSHOM.OCX and
all are present with no bad DEPENDS with the following
versions:

1. KERNEL32.dll 4.00.1111
2. NTDLL.DLL 4.00.950
3. msvcrt.dll 6.00.8797.0
4. OLEAUT32.dll 2.40.4277
5. ole32.dll 4.71.2900
6. ADVAPI32.dll 4.71.0118.0
7. USER32.dll 4.00.950
8. MPR.dll 4.00.950
9. SHELL32.dll 4.00.1111
10. WINSPOOL.DRV 4.00.950
11. ScrRun.dll 5.6.0.8515

There are some dll files that were listed twice with
different versions (earlier), but those did not exist in
the /windows or /windows/system directory:
These are:

NTDLL.DLL loaded to /ProgramFiles/ATT
ADVAPI32.dll loaded to /ProgramFiles/ATT
msvcrt.dll loaded to /tools_95/ for Iomega ZIP Drive
which was removed via Control
Panel.

And, the $Path is not set to include these.

Item 4: Windows 95 Library Upgrade (SPEU.exe)

When I listed the link mentioned in item number 4 below
(W95 Library Upgrade--SPEU.exe), I found links to 197298
and 194022.

The files mentioned in Article 197298 were checked for
comparison of version numbers on the W95 machine and the
following was found:

Version Listed Version on the W95
by Article 197298 machine before Upgrade
--------------- ----------------------
Msvcrt.dll 6.00.8337 6.10.8637.0 (listed as -
"Signature" W2000 Beta
Friday Oct 18, 1999)
Oleaut32.dll 2.30.4265 2.40.4277
Olepro32.dll 5.00.4265 5.0.4277
Asycfilt.dll 2.30.4265 2.40.4277
Stdole2.tlb 2.30.4265 2.40.4277
Mfc42.dll 6.00.8267 6.00.86650
Mfc42u.dll 6.00.8267 for NT PLATFORM Only
Regsvr32.exe 5.00.1641.1
RegTlib.exe 6.00.8191

Since the versions currenly existing on the W95 machine
were higher, the SPEU.exe did not replace any of the above
files.

However, the Msvcrt.dll was suspect because of
the "signature" listed in the properties that specified
it as a "W2000 Beta" version(for a W95???). I replaced it
from the Visual Studio Service Pack 5 CAB file. It is now
6.00.8797.0, but still is not the same as Article 194022
says it should be.

Based on Article 194022 this W95 machine does have Visual
Studio 6.0 Standard Edition installed (C++, etc.). So I
downloaded and installed the Visual Studio 6.0 Service
Pack 5 (vs6sp5.exe) making sure MDAC_TYPE.exe for MDAC 2.5
was executed first.

Boots were done in between each upgrade with the execution
of scr56en.exe and each time the same errors listed in the
first Email were produced.

After each upgrade & reboot the versions were compared
again and remained the same as listed above.

Also, the version listed above for this W95 box are
probably the result of Upgrading of W95 over the last year
or so based on the Microsoft Upgrade Web page for W95
for "critical and security" type Upgrades. I have no idea
how that report of Properties for msvcrt.dll become
related to Windows 2000 Beta (6.10.8637.0) or even if it
is acceptable for a W95 platform.

The only I/O devices connected to this W95 box that may
relate to this situation is a MicroSolutions BackPack CD
R/W Drive conntected to the Parallel (lpt) port with
Drivers loaded and working as expected, plus the AT&T dial
stuff for com1 with an external modem (the latest dialer
for W95 upgrade has been downloaded and upgraded to this
W95 Box). Both devices are working as expected.

There is no sound card, internal modem, or any other
device connected. Plus, ControlPanel/System reports no
device errors.

Boy,,,,any further suggestion would be great!!!

Thanks for your Time, Advise, and HELP!!!! :)

Jerry

-----Original Message-----
Hello Petal,,, :)
Thanks for the REPLY all of this sounds promising,,,,,,,
and I am now working on the items you listed.
I will let you know the results as soon as possible!!!:)
THANKS again for your Time, Help, and Advise!!! :)
Jerry

-----Original Message-----
Hi Jerry
I've been searching around for similar errors to try and

help on this. The

commonest suggestion is that there is a

missing/incorrect

DLL - possibly,

although DEPENDS shows no missing DLL, there may be a

missing entry point or

something? I'm not a programmer so don't know the right

terminology. On that

1) try RegDrop from http://www.addisonsw.com/ - haven't

used it myself, but

maybe it'll do what it says on the tin (informative

errors).

2) "open the ocx file with QuickView (right-click within

Explorer) and look

in the "Imported-Name Table (Link-Time Imports)"

section. This will list

required dll's." - if you can find a working box,

compare

DLL versions

(maybe try copying over from W98?)
3) hack it with notepad to see internal references - on

my W2K box usual

suspects are there (ADVAPI32, SHELL32, KERNEL32, USER32,

OLE32, OLEAUT32,

MPR, SCRRUN, MSVCRT)
3) "replace comcat.dll version 5.0 with 4.71 (copied

from

another box)..."

4) try an updated version of MSVCRT.DLL (latest W95

version from

http://www.microsoft.com/windows95/downloads/contents/WUR

e

commended/S_WUServicePacks/MFCLibrary/Default.asp)

5) try installing a Visual Studio or recent Office

product to see if this

will provide the necessary updates...
regards
petal
.

.