I enjoy collecting old text files and
demoscene stuff. There's a lot of people interested in this
stuff, so you can find a lot of old archives of ASCII/ANSI artwork,
e-zines, demos, cracktros, music and other stuff.. It also helps
that there's basically a perfect working emulator for almost every
hardware platform ever created.
Recently I discovered that Jason Scott had given a speech on Inter-Pirate battles through the years.
It's really facinating to read some of the files that get passed back
and forth between groups. You can get the archive here. There is also this site which you can spend many decades searching and looking at notices.
There also happens to be a load of Scene related collections on
archive.org. Below I'll start with some links to my favorite
Scene sites, and then provide some technical information about running
Running graphic demos in Linux using Wine:
Running modern graphics demos under Wine is
a hit or miss. Apparently it boils down to how Wine can
process the items which use Windows proprietary calls (like Direct3D)
to interact with
the graphics card. On the other hand, running old school DOS,
Amiga, or C64 demos under Linux works great becuase we have emulators
such as DOSbox, FS-UAE, and Vice.
32 bit Windows demos can be run simply via
"wine xxxx.exe", YMMV. One thing I've noticed is that getting
vertical sync to work with OpenGL in these demos is a bit
strange. I use Nvidia graphics cards and tearing is something
that my eyes are very sensitive to. So I always configure my
systems to sync to vblank for OpenGL rendered content. In demos
using Wine I've noticed that sometimes you actually have to turn the
vsync off to get the vsync to
work! Apparently this has to do with the way Wine interacts with
the nvidia setting utility. More info here. If you see tearing in an OpenGL demo
and use an Nvidia card, try setting this environment variable before
running the demo with Wine:
UPDATE There's a new emulator on the block called FS-UAE and it's using the WinUAE codebase. It kicks ass, is easy to configure, and has already gained a huge following. I strongly suggest using it for Amiga emulation on Linux.
I consider the info from here on superceded by FS-UAE, but will leave it in case someone needs it. In Linux there is basically one native Amiga emulator and that is called UAE. There is the E-UAE version from Richard Drummond, then there is a OpenGL bilinear vsync patched version, then there is the actively developed P-UAE version which is attempting to port to different OSes and bring it to the level of WinUAE (discussion forums here).
The keys to success is
a good .uaerc configuration file since the GUI doesn't open up to all
the different options. I linked to mine here,
you'll need to tweak it for the directories you're using and your other
preferences. I use an LCD on my main box and like to have the low
resolution from emulated systems smoothed out and vsynced. The
GUI of these different versions is the same. Below I listed the
most important parameters to setup. ADF format programs are just
Amiga Disk Formats, so you can load them up into the section that
allows you to load floppy disks. When you run "exe" style Amiga demos you make the directory containing the demo exe as a hard disk, and make the
exe as executible in Linux. When the emulated Amiga boots into
the workbench environment, type in the full name of the exe like
this "demo.exe" and press enter. You also need a copyrighted
kickstart ROM image to make this all work, which is not difficult to
68020 with 68881 FPU, fastest speed with timing
JIT 8092 MB cache
Chip 2 MB
Slow 1 MB
Fast 8 MB
Z3 zorro 64 MB
Here is an example of using CLI techniques and scripts to run DOS demos using DOSbox:
Find some DOS demo you like. For example, recently I saw some demoscene videos called The Art of Textmode by RaD Man of ACiD and The Full History of the Demoscene by Tamas Polgar. In The Art of Textmode, RaD Man mentioned this old school DOS demo called Starport by Futurecrew, and he liked it becuase of the early parallax scrolling it used.
Create a text file in the same directory as the DOS exe and call it starport.conf, copy the following into it:
mount C "/home/xxxxx/Scene" -t dir
Create another file in the same directory and call it starport.sh, copy the following into it, also make it executable:
dosbox -conf ./starport.conf ;
Now simply run the starport.sh script and watch the results.
may need to tweak some of the parameters in the conf file. Read
the default dosbox conf file that should be located in your
/home/xxxx/.dosbox directory.for information about what all the options
mean. You could also just use the example configuration above in
your default .conf file, so then all you need to do is run DOS programs
like "dosbox xxxxx.exe"
If you want to use a GUI interface to DOSbox then I recommend DBGL. It's a simple interface and allows you to create profiles for individual programs.