ReinitializeCriticalSection problem, XP

Here is my problem, one I have searched for many=20
hours to find out how to fix:

"Procedure entry point ReinitializeCriticalSection could=20
not be located in the dynamic link library KERNEL32.dll"=20
is the warning I get when opening certain programs. When I=20
click on OK, the programs open and work normally. I have=20
done searches of Microsoft and newsgroups and find=20
the following answer for NT users many times,=20
but not once for XP users (I use XP Home). They say that a=20
program that was installed replaced the url.dll file with=20
an earlier version. They say to first go to your=20
Windows\System 32 folder (by the way, I have this dll=20
in three places, once in C:\WINDOWS\SYSTEM32,=20
once in C:\WINDOWS\SYSTEM32\DLLCACHE, and=20
once in C:\I386) and rename url.dll to url.old,=20
then go to the installation disk and find under the=20
i386 folder, url.dll, then "expand" that file to your
System 32 folder. First, is this the problem? Second,=20
even if this is the problem, is the solution the same in XP
as in Nt?

I checked the version of the url.dll file in my computer's system 32=20
folder and it is the same version as my Internet Explorer=20
(6.0.2800), so it sounds like that is the correct version=20
of url.dll in my machine and thus this may not be the=20
problem.=20

Third, I am a little hazy on how to fix this even=20
if the stated reason for the problem above actually is the=20
problem. So, is this the actual problem, and could someone=20
please help me fix this? Thans very much in advance!

Windows XP (Home or Pro) is based on the same Kernal as NT and Windows 2000,
often solutions you find for problems like this that reference NT will work
for XP.

XP has a built in file checker that will make sure that core files are
installed correctly and that they are the right version. I'm not sure if
this checker covers url.dll but it is worth running it.

Click on Start Run type sfc /scannow Click Ok

Once the scan is finished reboot and try again.

If you still get the error then try replacing the url.dll file. You may find
that the c:\i386 folder contains a different version number to the one in
c:\windows\system32. If the version is higher in the i386 folder then use
that file.

--
Greg Palmer
MS-MVP Windows - Shell/User
http://www.palmersoft.co.uk
"Lee" wrote in message
...
Here is my problem, one I have searched for many
hours to find out how to fix:

"Procedure entry point ReinitializeCriticalSection could
not be located in the dynamic link library KERNEL32.dll"
is the warning I get when opening certain programs. When I
click on OK, the programs open and work normally. I have
done searches of Microsoft and newsgroups and find
the following answer for NT users many times,
but not once for XP users (I use XP Home). They say that a
program that was installed replaced the url.dll file with
an earlier version. They say to first go to your
Windows\System 32 folder (by the way, I have this dll
in three places, once in C:\WINDOWS\SYSTEM32,
once in C:\WINDOWS\SYSTEM32\DLLCACHE, and
once in C:\I386) and rename url.dll to url.old,
then go to the installation disk and find under the
i386 folder, url.dll, then "expand" that file to your
System 32 folder. First, is this the problem? Second,
even if this is the problem, is the solution the same in XP
as in Nt?

I checked the version of the url.dll file in my computer's system 32
folder and it is the same version as my Internet Explorer
(6.0.2800), so it sounds like that is the correct version
of url.dll in my machine and thus this may not be the
problem.

Third, I am a little hazy on how to fix this even
if the stated reason for the problem above actually is the
problem. So, is this the actual problem, and could someone
please help me fix this? Thans very much in advance!

Thanks for helping, Greg. I did the scan to no avail. All three url.dll =
files are of the same version: 6.0.2800.1106 . That is the same version =
as my Internet Explorer. So it looks like I have the correct version, =
because if the problem is related to what I have read and then written =
below, a software program that was installed would have had to have =
replaced the url.dll file with an earlier version. Nowhere else has =
there been a mention of another possible reason for the =
ReinitializeCriticalSection problem. Any ideas? I really appreciate your =
help.

Lee


"gpalmer711" wrote in message =
...
Windows XP (Home or Pro) is based on the same Kernal as NT and Windows =
2000,=20
often solutions you find for problems like this that reference NT will =
work=20
for XP.
=20
XP has a built in file checker that will make sure that core files are =

