In version 1.0-beta1, I notice that the "Test settings" buttons are gone.

At first I thought "Oh no, this makes configuration in a training environment much more difficult for the sys admin, who, in order to trigger firewall prompts, now has to actually BUILD a topology on each computer, and not just install & run GNS3", but come to think of it a little more, their absence is an opportunity for a new approach for testing settings to be implemented.

Ideally, I'd hope to see a new menu item (let's say "Tools > Test settings") or something, that would try to first run all the different executable files used by GNS3 (dynamips, VPCS, vboxwrapper, etc.) individually, with their settings, as defined in the preferences, and then also try to run them all together, as a way of detecting conflicts between the individual modules (e.g. if a port happens to be within the range of both dynamips and VPCS). It should also try to create the project, images and temp folders, if they're not created, as a way of detecting basic permission issues. It should go without saying that the results of all of those stages should be written out on screen somehow.

Even better - during installation, there should also be a checkbox for testing the settings on first run, checked on by default, easing installation further.

Hi,

I was thinking doing something similar of what you have proposed :)

Thanks for the suggestions, I am sure they will be useful.

Cheers,

_________________
Jeremy, GNS3 Programmer & Benevolent Dictator for Life.