This repair guide is the one for you know matter if your a professional or a inexperieced repair man

This will show you how to :

Replacement PS2 Parts
Playstation 2 Maintenance (With VIDEO)
Disassembling you're PS2 (With VIDEO)
Laser Cleaning Procedures (With VIDEO)
Adjusting the Laser Voltage (With VIDEO)
Adjusting the Laser Height (With VIDEO)
Replacing your PS2's Laser (With VIDEO)
CD Tray Alignment (With VIDEO)
Testing Fuses (With VIDEO)
Desoldering & Soldering Fuses (With VIDEO)
Common Playstation Problems and Fixes/FAQ
Power Supply Troubleshooting and Diagram
Precision Laser Adjusting with O'Scope
Disk Read Error
Find Your PS2 Version
More on Disk Read Error
Buying PS2's to Repair
Replacement PS2 Parts

This tutorial is very detailed and very easy to use for ANY one

Code:
http://rapidshare.com/files/8494511/ps2_Repair_Guide.exe

Here are Registry Tweaks and Scroll down to see Patches


1.Increase bandwidth by tweaking QoS in Windows XP Pro

The following tweak applies only to Windows XP Professional edition.

The default system behavior is that all 100% bandwidth is available, however, if there is a running application that indicates to the OS it needs to send high priority/real time data, then as long as it has the socket open, Windows XP will restrict “best effort” traffic to 80% of the bandwidth so that high priority traffic can be accommodated. Basically, applications can make this request to the operating system for QoS support using the QoS application programming interfaces (APIs) in Windows and this only applies if a specific app is requesting QoS.

If you'd like to change how much bandwidth is reserved for QoS (the default is 20% of the total bandwidth), do the following:

1. Make sure you're logged in as "Administrator" (not just any account with admin privileges).
2. Navigate to START>Run and type: gpedit.msc
3. Navigate to Local Computer Policy > Administrative Templates > Network > QOS Packet Scheduler
4. In the right window, double-click the limit reservable bandwidth setting
5. On the setting tab, check the enabled setting.
6. Where it says "Bandwidth limit %", change it to read 0 (or whatever percentage you want to reserve for high priority QoS data)
7. Click OK, close gpedit.msc

Under START > My Computer > My Network Connections > View Network Connections, right-click on your connection and under Properties (where it lists your protocols), make sure QOS Packet Scheduler is enabled.



The tweak desribed below helps boost priority for DNS & hostname resolution in general. What this means is, it helps web pages load faster, and has negligible effect on downloads (not counting the couple of ms gain with the host resolution at connect-time).

Applying this tweak assumes some proficiency in editing the Windows Registry using Regedit (Start > Run > type: regedit). As always, backup your Registry before making any changes so you can revert to the previous state if you don't like the results.


2.Host Resolution Priority Tweak
host name resolution priority
Windows 2k/XP

First, open the Windows Registry using Regedit, and (after backing up) navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\ServiceProvider



Note the following lines (all hex dwords):
Class = 008 (8) - indicates that TCP/IP is a name service provider, don't change.

LocalPriority = 1f3 (499) - local names cache
HostsPriority = 1f4 (500) - the HOSTS file
DnsPriority = 7d0 (2000) - DNS
NetbtPriority = 7d1 (2001) - NetBT name-resolution, including WINS

What we're aiming to do is increase the priority of the last 4 settings, while keeping their order. The valid range is from -32768 to +32767 and lower numbers mean higher priority compared to other services. What we're aiming at is lower numbers without going to extremes, something like what's shown below should work well:

Change the "Priority" lines to:
LocalPriority = 005 (5) - local names cache
HostsPriority = 006 (6) - the HOSTS file
DnsPriority = 007 (7) - DNS
NetbtPriority = 008 (8) - NetBT name-resolution, including WINS

Windows 9x/ME

The tweak is essentialy the same as in Windows 2000/XP, just the location in the Registry is slightly different. For a more detailed description see the Windows 2000/XP section above.

Open the Windows Registry using Regedit, and (after backing up) navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\ServiceProvider

