Documentation:Windows Section 3 - Revision history

Clipka: /* Publishing via Group Policy */ registry key

2017-07-04T14:41:02Z

Publishing via Group Policy: registry key

Clipka: /* Background */ superfluous version number

2017-07-04T14:39:11Z

Background: superfluous version number

Clipka: /* POV-Ray Documents Directory */ superfluous version number

2017-07-04T14:37:55Z

POV-Ray Documents Directory: superfluous version number

Jholsenback: generic version

2017-07-04T11:41:26Z

generic version

Clipka: /* Non-Standard Installations */ version number

2017-07-01T08:43:10Z

Non-Standard Installations: version number

Clipka: /* The Benchmark Command-line Option */ version number in file path

2017-07-01T08:41:23Z

The Benchmark Command-line Option: version number in file path

Clipka: /* POV-Ray Documents Directory */ version number

2017-07-01T08:39:37Z

POV-Ray Documents Directory: version number

Clipka: /* Publishing via Group Policy */ updated version numbers in reg key names (plus another minor cleanup)

2017-06-30T20:19:03Z

Publishing via Group Policy: updated version numbers in reg key names (plus another minor cleanup)

Jholsenback: version changes

2017-06-30T09:08:23Z

version changes

Jholsenback: added tag admonishment

2016-12-16T13:07:24Z

added tag admonishment

@@ Line 134: / Line 134: @@
 ====Publishing via Group Policy====
-<p>If you wish to push the settings out via GP, there's only one or two values you need to supply. The main one is the location of the home dir containing the binaries etc. This is <code>HKCU\Software\POV-Ray\v3.8\Windows\Home</code>, which is a <code>REG_SZ</code> containing the path. Alternately you may place this into the same location within <code>HKLM</code> on each workstation; either is sufficient (with <code>HKCU</code> being checked first).</p>
+<p>If you wish to push the settings out via GP, there's only one or two values you need to supply. The main one is the location of the home dir containing the binaries etc. This is <code>HKCU\Software\POV-Ray\vX.y\Windows\Home</code>, which is a <code>REG_SZ</code> containing the path. Alternately you may place this into the same location within <code>HKLM</code> on each workstation; either is sufficient (with <code>HKCU</code> being checked first).</p>
-<p>The second value is that of the user files directory: <code>HKCU\Software\POV-Ray\v3.8\Windows\DocPath</code>, also a <code>REG_SZ</code>. There is no <code>HKLM</code> equivalent of this.</p>
+<p>The second value is that of the user files directory: <code>HKCU\Software\POV-Ray\vX.y\Windows\DocPath</code>, also a <code>REG_SZ</code>. There is no <code>HKLM</code> equivalent of this.</p>
-<p>In either case, if the version of POV-Ray changes, the registry key will change accordingly, but only for X.X releases; e.g. 3.9 would use <code>HKCU\Software\POV-Ray\v3.9\...</code>, but 3.8.1 would still use <code>HKCU\Software\POV-Ray\v3.8\...</code>. This allows multiple versions of POV-Ray to be used on the same system.</p>
+<p>In either case, if the version of POV-Ray changes, the registry key will change accordingly, but only for X.y releases; e.g. 3.9 would use <code>HKCU\Software\POV-Ray\v3.9\...</code>, but 3.8.1 would still use <code>HKCU\Software\POV-Ray\v3.8\...</code>. This allows multiple versions of POV-Ray to be used on the same system.</p>
 ====System Admins / Lab Techs====

@@ Line 115: / Line 115: @@
 <p>If the home directory is not specified in the registry, POVWIN will attempt to work it out by looking at the path from which it was loaded, then taking the parent of that and looking for the <code>help</code> directory within that. So for example if POVWIN was loaded from <code>m:\foo\bar\bin\pvengine32.exe</code>, it would look for <code>m:\foo\bar\help</code>. If this is not found it will look for <code>sounds</code> and then finally <code>tiles</code>. If any of these succeed it will infer that this parent directory is the home and store that for the session along with a value in the registry that lets POVWIN check if it has changed (the Home registry key is not set however). The first time this infer succeeds, a message is displayed in a dialog saying so. The next time POVWIN starts it will do the infer again and if the location has not changed it won't display this message.</p>
