4
47_oldtimer
Hi,
"dependent" is the key to success.
U can register dll-s or ocx-es only, if another file (correct/latest
version)
is already present / registered.
Here a sample:
OS=WIN98SE ... I know it's old, but good for this sample ...
For finding out what a kind of version of XML parser is installed on
the PC, according to MS kb278674, U have to install
xmlversion.exe or
xmlversiontext.exe
U have to extract one of the exe-s, let's say to C:\TEMP by starting
one of these exe-files.
Now U will find next to other files, the file
XMLVersiontext.ocx
I did it with "xmlversiontext.exe" because MS had mentioned somewere
if the machine(PC) had never before done anything with XML there
could be the chance that "xmlversion.exe" and the later test would
be fail.
Now I progressed with the registration process ...
Start | run| regsvr32 [blank] C:\temp\xmlversiontext.ocx
Start that ...
Now there is a message ...
LoadLibrary("C:\temp\xmlversiontext.ocx") failed
GetLastError returns 0x00000485
Now put that 0x00000485 in Google search
(http://www.google.com/intl/en/)
and U will get a lot of answers ...
One of these answers helped me ...
forum.doom9.org/archive/index.php/index.php/t-70118.html
There was mentioned something about vbrun etc.
Now since I know, I never had put in vbrun, I crawled
through my SW collection and found
vbrun60sp5.exe
Ok opened it with an unzipper, writing down the content
of it, with recording of the version numbers of those files
contained in "vbrun60sp5.exe"
So, I found out, on the machine a file "msvbvm60.dll"
was missing.
Ok, now started that exe to install its content.
Great, now "msvbvm60.dll" Version 6.00.8964 is on the machine
RESTART the machine
Another registering try of "xmlversiontext.ocx"
... and SUCCESS
Message:
"DllRegisterServer in C:\temp\xmlversiontext.ocx succeeded"
GREAT
Problem solved
NB: I upgraded my runtime with "vbrun60sp6.exe" for to be uptodate.
During all those searches I found out there is a nice programm called
"PROZESS-EXPLORER"
Links to 'em U will find at MS kb296647
http://support.microsoft.com/kb/296647/en-us
http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx
http://technet.microsoft.com/de-de/sysinternals/bb896653(en-us).aspx
http://download.sysinternals.com/Files/ProcessExplorer.zip
Now with that fine tool U could see all the dependencies.
To return to Scott's story/problem ...
At one of those PCs he mentioned, a certain file was installed
at the other not ...
And to find out which one is not installed U could use
PROZESS-EXPLORER
That' s all folks
.. have fun ...
Regards
Hardy
MUC-Germany
--
47_oldtimer
------------------------------------------------------------------------
47_oldtimer's Profile: http://forums.techarena.in/member.php?userid=37769
View this thread: http://forums.techarena.in/showthread.php?t=16513
http://forums.techarena.in
"dependent" is the key to success.
U can register dll-s or ocx-es only, if another file (correct/latest
version)
is already present / registered.
Here a sample:
OS=WIN98SE ... I know it's old, but good for this sample ...
For finding out what a kind of version of XML parser is installed on
the PC, according to MS kb278674, U have to install
xmlversion.exe or
xmlversiontext.exe
U have to extract one of the exe-s, let's say to C:\TEMP by starting
one of these exe-files.
Now U will find next to other files, the file
XMLVersiontext.ocx
I did it with "xmlversiontext.exe" because MS had mentioned somewere
if the machine(PC) had never before done anything with XML there
could be the chance that "xmlversion.exe" and the later test would
be fail.
Now I progressed with the registration process ...
Start | run| regsvr32 [blank] C:\temp\xmlversiontext.ocx
Start that ...
Now there is a message ...
LoadLibrary("C:\temp\xmlversiontext.ocx") failed
GetLastError returns 0x00000485
Now put that 0x00000485 in Google search
(http://www.google.com/intl/en/)
and U will get a lot of answers ...
One of these answers helped me ...
forum.doom9.org/archive/index.php/index.php/t-70118.html
There was mentioned something about vbrun etc.
Now since I know, I never had put in vbrun, I crawled
through my SW collection and found
vbrun60sp5.exe
Ok opened it with an unzipper, writing down the content
of it, with recording of the version numbers of those files
contained in "vbrun60sp5.exe"
So, I found out, on the machine a file "msvbvm60.dll"
was missing.
Ok, now started that exe to install its content.
Great, now "msvbvm60.dll" Version 6.00.8964 is on the machine
RESTART the machine
Another registering try of "xmlversiontext.ocx"
... and SUCCESS
Message:
"DllRegisterServer in C:\temp\xmlversiontext.ocx succeeded"
GREAT
Problem solved
NB: I upgraded my runtime with "vbrun60sp6.exe" for to be uptodate.
During all those searches I found out there is a nice programm called
"PROZESS-EXPLORER"
Links to 'em U will find at MS kb296647
http://support.microsoft.com/kb/296647/en-us
http://www.microsoft.com/technet/sysinternals/utilities/ProcessExplorer.mspx
http://technet.microsoft.com/de-de/sysinternals/bb896653(en-us).aspx
http://download.sysinternals.com/Files/ProcessExplorer.zip
Now with that fine tool U could see all the dependencies.
To return to Scott's story/problem ...
At one of those PCs he mentioned, a certain file was installed
at the other not ...
And to find out which one is not installed U could use
PROZESS-EXPLORER
That' s all folks
.. have fun ...
Regards
Hardy
MUC-Germany
--
47_oldtimer
------------------------------------------------------------------------
47_oldtimer's Profile: http://forums.techarena.in/member.php?userid=37769
View this thread: http://forums.techarena.in/showthread.php?t=16513
http://forums.techarena.in
