AW: Difference between XP and Vista/7?
Tiemo Hollmann TB
toolbook at kestner.de
Sun Nov 1 10:19:40 CST 2009
as Shao already pointed out, you may not write / update to the program dir,
as far, as you haven't given full access for a normal user to your sub dir.
The installer (inno) gets from vista once admin persmissions because of the
name of the setup to allow him to write to the program dir. But your
standalone may not.
As Shoa told you, Vista, 7 and later will virtualize your files to the
virtual store, if you attempt to write / update to the program dir (or sub
dir of the program dir). Usually this happens completely transparent, so
that it gives you a feeling, as if you HAVE updated your file in the program
dir, but actually it was copied to the virtual store and will bring you into
trouble in the future, because you have two files (read the posts in the
archives "Vista virtualize", especially of Ken Ray:
http://www.sonsothunder.com/devres/revolution/tips/env007.htm) So that is
why I actually am unsure, what is going on in your case, when you say, the
update of the preferences wasn't taken.
Conclusion, as Shao also said, is you should put your files, which have to
be updated in a writeable dir.
> -----Ursprüngliche Nachricht-----
> Von: use-revolution-bounces at lists.runrev.com [mailto:use-revolution-
> bounces at lists.runrev.com] Im Auftrag von Lars Brehmer
> Gesendet: Sonntag, 1. November 2009 16:31
> An: use-revolution at lists.runrev.com
> Betreff: Difference between XP and Vista/7?
> I have a standalone that is thoroughly tested in XP and I am now
> trying in Vista and Windows 7. I never bothered with Vista before, but
> Windows 7 will surely be adopted in far greater numbers than Vista
> was, so they are obviously extremely important now.
> This is a standalone that is a splashscreen with the actual program
> stacks in the package or program folder. Nothing unusual here - in
> OSX the program stacks have always been "savable." In XP as well,
> whether the stanalone is installed or is just a program folder sitting
> on the desktop containing the .exe and other program stacks. I don't
> use any installer for OSX, just dragging the application to the
> applications folder.
> When the free trial is launched for the first time, some custom
> properties which define the trial period are set in one of the stacks
> and saved. If the user buys the program, he receives an unlock code
> that also, among other things, sets some custom properties in one of
> the program stacks and saves it.
> In Vista this all works as expected in the Rev IDE and also works as a
> program folder with the .exe inside on the desktop. But when I
> actually install the program and launch it from the start menu, the
> necessary custom properties for defining the the trial period and then
> the unlocking process are not saved.
> I use the Inno setup compiler to create my Windows installers, and
> again, it always worked perfectly in XP. As you can see, I don't know
> a lot about Windows, I've only gotten pretty good at what it takes to
> get my standalones working in XP.
> So I guess the question is this; What is different about Vista that an
> installed applications works differently than one that isn't
> installed? Why won't it save some simple custom properties once the
> standalone is actually installed? Or does the problem lie in the Inno
> setup compiler? And is it the same for Windows 7?
> Any tips would be greatly appreciated!
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode