 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I just tried with a fresh copy of POV-Ray 3.62 on Windows 10.
"Keep single instance" is enabled by default after installing POV-Ray.
The very first time you try to open 3 files at once, 2 instances of
POV-Ray are spawned, and two of the instances tell me that "Keep single
instance" is enabled, blah blah blah. After you click the checkbox to
hide this message in the future, the program starts behaving as it
should. E.g. all files are loaded in one instance of POV-Ray.
So, something happened to the editor in recent versions.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/22/2018 2:11 PM, Mike Horvath wrote:
> I just tried with a fresh copy of POV-Ray 3.62 on Windows 10.
>
> "Keep single instance" is enabled by default after installing POV-Ray.
>
> The very first time you try to open 3 files at once, 2 instances of
> POV-Ray are spawned, and two of the instances tell me that "Keep single
> instance" is enabled, blah blah blah. After you click the checkbox to
> hide this message in the future, the program starts behaving as it
> should. E.g. all files are loaded in one instance of POV-Ray.
>
> So, something happened to the editor in recent versions.
>
>
> Mike
I tried 3.62 on my principal Windows 7 machine, and the behavior is kind
of random. It's possible my system is messed up after
installing/reinstalling POV-Ray so many times.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/22/2018 2:30 PM, Mike Horvath wrote:
> I tried 3.62 on my principal Windows 7 machine, and the behavior is kind
> of random. It's possible my system is messed up after
> installing/reinstalling POV-Ray so many times.
>
>
> Mike
Now I can't uninstall/repair POV-Ray 3.62.
"Error opening installation log file. Verify that the specified location
exists and is writable."
Sigh.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/22/2018 2:40 PM, Mike Horvath wrote:
> On 1/22/2018 2:30 PM, Mike Horvath wrote:
>> I tried 3.62 on my principal Windows 7 machine, and the behavior is
>> kind of random. It's possible my system is messed up after
>> installing/reinstalling POV-Ray so many times.
>>
>>
>> Mike
>
> Now I can't uninstall/repair POV-Ray 3.62.
>
> "Error opening installation log file. Verify that the specified location
> exists and is writable."
>
> Sigh.
This was easy to fix. Simply restart Explorer in Task Manager.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Mike Horvath <mik### [at] gmail com> wrote:
>
> This was easy to fix. Simply restart Explorer in Task Manager.
>
I've never attempted such a thing on a running system; I thought it would
completely shut down the Windows OS, or something just as bad, leading to...
chaos! :-O
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/22/2018 3:21 PM, Kenneth wrote:
> Mike Horvath <mik### [at] gmailcom> wrote:
>
>>
>> This was easy to fix. Simply restart Explorer in Task Manager.
>>
>
> I've never attempted such a thing on a running system; I thought it would
> completely shut down the Windows OS, or something just as bad, leading to...
> chaos! :-O
>
>
>
>
If you stop the process, your Desktop will disappear except for the
background. Most of the time it will automatically restart itself, but
I've had it not do so a few times. This can be annoying.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 22.01.2018 um 18:41 schrieb Kenneth:
> I wonder if older *slower* processors (like a really old Windows 286 system!)
> would show more consistent behavior re: the race conditions-- in other words,
> more 'time' to check if there's a king of the hill already present. Or maybe
> there would be more INconsistent behavior-- because the first instance of
> POV-Ray would be loading so slowly? Actually, I would assume that the faster
> the processor(s), the more chance there would be of race conditions showing
> their ugly heads.
Difficult to say.
But I'd certainly expect multi-core systems to be more susceptible than
single-core systems.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 22.01.2018 um 20:11 schrieb Mike Horvath:
> So, something happened to the editor in recent versions.
If by "in recent versions" you mean "somewhere between v3.6.2 and
v3.8.0-alpha", then yeah, that's quite possible.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 22.01.2018 um 21:21 schrieb Kenneth:
> Mike Horvath <mik### [at] gmailcom> wrote:
>
>>
>> This was easy to fix. Simply restart Explorer in Task Manager.
>>
>
> I've never attempted such a thing on a running system; I thought it would
> completely shut down the Windows OS, or something just as bad, leading to...
> chaos! :-O
There was a time indeed when that would have left your system in a state
where you had to know how to start a program (namely the Windows
Explorer) without the Windows Explorer running.
Nowadays, the Windows Explorer is automatically restarted if it ever
crashes or is shut down.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/23/2018 3:36 PM, clipka wrote:
> Am 22.01.2018 um 20:11 schrieb Mike Horvath:
>
>> So, something happened to the editor in recent versions.
>
> If by "in recent versions" you mean "somewhere between v3.6.2 and
> v3.8.0-alpha", then yeah, that's quite possible.
>
Maybe POV-Ray exhibited the proper behavior on my Windows 10 machine...
because it is a virtual machine running in VMWare with fewer CPU cores
than my physical machine. Dunno.
Mike
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
