 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich <tho### [at] trf de> wrote:
> On 14.07.10 20:17, JimB wrote:
> > Trying to install POV-Ray 3.62 on Windows 7 boxes (one is 64bit the other is
> > 32bit). It is not installing for all users. Is there a way to install it for all
> > users?
>
> You must have administrator privileges to install an application for all
> users on Windows.
>
> Thorsten
I am installing it with admin privileges...even RClicking "Ran as administrator"
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"JimB" <nomail@nomail> wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
> > On 14.07.10 20:17, JimB wrote:
> > > Trying to install POV-Ray 3.62 on Windows 7 boxes (one is 64bit the other is
> > > 32bit). It is not installing for all users. Is there a way to install it for all
> > > users?
> >
> > You must have administrator privileges to install an application for all
> > users on Windows.
> >
> > Thorsten
>
> I am installing it with admin privileges...even RClicking "Ran as administrator"
Using Win7x64, I:
*Created a shortcut to the Command Prompt
*Configured the Shortcut to Run As Administrator
*Ran the Link
I was dropped to C:\Windows\System32
*CD \Users\<YourNameHere>\Downloads
*msiexec /I "POV-Ray for Windows v3.7 beta 38 (64-bit).msi"
And I installed it for Everyone.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"deanmsands3" <nomail@nomail> wrote:
> > I am installing it with admin privileges...even RClicking "Ran as administrator"
> Using Win7x64, I:
> *Created a shortcut to the Command Prompt
> *Configured the Shortcut to Run As Administrator
> *Ran the Link
> I was dropped to C:\Windows\System32
> *CD \Users\<YourNameHere>\Downloads
> *msiexec /I "POV-Ray for Windows v3.7 beta 38 (64-bit).msi"
>
> And I installed it for Everyone.
msiexec /I "POV-Ray for Windows v3.7 beta 38 (64-bit).msi ALLUSERS=1 /qb- you
would have thought.
And it still insists on going in <homedir>\<user>\appdata\povray\...
Why can't it go in Program Files like everything else? If you force it there it
will work for you - even then you have to fix the shortcut. But no shortcuts
for anyone else, broken or otherwise, and a warning box that the application was
installed incorrectly when you run it direct from the executable.
So a plea please for a working installer designed for on multi-user systems, eg
for classroom use which is what I want to do.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Unfortunately we can't please everyone; whenever I make a change to the
install locations (prompted by Microsoft's own changes) someone is unhappy.
I distinctly remember getting a fairly abusive message from a user back in
the mid-90's complaining that installing into 'program files' was a stupid
idea and we should have continued using c:\povray :-(
On 23/07/2010 23:11, Nick wrote:
> Why can't it go in Program Files like everything else?
Because Microsoft recommends not using program files except for system-wide
installations (see below about that). For non-admin installs, even if a
user *thinks* they are installing into program files, they are actually
not: the files get put into the compatibility folder under their user
profile.
> So a plea please for a working installer designed for on multi-user
> systems, eg for classroom use which is what I want to do.
I have been considering changing the code to install into program files by
default (even if it ends up in compatibility folders), as the location we
are using seems to be confusing a bunch of people.
The 'install for all users' option in the version 3.7 installer is
*supposed*, if the installer is elevated, to install in program files. If
it is not then the install has a bug. In respect of v3.6 which you are
using, I'd have to take a look; quite possibly I have the same logic but
perhaps I didn't back-port that.
FWIW The ultimate intent of the 'install for all users' option is to
install the core files into program files, and leave an advertised
component linked to the install. When a user runs the program for the first
time, the advertised component runs and installs the per-user files (scene
files, include files, etc - basically anything they can edit). This isn't
done yet, though.
In any event, I intend to re-write the installer as I don't like
installshield (they seem to have a habit of implying legitimate users of
their software have stolen it). I'm probably going to change to using WiX
(http://wix.codeplex.com/).
If you're interested in helping re-write this you're welcome to volunteer:)
NB please also check the docs about the 'inferred install location' feature
and associated command-line options. It is there specifically for networked
and/or classroom use of the software.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 7/14/2010 2:34 PM, JimB wrote:
> I am installing it with admin privileges...even RClicking "Ran as administrator"
Yeah, I ran into this problem as well. Never did try to identify a
workaround and simply installed it under my local account instead.
--
http://isometricland.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason wrote:
> I have been considering changing the code to install into program files by
> default (even if it ends up in compatibility folders), as the location we
> are using seems to be confusing a bunch of people.
I'd recommend against using virtualization. This is mainly for legacy
software which is not Vista-aware. As Povray 3.7 is a state of the art
software it should support a newer OS directly. Also note that 64-bit
applications will never use virtualization so you may get into trouble
when running 64-bit povray after installing that way.
Both installer and povray itself should contain a manifest marking them
as vista/7 aware. This is mainly done by adding <requestExecutionLevel>
and <supportOS> elements to the manifest. I'm not an InstallShield user
but I'd expect version 12 or higher to add a manifest automatically
based on "Required Execution Level".
My suggestion would be to test for administrator privileges (something
like if (Is(USER_INADMINGROUP,"") = TRUE)). If available, make Program
Files default. If not, display a warning message box that a single-user
install to application data will be performed, and if that is undesired
to cancel and restart with "Run As Administrator".
The latter option might be simplified for the user by providing
an EXE instead of an MSI.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I'd recommend against using virtualization. This is mainly for legacy
> software which is not Vista-aware. As Povray 3.7 is a state of the art
> software it should support a newer OS directly. Also note that 64-bit
> applications will never use virtualization so you may get into trouble
> when running 64-bit povray after installing that way.
Yes, good point.
> My suggestion would be to test for administrator privileges (something
> like if (Is(USER_INADMINGROUP,"") = TRUE)). If available, make Program
It's a little more complicated than this for me currently, as Windows
Installer lies about admin privilege by default (telling us that the user
has admin when they don't). There is a way around this, which I use, and
the installer (at least for the betas) will offer an 'all users' install if
the install is started under elevation. Unfortunately this doesn't work
just by running as administrator; elevation has to be explicitly requested.
> Both installer and povray itself should contain a manifest marking them
> as vista/7 aware. This is mainly done by adding <requestExecutionLevel>
> and <supportOS> elements to the manifest. I'm not an InstallShield user
> but I'd expect version 12 or higher to add a manifest automatically
> based on "Required Execution Level".
Thanks for the tip, this might be the thing I need to change the above
behavior. I don't have IS 12 (we got IS 11 two weeks before they released
v12; Acresso kindly offered to let me upgrade for 'only' $800) but I can
surely add these manually.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Here's something I hadn't come across yet (dual-mode installs now easier):
http://msdn.microsoft.com/en-us/library/dd408068%28VS.85%29.aspx
Microsoft has also apparently realised that it was a bit silly not to have
provided a program files equivalent under the user's profile, so now there
is one: by default, it's C:\Users\<username>\AppData\Local\Programs.
I think that pretty much answers the 'where to install' issue.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason wrote:
> It's a little more complicated than this for me currently, as Windows
> Installer lies about admin privilege by default (telling us that the user
> has admin when they don't). There is a way around this, which I use, and
> the installer (at least for the betas) will offer an 'all users' install if
> the install is started under elevation.
good so you already have a test. My main issue was that 'all users'
should be the default option when started under elevation (not sure
if it is now, didn't yet try beta 38). It's just the behavior you'd
expect when you do Run As Administrator (even worse: if a separate
admin account is used for elevation then the local option would
install into the admins user profile, inaccessible to the user).
Also, a message box might be useful when starting without
elevation to inform about what will happen in this case. It draws
more attention than text on normal installer pages where most users
will simply click next next next until installation is finished,
only to find the program ended up where they didn't expect it.
>> Both installer and povray itself should contain a manifest marking them
>> as vista/7 aware.
>
> Thanks for the tip, this might be the thing I need to change the above
> behavior.
I don't think it will help in your case, as you can't request
admin privileges in the manifest if you wish to support user installs.
However, the presence of this part of the manifest tells Vista that
the application is Vista-aware, which means the app will not be run
in compatibility mode (so virtualization will be disabled).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason <del### [at] deletethistoopovrayorg> wrote:
> FWIW The ultimate intent of the 'install for all users' option is to
> install the core files into program files, and leave an advertised
> component linked to the install. When a user runs the program for the first
> time, the advertised component runs and installs the per-user files (scene
> files, include files, etc - basically anything they can edit). This isn't
> done yet, though.
I was hoping you guys could also add an option during the install process or in
the Settings to change the location the per-user files are stored. I would like
to move them all to <homedir>\<user>\ and not <homedir>\<user>\Documents\. But
the program complains it cannot find it's files.
There are some settings to change the file locations, but I'm not able to change
them all and they are all over the place.
Thanks
Dean
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
