Why does DHTML Menu Builder requires configurations you may ask.

Configurations are pieces of information that let DMB know about your web site. Remember that DMB is a tool to create navigation systems. Usually you create your web site structure with some other tool, such as ColdFusion, FrontPage or Dreamweaver, but then you use a third party application (DMB) to create the navigation system.
Is because of this that DMB needs to know about your web site as much as possible.

DMB uses two configurations to work one local and one remote:

• Local/Relative: These are used by DMB to know where to put the files it creates. The paths specified on this type of configurations will be used by DMB to save the javascript and images (if any) that conform your menus.
  The internal links used by the menus when using a configuration of type "relative" are relative. This means that the menus will work from any resource, including your local computer, a web server, a CD-ROM, etc...

  ---

• Remote: Remote configurations are used when the menus need to use absolute paths.
  Setting up remote configurations tends to be somewhat confusing for some users. Here're some questions that you can ask yourself that may help you determine what to put on the Paths section of your remote configuration:
  • What do I type on the browser to access the web site using my browser?
    That’s the Web Server Root
    For example, to access our web site we type: http://software.xfx.net/
    ...so that’s exactly what we have on the Web Server Root parameter

    ---

  • What would I need to type on the browser to download one of the .js files generated by DMB?
    Well, on our case I would have to type this: http://software.xfx.net/menu/iemenu.js
    So… the path to the compiled files parameter must be: /menus/

    ---

  • And finally, what would I have to type on the browser to download one of the images used by the menus?
    Again, I would have to type this: http://software.xfx.net/menu/images/ofolder.gif
    So the path to the images must be: /menu/images/

And what's the difference of making a configuration the default configuration?

DHTML Menu Builder will always use the local/relative configuration Paths information to know where the files created at compilation time must be stored (saved).

Now, the paths and links used internally by the menus are defined based on the configuration set up as the default one.

If your default configuration is one of type relative, the internal paths to the images, to the javascript files and the links in your menu items will be relative.

If your default configuration is of type remote, then the paths will be server based (absolute), which means that your menus will be "prepared" to work from your web server only and will.