The Netscape Knowledge Base Article 19970820-45, lists several different solutions for this error. However, this particular Article is somewhat outdated, and you might want to try the following solution first. I have found it to be immediately effective in eliminating the KERNEL32.DLL error, which, for the most part, is caused by a corrupt Netscape Registry file (nsreg.dat):
With Communicator closed:
Delete the nsreg.dat file, found in C:\WINDOWS, or rename the file to nsreg.bak. This is your Netscape Registry file.
Start Communicator
The User Profile Manager will prompt for a new User Profile Name. Enter the EXACT SAME NAME OF THE CURRENT USER PROFILE.
Windows will then ask the following:
The directory you specified appears to already contain profile data. Would you like to use profile data that already exists in this directory? Answer YES.
This should solve your KERNEL32.DLL error. If not, try the solutions offered below:
Ramona
----------
Subject: Re: Can't open Messenger Netscape 4.7/ KERNEL32.DLL
Date: Sat, 03 Nov 2001 20:06:27 -0800
From: hb
Newsgroups: netscape.communicator
Pastor Secker/Phil wrote:
When I try to open Messenger in Netscape 4.7 I get an Illegal action notice telling me the problem is in kerne132.dll. A support message on that, tells me to set up a new profile, but when I do and try to check to be sure it is working, I am told my password is invalid. I checked all profile information with Snet.net.
As an alternative I tried to download Netscape 6.2 but get this message: A fatal exception has occurred at 0028:C1532867 in VXD VNBT (01) + 00006D27.
I have not tried downloading Netscape 4.78.
Phil
----------
Watch the splash screen for clues. Does it crash when...
Loading bookmarks? Rename the BOOKMARK.HTM file and try again. If that's the problem, open the file with NOTEPAD and look for obvious corruption - long lines, gaps, binary junk - and fix it.
Loading plugins? Move some or all of the DLL files for the plugins from the COMMUNICATOR\PROGRAM\PLUGINS directory to another directory (folder). If that's the problem, move one at a time back to the PLUGINS directory until the culprit is found.
Loading preferences? Rename the NSREG.DAT file in c:\windows to NSREG.BAK.
Then create a new Profile.
--------