pouët.net

Requires lastest DirectX and may crash while exiting.

Yeah it aint really a 1k if you need to install an operating system to make even the simplest task with your computer.

Download the official directx distrib instead of juggling with dlls: http://www.microsoft.com/downloads/details.aspx?FamilyId=0A9B6820-BFBB-4799-9908-D418CDEAC197&displaylang=en

That's the url i was looking for yesterday:

http://www.microsoft.com/downloads/details.aspx?FamilyID=402111c4-6478-46c1-bbd9-1bf9fcce52f4&displaylang=en

April 2005 DX redistribuable files.

http://www.microsoft.com/downloads/details.aspx?FamilyID=402111c4-6478-46c1-bbd9-1bf9fcce52f4&displaylang=en

or

http://www.speckdrumm.org/EvilOne/d3dx9_25.dll

The volume of the sound is rather low

I'll explain you:

Here i played with darkness & lighting to set the gloomy mood & to make the volumes appear to be more numerous than they really are.

This is not really about what you present but more about how you present it.

Nothing is really 1k or 4k or 64k or whatever size limited stuff, there's still dependencies of some kind. The dll i used (which was also used in the 4k intro "parsec") will soon be shipped with every directx around, it just comes a little bit before it's time.

And don't think doing such stuff it's just a matter of calling an external dll function (and even that takes bytes too, so it's never for "free") that would do everything, you can't directly write on the screen as it was possible under dos or on other machines, you have to open a window, obtain a directx interface, etc.,
Opening a window & obtaining a directx screen & setting a projection matrix & waiting for the esc key with a frame counter, all that in a windows exe, takes approx 550 bytes once packed.

Asm instructions & datas are gathered in a way they'll ease the compression flow of the file. Datas are re-used as much as possible to increase redundancies or are crafted to be similar in some ways, values of the processor's registers must be known at every possible step to have the opportunity to use them as a base to do operations in a smaller way (eg. directx calls returning 0 in eax if everything went fine, etc.), not to forget the structure of windows executables files which is rather big (in a 1k world, everything is big) and have to be crafted by hand too (optimizing tools aren't precise enough).

And that's not all, you must think carefully about what you want to show because you just can't do any effect you can see all around, there's simply no room for this, sometimes you can't even choose the colors as it may break the flow of compression, etc.

1k of brainfuck.

Btw, i uploaded an improved version (with a less harsh sound in stereo this time).

I'm using the same xp version, the requirements aren't too high unless your gfxcard can't display 800x600x32 screen, Also it works in dx retail & debug mode. I don't know if it works on nvidia cards, but i guess it does.

http://www.speckdrumm.org/EvilOne/d3dx9_25.dll
http://www.microsoft.com/downloads/details.aspx?FamilyID=402111c4-6478-46c1-bbd9-1bf9fcce52f4&displaylang=en

Prepare to be sorry for a long time then, because in the future you'll see a *lot* of 4k & 64k intros using the same dll under this name or an other (and it have already begun with the winning bp 4k). It is exploding plastic inevitable.

At first i used your dropper utility but it wasn't able compress it enough so i had to make my own tool.
Note that the packed version and the unpacked one are the same byte for byte (no ordinal imports, etc.).



That dll is the new incarnation of the directx helper library. Ms don't leave any alternative as it doesn't exist as a static library anymore.



Actually, i think i found a new trick regarding this :D
Wait & see.