 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Folks,
I would appreciate it if some of you could sanity-check the RC4
windows installer, which may be found here:
http://www.povray.org/beta/povwin-3.7.RC4-setup.exe
This is a combined 32 and 64-bit setup which is the first we have done
using NSIS (previously we used InstallShield). Please advise if you
have any installation issues.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 09.02.2012 17:25, schrieb Chris Cason:
> I would appreciate it if some of you could sanity-check the RC4
> windows installer,
installed on Windows 7 64bit and XP 32 bit, both times within
C:\CGI\POV-Ray (and not "Program Files"), changed the master ini file
(to point to my own include directories and set output to OpenEXR), did
run a quick test with one of my more complex scenes and everything worked.
-Ive
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in news:4f33f369@news.povray.org Chris Cason wrote:
> Folks,
>
> I would appreciate it if some of you could sanity-check the RC4
> windows installer, which may be found here:
Worked fine on win7/64
Thanks,
Ingo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
V3.7 RC4 installation appears to have worked perfectly on my Windows 7
(Ultimate, 64-bit, SP1) machine using all default options.
I'll do some customisation and test a few more things then report back.
Looking good so far!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Chris Cason wrote:
> I would appreciate it if some of you could sanity-check the RC4
> windows installer
Works fine on XP 32-bit, unfortunately I'm not currently
in the same country as my Windows 7 64-bit machine, I'll try
that on the weekend.
> This is a combined 32 and 64-bit setup which is the first we have done
> using NSIS (previously we used InstallShield).
So you went down this route after all ;)
A few suggestions:
I think there should be an uninstall link (short-cut to uninstall
exe) added to the start menu. Note the uninstaller doesn't have to
reside top-level, you could also write it to $INSTDIR\bin, although
you then need to set $INSTDIR to $INSTDIR\.. on execution (even
better would be to retrieve the installdir from registry when
starting the uninstaller, then the uninstaller also works if
it gets copied to a different location).
BTW how are you removing the files? There is some dangerous sample
code floating out there that recursively removes $INSTDIR in a way that
would clear the users drive should he accidentally install to c:\.
Also note there are some optional checkboxes that could be
activated for the Finish Page, to determine whether desktop
icons should be created, some readme or manual opened, the
application automatically started after installation, ...
Finally, note there is a BgImage Plugin included with the
standard NSIS distribution. If the final version has some sort
of official raytraced image to show off the release, it could
easily be added as a fullscreen background to the installer.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 10/02/2012 11:09, Christian Froeschlin wrote:
>> This is a combined 32 and 64-bit setup which is the first we have done
>> using NSIS (previously we used InstallShield).
>
> So you went down this route after all ;)
Yep, I just couldn't stand using IS anymore. I utterly loathe that
product :-/
> I think there should be an uninstall link (short-cut to uninstall
> exe) added to the start menu. Note the uninstaller doesn't have to
The old installer did do this, however I chose not to replicate that
as I have seen it recommended that installers do not create such
shortcuts. Can't recall where I read this other than it was a
sufficiently authoritative location that I chose to follow the
recommendation.
> BTW how are you removing the files? There is some dangerous sample
> code floating out there that recursively removes $INSTDIR in a way that
> would clear the users drive should he accidentally install to c:\.
I was fairly careful about the removal: the code does a recursive
remove of the specific named sub-directories of INSTDIR (bin, help
etc), and then does an rmdir (non-recursive so will fail if not empty)
of INSTDIR. Also, the installer code will not permit the user to
choose the root dir as a install target.
You're welcome to the installer source if you are familiar with NSIS
and want to try to improve it; it's my first NSIS script so there
would definitely be room for improvement.
> Also note there are some optional checkboxes that could be
> activated for the Finish Page, to determine whether desktop
> icons should be created, some readme or manual opened, the
> application automatically started after installation, ...
The POVWIN program itself will auto-load the release notes and change
log when it is started for the first time after an install. I could
add a run checkbox I guess.
> Finally, note there is a BgImage Plugin included with the
> standard NSIS distribution. If the final version has some sort
> of official raytraced image to show off the release, it could
> easily be added as a fullscreen background to the installer.
Thanks for the info, I'll have a look.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 09/02/2012 4:25 PM, Chris Cason wrote:
> This is a combined 32 and 64-bit setup which is the first we have done
> using NSIS (previously we used InstallShield). Please advise if you
> have any installation issues.
The installer correctly installed pvengine64.exe on my Win7 (Home
premium SP1)
But there was no option to install the 32 bit version which I need to
run Bishop3D. Could you add an option to install the 32 bit version as well.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 10/02/2012 18:51, Stephen wrote:
> But there was no option to install the 32 bit version which I need to
> run Bishop3D. Could you add an option to install the 32 bit version as well.
It's there (in the bin directory); just point Bishop3d at it.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>Chris Cason on date 09/02/2012 17:25 wrote:
> Folks,
>
> I would appreciate it if some of you could sanity-check the RC4
> windows installer, which may be found here:
>
> http://www.povray.org/beta/povwin-3.7.RC4-setup.exe
>
> This is a combined 32 and 64-bit setup which is the first we have done
> using NSIS (previously we used InstallShield). Please advise if you
> have any installation issues.
>
> -- Chris
Fine on Windows XP 32 bit, even changing default documents path.
Paolo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 10/02/2012 7:57 AM, Chris Cason wrote:
> On 10/02/2012 18:51, Stephen wrote:
>> But there was no option to install the 32 bit version which I need to
>> run Bishop3D. Could you add an option to install the 32 bit version as well.
>
> It's there (in the bin directory); just point Bishop3d at it.
>
> -- Chris
Oops! And here is me thinking that you were being really clever and
automatically installing the version belonging to the OS.
Thanks.
--
Regards
Stephen
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
