| |
ChristopherJam
Registered: Aug 2004
Posts: 1408 |
When is a One-File Demo not a One-File Demo?
So, I've finally finished a small release (title+one effect+music), except it's 250 blocks long even before I decrunch it; initial load is from $0801 to $fffe
It's all a single file, that if I send to my c64 via codenet it runs just fine standalone, but in order to make it loadable with stock 1541+c64 I'm bundling it with the Effluvium loader. (cf Packer/decruncher for under IO?)
Should I make the Release Type "C64 One-File Demo" or "C64 Demo"? |
|
| |
Ejner
Registered: Oct 2012
Posts: 43 |
c64 demo imo. |
| |
WVL
Registered: Mar 2002
Posts: 899 |
Good question..
A while ago, there was this single-load slideshow that fitted in one file that was >600 blocks long.. now, is that a singlefile demo or a demo? I'd say the latter...
As for this, I'm not sure :) |
| |
Flavioweb
Registered: Nov 2011
Posts: 463 |
Single and stand-alone file executable that don't need a disk image (d64....) to load data?
If disk image is needed... should be named "demo"...
IMHO. |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1408 |
@Flavioweb, Well, disk image is not needed to run the thing; all the effects code, graphics and music are all in a single 250 block file that starts with "10 sys2061". It's just that the kernal load routines are too stupid to load under ROM/IO. Any decent fastload cart should be able to load it directly.
@WVL, how can a 600 block file be single load? Surely there's only room in the c64 for 258 blocks, and even that wouldn't leave room for a loader?
Anyway, I'll go with c64 demo for now I guess; corrections welcome. |
| |
Bitbreaker
Registered: Oct 2002
Posts: 504 |
@ChristopherJam: Now stop making us wet and release this thing!!! :-)
I'd say anything that fits into memory with a single loading action is considered a onefile-demo. |
| |
JackAsser
Registered: Jun 2002
Posts: 2014 |
Quote: @ChristopherJam: Now stop making us wet and release this thing!!! :-)
I'd say anything that fits into memory with a single loading action is considered a onefile-demo.
Agree, and if it doesn't work with standard KERNEL loader then it's a crippled one filer. If you then add a loader to it to make it work with KERNEL it will become a demo. :) |
| |
The Human Code Machine
Registered: Sep 2005
Posts: 112 |
Did You try ALZ64 to squeeze the file into 202 blocks? If it works just make two downloadable versions. One for impatient cartridge owners and one for all the others ;)
ALZ64 |
| |
Oswald
Registered: Apr 2002
Posts: 5086 |
Quote: So, I've finally finished a small release (title+one effect+music), except it's 250 blocks long even before I decrunch it; initial load is from $0801 to $fffe
It's all a single file, that if I send to my c64 via codenet it runs just fine standalone, but in order to make it loadable with stock 1541+c64 I'm bundling it with the Effluvium loader. (cf Packer/decruncher for under IO?)
Should I make the Release Type "C64 One-File Demo" or "C64 Demo"?
so where do you decrunch to? $0000-$0800 ? :D |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1408 |
Ok, it's up. Jam Ball 2
@The Human Code Machine, it's already crunched!
Very good @Oswald. (FWIW I decrunch to $0200 to $ff6a :P) |
| |
ChristopherJam
Registered: Aug 2004
Posts: 1408 |
My apologies The Human Code Machine, I was overly dismissive of your suggestion. For some reason I didn't think of applying ALZ64 to the released file, rather than the precrunched file.
I'd thought ALZ64 was a poor fit because it requires the input file size to be in range $0003..$F800, which prior to using my own simplistic packer Jam Balls exceeds.
However, the file I load from disk is just under the upper limit, so I just gave it a go.
It's pretty effective, but sadly not enough to make this a one filer. File size drops from 250 blocks to 230. Decrunching also takes forever! |
... 13 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 | 3 - Next |
