 
								   9/30/93
Ŀ
  ******     NOW with ICMAINT.EXE your have no Icon maintenance!   ******   

Ŀ
              IconUpDater adds RIP_FILE_QUERY features !!!                 


	   This Version of IconUpDater does not read USERINFO.DAT if
	   you select NON-WILDCAT BBS software in the config program.
	   Meaning any BBS software that can produce a 52 line Wildcat    
	   3.x type DOOR.SYS file. I have included a copy of my DOOR.SYS
	   that Wildcat creates... the filename is DOORSYS.DOC.              




 
		   \   \  \   \ 
		    \  \  \  \  \  \
		     \   \ \  \ \  \   
		      \  \  \  \  \  \    
		       \    \    \     
			 Digital Universe Online!                          
		       WildCat 3.9 w/ RIP graphics
			       HOME of the 
			    
			      IconUpDater!
				  Door

		      \  \   \       
		     \  \ \  \ \                          
		    \  \   \       
		   \  \ \  \      \
		  \  \  \    (513)-324-8606


Ŀ
                               IconUpdater                                  
                                                                           
                                                                           
                                                                           
                            Copyright (c) 1993                             
                      With the most Features available                     
                       in an Icon/File Login updater.                      
                      And Great RIP Graphics interface.                    
                                                                           
                                                                           
                          ICONUPD.EXE   ver 2.40                           


		   You can file Freq this program from:
		 ASAD BBS (513)-390-1093   FIDO 1:110/685
			 Poll >  MAGIC  ICONUPD

		  You can also get a DEMO KEY from ASAD
			   if DUOnline is Busy.

Ŀ
 Important - - Start w/ 2.34  DNICON.CFG config file has 29 lines!         

Ŀ
 ICSETUP will automactically update your 2.10 and version of DNICON.CFG    

     IF YOU ARE RUNING AN VERSION of IconUpDater older then 2.10, then
     DELETE your DNICON.CFG file and RE-RUN ICSETUP.EXE !!!!



	      See DNICON.DOC for details!
	     Starting w/ 2.01. Version 2.01 has been re- KEYED, meaning
	     you will need ICONUPD.KEY in order for it to run.
	     Call DUOnline BBS
	     Read the NEWKEY.DOC for more info.



 This door was designed to decrease maintenance time for the sysop,
 while still offering other options.  I put everything in one
 ConFig file, so when it comes time to add more RIP Icons to you BBS,
 and therefore, your BBSICONS.ZIP file, you only have to change one 
 config file.  Just change the date, and if you have to, the paths and 
 file names.  That's it!  Plus with the NEW ICSETUP it is even EASIER,
 even for Multi-line BBSes!


  -----------------------------------------------------------------------
      You also need to make sure you have DSZ or GSZ in your DOS path
      or in the same directory as as the IconUpDate programs!!
  -----------------------------------------------------------------------
      This program supports COM 1, 2, 3, & 4 and IRQs 1 thru 15. 
  -----------------------------------------------------------------------



