View Single Post
  #3  
Old February 2nd 08, 10:43 PM posted to microsoft.public.win98.gen_discussion
glee
External Usenet User
 
Posts: 2,458
Default "Error loading KERNEL" message

When you are going to change major hardware such as the motherboard and processor,
you first need to remove the drivers for everything that is part of that
hardware.....chipset drivers, onboard audio and video, onboard LAN, floppy
controller, hard drive controllers, and so forth. If you did not do that before
changing the hardware, you should do it now from Safe Mode in Win98, as that is the
OS giving you trouble.

Click StartRun, type: scanregw
|click OK|
When prompted, say Yes to backing up the Registry.

Next, if your old or new motherboard uses onmboard video rather than a dedicated
video card, uninstall any display software and drivers, allowing Windows to change
your display adapter to Standard VGA 640x480, and reboot if prompted. Then
uninstall any audio software and drivers that are not part of the new system.

Now restart in Safe Mode, open Device Manager, expand all categories and start
removing devices.
You pretty much need to remove everything except the keyboard/mouse/monitor,
including all the items in the System section of Device Manager as well as in the
Other section, the USB Controllers section, all other drives and controllers,
display adapters, audio controllers, network adapter.

Click OK to close, then start in normal mode. Windows will begin detecting
hardware....when it finds the primary IDE controller and wants to reboot, say no and
let it find the secondary IDE controller too, then reboot at that prompt.
The next restart should find the rest of the current hardware, while the remnants of
the old hardware will no longer be present.

Be sure to then install the chipset drivers from the disc that came with your new
motherboard, reboot, then install the drivers for your display, audio and so forth.

An alternative to deleting individual items in Safe Mode Device Manager, is to open
the Registry Editor and delete the entire Enum key at this location:
HKEY_LOCAL_MACHINE\Enum
Then, shutdown, move the hard drive to the new system, and follow the suggestions
above.
The Safe Mode method is usually safer.
--
Glen Ventura, MS MVP Shell/User, A+
http://dts-l.net/
http://dts-l.net/goodpost.htm


"Olin K. McDaniel" wrote in message
...
Hopefully this won't get too longwinded, but as a bit of background, I
recently upgraded my hardware and wanted to keep all the software as
before. I installed a new M.B. and CPU to go from a 600MHz Pentium 3
unit to a 2.6 GHz Celeron unit. Also I cloned over the multiboot
OS's from drive 1 to another HD, since the older one was showing signs
of failing. The program used for cloning was Acronis True Image.
There were 3 OS's on Drive 1, and they also are now on the newly
installed HDD. The heart of the multiboot system is Powerquest's Boot
Magic, that has worked wonderfully for years. The 3 OS's are DOS 6.22
(rarely used anymore), Windows 98SE (most heavily used) and Windows
2000 Pro (used somewhat).

The problem developed subsequent to several days of allowing the new
M.B. and CPU to install all its drivers, etc.

Essentially, I cannot boot up (on the NEW Hard Disk 1) into Win98SE in
Normal mode - I get an error message that says "Error loading KERNEL.
You must reinstall Windows". BUT - much to my annoyance, it WILL
boot up fully in SAFE mode. Nothing that I've tried has cleared up
this anomaly. I've followed the procedure found on MS's web site
which tells me to "extract Kernel32.dll" from my installation CD and
copy it to the folder Windows\System\, all to no avail, after multiple
efforts. In addition, I've copied it over from the presumed "failing"
hard drive, again with no success. I'm about ready to throw in the
towel - hopefully, someone can give me an out. Before someone asks,
there is NO problem booting up in Win2000 on this drive.

Finally, as a further frustating fact, I can still do the multiboot if
I swap out the new HD 1 to the old failing one. But I don't trust it
lasting much longer.

I'm admittedly out of ideas - and if it should be a problem with the
MBR, then I don't know how to repair it.

Sorry it got this long - and it may not have all the useful info
someone might think would lead to a clue. If so, please tell me what
to check.

Thanks, Olin McDaniel

To reply by email, please remove "abcd" from Return address
-----------------------------------------------------
"Ignorance is treatable, Stupidity is incurable. Sometimes
the difference is hardly distinguishable, however."