-
Register an OCX
Can somebody help with these questions?
What does the Loadwc.exe program do?
Why is it on the task list (CTRL+ALT+DEL) when I boot Windows 95?
After downloading and installing the Windows Script engine update file mentioned in MSKB 308260, I get the message below when tryingto close the installation window.
"Windows Script 5.6
Error registering the OCX C:\WINDOWS\SYSTEM\WSHOM.OCX"
After clicking OK I get:
"Windows Script 5.6 is now installed."
Do I need to register it?
How do I register WSHOM.OCX?
(The WSHOM.OCX file is in the C:\WINDOWS\SYSTEM folder)
-
Re: Register an OCX
Description of the Loadwc.exe File in Internet Explorer
******
At the C:\WINDOWS\SYSTEM\> prompt, issue the command regsvr32 WSHOM.OCX .
For more information, check Explanation of Regsvr32 Usage and Error Messages.
-
-
-
I tried the regsvr32 wshom.ocx command from a command prompt after starting Windows 95 in normal mode, and get the following:
Regsvr32
LoadLibrary ("wshom.ocx") failed.
GetLastError returns 0x0000001f. OK
According to Microsoft, this is caused by a 16-bit version of the object or some such thing.
So, i tried to rerun scr56en.exe to recreate the wshom.ocx file after
I renamed the wshom.ocx to wshom.xco
I get this again:
LoadLibrary ("wshom") failed.
GetLastError returns 0x0000001f. OK
-
The error could be related to the more "16-bittedness" of Win95 as compared to Win98 (not that Win98 is that much more 32-bit than Win95, as the Pentium Pro processor will reveal.)
-
Yeah,
That's what I was thinking, also.
I did notice the requirements before downloading but wanted to try it anyway. (It seems to have fixed my scripting error)
But, let's say that's the problem.....where can I get the latest Windows 95 scripting engine file update or (install the original from cab files on my hard drive)?
Thanks
-
The link below provides some information.
http://support.microsoft.com/default...b;EN-US;146219
How can I
1. Verify in the Registry that the control has not been registered before?
-
A registered .OCX will have several Registry entries, unregistering the .OCX may not always remove those entries. Perhaps there are entries that have conflicting version information or something....
All very 'iffy' information, I'm sure-- you'd think Microsoft could have been more clear. Sometimes, they explain how to go to Device Manager but here they don't explain this seemingly more complicated task...