time changes everythng,
but i aint gonna change,
i'll alwz b d same,
a kid at heart,
whose sweet and smart.
time is a teacher,
and am it's student,
who is a learner,
and smarter than his teacher,
there will b times,
whn u'll b down and out,
and worn out,
feel like givin up,
but u need 2 fight,
with all ur plight,
and beat the *** out of time.
time changes everythng,
but i aint gonna change,
i'll alwz b d same,
a kid at heart,
whose sweet and smart.
time is a carrier of pain and tears,
but i am gonna fight like the warrirors,
stand up tall till i am alive,
and stick a bee hive in the face of time.
I aint gonna lie down low,
coz i will show time,
how to stick and arrow up it's ass,
with my gold plated bow.
life mayb *** up,
and I maybe *** up,
but i aint gonna give up,
coz i am gng 2 stick it up...
time changes everythng,
but i aint gonna change,
i'll alwz b d same,
a kid at heart,
whose sweet and smart.
Thursday, September 20, 2007
Wednesday, September 12, 2007
Sprite AD of software engineer
Imagine
Your Colleague : Hey!! Kya yahan baitha mail forward karta rahta hai yaar !!
Naye packages dekh.... Naye language seekh. Night out
Maar....Fundoo programming kar like me....! Do something
cool man !!
You : Achha! To usse Kya hoga ..
Your Colleague : Impression!!! Appraisal !!! Har appraisal main tu No 1!
Hike in salary !! Extra Stocks
You : Phir kya hoga...
Your Colleague : Project Leader ban jaayega..Phir Project Manager !!!
Phir Business Manager ! One day U will be a Director of the
Company man !!
You : Acchha to phir kya hoga...
Your Colleague : Abe phir tu aish karega! Koi kaam nahin karna padega !
Araam se office aayega aur MAIL check karega.
You : To ab main kya kar raha hoon????
"Dikhawe pe na jao, apni akal lagao.
Programming hai waste, trust only copy-paste "
Powered by ctrl C
Driven by ctrl V
Tuesday, September 11, 2007
The quickest way to crash Windows 9x
The quickest way to surely bring down a Windows 9x machine: What happens is that we overwrite the "zero page" (which contains the interrupt table; including the IRQ vectors). Anything interrupt related (including the IRQ0 timer executed (normally) 18.2Hz) will make the processor jump to ffff:ffff, which doesn't contain any sensible code. Windows 9x is unable to recover from this.
Manually crash Windows XP
First: I do not take credit for this. This is information that I read in an article, But I feel it is a nice bug, and should be spread around so that microsoft might one day decide to fix their bugs!
The Bug:
CSRSS.EXE is a windows critical process. Make it crash and your whole system will follow. This affects all versions of windows NT (from source, My own test was only on win2k)
But how do you make it crash? The point to remember is that CSRSS.EXE controls the output of console apps.
Also, CSRSS has a bug on how it handles the backspace character while printing.
So the followin print statement will cause a small bug to appear:
printf("Crashing Your PC byte by byte ")
This bug is that CSRSS has now backspaced one character to many! In efect, it has now backspaced through it's video buffer memory. If the problem repeats itself too many times, CSRSS will cause a memory violation. Which will then make Windows kill the CSRSS.EXE process which in itself makes windows kill itself.
Now, this affects all outputs to the console, so you can either put that code into a while loop, compile in the language of your choice (that produces console apps) OR simply replece the printf statement with a fprintf and have the user dump the contents of the file on his screen ('type file' in the shell)
Now, This is not a very serious thing. It will not cause hard disk corruption (unless the reboot causes it), will not delete files, etc... But it can make an interesting DoS attack by implanting it into some program run on startup.
Hope this doesn't help ;)
The Bug:
CSRSS.EXE is a windows critical process. Make it crash and your whole system will follow. This affects all versions of windows NT (from source, My own test was only on win2k)
But how do you make it crash? The point to remember is that CSRSS.EXE controls the output of console apps.
Also, CSRSS has a bug on how it handles the backspace character while printing.
So the followin print statement will cause a small bug to appear:
printf("Crashing Your PC byte by byte ")
This bug is that CSRSS has now backspaced one character to many! In efect, it has now backspaced through it's video buffer memory. If the problem repeats itself too many times, CSRSS will cause a memory violation. Which will then make Windows kill the CSRSS.EXE process which in itself makes windows kill itself.
Now, this affects all outputs to the console, so you can either put that code into a while loop, compile in the language of your choice (that produces console apps) OR simply replece the printf statement with a fprintf and have the user dump the contents of the file on his screen ('type file' in the shell)
Now, This is not a very serious thing. It will not cause hard disk corruption (unless the reboot causes it), will not delete files, etc... But it can make an interesting DoS attack by implanting it into some program run on startup.
Hope this doesn't help ;)
Manually crash Windows XP
1. Start regedit. (If you are unfamiliar with regedit, please refer to this FAQ)
2. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
3. Create a new DWORD value and name it CrashOnCtrlScroll
4. Right-click on this newly created value and click on Modify
5. Enter 1 in the Value data field and click on OK.
6. Close regedit and reboot your system.
7. Now you can blue screen (crash) your system by holding the right CTRL key and pressing "Scroll Lock" twice.
Note:
Your system may reboot or show a blue screen whenever this crash is initiated. If your system reboots after initiating the crash, and you want to see the blue screen, follow these steps:
1. Go to Control Panel > System
2. Click on the Advanced tab
3. Under Startup and Recovery, click the Settings button.
4. Under System failure, uncheck the option Automatically restart.
...
2. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
3. Create a new DWORD value and name it CrashOnCtrlScroll
4. Right-click on this newly created value and click on Modify
5. Enter 1 in the Value data field and click on OK.
6. Close regedit and reboot your system.
7. Now you can blue screen (crash) your system by holding the right CTRL key and pressing "Scroll Lock" twice.
Note:
Your system may reboot or show a blue screen whenever this crash is initiated. If your system reboots after initiating the crash, and you want to see the blue screen, follow these steps:
1. Go to Control Panel > System
2. Click on the Advanced tab
3. Under Startup and Recovery, click the Settings button.
4. Under System failure, uncheck the option Automatically restart.
...
Subscribe to:
Posts (Atom)