As the name suggests Object-Oriented programming means you should be thinking about objects. I've taken a quick peek at your code, and I don't see anything crying out to be an object. That's the test I always make. Is there an obvious object? In your code, I don't see it, but then you know your code better than I do.
If you had it more generic, say a function ( or set of functions ) to read and write to .ini files then you could have any IniFile object, read them, write them, add entries, remove entries. That's your object. Indeed entries could be objects too. In your code, you look to be hard coding for a specific purpose and as such, I don't see much reusable code that I would call related to an object.
Just my 2c.
If you had it more generic, say a function ( or set of functions ) to read and write to .ini files then you could have any IniFile object, read them, write them, add entries, remove entries. That's your object. Indeed entries could be objects too. In your code, you look to be hard coding for a specific purpose and as such, I don't see much reusable code that I would call related to an object.
Just my 2c.