GUSTEST.EXE v1.21        4/6/1993

  GUSTEST is a simple program which detects the base address of the
  Ultrasound and how much memory is installed.  (For some reason on
  my system DRAM lies and says I have 768K. And no, I'm not running
  SBOS at the time.)

  If you specify the -t option, GUSTEST will write patterns to check the
  DRAM installed on the GUS.

  If you specify the -u option, GUSTEST will assume you're using unsigned data.
  
  If you specify the -s option, GUSTEST will assume you're using signed data.
  
  If you specify the -w option, GUSTEST will swap data bytes for 16-bit samples.
  
  If you pass filenames to GUSTEST, it will play them as .SAM files.

  If you specify the -d option, GUSTEST will dump the DRAM contents to screen.
  
  The -b option lets you choose 8-bit (-b8; default) or 16-bit (-b16) SAMs.

  The -z option clears the DRAM.

  This is my first GUS program so far... apologies if you think it sucks.
  Written using Turbo C++ v1.01 in C mode.

  -- Michael Chen     mchen@cs.psu.edu          3/23/1993

  A tiny fix (< instead of <=) was made to prevent 1024K GUS owners from
  being told they have an extra 256K. (4/5/93)

  The block-move and block-set routines were speeded up considerably.
  I can now clear 256K of DRAM to zero in 3.3 seconds, including program
  loading from disk/cache.  Also includes source, with C (and C++?) code
  for using the GUS.  No assembler required... it's all in Turbo/Borland
  C.  Enjoy! (4/18/93)

SOURCE CODE USAGE NOTE

  If you use this for free or public domain software, please let me know
  and send me a copy of the program.

  If you use this for programs which require a fee, please send $10 to me.
  The address below is valid through early August 1993; after that, send 
  e-mail to the above address for an updated one.

        Michael Chen            (until 8/93)
        144 East Cherry Lane
        State College, PA 16803

  In any event, the source code distributed here may not be altered for
  distribution without my permission (so I can keep track of changes).
  Mention of the use of these routines should appear somewhere in programs
  which use it (not just in comments, please).