I'm also at a complete loss regarding all this discussion. If volunteers are unable to find the default Output folder location for WinBMD produced files which I happen to maintain should be in a subfolder of the WinBMD what chance have they got of understanding the proposed new WinBMD requirements. We seem to be creating a rod for our back, this discussion started because of a suggested requirement to assist volunteers in being able to locate their files to send to their Co-ordinators. If it was recommended that all files produced by WinBMD were to be held in the default subfolder on WinBMD aptly called Output folder this problem should resolve itself without all these changes to WinBMD. I keep saying I have WinBMD to work on Vista and have no trouble finding where the WinBMD files are held C:/WinBMD/Output. I believe I have found a solution to the problem why some volunteers can't get WinBMD on Vista and fingers crossed I have managed to get two long suffering Vista volunteers to get WinBMD to work following my simple suggestion of C:/WinBMD/Output. Allan Raymond ----- Original Message ----- From: "Nowl" <owl.news@zen.co.uk> To: <FreeBMD-Syndicates@rootsweb.com> Sent: Wednesday, February 04, 2009 1:17 PM Subject: Re: re Windows Wish List Excuse me butting in. . . I've been following the exchanges between Ian and Barrie with great interest, as I do feel the current default Save Path causes some problems. But I'm not following why we would want to move users' existing files at all. I thought the idea was to define a new default location that was easier to find for new users and "better" from a programmers' point of view, particularly with Vista. But shouldn't it apply only to new users/fresh installs, rather than upgrades? People who are already happily using WinBMD surely already know where to find their files and/or have defined a custom Save Path and don't want it changed. Much of Ian and Barrie's discussion seems to be about the difficulty of discovering the path to a user's current output folder and the mechanism of moving it. Couldn't all this be avoided if the installer checked for an existing WinBMD, and if it found one, left the current settings in place? I'm also wondering whether the installation would fail if, when asked where they want their files moved, users chose their existing output folder, since files can't be "moved" to the same place? Would they be forced to choose another path and then switch back? I'm not a programmer, so may well be missing the point here and am happy to be corrected :-) -- Nowl