|
If you want to use any images or text from this site you must get written approval first. Click HERE to send an email request explaining your intended usage. |
| ../ | [Parent directory] |
| Date | Size | Filename | Description | |
|---|---|---|---|---|
| 1997-02-16 | 9712 | Birthday.prg | ||
| 2000-02-01 | 8237 | Birthday_n.prg | A vic-20 demo released 11.8.1990 by Secundus of Pu-239. 16k extra memory required. Load and run. Separate PAL and NTSC versions. Re-sourced, NTSC-fixed, compressed and uploaded by Albert of Pu-239 ([email protected]) | |
| 1998-04-16 | 7134 | Bouncing Ball II.d64.gz | Bouncing Ball II (for unexpanded Vic-20). The winner of the Alternative Party '98 demo competition. | |
| 1998-04-16 | 21703 | Bouncing Ball II.zip | This packet contains source code, binaries in separate files and some information. Uploaded by Viznut/Ocsa ([email protected]), http://www.hytti.uku.fi/%7Evheikkil/ocsa/. | |
| 1997-08-27 | 5958 | Cuckoo-clock-source.zip | Source code of the cuckoo clock program in DASM format | |
| 1997-08-19 | 7431 | Cuckoo-clock.prg | A cuckoo clock for the VIC-20 written by Timo Raita <[email protected]>. This interrupt-driven program reads the system time (TI$) and plays cuckoo samples at half and full hours. Requires at least an 8k expansion. | |
| 1995-03-05 | 304 | Fine scroll.prg | A scroller demo. The scroll is not too fine on PAL-B systems. SYS8192 to start. Requires an 8k expansion. | |
| 1997-02-16 | 4467 | PU-239 in Lahti.prg | ||
| 2000-02-01 | 4003 | PU-239 in Lahti_n.prg | A vic-20 demo from 1989 by Secundus of Pu-239. 8k extra memory required. No sound included. Load and run. Separate PAL and NTSC versions. Re-sourced, NTSC-fixed, compressed and uploaded by Albert of Pu-239 ([email protected]) | |
| 1997-02-23 | 3627 | PU-239-demo.prg | ||
| 2000-02-01 | 3408 | PU-239-demo_n.prg | The very first vic-20 demo by Secundus of Pu-239 (15.2.1989). 3k memory expansion required. Load and run. Separate PAL and NTSC versions. Re-sourced, NTSC-fixed, compressed and uploaded by Albert of Pu-239 ([email protected]) | |
| 1997-02-16 | 5467 | Pacman.prg | ||
| 2000-02-01 | 4741 | Pacman_n.prg | A vic-20 demo from 1989 by Secundus of Pu-239. 8k extra memory required. Load and run. Separate PAL and NTSC versions. Re-sourced, NTSC-fixed, compressed and uploaded by Albert of Pu-239 ([email protected]) | |
| 2000-02-01 | 38531 | Pu239-1990-src.lha | "Re-sourced" source codes for Pu-239 VIC20 demos from 1989 and 1990. (Pu-239 in Lahti, Pu-239-demo, Pacman, and Birthday) The sources are compilable with at least DASM 2.12. | |
| 1994-06-25 | 3329 | VIC20-AR89-1.prg | ||
| 1994-06-25 | 750 | VIC20-AR89-1.readme | A simple demo for the unexpanded PAL Vic-20, written in June 1994. Only seems to scroll text on the screen. | |
| 1997-01-15 | 25934 | VVV-NTSC.lha | Veni vidi Vic!, 6560 (NTSC-M) version. Some parts of this demo are available separately, so that they can be loaded on an unexpanded VIC-20. The demo itself requires an 8k memory expansion and a 1540/1541/1570/1571 disk drive. | |
| 1996-12-24 | 29655 | VVV-NTSC.sfx | Veni vidi Vic!, 6560 (NTSC-M) version. This self-extracting archive can be loaded and started on a Commodore 64 or 128. | |
| 1997-01-15 | 26160 | VVV-PAL.lha | Veni vidi Vic!, 6561 (PAL-B) version. Some parts of this demo are available separately, so that they can be loaded on an unexpanded VIC-20. The demo itself requires an 8k memory expansion and a 1540/1541/1570/1571 disk drive. | |
| 1996-12-24 | 29881 | VVV-PAL.sfx | Veni vidi Vic!, 6561 (PAL-B) version. This self-extracting archive can be loaded and started on a Commodore 64 or 128. | |
| 1996-12-24 | 75317 | VVV-src.tar.gz | Source code of Veni vidi Vic!, World's first known trackmo (multipart demo that loads from disk while running) for the VIC-20, developed in 1996 and published on The Party '96 in Denmark. For more information, see http://www.hut.fi/Misc/cbm/vic20-demos.html#VVV. |
[FTP://NIC.FUNET.FI/pub/cbm/vic20/demos/ | SunSITE ftp | SunSITE http]
[email protected]
|
If you want to use any images or text from this site you must get written approval first. Click HERE to send an email request explaining your intended usage. |