Carlos Sastre Bags 2008 Tour de France

Carlos Sastre Candil (born 22 April 1975 in Leganés, Madrid) is a Spanish professional road bicycle racer and champion of the 2008 Tour de France. Through his consistently improved top 10 results in the Vuelta a España and good showings in the Tour de France, Sastre established himself as a strong and stable climbing specialist, and after working to improve his individual time trial skills, he has become a contender for the top GC spots in the Grand Tours.










2008 Tour de France record:

Stage	1	2	3	4	5	6	7	8	9	10
Class.	14	44	70	28	83	8	18	66	36	7
	14	27	31	23	23	12	12	12	10	6
	15	28	36	38	47	27	27	33	34	28
	-	-	-	-	-	-	-	-	-	17
	-	-	-	-	-	-	-	-	-	-

11	12	13	14	15	16	17	18	19	20	21
35	40	50	63	6	15	1	37	38	12	62
6	6	6	6	6	4	1	1	1	1	1
29	29	32	35	28	26	18	19	22	22	22
17	13	13	13	9	14	2	2	2	2	2
-	-	-	-	-	-	-	-	-	-	-

2008 Tour de France Standing:

Standing	Rider	Rider number bib	Team	Time
1	SASTRE Carlos	11	TEAM CSC SAXO BANK	87h 52' 52"
2	EVANS Cadel	1	SILENCE - LOTTO	87h 53' 50"
3	KOHL Bernhard	115	GEROLSTEINER	87h 54' 05"
4	MENCHOV Denis	131	RABOBANK	87h 55' 02"
5	VANDEVELDE Christian	191	GARMIN CHIPOTLE	87h 55' 57"
6	SCHLECK Frank	17	TEAM CSC SAXO BANK	87h 57' 20"
7	SANCHEZ Samuel	27	EUSKALTEL - EUSKADI	87h 59' 17"
8	KIRCHEN Kim	41	TEAM COLUMBIA	87h 59' 47"
9	VALVERDE Alejandro	31	CAISSE D’EPARGNE	88h 00' 04"
10	VALJAVEC Tadej	109	AG2R-LA MONDIALE	88h 01' 57"
11	EFIMKIN Vladimir	104	AG2R-LA MONDIALE	88h 02' 47"
12	SCHLECK Andy	16	TEAM CSC SAXO BANK	88h 04' 24"
13	KREUZIGER Roman	65	LIQUIGAS	88h 05' 51"
14	CASAR Sandy	161	FRANCAISE DES JEUX	88h 12' 15"
15	MOINARD Amaël	187	COFIDIS CREDIT PAR TELEPHONE	88h 16' 23"
16	ASTARLOZA Mikel	22	EUSKALTEL - EUSKADI	88h 16' 32"
17	SIUTSOU Konstantsin	49	TEAM COLUMBIA	88h 17' 47"
18	BOTCHAROV Alexandre	83	CREDIT AGRICOLE	88h 20' 03"
19	FOFONOV Dmitriy	85	CREDIT AGRICOLE	88h 21' 23"
20	NIBALI Vincenzo	67	LIQUIGAS	88h 21' 25"
21	GOUBERT Stephane	107	AG2R-LA MONDIALE	88h 24' 42"
22	TEN DAM Laurens	138	RABOBANK	88h 25' 51"
23	MONFORT Maxime	189	COFIDIS CREDIT PAR TELEPHONE	88h 28' 33"
24	POPOVYCH Yaroslav	7	SILENCE - LOTTO	88h 29' 16"
25	SCHUMACHER Stefan	111	GEROLSTEINER	88h 30' 12"
26	SZMYD Sylvester	78	LAMPRE	88h 37' 35"
27	BRUSEGHIN Marzio	74	LAMPRE	88h 38' 11"
28	DESSEL Cyril	101	AG2R-LA MONDIALE	88h 39' 23"
29	KNEES Christian	153	TEAM MILRAM	88h 40' 35"
30	ARROYO David	32	CAISSE D’EPARGNE	88h 41' 15"
31	AERTS Mario	2	SILENCE - LOTTO	88h 41' 50"
32	FEDRIGO Pierrick	141	BOUYGUES TELECOM	88h 43' 11"
33	FOTHEN Markus	113	GEROLSTEINER	88h 53' 56"
34	MOERENHOUT Koos	135	RABOBANK	88h 58' 30"
35	HINCAPIE George	47	TEAM COLUMBIA	89h 01' 07"
36	CARRARA Matteo	93	QUICK STEP	89h 02' 17"
37	VOIGT Jens	19	TEAM CSC SAXO BANK	89h 04' 47"
38	PINEAU Jérôme	145	BOUYGUES TELECOM	89h 05' 50"
39	GONZALO RAMIREZ Eduardo	125	AGRITUBEL	89h 12' 58"
40	LE MEVEL Christophe	87	CREDIT AGRICOLE	89h 13' 16"
41	LÖVKVIST Thomas	48	TEAM COLUMBIA	89h 18' 19"
42	MONCOUTIE David	188	COFIDIS CREDIT PAR TELEPHONE	89h 19' 14"
43	ZABEL Erik	151	TEAM MILRAM	89h 19' 32"
44	VELO Marco	159	TEAM MILRAM	89h 19' 34"
45	ZUBELDIA Haimar	21	EUSKALTEL - EUSKADI	89h 19' 52"
46	GUSTOV Volodymir	14	TEAM CSC SAXO BANK	89h 22' 51"
47	HESJEDAL Ryder	195	GARMIN CHIPOTLE	89h 26' 14"
48	AUGUSTYN John-Lee	52	BARLOWORLD	89h 29' 13"
49	TIRALONGO Paolo	79	LAMPRE	89h 29' 49"
50	MARTINEZ Egoi	24	EUSKALTEL - EUSKADI	89h 29' 52"
51	LOPEZ GARCIA David	36	CAISSE D’EPARGNE	89h 32' 29"
52	TXURRUKA Amets	28	EUSKALTEL - EUSKADI	89h 34' 51"
53	DUQUE Leonardo	186	COFIDIS CREDIT PAR TELEPHONE	89h 37' 16"
54	TSCHOPP Johann	148	BOUYGUES TELECOM	89h 40' 14"
55	DUPONT Hubert	103	AG2R-LA MONDIALE	89h 40' 16"
56	GUTIERREZ José Ivan	35	CAISSE D’EPARGNE	89h 41' 19"
57	ARVESEN Kurt-Asle	12	TEAM CSC SAXO BANK	89h 42' 32"
58	VELITS Peter	158	TEAM MILRAM	89h 42' 41"
59	DI GREGORIO Rémy	163	FRANCAISE DES JEUX	89h 42' 46"
60	TANKINK Bram	137	RABOBANK	89h 43' 16"
61	CHAVANEL Sylvain	181	COFIDIS CREDIT PAR TELEPHONE	89h 47' 17"
62	SANCHEZ Luis-Leon	39	CAISSE D’EPARGNE	89h 48' 31"
63	WEENING Pieter	139	RABOBANK	89h 48' 44"
64	VOGONDY Nicolas	129	AGRITUBEL	89h 48' 56"
65	CANCELLARA Fabian	13	TEAM CSC SAXO BANK	89h 50' 01"
66	PORTAL Nicolas	38	CAISSE D’EPARGNE	89h 51' 08"
67	POZZATO Filippo	61	LIQUIGAS	89h 52' 05"
68	MILLAR David	198	GARMIN CHIPOTLE	89h 52' 31"
69	POSTHUMA Joost	136	RABOBANK	89h 58' 02"
70	FREIRE Oscar	133	RABOBANK	89h 58' 38"
71	ELMIGER Martin	105	AG2R-LA MONDIALE	89h 59' 13"
72	ARRIETA Jose Luis	102	AG2R-LA MONDIALE	90h 00' 25"
73	VERDUGO Gorka	29	EUSKALTEL - EUSKADI	90h 01' 15"
74	LE BOULANGER Yoann	167	FRANCAISE DES JEUX	90h 01' 42"
75	LANG Sebastian	117	GEROLSTEINER	90h 02' 15"
76	FISCHER Murilo Antoniobil	64	LIQUIGAS	90h 05' 55"
77	LOWE Trent	196	GARMIN CHIPOTLE	90h 06' 33"
78	VAN DE WALLE Jurgen	99	QUICK STEP	90h 06' 42"
79	GERRANS Simon	86	CREDIT AGRICOLE	90h 07' 17"
80	PAURIOL Rémi	88	CREDIT AGRICOLE	90h 09' 25"
81	LELAY David	127	AGRITUBEL	90h 09' 35"
82	VAUGRENARD Benoît	169	FRANCAISE DES JEUX	90h 12' 25"
83	CIONI Dario	4	SILENCE - LOTTO	90h 13' 41"
84	FROOME Christopher	57	BARLOWORLD	90h 15' 25"
85	LEQUATRE Geoffroy	128	AGRITUBEL	90h 15' 56"
86	LEFEVRE Laurent	144	BOUYGUES TELECOM	90h 16' 08"
87	VAN SUMMEREN Johan	8	SILENCE - LOTTO	90h 19' 56"
88	CHEULA Gianpaolo	54	BARLOWORLD	90h 23' 04"
89	BARREDO Carlos	92	QUICK STEP	90h 23' 28"
90	CLEMENT Stef	142	BOUYGUES TELECOM	90h 25' 11"
91	PEREZ Ruben	26	EUSKALTEL - EUSKADI	90h 26' 47"
92	MARZANO Marco	75	LAMPRE	90h 27' 00"
93	SCHOLZ Ronny	118	GEROLSTEINER	90h 27' 04"
94	BALLAN Alessandro	72	LAMPRE	90h 28' 00"
95	PATE Danny	199	GARMIN CHIPOTLE	90h 29' 21"
96	TOSATTO Matteo	98	QUICK STEP	90h 30' 59"
97	VOECKLER Thomas	149	BOUYGUES TELECOM	90h 31' 05"
98	ROSSELER Sébastien	96	QUICK STEP	90h 32' 50"
99	HUSHOVD Thor	81	CREDIT AGRICOLE	90h 38' 12"
100	SCHRÖDER Björn	156	TEAM MILRAM	90h 41' 25"
101	FLORENCIO Xavier	143	BOUYGUES TELECOM	90h 46' 43"
102	BONNET William	82	CREDIT AGRICOLE	90h 48' 21"
103	OROZ Juan José	25	EUSKALTEL - EUSKADI	90h 49' 04"
104	ISASI Inaki	23	EUSKALTEL - EUSKADI	90h 50' 36"
105	MÜLLER Martin	155	TEAM MILRAM	90h 51' 23"
106	CIOLEK Gerald	44	TEAM COLUMBIA	90h 51' 26"
107	HUNTER Robert	58	BARLOWORLD	90h 56' 54"
108	HANSEN Adam	46	TEAM COLUMBIA	90h 57' 44"
109	O’GRADY Stuart	15	TEAM CSC SAXO BANK	91h 00' 38"
110	DEAN Julian	193	GARMIN CHIPOTLE	91h 00' 49"
111	STEEGMANS Gert	97	QUICK STEP	91h 01' 15"
112	GILBERT Philippe	165	FRANCAISE DES JEUX	91h 02' 48"
113	WILLEMS Frederik	69	LIQUIGAS	91h 06' 30"
114	DUMOULIN Samuel	185	COFIDIS CREDIT PAR TELEPHONE	91h 07' 29"
115	COYOT Arnaud	33	CAISSE D’EPARGNE	91h 08' 45"
116	FÖRSTER Robert	112	GEROLSTEINER	91h 09' 03"
117	BONO Matteo	73	LAMPRE	91h 09' 28"
118	SORENSEN Nicki	18	TEAM CSC SAXO BANK	91h 09' 53"
119	BRARD Florent	183	COFIDIS CREDIT PAR TELEPHONE	91h 10' 37"
120	BURGHARDT Marcus	42	TEAM COLUMBIA	91h 13' 20"
121	ROY Jérémy	168	FRANCAISE DES JEUX	91h 14' 24"
122	MC EWEN Robbie	6	SILENCE - LOTTO	91h 15' 28"
123	GRABSCH Ralf	152	TEAM MILRAM	91h 16' 09"
124	HOSTE Leif	5	SILENCE - LOTTO	91h 16' 45"
125	DE JONGH Steven	94	QUICK STEP	91h 17' 00"
126	HAUSSLER Heinrich	114	GEROLSTEINER	91h 18' 26"
127	RIGHI Daniele	77	LAMPRE	91h 19' 08"
128	KUSCHYNSKI Aleksandr	66	LIQUIGAS	91h 19' 39"
129	LANCASTER Brett Daniel	154	TEAM MILRAM	91h 20' 21"
130	QUINZIATO Manuel	68	LIQUIGAS	91h 20' 55"
131	LANGEVELD Sebastian	134	RABOBANK	91h 20' 59"
132	GERARD Arnaud	164	FRANCAISE DES JEUX	91h 22' 52"
133	FRISCHKORN William	194	GARMIN CHIPOTLE	91h 23' 39"
134	MAASKANT Martijn	197	GARMIN CHIPOTLE	91h 24' 22"
135	BICHOT Freddy	122	AGRITUBEL	91h 25' 17"
136	TERPSTRA Niki	157	TEAM MILRAM	91h 26' 32"
137	RIBLON Christophe	108	AG2R-LA MONDIALE	91h 28' 16"
138	ENGOULVENT Jimmy	84	CREDIT AGRICOLE	91h 28' 22"
139	AUGE Stéphane	182	COFIDIS CREDIT PAR TELEPHONE	91h 28' 44"
140	MORI Massimiliano	76	LAMPRE	91h 30' 14"
141	GARCIA ACOSTA Vicente	34	CAISSE D’EPARGNE	91h 32' 40"
142	SPRICK Matthieu	146	BOUYGUES TELECOM	91h 41' 10"
143	KRAUSS Sven	116	GEROLSTEINER	91h 44' 47"
144	EISEL Bernhard	45	TEAM COLUMBIA	91h 47' 44"
145	VANSEVENANT Wim	9	SILENCE - LOTTO	91h 48' 37"

BSOD in Windows XP Pro

BSOD in Windows XP Pro

A stop error occurs when Windows XP Professional stops responding. Stop error messages can be caused by hardware or software malfunctions. The error messages appear on a blue or black background. The following steps, which also appear on the stop error screen, help you find out the cause of a stop error and how to fix the problem.

To troubleshoot General Stop Errors:
1. Restart your PC. Unplug each new hardware device, one at a time, to see if this resolves the error. Try to run any hardware diagnostic software supplied by your computer manufacturer.

2. If this is a new installation of hardware or software, contact the manufacturer for any Windows XP Professional updates or drivers you might need. Click Get support, or find information in Windows XP newsgroups (under "Ask for assistance") and then click Get help from Microsoft in the left-hand column.

3. Check the Microsoft Hardware Compatibility List (HCL) to verify that all your hardware and drivers are compatible with Windows XP Professional.

4. If you can start Windows XP Professional, check the System Log in Event Viewer for additional error messages that might help identify the device or driver causing the problem.

5. If you cant start Windows XP Professional, try to start your computer in safe mode, and then remove or disable any newly added programs or drivers.

6. Search the Microsoft Knowledge Base for "Windows XP Professional" and the number associated with the stop error you received. Specific Stop Errors Some stop errors display descriptive messages such as "DATA_BUS_ERROR" that can help you determine the exact solution for the error. This section discusses how to troubleshoot specific stop errors, based on the type of error you receive.


