Posted by nonama on 06:25:00 07-31-2002
This competition is about crashing pc. smallest app that will crash your pc. win:95/98/me/xp/nt/2k platforms...
it wont be hard...
Posted by nonama on 06:25:00 07-31-2002
first submition
top:
jmp top
Posted by nonama on 06:27:00 07-31-2002
win2k didnt crash... so there are things to do...
Posted by nonama on 06:30:00 07-31-2002
i guess most fun would be to crash win2k
Posted by MooKeen on 09:37:00 07-31-2002
Hmm... let's take a look at what's wrong with this picture.
1. I've seen a lot of lame contests in my time-- this is the worst.
2. You can edit your post... instead of posting four times in a row.
3. See #1.
Yes, I know. I don't like mean people either
Posted by nonama on 00:15:00 08-01-2002
you wont believe but i found a nast feature called reboot in start menu. thats what we call windows :]
Posted by dougdrums1 on 06:36:00 08-06-2002
gha, forgot to enter my user and pass
Posted by KaGez on 20:13:00 08-06-2002
freeze?
[addsig]
Posted by dxprog on 10:54:00 08-07-2002
In VB there is an API that disables ctl-alt-del and the win key and other various things like that. Do that and run an endless loop without a DoEvents and your computer is pretty dang frozen.
[addsig]
Posted by KaGez on 12:12:00 08-07-2002
not just overloaded and slow?
[addsig]
Posted by dxprog on 21:42:00 08-07-2002
You're right. I'll have to think of something else. There is a way to freeze Win98. It's not code but I'll give it to you anyways. In the run box type C:\con\con and it's supposed to freeze.
[addsig]
Posted by KaGez on 12:53:00 08-08-2002
just write to the very first block of the RAM and overwrite the windows kernel in memory I think Windows won't let you do so, but I think it's a try worth
[addsig]
Posted by dxprog on 03:34:00 08-09-2002
Unhook your hard drive while windows is running.
[addsig]
Posted by KaGez on 11:33:00 08-09-2002
is that possible with asm?
[addsig]
Posted by robost86 on 01:45:00 08-13-2002
Sometimes I wonder where the YPN is going
KaGez is right, this is a stupid contest, and an even more stupid thread.
Well, to the contest... this depends on the system and the OS. For example, many CPUs have the so called f00f bug, which can be used to crash the computer from a _user program_, even in secure OSs, such as Linux or the BSDs. Windows 95 is easier, a com file that sends a reboot signal to the KBC (or writes over the V-86 interrupt table ) can easily crash/reboot the computer.
Posted by robost86 on 01:47:00 08-13-2002
(Hint for nonama):
Most NASM versions (except 0.98.8, I think), will assemble this to a 5-byte instruction:
begin:
jmp begin
Use this, to get a 2-byte instruction:
begin:
jmp short begin
Posted by dxprog on 02:17:00 08-13-2002
What is the f00f bug? My Pentium 133 has it according to Linux.
[addsig]
Posted by Darioush on 15:48:00 08-13-2002
Hehe & lol at the contest. using assembly is FAST.
(every1 knows the code)
Posted by MooKeen on 03:52:00 08-14-2002
Okay, to put this thread to death:
HLT
(Intel 4004 processors and up, as far as I know)
I win!
Blah,
D. Kuehn
Posted by robost86 on 19:12:00 08-15-2002
Darioush: What...?
MooKeen: Hah, that's protected in many environments. The f00f way can be used even in user code in e.g. Linux. Windows can be crashed by just about anything. DOS can easily be crashed by loading an _empty_ .com file. An even better way to mess things up would be "CLI". At least when you have permission to do that.
/Hannibal The Cannibal...or something like that.
Posted by MooKeen on 04:07:00 08-17-2002
Hmm, wait a minute... why would I want to crash my computer (or anybody's for that matter) anyway? I don't. I'd rather do something constructive.
Why did I post again?
D. Kuehn
Posted by robost86 on 04:14:00 08-19-2002
Feel free to be constructive, I'm niether way. I'm not good enough to do anything constructive, not even to do anything destructive
Posted by seunosewa on 08:17:00 08-20-2002
"We" don't believe that
"We" don't agree with you