Jump to content
CCleaner Community Forums

WinappDebug - A tool to find error in your winapp2.ini file


Recommended Posts

Thanks to help from Robbie Ward (User: winapp2.ini); I've made this very simple console app to detect common errors with your winapp2.ini file.

How do I use it?
Simply place 'winapp2.ini' in the same folder as 'WinappDebug.exe' and run the tool. It will output a list of errors that it detects.

What kind of errors does it detect?
- Starting and trailing whitespace
- LangSecRef, FileKey & RegKey spelling errors
- Spaces in environmental variables
- Missing numbers next to FileKey and Regkey entries
- Missing backslashes next to environmental variables
- Incorrect usage of the 'Detect' & 'DetectFile' commands.

WinappDebug.png

It's not working! HELP!!!
WinappDebug requires the Microsoft .NET Framework to be installed on your computer. Make sure winapp2.ini can be accessed by the tool by closing any programs you are using to edit it.

Download (version 0.3)
http://content.thewebatom.net/files/WinappDebug.exe

 

MetaScan results show 1/40 security products incorrectly detect WinappDebug as malware. If you have any concerns, you're welcome to compile it from the source code below ;)

Source Code
Written in VB.NET. Available from PasteBin.

Please feel free to leave comments and suggestions.

Link to post
Share on other sites
  • 2 years later...

Updated to 0.3

 

- Number of detected issues reported correctly.

- Better support for the new permitted wildcards

- Fixed a compiler warning.

Link to post
Share on other sites

Yeah, I used an updated version of the Visual Studio compiler. It's interesting to note that the output was 40% bigger, even before I made changes to the code.

Link to post
Share on other sites
  • 4 weeks later...

@ TheWebAtom: I know the coding language will have a look and see if I can help you out.

 

This thing can grow to become really big and helpful.

Link to post
Share on other sites
  • 3 months later...

It would be grat to add a check routine for that :

 

 


_________________________________________________________________

 

working of Excludekey: I think these Excludekey should not work, because you use | instead of \, cause Excludekeys work like this.

 

 

also true !!!!

 

but second bug:

ExcludeKey1=FILE|C:\Users\Admin\Desktop\Musik\1.txt;2.txt

 

; dont work, serperate each file ......

___________________________________________________________________

 

from winapp2.ini

[Diablo III Logs*]
Section=Games
Detect=HKCU\Software\Blizzard Entertainment\D3
Default=False
FileKey1=%CommonAppData%\Battle.net\Setup\diablo3_engb\Log
FileKey2=%ProgramFiles%\Diablo III\Logs
FileKey3=%ProgramFiles%\Diablo III Beta\Logs|*.*
FileKey4=%LocalAppData%\VirtualStore\Program Files*\Diablo III\Logs
FileKey5=%LocalAppData%\VirtualStore\Program Files*\Diablo III Beta\Logs|*.*
FileKey6=%LocalAppData%\VirtualStore\ProgramData\Battle.net\Setup\diablo3_engb\Log

File key 1 ,2 ,6 not cleaning definition! could it work ? like *.log e.g.

 

______________________________________________________________________

 

 

 

also nice double use of ||  \\   ;;   |\   \| **

 

 

 

also:

 

 

 

Oh shoot, realtek (logs) does a recursive scan from %SystemDrive%, that's just horrid.

 

Thats not just clean,

Its squeaky clean :)

 

 

and doble rules detection....

Link to post
Share on other sites
  • 5 months later...
  • 3 years later...
  • Moderators

Old thread is old.  Unpinned by request, any information about this debugger ask at the winapp2 thread.

 

Thanks

Link to post
Share on other sites
  • Nergal unpinned this topic

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...