The Shell.dll file is a key system file. It is a favorite target of virus
and spyware . Scan with your up to date antiviral and antispyware utilities.
Run the WinXP Recovery Console to repair any hard drive errors that might
have damaged the file. Inserting the Windows setup CD in the computer and
rebooting the system. When the Welcome To Setup menu displays, press R and
then press ENTER to access the Recovery Console.
Following the on-screen instructions. Log into Windows and enter the
administrator's password (if there is one). A command prompt will eventually
appear on-screen; when it does, type chkdsk /r and press ENTER.
When the disk scan is complete, perform an in place upgrade to reinstall the
Shell.dll file and any other corrupted or damaged system files.
To do this boot using the Windows setup CD to boot the machine and access
the Welcome To Setup menu. Rather than press R, however, press ENTER this
time to set up WinXP. Follow the on-screen instructions to accept the EULA
(End-User License Agreement), after which setup will ask whether you wants
to repair an existing installation of Windows. Answer yes. Highlighting the
drive on which Windows is installed and pressing R.
Windows Setup will handle the situation from here. It will reinstall key
system files, restart the PC ( remove the installation disc before the
computer reboots), and proceed with the rest of the reinstall. Windows
should reboot normally.
You need a windows set up CD at the same service pack lever for the above
to work. Another way to do it and you are sure that your OS is clean is to
copy the shell.dll file from another machine or place to the correct
directory on the problem one or to run system file checker.
Actually you should try sfc before the repair/in place install that is
referred to above.
Start>Run>sfc /scannow. You might need your windows set up CD if a i386
folder was not copied to your hard drive before. The windows set up CD must
be at the same SP level for sfc to work using the CD.
Remember to always backup your important file before trying to repair or
make any changes to your machine.
"marioB52" <marioB52@cox.net.(donotspam)> wrote in message
news:29DD3624-7B01-4E9A-B9C4-231F4B2D8944@microsoft.com...
