
                    - Creative Interface Design, Inc. -
                                  presents


                                 "TREKKER"
                            
         Qmodem Vers. 4.3 sharware host mode for use with RIPTERM 1.54

   If you've always wanted to do something with RIP, if you've heard about
   it - yet had little to no idea as to how to implement Remote Imaging 
   Protocol on your BBS but never really had anything experiement on, or 
       found the documentation that came with RIPTERM too dry, then
   roll up your sleeves and prepare to get icky up to your elbows, because
   this is the next best thing to putting rip on a BBS, without having to
   worry about endangering your hundreds, even thousands of hours worth of 
   Ansi work and the general state of your BBS...and for those who are 
   curious about, but don't operate a bbs, knowledge is power...try this 
   out...:)

   "Why RIP?"  Well, unless you're running Mosaic under Windows, there are 
   very few telecomunications programs which will provide PCX and higher 
   graphics quality.  
   Rip(Remote Imaging Protocol) is one method of transcending bandwidth by
   allowing the user/client system hang onto the necessary graphics and 
   commands to create screens.  
   Ripterm accomplishes this using a scripting language/protocol which is 
   compact and can work on any system/server/network which supports typical
   Ascii...in fact, a system doesn't even have to be able to understand 
   the RIPSCRIP to serve as a host to a machine that does...and many RIP 
   files are incredibly small.  
   
   Getting Started...
      Okay, you've unpacked the QMTREK.ZIP file, and now have this file
      and a ZICONS.ZIP file and a HOST.ZIP file.  Here's what you have
      to do to implement this host mode.

      1) COPY the HOST.ZIP file into your host modes' download 
         directory.
      2) Create 2 new subdirectories under your Qmodem subdirectory which 
         will hold your old and new *.hst files, this is important.  You 
         should name them destinctively enough so you don't confuse them.
         -Copy all your current host files *.hst into the subdirectory 
          for all your old Ascii hostmode files.
      3) copy the HOST.ZIP file into the new subdirectory for rip files 
         and unpack all the new RIP *.hst files
      4) Once that is done, back out of the new subdirectory and into your
         qmodem directory, where you will write 2, 1-line batch files.
         These batch files will allow you to switch between Ascii and 
         RIP.  They should look like,

      c:\qmodem> copy con asci2rip.bat
      copy c:\qmodem\riphst\*.hst c:\qmodem
      ^z

      c:\qmodem> copy con rip2asci.bat
      copy c:\qmodem\asciihst\*.hst c:\qmodem
      ^z

      5) The person who calls your system will have to have a copy of the
         icons...and they should log on in Ansi or Ascii initially...so 
         please don't have the RIP icons active within the Qmodem 
         subdirectory when you go to host mode...do a local logon before
         your guest calls just to be sure.
      6) Once they log on and download the packet, they will need to unpack 
         the icons into a subdirectory under your system's name in their
         RIPterm dialer...if this seems too intricate, they can also unpack
         them in the icons subdirectory for RIPterm, but this is going to
         make things messy in the long run; this option should be used only
         if nothing else seems to work.
      7) Once this is done, they can either call back, or if they shelled 
         to dos, then all you have to do is drop to dos, run the batch file
         that copies all the RIP .hst files into the qmodem directory, and
         then when you turn them lose again, they should see some rip...
      -NOTE: If your caller doesn't get anything but funny boxes with
             the names of missing Icons in them, and they have the icons
             in a subdirectory under your number, then have them try calling
             back without hanging up...this will reinitialize RIPTERM and
             ensure that it knows where to find it's icons.

A final word...
   Although it is necessary to utilize an editor like DeadPaint, Tombart, and
   a hoary host of other RIPSCRIP editors out to manipulate Icons and use
   different fonts effectively, what is written to the screen as regular text
   is still clearly visible in a text edit of the ripscrip file.  So keeping
   in mind that RIPSCRIP can be transmitted over any system w/o setting off
   bells and whistles, you can edit/delete, and revise any of the text you
   see inside the RIPscrip files.  However, please remember,
   \    <-these are continuation symbols, delete them and ugly things 
          happen.
   ((listname::field1, field2, field3)) <- Picklist example...powerful stuff!
   

   This is your chance to learn about RIP...good luck and let me know
   if there is anything I can do better with this...:) 
   Thanks...

   David Chandler '95
 
 RIPterm and RIPscrip are trademarks of Telegrafix Communications, Inc. 
 Qmodem 4.3 is a trademark of The Forbin Project, Inc. 1991

 Creative Interface Design, inc. 
 -We don't need no steenking Pentiums-