Software and device driver errors:

0x0000001E KMODE_EXCEPTION_NOT_HANDLED__0X000000D1

DRIVER_IRQL_NOT_LESS_OR_EQUAL__0x000000EA

THREAD_STUCK_IN_DEVICE_DRIVER__0x00000050

PAGE_FAULT_IN_NONPAGED_AREA__0X0000000A

IRQL_NOT_LESS_OR_EQUAL__0x0000007B

INACCESSIBLE_BOOT_DEVICE__0x0000009F

DRIVER_POWER_STATE_FAILURE__0XC000021A

STATUS_SYSTEM_PROCESS_TERMINATED__0XC0000221

STATUS_IMAGE_CHECKSUM_MISMATCH

Note: Stop errors 0x0000001E, 0x0000000A, and 0x0000007B can also be caused by general hardware errors. If the steps provided here do not resolve these errors, see the steps under Hardware Failure Errors.

1. Follow the procedure under General Stop Errors. If the stop error persists, try the following steps.

2. Check that the driver identified in the stop message is signed and certified by Windows Hardware Quality Labs (WHQL).

3. If you have a video driver not supplied with Windows XP Professional, try switching to the standard VGA driver or to a compatible driver supplied with Windows XP.

4. Run Recovery Console, and allow the system to repair any errors that it detects. If the error occurred immediately after RAM was added to the computer, the paging file might be corrupted or the new RAM might be either faulty or incompatible.


