Click above to get retro games delivered to your door ever month!

     This keyword allows you to  specify which soundfile to play  when a
     specfic event occurs. The following <eventtype>'s are defined:

         EVENTTYPE       TRIGGER:

         Arealist        When the arealist shows.
         AskYesNo        Any Yes/No type prompt.
         Attention       Warnings or information popup messages.
         DosShell        When entering a DOS or OS/2 shell.
         EditComment     When an editcomment is found.
         EndOfMsgs       When there are no more msgs in the area.
         ErrorFatal      Fatal error exit.
         Exit            Exit from GoldED.
         JobDone         Successful completion of a job.
         JobFailed       Unsuccessful completion of a job.
         MsgDeleting     When deleting a msg.
         MsgFromYou      When a msg from you is found.
         MsgIsLocal      When a msg marked Local is found.
         MsgIsTwit       When a msg from a Twit is found.
         MsgToYou        When a msg to you is found.
         SearchFailed    Search operation failed.
         SearchSuccess   Search operation was successful.
         Startup         When the GoldED startup screen shows.

           There is currently only one <eventcommand> defined:

         PLAY <filename.ext/beepnoise>.

     The parameter  to PLAY  can be  either a  sound file  or one of the
     following standard beepnoises:

         TheEnd    A high and a low note.
         GotIt     Two sets of low-high notes.
         TooBad    A falling note.
         ToYou     A rising and falling note.
         SayBiBi   A single beep.
         SOS       Morse S O S (...---...).

     If a  sound file  is specified,  the sound  driver must support the
     format.

     The DOS and 386 versions  need a Goldware Sound API  compatible TSR
     or program loader which  installs an interrupt service  function on
     the multiplex  interrupt 2Dh.  See the  chapter about  the Goldware
     Sound API for more  details. The GCTVSAPI program  loader (released
     separately) currently only supports  the CT-VOICE.DRV driver for  .
     VOC files.

     The  OS/2  version  relies  on  MMPM/2 (using the mciSendString API
     call) to play the  sound files. On my  system with a Sound  Blaster
     Pro, MMPM/2  plays both  .WAV and  (to my  surprise) .VOC files. It
     even plays .MID files :-)

     The Win32 version uses  the Win32 API to  play the sound files.  It
     should be able to play  any multimedia file that Windows  knows how
     to handle.

       Example usages:

         EVENT MsgToYou  PLAY HIMAN.VOC
         EVENT MsgIsTwit PLAY SHOTGUN.VOC

     You have to select the sounds carefully and probably with a lot  of
     experimentation, unless  you want  to turn  your mailreader  into a
     honking, wailing and farting monster and drive your poor family  or
     yourself nuts with a cacophony of noises...