recursively search the registry and delete text
-
I need some help. I need source code that will recursively search the registry and delete text found. It would need to work on 95/98/NT/XP/2000. I'm looking to return a list (perhaps in a list box) of all keys (ALL TEXT) that were found. If that Text appears anywhere in registry I want it added to my list. Then I can select/deselect what I wish and then delete the selected items. Allow someone to highlight and delete specific ones. Any ideas? Any help is appreciated. Cheers, Derek
-
I need some help. I need source code that will recursively search the registry and delete text found. It would need to work on 95/98/NT/XP/2000. I'm looking to return a list (perhaps in a list box) of all keys (ALL TEXT) that were found. If that Text appears anywhere in registry I want it added to my list. Then I can select/deselect what I wish and then delete the selected items. Allow someone to highlight and delete specific ones. Any ideas? Any help is appreciated. Cheers, Derek
I have been writing registry editors, searchers, and replacers for some time, so perhaps I could help. However, the core guts of almost all my code is in C or C++. I have tinkered with other languages, but none I have tried have efficient enough string handling to prevent the user from falling asleep. One catch is the Win95 requirement, which eliminates the .Net languages. Thus, your options are to use strictly C/C++ to target Win95, or exclude Win95 and use .Net (and optionally a managed wrapper around some C++ to get decent performance). If you can tell me how you wish to proceed, I can explain further. Cheers
-
I have been writing registry editors, searchers, and replacers for some time, so perhaps I could help. However, the core guts of almost all my code is in C or C++. I have tinkered with other languages, but none I have tried have efficient enough string handling to prevent the user from falling asleep. One catch is the Win95 requirement, which eliminates the .Net languages. Thus, your options are to use strictly C/C++ to target Win95, or exclude Win95 and use .Net (and optionally a managed wrapper around some C++ to get decent performance). If you can tell me how you wish to proceed, I can explain further. Cheers
Yes, I would like some help. I emailed you earlier. Any help you could provide would be great. My primary language is C++. I'd like to have it list the locations and values of where it found the text that I am searching for, and allow me to choose to delete or not delete a certain entry. Derek
-
Yes, I would like some help. I emailed you earlier. Any help you could provide would be great. My primary language is C++. I'd like to have it list the locations and values of where it found the text that I am searching for, and allow me to choose to delete or not delete a certain entry. Derek
Sorry for the late reply; I've been rather busy (as if I have lots of spare time :) I've looked through my search functions, and can only find the more recent ones, which is fine, but they are very complicated (custom dynamic buffers and arrays, handle a zillion options, search binaries in various formats, some assembler, stored info to avoid recursion overhead, etc.). I am in the process of distilling one down to something digestable and more useful for your purposes. Will post (or email if too large) later today. Just wish I could find some of my regular stuff... Cheers
-
Yes, I would like some help. I emailed you earlier. Any help you could provide would be great. My primary language is C++. I'd like to have it list the locations and values of where it found the text that I am searching for, and allow me to choose to delete or not delete a certain entry. Derek
Hello Derek, I email you the rough code via CP's email system, which complained about the long text, so I hope it made it to you. If not, or it gets mangled, you can email me with an address I can send it to you as an attachment. I reduced it all down to just a few hundred lines, so it should be pretty manageable. It's strictly search and callback with keypath, entry name, data, data length, data type, and where the string was found. That should be enough to load up a listbox or listview with. RegDeleteValue is easy to call after that. Let me know if you have any questions. Cheers