Chapter 16 Projects

PROJECT 16-1: Digging Deeper into System File Checker

The System File Checker tool can be used to find and replace corrupted Vista system files. The tool
keeps a log of its actions, and, if it cannot replace a corrupted file, you can find that information
in the log file. Then you can manually replace the file. Locate the Microsoft Knowledge Base
Article 929833 at the support.microsoft.com site. Do whatever research is necessary to understand
the steps in the article to manually replace a corrupted file and answer these questions:

1. What are other parameters for the sfc command besides /scannow?

2. Explain the purpose of the findstr command when finding the log file.

This command helps you locate matches through strings or file names of characters located inside the files.
 3. Can a filename other than sfcdetails.txt be used in the findstr command line? Explain
your answer.

Yes because findstr command is it's own command.

4. What is the purpose of the edit command?

You are able to edit text files.

5. Explain the purpose of the takeown command when replacing a system file.

This command allows you to administrate the file anyway you want it but with out the admin power you cannot edit protected system files.

6. Explain why the icacls command is needed in the process.

This is like the Access Control List where you have access to files.

7. List some ways that you can locate a known good copy of the corrupted system file.

You can find them in the recovery/backup disks, installation discs and the systems recovery partition.



PROJECT 16-2: Practice Using the Recovery Console

To get some practice using the Recovery Console, first boot from your Windows 2000/XP
setup CD and load the Recovery Console. Then do the following: 

( I can't do this project fully because I am using a virtual machine, and I don't have an actual computer with these Operating Systems. I'm not sure how to make Windows XP go in to the Recovery Console on a virtual machine. I won't be able to to this project properly at 100 percent.)

1. Get a directory listing of C:\. Are files normally hidden in Windows Explorer displayed in
the list? Yes

2. Create a folder on your hard drive named C:\Temp. 

3. List the files contained in the Drivers.cab cabinet file.

4. Expand one of these files and put it in the C:\Temp folder. 

 

5. Exit the Recovery Console and reboot.

PROJECT 16-3: More Practice with Recovery Console

Using Windows Explorer, rename the Ntldr file in the root directory of drive C. Reboot the
system. What error message do you see? Now use Recovery Console to restore Ntldr without
using the renamed Ntldr file on drive C. Copy the file from the Windows setup CD to
drive C. List the commands you used to do the job.

I can't fully do this project but I have done some research on google about this project. If Ntldr isn't located on the computer then the computer can't load up or boot up correctly. If you rename the Ntldr file then I assume the file goes missing. This link is about how NTLDR is missing and how to solve it.
Here is the the link: http://www.computerhope.com/issues/ch000465.htm

The full error messages are like this:

NTLDR is Missing
Press any key to restart
Please insert another disk
Press Ctrl Alt Del to Restart
Boot: Couldn't find NTLDR

Here is the solution for XP Users:

Windows XP users
Insert the Windows XP bootable CD into the computer.
When prompted to press any key to boot from the CD, press any key.
Once in the Windows XP setup menu press the "R" key to repair Windows.
Log into your Windows installation by pressing the "1" key and pressing enter.
You will then be prompted for your administrator password, enter that password.
Copy the below two files to the root directory of the primary hard drive. In the below example we are copying these files from the CD-ROM drive letter, which in this case is "e." This letter may be different on your computer.

copy e:\i386\ntldr c:\
copy e:\i386\ntdetect.com c:\
Once both of these files have been successfully copied, remove the CD from the computer and reboot.


PROJECT 16-4: Sabotage a Windows XP System

In a lab environment, follow these steps to find out if you can corrupt a Windows XP
system so that it will not boot, and then repair the system.

1. Looking at Figure 16-22, make a list of the user-mode processes critical to Windows XP.
2. Rename or move one of the program files shown in Figure 16-22. Which program file did
you select? In what Windows folder did you find it?

I picked services.exe and the path for this exe file is C\:Windows\System32

3. Restart your system. Did an error occur? Check in Explorer. Is the file restored? What
Windows feature repaired the problem? 

Yes an error occured but I restored it by using System Restore

4. Try other methods of sabotaging the Windows XP system, but carefully record exactly
what you did to sabotage the boot. Can you make the boot fail?

You can make a boot fail I am sure if you delete important files deep with in a root directory.

5. Now recover the Windows XP system. List the steps you took to get the system back to
good working order. 

You want to use a fixntldr.exe and burn the ISO on a blank CD. This will fix the boot up on Windows XP.



PROJECT 16-5: Using a Windows 2000/XP Boot Disk

Create a Windows 2000/XP boot disk and use it to boot your computer. Describe how the
boot worked differently from booting entirely from the hard drive.

(I'm not able to do this project because I don't have the software or free computer to do this project.)