 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I think there should be an uninstall link
uninstall pov-ray? blasphemy!
B.Gimeno
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 10/02/2012 20:22, B. Gimeno nous fit lire :
>
>
>
>> I think there should be an uninstall link
>
> uninstall pov-ray? blasphemy!
Indeed.
More seriously, clobbering the menu of MS-* with 1 uninstall icon/entry
per installed program has a very bad effect on reactivity of the menu,
(nearly doubling the number of I/O when computing the menu, for no real
benefit, as that shortcut is not gonna be used very often)
so current recommendation is to NOT add an uninstall shortcut and let
the removal being handled by the Parameters/ sub panel.
Sic Transit Gloria Mundi.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/02/2012 03:37, Stephen wrote:
> Oops! And here is me thinking that you were being really clever and
> automatically installing the version belonging to the OS.
We used to do that with the old installer, but now that we have a
combined one I didn't see any point in not providing the other
binaries in case someone wanted them. The installer is smart enough to
install the right shortcut (standard, SSE2 or 64-bit) to the
appropriate binary.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Penrose tiling patterns and all the other stuff perfectly installed on my
Windows 7 64-bit (aspire laptop 5732ZG, Dual Core Intel T4400 2,2 GHz, 4GB RAM)
thanks for you effort
B.Gimeno
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2/9/2012 16:09, Christian Froeschlin wrote:
> application automatically started after installation, ...
I always worry that's going to actually launch the program as administrator. :-)
--
Darren New, San Diego CA, USA (PST)
People tell me I am the counter-example.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
