Omnimaga
General Discussion => Other Discussions => Humour and Jokes => Topic started by: shmibs on August 25, 2010, 09:19:15 pm
-
(http://img.removedfromgame.com/imgs/1282785481-virus1.gif)
(http://img.removedfromgame.com/imgs/1282785507-virus2.gif)
-
Woah what? That looked cool. You made it, right?
Also, I saw a real virus do something similar before on Windows 98 at school.
-
yeah, i made it. it's cooler on calc, because if the user manages to exit before it asplodes the os will do wonky things like displaying 50 progs named JO until the RAM is cleared or simply refusing to run anything
-
@shmibs: You are now the official reason Blast Antivirus has to be made.
-
That looks neat. What language is it coded in?
lol @ Raylin ^-^
-
Lol Raylin nice one :P
-
the question is if Blast would be able to catch this program o.O
-
Yeah, it needs to not be inspired from Norton. Also would Blast freak out when someone would type STARTKEYLOGGER on the home screen on a linked calc?
-
that is in axe, and it uses a VERY simple function to achieve that effect(a cookie to anyone who can guess)
-
Oh, oh, masked sprites? ;D
-
Bitmap?
-
Hm, that might work too. How is it done, shmibs? ;D
-
Some random position, a couple of boxes layered on each other to make it look 3d-ish and some text all at that point? At least that would be the way I'd do it ...
-
Asm(00 for the RAM clear?
-
Asm(00 does nothing :P (it's a nop). The relevant line is Asm(C7, which simulated pulling a battery, IIRC.
However you can crash the calc in pure Axe. Something like Fill(E8000,E7FFF should work nicely ;D
-
Lol
-
I would be scared if this happened to my computer. Or calc.
-
Especially the calc :)
-
Asm(00 does nothing :P (it's a nop). The relevant line is Asm(C7, which simulated pulling a battery, IIRC.
However you can crash the calc in pure Axe. Something like Fill(E8000,E7FFF should work nicely ;D
that's pretty it.
every time a box is displayed a random byte in RAM is erased(resulting in all the possible OS hijinks even if the user exits the program). even though it only directly affects the ram, im a bit hesitant to put this on a data-filled calc(i've only tried it in emu and on my disposable 83+). could this possibly mess with routines that do interact with the archive to mess things up?
-
Extremely, ridiculously unlikely (and possibly impossible), but it might happen.
Even if it can, it'd be extremely rare.
-
interesting, what kind of weird OS things had been happening if you quit early?
-
yeah, i made it. it's cooler on calc, because if the user manages to exit before it asplodes the os will do wonky things like displaying 50 progs named JO until the RAM is cleared or simply refusing to run anything
also, random characters displayed on the homescreen or the plot icons not appearing at the top of the screen under y=
-
More fun is simply doing "rand->{rand", with an optional "}r" at the end ;D
Or have I mistaken you and is that what you're doing? (From what you said I inferred "0->{rand" or similar)
More fun is a program that does simply that multiple times. How long until this code crashes your calc? (Make sure Ans is between 0 and 65536, obviously)
Ans->X
For(I,1,X
rand->{rand
EndPrograms that slowly screw up your calc are fun :P
-
Lol I wonder what would happen if someone wrote a program that loads about 2000 programs in your RAM and 7001 others in archive. I wonder if the PRGM menu, Mirage OS and Doors CS would even be able to handle this.
Another thing, put . at the start and check how Axe Parser compile menu behaves ;D
-
Lol I wonder what would happen if someone wrote a program that loads about 2000 programs in your RAM and 7001 others in archive.
>9000 programs! the calc would probably explode. :P