Thanks for the information.  Unfortunately, since we're running our server on
VM, we'll have to wait a while to be able to bring everything into sync.
I'll let my customer know it's a temporary thing, though.

As I think about it more, though, as we were testing we backed up a few files
to a new node name just to check out the restore process.  I believe we
discovered before we did the restore that we had forgotten to change the icon
properties to point to the newly installed version.  We fixed that and then
restored the test files with version 316.  Which is pretty much what you're
describing here I think.

Thanks again.




ADSM-L AT VM.MARIST DOT EDU on 03/21/99 09:44:14 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: Re: Date modified Year - 1601

Hi Betsy,

Yes, I've noticed this a number of times. I'm not sure of the exact versions
involved, but it is somehow connected with trying to restore using an
earlier version of the client than did the backup.

For example, if you have a server running 3.1.0.6 and then, from a
workstation, which is running ADSM 3.1.0.1 (or maybe 3.1.0.3) do 'dsm
-nodename=server', you will see the 1601 date. The solution is to bring all
ng all
systems up to the same level.


regards,

Trevor