The Best Way to compare Old & New Registry?

[CWKJ]

Suggestions welcome!

Have you ever wonder, especially after you installed a new software, what are the registry that are modified?
1. Before install, study CAB file?
2. After install, check manually?
3. Have both Old and New Registry copied and use PC's FC.EXE?
4. Use text editor to open both Old & New Registry files in PC at window maximise mode, use ALT TAB and capture the difference with the Best Camera (your eyes) and Best Image processor (your brain)?

Here is my stupid way of doing it.
5. Have both Old and New Registry copied and use PC's M$ Winword, Document Compare feature.

Last Days of 2006
Happy 2007
Cheers

 

[vijay555]

ssnap.

V

 

[CWKJ]

Hey, Thanks.

Learn a new thing again today.

 

[Menneisyys]

I also recommend, as far as desktop-based tools are concerned, windiff.

I've even written a tutorial on using it: http://forum.brighthand.com/showthread.php?t=215073

 

[ivorh]

Perl

This perl script will diff two textual registry files and show the differences.
(hmm no .pl allowed, rename from .txt)

 

[cellneuron]

Can't we just open the cab and see what it will add to the registry?

 

[vijay555]

Lol, despite responding to this thread I've never read it

Yes, 100% agree with cellneuron. Decompile the cab, or ideally use WinCE Cab Manager to see what registry changes it will make.

V

 

[ivorh]

hehe. What? Haven't you got time to read all of the threads each day?
anyway, yup, can't argue with that technique either. it never hurts to have too many tools at your disposal though.
Personally, I just found that reading the cab file registry entry format wasn't as clear as simply extracting the keys in .reg format. but that's just my preference.

 

[markvan]

The problem I've found with just looking in the cab is that sometime the exe files make registry and file changes too. So my vote goes with ssnap and idiff.

 

[pof]

In the past I used regdiff and registry workshop.

 

[CWKJ]

In the past I used regdiff and registry workshop.

In the past, what about now?

 

[TT_boy]

Lol, despite responding to this thread I've never read it

Yes, 100% agree with cellneuron. Decompile the cab, or ideally use WinCE Cab Manager to see what registry changes it will make.

V

Honestly, I also prefer t use WinCE Cab Manager to see the changes

 

[vijay555]

Yeah, I'm a bit soft in the brain so prefer WinCE to cabtools,

but as the geeks point out, if I was making an installer I would probably hard code some of the registry entries, so won't be reflected in Cab manager etc. So use a standard registry dump and windiff them, or use ssnap.

V

 

[200mpx]

http://s-k-tools.com/index.html?sktracker/m_feat.html

SKTracker this is program allowing You to trace changes on Your PocketPC.


As example, having done two records of the condition of the system,
before and after the installation of some software,
You will be able to learn about changes fom system.
You will be also able to use information for full removing software from system.

SKTracker features:

writing the current condition of the file system
writing the current condition of the registry
writing the current condition of the databases
comparison and suitable viewing result
start of Your file manager and registry editor from viewing window
a removing new or changed files and registry keys
keeping to information in compressed type
export information to text file
pre-defined rules
2 special rules for control of places of probable harmful programs intrusion (just in case)
shortcut wizard
support several languages of the interface
QVGA/VGA support
PPC2002/WM2003/WM2003(SE)/WM2005 compatible

 

[accepted]

SK Tracker

With SK Tracker you can Compare Files,Registry Keys
thanks 200mpx