 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 18-08-31 à 16:47, Kenneth a écrit :
> "Kenneth" <kdw### [at] gmail com> wrote:
>> "Kenneth" <kdw### [at] gmailcom> wrote:
>>
>> Well, things are still not quite right...
>>
> ..... and they're getting stranger :-/
>
> Now the same problem is happeniong with my (older) 3.7 alphas and betas-- even
> my original 3.7.0-- EXCEPT with my 'stand-alone' 3.7.1 beta 9 install. That
> one continues to work correctly. (It's own 'guts' are in its own folder in
> "Programs/POV-Ray" called "3.7 beta", which might be a clue; all the other 3.7
> alphas and betas-- and 3.7.0-- share another different folder there but still in
> "Programs/POV-Ray".)
>
> So I re-booted my computer as a last resort. But the problem remains.
>
> Seems that *something* must have gotten corrupted in the 'problem' POV-ray
> folder (my only guess right now.) Woe is me :-(
>
>
>
To me, it look like you want to write the files into the POV-Ray install
directory instead of the .POV file location.
Make sure that the output paths all point to the correct locations.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain <kua### [at] videotronca> wrote:
> Le 18-08-31 à 16:47, Kenneth a écrit :
> >
> > Seems that *something* must have gotten corrupted in the 'problem' POV-ray
> > folder (my only guess right now.) Woe is me :-(
>
> To me, it look like you want to write the files into the POV-Ray install
> directory instead of the .POV file location.
> Make sure that the output paths all point to the correct locations.
I probably confused you with a lack of detail; sorry. My original two 'complete'
POV-ray installs (3.7.0 and 3.7.1 beta 9) had their various folders in two
places, as usual: "Documents", and "Programs". My scene files are in a separate
folder in "Documents", outside the 'master' "POV-RAY" folder there, for safety's
sake. The folder I send renders to is also a separate one, and also in
"Documents." My main problem was that both versions of the program have there
own POVRAY.INI files-- with the library path to my image-output folder in both--
but I forgot to update one of those with a *change* I made to the name of that
folder.
All is well now.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Kenneth" <kdw### [at] gmailcom> wrote:
>
> No vestige of beta 4 remains!!
[even further off-topic]
I'm curious: Is there a way to do an automated word search (and/or partial word
search-- "beta4" for example) of the ENTIRE Windows registry, all at once? In
other words, to find a particular registry entry (or multiple ones) when you
only know part of its name beforehand?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 03.09.2018 um 21:34 schrieb Kenneth:
> "Kenneth" <kdw### [at] gmailcom> wrote:
>
>>
>> No vestige of beta 4 remains!!
>
> [even further off-topic]
>
> I'm curious: Is there a way to do an automated word search (and/or partial word
> search-- "beta4" for example) of the ENTIRE Windows registry, all at once? In
> other words, to find a particular registry entry (or multiple ones) when you
> only know part of its name beforehand?
You mean something like a "find all" that spits out a list of
occurrences, rather than a find first / find next mode of operation?
Sure - albeit not with regedit, but a lesser known command-line tool,
`reg.exe`.
For instance, to search for anything in "HKEY_LOCAL_MACHINE" containing
"v3.7-beta", open a command prompt and run:
reg.exe HKLM /s /f "v3.7-beta"
then go and make yourself a fresh cup of your favourite hot beverage.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 18-09-03 à 15:34, Kenneth a écrit :
> "Kenneth" <kdw### [at] gmailcom> wrote:
>
>>
>> No vestige of beta 4 remains!!
>
> [even further off-topic]
>
> I'm curious: Is there a way to do an automated word search (and/or partial word
> search-- "beta4" for example) of the ENTIRE Windows registry, all at once? In
> other words, to find a particular registry entry (or multiple ones) when you
> only know part of its name beforehand?
>
>
>
>
In regedit, you can only find matches one by one. You can use F3 to find
the next occurance.
It can be very long and tedious.
There are some third party replacements, like Registry Workshop, that
will find all occurances in one swoop and let examine all hits in any order.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
