 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Kenneth" <kdw### [at] gmail com> wrote:
> "omniverse" <omn### [at] charternet> wrote:
> >
> > Attention please!
> [snip]
> > The file open/save (as) caused Windows 10 to force a close of the program. Acts
> > like it isn't able to determine the correct folder/file location to use.
> >
> > And unfortunately, for me, uninstalling all versions and reinstalling 3.7.0
> > again has yet to fix the problem.
>
> Sorry to hear that you're having such troubles. I guess you've already tried
> shutting down the machine and restarting? That seems to help somewhat with
> strange glitches, at least on my Win7 box. Sounds like a registry problem (if
> Win10 even has a registry now!)
>
> The only problem I've ever seen with POV-Ray (in my own similar alpha/beta
> install screwups) is a mis-loaded 'resolution INI' file; but that was easily
> fixed.
Thanks for the sentiment, and I can't report a successful fix yet. Other than to
say it's apparently only affecting the pvengine64.exe while the
pvengine32-sse2.exe is okay.
I went into the registry editor to look around and found a curious thing, no
..pov listed among all the other file types. Although there is the .inc file type
there, it says inc_auto_file within it, and once finding that particular item it
has a pointer (shell, command, open) to "pvengine64.exe" "%1"
Risk taker that I am I duplicated the .inc to make a new .pov and whatever
happened wasn't a fix, but it might have allowed POV-Ray to list folder contents
when I tried to Open a file before once again freezing and forcing another close
of the program.
All this after a couple variations on uninstalls and reinstalls of only version
3.7.0.0.
I'm fairly sure something got mixed up in the Windows registry that makes
pvengine.exe choke on the folder/file system.
Probably my fault for putting everything from version 3.1g to 3.8 on here, beta
and rc 3.7.1 and unofficial stuff too.
Another thing I need to check is a user account which also uses 3.7.0.0
pvengine64.exe but not the others.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 28.09.2017 um 07:18 schrieb omniverse:
> I went into the registry editor to look around and found a curious thing, no
> ...pov listed among all the other file types. Although there is the .inc file type
> there, it says inc_auto_file within it, and once finding that particular item it
> has a pointer (shell, command, open) to "pvengine64.exe" "%1"
Normally, you should find something like the following (HKCR =
Computer\HKEY_CLASSES_ROOT, D:\POV-Ray = C:\Program Files\POV-Ray):
HKCR\.pov
(default) POV-Ray.Scene
PerceivedType text
HKCR\POV-Ray.Scene
(default) POV-Ray scene source file
HKCR\POV-Ray.Scene\DefaultIcon
(default) D:\POV-Ray\v3.7\bin\POV-Ray.Scene-XP.ico
HKCR\POV-Ray.Scene\shell\Open
(default) Edit in POV-Ray 3.7
HKCR\POV-Ray.Scene\shell\Open\command
(default) "D:\POV-Ray\v3.7\bin\pvengine64.exe" /edit "%1"
HKCR\POV-Ray.Scene\shell\Render
(default) Render with POV-Ray 3.7
HKCR\POV-Ray.Scene\shell\Render\command
(default) "D:\POV-Ray\v3.7\bin\pvengine64.exe" /render "%1"
(typically along with one entry per key named "backup")
Besides that, you should also have the following keys, each with lots of
stuff in them (HKCU = Computer\HKEY_CURRENT_USER):
HKCU\Software\POV-Ray\v3.7\Components
HKCU\Software\POV-Ray\v3.7\POV-Edit
HKCU\Software\POV-Ray\v3.7\POV-Edit\Macro
HKCU\Software\POV-Ray\v3.7\POV-Edit\Older
HKCU\Software\POV-Ray\v3.7\POV-Edit\Open
HKCU\Software\POV-Ray\v3.7\POV-Edit\Recent
HKCU\Software\POV-Ray\v3.7\Windows
If you don't see those keys, shout out loud.
You might also want to have a close look at the following entry:
HKCU\Software\POV-Ray\v3.7\POV-Edit
InitialDir
That's where POV-Ray (more specifically, POV-Ray's editor DLL) seems to
get the initial directory for the "open file" dialog. If that registry
entry is broken, that might explain your symptoms.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
Thanks for the help! Haven't fixed it by checking what you listed, only found
one thing not the same.
> Normally, you should find something like the following (HKCR =
> Computer\HKEY_CLASSES_ROOT, D:\POV-Ray = C:\Program Files\POV-Ray):
>
> HKCR\.pov
> (default) POV-Ray.Scene
> PerceivedType text
>
> HKCR\POV-Ray.Scene
> (default) POV-Ray scene source file
>
> HKCR\POV-Ray.Scene\DefaultIcon
> (default) D:\POV-Ray\v3.7\bin\POV-Ray.Scene-XP.ico
>
> HKCR\POV-Ray.Scene\shell\Open
> (default) Edit in POV-Ray 3.7
>
> HKCR\POV-Ray.Scene\shell\Open\command
> (default) "D:\POV-Ray\v3.7\bin\pvengine64.exe" /edit "%1"
>
> HKCR\POV-Ray.Scene\shell\Render
That said "edit" not render, other parts within were right.
> (default) Render with POV-Ray 3.7
>
> HKCR\POV-Ray.Scene\shell\Render\command
> (default) "D:\POV-Ray\v3.7\bin\pvengine64.exe" /render "%1"
>
> (typically along with one entry per key named "backup")
>
>
> Besides that, you should also have the following keys, each with lots of
> stuff in them (HKCU = Computer\HKEY_CURRENT_USER):
>
> HKCU\Software\POV-Ray\v3.7\Components
> HKCU\Software\POV-Ray\v3.7\POV-Edit
> HKCU\Software\POV-Ray\v3.7\POV-Edit\Macro
> HKCU\Software\POV-Ray\v3.7\POV-Edit\Older
> HKCU\Software\POV-Ray\v3.7\POV-Edit\Open
> HKCU\Software\POV-Ray\v3.7\POV-Edit\Recent
> HKCU\Software\POV-Ray\v3.7\Windows
All there but I removed references to versions 3.5, 3.6 and 3.7.1 beta.
> You might also want to have a close look at the following entry:
>
> HKCU\Software\POV-Ray\v3.7\POV-Edit
> InitialDir
>
> That's where POV-Ray (more specifically, POV-Ray's editor DLL) seems to
> get the initial directory for the "open file" dialog. If that registry
> entry is broken, that might explain your symptoms.
When reading this I thought that was going to be the answer. It wasn't.
Once again, I have the file open box showing the folder/file list but no buttons
or finishing of that box. It wasn't doing that much before I attempted to get
that missing HKCR/.pov into the registry, which I found was put right after I
removed it.
The broken Open file box is there several moments before Windows puts up the
close program message. Must be something else the 64-bit POV-Ray is expecting to
find.
I've already looked at pvengine.ini in the Documents POV-Ray ini folder and it
has the right things there, based on previous backup save of that.
I think next step would be to try a Restore Point and go back to an earlier time
when things were okay, so I'm going to give that a look. I'm not sure about
getting back to before 3.5, 3.6 and 3.7.1 beta were installed. I wonder how much
3.5 caused trouble, since it refused to render a while ago and I ignored it.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 28.09.2017 um 21:10 schrieb omniverse:
> Once again, I have the file open box showing the folder/file list but no buttons
> or finishing of that box. It wasn't doing that much before I attempted to get
> that missing HKCR/.pov into the registry, which I found was put right after I
> removed it.
>
> The broken Open file box is there several moments before Windows puts up the
> close program message. Must be something else the 64-bit POV-Ray is expecting to
> find.
Strictly speaking, it's not POV-Ray itself (pvengine.exe) that's dealing
with the Open file dialog, but the editor DLLs (more specifically,
cmedit*.dll). Maybe you want to investigate in that direction (e.g.
uninstalling and re-installing the editor DLLs).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 28.09.2017 um 21:10 schrieb omniverse:
>
> > Once again, I have the file open box showing the folder/file list but no buttons
> > or finishing of that box. It wasn't doing that much before I attempted to get
> > that missing HKCR/.pov into the registry, which I found was put right after I
> > removed it.
> >
> > The broken Open file box is there several moments before Windows puts up the
> > close program message. Must be something else the 64-bit POV-Ray is expecting to
> > find.
>
> Strictly speaking, it's not POV-Ray itself (pvengine.exe) that's dealing
> with the Open file dialog, but the editor DLLs (more specifically,
> cmedit*.dll). Maybe you want to investigate in that direction (e.g.
> uninstalling and re-installing the editor DLLs).
Only did the editor re-installs along with 3.7.0.0 install after everything was
uninstalled. No change there anyhow.
I may have jumped the gun on finding the actual problem because I just did the
restore point to what was good a week ago and that fixed it. Or has for now.
Took a look at the redone registry and found a surprise. Or at least didn't
notice, or mixed myself up about it.
Under HKCR there isn't a POV-Ray listed there, although the .pov and all else
within it is okay. Instead there's a povfile key, with the associated shell
commands.
Can't investigate more, I'm going out my door for the evening and late already!
Typical for me.
Hope to shed more light on this later. Thanks for the registry info!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 17-09-28 à 16:44, omniverse a écrit :
>
> Only did the editor re-installs along with 3.7.0.0 install after everything was
> uninstalled. No change there anyhow.
>
> I may have jumped the gun on finding the actual problem because I just did the
> restore point to what was good a week ago and that fixed it. Or has for now.
>
> Took a look at the redone registry and found a surprise. Or at least didn't
> notice, or mixed myself up about it.
> Under HKCR there isn't a POV-Ray listed there, although the .pov and all else
> within it is okay. Instead there's a povfile key, with the associated shell
> commands.
>
> Can't investigate more, I'm going out my door for the evening and late already!
> Typical for me.
>
> Hope to shed more light on this later. Thanks for the registry info!
>
>
Maybe you got a broken download.
I would clear my browser cache, then get a new download to reinstall
everything. Don't know if you did just that, but probably worth trying.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alain <kua### [at] videotronca> wrote:
>
> Maybe you got a broken download.
Well, this seemed to be after trying the 3.8 alpha v499 and I'm not going to try
that again yet. I don't think it began with the first alpha.
Something probably going on with the Windows Registry entries, even before that,
due to my installing so many versions of POV-Ray. Somehow able to run the
different version okay, except v3.5 and maybe MegaPOV. I considered them shelved
for the time being until I could find a fix (MegaPOV renders okay again, too,
while v3.5 remains uninstalled).
To recap on that again, as Clipka said, there should be a POV-Ray.Scene key in
the HKCR section (not just within the .pov key), and all I have in HKCR is .pov
and povfile which is a result of version 3.6 installation (or so it seems).
Strange to me that version 3.7.0.0 is okay this way after the restore point from
last week. But then, nothing was wrong until 3.8 alpha.
And now I've found a key in the registry that contains both povfile and
POV-Ray.Scene, yet both have _.pov appended to them at:
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\ApplicationAssociationToasts
Another mention of those without the _.pov at:
Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pov\OpenWithProgids
Needless to say I'm good at making a mess of things even without potential
program bugs!
I'm considering going the route of uninstalling 3.6, 3.7.1-beta9, 3.7.1-rc and
3.7.0.0 (because I put it into renamed folder 3.70) then just installing 3.7.0.0
again.
Does any of this help explain what might have happened?
Could pvengine64.exe of 3.8 alpha alone do anything to cause this?
Or would the editor need a reinstall simply from putting 3.8 alpha in? Makes no
sense to me anyway.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 29.09.2017 um 06:34 schrieb omniverse:
> To recap on that again, as Clipka said, there should be a POV-Ray.Scene key in
> the HKCR section (not just within the .pov key), and all I have in HKCR is .pov
> and povfile which is a result of version 3.6 installation (or so it seems).
There's nothing wrong with that: POV-Ray 3.6 and earlier registered the
`.pov` file type as `povfile`, while POV-Ray 3.7 and later renamed that
to `POV-Ray.Scene`. Different monikers, same mechanism.
> Does any of this help explain what might have happened?
>
> Could pvengine64.exe of 3.8 alpha alone do anything to cause this?
> Or would the editor need a reinstall simply from putting 3.8 alpha in? Makes no
> sense to me anyway.
Makes no sense to me either.
If you run into the issue again, please let us know.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 29.09.2017 um 06:34 schrieb omniverse:
>
> There's nothing wrong with that: POV-Ray 3.6 and earlier registered the
> `.pov` file type as `povfile`, while POV-Ray 3.7 and later renamed that
> to `POV-Ray.Scene`. Different monikers, same mechanism.
Okay, thanks again.
I delayed a while with the uninstall/reinstall of 3.7.0 so I'm just now getting
a look at the Windows Registry.
POV-Ray.Scene is there after that, listed right after povfile. No problems with
file open or save (as). Apparently that's what happened, lost the POV-Ray.Scene
somehow.
Just got me curious about Windows 10 possibly juggling the pov file associations
around to allow the different versions to work together.
If happens again, easily fixed by exporting that POV-Ray.Scene key now and
importing it back into the Registry. If there ever is a next time.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 9/21/2017 3:10 PM, clipka wrote:
> Be advised that this binary-only release wants to reside in an existing
> v3.7.x installation.
nix is working oh-key-dokey fine however doze has an issue ... binary in
v3.7.1 install directory but help buttons for POV-Win and Scene aren't
working
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
