ReinitializeCriticalSection not located in Kernel32.dll

rlegg · 10th April 2001, 20:48

An error message must be acknowledged manually before the succeeding track in the playlist will start.

"OleMainThreadWndName:winamp.exe Entry Point Not Found. The procedure entry point ReinitializeCriticalSection could not be located in Kernel32.dll"

So; do I just fiddle with pluggins? Kernel32 is used everywhere.

Last time OleMainThreadWndName errors were reported, there were crashes involved. This is just an inconvenience, disables the intended function of a playlist.

Rob

peter · 10th April 2001, 21:37

try removing third-party plug-ins. it is possible that your windows is messed up and you will have to reinstall it.
what windows version do you have ? nt ? 2k ? me ?

[Edited by PP on 04-10-2001 at 05:56 PM]

rlegg · 11th April 2001, 01:43

This is using NT4

Winamp is installed in folder of partition separate from OS.

The system has provided fair stability. Not too many toys installed. Used mostly for CAD, Com and Docs.

How do you define or identify 3rd party dlls?

RL

peter · 11th April 2001, 13:43

third party plug-ins = those not bundled with Winamp setup
try searching your Winamp folder for a file containing "ReinitializeCriticalSection" - it might enable you to find who is to blame (or search your whole hard drive, heh). are you sure that you didn't install anything that was supposed to run on win2k only ?

rlegg · 11th April 2001, 14:58

How would you perform such a 'text' search?

I doubt the text string is associated directly with the bug. They are merely text displayed in the error message.

Most of the SW on this machine was running before Win2k or ME was concieved.

Why would anyone, in their right mind, intentionally create SW specifically for either?

peter · 11th April 2001, 16:37

text search ? use simple windows' file search function (winlogo key + F)
are you sure that you have written that error down correctly ? that function name - "ReinitializeCriticalSection" sounds strange. there are similar functions in kernel32.dll, but i haven't heard about this one (msvc5 docs don't mention it) so i assume that it is something new specific to win2k (or some recent nt4 sp). maybe you should (re)install the latest service pack.

rlegg · 11th April 2001, 21:32

The error message is letter/punc/spacing copy, though I can't be too sure whether there were spaces around the colon, or not. The only plug-ins present are those from the initial installation.

The windows 'find' function only recognizes file or folder names. There is no reason for any of the text in the error message to show up there (and it does not), with the exception of the identified system dll.

I'm not too sure I want to re-install SP4 of NT4, because there were a considerable number of loose ends, biult-in, that would have to be cleaned up again. Its a matter of resources and time here.

Considering that I use Winamp infrequently, it doesn't seem worth the time it would take to carry this matter further. It is, after all, only an inconvenience. I note it for the possible benefit of other users and to attract known solutions for the knowledge base.

who_am_i · 12th April 2001, 00:02

The Windows Find thing does find text within files also; look for the "Containing Text" textbox

I realize this does nothing to solve your problem though.. it is really unlikely that you will find that anyway unless it is simply a message box's text..

peter · 12th April 2001, 00:49

none of Winamp's components use anything called 'ReinitializeCriticalSecion'; this is NOT a fault of Winamp. if you want to find who is to blame, scan your whole hdd (and have patience).

rlegg · 12th April 2001, 13:56

Noticed that the Winamp revision in question was 2.5C.

Removed this and installed rev 2.74.

The previously noted error message occurs ONCE only during installation of this rev.

It does not re-occur in subsequent normal program use, and is therefor no longer a nuisance.

11th April 2001, 01:43	#3
rlegg Junior Member Join Date: Apr 2001 Posts: 5	RCS not located in Kernel32.dll This is using NT4 Winamp is installed in folder of partition separate from OS. The system has provided fair stability. Not too many toys installed. Used mostly for CAD, Com and Docs. How do you define or identify 3rd party dlls? RL

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

10th April 2001, 20:48	#1
rlegg Junior Member Join Date: Apr 2001 Posts: 5	An error message must be acknowledged manually before the succeeding track in the playlist will start. "OleMainThreadWndName:winamp.exe Entry Point Not Found. The procedure entry point ReinitializeCriticalSection could not be located in Kernel32.dll" So; do I just fiddle with pluggins? Kernel32 is used everywhere. Last time OleMainThreadWndName errors were reported, there were crashes involved. This is just an inconvenience, disables the intended function of a playlist. Rob

10th April 2001, 21:37	#2
peter ist death Join Date: May 2000 Posts: 3,704	try removing third-party plug-ins. it is possible that your windows is messed up and you will have to reinstall it. what windows version do you have ? nt ? 2k ? me ? [Edited by PP on 04-10-2001 at 05:56 PM]

11th April 2001, 13:43	#4
peter ist death Join Date: May 2000 Posts: 3,704	third party plug-ins = those not bundled with Winamp setup try searching your Winamp folder for a file containing "ReinitializeCriticalSection" - it might enable you to find who is to blame (or search your whole hard drive, heh). are you sure that you didn't install anything that was supposed to run on win2k only ?

11th April 2001, 14:58	#5
rlegg Junior Member Join Date: Apr 2001 Posts: 5	How would you perform such a 'text' search? I doubt the text string is associated directly with the bug. They are merely text displayed in the error message. Most of the SW on this machine was running before Win2k or ME was concieved. Why would anyone, in their right mind, intentionally create SW specifically for either?

11th April 2001, 16:37	#6
peter ist death Join Date: May 2000 Posts: 3,704	text search ? use simple windows' file search function (winlogo key + F) are you sure that you have written that error down correctly ? that function name - "ReinitializeCriticalSection" sounds strange. there are similar functions in kernel32.dll, but i haven't heard about this one (msvc5 docs don't mention it) so i assume that it is something new specific to win2k (or some recent nt4 sp). maybe you should (re)install the latest service pack.

11th April 2001, 21:32	#7
rlegg Junior Member Join Date: Apr 2001 Posts: 5	The error message is letter/punc/spacing copy, though I can't be too sure whether there were spaces around the colon, or not. The only plug-ins present are those from the initial installation. The windows 'find' function only recognizes file or folder names. There is no reason for any of the text in the error message to show up there (and it does not), with the exception of the identified system dll. I'm not too sure I want to re-install SP4 of NT4, because there were a considerable number of loose ends, biult-in, that would have to be cleaned up again. Its a matter of resources and time here. Considering that I use Winamp infrequently, it doesn't seem worth the time it would take to carry this matter further. It is, after all, only an inconvenience. I note it for the possible benefit of other users and to attract known solutions for the knowledge base.

12th April 2001, 00:02	#8
who_am_i Junior Member Join Date: Apr 2001 Posts: 15	The Windows Find thing does find text within files also; look for the "Containing Text" textbox I realize this does nothing to solve your problem though.. it is really unlikely that you will find that anyway unless it is simply a message box's text..

12th April 2001, 00:49	#9
peter ist death Join Date: May 2000 Posts: 3,704	none of Winamp's components use anything called 'ReinitializeCriticalSecion'; this is NOT a fault of Winamp. if you want to find who is to blame, scan your whole hdd (and have patience).

12th April 2001, 13:56	#10
rlegg Junior Member Join Date: Apr 2001 Posts: 5	Noticed that the Winamp revision in question was 2.5C. Removed this and installed rev 2.74. The previously noted error message occurs ONCE only during installation of this rev. It does not re-occur in subsequent normal program use, and is therefor no longer a nuisance.