installed correctly and that they are the right version. I'm not sure =
if=20
this checker covers url.dll but it is worth running it.
=20
Click on Start Run type sfc /scannow Click Ok
=20
Once the scan is finished reboot and try again.
=20
If you still get the error then try replacing the url.dll file. You =
may find=20
that the c:\i386 folder contains a different version number to the one =
in=20
c:\windows\system32. If the version is higher in the i386 folder then =
use=20
that file.
=20
--=20
Greg Palmer
MS-MVP Windows - Shell/User
http://www.palmersoft.co.uk
"Lee" wrote in message=20
...
Here is my problem, one I have searched for many
hours to find out how to fix:
=20
"Procedure entry point ReinitializeCriticalSection could
not be located in the dynamic link library KERNEL32.dll"
is the warning I get when opening certain programs. When I
click on OK, the programs open and work normally. I have
done searches of Microsoft and newsgroups and find
the following answer for NT users many times,
but not once for XP users (I use XP Home). They say that a
program that was installed replaced the url.dll file with
an earlier version. They say to first go to your
Windows\System 32 folder (by the way, I have this dll
in three places, once in C:\WINDOWS\SYSTEM32,
once in C:\WINDOWS\SYSTEM32\DLLCACHE, and
once in C:\I386) and rename url.dll to url.old,
then go to the installation disk and find under the
i386 folder, url.dll, then "expand" that file to your
System 32 folder. First, is this the problem? Second,
even if this is the problem, is the solution the same in XP
as in Nt?
=20
I checked the version of the url.dll file in my computer's system 32
folder and it is the same version as my Internet Explorer
(6.0.2800), so it sounds like that is the correct version
of url.dll in my machine and thus this may not be the
problem.
=20
Third, I am a little hazy on how to fix this even
if the stated reason for the problem above actually is the
problem. So, is this the actual problem, and could someone
please help me fix this? Thans very much in advance!
=20
=20

It thinks it is on 95/98/ME. Have you set any compatability options.

--=20
----------------------------------------------------------
http://www.uscricket.com
"Lee" wrote in message =
...
Thanks for helping, Greg. I did the scan to no avail. All three url.dll =
files are of the same version: 6.0.2800.1106 . That is the same version =
as my Internet Explorer. So it looks like I have the correct version, =
because if the problem is related to what I have read and then written =
below, a software program that was installed would have had to have =
replaced the url.dll file with an earlier version. Nowhere else has =
there been a mention of another possible reason for the =
ReinitializeCriticalSection problem. Any ideas? I really appreciate your =
help.

Lee


"gpalmer711" wrote in message =
...
Windows XP (Home or Pro) is based on the same Kernal as NT and Windows =
2000,=20
often solutions you find for problems like this that reference NT will =
work=20
for XP.
=20
XP has a built in file checker that will make sure that core files are =

installed correctly and that they are the right version. I'm not sure =
if=20
this checker covers url.dll but it is worth running it.
=20
Click on Start Run type sfc /scannow Click Ok
=20
Once the scan is finished reboot and try again.
=20
If you still get the error then try replacing the url.dll file. You =
may find=20
that the c:\i386 folder contains a different version number to the one =
in=20
c:\windows\system32. If the version is higher in the i386 folder then =
use=20
that file.
=20
--=20
Greg Palmer
MS-MVP Windows - Shell/User
http://www.palmersoft.co.uk
"Lee" wrote in message=20
...
Here is my problem, one I have searched for many
hours to find out how to fix:
=20
"Procedure entry point ReinitializeCriticalSection could
not be located in the dynamic link library KERNEL32.dll"
is the warning I get when opening certain programs. When I
click on OK, the programs open and work normally. I have
done searches of Microsoft and newsgroups and find
the following answer for NT users many times,
but not once for XP users (I use XP Home). They say that a
program that was installed replaced the url.dll file with
an earlier version. They say to first go to your
Windows\System 32 folder (by the way, I have this dll
in three places, once in C:\WINDOWS\SYSTEM32,
once in C:\WINDOWS\SYSTEM32\DLLCACHE, and
once in C:\I386) and rename url.dll to url.old,
then go to the installation disk and find under the
i386 folder, url.dll, then "expand" that file to your
System 32 folder. First, is this the problem? Second,
even if this is the problem, is the solution the same in XP
as in Nt?
=20
I checked the version of the url.dll file in my computer's system 32
folder and it is the same version as my Internet Explorer
(6.0.2800), so it sounds like that is the correct version
of url.dll in my machine and thus this may not be the
problem.
=20
Third, I am a little hazy on how to fix this even
if the stated reason for the problem above actually is the
problem. So, is this the actual problem, and could someone
please help me fix this? Thans very much in advance!
=20
=20

David,=20
Thanks for the help. I did the compatibility wizard to no avail. Any =
other ideas?
Thanks,
Lee
"David Candy" wrote in message =
...
It thinks it is on 95/98/ME. Have you set any compatability options.