You should see the following settings:
Class=hex:08,00,00,00

LocalPriority=hex:f3,01,00,00
HostsPriority=hex:f4,01,00,00
DnsPriority=hex:d0,07,00,00
NetbtPriority=hex:d1,07,00,00

The "priority" lines should be changed to:
LocalPriority=hex:05,00,00,00
HostsPriority=hex:06,00,00,00
DnsPriority=hex:07,00,00,00
NetbtPriority=hex:08,00,00,00

Reboot for changes to take effect.


In addition to the tweaks already covered in Win 2k/XP Registry Tweaks and More Win 2k/XP Tweaks, the Windows XP Service Pack 2 introduces a few new issues covered in the article below. Please make sure you understand what you are doing before making any changes to your Operating System. Note the information below only applies to Windows XP Service Pack 2.



3.Remove the limit on TCP connection attempts

Windws XP SP2 introduces a few new twists to TCP/IP in order to babysit users and "reduce the threat" of worms spreading fast without control. In one such attempt, the devs seem to have limited the number of possible TCP connection attempts per second to 10 (from unlimited in SP1). This argumentative feature can possibly affect server and P2P programs that need to open many outbound connections at the same time.

Rant: The forward thinking of Microsoft developers here is that you can only infect 10 new systems per second via TCP/IP ?!?... If you also consider that each of those infected computers will infect 10 others at the same rate:
second 1: 1+10 computers
second 2: 10+10*10 computers (110 new ones)
second 3: 10+100*10 computers ( 1110 new ones)
second 4: 10+1000*10 computers (11110 new ones)
....
all the way to 10*60 + 10^60 computers in a single minute (that's a number with 60 digits, or it would far exceed Earth's population). Even if we consider that 90% of those computers are unreachable/protected, one would still reach ALL of them within a minute.

In other words, even though it is not going to stop worm spreading, it's going to delay it a few seconds, limit possible network congestion a bit, and limit the use of your PC to 10 connection attempts per second in the process ! I have no problem with the new default setting limiting outbound connection attempts. Still, users should have the option to easily disable or change this setting. I might be going out on a limb here, but ever since the introduction of Windows XP I can't help thinking that I dislike all the bult-in Windows "wisardry" in a sense that the system also limits user access. That irritating trend to ease the mental load on end users is somewhat insulting, considering that Windows is to make the more "intelligent" choice instead of the end user, as well as limit their access to tuning such settings...
End of rant.

With the new implementation, if a P2P or some other network program attempts to connect to 100 sites at once, it would only be able to connect to 10 per second, so it would take it 10 seconds to reach all 100. In addition, even though the setting was registry editable in XP SP1, it is now only possible to edit by changing it directly in the system file tcpip.sys. To make matters worse, that file is in use, so you also need to be in Safe mode in order to edit it.

You only need to worry about the number of connection attempts per second if you have noticed a slowdown in network programs requiring a number of connections opened at once. You can check if you're hitting this limit from the Event Viewer, under System - look for TCP/IP Warnings saying: "TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts". Keep in mind this is a cap only on incomplete outbound connect attempts per second, not total connections. Still, running servers and P2P programs can definitely be affected by this new limitation. Use the fix as you see fit.

To change or remove the limit, you can use the following program:

Event ID 4226 Patcher v2.11

Code:
http://www.speedguide.net/files/xp_sp2/EvID4226Patch211a-en.zip


- A patching program for removing or changing the limit imposed on connection attempts in SP2. The patcher has the ability to restore tcpip.sys back to the original... Still, you might want to back up tcpip.sys, use it at your own risk. The author of this patch can be reached @ http://www.lvllord.de/

4. Recommended settings for Windows 2000 / XP
Windows 2000 & XP, unlike NT supports large windows as described in RFC1323 ( the 'RcvWindow' has a maximum value of 2**30 rather than 64K), and includes some other improvements over its predecessors you can use to speed up any TCP/IP transfers. , the descriptions and other options are added to provide you with better understanding and enable you to customize your settings.

