 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm posting this in this group because I don't think it is a bug.
I had a crash of the editor when trying to change an inc file made with
PoseRay. The editore claimed "access violation in codemax.dll" and then
"access violation in ntdll.dll". I checked the PoseRay file with another
editor and something was messed up with it indeed.
After the crash restarted POV-Ray, had to fix a few things in the editor
preferences but was unable to reset my custom color scheme. I have selected
POV-Ray as language scope and I have selected the custom color scheme with
my colors. I'm running POV-Ray 3.6 on a WinXP home edition PC with SP2
installed. One more thing: if there is a syntax error, the line with the
error is still highlighted in yellow but all the rest is just black and
white. It doesn't show colored keywords, numbers, strings, etc. The render
engine and message window still work fine.
Any hints?
Best regards, Christoph
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gerberc nous apporta ses lumieres en ce 19-01-2007 03:27:
> I'm posting this in this group because I don't think it is a bug.
> I had a crash of the editor when trying to change an inc file made with
> PoseRay. The editore claimed "access violation in codemax.dll" and then
> "access violation in ntdll.dll". I checked the PoseRay file with another
> editor and something was messed up with it indeed.
> After the crash restarted POV-Ray, had to fix a few things in the editor
> preferences but was unable to reset my custom color scheme. I have selected
> POV-Ray as language scope and I have selected the custom color scheme with
> my colors. I'm running POV-Ray 3.6 on a WinXP home edition PC with SP2
> installed. One more thing: if there is a syntax error, the line with the
> error is still highlighted in yellow but all the rest is just black and
> white. It doesn't show colored keywords, numbers, strings, etc. The render
> engine and message window still work fine.
> Any hints?
> Best regards, Christoph
Maybe the crash corrupted some INI files.
Look for "pvengine.ini" in the \ini filder and "povray.ini" in the \renderer folder.
Open them in notepad or your favorite text editor. Loof if there is something
strange in them.
Try clearing the \rerun folder.
If all else fails, try reinstalling POV-Ray. This won't affect any file you
created, but will reset any distribution file that you may have edited to
default state.
--
Alain
-------------------------------------------------
Educate and inform the whole mass of the people... They are the only sure
reliance for the preservation of our liberty.
Thomas Jefferson
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I cleared the rerun directory and reinstalled POV-Ray. Still the same.
Strange ...
Thanks for the answer anyway.
Christoph
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
You might want to check your script permisions.
Options>Script I/O restrictions>etc
It sounds like something in one of your ini files
is trying to read from a directory that is restricted.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gerberc wrote:
> I'm posting this in this group because I don't think it is a bug.
>
> I had a crash of the editor when trying to change an inc file made with
> PoseRay. The editore claimed "access violation in codemax.dll" and then
> "access violation in ntdll.dll". I checked the PoseRay file with another
> editor and something was messed up with it indeed.
>
> After the crash restarted POV-Ray, had to fix a few things in the editor
> preferences but was unable to reset my custom color scheme. I have selected
> POV-Ray as language scope and I have selected the custom color scheme with
> my colors. I'm running POV-Ray 3.6 on a WinXP home edition PC with SP2
> installed. One more thing: if there is a syntax error, the line with the
> error is still highlighted in yellow but all the rest is just black and
> white. It doesn't show colored keywords, numbers, strings, etc. The render
> engine and message window still work fine.
>
> Any hints?
Editor schemes are stored in the registry.
Check HKCU\Software\POV-Ray\v3.6\POV-Edit\.
Please export the entire POV-Ray registry tree (both HKCU and HKLM) before
changing it. If changing any of the above fixes the problem please email me
the exported registry entries (zipped up) so I can attempt to replicate the
problem.
thanks,
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dear Chris
Thank you very much. I just sent you the registry trees by email. Hopefully
I got the right address. If not please tell me.
One more thing about the error: I can change the color scheme from black on
white to white on black and back but not to the custom color scheme. May be
that helps. Unfortunately I have no idea how the Windows registry works and
therefore I'm afraid to make changes ...
Best regards, Christoph
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
gerberc nous apporta ses lumieres en ce 20-01-2007 05:13:
> Dear Chris
> Thank you very much. I just sent you the registry trees by email. Hopefully
> I got the right address. If not please tell me.
> One more thing about the error: I can change the color scheme from black on
> white to white on black and back but not to the custom color scheme. May be
> that helps. Unfortunately I have no idea how the Windows registry works and
> therefore I'm afraid to make changes ...
> Best regards, Christoph
If you are afraid about editing your registry, DON'T change anything unless you
have precise instructions.
BEFORE changing anything, create a restore point! That way, if you screw up, you
can go back to the way it was before.
Export any key you are about to change. If you make a mistake, simply reimport
the .REG file created by the export to undo your changes.
--
Alain
-------------------------------------------------
"Sure, everyone's in favor of saving Hitler's brain, but when you put it into
the body of a great white shark, suddenly you're a madman."
--Futurama
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
If this is a registry problem, then uninstall
POV, then run a registry cleaner like CCleaner
http://www.ccleaner.com/
Back up any changes from within CCleaner,
and go ahead and have it look for problems.
Anything that is "file not found", or "class not
found", etc. is OK to remove in my experience.
Then go ahead and re-install POV.
It's not uncommon to have hundreds of broken
registry entries. Every time windows goes and
looks for a file that isn't there it slows down
the system, especially at boot up.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thank you very much for the link to CCleaner. I did exactly as you said and
CCleaner fixed more than 250 broken registry entries. Unfortunately the
problem with the POV-Ray editor remained. So I assume the crash of the
editor corruped something that is not directly linked to POV-Ray.
Best regards, Christoph
"Tim Attwood" <tim### [at] comcast net> wrote:
> If this is a registry problem, then uninstall
> POV, then run a registry cleaner like CCleaner
> http://www.ccleaner.com/
> Back up any changes from within CCleaner,
> and go ahead and have it look for problems.
> Anything that is "file not found", or "class not
> found", etc. is OK to remove in my experience.
> Then go ahead and re-install POV.
>
> It's not uncommon to have hundreds of broken
> registry entries. Every time windows goes and
> looks for a file that isn't there it slows down
> the system, especially at boot up.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