Ŀ
   Main Menu Options Defined:                                               


   IconUpDater is just that; an Up-Dater!  You have 7 options on the main
 menu, actually a RIP caller has 7 menu options and an ANSI caller has 
 6 menu options.  The one option a RIP caller has over an ANSI caller is
 the [A]uto Icon Scan Downloader, which Queries the existence of Icons on
 the callers hard drive.
 Two (2) of the 7 menu options is totally SysOp configurable! See below. 

 By the way - the KEYS in the brackets [], are the keys you have to
 setup for your users when making a custom menu. When making a RIP screen
 make sure you set your buttons as follows....

 !|1B3W0K0201F204000F0F050D00040F0700003W|1U6P5000000000<>Download Icons<>D

   Notice that the command set to the host is "D" and NOT "D^M".
   The "^M" sends the host a carriage return <cr>. IconUpdater does not
   need or use the <cr> expect for continue buttons.  An IconUpdater
   "Continue" button for any RIP screen, user defined or not, would
   look similar to the following...

 !|1B3W0K0201F204000F0F050D00040F0700003W|1U6P5000000000<>Continue<>^M

     [D]ownload ALL Icons

	    This is the options that most of your NEW callers and
	    NEW RIP BBSer's will use to get all you Icons in one
	    shot.  The idea here is tha when you update your icons,
	    say you added 4 more icons to your BBSICONS.ZIP file, well
	    your current RIP users are not interested in downloading
	    all of your icons everytime you add a few.  So you add your
	    4 new icons to your BBSICONS.ZIP and then....

	    If you make your own MAINMENU.RIP screen remember to set
	    your [D]ownload ALL Icons option to "D" not "D^M" like the 
	    above example.

     [J]ust download updated Icons

	    create another zip file of just you new icons for your
	    current RIP users.  They love not having to download the
	    same icons over and over, just to get the new ones.
      
     [I]nformation on RIP graphics
      
	    well if your callers are like mine you'll like this feature
	    also, especially since this program is the first thing your 
	    new user see.  Well they have heard of RIP, or maybe not, and
	    they have this Download Menu Options screen present to them?
	    Well, allthey need to do is select I for more info... and that
	    info is what ever you want it to be.  You can enter the text
	    to suit your needs, tell your users what ever you want. 
	    See DNINFO.TXT below for details.  You can create your own
	    RIPgraphics information screen, even if IconUpDater is
	    unregistered.  See below.

     [A]uto Icon Scan Downloader (Updater)

	    This is the New RIP_FILE_QUERY option. Only users who call
	    in to the BBS with RIPterm or QMpro will be able to select
	    this option.  If selected, IconUpDater will pass vitial info
	    to ICFILE.EXE, which will then perform all the necessary
	    processes for Quering Icons on the callers Hard drive.
	    
	    After the scan takes place and the caller needs more than
	    20 of your icons, then the program will give them a choice of
	    Abort the icon transfer or continuing with it.  If the abort
	    then the system is tuen over to the BBS and IconUpDater quits.
	    IconUpDater will also give the user the option to abort a
	    transfer if the need every icon in your Icons archive.

	    If the caller has all the icons, then IconUpDater notifies
	    the user as such, and then continues to the BBS.

	    Please try calling from another Computer with RIPterm
	    if you can.  It's truely a neato function.  For more 
	    detials on what Auto Scan does see below.
	    See ICFILE.EXE for more info.

	   
     [RETURN] to BBS!            (RETURN =  ^M in RIP)

	     where BBS is your BBS initials read from the ConFig file.
	     Self explanatory.  Exits Door.  A return key will work also.
	     If you run ICSETUP you will see that you as the SysOp have
	     the option to force to feature on your callers.  If you set
	     it to "Y" (Yes) then when the caller continues to the BBS,
	     IconUpDater will pass control over to ICFILE.  When ICFILE
	     is finished scanning Icons it will then exit to the BBS and
	     NOT return control to IconUpDater.

 
     AND...

     [_]_____________  ( you have 2 sysop definable Menu options now)
     
	      Blank!  Yep, you can put whatever you want here for your
	      users to download.  RIPterm? Maybe your MEMBERSHIP.DOC
	      file?  New important info!  Users can't get away from this
	      Door, since it runs everytime they get online, so make
	      it interesting for them.  Your description can only be
	      30 characters long!  If you make your own RIP screen
	      remember that your RIP Button command should just have
	      the letter you set up in your config file; for example
	      if you define a menu option for downloading your 
	      [M]embership file then your RIPscript command should
	      look similar to the follow, just having the "M" on then
	      end of the RIPscript.

 !|1B3W0K0201F204000F0F050D00040F0700003W|1U6P5000000000<>Member file<>M