All the following entries, unless otherwise noted should be placed in the Windows 2000/XP Registry under the key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

TCPWindowSize

The value of TCP Window in the Windows 2000 Registry is DWORD, representing number of bytes, with range from 0 to 2^30. The recommended values (in red) optimize TCP for any high speed Internet connection and work best in most cases, however if you'd like to use a custom value follow these guidelines:

For best results, the TCPWindow should be a multiple of MSS (Maximum Segment Size). MSS is generally MTU - 40, where MTU (Maximum Transmission Unit) is the largest packet size that can be transmitted. MTU is usually 1500 (1492 for PPPoE connections). To determine the MTU value of your ISP, check out the Advanced Registry Editing section of our site.

There are three places in the Windows 2000 Registry where you can add the TCP Window parameter.

HKLM/SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
GlobalMaxTcpWindowSize="256960" (DWORD, number of bytes) Valid range is from MSS to 2^30. Add the value as a decimal. Note: For best results RWIN has to be a multiple of MSS lower than 65535 times a scale factor that's a power of 2, i.e. 44 x 1460 = 64240 x 2^2 = 256960. If you choose to use a RWIN lower than 65535, you can simply make it multiple of MSS and turn scaling off (Tcp1323Opts=0)

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
TcpWindowSize="256960" (DWORD, number of bytes) Valid range is from MSS to 2^30. Add the value as a decimal. TcpWindowSize can also exist under TcpipParametersInterface - if added at this location, it overrides the global setting for this particular . Note (10/20/00): Seems MS has found another bug in Windows 2000, the TCPWindowSize should be configured with the global setting (GlobalMaxTcpWindowsSize) rather than this one - Q263088

Note: For best results RWIN has to be a multiple of MSS lower than 65535 times a scale factor that's a power of 2, i.e. 44 x 1460 = 64240 x 2^2 = 256960. If you choose to use a RWIN lower than 65535, you can simply make it multiple of MSS and turn scaling off (Tcp1323Opts=0)

Tcp1323Opts

Tcp1323Opts is a necessary setting in order to enable Large TCPWindow support as described in RFC 1323. Without this parameter, the TCPWindow is limited to 64K.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Tcp1323Opts="1" (DWORD, recommended setting is 1. The possible settings are 0 - Disable RFC 1323 options, 1 - Window scaling but no Timestamp options, 3 - Window scaling and Time stamp options.)

Note: Tcp1323Opts="3" might help in some cases where there is increased packet loss, however generally you'll achieve better throughput with Tcp1323Opts="1", since Timestamps add 12 bytes to the header of each packet.

DefaultTTL

DefaultTTL determines the time in seconds and the number of hops a packet lives. While it does not directly affect speed, a larger value increases the amount of time it takes for a packet to be considered lost, discarded and retransmitted. A value that's too small can cause packets to be unable to reach distant servers at all.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
DefaultTTL="64" (DWORD, recommended setting is 64. Other settings that are widely used are 128 and 32)

EnablePMTUDiscovery

When set to 1 (True), TCP attempts to discover MTU automatically over the path to a remote host. Setting this parameter to 0 causes MTU to default to 576 which reduces overall performance over high speed connections. Note that this setting is different than our Windows 9x recommendation.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
EnablePMTUDiscovery="1" (DWORD - boolean, valid settings are 0-->False and 1-->True. Many connections perform better with this entry at 1, however, if you prefer to set your upstream to send fixed 1500 packets, you might want to use 0 instead). When set at 1, establishing connections and initial transfer speed might slow down a bit, however you will get better throughput if somewhere in the path large packets need to be fragmented.

EnablePMTUBHDetect

Setting this parameter to 1 (True) enables "black hole" routers to be detected, however it also increases the maximum number of retransmissions for a given segment. In most cases you'd want to keep BHDetect to 0 (False).

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
EnablePMTUBHDetect="0" (DWORD - boolean, valid settings are 0-->False and 1-->True. Recommended setting is 0)

SackOpts