-<p>If the POVWIN documents directory is not stored in the registry, POVWIN will - each time it is run - look for its presence in the default location, which is <code><User's Documents Folder>\POV-Ray\vX.y</code> for the case of POV-Ray v3.8. If that directory does not exist, <strong>it will be automatically created</strong> along with the <code>INI</code> directory beneath it. No error message is issued if this create fails, however, nor will it prevent POVWIN from working (provided any needed source/include files can be located elsewhere).</p>
+<p>If the POVWIN documents directory is not stored in the registry, POVWIN will - each time it is run - look for its presence in the default location, which is <code><User's Documents Folder>\POV-Ray\vX.y</code>. If that directory does not exist, <strong>it will be automatically created</strong> along with the <code>INI</code> directory beneath it. No error message is issued if this create fails, however, nor will it prevent POVWIN from working (provided any needed source/include files can be located elsewhere).</p>
 <p>If you want to persist the inferred location, or want to provide custom locations for the above without the need to run an installer on each workstation, you may use the <code>/INSTALL</code> or <code>/QINSTALL</code> command-line switches as documented below.</p>

@@ Line 37: / Line 37: @@
 <p>
 The location of the POV-Ray Documents directory containing user-editable files (include and INI files, sample scenes, insert menu, etc)
-now defaults to <code>&lt;Your Documents Folder&gt;\POV-Ray\vX.y</code> (for version 3.8). You may specify a different location upon
+now defaults to <code>&lt;Your Documents Folder&gt;\POV-Ray\vX.y</code>. You may specify a different location upon
 install if you wish.
 </p>

@@ Line 37: / Line 37: @@
 <p>
 The location of the POV-Ray Documents directory containing user-editable files (include and INI files, sample scenes, insert menu, etc)
-now defaults to <code>&lt;Your Documents Folder&gt;\POV-Ray\v3.8</code> (for version 3.8). You may specify a different location upon
+now defaults to <code>&lt;Your Documents Folder&gt;\POV-Ray\vX.y</code> (for version 3.8). You may specify a different location upon
 install if you wish.
 </p>
@@ Line 70: / Line 70: @@
 ===The Benchmark Command-line Option===
-<p>The <code>/BENCHMARK</code> command-line option causes POVWIN to begin rendering the standard POV-Ray benchmark as soon as it is launched, then exit. Normally no dialogs should be presented - the intention is to allow for the benchmark to be rendered without user interaction. The results of the benchmark are automatically placed into the clipboard at the end of the run, and additionally saved to a file in the POV-Ray documents directory (this is the same location that the include file and sample scene folders are placed upon installation - by default this is <code>c:\users\&lt;username&gt;\Documents\POV-Ray\v3.8</code>). The file name is in the format <code>benchmark-YYYYMMDD.HHMMSS.txt</code>, where the timestamp represents the time the render completed. An example of the file content is below.
+<p>The <code>/BENCHMARK</code> command-line option causes POVWIN to begin rendering the standard POV-Ray benchmark as soon as it is launched, then exit. Normally no dialogs should be presented - the intention is to allow for the benchmark to be rendered without user interaction. The results of the benchmark are automatically placed into the clipboard at the end of the run, and additionally saved to a file in the POV-Ray documents directory (this is the same location that the include file and sample scene folders are placed upon installation - by default this is <code>c:\users\&lt;username&gt;\Documents\POV-Ray\vX.y</code>). The file name is in the format <code>benchmark-YYYYMMDD.HHMMSS.txt</code>, where the timestamp represents the time the render completed. An example of the file content is below.
 </p>
@@ Line 115: / Line 115: @@
 <p>If the home directory is not specified in the registry, POVWIN will attempt to work it out by looking at the path from which it was loaded, then taking the parent of that and looking for the <code>help</code> directory within that. So for example if POVWIN was loaded from <code>m:\foo\bar\bin\pvengine32.exe</code>, it would look for <code>m:\foo\bar\help</code>. If this is not found it will look for <code>sounds</code> and then finally <code>tiles</code>. If any of these succeed it will infer that this parent directory is the home and store that for the session along with a value in the registry that lets POVWIN check if it has changed (the Home registry key is not set however). The first time this infer succeeds, a message is displayed in a dialog saying so. The next time POVWIN starts it will do the infer again and if the location has not changed it won't display this message.</p>
