I'm not completely sure what caused the problem but today TaskUnifier stoped starting up after it had already been run and closed once before. It seems to be quiting on the "Check Single Instance" portion of the loading screen. I checked windows task manager to make sure TaskUnifier wasn't still running in the background and I didn't find anything that looked like a match. Logging off and back on to my Windows user profile appears to clear up the problem preventing TaskUnifier from completely loading. I can't be sure it's related but this appears to have started after I setup the google publication plugin. Just in case it's relevant I'm running Windows 7 x64 and v4.0.4 of TaskUnifier with v7 update:45 of Java 32bit.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If this would happen to other users, the problem seemed to be linked with the fact that the data folder of TaskUnifier was set on a Google drive folder.
TaskUnifier creates a temp file in order to check if he is already started.
Using the Google drive messed up this temp file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Forum"
I'm not completely sure what caused the problem but today TaskUnifier stoped starting up after it had already been run and closed once before. It seems to be quiting on the "Check Single Instance" portion of the loading screen. I checked windows task manager to make sure TaskUnifier wasn't still running in the background and I didn't find anything that looked like a match. Logging off and back on to my Windows user profile appears to clear up the problem preventing TaskUnifier from completely loading. I can't be sure it's related but this appears to have started after I setup the google publication plugin. Just in case it's relevant I'm running Windows 7 x64 and v4.0.4 of TaskUnifier with v7 update:45 of Java 32bit.
If this would happen to other users, the problem seemed to be linked with the fact that the data folder of TaskUnifier was set on a Google drive folder.
TaskUnifier creates a temp file in order to check if he is already started.
Using the Google drive messed up this temp file.