PDA

View Full Version : Stop Error


fryan3095
11-22-2005, 04:58 PM
I have a dual boot Windows XP/Windows 2000 setup.

When attempting to boot W2000, I get an error (WXP is OK) :

STOP: c0000221 (bad image checksum)

The text suggests the shell32.dll may be corrupt or the error may be due to some newly installed software and to restart in the safe mode to remove any such items. However, it will not start in the safe mode when attempting to do so!!

I am trying to replace the shell32.dll in the W2000 directory while using WXP.

However, the W2000 CD has the shell32.dll file listed as shell32.dl_. It renames as shell32.dll.dl_.

How do I extract the shell32.dll???

Any other suggestions are appreciated.

Thanks.

ski
11-23-2005, 11:23 AM
See if renaming the shell32.dll file, and then copying the shell32.dl_ file using the recovery console works.
Go here for instructions on accessing the recovery console:
http://www.winsupersite.com/showcase/win2k_recoverycon.asp

Notes:
1. Copy the shell32.dl_ file to a floppy.
2. Go into BIOS, and make sure the CD-ROM drive is listed ahead of the HD as a boot device.
3. Access the recovery console, and choose the 1st repair option.
4. At the command prompt type "dir C:\windows\system /p" (without the ") and press Enter.
5. If the shell32.dll file is listed in the system folder, then at the command prompt type "Rename C:\Windows\system\shell32.dll shell32.old" (without the "), and press Enter. ( Note: If the shell32.dll file is not listed in the system folder, then repeat step 4, except type "dir C:\windows\system32 /p" )
6. Insert the floppy that has the shell32.dl_ file.
7. At the command prompt type "Copy A:\shell32.dl_ C:\Windows\system" and press Enter (Note: type C:\windows\system32 if the shell32.dll file was found in the system32 folder in step 5)
8. Remove the floppy and CD, and restart the computer.

fryan3095
11-23-2005, 04:43 PM
I was successful in repairing the shell32.dll and the system appeared to be booting ----then I got the message "Explorer.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being generated." ---and the proverbial demon, the clear blue screen appeared.

At one point during a W2000 startup I got a message that one of my drives was corrupted although they had all been tested when I could boot to WXP earlier in my adventures.

After restarting the message "Windows2000 could not start because the following file is missing or corrupt WINDOWS\SYSTEM32\CONFIG\SYSTEM"

They then suggest the repair process again!!

I think it may be time for a clean install on a new HD and use my current 20gig and 5 gig for storage!!!!


Thanks for your help!!!

ski
11-24-2005, 09:37 AM
I think that's a good idea.
But just a suggestion - do not use that problematic HD for any critical storage.

ScottHann
12-09-2005, 11:37 PM
Guys I hope you can help! Last week, while booting my Dell Dimension 8400 I got the BSOD and the following message: "Stop: c0000221 {Bad Image Checksum} The image imagehlp.dll is possibly corrupt. The header checksum does not match the computed checksum." I'm a newbie at computer repair so if someone has a solution you'll need to walk me through it. I have years of invaluable Civil War research on my computer which I haven't backed up since June. When I called Dell they thought it was a problem with the hard drive and replaced them (although I still have the originals with the research on them). These must be returned in a few days. Any ideas? Thanks so much! I'm at my wit's end, and Dell's support has been unhelpful. Scott

ski
12-10-2005, 09:27 AM
Reinstall each original HD one at a time as a Slave drive, and then see if any of the following data recovery tools can retrieve the critical data from them:
http://www.snapfiles.com/Freeware/system/fwdatarecovery.html

ScottHann
12-10-2005, 10:00 AM
Thanks for the advice, but I have no idea what a slave drive is, or how to install it. Sorry, I'm new at this, as I mentioned before.

ski
12-10-2005, 10:51 AM
There is a small plastic piece on the back of the hard drive called a jumper that's placed on small metal pins. Position the jumper so that it's on the set of pins labeled Slave, SL, or similar.

Then, with the computer turned off and its power cable disconnected, connect the Slave hard drive to the flat ribbon cable that's NOT attached to the other Master hard drive.
If the Slave hard drive's cable has 2 other drives attached to it, then disconnect one of them in order to attach the Slave drive.
Finally, connect a power lead to the Slave drive, reconnect the computer's power cable, start up, and see if any of the recovery tools in my previous post can transfer the Slave drive's critical data to the Master hard drive.
If there is insufficient space on the Master HD to hold all of the data, then you'll have to transfer the data to another storage device, i.e., burn it to a CD or a DVD, save it to a flash drive, etc.

ScottHann
12-10-2005, 11:57 AM
Thanks for all of your help. I have to leave for work soon, so I'll have to give it a try tonight. Scott