File and setting transfer wizard: status file

[Guest]

Before I re-installed Windows XP Pro on my Laptop I wanted to save my files
and setting from the laptop.
I run the wizard on my laptop, writing the files to a sub-directory on a
Windows 200 server on my network. Every thing ran ok without any errors.
When running the wizard on the laptop to pickup the files and setting I get
the message " The location that you specified does not contain stored
information. Please type a valid folder path into the edit box". The folder
contains a folder called USMT2.UNC and that contains one file "IMG00001.DAT".
Looking into this my “status†file is missing. Is there ay way to recover
from this? The DAT file is 1.99GB in size.

 

[Johan Arwidmark]

There is a utility named fastconv that can be used to extract data
from a USMT 2.x store (and FSTW is using a USMT 2.x data store)

This tool can be optained from PSS or from this link
http://windowsxp.mvps.org/utils/FASTConv.zip


regards

Johan Arwidmark
Microsoft MVP - Setup/Deployment

 

[Ron Martell]

Before I re-installed Windows XP Pro on my Laptop I wanted to save my files
and setting from the laptop.
I run the wizard on my laptop, writing the files to a sub-directory on a
Windows 200 server on my network. Every thing ran ok without any errors.
When running the wizard on the laptop to pickup the files and setting I get
the message " The location that you specified does not contain stored
information. Please type a valid folder path into the edit box". The folder
contains a folder called USMT2.UNC and that contains one file "IMG00001.DAT".
Looking into this my “status” file is missing. Is there ay way to recover
from this? The DAT file is 1.99GB in size.

Did you point the FASTW at the containing folder or at the USMT2.UNC
folder?

When I use FASTW (which is quite often) I always create a folder named
\Transfer to save the data into, and FASTW creates a USMT2.UNC folder
within it. When I go to restore the data I point the program at the
\Transfer folder and it always works for me.

One question. Did you update your new installed Windows XP before
running the FASTW? If not then that may be a factor, as there have
been some updates to FASTW. If your data was created by an updated
version of FASTW and your new install is an older version that has not
been updated then that could explain the type of behavior that you are
experiencing.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2006)
On-Line Help Computer Service
http://onlinehelp.bc.ca

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."