Bizzaro situation on my computer

A little background... I have been using FS for about 2 years and am
extremely happy. On a single machine at home, I have had problems w/ FS
however. Notably I couldn't get the old FS client to synch when Windows
Firewall was on (even though it was listed as an exception). The FS client
would sit trying to log on and use 100% CPU resources. Disabling the
Firewall allowed me to use it w/o problems... since I have a router that acts
as a firewall.. no problems.

Recently, I noticed that my FS icon was greyed out. I checked the FS
website and saw that there was a new client and downloaded and installed. It
seemed to connect but again was trying to log on for a while. This was only
a temporary situtation. After restart, it connected and was active (i.e.
files synching) but then the FS client just crashed.

OK, the bizzaro part. Recently, I set my wife up w/ FS. She loves it. She
uses it on the same machine, under a separate user account. Her FS seems to
work fine. Even with the upgrade, it seems to work beautfully. It also
seems that the FS client is installed separately for separate users...unlike
the previous FS client.

Anyway, I contact FS support. They told me to unistall it and delete the
folder contating the registry key uder HKEY_CURRENT_USER, which I did. Still
no luck. There are many other FS entries in the registry but I am leary of
just deleting them all.

Also, it still does not answer the question of why it works fine for my wife
and not for me... and why does it seem to work only for a minute before
crashing? It seems to me that it should either work or it shouldn't... not
stop in the middle of synching (and it doesn't seem that it trips on a
particular file ... the next time I start it, it picks up where it left off
and continues happily for another minute before crashing). I've even gone to
removing any unecessary startup items (spybot, desktopsearch, etc) to make
sure that none of those were interfering... no luck. Anyway... bizzare.
Hoping that the brain power of the user community may be able to offer a
solution.

p.s. I have a P4, 3GHz, 1GB RAM, WinXP SP2... if it makes any difference.
Als, just saw another post "New Foldershare Beta Crashes on startup"...
apparently there is a bug of some sort, but again, why does it not affect my
wife's instance of FS on the SAME computer?

Are you using the new client (that we posted this week) or the old client?

thx
-Mohammed

"vts" <vts@xxxxxx> wrote in message
news:C30009A7-2EEF-427A-B991-AFA4B038C55A@xxxxxx

The new client...

Mohammed, does the client get installed separately for each user? I am
guessing there may be something under my user profile that causes the FS
client to crash... not sure what this could be. I have tried to eliminate
all the non-essentail startup programs using the MSCONFIG-> Startup. The
only item that i didn't stop are video/audio drivers and Symantec antivirus
(corporate ed). Still no luck.

I had submitted this to the FS support and it has been kicked up to the
Level 2 supervisors... but I think that you will be able to address this
problem better? If you want I can e-mail you the log file.

Did you sign up for Foldershare BEFORE Microsoft acquired the company?

If yes, did your wife sign up AFTER Microsoft acquired the company?

If yes to both, this supports the theory that something in old accounts,
created before MS acquired the company are incompatible with the new system.
That is, same software for you and your wife, same computer systems, etc.
But, different account types: yours created with ByteTaxi, hers with MS.


"vts" wrote:

No... we both signed up afterwards. I had signed up in late 2006 and my wife
early 2008.

I gotta believe that there is some type of bad interaction in my user
profile and FS on this pc (I have it working fine on 4 other pc's). Also, as
I said this PC had the wierd firewall probelm with the older client. My
personal believe is that there may be something flawed with one of the old
uninstalls and that this is causing some sort of conflict.

My thought as a work around is to create a new user profile, but I'll stick
it out a little longer to see if this problem can get solved.