Ŀ
   Download Menu Options Defined:                                           

      If you make your own DOWNMENU.RIP screen for your IconUpDater
  download menu, you will need to follow the same proceedures as above.  
  
     The download menu has for Menu buttons (or Options) you will need
     to put in your RIPscript screen.  They are as follows...

	 [X]-modem     [Y]-modem    [Z]-modem    [A]bort transfer

	 each of these buttons should be set up in this manner...

   !|1B3W0K0201F204000F0F050D00040F0700003W|1U6P5000000000<>Z-modem<>Z

       This does not mean you have to have this exact RIPscript...
       I am just saying make sure you have the command at the end
       with out a <cr> ( or  ^M ).



Ŀ
   Your LogIn.BAT FILE                                                      


     See DNICON.DOC for information on the DNICON.CFG (config) file!
     BUT, your best bet is to RUN the Config program ICSETUP.EXE!
     See the next section on ICSETUP.EXE.

  Sample LOGIN1.BAT file:

      C:
      cd\doors\icondown
      iconupd
      CD\WC30
      exit 
       
       More info on LOGIN.BAT files.  WildCat has 2 LOGIN.BAT files
       that I know of.  One is Login1.bat and the other is Login2.bat.

       Login1.bat will execute immediately after the user has signed
       in to the BBS.  After it is finished it then returns to the
       Open Hello screens, if the user did not use the Fast Login "*".
       Note: If the caller uses the Fast Login the login1.bat runs.

       Login2.bat executes after all of the Hello, Bulletins, and 
       Newsletter screens. Other than when it runs, it follows the 
       same attributes as Login1.bat.

       So... you can set IconUpDater to run anywhere, login1.bat,
       login2.bat, door6.bat, door6.run, whatever... it's a DOOR.



Ŀ
   ICSETUP.EXE  &  DNICON.CFG                                               


   DNICON.CFG
   
     Is the MAIN config file used by IconUpD.EXE  Make Sure that this 
     file is in the SAME directory as ICONUPD.EXE.

     Run ICSETUP.exe to Create or to Edit DNICON.CFG File

  ICSETUP.EXE
  
   The 1st question ask if you are runing Wildcat software.
   If you selct [Y]es then "WILDCAT" will be put on the
   1st line of the config file DNICONx.CFG and USERINFO.DAT
   will be used.

   If you select [N]o then "NON-WILDCAT" will be put on the 1st
   line of the config file and USERINFO.DAT wil NOT be used!

   I totally re-wrote this program starting with ver 1.87 and
   has been updated to 2.01.   

   ICSETUP now makes it easier than even to change or update your 
   information in your config file.
   
   This Program will Create the Config file "DNICON.CFG" if it does
   not exist and enter some of the standard information for you.

   If your config file DOES exist then ICSETUP will load it so you
   can freely edit each config line painlessly. 
   
   Important - if you are upgrading from a older version than 1.87
   then you should print out your old DNICON.CFG file, then delete it.
   After you have done that run ICSETUP and create a new DNICON.CFG.

  Multi-Line
  
   
   ICSETUP version 2.01 has really only changed for Multi-Line BBS
   SysOps...   You can now create Multiple CONFIG files in the same
   directory as ICONUPD.EXE (meaning NO multiple copies of the program.)
     
   Be sure to RUN ICSETUP and select #3 menu option for More info
   on setting it up.

       The multiple config file names go something like:

			     DNICON.CFG    <--- Main CONFIG.FILE
			     DNICON1.CFG   <--- Node 1 Config File
			     DNICON2.CFG   <--- Node 2 Config File
			     DNICON3.CFG   <--- Node 3 Config File
			     DNICONx.CFG   <--- Node x Config File

 |----------------------------*-Wildcat Only-*------------------------------|
 |                                                                          |
 |      When IconUpDater starts up it reads in the environment variable     |
 |      %WCNODEID% if you have your config file set to Multi-line "Y".      |
 |      Then IconUpDater adds this variable to the end of your door.sys     |
 |      and reads in your DNICONx.CFG....  for example:                     |
 |                                                                          |
 |              say a user calls in on node #4 then IconUpDater will        |
 |              first look for DNICON4.CFG. and read in the proper info,    |
 |              like the IRQ for Node#4 and the Locked Baudrate. Then       |
 |              it will look for c:\wc30\wcwork\node4\door.sys, and next,   |
 |              it will search for c:\wc30\wcork\node4\userinfo.dat         |
 |                                                                          |
 |              Get the picture?   I hope this make it easier on you.       |
 |                                                                          |
 |--------------------------------------------------------------------------|

   For other BBS software packages:

	In your login1.bat or door.bat pass the node # there...

	ex.          
	       c:                             c:
	       cd\DownIcon                    cd\DownIcon
	       iconupd 2          or          iconupd %1
	       cd\bbs                         cd\bbs
	       exit                           exit
		       ^
		       |--- this would load DNICON2.CFG file!
		     
	  To change a Node# Config file, just pass the number to             
	  ICSETUP when you run in from the DOS prompt... like so...
								      
			   c:/>ICSETUP 2

	   This will run ICSETUP with DNICON2.CFG loaded.  ICSETUP will
	   duplicate Node# Configs for ya also... that way you don't 
	   have to re-type all the config line back it.  Just select
	   Menu #3 ( [3].....Multiline (Y/N):>)..

	   REALIZE that you MUST compress all your icons for your BBS
	   into one ALLICONS.ZIP file... or ARJ file. Once you do this
	   and specify the path to this file in your DNICON.CFG file,
	   which ICSETUP makes for you, IconUpDater, along with
	   ICMAINT, will keep track of when you update your icons,
	   whether you add them, remove some, or just change them...
	   see ICMAINT.EXE for more info....



