 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I think that the install should ask you where you want the pov ray files
to be installed to.
Personally I would prefer the files to be in program files instead of my
documents.
Is it possible at the moment to move the files somewhere else out of my
documents?
If I move the folder, povray complains about it and I can't find any
options, so is there a way to point povray to the new location?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>I think that the install should ask you where you want the pov ray files
> to be installed to.
> Personally I would prefer the files to be in program files instead of my
> documents.
>
> Is it possible at the moment to move the files somewhere else out of my
> documents?
> If I move the folder, povray complains about it and I can't find any
> options, so is there a way to point povray to the new location?
In Vista...
open a cmd prompt as administrator
(windows key, type cmd in search box, cntrl-shift-enter)
run the pov installer from the command line
select install for all users... that should let you select the
location for the program files.
This install process is sort of clumsy, if you do a single
user install with administrator privledges then POV will
end up in program files, but if it doesn't have privledges
it'll end up in a hidden roaming profile because of UAC.
Either way, the editable portion of the files ends up in
documents.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I hope the POVRay team will create a standard installation process to eliminate
multi-user or privilege related problems.
In my opinion, the installation should be :
- Programs (pvengine.exe, manuals...) and non-editable files => Program files
- Shared files (includes, objects...) => Accessible for all users
- Personal files (personal configuration for example) => Current user
The directories should be configurable in a main configuration file.
Applications and data should be separated, Windows provides this.
A portable version will be a great thing for more experienced users who want to
create their own installation. For example, put the shared files in a network
drive.
The current installation process totally breaks non official versions (I have
managed to use MegaPOV on Vista but I had to copy and duplicate files to make it
run like before).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 23.01.10 14:51, Rocco wrote:
> I hope the POVRay team will create a standard installation process to eliminate
> multi-user or privilege related problems.
>
> In my opinion, the installation should be :
>
> - Programs (pvengine.exe, manuals...) and non-editable files => Program files
> - Shared files (includes, objects...) => Accessible for all users
> - Personal files (personal configuration for example) => Current user
>
> The directories should be configurable in a main configuration file.
>
> Applications and data should be separated, Windows provides this.
You realize that under Vista the issue is not that POV-Ray does not want to
install in program files, but as discussed numerous times before, is not
allowed to install there by Vista itself unless *you*, the user, allow it to
do so. If you prohibit POV-Ray to access the program files folder, you can
hardly be surprised that it does not install where you prohibited it from
installing at in the first place!
Please read the old messages in this group. The problems Vista creates for
non-administrator installs have been discussed numerous times before. There
is really no need to start over discussing the benefits and drawbacks of
Vista rights management! They are for M$ to fix, and nothing POV-Ray can do
anything about.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich <tho### [at] trf de> wrote:
> You realize that under Vista the issue is not that POV-Ray does not want to
> install in program files, but as discussed numerous times before, is not
> allowed to install there by Vista itself unless *you*, the user, allow it to
> do so.
What do other programs do? I don't remember seeing the same complaint in
relation to other programs (ie. that the program installs itself into the
My Documents folder by default).
> Please read the old messages in this group. The problems Vista creates for
> non-administrator installs have been discussed numerous times before. There
> is really no need to start over discussing the benefits and drawbacks of
> Vista rights management! They are for M$ to fix, and nothing POV-Ray can do
> anything about.
There is something POV-Ray can do: Ask the user what to do. ("Because of
<reason xyz> POV-Ray will be installed in <the My Documents folder>.
Yes/No/Cancel.")
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 23 Jan 2010 19:19:03 +0100, Warp <war### [at] tagpovrayorg> wrote:
> Thorsten Froehlich <tho### [at] trfde> wrote:
>> You realize that under Vista the issue is not that POV-Ray does not
>> want to
>> install in program files, but as discussed numerous times before, is not
>> allowed to install there by Vista itself unless *you*, the user, allow
>> it to
>> do so.
>
> What do other programs do? I don't remember seeing the same complaint
> in relation to other programs (ie. that the program installs itself into
> the My Documents folder by default).
Many installers are properly setup to request privilege escalation if
needed. In some cases, Windows itself will deduce that it is needed and
automatically prompt for it.
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 23.01.10 19:19, Warp wrote:
>> You realize that under Vista the issue is not that POV-Ray does not want to
>> install in program files, but as discussed numerous times before, is not
>> allowed to install there by Vista itself unless *you*, the user, allow it to
>> do so.
>
> What do other programs do? I don't remember seeing the same complaint in
> relation to other programs (ie. that the program installs itself into the
> My Documents folder by default).
It depends. Some installers just don't work. What does work though,
amazingly, is that if one uses an older Visual Studio (2003) to build a M$
Installer is that it magically works without too many problems. The same is
not true if using VS 2008 to build the same installer (out of a converted
project file).
>> Please read the old messages in this group. The problems Vista creates for
>> non-administrator installs have been discussed numerous times before. There
>> is really no need to start over discussing the benefits and drawbacks of
>> Vista rights management! They are for M$ to fix, and nothing POV-Ray can do
>> anything about.
>
> There is something POV-Ray can do: Ask the user what to do. ("Because of
> <reason xyz> POV-Ray will be installed in<the My Documents folder>.
> Yes/No/Cancel.")
No, because POV-Ray is not the Windows installer!
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 23.01.10 19:25, Fredrik Eriksson wrote:
> In some cases, Windows itself will deduce that it is needed and
> automatically prompt for it.
Indeed, this feature seems to exist if the installer is built with an older
version of Visual Studio, for example. I guess the assumption M$ makes is
that if the system detects an older installer it cannot know about Vista's
odd manual privilege requirements and does things automatically.
I wonder if all these issues have been resolved in Windos 7...
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 23 Jan 2010 19:44:15 +0100, Thorsten Froehlich <tho### [at] trfde>
wrote:
> On 23.01.10 19:25, Fredrik Eriksson wrote:
>> In some cases, Windows itself will deduce that it is needed and
>> automatically prompt for it.
>
> Indeed, this feature seems to exist if the installer is built with an
> older version of Visual Studio, for example. I guess the assumption M$
> makes is that if the system detects an older installer it cannot know
> about Vista's odd manual privilege requirements and does things
> automatically.
http://msdn.microsoft.com/en-us/library/bb384154.aspx
"Windows Vista built-in installer detection prompts for consent when you
run under UAC. A bootstrapper (Setup.exe) built with Visual Studio 2005
always prompts for consent, regardless of what it is installing."
"In Visual Studio 2008, the behavior of Setup.exe changes; it does not
prompt for elevation when it is started. To prevent the elevation prompt,
the embedded manifest of the bootstrapper specifies that Setup.exe run
with a requested execution level of asInvoker."
The proper way of triggering a privilege escalation prompt with Windows
Installer is to set the RequiresElevation property appropriately. Relying
on the installer detection heuristics is a bad idea, not the least because
it is not available for 64-bit installers.
--
FE
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thorsten Froehlich wrote:
> I wonder if all these issues have been resolved in Windos 7...
>
> Thorsten
FWIW
When I installed the latest Beta on my Window 7 system it was installed
me the choice of install for all users. But then as I have only one
account on this laptop it is hardly surprising.
--
Best Regards,
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
