I have spent the greater part of the last 2 weeks attempting to file share with a Vista laptop via my wireless network. I'm using an XP PC as the host or server. Without going into a long diatribe of the issue it boils down to what I've read in many posts on other websites. Microsoft could help with the issue, but won't. I came across a program called "MigRecover, but even they don't guarantee success. I painstakingly took my time and, with many stops and starts, finally got some results. But I can't say I'm happy with them. I will paste the results here and if anyone has any knowledge of these things and could give some much needed advice I would greatly appreciate it.
Here are the results copied from notepad:
************************************************** ***************
C:\Documents and Settings\Sharing>Register DLL on PC
'Register' is not recognized as an internal or external command,
operable program or batch file.

C:\Documents and Settings\Sharing>RegSvr32 C:\Windows\Sytem32\wdscore.DLL

C:\Documents and Settings\Sharing>MD C:\MIGRECOVER\RECOVER
A subdirectory or file C:\MIGRECOVER\RECOVER already exists.

C:\Documents and Settings\Sharing>CD C:\MIGRECOVER

C:\Migrecover>
C:\Migrecover>MIGRECOVER.EXE C:\SaveData.MIGC:\MIGRECOVER\RECOVER

A utility to recover files from a Windows Easy Transfer or USMT archives.

Syntax:

MigRecover.exe [/i:<include pattern>] [/e:<exclude pattern>] [/v] <source MIG
file> <destination path> [password]

Where:

/i:<include pattern>
- pattern for files to be extracted. Multiple include patterns are
allowed. They can be combined with exclude patterns, whenever a
conflict is detected the last specified pattern wins.

/e:<exclude pattern>
- pattern for files not to be extracted. Multiple exclude patterns are
allowed. They can be combined with include patterns, whenever a
conflict is detected the last specified pattern wins.

/v
- verify the store, don't extract anything. A list of all the files
in the store together with their status will be generated in a file
called STATUS.TXT in the root of the destination path.
This will have a line for each file, followed by a TAB and either
"corrupt" or "OK" depending on the status of the file.
The last entry will have the name "STRUCTURE" and will be set to
"OK" if all the headers in the store file are intact.

<source MIG file>
- the full path to the MIG file you need to recover files from.

<destination path>
- the path where the tool should unpack the recovered files.

[password]
- the password used to encrypt the store (if any).

Return codes:
0 - the tool completed successfully, the store is not corrupt (if /i /e
were used there might still be corruption in unprocessed files)
1 - internal error
2 - invalid usage, see this help screen
3 - invalid destination directory
4,5 - error opening the store
6 - cannot create STATUS.TXT file
1392 (ERROR_FILE_CORRUPT)
- the tool completed successfully, but some of the data in the store
is corrupt

C:\Migrecover>
************************************************** **************
I don't know the file paths and still can't open the original MIG file. Of course.
If you have any questions or answers to what I can do next please email me
Thanks in advance.....Lance