Restore Files from a Windows XP .BKF file in Vista

1) create a folder somewhere, call it ntbackup just so you can keep track of
what you’ve done
2) from an existing XP installation, copy these 3 files into the new folder:
ntbackup.exe, vssapi.dll, ntmsapi.dll. Optionally, copy the files
ntbackup.chm and ntbackup.hlp. Do not overwrite any Vista files that have
the same names.
3) run ntbackup.exe. dismiss the error dialog concerning removable storage
if it appears.
4) catalog the backup file as you normally would (select the Restore tab,
then select Tools/Catalog) then select and restore your files. Remember to
restore them to an alternate location using the drop-down box in the
lower-left corner of ntbackup.

If you don’t have a running XP installation, then extract the listed files
from the XP installation CD. If you don’t know where these files are, you
can use search to find them; they will have the same filename except the last
character will be an underscore (e.g., ntbackup.exe will be ntbackup.ex_ on
the CD). i have not done an exhaustive search of every version of XP’s
installation CD to determine their locations.

Since you are (presumably) not running as an administrator under Vista as
you probably were under XP,
1) some extraneous errors may occur during the restore. check the results
of the restore to ensure that you got all the files you needed from the
backup, and apply the appropriate security settings to the restored files
manually if necessary
2) You might need to turn off the option to restore file security. (Hit the
“Advanced” button in the restore dialog).

ntbackup also appears to work for backing up files, but I wouldn’t trust it
to do so correctly without extensive testing.

Run a Program that Doesn’t Recognize Vista

Lots of apps check the operating system during installation to make sure the version of Windows is supported. This is designed to prevent the user from installing it in an old version of Windows that doesn’t have the necessary files or features. Sometimes, however, it’ll also block a new version of Windows–such as Windows Vista.

Fortunately, you can configure a program to run in compatibility mode, which causes Windows Vista to lie about the version of Windows. To trick a program (usually a Setup file) into thinking you’ve got Windows XP, follow these steps:

1. Right-click the program and then click Properties.

2. Click the Compatibility tab.

3. Select the Run this program in compatibility mode for check box. Then, select Windows XP (Service Pack 2) from the list.

4. Select the Run this program as an administrator check box (just to help further reduce compatibility problems).

4. Click OK.

Now, re-run the program. It should work this time.



compat-mode.png

Trace Application Activity with Process Monitor (ProcMon.exe)

Sometimes, an application gives you a generic error that a file or setting is missing or unavailable, but doesn’t give you enough information to identify exactly what it’s trying to open. With this free download from Microsoft, Process Monitor, you can monitor all activity on your computer, including the exact registry keys and files being accessed, and whether or not each access attempt was successful.

Process Monitor replaces FileMon and RegMon (tools made by the SysInternals guys, who are now part of Microsoft) by duplicating the functionality of each. To use it, follow these steps:

1. Download Process Monitor and extract the .ZIP file to a folder.

2. Double-click the ProcMon.exe file to run it. It doesn’t add a shortcut to the Start menu, but you can manually add one.

3. Run the application that’s having a problem, and duplicate the error.

4. Return to Process Monitor. Click the File menu, and then clear the Capture Events check box.

5. Browse the list of events. Right-click any entry with your process name, click Include, and then click Process Name. Now, you can easily see the events that your application created.

6. Look for events with a result other than SUCCESS. To hide the success events, right-click any successful event, click Exclude, and then click Result. Process Monitor shows just those events that had problems.

procmon2.png

7. Once you determine the registry key or file that can’t be accessed, replace it (you might copy it from another computer) or, if it’s a security problem, change the permissions so that your application can access it.

If you continue to have problems, you might have more than one unavailable resource. Just repeat these steps to solve the additional problems.