| |
Sorex
Account closed
Registered: Nov 2003
Posts: 43 |
Compo and challenge rules
Howdy,
Just wondering...
If you have a challenge like that scroll or bbs gfx thing with a certain limit how is this limit counted?
if the limit is set to a 256 bytes program is then the actual filesize as seen on pc/mac/etc
256 (254+2 bytes load address)
or
258 (256+2 bytes load address) ?
imo the load address is not really part of the actual program. |
|
... 1 post hidden. Click here to view all posts....
|
| |
iAN CooG
Registered: May 2002
Posts: 3194 |
wrong for me, 1block is not 256byte intro, that would make only 252 bytes available for code, 2 bytes are for the t/s link (or size if single block) and 2 for load address. To me 258 is the correct size for a 256 bytes intro, what matters is the size in memory of the loaded file (of course what it does to the whole memory after running doesn't count). |
| |
Sorex
Account closed
Registered: Nov 2003
Posts: 43 |
so in that scroll thing it's 258 aswell?
which is where I'm at at the moment :) |
| |
Cruzer
Registered: Dec 2001
Posts: 1048 |
In the beginning I always counted only the data loaded into the C64 memory, which means 258b .prg filesize. Then I got some complaints from lamers on Pouet and decided to try to limit the .prg to 256, or even 254 to keep it within a disk block. But really I don't think meta data shouldn't be counted. Then we should also include the filename etc.
|
| |
Sorex
Account closed
Registered: Nov 2003
Posts: 43 |
ok thanks, so we bend for noobs? :)
I've added 3 of them in the d64, it's in the releases part of this site. |
| |
Ninja
Registered: Jan 2002
Posts: 411 |
Nonono, I never said 256-byters should have one block. I say there shouldn't be 256-byter on C64 ;)) (And for the topic matter: I would just consider the 256 byte on a C64; why should it matter how much bytes are occupied on a different system? What about a D64 then?) |
| |
Frantic
Registered: Mar 2003
Posts: 1648 |
When I did the "tinysids" (some 256 byte music compo that were held a while ago) I always made sure to make them fit within one block on the disk. That filesize of "1" looks so neat....and wasting that second block with only 2 bytes of data or so is such a horrible waste of data. ;) |
| |
Devia
Registered: Oct 2004
Posts: 401 |
Should be 1 block imo.. The load address can be (ab)used too and thus should be counted. And yes the 1 block count in the dirlist looks neat ;-)
|
| |
enthusi
Registered: May 2004
Posts: 677 |
so let's vote to rename that entry category since 256b IS different from one block and rises the question of load address every time... |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Load addy vs. ELF/PE-header
T/S link vs. inode/fat/ntfs-entry
With that in mind it should be 256 bytes including load addy. But 1 block in the dir list do look neat, however a 256b .prg file also looks neat and that for more users/viewers aswell.
Lucky windows-dudes can use .com-files however which have no header, good for them.... |
| |
TNT
Account closed
Registered: Oct 2004
Posts: 189 |
Quoting CruzerThen we should also include the filename etc
Yes we should if code doesn't work if you do LOAD":*",8,8 instead of typing that strange-looking 16-char filename in full. JSR ($00bb) anyone... ;) |
| Previous - 1 | 2 - Next |
