|
|
"Chris Cason" <del### [at] deletethistoopovrayorg> wrote in
message news:486f0972$1@news.povray.org...
> Bob Hughes wrote:
>> The currently available file on the beta web page wouldn't go into my
>> Vista
>> computer so I had to do some system registry additions and font installs
>> manually. I'm the sole user, administrator status.
>
> I was able to install under Vista as an ordinary user (no admin). I had to
> choose a different install path, and also had to click to ignore several
> errors during install (where the installer attempts to do things like set
> admin keys or install fonts - none of these are essential). No registry
> editing was needed to get the installed program to work. I'm not sure what
> went awry in your case.
Glad to hear you say that, I think. ; )
I'm fairly certain I had to change the security status of the program folder
to let the installer write the files first, likewise the "bin" subfolder, as
I recall. I didn't have any luck with specifying a different location
outside of Program Files. Then again, I kept stopping when I got the errors.
> NB the fonts in question are part of the standard POV-Ray include
> directory
> and weren't even intended to be installed into Windows: I didn't realise
> until I did the no-admin-rights Vista test that InstallShield
> automatically
> installs any fonts it finds in the file set, unless you tell it otherwise.
> At that point it was so late I decided not to make a new installer as the
> fonts will be removed when the current beta is uninstalled.
I actually added the fonts after the fact, remembering that now, and just
wanted to go ahead with the manual install of them anyway. I had run povray
before that without any problem.
A lack of any other reports of trouble getting POV installed into Vista
makes my experience seem unique. Maybe I can retry it again after an
uninstall, now that I know I can put the thing back together easily enough,
just to see if I can figure out if those errors are ignorable or not. If
anything I'm wondering why the initial trouble about the folder writing
happened. I was sure anything like that would be reported if other people
had the same problem unless it's a simple thing I've overlooked-- very
likely for me.
Bob
Post a reply to this message
|
|