Friday, January 16, 2009

Differences between the XP Home and Professional Edition !

Windows XP is based on Windows NT4 and Windows 2000 technology.
Microsoft is positioning the Windows XP Professional Edition to replace Windows NT4 and
Windows 2000 Professional. In addition, the Windows XP Home edition will be replacing
Windows 95/98/ME.

But do NOT expect to receive full Window NT4/2000 functionality when using the XP Home Edition:
There is a substantial difference in price, and that is reflected in some reduced functionality in the
XP Home edition compared to the XP Professional Edition : features turned off !

This is NOT a complete list, I am just listing the features related to networking:

Windows XP Home EditionWindows XP Professional Edition
User managementLimited to 2 security levels,
no policies
Full User Management and
Security Policies
Workgroup networking/
Joining domains
Limited to Workgroup
network (unable to join
a domain)
Workgroup networking and
able to join a Domain
Security on sharing
disks and folders
no security, everybody
has access to shared data
Full security based on
User Management
Limit of simultaneous
file-sharing
connections
max 5 simultaneous
file-sharing connections
max 10 simultaneous
file-sharing connections
Security of disks and
folders (NTFS drives)
limited Security, made
difficult to use
Full Disk/Folder Security based
on User Management
Group Policy
Editor
not includedIncluded
Remote Desktop
Access
not included.Remote Desktop Access
Backup Programonly included via
VALUEADD
Included
ASR Automatic
System Recovery
not includedIncluded

The lack of the possibility to join a domain and the lack of securing a shared network resource
will prevent the use of the XP Home edition in most office networks, even in configurations where
Windows95/98/ME could be used.

More differences will be listed, once I encounter the item during my work.


Backup Program on Windows XP Home :

