How do I clean up the registry

Hi,

When I run ndistest, 1c_faulthandling test modifies the registry to
simulate various error conditions (causing scenarios).
I am unable to load the driver because of some tweaking done by
1c_faulthandling after the test-run got over…

Question is: How do I restore the registry/fix this problem?

Regards,

If you know the set of registry entries that being affected. Then before
running any of those tests, you can back those up. Most likely it is only
few entries, and you go back the tree to get to a point where every affected
nodes of the registry is coverd ( for example HKLM might be one such), and
from regedit look at the menu to back up those entries. Search the net for
some help on Registry backup.

When backed up, have the file saved to a convienent place.

Next time when U bootup, double clicking on the file would restore ( it
would prompt you too :slight_smile:

And you would be back with clean slate of registry.

-pro

On 2/2/07, Praveen Kumar Amritaluru wrote:
>
> Hi,
>
> When I run ndistest, 1c_faulthandling test modifies the registry to
> simulate various error conditions (causing scenarios).
> I am unable to load the driver because of some tweaking done by
> 1c_faulthandling after the test-run got over…
>
> Question is: How do I restore the registry/fix this problem?
>
> Regards,
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

The approach that I use, and I imagine many others do as well, is not to
try to clean up the registry. Instead, perform tests that on a machine that
has been setup so you can completely re-image the test OS partition.

I use multi-partition machines where one partition is used for testing and
another is a “safe” partition. The safe partition (Drive D:, for example)
has a copy of Windows XP installed on it. The test partition (Drive C;, for
example, has a clean copy of Windows XP installed on it. After the clean
install of Windows XP is made I reboot to the safe partition and copy the
entire contents of the test partition to a file using a disk copy utility.

Now instead of trying to cleanup the registry after a failed test I can
simply boot to the safe partition and use the disk copy utility to re-image
the test partition. That way I know that the registry and everything else
has been restored to pristine state.

You can go further and have a “library” of saved test partitions. For
example, Windows XP, Windows XP with NDIS Tester installed, Windows Server
2003, Windows Vista, etc. Or, if you get interrupted while testing one
driver you can make a temporary copy or “snapshot” of the partition, reload
a clean OS and then go back to where you were by restoring the snapshot.

To answer your specific question: I don’t know what changes NDIS tester may
have made, so I’m certainly not smart enough to try to undo them.

You could see if the Windows Restore facility would help.

Good luck,

Thomas F. Divine

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:bounce-277292-
xxxxx@lists.osr.com] On Behalf Of Praveen Kumar Amritaluru
Sent: Friday, February 02, 2007 10:35 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] How do I clean up the registry

Hi,

When I run ndistest, 1c_faulthandling test modifies the registry to
simulate various error conditions (causing scenarios).
I am unable to load the driver because of some tweaking done by
1c_faulthandling after the test-run got over…

Question is: How do I restore the registry/fix this problem?

Regards,


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

Hi,

I still have this option open to reimage…

But I was trying to figure out whether there is any such option that will
let me recover.
I just figured out test has done something to fail my interrupt
registration and that fails
loading my driver…

Regards,

