| Thank you for the reply, Michel. I assure you that the install wanted to install Ekiga in the My Documents directory. I made a deliberate decision to allow it, because I thought maybe there was something in My Docs that Ekiga could use. I thought it a bit unusual, but let it happen. I could have browsed to Program Files and forced the install in that directory, but decided not to. In any case, I am concerned about two things. First, where the deletions would have stopped had I not interrupted the uninstall by unplugging my computer. As you can see in the screen shot I link to below, Ekiga installed itself in MyDocs. When I uninstalled it, the uninstaller did not stop deleting files when the Ekiga subdirectory was empty. Instead, it jumped up a level in the directory and began deleting file within other My Docs subdirectories. Screen shot: http://www.flickr.com/photos/34403391 N07/4356542596/ If I had not interrupted the uninstall, what would have happened when the uninstaller emptied the My Documents directory? Would it then have started deleting files a level higher in the directory hierarchy, and continued until it erased the entire hard drive? Second, I also ask myself if anything would have been different had I forced Ekiga to install itself in the Program Files directory, and then ran the uninstaller? In other words, if at any time a user decides to uninstall Ekiga for any reason whatsoever, will the uninstall NSI script attempt to erase everything at that level (and maybe higher) on the hard drive? Maybe the reason you (the Ekiga team) have not seen this problem before is that no one had tried to uninstall it on a Win XP box. Maybe this problem is waiting in the uninstall script on every Windows computer Ekiga has been downloaded to? I think the Ekiga team needs to stop releasing the beta Win XP version until this issue is resolved. Thank you again, Stan --- On Sun, 2/14/10, michel memeteau <michel memeteau gmail com> wrote: From: michel memeteau <michel memeteau gmail com> |