File system errors:
0x00000023 FAT_FILE_SYSTEM
0x00000024 NTFS_FILE_SYSTEM

Follow the procedure under General Stop Errors. If the stop error persists, try the following steps:

1. If you're using a small computer system interface (SCSI) adapter, obtain the latest Windows XP Professional driver from the hardware vendor, disable the sync negotiation for the SCSI device, verify that the SCSI chain is correctly terminated, and check the SCSI IDs of the devices.
2. If Windows XP Professional can't run Chkdsk, move the drive to another computer running Windows XP Professional, and run the Chkdsk command on the drive from that computer.


Hardware Failure errors:

0x0000001E KMODE_EXCEPTION_NOT_HANDLED

0x0000000A IRQL_NOT_LESS_OR_EQUAL

0x0000007B INACCESSIBLE_BOOT_DEVICE

0x0000007F UNEXPECTED_KERNEL_MODE_TRAP

0xC0000218 UNKNOWN_HARD_ERROR

Note: Stop errors 0x0000001E, 0x0000000A, and 0x0000007B can also be caused by software and device driver errors. If the steps provided here do not resolve these errors, see the steps under Software and Device Driver Errors.

Follow the procedure under General Stop Errors, earlier in this book. If the stop error persists, try the following steps:

1. To troubleshoot hardware failure stop errors check that the devices on your computer have drivers that are signed and certified by Windows Hardware Quality Labs (WHQL).
2. Run Recovery Console, and allow the system to repair any errors that it detects.

