Page 1 of 1

Update to build 1.0.67 problem

Posted: Tue Mar 15, 2011 5:20 am
by Spurred On
I had MailWasher Pro 2011 build 1.0.xx (the second to most recent update) installed and working wonderfully. Today I downloaded and tried to install the update to build 1.0.67. The first problem was that the installation required Microsoft.NET version 4.0. My .NET version was older, so I downloaded and installed .NET 4.0. Then the installation of MailWasher was able to proceed. Using the Custom Install, I decided to move where all of my MailWasher user data was installed to a new location on another drive. First, I copied over all of the existing data from the default location C:\Documents and Settings\[User]\Application Data\Firetrust\MailWasher to the new location so that the existing data would be available to the update.

After the update installation, MailWasher opened with none of my settings, none of my preferences, none of my filters, none of my e-mail accounts. I found that the installation had created a new subfolder, User1, and made that my new user data folder. I renamed the User1 folder to UserX, created an new empty User1 folder, and copied all of my original user files into that folder. MailWasher then opened normally with all of my settings, preferences, and accounts loaded.

Why is the installation process creating this new User1 subfolder? Is there a way to keep it from doing so? Is it because the data is no longer under the Windows user account C:\Documents and Settings\[User] folder? Can I change the name of the folder from User1 to something else (a Registry key value edit)?

Thanks for your help — Tony

Re: Update to build 1.0.67 problem

Posted: Tue Mar 15, 2011 5:32 am
by rusticdog
The User1 is tacked on to the end should another user account want to use MailWasher, so that way individual users can still have their own 'user profile' data.

There's no way to stop the subfolder from being created, though technically it is possible to alter the name of the folder, so instead of 'User1' it could be 'data', however I'm not sure of the point in doing that.

Re: Update to build 1.0.67 problem

Posted: Tue Mar 15, 2011 5:43 am
by rusticdog
I should have added....to do this, go into your old data folder location and look for a file called redirect.dat. With MailWasher closed open this and rename the folder name to whatever you want, you probably want to create and copy the data across to the new folder also....or just start MW and it will recreate this folder as a new user, then you could copy the info across.

Re: Update to build 1.0.67 problem

Posted: Tue Mar 15, 2011 8:44 am
by Spurred On
Thanks for your reply rusticdog. The folder name change was very simple to do and MailWasher opened normally after the change.

Back in the original (default) folder C:\Documents and Settings\[User]\Application Data\Firetrust\MailWasher, are there any other files I need to keep in that folder besides redirect.dat? It'd be nice to be able to delete all of those files and subfolders now that they've all been copied over to the new folder. Also, can I safely delete the redirect.dat file from the newly named folder in the new location?
. . . it is possible to alter the name of the folder, so instead of 'User1' it could be 'data', however I'm not sure of the point in doing that.
If there were more than one MailWasher user account, it would be easier to find the data files for a particular use if the data folders were named after that user's account (eg rusticdog or Spurred On) as opposed to an arbitrary number and having to figure out which number goes with which user. With only one user, it wouldn't matter.

Tony

Re: Update to build 1.0.67 problem

Posted: Tue Mar 15, 2011 2:50 pm
by rusticdog
Unfortunately for us, we've been struggling with an issue where MailWasher cannot function with its SQLite database if certain characters are in the data path. We got it working fine with some characters you see in French/German/Spanish etc...however it never wanted to play nice with Cyrillic and some others. These same characters are often found in peoples username which is why we've used the method above to not carry across the actual username.

Re: Update to build 1.0.67 problem

Posted: Wed Mar 16, 2011 3:54 am
by Spurred On
Thanks rusticdog.
MailWasher cannot function with its SQLite database if certain characters are in the data path
Never thought of that. We don't realize how deeply ingrained the Latin alphabet is into program languages.

Are there any files or folders in the default C:\Documents and Settings\[User]\Application Data\Firetrust\MailWasher other than redirect.dat that I need to keep there, or can I safely delete everything else?

Tony

Re: Update to build 1.0.67 problem

Posted: Wed Mar 16, 2011 9:39 am
by rusticdog
Sorry forgot to answer that didn't I. Yes, it should be perfectly fine to delete those files except the redirect.dat, I just tried and it's worked all OK on my Virtual Machine setup doing this.

Re: Update to build 1.0.67 problem

Posted: Thu Mar 17, 2011 2:48 am
by Spurred On
Thanks rusticdog. As a safeguard, I renamed the MailWasher folder to MailWasherX, created a new MailWasher folder, and put only redirect.dat into it. MailWasher opened and worked normally. I then deleted the MailWasherX folder and all of its contents with a satisfied smile.

I appreciate all of your help.

Tony

Re: Update to build 1.0.67 problem

Posted: Thu Mar 17, 2011 1:58 pm
by rusticdog
No problems :)