Shutting down Windows XP Faster

Hi all,

                     Sometimes the users could be irritated while system takes plenty of time to shut down the computer. At the backend the processor needs to kill down the active processors. We can manually change the set time factor for processor kill time and so the shut down time can be minimised. Let me give out the steps to handle the process. It could be possible by making changes in the registry settings. Do follows the steps to do shut down quicker.

• Go  to the Registry Editor(by ‘regedit’ from the run command)

• Select the HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Control from the left pane

• Select the ‘WaitToKillServiceTimeout’ from the right pane.

• Change the value field from ‘2000′ to ‘200′

                      And you could feel now the Windows XP shutting down quicker.

Comments are Welcomed…!

Dell hopes on Colour

Hi all,

                       Dell Laptops are going to fade out the traditional gray and black color models. Yeah Dell on last week introduced the laptops in different colors in the Inspiron model. From now Dell laptops can be available in blue, red, green, pink and yellow. Dell keeps on targeting all kind of peoples. Since from the starting of Dell computers, the support provided by them are quite good. They are focussing on the quality of the products delivered. To know more about this…click here

                       To add up one more about Michael Dell, (Founder of Dell Computers) he was discontinued from his graduation. He too added in the list of Steve Jobs(my inspirational character), Bill Gates.

 Comments are Welcomed…!

Real Situation of Software Engineers

Extracted from urbaczewski.com

 

Software doesn’t just appear on the shelves by magic. That  program shrink-wrapped inside the box along with the  indecipherable manual and 12-paragraph disclaimer notice  actually came to you by way of an elaborate path, through  the most rigid quality control on the planet.   Here, shared for the first time with the general public, are  the inside details of the program development cycle.   

1. Programmer produces code he believes is bug-free.   

2. Product is tested. 20 bugs are found.   

3. Programmer fixes 10 of the bugs and explains to the testing department that the other 10 aren’t really bugs.   

4. Testing department finds that five of the fixes didn’t  work and discovers 15 new bugs.   

5. See 3.   

6. See 4.   

7. See 5.   

8. See 6.   

9. See 7.   

10. See 8.   

11. Due to marketing pressure and an extremely pre-mature product announcement based on overly-optimistic programming schedule, the product is released.

12. Users find 137 new bugs.   

13. Original programmer, having cashed his royalty check, is nowhere to be found.

14. Newly-assembled programming team fixes almost all of the 137 bugs, but introduce 456 new ones.

15. Original programmer sends underpaid testing department a postcard from Fiji. Entire testing department quits.

16. Company is bought in a hostile takeover by competitor using profits from their latest release, which had 783 bugs.

17. New CEO is brought in by board of directors. He hires programmer to redo program from scratch.

18. Programmer produces code he believes is bug-free….

 

Comments are Welcomed…!