🚀 go-pugleaf

You're using a strange environment.  If you have at least 512K, you'll want
to copy your library into ram: and link like:

ln snarf.c ram:c32.lib   (or c.lib)

There's no sense in copying ln to ram because it takes little noticable time
to load but there's an incredible time gain with the library in ram.

Also, how in the world can you stand to type those HUGE disk names?
I've got my disks (backups) renamed to:
Az: for disk 1
Aex: for disk 2  (Aztec Examples)

Generally, keeping commands on disk and data files in memory has sped up
things to a much more acceptable level (besides, my disk drive makes noises
reminding of an Apple II drive grinding and such when linking)

Dan Wallach