Sorry - I forgot to mention that our cache hit is 98.23 so that looks ok.
And, agreed, the command line is slightly faster but not dramatically
different.  Where we see the big difference is when we boot the client from
an alternate partition, simulating the destruction of that client.  Our
first testing had this alternate partition with a different node name than
the original which caused us to have to specify the path to restore a disk,
directory, or file.  We got very slow performance with this.  Next we
changed this alternate partition to have the same node name as the original
client so we could then do a restore without being forced to specify the
path.  Unfortunately, this had the same result.  So at this point we have to
believe the problem is something to do with running the client from an
alternate partition (and, therefore, not running from the C drive).  I have
seen statements that the client should be running from the C drive, but if
you lose the client entirely, how do you restore enough of the client to get
back to the C drive to then complete the rest of the restores?
 
No changes are being made to the file system types, either.  At this time we
are dealing with a test NT box, deleting the data or formatting disks and
trying to recover it to exactly the same hardware and software.
 
Examples:  restoring a directory of 178 MB of data, 2925 objects took 2:35
minutes when restored from the original client, while it took 1 hour and 10
minutes when the restore was initiated from the alternate partition.
Restoring the D drive, 195 MB, 4955 objects took 4:25 minutes from the
original client, while it took 1 hour and 41 minutes when initiated from the
alternate partition.