If nothing works you will have to uninstall Windows XP, Click Start, click Control Panel, click Add or Remove Programs. Click Windows XP Professional, click Remove and then follow the instructions on your screen.

Blue Screen of Death XP

The Blue Screen of Death, or more properly the 'Windows stop message' occurs when Windows detects a problem or error from which it cannot recover. The operating system halts and diagnostic information is displayed on a blue screen. In newer versions of the operating system, the contents of the PC's memory are dumped to a file for later analysis.

In Windows XP, stop messages generally take one of five forms:

1. Software errors during Windows operation. Software or device drivers installed in your computer may have errors or problems which cause a stop error, either constantly or under certain conditions.

2. Hardware errors during Windows operation. If a hardware device malfunctions or is removed during the operation of Windows, or if your hardware does not fully support the operations that XP expects it to support, a hardware stop error will occur. Outdated BIOS information on older computers might also be an issue.

3. Installation errors. The Windows XP installation process is the most sensitive time for hardware and disk errors. If there is a problem with your computer's hardware configuration or the media you are using to install XP, a stop error will likely occur.

4. Startup errors. Corrupted system files, hardware and driver errors can all cause Windows XP to halt with a stop message without correctly booting into Windows. An error of this sort will almost always require troubleshooting before Windows can be loaded correctly.

5. Intermittent errors. The most irritating type of stop message, these crop up consistently but apparently randomly. The most likely culprits for this include: defective system memory, an overheating processor, dead or dieing hard drive or faulty software and device drivers.