“Thomas F. Divine” wrote in message news:xxxxx@ntdev…
> The approach that I use, and I imagine many others do as well, is not to
> try to clean up the registry. Instead, perform tests that on a machine
> that
> has been setup so you can completely re-image the test OS partition.
>
> I use multi-partition machines where one partition is used for testing and
> another is a “safe” partition. The safe partition (Drive D:, for example)
> has a copy of Windows XP installed on it. The test partition (Drive C;,
> for
> example, has a clean copy of Windows XP installed on it. After the clean
> install of Windows XP is made I reboot to the safe partition and copy the
> entire contents of the test partition to a file using a disk copy utility.
>
> Now instead of trying to cleanup the registry after a failed test I can
> simply boot to the safe partition and use the disk copy utility to
> re-image
> the test partition. That way I know that the registry and everything else
> has been restored to pristine state.
>
> You can go further and have a “library” of saved test partitions. For
> example, Windows XP, Windows XP with NDIS Tester installed, Windows Server
> 2003, Windows Vista, etc. Or, if you get interrupted while testing one
> driver you can make a temporary copy or “snapshot” of the partition,
> reload
> a clean OS and then go back to where you were by restoring the snapshot.
>
> To answer your specific question: I don’t know what changes NDIS tester
> may
> have made, so I’m certainly not smart enough to try to undo them.
>
> You could see if the Windows Restore facility would help.
>
> Good luck,
>
> Thomas F. Divine
>
>> -----Original Message-----
>> From: xxxxx@lists.osr.com [mailto:bounce-277292-
>> xxxxx@lists.osr.com] On Behalf Of Praveen Kumar Amritaluru
>> Sent: Friday, February 02, 2007 10:35 PM
>> To: Windows System Software Devs Interest List
>> Subject: [ntdev] How do I clean up the registry
>>
>> Hi,
>>
>> When I run ndistest, 1c_faulthandling test modifies the registry to
>> simulate various error conditions (causing scenarios).
>> I am unable to load the driver because of some tweaking done by
>> 1c_faulthandling after the test-run got over…
>>
>> Question is: How do I restore the registry/fix this problem?
>>
>> Regards,
>>
>>
>>
>> —
>> Questions? First check the Kernel Driver FAQ at
>> http://www.osronline.com/article.cfm?id=256
>>
>> To unsubscribe, visit the List Server section of OSR Online at
>> http://www.osronline.com/page.cfm?name=ListServer
>
>

OK. Uninstalling/reinstlling the driver fixed the problem.

Moreover the registry key and the value of registry key that does this trick
was found.

“Praveen Kumar Amritaluru” wrote in message
news:xxxxx@ntdev…
> Hi,
>
> I still have this option open to reimage…
>
> But I was trying to figure out whether there is any such option that will
> let me recover.
> I just figured out test has done something to fail my interrupt
> registration and that fails
> loading my driver…
>
> Regards,
>
>
>
> “Thomas F. Divine” wrote in message
> news:xxxxx@ntdev…
>> The approach that I use, and I imagine many others do as well, is not
>> to
>> try to clean up the registry. Instead, perform tests that on a machine
>> that
>> has been setup so you can completely re-image the test OS partition.
>>
>> I use multi-partition machines where one partition is used for testing
>> and
>> another is a “safe” partition. The safe partition (Drive D:, for example)
>> has a copy of Windows XP installed on it. The test partition (Drive C;,
>> for
>> example, has a clean copy of Windows XP installed on it. After the clean
>> install of Windows XP is made I reboot to the safe partition and copy the
>> entire contents of the test partition to a file using a disk copy
>> utility.
>>
>> Now instead of trying to cleanup the registry after a failed test I can
>> simply boot to the safe partition and use the disk copy utility to
>> re-image
>> the test partition. That way I know that the registry and everything else
>> has been restored to pristine state.
>>
>> You can go further and have a “library” of saved test partitions. For
>> example, Windows XP, Windows XP with NDIS Tester installed, Windows
>> Server
>> 2003, Windows Vista, etc. Or, if you get interrupted while testing one
>> driver you can make a temporary copy or “snapshot” of the partition,
>> reload
>> a clean OS and then go back to where you were by restoring the snapshot.
>>
>> To answer your specific question: I don’t know what changes NDIS tester
>> may
>> have made, so I’m certainly not smart enough to try to undo them.
>>
>> You could see if the Windows Restore facility would help.
>>
>> Good luck,
>>
>> Thomas F. Divine
>>
>>> -----Original Message-----
>>> From: xxxxx@lists.osr.com [mailto:bounce-277292-
>>> xxxxx@lists.osr.com] On Behalf Of Praveen Kumar Amritaluru
>>> Sent: Friday, February 02, 2007 10:35 PM
>>> To: Windows System Software Devs Interest List
>>> Subject: [ntdev] How do I clean up the registry
>>>
>>> Hi,
>>>
>>> When I run ndistest, 1c_faulthandling test modifies the registry to
>>> simulate various error conditions (causing scenarios).
>>> I am unable to load the driver because of some tweaking done by
>>> 1c_faulthandling after the test-run got over…
>>>
>>> Question is: How do I restore the registry/fix this problem?
>>>
>>> Regards,
>>>
>>>
>>>
>>> —
>>> Questions? First check the Kernel Driver FAQ at
>>> http://www.osronline.com/article.cfm?id=256
>>>
>>> To unsubscribe, visit the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>>
>>
>
>
>