The main issue that have to be settled before going into details is how
compatibility shall be maintained. I.e. patching the existent format or do
a fresh start on someting that can last and solve compatibility by a
conversion program for those who want to continue their use of old
software.

Hanging on to a solution suffering from more and more problems for every
additions needed is in my opinion a wrong way to go. As longer we wait, as
harder will it be the day it becomes impossible to go on with those
patches.

A new format can carry all the information that exists in the present list.
If we choose a format with field identifiers then future additions and
compatiblility with old software will be no problem at all. In my opinion
that is the only option that make sense.

Where lies the big problem with a convertion routine? As I can see, it is
only a question of obtaining a pice of software and add a new line before
the nodelist compiler in the .BAT or shellscript that handles nodelist
compilations.

If the new list comes in a new file-echo and maybe with a new name there
will be no confusion. The old software will not recognize it as a nodelist
or nodediff until it has been converted. A list in the present format can
be distributed in paralell during a reasonable time to make a smooth
transition possible.

 M.v.h. //Haakan

--- MyPoint Windows 2.03xE