Solutions:

Basic troubleshooting for all BSOD errors

First off, note down all relevant information when you see a BSOD flash across the screen. This includes the error number and friendly name from the 'bugcheck' section of the stop error (see above), and any file names specified in the 'driver information' section.

If the BSOD comes up on the screen for a split-second before the PC restarts and wipes all the useful information away, we need to change some settings within Windows XP. In most cases, it should be possible to stop your PC from automatically restarting when it develops a major error, allowing you enough time to jot down the BSOD error message. If you are using Windows XP, right click on my computer > Properties > Select the 'Advanced' tab > and under 'startup and recovery' click the 'settings' button. This will open a new window, and under the 'System Failure' heading, uncheck 'Automatically restart.'

Attempt to restart the computer normally into Windows. If the BSOD occurred while booting Windows, you may be taken to a troubleshooting menu and will have to select 'attempt to start Windows normally.'

If your computer starts correctly, continue using it and store the error information for later reference. If the BSOD reoccurs at random or irregular periods, see Section D below on troubleshooting intermittent stop errors.

If your system does not start correctly or the stop message happens again, reboot the system. When the POST (memory checking) screen comes up, press F8 repeatedly. This will bring you to the Windows advanced options menu.

In the Windows advanced options menu choose 'safe mode' to attempt to boot into Windows Safe mode. Safe mode loads Windows XP with a minimal set of drivers and no automatically loaded software. If faulty software or drivers are causing your BSOD problem, safe mode should load correctly. If safe mode loads correctly, refer to Section A below on 'troubleshooting software stop messages.'

If safe mode does not load correctly, and/or you get the same stop message upon attempting safe mode, it's time to try the 'restore last known good configuration' option in the advanced options menu.

Restart your computer, pressing 'F8' again to load the advanced options menu and select 'last known good configuration (your most recent settings that worked).' This uses Windows XP's built in system restore utility to restore the most recent save point, which should be the last time you installed any drivers or other software. If your system boots normally after this operation, hopefully your problem has been fixed.

If you are still receiving a Blue Screen Of Death after the above procedures, or if system restore was disabled on your system, note down any new information on the error and start thinking.

Did you install any new hardware or software just before this problem occurred? The driver information section of the BSOD may help with this.
If you did install new hardware or software, and you think you know what it might be that is causing the problem, this gives you a big boost in resolving the situation.

Otherwise, proceed to the advanced troubleshooting sections below. Chances are your error is hardware or system file based and will require more effort to repair.
Specific Repair Instructions

If you have a reoccurring Blue Screen Of Death or crashing problem, and can't use Windows effectively because of it, it's time to look at more specific methods of troubleshooting your problem. Depending on the results of the basic troubleshooting steps above, you should have a good idea of whether the problem that is causing the stop messages is related to software or drivers you have installed, or is a hardware or system file issue.

Essentially, if you can't boot into Windows XP safe mode because of crashes or Blue Screens Of Death, you likely either have a hardware error or one or more essential system files is corrupted or missing. If you can boot into Windows XP safe mode, but get constant or frequent BSOD's when running XP normally, you have a software or device driver problem.

Troubleshooting Intermittent Blue Screens or Crashes

Nothing is more maddening than a random crashing problem on your PC. Most of all because almost any type of hardware or software error could cause this behavior.

The first step you can take to narrow the field down is booting in safe mode and trying to use the system normally (or as normally as you can in safe mode.) If the errors do not occur, it is likely to be software or drivers that are causing the problem. Refer to Section A in this Guide for advice on treating these issues.

If the errors occur randomly, even in safe mode, hardware issues are likely to blame. Consult

Section B of this Guide for a list of steps to take. Also you should check that the processor heat
sink fan is working correctly, and that your PC is not overheating.

Section C: Troubleshooting Windows XP install BSODs

Constant Blue screen errors while attempting to install Windows XP are generally caused by hardware or media problems. The most common hardware-related installation issue is faulty memory chips, which can cause havoc to any XP installation. Overheating or a dying or defective hard disk is other common causes. A severely scratched or otherwise faulty XP install CD may also cause stop errors.

