9 bytes : smallest crap
[nfo]
|
||||||||
---|---|---|---|---|---|---|---|---|
|
||||||||
|
popularity : 62% |
|||||||
alltime top: #47723 |
|
|||||||
added on the 2004-01-03 12:52:41 by apricot |
popularity helper
comments
please leave a comment here if you know another 9-bytes msdos crap. I'm really interested ;P
added on the 2004-01-03 13:39:58 by apricot
The smallest crap?
This one doesn't crash the system under XP :)
This one doesn't crash the system under XP :)
the title fits... except for the "smallest" (for smaller craps, see the bastardized brainchilds of ryg and kb also known as the fr-016* series)
2 Gargaj : hmmm i mean smallest dos videomode (int10) dynamic one....
ryg&kb's smallest videomode one is 11 bytes :P
ryg&kb's smallest videomode one is 11 bytes :P
mov ax,13h
int 10h
wtf:
jmp short wtf
:)
int 10h
wtf:
jmp short wtf
:)
s/ax/al/ for an extra byte :)
ok smart guy :)
1] better mov al,13h cuz it's only 2 bytes and ax is 0 when app is loaded
2] D Y N A M I C means the picture on the screen changes. so ... you have to patch video memory somehow...
to do that you have to fill some segment register with 0a000h... etc
1] better mov al,13h cuz it's only 2 bytes and ax is 0 when app is loaded
2] D Y N A M I C means the picture on the screen changes. so ... you have to patch video memory somehow...
to do that you have to fill some segment register with 0a000h... etc
1] better mov al,13h cuz it's only 2 bytes and ax is 0 when app is loaded
Assumption.
2] D Y N A M I C means the picture on the screen changes. so ... you have to patch video memory somehow...
"dynamic" aka realtime has nothing to do with video modes. Oh, and I think, you don't really need to write anything in the video memory, screwing up some vga registers might be an even shorter route to bring 'some crap' on the screen. Whatever, all this is rather senseless idiocy anyway. ;)
Assumption.
2] D Y N A M I C means the picture on the screen changes. so ... you have to patch video memory somehow...
"dynamic" aka realtime has nothing to do with video modes. Oh, and I think, you don't really need to write anything in the video memory, screwing up some vga registers might be an even shorter route to bring 'some crap' on the screen. Whatever, all this is rather senseless idiocy anyway. ;)
push word 0xb800
pop es
wtf:
stosw
inc ax
jmp short wtf
hehe :)
i'm not sure if it complies your rules (there is no int10h call) but it does work :)) and it flickers! :))
pop es
wtf:
stosw
inc ax
jmp short wtf
hehe :)
i'm not sure if it complies your rules (there is no int10h call) but it does work :)) and it flickers! :))
2 Tomaes :
1] proven with sice ! :)
2] yes, it is
2 Gargaj:
in that case fr's fuenf(inyourface) is
much smaller than your example.
1] proven with sice ! :)
2] yes, it is
2 Gargaj:
in that case fr's fuenf(inyourface) is
much smaller than your example.
in that case fr's fuenf(inyourface) is
much smaller than your example.
i never said it's not :))
much smaller than your example.
i never said it's not :))
the best shitty crap i've ever seen.
:O
Ha ha ha :-)
I did the same effect and it was 47 bytes :(
this prod is just like being able to jump on top of your bike really really quickly without having a clue about how to ride it.
yeah, this simply rules! impressive!
Amusingly, i did exactly the same as mft_9b_2.com more recently (http://www.pouet.net/prod.php?which=4767) without knowing about this one.
(i did it after the one posted just above in the same thread by b_killer). There's not many possible combinations.
The trick is too have 2 embedded instructions (adc ah,al and daa) right before the stosb so the loop + 1 will give:
instead of:
from the second time it is executed due to the fact that we're jumping directly into the "middle" of the int 0x10 (which is 2 bytes).
Other possible values are: 11 0d and 0f for the gfx mode
and si di bp sp for the offset register added to segment reg. es in les instruction.
Any other may lead to a crash or to black screen.
I don't think it can get smaller while keeping moving (shitty) colors bars.
(i did it after the one posted just above in the same thread by b_killer). There's not many possible combinations.
The trick is too have 2 embedded instructions (adc ah,al and daa) right before the stosb so the loop + 1 will give:
Code:
adc ah,al
daa
stosb
instead of:
Code:
int 0x10
les sp,[bx] ; si di bp sp
stosb
from the second time it is executed due to the fact that we're jumping directly into the "middle" of the int 0x10 (which is 2 bytes).
Other possible values are: 11 0d and 0f for the gfx mode
and si di bp sp for the offset register added to segment reg. es in les instruction.
Any other may lead to a crash or to black screen.
I don't think it can get smaller while keeping moving (shitty) colors bars.
This is not the smallest crap, you suck!
finally
Wtf?? I've been beaten ;-( (long ago, i see :-D) Good work i guess... Anyway, this smallest shit thing is getting a bit boring, let's do something else ( ;-)) ) Ie. who can code the most gfx effects in 256 bytes, 1-15 sec/part, variegation is a bonus! [20bytes/piece avg=10 effects, 2 min playtime! What a demo it could be!!] We could also enter them to a standard 256b-compo, and then also to www.256b.com!
Sure it's small, but it's also ugly and totally pointless. Why not try even 128 bytes?
quiete useless
amazing ! 9 bytes ? lol
stop these annoying int10h stuff please. it's a disgrace to assembly... :(
argh
A 16 byte i2c EEPROM costs 42cents, a 128 byte one costs 46c at out local store... (comes in SOT-23 1mm by 2.9mm packaging =) ) Larger capacities are cheaper! Hey guys, why don ya write 4K/64K with lots of effects (+story)?! Would be prettier...
Balls!
13h mode and 9 bytes.
show please source code (:
Man, can't you disassemble it?
broken link (:
Gluk, Intro Inferno has not broken links and it supplies (almost) all smallest PC intros.
Pirx, thank (:
Hehe! But stop this crap :)
crap indeed
no ESC ;)
nice
naming prods "crap" always deserves thumbs down when they actually are crap.
what Sense said
oh crap!
submit changes
if this prod is a fake, some info is false or the download link is broken,
do not post about it in the comments, it will get lost.
instead, click here !