Ŀ
   DNINFO.TXT                                                               

   
   Edit this file to say what ever you want, up to 74 characters per line,
   7 lines max.  Your text will be displayed when a user selects option I
   from the main menu.  If you put more than 7 line of text, IconUpDater
   will lockup or exit with an errror message!  But READ ON....

Ŀ
            You can now create you own RIPINFO.RIP screen!!                


   You can also create your own RIP graphics screen for the [I]nfo on RIP
   option.  This file must be named "RIPINFO.RIP".  If this file exist
   then IconUpdater will send this screen instead of IconUpdater's.
  
   MAKE sure you have a continue button!  And you need to have that 
   button send just a RETURN... "^M".



Ŀ
  MAININFO.TXT  or Create your own MAINMENU.RIP screen!!                   

 
   Edit this file to say what ever you want, up to 74 charters per line,
   5 lines max.  Your text will be displayed just below the main menu!

   If IconUpDater is Registered you can create your own RIPgraphics menu
   screens!  The file name for the Main Menu has to be: "MAINMENU.RIP" and
   must be in the same DIR as Iconupd.exe.  I have added my first shot
   at @-codes also; but only 2.  They are:
  
		@UPDATE@  This is the Date you type is ICSETUP.
			  The date you last updated your icons.

		@LASTON@  This is the date the user was last on.
			  It comes from door.sys
   
   You can also make your own downlaod menu on the registered version!
   That file has be in the IconUpDater DIR and has to be called:
							     "DOWNMENU.RIP"


   note:  I have only selected to support RIP custom user menus. 

	

Ŀ
  USERLOG.TXT                                                              


   This file is created to tell you who downloaded what and when.  IF you
   delete this file, becuase it gets to long or something, IconUpDater will
   just create another one.  It just keeps APPENDing USERLOG.TXT forever,
   so it's a good idea to delete this file every so often.