First, check your CD and clean or replace it as necessary. Your next step should be to test your system memory for errors with a diagnostic program.
To do this obtain the Windows Memory Diagnostic or Memtest memory diagnostic programs on floppy or CD we mentioned earlier, and use it to boot your system and test the memory. If either of these programs shows any errors in your memory, you have likely found the source of your troubles. Chances are you will need to purchase new memory.

Now it's time to test the hard drive for errors. Visit the website of your hard drive's manufacturer and download their drive diagnostic utility software. Every major hard drive company makes a utility like this freely available. An example is Maxtor's PowerMax software. Follow the included instructions to install the software and test your drive(s) for errors.

If no errors were found in memory or with the hard disk, you need to ensure that your processor is not overheating. Make sure the fan on the heat sink is in working order and reboot the computer, pressing DEL repeatedly on startup to go into the BIOS setup screen.

Let your PC run on this screen for an hour or so, checking back to make sure it has not crashed. If a PC crashes on the BIOS screen, it generally means the processor is overheating for one reason or another.

As a final measure, you can remove all unnecessary hardware from your system before attempting to install Windows XP again. Power off the computer, remove the case and remove all hardware except:

Mouse & keyboard
Hard drive
CD-Drive
Video card
Memory

(And obviously the processor and power supply must still be connected also)
Attempt to install XP again. If it works correctly, you can troubleshoot the remaining devices from within Windows.

Igme

Well it is another great day for adventure riders like me, slick pavements, good knobbies, 180kph wind gust plus very heavy rain (when I meant heavy I meant the same feeling like getting hit by a Tokyo Marui air-soft gun). Yes it is one of the four cyclones that have been felt by my part of the city, were Marikina river rises but at a tolerable level and out goes the rain gear. As for me, cold got me, what’s new, I ain’t no superman. Good news is it is leaving to Taiwan before weekend, so i get to go trailing on my planned schedule to Mt. Maarat and sure hope to see my mentors in off-road riding, the FSG (Famous Saturday Group), now you know why we love weekends.

Bye Igme (well that’s the name you’ll get if you’re a storm here in the Philippines)

System Restore

Use System Restore to Undo Changes if Problems Occur

Every time you download or install a new game, application, or software update, you make changes to your computer. Sometimes that change may make your system unstable. Have you ever wanted to go back to the way it was? With System Restore, you can.

System Restore works a lot like the Undo command in Microsoft Word. You can use System Restore to remove any system changes that were made since the last time you remember your computer working correctly. System Restore does not affect your personal data files (such as Microsoft Word documents, browsing history, drawings, favorites, or e–mail) so you won't lose changes made to these files.

How does System restore work?

Windows XP periodically records a snapshot of your computer. These snapshots are called restore points. Windows XP also creates restore points at the time of significant system events (such as when an application or driver is installed) or you can create and name your own restore points at any time. If you’ve installed a program that has made your computer unstable, you can open system restore, choose a restore point, and return your computer to its previous stable state.

When you run System Restore, a calendar is displayed to help you find restore points. If you don't use your computer every day, some days might not have any restore points. If you use your computer frequently, you might have restore points almost every day, and some days might have several restore points.

Use System Restore to undo changes you’ve made to your computer

Before you open the System Restore console, you may want to save your work and close all programs since System Restore requires you to restart your computer.

There are two ways to access System Restore – through Help and Support or through your All Programs folder.

Through Help and Support:

1.Click Start, and then click Help and Support.

2.Under Pick a Task, click Undo changes to your computer with System Restore.

3.Follow the instructions on the wizard.

Through the All Programs menu:

1.Click Start.

2.Point to All Programs.

3.Point to Accessories.

4.Point to System Tools.

5.Click System Restore.

6.Follow the instructions on the wizard.

Creating a restore point can be useful any time you anticipate making changes to your computer that are risky or might make your computer unstable. If something goes wrong, you select the restore point you just created and Windows XP undoes any system changes made since that time.