well the new version will fix this, i could build you a copy for testing.
but let me clarify something based on my understanding of vista which might help you understand what i think is happening.
when farr first starts, if the ini doesnt exist yet in VirtualStore, it will read the one in its application directory. when it saves it, it will try to save it in its application directory. but vista will intercept this and write it instead to VirtualStore.
thereafter, even if you copy and replace the ini in the application dir, vista will trick the app into using the one in VirtualStore.
basically VirtualStore is alike a secret hidden cache, which makes apps think they can write into the application directory when they really cant. it can cause EXACTLY the kinds of troubles you are experiencing.
personally this seems to be like a horrible solution on microsoft's part, though i understand the idea. In my opinion they should have set the permissions to let an app write into its own directory. that would have made life so much simpler.
anyway try this for now:
1. exit farr.
2. delete the virtual store ini.
3. copy your desired ini into application directory.
4. restart farr.
that really should work.
if you restart farr between steps 2 and 3, you trick yourself.
ps. if this still gives you trouble don't worry about it and email me for new vista-aware version (firstname.lastname@example.org).
wait, i think i already incorporated the vista stuff in 2.00.82
, so its using vista user directory
sorry for the confusion!
so can you tell me where you WANT to portable usb copy to get its farr ini file from and save to? is it the case that you are running it on vista and you want it to store its settings in the usb drive application directory where farr lives, instead of to the user settings on c drive? will vista let an application on the usb drive write to its application directory? if so i can tell you what to do to convince farr to override vista default save location.