Re: Vista/Win7 priveleges
I just had to deal with something like this in a standalone I created for a guy running it in Vista. Apparently there's a difference depending on where the app is installed. I put mine in Program Files on his c drive. Even though he's the only user on the computer and has admin privileges, my Rev app wasn't writing text files to disk in its own directory. No error, nothing to indicate it wasn't working. The fix was to right click my app and set its properties to run as administrator. Evidently, even though he has admin permissions, an app he launches has to be specifically set to run as administrator in order to write to a file outside his own Documents folder. I was lucky to find the solution pretty quickly and thus didn't have to study it very much; so there may be (probably is) a lot more to it than that. But it worked, and I was happy. Joe F. On Jan 22, 2010, at 3:47 PM, Jim Bufalini wrote: Jacque wrote: My client wants that auto-run checkbox because his customer base is largely computer illiterate. Many don't know how to start an app without it. (Makes me wish you had to get some kind of license to run a computer.) Well, if they are that illiterate, you may want to consider starting your splash screen (if on Vista) with a message that says something to the effect of, *Please click Allow for any permissions your computer may request.* Because if they click Deny, your program will never run on that computer until it is removed from the blocked list. And, if they don't know how to run a program, they certainly won't know how to do this. When I say Vista blocks the program from running, it actually lets the program load. But, before the program can do anything like access the local hard drives, the dialog is presented. Also, let's say your program does attempt to access the Internet or ports at some point, there could be a second dialog presented. So, for example, in one app I have, I do exactly this. When the program first launches, I throw up a splash message telling them to click Allow to any requests and then write a little text file and then make an unnecessary and arbitrary request to the Internet. These two actions are just to force any possible dialogs from Vista. When I get past the Internet request, I take down the message. ;-) Aloha from Hawaii, Jim Bufalini ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Vista/Win7 priveleges
That OS really annoys the out of me! That makes no sense at all. On Fri, Jan 22, 2010 at 4:06 PM, J. Landman Gay jac...@hyperactivesw.comwrote: I use Install Creator to make Windows installers. There is this warning in the docs: Note about Vista: on Vista you shouldn't run your program from the installer, as it will be executed with administrator privileges. For example any file created with your program in administrator mode won't be overridable the next time your application will be executed, unless it is run as administrator. How limiting is this to the average user? I know Vista/Win7 enforce a sort of super-admin mode and I think this is what installers use. Does this mean that any documents created after an auto-launch will not be accessible at all when the program next runs as a standard user? Even if they are logged in as admin? Or if not, what limitations would be enforced? I'm not clear on what overridable means here. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution -- http://www.andregarzia.com All We Do Is Code. ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
RE: Vista/Win7 priveleges
Jacque wrote: I use Install Creator to make Windows installers. There is this warning in the docs: Note about Vista: on Vista you shouldn't run your program from the installer, as it will be executed with administrator privileges. For example any file created with your program in administrator mode won't be overridable the next time your application will be executed, unless it is run as administrator. How limiting is this to the average user? I know Vista/Win7 enforce a sort of super-admin mode and I think this is what installers use. Does this mean that any documents created after an auto-launch will not be accessible at all when the program next runs as a standard user? Even if they are logged in as admin? Or if not, what limitations would be enforced? I'm not clear on what overridable means here. I suspect this to be a typo for over-writable? ;-) Quite honestly, I've never heard of such a thing. First, it is true that in Vista/7 programs inherit permissions. So, if your installer is running at highest permissions (which it has to) then, if it launches another program, that launched program automatically inherits the permissions of the installer (for that launch only). That said, I always have a checkbox that is, by default, checked for running a program after the installer quits. I have never had a problem with permissions on ensuing launches of the program with files created by that initial launch of the program. And, for example, the initial launch will do things like create SQLite DB files, which must be accessed and modified by the program on ensuing launches, create new registry entries that get updated later, and other things. So, I think you can safely ignore this warning unless on initial launch your program writes something to, for example, the System32 directory and then wants to totally overwrite that file later. Your bigger issue with Vista/7 is that on first launch, Vista is going to put up a dialog asking permission from the user to allow the new EXE to run and will block actual execution of the program until the user clicks Allow. You need to account for this delay, especially if there are any time-sensitive actions your program is going to take on first launch, like accessing the Internet. Aloha from Hawaii, Jim Bufalini ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Vista/Win7 priveleges
Jim Bufalini wrote: So, I think you can safely ignore this warning unless on initial launch your program writes something to, for example, the System32 directory and then wants to totally overwrite that file later. Thanks very much, Jim. Just what I needed to know. My app doesn't have any time-critical operations or write any files at launch, it just sits there and waits for the user to do something, so it sounds like we're okay. My client wants that auto-run checkbox because his customer base is largely computer illiterate. Many don't know how to start an app without it. (Makes me wish you had to get some kind of license to run a computer.) -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
RE: Vista/Win7 priveleges
Jacque wrote: My client wants that auto-run checkbox because his customer base is largely computer illiterate. Many don't know how to start an app without it. (Makes me wish you had to get some kind of license to run a computer.) Well, if they are that illiterate, you may want to consider starting your splash screen (if on Vista) with a message that says something to the effect of, *Please click Allow for any permissions your computer may request.* Because if they click Deny, your program will never run on that computer until it is removed from the blocked list. And, if they don't know how to run a program, they certainly won't know how to do this. When I say Vista blocks the program from running, it actually lets the program load. But, before the program can do anything like access the local hard drives, the dialog is presented. Also, let's say your program does attempt to access the Internet or ports at some point, there could be a second dialog presented. So, for example, in one app I have, I do exactly this. When the program first launches, I throw up a splash message telling them to click Allow to any requests and then write a little text file and then make an unnecessary and arbitrary request to the Internet. These two actions are just to force any possible dialogs from Vista. When I get past the Internet request, I take down the message. ;-) Aloha from Hawaii, Jim Bufalini ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution