VirtualStore location

[Shari]

>Actually....   It's a can of worms.  AFAIKT if a user has UAC turned 
>on the virtual storage will activate.  If the user turns UAC off 
>they can no longer get the reference to the file.  If they then turn 
>UAC back on they get an entirely different virtual storage file. 
>Micro$oft provide the virtual storage purely for legacy software so 
>it doesn't "break".  However it is a band aid and there are no 
>guarantees it will be there in future Windows versions.  Better to 
>use the designated folders such as provided by the SpecialFolderPath 
>function.  Even writing to the root directory (C:\MyProgramsName) is 
>no longer recommended as it is suggested it is the next place 
>Microsoft will "lock down".    This is the price we Windows users 
>pay for using a system that was never designed to be secure.
>
>Scott Kane

Scott,

Actually I didn't want to write to it, but to delete any VirtualStore 
files that MS created if a user decides to uninstall my software 
using my custom built (Rev menu item) uninstaller.  Right now, the 
Uninstaller looks for files the game may have created outside the 
game folder, and if they exist, deletes them.

With Windows becoming more and more nitpicky about what files you can 
update, my next release won't create or update any files or stacks in 
the program's folder any more.  All files, including stacks that get 
updated, will be installed in a hopefully writeable location.  During 
initial launch, it will check several SpecialFolderPath() options to 
see if they exist, and the first hit it finds, that's where the files 
will go.    But it means more files to Uninstall.....

Mac is so clean.  I have so few troubles on Macs.  Microsnot is a bugger :-)

Shari
-- 
Gypsy King games for
MAC and WlND0WS
http://www.gypsyware.com