Quote:

---

Trick for newbabies:
Regshot can monitor "most" of the windows registry changes,Why is "most" ,not "all" ??
Yep,regshot can monitor almost "all" user application's changes done to the registry, but in Windows NT(2000,XP,2003) platform, user apps do not have enough privileges to "see" what System OS have done,
for example: If you are using XP,and change the xDSL Dialup password in the "network connections", and you have monitor the action with regshot, but after compare the 2 shots, you would find nothing happend ( , does windows save it else where ??
The answer is no, Windows does save the password (encrypted) in the Registry, but user just can not see it.
The solution is we should run regshot in a higher privileged level,here is how:
1.Open your services control panel,Make sure that your "Task scheduler" service is running and is using the "Local system" account.
2.Schedule a task with "at" command in a cmd shell:
at 18:22 /interactive "d:\tools\regshot.exe"
The time "18:22" is the current clock time(eg:18:20) plus 1 or 2 minutes , so you can wait task scheduler to run your regshot at 18:22
3. Wait 1 or 2 minutes,after the regshot runs, do the normal job .Remember, it is running with the "local system" privileges and can "see" the changes made by the system os. Guess where windows store the xDSL dialup password )

For more info , try search help in microsoft for "windows privileges","task schedule","regedt32", There may be more tricks...... There are even utils help you to run apps under special account....

---

$=wshShortCut("DUN Test","%windir%\system32\RasPhone.exe","-d DUN Test")