--=20
----------------------------------------------------------
http://www.uscricket.com
"Lee" wrote in message =
...
Thanks for helping, Greg. I did the scan to no avail. All three url.dll =
files are of the same version: 6.0.2800.1106 . That is the same version =
as my Internet Explorer. So it looks like I have the correct version, =
because if the problem is related to what I have read and then written =
below, a software program that was installed would have had to have =
replaced the url.dll file with an earlier version. Nowhere else has =
there been a mention of another possible reason for the =
ReinitializeCriticalSection problem. Any ideas? I really appreciate your =
help.

Lee


"gpalmer711" wrote in message =
...
Windows XP (Home or Pro) is based on the same Kernal as NT and Windows =
2000,=20
often solutions you find for problems like this that reference NT will =
work=20
for XP.
=20
XP has a built in file checker that will make sure that core files are =

installed correctly and that they are the right version. I'm not sure =
if=20
this checker covers url.dll but it is worth running it.
=20
Click on Start Run type sfc /scannow Click Ok
=20
Once the scan is finished reboot and try again.
=20
If you still get the error then try replacing the url.dll file. You =
may find=20
that the c:\i386 folder contains a different version number to the one =
in=20
c:\windows\system32. If the version is higher in the i386 folder then =
use=20
that file.
=20
--=20
Greg Palmer
MS-MVP Windows - Shell/User
http://www.palmersoft.co.uk
"Lee" wrote in message=20
...
Here is my problem, one I have searched for many
hours to find out how to fix:
=20
"Procedure entry point ReinitializeCriticalSection could
not be located in the dynamic link library KERNEL32.dll"
is the warning I get when opening certain programs. When I
click on OK, the programs open and work normally. I have
done searches of Microsoft and newsgroups and find
the following answer for NT users many times,
but not once for XP users (I use XP Home). They say that a
program that was installed replaced the url.dll file with
an earlier version. They say to first go to your
Windows\System 32 folder (by the way, I have this dll
in three places, once in C:\WINDOWS\SYSTEM32,
once in C:\WINDOWS\SYSTEM32\DLLCACHE, and
once in C:\I386) and rename url.dll to url.old,
then go to the installation disk and find under the
i386 folder, url.dll, then "expand" that file to your
System 32 folder. First, is this the problem? Second,
even if this is the problem, is the solution the same in XP
as in Nt?
=20
I checked the version of the url.dll file in my computer's system 32
folder and it is the same version as my Internet Explorer
(6.0.2800), so it sounds like that is the correct version
of url.dll in my machine and thus this may not be the
problem.
=20
Third, I am a little hazy on how to fix this even
if the stated reason for the problem above actually is the
problem. So, is this the actual problem, and could someone
please help me fix this? Thans very much in advance!
=20
=20

Only windows 95, 98, ME programs use this API call as NT has others. =
What makes you think URL.dll is involved (it can be but not necessarly). =
What programs give this error.

--=20
----------------------------------------------------------
http://www.uscricket.com
"Lee" wrote in message =
...
David,=20
Thanks for the help. I did the compatibility wizard to no avail. Any =
other ideas?
Thanks,
Lee
"David Candy" wrote in message =
...
It thinks it is on 95/98/ME. Have you set any compatability options.

--=20
----------------------------------------------------------
http://www.uscricket.com
"Lee" wrote in message =
...
Thanks for helping, Greg. I did the scan to no avail. All three url.dll =
files are of the same version: 6.0.2800.1106 . That is the same version =
as my Internet Explorer. So it looks like I have the correct version, =
because if the problem is related to what I have read and then written =
below, a software program that was installed would have had to have =
replaced the url.dll file with an earlier version. Nowhere else has =
there been a mention of another possible reason for the =
ReinitializeCriticalSection problem. Any ideas? I really appreciate your =
help.

Lee


"gpalmer711" wrote in message =
...
Windows XP (Home or Pro) is based on the same Kernal as NT and Windows =
2000,=20
often solutions you find for problems like this that reference NT will =
work=20
for XP.
=20
XP has a built in file checker that will make sure that core files are =