This parameter controls whether or not SACK (Selective Acknowledgement) support is enabled, as specified in RFC 2018. SACK is especially important for connections using large TCP Window sizes.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
SackOpts="1" (DWORD - boolean, recommended setting is 1. Possible settings are 0 - No Sack options or 1 - Sack Option enabled).

TcpMaxDupAcks

This parameter determines the number of duplicate ACKs that must be received for the same sequence number of sent data before "fast retransmit" is triggered to resend the segment that has been dropped in transit.

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
TcpMaxDupAcks="2" (DWORD - range 1-3, recommended setting is 2).



Patches


This Includes

1. sguide_tweak_2k.zip
Description: Generic patch for Windows XP and Windows 2000 (all versions). This patch will optimize your TCP/IP Registry settings for high speed Internet connections. To install, extract the .inf file first, then double-click (or right-click on filename and choose install from the pull-down menu) and reboot for changes to take effect.

Code:
http://www.speedguide.net/files/sguide_tweak_2k.zip


2.sguide_tweak_2k_pppoe.zip

Description: Generic patch for Windows XP/2000 and DSL connections using PPPoE. This patch will optimize your TCP/IP Registry settings for high speed Internet connections. It is specifically designed for PPPoE DSL connections. To install, extract the .inf file first, then double-click (or right-click on filename and choose install from the pull-down menu) and reboot for changes to take effect.

Code:
http://www.speedguide.net/files/sguide_tweak_2k_pppoe.zip



3. winxp_dnscache.zip

Description: Patch Windows 2k/XP not to cache failed DNS entries. By default, when a DNS lookup fails (due to temporary DNS problems), Windows still caches the unsuccessful DNS query, and in turn fails to connect to a host regardless of the fact that the DNS server might be able to handle your lookup seconds later. This patch fixes the problem by configuring the DNS client to continue sending queries to an unresponsive network. To install, save to your HD, unzip the .reg file, then double-click the filename.

Web Patches - faster loading of Web Pages

The following patch increases Web page loading speed, by doubling the number of possible concurrent open connections. For example, imagine a web page has 20 images and some text - in order for your browser to get all these files, it opens 2 or 4 concurrent connections, depending on the Web server. Increasing the number of open connections allows for faster retrieving of the data. Please note that the patch sets some values outside of the HTML specs. If you decide to install it, backup your Registry first. Changes will take effect after you reboot. Download the patch appropriate for your OS:

OS: Windows 9x/ME

Code:
http://www.speedguide.net/files/sg_webtweak_9x.zip


OS: Windows 2K/XP/2k3

Code:
http://www.speedguide.net/files/sg_webtweak_2k.zip


TCP OPTIMISER

Please reupload this image to another image host:
http://img414.imageshack.us/img414/31/tcpoptimizer12es.png


Description: The TCP Optimizer is a free, easy Windows program that provides an intuitive interface for tuning and optimizing your Internet connection. Just download and run, there is no installaion required. The program makes it easy to find the best MTU and RWIN values, test latency and tweak all the important broadband related registry parameters. The Optimizer can be helpful with tuning any Internet connection type, from dialup to Gigabit+

Code:
URL http://www.speedguide.net/files/TCPOptimizer.exe
Technorati Profile

his is penis enlargement exercise.Do not need
applications.Just need your hand.
(Tutorial Videos + E-book)


Code:
http://rapidshare.com/files/10713140/Penis_Enlargement_Guide.rar

pass: ufc4.com/h

Stopping Unneeded Startup Services

Along with the core operating system and programs that Windows XP runs when it starts, there is also a host of services involved. Many of these services are necessary for Windows XP to operate correctly. However, many of them are for features in Windows XP that you may not use at all. You can peruse the services and disable any service that you do not want to run. The fewer services that run, the more quickly Windows XP will boot.

Caution:
Exercise caution when stopping services. If you do not know what a service does or are unsure of the ramifications of stopping the service, leave it alone. Some services are critical to Windows XP's operations, so make sure you understand what the service is before you disable it.