Ŀ
  FORCED.LOG                                                               


  If this file does not exist, IconUpDater will create it.
  This file MUST be in the same directory as ICONUPD.EXE!  This LOG will
  keep track of who has download the FORCED FILE if you have "Y" on the
  last line of DNICON.CFG.  When someone downloads the FORCED File the
  user's name is added to this LOG.  A user will not be forced to 
  download your forced file if his name is in the LOG.  This means you
  have total control over who and when you want to make download your
  FORCED file.  
    For example, lets say you FORCE your users to download your BBS
    registeration text file.  Once they have downloaded it they will
    never be forced to download it again until you delete that user's 
    name from the LOG or til you delete the LOG all together!

    Let's say you have a log that's been running for a while, and you
    update you BBS registeration text file and you want everyone to
    download the new one. Well just delete the FORCED.LOG file and
    everyone will be forced again.  To not FORCE a file on a particular
    user, just put his name in the LOG exactly how it is spelled in
    the WildCat database.  

   With 1.6C update users who have not downloaded the Forced File (becuase
   their name is not in either of the Forced logs) then IconUpdater will
   run regardless of their last time on the BBS.  So if you have not been
   forcing your callers on any files, but ow decide to with this new update,
   IconUpDater will run and make all your callers download your new Forced
   file, regardless of whether they have recieved the updated icons or not;
   and put their name in one of the forced logs.  

   To totally turn off the FORCED feature just put "N" on lines 18 & 24
   of your DNICON.CFG file.



Ŀ
  FORCEDB.LOG                                                              


   This is the same as the above, except it monitors callers forced
   on Menu option #2.


  MORE INFO on FORCED LOGS:

       Says for example that you just started using IconUpdater and 
  would like to force your BBS Membership file on all your users EXCEPT
  those you are already members.  If you have WCPRO utilities then doing
  so will be easy.

      Remember that IconUpDater will not Force a File on a user if his
  name is in that Force file Log.  So say that you have IconupDater set
  up with the 1st definable menu option as RIPterm; then you most likely
  do not want to force RIPterm on your users.  But you have your Member-
  ship DOCs set as IconUpDater's definable menu option #2 (FORCEDB.LOG).

    Run WCpro select USERS then do a MATCH on all users who are MEMBERS.
  Then create a LIST; choose list by USER NAME only; then set output as
  "COMMA DELIMITED"; and last name the file (FORCEDB.LOG) and F10. 

  I would look at this new file you just create with a text editor to
  insure that it is a list of your MEMBERS.  

  Now run the program that came with IconUpDater called "CONVERT.EXE".
  This program will convert the file you jsut created in WCpro to a
  format that IconUpdater can read.

	It will ask you to enter the filename of the file you just
	created in WCpro.  Then it will ask you to enter the name of
	the output file.  It will default to ForcedB.log if you hit
	return. REMEMBER that Forced.log is for the first menu option,
	and ForcedB.log is for the second menu option!!!

  Now IconUpDater will check this file before running; and will not 
  Force the File under menu option #2 to any user list in ForcedB.Log;
  or it will not Force a file under menu option #1 if the user's name
  is in the Forced.log.

  If you have questions, please call during the posted hours below.




Ŀ
  QUES004.DAT                                                              


I have added a copy of my QUES0004.DAT file.  I use this to ask my callers
in a questionsnaire if they want to DISable the LogIn IconUpdater Menu for 
when they logon (next time)*.  Look at my QUES0004 with the program "makeques" 
and see how I ask them.  The answer goes in the "Comments 1" of the users
data base file.  If you modify the questionnaire make sure that you
have one of these 3 key words at the beginning of your user's Comments 1
database area.

 "Display"   - this turns ON the IconUpDater
 "Only"      - Will Scan & compare dates (see next item, Default Scan Update)
		Only run IconUpDater since last Icon update.
 "Never"     - will disable (turn off) IconUpDater

If you use your comments 1 user data area for something else then
forget about this option.  It won't work.  Either give up the 
Comments 1 for IconUpdater so your user who like Quick Logons can 
disable IconUpDater (just for that user), then give it up.

* Note: If you have "Y" on your 14 line of your DNICON.CFG file then
	 IconUpDater will NOT check the user's Comment1 field at all.
	 So if you want to give your user's a choice, set Default
	 Scan to "N".



