I've tested this on two different computers running Windows XP, and a fresh install of Mushclient (where no previous version existed before) does not create a shortcut to Mushclient in the \Start Menu\Programs\MUSHclient directory. It is easy enough to do manually, but thought it should be brought up.
Fresh install of version 4.43
Posted by ErockMahan on Sat 17 Jul 2010 02:46 PM — 9 posts, 36,040 views.
Hopefully fixed in version 4.54
I noticed a bit ago that if I chose not to install the default plugins, no plugins/ or state/ folder was created. I think these should probably be created even if the default plugins aren't added, because it makes it easier to add third-party plugins later.
Why do I have mushclient_prefs.sqlite in my MUSHclient Start Menu directory, anyhow?
Please see the forum thread: http://gammon.com.au/forum/?id=9260.
Hmm. It seems to have only affected the computer that's had it for longer, because my new laptop doesn't have it there.
Oh, and FYI I was talking about a Start Menu shortcut to the sqlite database, which is très bizzare. Anyways, looks like that was something specific to my computer and not a real bug.
Oh, and FYI I was talking about a Start Menu shortcut to the sqlite database, which is très bizzare. Anyways, looks like that was something specific to my computer and not a real bug.
I think that what is happening is that according to the logic in thread 9260, if it happens to create a prefs database in the same directory as the shortcut (that is, the directory the program started in), then if that happened to be the Start Menu, well so be it. Strange, I know.
Actually now I see mushclient.ini in my Start Menu folder. Ah well, someone who is an expert in installers can perhaps fix all that.
You should create those files in %appdata%\MUSHclient, and not in the current directory. It's where application prefs are supposed to go.
And yeah, I know MUSHclient likes to be portable on USB sticks, but I have in the past always solved such issues by looking for a "mushclient.portable" file in the same directory as my executable, in which case it would use the current directory, or in one occasion, a directory specified in said file as its portable version of %appdata%\MUSHclient. (Of course my apps and thus the files had slightly different names, but yeah...)
The Starting Directory should only serve ONE purpose EVER, and that is to define a starting point for the users file-management tasks, be it to open or to save files.
And yeah, I know MUSHclient likes to be portable on USB sticks, but I have in the past always solved such issues by looking for a "mushclient.portable" file in the same directory as my executable, in which case it would use the current directory, or in one occasion, a directory specified in said file as its portable version of %appdata%\MUSHclient. (Of course my apps and thus the files had slightly different names, but yeah...)
The Starting Directory should only serve ONE purpose EVER, and that is to define a starting point for the users file-management tasks, be it to open or to save files.