 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
When I try to open any file with POV-Ray for Windows V3.1g, I get
error messages such as these:
POV-Ray Editor - Division by zero
POV-Ray Editor - Access violation at address 012A01FC in module
'CMAX101.DLL'. Read of address FFFFFFFF.
POV-Ray Editor - Access violation at address 012A1670 in module
'CMAX101.DLL'. Read of address FFFFFFFF.
File 'torus1.pov' - Failed to open file: The operation completed
successfully.
Whatever is causing this also affects the Super Patch and the Mini
Patch as well. I have tried uninstalling and reinstalling. I also
tried manually removing every mention of POV from the registry and
win.ini before one of the reinstallations. After several attempts, I
still can't get the problem corrected. Any help is most appreciated.
Thanks,
Glen Berry
To reply via email, remove the "7" from nos### [at] ezwv com
Post a reply to this message
|
|
| |
| |
|
|
From: Nieminen Juha
Subject: Re: Help, I'm having severe editor problems
Date: 5 Oct 1999 04:08:37
Message: <37f9b205@news.povray.org>
|
|
|
| |
| |
|
|
First of all: Is your computer overclocked?
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 5 Oct 1999 04:08:37 -0400, Nieminen Juha <war### [at] cctutfi> wrote:
> First of all: Is your computer overclocked?
No, just a normal Pentium 133.
My other software seems to work okay, but recently POV quite working.
I don't know if perhaps I installed something that screwed up a
windows dll or perhaps one of the recent power failures messed up
something, I just don't know what is causing this.
To reply via email, remove the "7" from nos### [at] ezwvcom
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Glen Berry wrote:
>
> On 5 Oct 1999 04:08:37 -0400, Nieminen Juha <war### [at] cctutfi> wrote:
>
> > First of all: Is your computer overclocked?
>
> No, just a normal Pentium 133.
>
> My other software seems to work okay, but recently POV quite working.
> I don't know if perhaps I installed something that screwed up a
> windows dll or perhaps one of the recent power failures messed up
> something, I just don't know what is causing this.
I was plagued by this problem with POV-Win 3.1d but with POV-Win 3.1g
a new editor .dll file was introduced that was supposed to fix this
problem. This is the first report I have seen with this error since
the revised edition came out. Are you sure you are using the right
version of codemax cmax101.dll ?
Got bad ram at that address ?
--
Ken Tyler
1100+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Tue, 05 Oct 1999 01:29:41 -0700, Ken <tyl### [at] pacbellnet> wrote:
>I was plagued by this problem with POV-Win 3.1d but with POV-Win 3.1g
>a new editor .dll file was introduced that was supposed to fix this
>problem. This is the first report I have seen with this error since
>the revised edition came out. Are you sure you are using the right
>version of codemax cmax101.dll ?
It's the one that came with POV 3.1g, so it should be the proper one.
I did a search of my entire system for any other copies and couldn't
find any.
>Got bad ram at that address ?
I hope not, but I'm not sure how to rule that out. Like I said, my
other software seems to be working okay, so I'm hoping that it isn't
something like bad RAM.
For what it's worth, I *can* render files with POV, but I can't open
them in the internal editor. It's a bit awkward after being used to
using the internal editor.
To reply via email, remove the "7" from nos### [at] ezwvcom
Post a reply to this message
|
|
| |
| |
|
|
From: Ron Parker
Subject: Re: Help, I'm having severe editor problems
Date: 5 Oct 1999 09:15:49
Message: <37f9fa05@news.povray.org>
|
|
|
| |
| |
|
|
On Tue, 05 Oct 1999 07:12:50 -0400, Glen Berry wrote:
>On Tue, 05 Oct 1999 01:29:41 -0700, Ken <tyl### [at] pacbellnet> wrote:
>>Got bad ram at that address ?
>
>I hope not, but I'm not sure how to rule that out. Like I said, my
>other software seems to be working okay, so I'm hoping that it isn't
>something like bad RAM.
Not likely. It's not an address that would normally be used for anything.
It's being accessed because there's a bad pointer somewhere. In any case,
virtual memory means never being able to relate an address to a physical
piece of memory, so even if it was bad RAM it wouldn't always map to the
same address.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
