

      Required configuration changes from Version 0.91.wb
      ---------------------------------------------------
      
There are not much changes necessary in this new version of XenObm

The most important thing is: You MUST update your COST.TBL. This is,
because the cost-calculation have changed since the 0.91.wb.

You can now define up to 20 different and fully independent timetables
(see the TIMETABLE statement in the sample COST.TBL).

Further, you must set up the rules for using this timetables. This can
be done with the USE statement, as shown in the sample COST.TBL.

And finally, you have to update your zone-configurations, because a new
feature called "opening fee" is supported by this version of XenObm.

The syntax of the USE statement is:
-----------------------------------

USE Zone_name dayrange:Timetable [dayrange:Timetable] and so on.

Example: USE local 1-5:weekday 0,6,7:weekend
                    |    |       |      |_____ name of a timetable
                    |    |       |____________ days to use
                    |    |       
                    |    |_______ name of a timetable
                    |    
                    |_____________range of days
                    
Days are defined as: 0=Sunday to 6=Saturday

The special day number 7 is a placeholder for all holidays, which are defined
with the HOLIDAY statement in COST.TBL.

Please be careful with the order of definitions in the costfile:

1. Define the Zones
2. Define the Use - rules
3. Define the timetables
4. Define the holidays
5. Define the dial-tables (phone numbers)

Point 2. and 3. may be swapped, should cause no problem.

The Syntax of the HOLIDAY statement is:

Holiday 1.1,25.12,26.12,.....

You can use more than one lines for this job, but every line must start with
the "HOLIDAY" keyword. (see the sample COST.TBL).


New feature: OPENING FEE: 
-------------------------

In some countries, you have to pay a so-called "opening fee" for each 
successful call. It's easy to configure this in the COST.TBL:

Just add this fee to your zone-setup, for example:

In the 0.91 a zone definition looked like:

--> Zone local N:80,67 C:90,67

now add the opening fee to each tag:

--> Zone local N:80,67,10 C:90,67,10    (valid in the 0.92.a and later)

If you don't need this feature, simply set the opening fee to "0".


New configuration statement: EDITOR 
-----------------------------------

With this, you can set up your own preferred texteditor for all editing jobs.

Syntax is:

  EDITOR x:\path\name %s, where the %s stands for the filename.
  
It is possible to pass some options to your favorite editor like:

  EDITOR d:\bin\fte\fte.exe -mTEXT %s
  
The above starts my favorite editor (FTE is the successor of the well-known
WWED/2). The -mTEXT option overrides the default editing mode.


Archiver Configuration:
-----------------------

If you want to use the enhanced features of the packet-viewer (delete
mails or packets), you have to configure your compression programs.
XenObm supports: ZIP, LHA, ARC, ARJ and RAR. There are built-in
defaults available, assuming that your archiver programs can be found
in your PATH.

If you need to change the compression programs, you must do this in
XenObm.CFG (see sample file).

