All Things Microsoft > Microsoft Software
Windows Pranks!
worker201:
--- Quote from: Refalm ---So why not transforming the BSOD in a more user friendly dialog box?
Maybe with some less geek code.
--- End quote ---
The geek code is there for 2 reasons.
1) So that no one ever (not even the guys who wrote the code) can know what the fuck happened
2) You get a stock phrase that Indian tech support can recognize, therefore instantly interrupting you and saying "reinstall Windows"
mobrien_12:
--- Quote from: toadlife ---We've done this to one of the executives at work before.....
1) Take screenshot of desktop (print screen button + paint) and save it
2) Move all (movable) icons on desktop to a temp folder
3) Tweak windows so that it doesn't display any special icons (ie. Internu Exploder, My Docs, etc.)
4) Set the background as the screeshot you took.
5) Laugh as the (l)user tries to click on his/her "icons".
--- End quote ---
I had heard a similar version of this, but much less work to execute.
1) Take screenshot of desktop (print screen button + paint) and save it.
2) Set the background as the screeshot you took.
3) Hide the windows taskbar by dragging it down to the bottom of the screen.
Voila. The "start" menu doesn't work (unless you activate it from the keyboard). The clock is frozen at one point in time. None of the quicklaunch icons or system tray icons work. None of the programs show up in the taskbar.
Course, you could mess with the icons also, and really frustrate the poor windoid.
sjor:
EDIT
Kintaro:
--- Quote from: worker201 ---The geek code is there for 2 reasons.
1) So that no one ever (not even the guys who wrote the code) can know what the fuck happened
2) You get a stock phrase that Indian tech support can recognize, therefore instantly interrupting you and saying "reinstall Windows"
--- End quote ---
Err, its usually pretty typically stuff that anybody with a brain, a debugger, and source code can work out dude. I am guessing you just lack the first dependency, a brain.
worker201:
Fucktard, I was joking.
However:
The number of people who have access to the source code to all the programs which might have caused a BSOD is probably zero. And using a debugger at the address level is not simple at all.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version