pouët.net

Enough already. Will you make all possible ugly combinations of asm opcodes in 32b or what ?

Everything has already been said ...

Nigga please!

Gluk, if making (it's not even coding, it's making) such things is fun for you, do it even every day, but don't release them as demoscene productions. Because of that "prods" people associate 32B category with spam, do you think it's ok? Try to realize some 128B or 256B reasonable project.

If you like asm hacks, I recommend releasing them all at once as an intropack ;-). But seriously, a stray interrupt will overwrite your code when messing up SP like this -- even under pure DOS. ESCable versions, please?

Ok, I did that a few times, but it's not like anyone will keep looking at my 32Bs for 32000 frames ;-)

The lines are diagonal but my thumb goes straight down. Cut it out already and code something with a point :)

i once wrote a program which would take a 256b intro, modify a few bits and test the result in dosbox, by analyzing it's screenshot. using 10 different versions, the two best ones would be merged, by randomly taking parts of both, making new children. (you probably remember this from some website, just using fpga chips? :D)
to get to the point: since my screenshot-analyzer-code was lousy and lame, after some iterations the result was exactly like your last three 32b submissions here. please stop adding such random crap, or i'll add a "auto-submit prod to pouet"-feature.

(actually i won't since all bit-modifications were completly random and the results run only on dosbox, not on real thing)

there's still science to do \o/

UTTER UTTER UTTER CRAP!

The day when the crap learned to reproduce itself :(

oh snap

I haven't rated this yet?!
If you're going to make shitloads of minimalistic(size-wise) intros, then consider yourself to release them in an intropack or something so that you don't release them every time you change place of a XOR operand.

GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK ! GLUK !

what everyone else said

well, i think its crap :D

but don't stop doing those,and don't stop releasing them. we all release shit here in some way or another.

waffle, xor is not an operand.

For the benefit of Waffle;

http://www.smartcomputing.com/editorial/dictionary/detail.asp?guid=&searchtype=&DicID=18416&RefType=Encyclopedia

eehrm...
4 postZ by me in the last one...and still i just wasted my Time,i guess...
...c´mon,Gluk...do a search for "32b" on Pouet,watch em ALL and come back(release) sth again,when you are SURE no1 (or in these cases many other ppl) achieved exactly the same thing already "once upon a Time".!
sry,i had a bad day.! ;)

still.: what Quisten said.!! ;)

XOR is not an operand, but "XOR operand" is a perfectly good term for "the operand associated with an XOR instruction" - just like "steak knife" is a perfectly good name for the knife associated with steak, even though steak is not a knife. As such, waffle's comment makes complete sense.

Pirx, Shockwave - you fail at grammar nazism :-P

Gluk can release what he has pleasure for.

@gasman
do you mean "XOR opcode"?

gasman, English is primitive language and I'm not sure what waffle had exactly on mind, but tone of his comment suggests he can be wrong. I didn't write he's wrong, take my comment as "just so you know" tip, not as a biting remark.

Bash me if you will, but I actually fell for this one. (The only thumb up this prod is going to get, I reckon)

xor operandcodes (hah!) rule the world. just like thumb downs \o/

okish

fuck no

holy shiiite.