To reduce the number of services that start on bootup, you can access two different areas of Windows XP. The first is the System Configuration Utility. The Services tab shows you the services that start when the computer boots.

You can stop a service from starting by simply clearing the check box next to the service and clicking OK. However, before you do so, there is another way to disable services that you may prefer because the interface gives you more information about the service in question.

Open Control Panel/Administrative ToolsServices or else select Start/Run, type services.msc, and click OK. Either way, you see the Services console.

I prefer to use the Services console instead of the System Configuration Utility because it describes what the service does. Additionally, you can double-click a service and examine its properties.

Notice the Startup Type column in Figure 4-2. This information lists whether the service is automatic or manual. Manual services are only started in Windows XP when you start a process that requires the service. Some other process may require the service that has a "dependency" relationship with it; in this case, the dependency service will start, as well. Because these services do not start automatically when you boot Windows XP, you do not need to do anything with manual services.

However, all services listed as automatic start when Windows XP boots. These are the services that increase boot time. As I have mentioned, many of them are necessary and important, so you should not stop automatic services from booting unless you are sure of the ramifications. You can get this information by looking at the Description column. Here's a quick look at common services you may want to live without:

Arrow Automatic Updates: This service enables Windows XP to check the Web automatically for updates. If you don't want to use Automatic Updates, you can disable the service. You can always check for updates manually at the Windows Update Web site.

Arrow Computer Browser: If your computer is not on a network, you don't need this service. If you are on a network, leave it alone.

Arrow DHCP Client: If you are not on a network, you do not need this service. If you are on a small workgroup, you can still increase boot time by configuring manual IP addresses (which I explore later in this chapter).

Arrow DNS Client: If you are not on a network, you do not need this service. If you are, leave it alone.

Arrow Error Reporting and Event Log: You don't have to use these services but they can be very helpful, so I would leave them configured as automatic.

Arrow Fax: If you don't use your computer for fax services, you can disable this one.

Arrow Help and Support: If you never use the Windows XP Help and Support Center (found on the Start menu), you can disable this service.

Arrow IMAPI CD-Burning COM: This service enables you to burn CDs on your computer. If you never burn CDs, you can disable the service.

Arrow Indexing Service: Your computer keeps an index of files but if you rarely search for files, the service is just a resource hog. You can stop it and turn the service to manual.

Arrow Windows Firewall/Internet Connection Sharing: If you do not use these features, you can disable them.

Arrow Infrared Monitor: If you do not use infrared devices, you can disable this service.

Arrow Messenger: This service sends alert messages on a local area network (it is not the same as Windows Messenger). If you are not on a network, you can disable this service.

Arrow Print Spooler: If you do not do any printing from the computer, you can disable this service. If you print, make sure you leave it as automatic.

Arrow Remote Registry: This service allows remote users to modify the Registry on your computer. If you are not on a network, you can disable this service.

Arrow System Restore Service: This service allows you to use System Restore. If you have turned off System Restore anyway, you do not need to turn off the service. If you do, you turn off System Restore.

Arrow Themes: If you do not use themes, you can disable this service.

Arrow Windows Image Acquisition: If you do not use scanners or digital cameras, you can disable this service.

Arrow Wireless Zero Configuration: If do not use wireless networking devices, you can disable this service.

You may have a number of other automatic services, depending on software and other configurations on your computer. So it's a good idea to look through the services and learn more about them. If you double-click a service, a Properties dialog box appears

Notice that on the General tab, you see a Startup Type drop-down menu. If you want to change an automatic service to manual, select Manual here and click OK. As a general rule, don't disable a service unless you are sure you will never use it. However, manual configuration allows the service to be started when you find it necessary, thus speeding up your boot time.

However, before you change a service to manual, look at the Dependencies tab (see Figure 4-4). This tab shows you which other services depend upon the service you are considering changing.

Keep in mind that services are necessary for the vast functionality you get with Windows XP. Change only those services that you understand and do not use. How you use your Windows XP computer should be the best guide in terms of optional startup services.

Tip:

The Indexing service and the System Restore service take up a lot of disk space and system resources across the board. You can live without the Indexing service but I suggest that you keep using System Restore. It works great when you are in a bind and this is one case where the loss of speed may not be worth the ramifications of not using System Restore.

Speed Tips and Tricks for Windows XP Startup

Aside from startup programs, services, and the Prefetch folder, there are a number of other startup procedures and issues you can modify to help Windows XP start faster. The following sections explore those tips and tricks.

Manual IP Addressing on Small Office/Home Networks

Windows XP is configured to help you take care of networking. It uses the TCP/IP protocol for networking in workgroups, or what you might call small office or home networks that do not use a dedicated server.

The problem is that automatic IP addressing can be slow. When your computer boots, it has to query the network to see what IP addresses are already in use and then assign itself one. If you want to speed up the boot time a bit, consider manually assigning IP addresses to all computers on the network. This way, the network computers do not have to worry about locating an automatic IP address. Because one is manually configured, the operating system doesn't have to spend time solving this problem.

This isn't a networking book, however, so I won't delve into the implications of using a manual IP address, but if you are using a computer that functions as a host computer to the Internet (using Internet Connection Sharing [ICS]), you can get into connectivity problems if you change the configuration of the IP address. However, you can still work around this problem by starting with the ICS host computer.

Select Start/Connect To/Show All Connections. Right-click your network adapter card and click Properties. On the General tab, select TCP/IP in the list of services and click the Properties button.

In the TCP/IP properties, you can see if you use an automatic or manual IP address. In the example in Figure 4-5, I have configured a manual IP address of 90.0.0.1 and a default subnet mask. The other computers on my office network each use a different IP address in the same class, such as 90.0.0.2, 90.0.0.3, 90.0.0.4, and so on. This way, each computer has a permanent IP address, which helps increase boot time. Note that if you change the IP addresses of your computers, they must all use the same subnet mask. A default subject mask of 255.255.255.0 will keep you in good shape.

Make sure you understand the implications of changing IP addresses on your network. If you have no networking experience at all, you may be wiser to leave the automatic IP addressing as is and try to gain some speed using the additional suggestions in this chapter.

Disabling Recent Documents History

Windows XP includes a feature that keeps track of all recent documents you have opened or used. The idea is that you can select Start/Recent Documents History and quickly reopen any document you have recently used. I use many documents each day and never use the feature myself. In my opinion, I can keep up with what I want to use without Windows XP doing it for me.

The bad thing about Recent Documents History is that Windows XP has to calculate what should be put there each time you boot Windows, which can slow things down. So, if you never use the Recent Documents History, it's a good idea to disable it. Here's how:

1) Open the Registry Editor (select Start/Run, type regedit, and click OK).
2) Navigate to HKEY_CURRENT_USER\Software\Mcft\Windows\ CurrentVersion\Policies\Explorer.
3) Create a NoRecentDocsHistory D_WORD key. Double-click the value to open it once it is created.
4) Set the Data Value to 1 to enable the restriction.
5) Click OK and close the Registry Editor. You'll need to restart the computer for the change to take effect.

Disabling the Boot Logo

You can remove the boot logo that appears when you start Windows XP. This little tweak probably shaves only a few seconds off your boot time but seconds count if you are serious about trying to get Windows XP up and running as quickly as possible. The only negative is that if you remove the boot logo, you will also not see any boot messages, such as check disk. (But if you are not having problems with your computer, this isn't such a big deal.)

To remove the boot logo, follow these steps:
1) Select Start/Run, type msconfig, and click OK.
2) In the System Configuration Utility, click the BOOT.INI tab.
3) On the BOOT.INI tab, click the NOGUIBOOT check box option. Click OK.

Removing Unwanted Fonts

One trick that increases your boot time a bit is to lose any fonts in the Fonts folder in Control Panel that you never use. The more fonts you have, the more processing Windows XP has to do to prep all of those fonts for use. You must be a bit careful here to not remove fonts that you might want, but there is a good chance that you can live without many of them. For instance, you may have foreign language fonts and other symbol fonts (such as Wingdings) that you never use.

