![]() ![]() ![]() |
|
Dstarzero: Install Keylogger, check bank account, then pay the balance of their credit card
mwahahaha
Ray Taylor
There is no place like localhost
Spreadsheet for Comparing Electricity Plans Here
graemeh: Remove the 1, 2, 3, 7, 8 and 9 keys from the numeric keypad and put them back in the same order you get on a phone (1, 2, 3 across the bottom). This can really confuse some people because it looks "right".
Just a heads up to all you pranksters, someone has made a fantastic site for this:
Just open the relevant animated screen, and put the browser in full screen (usually F11). Enjoy.
Dairyxox:
Just a head up to all you pranksters, someone has made a fantastic site for this:
Just open the relevant animated screen, and put the browser full screen (usually F11). Enjoy.
Was just about to post this
Also makes a BSOD if you push enter.
Another good one I heard about recently was putting the top number row in numerical order (0..9).
Try Vultr using this link and get us both some credit:
remember the days of IRC, someone posted something like this
user1: if you type your password in it appears as *s
user1: see **********
user2: mypassword123
user2: hey i can see it!
user1: only you can, we only see stars
user2: that is so cool!
For some reason I did not reply to this thread earlier, but I had a lot of fun with two outstanding harmless prank programs in the early days of MS-DOS (before graphics interfaces). These were little memory-resident utilities that played with the text screen. One was called 'Drip.Com' and it would cause random characters in lines of text to gradually drop down the screen until all the letters collected at the bottom. The other was called 'Danish.Com' and it would slyly replace different letters on the screen, eventually creating a hilariously garbled version of the text that was still understandable, but resembled a kind of pseudo-Scandinavian alphabet.
These programs worked by directly reading and writing the screen buffer, so no changes were made to any data. They didn't hurt anything but they did cause a lot of head-scratching in some corporate computer rooms at the time.
Plesse igmore amd axxept applogies in adbance fir anu typos
WindowsME
Had a colleague who would leave his phone right by his monitor. His ring tone was "thunderstruck" by ACDC.
Plugged my sound output into his monitor, and played Thunderstruck off you Tube at random times, he always thought it was his phone, but could not work out why it rang, but he didn't show any missed calls etc.
And one Joke I tried backfired, and nearly got me.
I was going to change someones settings, so every time they typed a certain phrase, it would change it . Firstly though I tested on my own PC. I changed the word Cheers to Go F yourself....
Try as I might, I could not get it to work, until I replied to an e-mail sent via a phone, and it had converted it to another format. Luckily I had spell checker on, and it pulled up the F word, and offered me appropriate alternatives. I spent the rest of the day scared I had sent out several replies with that cheery salutation...
surfisup1000:
Not so much the computer, but taping down the phone hook so the phone keeps ringing when they pickup.
Also not so much the computer, but I did used to enjoy calling a colleague via an outside line through the PABX, so it rang with the external ring cadence. Then immediately transferring that call to another colleague - the PABX saw that as an outside call as well. Both would usually answer pretty quickly as we were in an in-bound customer service role. The ensuing argument over who-called-whom was side-splittingly amusing. The joke came to an end once I'd run out of target combos that hadn't twigged to the game.
If someone hasn't locked the screen around here the usual practice is to rotate the screen with <control>+<alt>+<right arrow> ...
Setting all the apple computers in computer labs at uni to make the Big O noise at start up.
Mike
Okay, so this kinda falls into the 'breaking things' category but...
A company I used to work for (highly Linux orientated) had a tradition of in the support department, breaking the new guy's computer - intent been if they can't fix their own computer, how can they fix a customer's?
One guy went the 'old school' route and used tape to insulate one or two pins of an ethernet cable so it'd still Link-UP but transmission would be all funky (I never saw this in person, only second hand).
When I started there, one of the guys realising I was quite apt and fast at spotting the issues got me good by setting the immutable bit on files which caused a lot of havoc & confusion.
My trick was simply to modify the kernel options and tell the kernel to boot up with only 128 or 256MB of RAM blending that option in with the kdump configuration. Then to cap it off, insert a forkbomb into /etc/profile.d so it'd get triggered by init scripts. Even when they fixed the forkbomb they'd still get confused by the running out of memory issue.
Fun days.
OK I saw a couple of good VB script ones around, and took it to the next level...
Save this as a .VBS file, and double click to try it... dosn't do anything malicious I promise
It might error out if you don't have an exchange profile setup (it uses that to get your name) not sure.
Creepyscript.vbs:
Set app = CreateObject("Outlook.Application")
Set ses = app.GetNamespace("MAPI")
Set oVoice = CreateObject("SAPI.SpVoice")
ses.Logon
strFullName = ses.CurrentUser.Name
Set app = Nothing
Set ses = Nothing
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run "notepad"
WScript.Sleep 100
WshShell.AppActivate "Notepad"
WScript.Sleep 700
WshShell.SendKeys "{ENTER}"
WshShell.SendKeys "Hel"
WScript.Sleep 400
WshShell.SendKeys "lo "
oVoice.Speak "Hello"
WScript.Sleep 1600
WshShell.SendKeys strFullName
oVoice.Speak strFullName
WScript.Sleep 500
WshShell.SendKeys ", do "
WScript.Sleep 800
WshShell.AppActivate("Notepad")
WshShell.SendKeys "not "
WScript.Sleep 600
WshShell.SendKeys "pan"
WScript.Sleep 700
WshShell.SendKeys "ic "
oVoice.Speak "do not panic"
WScript.Sleep 700
WshShell.SendKeys "i'm "
WScript.Sleep 700
WshShell.SendKeys "here "
WScript.Sleep 700
WshShell.SendKeys "to "
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "he"
WScript.Sleep 700
WshShell.SendKeys "lp"
oVoice.Speak "I'm here to help"
WScript.Sleep 800
WshShell.SendKeys "{ENTER}"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "Ar"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "e yo"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "u fe"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "eling"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys " al"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "rig"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "ht?"
oVoice.Speak "Are you feeling alright?"
WScript.Sleep 3100
WshShell.AppActivate("Notepad")
WshShell.SendKeys " Ye"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "s?"
oVoice.Speak "Yes?"
WScript.Sleep 1700
WshShell.AppActivate("Notepad")
WshShell.SendKeys " Go"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "od!"
oVoice.Speak "Good!"
WshShell.SendKeys "{ENTER}"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "No"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "w, "
WScript.Sleep 1200
WshShell.AppActivate("Notepad")
WshShell.SendKeys "Ho"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "w ca"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "n I"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys " hel"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "p? "
oVoice.Speak "Now, how can I help?"
WScript.Sleep 3100
WshShell.AppActivate("Notepad")
WshShell.SendKeys "Sha"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "ll"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys " we "
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "pri"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "nt "
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "thi"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "s pa"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "ge"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "?"
oVoice.Speak "Shall we print this page?"
WScript.Sleep 2100
WshShell.AppActivate("Notepad")
WshShell.SendKeys " OK!"
oVoice.Speak "OK!"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys " Th"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "is "
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "wi"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "ll "
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "help "
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "docu"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "ment "
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "ho"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "w a"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "we"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "some"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys " you"
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "'re "
WScript.Sleep 700
WshShell.AppActivate("Notepad")
WshShell.SendKeys "feeling right now."
oVoice.Speak "This will help document how awesome you're feeling right now"
WScript.Sleep 2100
oVoice.Speak "print, print, print"
WshShell.AppActivate("Notepad")
WshShell.SendKeys "^p"
WScript.Sleep 1800
WshShell.SendKeys "{ENTER}"
WScript.Sleep 2700
WshShell.SendKeys "%f"
WScript.Sleep 300
WshShell.SendKeys "x"
WScript.Sleep 200
WshShell.SendKeys "n"
|
![]() ![]() ![]() |