problem: while trying fastconv extracts only to temp directories but does not rename files because it crashes while extracting TRANSDB.DAT
problem: using fastconv you get Source store is invalid
1) make sure you keep the old store safe on the external drive
2) reboot the new system
3) disable screensaver
4) check local drive(s) for space - you need 3x old store size in free space
5) create a directory FAST on the local system
6) start FSTW on the new system
7) do as though you would make a new store but select Files only
8) point FSTW to FAST on the local system e.g. C:\FAST (use browse to find it)
9) Select files only
11) after it finishes you should have a new store under C:\FAST\USMT2.UNC
12) close FSTW
13) open an explorer window containing the old store e.g. F:\USMT2.UNC
14) open an explorer window containing the new store in C:\FAST\USMT2.UNC
15) delete ALL .DAT files from the new store and leave only the status file
16) select all .DAT files from the old store - NOT the status file
17) right-click -> copy
17) go into the new store window right-click ->paste (this copies all old.DAT files into the new store location
18) after this finishes (make sure it does so correctly) wait 30sec then disconnect the external drive
19) You now should have a number of .DAT files in C:\FAST\USMT2.UNC and one status file
20) reboot - then start FSTW again
21) this time select "I am on the new system"
22) and "I already have the files"
23) point to the new store parent directory (C:\FAST) and start
That´s it. In other words do not use fastconv in this scenario.
You may still have migwiz.exe crash in the end, but all files should be back.
Now if for some reason you STILL cannot access the files you should try fastconv on the store to get
the temporary files created up until TRANS/DB.DAT (or as far as it goes before crashing).
A few remarks regarding fastconv.exe - the standard versions (older) cannot handle SP3 created stores.
Get the fastconv version from http://www.fastimgwiz.com/fiw_setup.exe (download and install fastimgwiz trial version and copy fastconv.exe - and only fastconv.exe - from the installation directory to the root of the drive where the store is)
fastconv cannot read stores that were created on another drive than that the store was created on - period
meaning if you created a store to an external drive you can only read the store using fastconv if you point to the external drive like so:
e.g. (assuming external drive is F: and primary local drive is C:)
f:\fastconv /V /S:F:\USMT2.UNC (This verifies the store with tmp files being created in %TMP% on C:). N.b. you cannot keep tmp files using /V
f:\fastconv /S:F:\USMT2.UNC /D:C:\RECOVERED (This extracts the store to C: with tmp files going into %TMP%)
So, if you still have no access after the solution in Main Section try this:
using the fastimgwiz fastconv.exe version in the parent directory of the store: (forget about tmp for now)
F:\fastconv /S:F:\USMT2.UNC /D:C:\RECOVERED
Make sure \RECOVERED does not exist before you start this - (yes fastconv does create the directory for you)
If it does not crash you will find all the files that were in the store in C:\RECOVERED with the correct names and paths, happy moving. If it did crash where did it crash? look in fastconv.log where it crashed or stopped. Did it crash in or just after TRANSDB.DAT? then goto and read the TRANSDB Section below
If it did crash on a regular .DAT file (like F:\USMT2.UNC\000010AE.DAT) exclude that file and rerun fastconv:
f:\fastconv /S:F:\USMT2.UNC /D:C:\RECOVERED /E:000010AE.DAT
does it still crash but this time on another .DAT file? (not TRANSDB.DAT)
exclude that file too. let´s say 00001EA1.DAT then rerun exluding that file too:
f:\fastconv /S:F:\USMT2.UNC /D:C:\RECOVERED /E:000010AE.DAT /E:00001EA1.DAT
keep doing this until fastconv finishes. you now should have all your files in C:\RECOVERED less the corrupted ones, happy moving. If it still crashes but this time in or after TRANSDB.DAT keep reading
Welcome to the Alamo. Make sure you have tried the Main Section solution first. While making the original USMT2.UNC store on the old system the index got corrupted somehow. Coming this far I am guessing that you no longer have access to the old data, otherwise slap yourself, go back and make a regular copy of the old data.
We now need to use fastconv to extract the store and keep the extracted files (=tmp) somewhere for you to manipulate.
Note: If you had corruptions too in your regular .DAT files you must take note of those and exclude them using /E:
First remove C:\RECOVERED completely (if it exists) and run: (as always assuming your external drive is F: and local is C:)
F:\fastconv /S:F:\USMT2.UNC /D:C:\RECOVERED /T:C:\RECOVERED\FILES /K
If you had previous regular corruption add /E:000010AE.DAT /E:0000... etc for the files that were corrupted.
This should run until it crashes in or just after TRANSDB.DAT
Close all windows
Close session (Start->Close session) and login again
Now go check C:\RECOVERED\FILES
You should have several directories there, one for every 2GB of store size and one for TRANS
In each but for the last of these numeric directories there are 4095 files which are named hexidecimally where the first is 001.DAT and last is FFF.DAT. Each file corresponds to an actual file (or registry entry) from the old system and the size of the files can give a clear hint of its contents. In TRANS there is a single file named DB.DAT - this holds the index as to how those *.DAT files were called and where they were on the old system
Is TRANS and/or DB.DAT missing? goto Missing TRANS Section else keep reading
Get BinTxt from http://www.mcafee.com/us/downloads/free-tools/bintext.aspx and open TRANS/DB.DAT with it.
Select advanced view and save the output to C:\RECOVERED\index.txt
Advanced reference: http://dow.ngra.de/2011/03/15/i-fought-the-f-a-s-t-and-i-won/
Now you at least have a reference to the original names of the files.
Example: Let´s say you desparately want your emails back for Outlook Express then just open C:\RECOVERED\index.txt in NOTEPAD
and search for Inbox.dbx. You should find something like this:
000001AED548 000001AED548 0 Inbox.dbx
000001AED7DE 000001AED7DE 0 000047FF.DAT
000001AED8D8 000001AED8D8 0 Inbox.dbx
000001AEDB22 000001AEDB22 0 Inbox.dbx
This means that your inbox is in the 00004 directory named 7FF.DAT
This way you can identify all dbx files and move them back to the correct location (google it if you do not know where that is)
Another example: email addresses - search for .wab files
000001B00F3E 000001B00F3E 0 00004850.DAT
000001B01038 000001B01038 0 Adres.WAB
The address book is under 00004 and is called 850.DAT
Keep reading to get a tool which automatically identifies what type the .DAT files are and renames them.
Get TrID File Identifier from here: http://mark0.net/soft-tridnet-e.html and use the commandline version to identify all files and rename them. This should get your essentials back like addresses, email, Office documents, images, etc etc. Remember that the directory structure is lost.
Happy moving and reorganising.
One final thing for reference:
problem: rmv2opq.exe cannot open my store
solution: you can only use rmv2opq.exe on stores that contain USMT2IMG.DAT files and only then you can use fastconv
If you MUST use FSTW use it from CD where you can to avoid version mismatches. ONLY use it for settings and manually copy the files. Else I would highly recommend Norton Ghost.
May you live in interesting times - Chinese proverb They sure are when you use FSTW.
Edited by Tsh00ter, 15 March 2012 - 01:22 PM.
Removed innuendo, moved from XP to Tips & Tricks..