To delete unneeded fonts, follow these steps:
1) Open the Fonts folder in Control Panel.
2) Select Edit/Select All and then Edit/Copy.
3) Create a new folder on your desktop, open it, and select Edit/Paste.
4) In this new folder, delete any of the fonts you do not want.
5) Return to the Fonts folder in Control Panel. Right-click the selected fonts and click Delete.
6) Go back to your new desktop folder and click Edit/Select All.
7) Return to your Fonts folder and click Edit/Paste. You now have only the desired fonts in the Fonts folder.

Tip:

You can directly delete fonts from the Fonts folder without creating the secondary folder. However, I recommend the preceding steps to help ensure that you do not make a mistake in the deletion process.

Stopping Remote Assistance and Remote Desktop Sharing

In Windows XP Professional, you have two remote networking features called Remote Assistance and Remote Desktop Sharing. These remote networking features are very helpful in a variety of situations but if you don't use them, it is good idea to disable them to save boot time. You can always enable them later if you want to use them.

Note:
If you are interested in using Remote Desktop or Remote Assistance, see my book Windows XP for Power Users: Power Pack published by John Wiley & Sons.

1) Open the Start menu, right-click My Computer, and choose Properties.
2) Click the Remote Tab.
3) Clear both check boxes to disable Remote Assistance and Remote Desktop.

Speeding Up the Dual-Boot Timeout

If you dual-boot your computer with Windows XP and another operating system, you see an operating system selection menu on startup. If you typically boot into Windows XP and not the other operating system, you can speed up the dual-boot timeout value so that you do not wait so long for the boot process to select your default operating system and continue with the boot process. The default timeout value is 30 seconds but you can change this setting to 10. This gives you enough time to select the alternate operating system if you want but also speeds up the boot process. You can skip this section if you do not use a dual-boot configuration.

Follow these steps:
1) Locate the boot.ini file on your computer. It is a hidden file by default; mine is located in C:\boot.ini.
2) Open the file with Notepad (which is what opens it by default).
3) Change the Timeout value to 10 (see Figure 4-11).
4) Select File/Save and close Notepad.

Speeding Up Your PPPoE Connection

If you use a Point-to-Point Protocol connection over Ethernet (PPPoE), you may notice a delay in using the PPPoE connection after startup. By default, there is a 120 second delay but you can stop this behavior by manually configuring an IP address for the network adapter card. If you do not use a PPPoE connection, you can skip this section.

1) Select Start/Connect to/Show All Connections.
2) Open the TCP/IP properties for your LAN network interface card.
3) Manually set the IP address on the TCP/IP properties to an appropriate IP address and subnet mask for your network.

Reducing the Wait Time

When you start to shut down Windows XP, it has to quit, or "kill," any live applications or processes that are currently running. So close all applications first. However, some applications and processes are always running in the background. You can reduce the amount of time that Windows XP waits for those applications and processes to close before Windows XP kills them. Edit three different Registry settings to change this:

1) Open the Registry Editor.
2) Navigate to HKEY_CURRENT_USER\Control Panel\Desktop. Select WaitToKillAppTimeout and set the value to 1000.
3) Select the HungAppTimeout value and set it to 1000 as well.
4) Navigate to HKEY_USERS\.DEFAULT\Control Panel\Desktop. Set the WaitToKillAppTimeout and set the value to 1000. Select the HungAppTimeout \newline value and set it to 1000 as well.
5) Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control. Select the WaitToKillServiceTimeout value and set it to 1000.
6) Close the Registry Editor.

Automatically Killing Tasks on Shutdown

You know the drill. You start to shut down the computer, you wait a few moments, and then you see a dialog box asking if you want to kill an application or service that is running. Instead of prompting you, you can make Windows XP take care of the kill task automatically. Here's how:

1) Open the Registry Editor.
2) Navigate to HKEY_CURRENT_USER\Control Panel\Desktop.
3) Highlight the value AutoEndTasks and change the value to 1.
4) Close the Registry Editor.

Enjoy reading with understanding...