installed correctly and that they are the right version. I'm not sure =
if=20
this checker covers url.dll but it is worth running it.
=20
Click on Start Run type sfc /scannow Click Ok
=20
Once the scan is finished reboot and try again.
=20
If you still get the error then try replacing the url.dll file. You =
may find=20
that the c:\i386 folder contains a different version number to the one =
in=20
c:\windows\system32. If the version is higher in the i386 folder then =
use=20
that file.
=20
--=20
Greg Palmer
MS-MVP Windows - Shell/User
http://www.palmersoft.co.uk
"Lee" wrote in message=20
...
Here is my problem, one I have searched for many
hours to find out how to fix:
=20
"Procedure entry point ReinitializeCriticalSection could
not be located in the dynamic link library KERNEL32.dll"
is the warning I get when opening certain programs. When I
click on OK, the programs open and work normally. I have
done searches of Microsoft and newsgroups and find
the following answer for NT users many times,
but not once for XP users (I use XP Home). They say that a
program that was installed replaced the url.dll file with
an earlier version. They say to first go to your
Windows\System 32 folder (by the way, I have this dll
in three places, once in C:\WINDOWS\SYSTEM32,
once in C:\WINDOWS\SYSTEM32\DLLCACHE, and
once in C:\I386) and rename url.dll to url.old,
then go to the installation disk and find under the
i386 folder, url.dll, then "expand" that file to your
System 32 folder. First, is this the problem? Second,
even if this is the problem, is the solution the same in XP
as in Nt?
=20
I checked the version of the url.dll file in my computer's system 32
folder and it is the same version as my Internet Explorer
(6.0.2800), so it sounds like that is the correct version
of url.dll in my machine and thus this may not be the
problem.
=20
Third, I am a little hazy on how to fix this even
if the stated reason for the problem above actually is the
problem. So, is this the actual problem, and could someone
please help me fix this? Thans very much in advance!
=20
=20

The reason I thought it might be involved was that the only information =
related to this error that I could find stated that this was a problem =
related to url.dll, and that related to NT. However, now I know that it =
is not involved.

Here are two that have that problem with my computer:

http://netez.com/xplorer2/

http://www.mlin.net/StartupCPL.shtml This one is a very popular =
program.

I really appreciate your help.

Lee

"David Candy" wrote in message =
...
Only windows 95, 98, ME programs use this API call as NT has others. =
What makes you think URL.dll is involved (it can be but not necessarly). =
What programs give this error.

--=20
----------------------------------------------------------
http://www.uscricket.com
"Lee" wrote in message =
...
David,=20
Thanks for the help. I did the compatibility wizard to no avail. Any =
other ideas?
Thanks,
Lee
"David Candy" wrote in message =
...
It thinks it is on 95/98/ME. Have you set any compatability options.

--=20
----------------------------------------------------------
http://www.uscricket.com
"Lee" wrote in message =
...
Thanks for helping, Greg. I did the scan to no avail. All three url.dll =
files are of the same version: 6.0.2800.1106 . That is the same version =
as my Internet Explorer. So it looks like I have the correct version, =
because if the problem is related to what I have read and then written =
below, a software program that was installed would have had to have =
replaced the url.dll file with an earlier version. Nowhere else has =
there been a mention of another possible reason for the =
ReinitializeCriticalSection problem. Any ideas? I really appreciate your =
help.

Lee


"gpalmer711" wrote in message =
...
Windows XP (Home or Pro) is based on the same Kernal as NT and Windows =
2000,=20
often solutions you find for problems like this that reference NT will =
work=20
for XP.
=20
XP has a built in file checker that will make sure that core files are =

installed correctly and that they are the right version. I'm not sure =
if=20
this checker covers url.dll but it is worth running it.
=20
Click on Start Run type sfc /scannow Click Ok
=20
Once the scan is finished reboot and try again.
=20
If you still get the error then try replacing the url.dll file. You =
may find=20
that the c:\i386 folder contains a different version number to the one =
in=20
c:\windows\system32. If the version is higher in the i386 folder then =
use=20
that file.
=20
--=20
Greg Palmer
MS-MVP Windows - Shell/User
http://www.palmersoft.co.uk
"Lee" wrote in message=20
...
Here is my problem, one I have searched for many
hours to find out how to fix:
=20
"Procedure entry point ReinitializeCriticalSection could
not be located in the dynamic link library KERNEL32.dll"
is the warning I get when opening certain programs. When I
click on OK, the programs open and work normally. I have
done searches of Microsoft and newsgroups and find
the following answer for NT users many times,
but not once for XP users (I use XP Home). They say that a
program that was installed replaced the url.dll file with
an earlier version. They say to first go to your
Windows\System 32 folder (by the way, I have this dll
in three places, once in C:\WINDOWS\SYSTEM32,
once in C:\WINDOWS\SYSTEM32\DLLCACHE, and
once in C:\I386) and rename url.dll to url.old,
then go to the installation disk and find under the
i386 folder, url.dll, then "expand" that file to your
System 32 folder. First, is this the problem? Second,
even if this is the problem, is the solution the same in XP
as in Nt?
=20
I checked the version of the url.dll file in my computer's system 32
folder and it is the same version as my Internet Explorer
(6.0.2800), so it sounds like that is the correct version
of url.dll in my machine and thus this may not be the
problem.
=20
Third, I am a little hazy on how to fix this even
if the stated reason for the problem above actually is the
problem. So, is this the actual problem, and could someone
please help me fix this? Thans very much in advance!
=20
=20