Hi to all of you,
to answer the last posts:
Games package
I haven't thought much about the games package jet. Yes, shareware game are a very good idea, too. With "freeware games" a meant "games I can distribute legaly". I will take a look at the 3D Realms website the next days.
Autosetup database
I'm not thinking of a single big database file. And also I don't want to bring only the mentioned settings. We already have a profile format, why not just using this ? At the moment I am thinking of just a third subfolder (besides "Confs" and "Templates") to store the autosetup templates as simple prof files. Making a autosetup template from an existing profile would mean copying the prof file to the new folder (and of course removing links to data folders etc.). The profile wizard could search in the new folder for matching autosetup profiles and simply make a real profile from one of this templates (like it can do from the "Template" templates at the moment). Only the game and setup exe paths would need to be changed.
Up to last week my best idea to find the correct autosetup profile for a game was to define some more characteristical files for the game while making the template. But the idea to use checksums from the Frond ends wish list thread sounds much better.
And yes, I am also thinking of things like an online database. But this is still very far away. The only thing I will have to attend for this at the moment is making the autosetup system secure. If there are one day perhaps not checked autosetup templates on the internet, one could also make a template which mounts "C:\" as drive D and than in the autoexec does some "del *.*". So the wizard should warn the user if he want's to use a template with 1.) mounting something outside the VirtualHD tree, 2.) have an autoexec section or 3.) have an custom settings section (because custom settings can be "[autoexec] del *.*", too).
Bugfix release yes or no
I do not like feature rich but buggy programs, too. But at the moment I don't know if this three bugs really make a 0.3.2 release necessary. If D-Fend Reloaded was a bigger project with more people involved, on could make beta and stable versions or one stable tree and one playground tree.
The three bugs are already fixed in my source code. So the main problem is not that I don't like fixing bugs. The release process is much more unpleasant: Building the 5 different installation packages, checking all version numbers are right, uploading them to SourceForge at <50KB/s (don't know why their ftp server is that slow, my connection is much faster anyway), making a new release there, sorting the files in the right locations, writing announcements here and at sourceforge, updating the download links, updating the homepage...
But I am still thinking of a 0.3.2 release. Perhaps, if someone finds some more bugs, I will make a bugfix release.
St.Count+1
Hi skatz, wow, someone looked at the source code, very nice. You are right, there should be a "+1".
By the way I have just created a list of known bugs website. I think it is better to show the user "Yes, there are bugs, but I know them all and they will be fixed soon" than to deny the existence of the bugs and then the user finds some and thinks there are unlimited many bugs and no one will ever find and fix them.