Ŀ
  ICFILE.EXE  and  [A]uto Icon Scan Download.                              


     At this time ICFILE.EXE only support ZIP or ARJ file compression
     formats! 

     The proceedure:
	   When a RIP user selects [A]uto Icon Scan Download, IconUpDater
	   writes a TEMP.CFG file which pass the following info:
		      The BBS name
		      The CommPort definitions
		      The Path to your ALLICONS file
		      (this Path comes directly from your DNICON.CFG file)
	    
	  Then IconUpdater passes control to ICFILE.EXE.  
	  ICFILE then checks to see if the extention of your ALLICONS
	  file name is "ZIP" or "ARJ".  Next ICFile will create a
	  temporary directory and copy your ALLICONS file to it.
	  Then decompress your icons, delete the Archive ( ZIP or ARJ ),
	  then create a txt file of your icons.  Finally, ICFile starts
	  its FILE QUERY.

	  When ICFILE is finished in deletes all temp files and the temp
	  directory and return control back to IconUpDater; in other
	  words it cleans up after itself.

	  If there are Icons to Transfer, ICFile does not prompt the
	  user if they should be downloaded or not; ICFile starts 
	  sending them regardless(*); heck that's the whole reason the
	  caller selected this option.
	  (*)-Only if the total # of icons that need to be transfered
	      is more than 20 or the total # of icons in your archive.

	  Note: if the carrier is dropped while ICFile has control
	  ICFile will clean up after itself then return to system.

	  



Ŀ
  ICMAINT.EXE   ****                                                       


       This is the AutoSysOp Maintenance Program.

       Make a Config file for it:  ICMAINT.CFG  In this config you need...

 1st line  c:\dlicon            <-- Path to where IconUpDater is Located
 2nd line  c:\RIPaint\BBSicons  <-- Path to working Icons directory 

      You should only have Icons that you are currently using on your
      BBS in this Working Icons Directory.

      ICMAINT.EXE will decompress you ALLICONS.ZIP file into a Temp DIR.
      Then it will scan your Working Icons Directory (2nd line), and
      compare the 2.  If any icons were added, deleted, or UpDater (and
      still have the same) ICMAINT.EXE will updated your ALLICONS.ZIP
      file automatically.

      If ICMAINT.EXE updates your ALLICONS.ZIP file then it will also
      automatically UpDate the DATE ("The Date your Icons were last UpDated")
      in your DNICON.CFG (IconUpDater Config file).

      In conclusion, if you run ICMAINT.EXE as an Event at night, you will
      not have to worry about keeping IconUpDater upto Date as long as you
      keep your BBS icons in your BBS icon working Directory.
      




