@Her_Kitty_Daddy - thoughts for this modification?

I addressed it over in http://forums.dlink.com/index.php?topic=54848.msg236095#msg236095
The crux of it is, the information needed for this sort of thing is
already saved in the configuration file so instead of coming up with a second export/import process (read "Error ****e" & redundant) it would be better if the import process for a configuation file (which already exists) could allow for some selectivity in restoration.
If designing it I would have the restore screen provide a list of checkboxes that will be restored (all on by default) and you can click off the things you don't want overwritten.
A sparkling example of this would be if you wanted to set up a second NAS, you don't want to overwrite the new networking information with the same information in the already running unit.