Windows XP stores a couple of values in its registry which are responsible for determining how long to wait before shutting down (killing) open applications and services once the shutdown command has been given.

By editing these two settings and changing them to lower values, you can considerably decrease the amount of time that Windows XP needs to successfully shut itself down. The first part of this tweak deals with setting the amount of time Windows will take to kill open applications on shutdown.

Open REGEDIT and navigate to ‘HKEY_CURRENT_USER\Control Panel\Desktop\’
Highlight the ‘WaitToKillAppTimeout’ value.
Set it to ‘1000′ (the default should be 20000).
Now highlight the ‘HungAppTimeout’ value
Set it to ‘1000′ also.

Boys:

1. Drive to the bank, park and go to the Cash Dispenser.
2. Insert card
3. Dial code and desired amount
4. Take the cash, the card and the slip

Girls:
1. Drive to the bank
2. Engine stalled
3. Check make-up in the mirror
4. Apply perfume
5. Manually check haircut
6. Park the car - failure
7. Park the car - failure
8. Park the car - Success
9. Search for the card in the handbag
10. Insert card, rejected by the machine
11. Throw phone card back in handbag,
12. Look for bank card.
13. Insert Card
14. Look for Secret Box (where secret code is written)in Handbag
15. Enter code
16. Study instructions for 2 minutes
17. #Cancel#
18. Re-enter code
19. #Cancel#
20. Call Boyfriend/husband to get correct the code
21. Enter desired amount
22. #Error#
23. Enter bigger amount
24. #Error#
25. Enter maximum amount
27. Take cash
28. Go back to the car
29. Check make up in rear mirror
30. Look for keys in handbag
31. Start car
32. Drive 50 meters
33. STOP
34. Drive back to bank machine
35. Go out of the car
36. Take card and ticket back from machine
37. Go back to the car
38. Throw card on passenger seat
39. Throw slip on the floor
40. Check make up in rear mirror
41. Manually check haircut
42. Go into roundabout - wrong way
43. BRAKE
44. Go into roundabout - right way
45. Drive 5 kilometers
46. Remove hand brake

47. Call boyfriend/husband to tell how miserable she was because of HIM.

Whenever I have a problem with an image “not showing up” on a web page, the first thing I do is take a close look at the file path that references that image. If that file path is relative (meaning that it doesn’t start with http://), I pay extra close attention to the relationship of where the file is that is referencing the image, and where that image actually is.

• Is the image in the same directory as the file referencing it?
• Is the image in a directory below?
• Is the image in a directory above?

By “below” and “above”, I mean subdirectories and parent directories. Relative file paths give us a way to travel in both directions. Take a look at my privative example:

Here is all you need to know about relative file paths:

• Starting with “/” returns to the root directory and starts there
• Starting with “../” moves one directory backwards and starts there
• Starting with “../../” moves two directories backwards and starts there (and so on…)
• To move forward, just start with the first subdirectory and keep moving forward