Ŀ
  Default Scan Update                                                      


   Default Scan Update and the RIP Menu option [A]uto Icon Scan Update
   are 2 different proceedure for the time being.

   Default Scan Update is set to "Y" (Yes) in your config file will only
   run ICSETUP is the user's last time on is older than your last Updated
   Icons date, which is also in your config file. (DNICON.CFG)
   By the way, the only other time IconUpDater will run when Default Scan is
   set to "Y" is when you have forced a file that a caller has not 
   downloaded.... see FORCED.LOG for more info (above).

       
   If Default Scan Update is set to "N" (No) then IconUpDater will not
   check the user's last time on versus your UpDated Icons Date... and
   therefore will run IconUpDater no matter what.


    Default Scan Update's Yes or No swicth is set on line # 14 
    of the config file!  
    If you have it set to "Y" then IconUpDater will compare the user last 
    time online date and the date you last updated your icons 
    (the date on line # 8).  If the user's last time on is older than your 
    icon update date, then the program will run.  
    If the user's last time on is more recent than the last time you
    updated your icons then the door will NOT run.  In default mode, 
    IconUpdate does not scan the user's "Comment 1" memo in the Wildcat
    Door.sys file. 

	  If you select "N" then IconUpdater will scan the "Comment 1"
    memo to see what the user's setting is.  For setting see above item.

	  Using "N" here give you the power to force your callers to
    see the IconUpDater Menu at Login.  Just incase you want them to see
    that you have some important you might want them to download; which
    you can put in the configurable menu option.


Ŀ
  Security Level Access Limiting                                           


    You have the option of limiting what menu options your callers
    have access to.  If you leave the defaults, (when running ICSETUP.EXE)
    then every caller will have access to all menu options.


    The reason for adding this option:
	A few sysops called me and said that my program made their
	icons easily accessible for others to download and use, basically
	stealing icons.  So they asked me to add security level limiting.
	This way the sysop has the option of verifying a user before 
	allowing a user to have access to the BBS's icons.


    The value you put in the config file is the minimum security level
    a user must have to access theat menu option.  For example, if I 
    entered a 20, then NO users with a security value of 19 or less
    will have access to that menu option.  

    You can set the access level for each of your 2 definable menu options 
    and you can set one access level value for the [D], [J] & [A] menu
    options.  See above for info on [D], [J] & [A].

    Relize that IconUpDater looks for the Wildcat "Menu access Level"
    value.  For example Wildcat comes pre-configed with NEWUSER (the 
    security level name) having a Menu access level value of 5.  This
    5, or Menu access level value is what IconUpDater uses, not the
    actual security level name.




Ŀ
  Legal Stuff                                                              



This is SHAREWARE, and no guarantees apply what so ever to any unregistered  
copies. On registered copies the author will only guarantee that you have
a working copy of IconUpDater.  Use the software at your own risk, registered
or unregistered.  IconUpDater is (c)Copyrighted.
This file maybe freely distributed in the original DEMO shareware format.
No one shall add or remove files from the original ZIP file.
See files.lst for the only files that should be in the ICUPDxxx.zip file.


Ŀ
  ICONUPD.KEY  files                                                       

    For reasons beyond beyond my control ( people who krack KEYs ), I will
    possibly create a new KEY file for each major version.  If you are a 
    registered IconUpDater User, you will have special access priviledges
    to DUOnline, which will enable to quickly login and Run the Registered
    IconUpDater KEY program directly from the IconUpDater Menu.  This will
    allow long distance caller to download there new KEY in a matter of
    minutes.  Realize that I will not have this get out of hand, to the
    point that you will have to call in every month or something like that.

    DUOnline is also in the process of Building a dedicated RIP support
    file area, where you can get the latest RIP stuff; like screens, Icons
    and support files.
   


Ŀ
  And By the way....                                                       


      Local Downloading is now available... why?   Well why the hell not.
      This is suppose to be a great door!!!

      Also try this...
	 Call IconUpDater from a remote system with RIPterm or WCpro w/RIP 
	 and click on the "IconUpDater ver #"...  go ahead I'll wait....
	 .... huummm.....  .....hummmmmm... 
	 Well?  Pretty cool huh?  bet cha didn't know that.


       Enjoy... 
			   -Ryan


Ŀ
  Registration                                                             


   You can quickly registered a Copy of IconUpDater Online with Visa
   or Master Card.  Or you can mail me a cashier's check or money order
   and I'll put your personal copy online for you and only you to download!
   I can also mail you a 3.5 or 5.25 if need be.
   There is no register.txt file in here... this is it.


			     === $23.00 ===

		     For Visa and MasterCard orders,
		    Cashier's check or money orders!
		 Stiff bouncing FEES for personal checks
	       that are returned as insufficient funds!!!
		 The sooner I get your check the quicker
	       your registered copy of IconUpDater will be
		available on DUOnline for you to Download.
	     
	     Program available by mail on floppy for $3 S & H.

	       See Register.FRM for more info on Registration.   
	
	    Registered IconUpDater Users receive Free Full Access 
		     Membership to DUOnline for a Year.

			Registered UpGrades are free!


-Ryan Andersen

Digital Universe Online BBS (513)-324-8606
212 1/2 E.Cassilly
Springfield, Ohio 45503

---------------------------------------------------------------------------
	       Feel Free to call me about Bugs or comments!
		    I'd like to know what you think!
	  Voice: 513-324-4587 between 3pm and 11:00pm ESTime or weekends
----------------------------------------------------------------------------
    This program uses Jeff Sumberg's QBserial for modem proceedure calls.
	     He is the sysop of SailBoard BBS (201)-831-8152.