-<p>If the POVWIN documents directory is not stored in the registry, POVWIN will - each time it is run - look for its presence in the default location, which is <code><User's Documents Folder>\POV-Ray\v3.8</code> for the case of POV-Ray v3.8. If that directory does not exist, <strong>it will be automatically created</strong> along with the <code>INI</code> directory beneath it. No error message is issued if this create fails, however, nor will it prevent POVWIN from working (provided any needed source/include files can be located elsewhere).</p>
+<p>If the POVWIN documents directory is not stored in the registry, POVWIN will - each time it is run - look for its presence in the default location, which is <code><User's Documents Folder>\POV-Ray\vX.y</code> for the case of POV-Ray v3.8. If that directory does not exist, <strong>it will be automatically created</strong> along with the <code>INI</code> directory beneath it. No error message is issued if this create fails, however, nor will it prevent POVWIN from working (provided any needed source/include files can be located elsewhere).</p>
 <p>If you want to persist the inferred location, or want to provide custom locations for the above without the need to run an installer on each workstation, you may use the <code>/INSTALL</code> or <code>/QINSTALL</code> command-line switches as documented below.</p>

@@ Line 115: / Line 115: @@
 <p>If the home directory is not specified in the registry, POVWIN will attempt to work it out by looking at the path from which it was loaded, then taking the parent of that and looking for the <code>help</code> directory within that. So for example if POVWIN was loaded from <code>m:\foo\bar\bin\pvengine32.exe</code>, it would look for <code>m:\foo\bar\help</code>. If this is not found it will look for <code>sounds</code> and then finally <code>tiles</code>. If any of these succeed it will infer that this parent directory is the home and store that for the session along with a value in the registry that lets POVWIN check if it has changed (the Home registry key is not set however). The first time this infer succeeds, a message is displayed in a dialog saying so. The next time POVWIN starts it will do the infer again and if the location has not changed it won't display this message.</p>
-<p>If the POVWIN documents directory is not stored in the registry, POVWIN will - each time it is run - look for its presence in the default location, which is <code><User's Documents Folder>\POV-Ray\v3.7</code> for the case of POV-Ray v3.7. If that directory does not exist, <strong>it will be automatically created</strong> along with the <code>INI</code> directory beneath it. No error message is issued if this create fails, however, nor will it prevent POVWIN from working (provided any needed source/include files can be located elsewhere).</p>
+<p>If the POVWIN documents directory is not stored in the registry, POVWIN will - each time it is run - look for its presence in the default location, which is <code><User's Documents Folder>\POV-Ray\v3.8</code> for the case of POV-Ray v3.8. If that directory does not exist, <strong>it will be automatically created</strong> along with the <code>INI</code> directory beneath it. No error message is issued if this create fails, however, nor will it prevent POVWIN from working (provided any needed source/include files can be located elsewhere).</p>
 <p>If you want to persist the inferred location, or want to provide custom locations for the above without the need to run an installer on each workstation, you may use the <code>/INSTALL</code> or <code>/QINSTALL</code> command-line switches as documented below.</p>

@@ Line 138: / Line 138: @@
 <p>The second value is that of the user files directory: <code>HKCU\Software\POV-Ray\v3.7\Windows\DocPath</code>, also a <code>REG_SZ</code>. There is no <code>HKLM</code> equivalent of this.</p>
-<p>In either case, if the version of POV-Ray changes, the registry key will change accordingly, but only for X.X releases; e.g. 3.8 would use <code>HKCU\Software\POV-Ray\v3.8\...</code>, but 3.71 would still use <code>HKCU\Software\POV-Ray\v3.7\...</code>. This allows multiple versions of POV-Ray to be used on the same system.</p>
+<p>In either case, if the version of POV-Ray changes, the registry key will change accordingly, but only for X.X releases; e.g. 3.9 would use <code>HKCU\Software\POV-Ray\v3.8\...</code>, but 3.81 would still use <code>HKCU\Software\POV-Ray\v3.7\...</code>. This allows multiple versions of POV-Ray to be used on the same system.</p>
 ====System Admins / Lab Techs====

@@ Line 10: / Line 10: @@
 {{#indexentry:options, windows command-line}}
 {{#indexentry:Command-line Options, windows version-specific}}
 {{#indexentry:command-line options}}
 <p>
 Options are what previous versions of POV-Ray used to refer to as command-line options. The term is no longer accurate for POV-Ray since version 3.5, because the command line is only one way of passing options to the program. There are now four ways you can pass an option to POV-Ray:
@@ Line 155: / Line 157: @@
 ===Adding New Resolutions===
 {{#indexentry:Resolutions, Adding New}}
 {{#indexentry:Adding New Resolutions}}
 <p>