> In addition, it is required the files should be copied to 'C:\Program files' as an administrator.
> and remove the *** access block *** that win7 (windows vista) puts on the help file afterwards.
> The person who reported this issue suggest to use windows installer for the gnuplot for windows.
> Before talking the way of install in the future, I would like to know the current state the security
> setting of the windows vista and 7.
Because so many program force the user to be administrator to run (and
therefore put the operating system at risk from bugs and malicious code),
Microsoft has developed a complicated system of permissions intended to
prevent administrative users from being able to easily cause damage. On
Vista and Seven, an administrative user must request elevated permissions
(i.e. "full" administrative access) before installation. This elevation
is apparently requested automatically if the installer is called
*setup*.exe. More information:
There are also integrity access controls to contend with. Processes
with lower integrity levels (e.g. the login/shell) cannot write to
higher-integrity data (e.g. Program Files), regardless of any other access
controls that might say otherwise. More information:
There are, of course, the usual discretionary access controls that
prevent non-administrative users from writing to system locations like
Program Files. These are separate from the integrity controls mentioned
I haven't read it, but this sounded like a good resource based on its
title. Sorry about the format; it's not my choice.
There are also NTFS streams attached to files downloaded from the internet
that mark those files as potentially unsafe. These streams are propagated
to files extracted from a so-marked zip file. Marked executables require
the user agree to an additional dialog before running. The "potentially
unsafe" mark can be removed via the Unblock button in the file properties,
or via explicitly finding and removing the NTFS stream. Since FAT
filesystems don't support streams, this is a non-issue in those cases
(e.g. USB thumb drives).
We could work around these issues by creating an installer for gnuplot
on Windows (possibly using Windows Installer, or not) and shipping (a)
manifest file(s). This would require a lot of Windows-specific effort and
code. I got out of the messing-with-Windows-Installer business some years
back, and I don't want to get back into it. Without a willing contributor
and maintainer, I think it is most friendly for gnuplot to ship the files
and no installer. Those who need an installer will be able to create an
installer for their evironment from the files we provide with minimal
As for winhlp, Microsoft has made clear it's going the way of the
dodo bird. The popular thing to do these days seems to be to ship the
documentation and help as a set of HTML pages (also copied into Program
Files). When the user requests help, the default browser is simply pointed
at the appropriate page.