Looking to the latest version.
My version is of 24-08-96 410 kb.
>Looking to the latest version.
>My version is of 24-08-96 410 kb.
You don't need the "latest" version, which would be for Windows XP.
You need the right version for your specific version of Windows.
Locate your kernel32.dll in Windows Explorer, right-click on the file
name and select Properties. Go to the version tab and make note of
the version number.
Then open Control Panel - System - General and make note of your
Windows version number, which will be one of the following 4:
4.00.950
4.00.950a
4.00.950B
4.00.950C
Post that information back here.
Also please include some additional details and descriptions of the
reason(s) why you think you need an updated version of kernel32.dll.
Good luck
Ron Martell Duncan B.C. Canada

Signature
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca
"The reason computer chips are so small is computers don't eat much."
Matthew Denton - 19 Mar 2004 01:14 GMT
>-----Original Message-----
>
[quoted text clipped - 24 lines]
>
>Ron Martell Duncan B.C. Canada
for Windows 95. It creating errors when I try to run some
programs. My system is version 4.00.950B Kernel32.dll is
version 4.00.1111
Ron Martell - 19 Mar 2004 02:17 GMT
>I'm also looking for the lastest version of kernel32.dll
>for Windows 95. It creating errors when I try to run some
>programs. My system is version 4.00.950B Kernel32.dll is
>version 4.00.1111
It is *extremely* unusual for kernel32.dll to *create* errors in any
version of Windows. In fact the Microsoft Knowledge Base does not
contain a single instance of a known problem where kernel32.dll is the
cause of the error.
The general format of the detailed error messages produced by Windows
95/98/Me is:
<culprit> caused a <type of error> in module <victim> (at <error
address>)
And there is not a single known instance of an error message being
produced that names kernel32.dll as the culprit. There are,
however, a vast number (thousands at least) of known instances where
kernel32.dll is the *victim*.
"Blaming the victim" is not generally a productive way of solving any
sort of problem situation. Usually it is more appropriate to focus
attention on the culprit.
When you get another one of these errors click on the Details button
in the error message and make note of the first part of the Detailed
Error Message, up to the word Registers:. Use this information to
check out the error further at MVP Jim Eshelman's kernel32 errors page
at http://aumha.org/win4/a/kernel32.htm
Good luck
Ron Martell Duncan B.C. Canada

Signature
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca
"The reason computer chips are so small is computers don't eat much."