I’d like to have the dude on my USB stick to make simple checks on different networks if necessary.
The problem is, that there seem to be some informations spreaded on different places, there is a c:\dude.conf, there are some values in the registry etc.
When doing an install and uninstall it is possible to start the dude, but no server and web-server is running and the path for images, fonts, the certificates etc. are not setted correctly.
It would be fine to be able to set the path using a parameter in the command line or what about collecting all configuration parameters in one single ini file which is placed in the same directory like the dude.exe
I would also like to be able to download a portable version of The Dude.
I’m not entirely sure if it would be smart to use the current version for this or a slighty less equipped one.
We’ll see what the guys at Mikrotik think of it and maybe make here..
OK.. KisstheNet is something but I fear that that is not what the request is about..
Is it an option to create something like The Dude (great program btw) which is suitable for use from an USB-device.
Usually that means that the program doesn’t write anything into the registry of the laptop/desktop where this device is connected with, usually all settings are written in the folder on the portable device. Besides that most tools write data and/or configs in a folder on the portable device.
I think a version of The Dude which is able to do almost everything like the current version but then running from a portable device, without writing settings etc to the laptop/desktop but instead to a file/folder on the portable device could have a big advantage for networkengineers who want to quickly have a look at a different network.
Maybe it’s worth considering, sure would be nice to have such a tool on my portable devices.
@QpoX: Why do some hacks and make a lousy workaround (the result will be bigger and slower than necessary)? Done by the programmerss of the Dude it should be a smoother solution!
And - at least I believe - it shouldn’t be that complicate, the main issues are the (stupid ) config file at c:\ and the registry entries for retrieving the install path (otherwise the fonts, images etc. can’t be found)
So all these information should be moved to a local* ini file, that’s it
Michael
*) If there are no user restrictions to the actual directory, it could be necessary to allow adding a path for the config file as start parameter, like “Dude.exe /portable /configpath=%APPDATA%/Dude”
) config file at c:\ and the registry entries for retrieving the install path (otherwise the fonts, images etc. can’t be found)