The default installation of Windows
XP Home does not include a Backup
program (as part of "Programs" /
"Accessories" / "System Tools"







If you have a copy of Windows XP Home on a Recovery CD-ROM : sorry.

If you have a retail copy ( as sold in
the shops) of Windows XP Home,
have a look on the CD-ROM to:
VALUEADD\MSFT\NTBACKUP,
which allows to install now the

Backup program.


READ MORE!

Connecting Windows XP to Multiple Networks: Office and Home

Are you using at work a notebook computer connected to your company network ?

If your company network uses TCP/IP protocol and a network server, then you will have your
notebook most probably configured to get the IP-address via DHCP:

Properties of the Network connection :


When you verify your network settings in the Properties of the Network,
checking the "Status" of your LAN connection:


you should see that your TCP/IP-address was "Assigned by DHCP"


You carry your notebook home and connect it to your home-network, to exchange some
files with other computers used in your family. Most probably there will be no server installed
at your home or another system able to act as DHCP-server, so Windows XP ( like Windows98,
WindowsME and Windows 2000) will now assign an Automatic IP-address:


If all other systems at home are also configured to use this Auto-IP-Address generation,
then you can use the network without having to reconfigure the TCP/IP-settings on your
notebook.

But if you use at home manually assigned IP-addresses (example: 192.168.1.x- range),
then you are required to adjust on your notebook the IP-address to match it up with the
IP-address range used at home.

You have to do this manually on previous versions of Windows.
Windows XP allows you to automate this step: In the Properties of Networking,
display the Properties of your LAN network connection ,
display the Properties of the TCP/IP-protocol and select the tab
"Alternate Configuration" :

By default, Windows XP will assign an IP-address via Automatic IP-address generation,
if no DHCP-server was located on the network.
You have now the possibility to change this, to define to use a "User Defined" setting,
allowing to define a static IP-address to be used in case that no DHCP-server was located :


This will be indicated in the "Status" of your LAN connection:



READ MORE!

Recovering Windows XP using the Recovery Console

Most Windows NT installations used a system-drive ( C: ) with FAT-filesystem, to allow
access to the drive via a DOS-boot-floppy to be able to copy files (like : updated DLL's)
to the system.

These screen dumps have been made using :
"VMWARE Workstation 3.0" of VMWARE.
( more details on this very powerful program )

Windows 2000 and XP allow to use on the system-drive ( C: ) the NTFS-file-system,
maintaining data-security but allowing limited access to the disk via the

Recovery Console

to repair a damaged system (like to fix boot problems).

Insert your Windows 2000 / XP installation CD-ROM and boot from CD-ROM :
(note : some Windows XP Revovery CD-ROM's do not allow to start the Windows SETUP,
in such cases you can try to use to create Windows XP Boot Floppy disks and boot from floppy).

Windows 2000:
On the "Windows 2000 Professional Setup" menu, select "R" for repair :


as Repair option, select "C" to use the "Recovery Console" :


Windows XP:
On the "Windows XP Professional Setup" menu, select "R" for Recovery Console :


Windows 2000 / XP :
You will be prompted to select the Windows installation to repair :
(usually just "1" ) :


You will need to enter the Administrator password !


At the command-prompt, type any valid command.
To get an overview on the supported commands, type : HELP




To get more detailed information on any of these commands, type the commannd followed by "/?",
which will then display the specific Help-information.

You have access to :
- the root directory of all disks
- the Windows system directory (and all sub-directories), usually : C:\WINNT
- to removable disks (floppy disk and CD-ROM drives)

You have NO Access to any other directory !

You can copy files FROM Floppy disk to the directories on disk, to which you have access.
You can NOT copy files from disk to Floppy Disk !


type : EXIT to restart the system.


Recovering from Bootup problems :
When the system displays on booting a message of "missing" NTLDR or NTDETECT,
you can copy these files via Recovery Console from the CD-ROM :

make sure to be on the root of the C:-drive (please make : CD \ ).
In my example, the CD-ROM drive is Drive D: , allowing to make a copy of the files
NTLDR and NTDETECT.COM from the i386-directory to the C:\ - root directory.


If there is a problem with the Boot-sector on the C:-drive, you can use "fixboot" to write
a new boot-sector.
If there is a problem with the Master-Boot-Record of the disk (maybe damaged by a virus),
you can use "fixmbr" to write a new MBR :



Extract files from CAB-files using "expand" :


example: I have copied a CAB-file from CD-ROM, display the content of the CAB-file
using "expand xxx.CAB /d /f:*" and then extract the required files via : "expand xxx.CAB /f:yyy":



Partition problems :
You can use "diskpart" to manage disk partitions :

If called up without an option, you get a simple user-interface :



Services and Devices
Use "listsvc" to display a list of all devices and services :



You can use "enable" and "disable" to switch on/off :




The Recovery Console can be installed on the harddisk as an additional boot-up selection:
at a command-prompt: drive:\i386\Winnt32.exe /cmdcons,
where drive is either the CD-ROM or disk with the Windows XP installation files :


The Windows 2000 Recovert Console has been successfully installed.

To use the Windows 20000 Recovery Console, restart your computer and then select
Windows 2000 Recovery Console from the Startup Menu.

For a list of commands you can use with the Recovery Console, type HELP at the
Recovery Console command Prompt.

When starting up Windows 2000 / XP, there will be a boot-selection menu displayed,
where you can startup Windows or the Recovery Console :




If the default selection is to start the Recovery Console and you like to change it to start Windows,
or if you like to reduce the bootup-delay or if you like to remove the Recovery Console from
the boot-menu, you can change the default boot selection :

In the Control-Panel, select the
System icon:

(or right-click "My Computer" on the desktop
and select Properties)

Select the tab: "Advanced" and
then use in the section :
"Startup and Recovery"
the button :
"Startup and Recovery"

Select from the drop-down menu the system
to boot as default, and define a delay value
(5 sec is a good choice, allowing time to
change the default but not delaying the
boot too long ).

If you think that you do not need the
selection anymore, you can turn off the
display of the boot-menu by un-checking
"Display list of operating systems" :



If you have a Windows XP Recovery CD-ROM, then you may not have the option to select "Recovery Console".
For such cases, Microsoft have made the Windows XP setup process (to get to the Recovery Console) available as
a download via Q310994 in different languages (note: there are different downloads for the Home and Professional Edition).
You have to execute the download file, which will create 6 boot floppies. You then can boot from the first floppy :
You will get first the message : "Setup is inspecting your computer's hardware configuration..."

You will be prompted to insert the additional floppy disks :
Windows Setup

Please insert the disk labeled
Windows XP Professional Setup Disk #2
into Drive A:
Press ENTER when ready


READ MORE!

Troubleshooting Startup Problems

Troubleshooting is merely the methodical application of common sense and technical knowledge to the inevitable problems that crop up in a fallen world. If common sense can be codified (and perhaps it can with AI) then it starts with answers to simple questions like: Why? How? What? In this article I'll try to distill the issues, tools and procedures of troubleshooting Windows XP/2003 boot problems into a small amount of easily digestible information that you as a system administrator can write on the back of a note card or store in your PDA for easy access when the proverbial poop hits the fan. Let's begin with the Why question.

Why do startup problems happen?

Windows may fail to start for a variety of reasons, and generally speaking in order of decreasing likelihood here they are:

  • Hardware failure
  • Bad driver
  • Corrupt file or volume
  • System misconfiguration
  • Virus infection

Let me elaborate. A common reason systems fail to start is because some element of the system's hardware has failed. This could range from the simple (someone kicked the power cord out of its socket) to the obvious (smoke emitting from the machine) to the mysterious (something transient that happens only when the moon is full or during sunspot minimum). Next most common is when you update the driver for some piece of hardware (or the BIOS for that matter) and the system won't boot afterwards. After that comes those mysterious messages we'll talk about shortly that usually indicate some key operating system file has somehow become corrupt or gone missing. Misconfiguration is another possible source of boot problems, but this is somewhat rare as in most cases you'll still be able to boot but one or more services may fail to start or your applications may not function as expected. Finally, virus infection can cause a system to fail to boot, but I've listed this in last place because I'm assuming you've got an antivirus solution in place and you're keeping the antivirus signature files updated, right?

Now that we know why Windows may fail to start properly, let's ask the logical next question: How can we know which of these underlying causes is the one that might be preventing Windows from successfully booting?

How to diagnose startup problems

Here is where we need to apply our brains and use a bit of common sense to determine what the cause of startup failure might be. Think of the previous list above as a list of disease-causing viruses, and now you have to play doctor and figure out which virus the patient (your sick computer) actually might have. For if you skip this step and try blasting the patient with every possible remedy in your doctor's bag, two things may happen:

  • One of the remedies you try may actually make the patient worse and indeed could prove fatal.
  • You'll waste a lot of time and the recovery of your patient will be delayed, and your boss may get upset with you as a result since her business is losing money due to downtime.

So careful diagnosis is a step you should always take time for and never avoid, and just like in the medical profession such diagnosis usually begins with your senses. For example, do you smell something burning? Better unplug your system immediately and wait for things to cool off, then open the case and inspect the damage. Do you hear your CPU fan making a slow grinding sound? Power down your system and replace the fan before your processor burns out and needs replacing. Is your video display flickering? Maybe try reseating the video card after checking if the video cable is seated properly.

OK let's assume its not such a simple and obvious problem. Instead, say you get a black screen with one of the following dreaded messages when you try and boot your system:

  • "NTLDR is missing"
  • "A disk read error occurred"
  • "Invalid partition table"
  • "Error loading operating system"
  • "Could not read from selected boot disk"
  • "Windows could not start because the following file is missing or corrupt"

Or you might get a blue screen (called a STOP screen) with some obscure message on it. Or if you're lucky you might make it all the way through the Windows splash screen to the logon box and then suddenly get a dialog box saying "One or more services failed to start". Or your mouse pointer might freeze and your system hang either before or immediately after logon. How can you match these symptoms to the underlying condition that might be causing them? First let's look at some possible "black screen" messages that can occur after the BIOS POST routine finishes but before the Windows splash screen appears:

Symptom

Probable Cause

  • "Invalid Partition Table"
  • "Missing Operating System"
  • "Invalid Partition Table"

Master boot record is corrupt due to hard disk errors or virus infection

  • "NTLDR is missing"
  • "A disk read error occurred"
  • System hangs after BIOS POST finishes

Boot sector is corrupt due to hard disk errors or virus infection

  • "Windows could not start because of a computer disk hardware configuration problem"
  • "Could not read from selected boot disk"
  • "Check boot path and disk hardware"

Boot.ini file is corrupt, missing, or needs updating.

  • "Windows could not start because the following file is missing or corrupt"

Boot volume is corrupt or the referenced system file is missing.

In addition to these error messages, a variety of other startup problems can occur including:

  • Blue screens. These are typically caused by hardware failure or driver problems but can also be due to virus infection.
  • Hung system. These are typically caused by buggy drivers or by registry corruption but can also be due to virus infection.
  • Dialog box saying "One or more services failed to start". This is typically caused by misconfiguration or registry corruption but can also be caused by application incompatibility of some form.

So what should you do to resolve such problems?

How to resolve startup problems

Like a doctor's mysterious black medical bag full of medical instruments (at least in old movies on TV) the system administrator also has a set of tools provided by Microsoft for resolving startup problems like the ones in the table above. In a nutshell, here's a quick inventory of the main tools:

  • Last known good. Restores the HKLM\System\CurrentControlSet portion of the registry its version during the last successful logon to the system.
  • Safe mode. Starts Windows with a minimal set of drivers and creates a record of which drivers load in %windir%\Ntbtlog.txt.
  • System Restore. Windows XP only feature to restore system to previously saved configuration.
  • Recovery Console. Boots to a command line that allows you to run various commands, see this article by Johannes Helmig for more info.
  • Automated System Recovery (ASR). Restores the boot volume from backup, see this article by Johannes Helmig for more info.
  • Repair. Run Windows Setup from your product CD and select the option to try and repair your installation.

Which tool should you use to address each of the symptoms we described earlier? Assuming there is no obvious hardware problem (no funny smell) and you've already asked yourself the Golden Question ("What was the last thing I did to this system?") then here's a quick outline that maps the type of knife (may be several in order of severity) to the kind of surgery (underlying problem or visible symptom) you need to perform on your system:

Problem/Symptom

Tool(s) to Use

Corrupt master boot record

Recovery Console (fixmbr)

Corrupt boot sector

Recovery Console (fixboot)

Corrupt or missing boot.ini

Recovery Console (bootcfg /rebuild)

Corrupt system file

Recovery Console (chkdsk)
Restore from ASR backup
Perform a Repair install

Corrupt registry

Recovery Console (chkdsk)
System Restore (XP only)
Restore system state from backup
Perform a Repair install

Blue screen

See this resource first
Last known good
System Restore (XP only)
Safe mode (roll back suspect driver using Device Manager)

Hung system

Last known good
System Restore (XP only)
Safe mode (roll back suspect driver using Device Manager)

"One or more services failed to start"

Don't logon! Reboot and select last known good, log on, undo the last configuration steps you performed.
Safe mode (undo last configuration steps you performed)


Conclusion

A good physician understands diseases, can recognize their symptoms, and knows how best to treat them. Fortunately if you toast your system while trying to repair a startup problem, you can always buy another. But by using a combination of common sense and an understanding of the causes of, symptoms of, and tools for treating startup problems, you can usually bring your systems back to perfect health and earn your pay as a system administrator!


READ MORE!

Building and Using a Windows XP Boot Disk

In this article we will learn how to make a boot disk for a Windows XP system. A boot disk can start the operating system on a computer running Windows XP if it will not boot properly and the damage is suspected to be in the files that start Windows.

Use the procedures in this article to work around the problems that hinder your system from starting. Problems that can occur are (but not limited to) boot sector damage, missing files, a virus, improper drivers and so on. In this article this is what we cover. We cover some terminology and the boot process, possible problems and situations and then show you how to make a boot disk and use it. A non booting Server is not a good thing when it’s hosting a thousand web pages for a company. I recommend this disk be created and kept nearby in case you are in a jam and need to get a system up and running that will not boot.

Terminology

In this section we will cover terminology that will be used throughout the chapter and define it.

  • POST: Power On Self Test. When a computer starts or boots, the BIOS carries out a procedure that verifies that all the system's components are operating properly. Hearing beeps are indicators of a BIOS trying to either indicate a successful transition, or it’s giving you a beep code that helps you figure out a problem most likely in the BIOS.
  • MBR: Short for Master Boot Record, a small program that is executed when a computer boots up. Typically, the MBR resides on the first sector of the hard disk. The program begins the boot process by looking up the partition table to determine which partition to use for booting
  • BIOS: An abbreviation for Basic Input/Output System. On PC systems, the BIOS is used to perform all necessary functions to properly initialize that system’s hardware when power is first applied. The BIOS also helps with the boot process.
  • CMOS: Complementary Metal Oxide Semiconductor. A chip which uses small amounts of electricity. It is used typically on battery-powered computers and to save configuration information on other computers when they are turned off.

Boot Process

The boot process once understood will help you visualize why putting certain files on a floppy disk will help you so much. Let’s look at the boot process. Click to visit Microsoft.

  • The first thing that happens when you power on your PC is you have a POST. The POST stands for Power on Self Test and it tests your system hardware.
  • Hardware such as Memory is tested as well as all other hardware on the system being verified. This can usually be seen on the monitor as the system starts.
  • Once POST completes, the PC will attempt to locate a bootable device configured via the system BIOS/CMOS.
  • Once the bootable device is found, the MBR (Master Boot Record) is loaded into memory
  • The MBR locates the active partition and loads the boot sector into memory.
  • The boot sector contains the code that starts Ntldr which is the boot strap loader for Windows XP. Ntldr must be located in root folder of the active partition along with Ntdetect.com, boot.ini, bootsect.dos (for dual booting) and Ntbootdd.sys (needed with some SCSI adapters)
  • The operating system is ‘selected’ by NTLDR.
  • NTLDR will use the Ntdetect.com, boot.ini, and bootsect.dos files to get the proper OS selected and loaded
  • The system starts in 16-bit real mode, then moves to protected mode at 32-bit.
  • Once NTLDR switches into 32-bit mode, the file system is loaded (NTFS, FAT32, etc) so that the boot.ini can be read and then checked.
  • Once the boot.ini is checked, you select the OS you would like to load.
  • Selecting XP from the boot menu causes Ntldr to run Ntdetect.com to get information about installed hardware.
  • Ntldr then uses the ARC path specified in the boot.ini to find the boot partition. It may look something like this:

default=multi (0)disk (0)partition (2) \WINDOWS
[operating systems]
multi(0)disk(0)partition(2)\WINDOWS="Microsoft Windows XP" /fastdetect

  • Ntdetect.com can start to gather information about your systems hardware (such as):
      • Computer ID
      • Bus/adapter type
      • SCSI adapters
      • video adapters
      • keyboard
      • Com ports
      • Parallel ports
      • Floppy disks
      • Pointing devices
  • Once Ntdetect.com collects the needed information, NTLDR loads Ntoskrnl and passes control to it.
  • Ntoskrnl.exe and hal.dll are loaded. Ntoskrnl.exe and Hal.dll must be located in the %SystemRoot%\System32 folder.
  • Next, the Registry is loaded and a hardware profile is selected. If you have multiple hardware profiles created, you may be asked to select from one to load.
  • After you have selected the proper hardware profile (or if the default one just loads), then you will next be greeted by the login prompt.
  • Ntoskrnl.exe starts Winlogon.exe which starts Lsass.exe (Local Security Administration), this is the program that displays the Welcome screen and allows a user to log on with their credentials (user name and password).

To get to this point, you have to have a healthy set of files to get you there. As with any other data, they are prone to corruption, damage or sabotage just like any other source of data. A boot disk is nothing more than a set of the most critical files that if they become damaged need to be replaced to allow the system to boot and load. You can use a boot disk in a time of disaster to get the system to the winlogon process and running to get to critical data or to bring the server up and operational to serve.

Booting Problems

Problems occur, issues arise, and most times it’s unavoidable. Corruption or a boot sector virus can render just about any system dead in the water. So what could happen? In this section we cover some basic issues that can occur so that you just what your up against and why a boot disk can be very handy.

Boot Disk 101

Now that you know the boot process and can see what could happen to hinder that process, let’s look at how to make and use the boot disk.

To create a boot disk for Windows XP for an NTFS or FAT Partition you will need to have a formatted floppy. It needs to be blank and virus free. You will also need the Windows XP CD-ROM or an operational Windows XP-based computer.

  1. Format your Floppy.

  1. Copy needed files (Ntldr, Ntdetect.com, and the boot.ini. Copy them from a system running Windows XP as long as it’s not virus infested and/or a Windows XP setup CD-ROM.
  2. Edit the boot.ini file you copied over to floppy. You will need to set the path correctly so you will need to understand the ARC naming convention. You will find what you need to know using Microsoft’s documentation.
  3. Start your computer by using the floppy disk, and then log on to Windows XP.

Boot.ini Example:

[boot loader]
timeout=30
Default= multi(0)disk(0)rdisk(0)partition(1)\windows
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\windows="Windows XP"

Note:

  • If your computer boots from a SCSI hard drive, you may need to replace the multi(0) entry with scsi(0) under [operating systems]
  • It is possible to disable the Windows XP boot splash screen and speeds up the boot process very slightly. Its more so if you would like practice editing the *.ini file and if you want to 'see' the boot process that this logo hides
    • Edit the boot.ini
    • Add " /noguiboot" right after "/fastdetect".
    • Once you reboot the splash screen will be gone.
    • It can be re-enabled by removing the new switch

Troubleshooting

At times, even if you use the boot disk, you may still encounter solvable problems. Its not ‘that’ easy to use so lets look at some helpers and tips to get you through the most common jams:

  • You may want to put a copy of edit on the boot disk to edit the boot.ini file with.
  • The Boot.ini file will most always be the problem with the boot disk unless the boot disk is corrupted, damaged, infected, etc.
  • You may see error messages about ‘ARC’ and if you do, its very common that your boot.ini file is not configured properly. If you don’t know the boot.ini syntax inside and out, then you may want to print out a copy of it and keep it with your boot disk or put a small text file on the floppy as well with a simple explanation so you can figure it out if you need to.
  • 3rd party companies (makers of NTFSDOS for example) have products that can ‘mount’ an NTFS drive which can allow you to copy the files if needed (if you don’t have a FAT partition to get into), as well, to see the boot.ini current to the system if you need to get ideas on what was in the boot.ini in the original system that failed.

READ MORE!

Gaining Speed: Empty Prefetch on your XP System

A little known tweak that can help you gain some performance on your XP Professional (and Windows Server 2003) related systems is to periodically empty the prefetch folder. The prefetch folder is used to help speed up the loading of programs; XP will load programs it thinks you need before you ask for them yourself.


For a complete guide to security, check out 'Security+ Study Guide and DVD Training System' from Amazon.com

Since applications are nothing other than data (files, folders which make up the programs), they are susceptible to the same form of punishment all other data on your system is open to… defragmentation, as well as just residing on your hard disk, if needed, the program must be called from the disk and loaded into memory. If XP (or 2003) tries to prefetch applications you don’t regularly use, then you may be wasting memory. In this article, we look at how to speed up performance by emptying the little known prefetch folder and allowing XP to start the prefetch determination and archiving process over again.

Prefetch Basics

The prefetch folder resides on your local hard disk, under the Windows folder.

%systemroot%\prefetch

-or-

X:\windows\prefetch

Where ‘X’ is the drive letter where you have Windows installed. Either path will get you to your local system. The second path is for those who have the default installation on the most commonly used drive letter, C:\

The prefetch folder is used for speeding up your system. The way it does this is by doing the following:

  • Windows XP is configured to prefetch application and program components so that when you load them to memory; it appears to be very quick.
  • When XP does this the first time, it winds up copying portions of the program to the prefetch area of your local disk.
  • When XP boots up, XP will prefetch portions of the files you use the most.
  • XP loads all associated files, libraries, and pointers necessary to run the program in advance, the preloaded subset makes your system appear quicker.

Prefetch when unattended can also slow down your system. This is because over time

  • XP will retain a copy of a portion of a program in the prefetch folder even if you only use it one time, which is not good. Since you may not use the program again, you may impact the performance of your system by having portions of a program you do not use loaded in your system's memory.
  • XP systems with very low hardware resources (such as memory and hard disk space) will definitely be affected by an over-bloated prefetch folder.

Open and Empty the Prefetch Folder

To view the contents of your prefetch folder, you only need to open to it. You can follow the path outlined earlier to view the prefetch folder. You can use Date Created or Modified fields to attempt to figure out how old each prefetch file is, this may help you determine what can be deleted and what you may want to keep. The easiest way to do this however is to just delete the contents and then start to open and use your common programs again – XP will go back through the same process and prefetch what you need.

You'll then see the contents of a very full prefetch file as seen on this XP client:

Note:
The layout.ini file can also be deleted without a problem. *.ini files are ‘information files’ that are used by Windows to make configurations. Layout.ini contains prefetch information for XP's disk defragmentation system (defrag). Information in this file is used by the defragmenter to move programs and files on your workstation's hard drive to a more favorable location, speeding up direct read times.

Cleaning out the folder

As you can see, just like the TEMP directory on your system, the Prefetch folder can fill up with lots of unused entries and take up needed space. The folder space isn't really what you are solely worried about, it’s all this 'preloaded in memory' stuff that you are trying to avoid. Memory is priceless… it's what makes your system 'seem' fast. In reality, you load everything from your hard disk… the more memory your system has, the more the operating system will attempt to load and keep loaded in memory. You always… always want to keep this area as free and clear as possible because when it fills up – it immediately impacts the system. Paging from disk to memory and back again taxes system resources and slows down your system. As well, running out of hard disk space simultaneously puts a strain on your system's page file, which needs all available free hard disk space to accommodate 'virtual memory'. In sum, you can improve system performance by deleting files from this folder not only to keep it out of memory but to also keep it off your hard disk. This is not space that will be gained back unless you are using fewer programs now then you were at another time. An example may be if you previously used many Graphic Art tools and now you aren’t. Since these tools and their environments are so large, removing the prefetch files for these tools may claim a lot in system resources back for you.

When cleaning out your folder, you have two choices: Selective or All

You can be selective or you can mass delete everything. Ctrl + A and then Del. Gone. No problems doing it that way, again – you can regenerate what you need upon reboot and reload. You can also be very selective, although the first method is the easiest, quickest and most effective way of doing it. Remember - to delete all the files, simply select them all in Explorer and select the delete key on your keyboard. Reboot, re-launch your programs and you are back in business. Programs no longer used often will remain dormant until used again.

You shouldn't delete these files often because then your system is constantly taxed in creating file and then you deleting them. This of course will put a strain on your hard disk and leave you needing another defrag. Use this tweak sparingly, remembering it when you do spring cleaning. You can tie this into a routine when you 'delete' unused programs, go and clear out the prefetch folder… cleaning out any other temp related folders and then a scandisk and defrag. If you spend a few bucks and get a memory upgrade, your system will 'appear' much quicker. As well, you will reclaim some serious hard disk space – and clear out memory as well. Heck, you may not even need that new stick of memory after you clean out your system. So, is there anyway to modify prefetch? Yes there is.

Changing Prefetch settings

To change settings for your Prefetch folder, you may need to take a trip into the system's Registry. You can do this with Regedit.

Start => Run => type Regedit => Enter

Now that you are in the Registry, you can change the way that Prefetch behaves by making a change in the registry. This is helpful when you want to alter Prefetch or disable Prefetch completely. Low resource (memory, hard disk space, etc) systems may need this functionality disabled to get the system to run more efficiently.

When the Registry Editor Dialog box opens, navigate to this value:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters

In the right side pane, look for the key named EnablePrefetcher. The value of this key represents how Prefetch will operate.

Values you can choose from include:

0: Disable

1: Application Launch Prefetch

2: Boot Prefetch

3: Prefetch everything

Simply type the number in that you want (keep all other settings the same) and click OK. Rebooting the system will give you the new Prefetch setting.

Summary

In this article we covered the basics of cleaning out the Prefetch folder and gaining more speed on your XP (or 2003) system. Stay tuned for more tweaks!


READ MORE!

Design by Free blogger template