hi group,

I know this might should have been posted as a bug report on the proper
group, but I really don't know enough to know if it is a bug or my error.

whenever I open a *.pov file in the povray codemax editor, edit a few lines,
save the file, and then click on the run button, I get the following GFP
error:
PVENGINE caused an invalid page fault in
module PVENGINE.EXE at 015f:00420413.
Registers:
EAX=00799940 CS=015f EIP=00420413 EFLGS=00010202
EBX=00000314 SS=0167 ESP=01a5fbf4 EBP=00000000
ECX=2a2a2a2a DS=0167 ESI=00000000 FS=0faf
EDX=424f2020 ES=0167 EDI=00000000 GS=0000
Bytes at CS:EIP:
89 51 0c eb dc 8b 46 0c a3 e8 18 4d 00 5e 5a 59
Stack dump:
00000000 00799940 00799958 00000314 00420229 00000000 004388b6 00000000
00000000 00000081 0000000c 0000007e 00000000 0041d58e 00000000 0000006e


after this happens the only way I can prevent it from happening again is to
re-boot, then select/ run the file. further editing after rebooting does not
cause another error, unless I edit the file in Moray again.

Why is this happening?

Moray win 3.1build 4325, not sure what version POV and don't know how to
find out.

Post a reply to this message

I think its a video card problem...you may have an ATI card at 16 bit? If
so, put it on 32 bit color.

Steven Durham <ste### [at] earthlinknet> wrote in message
news:37bb2804@news.povray.org...
> hi group,
>
> I know this might should have been posted as a bug report on the proper
> group, but I really don't know enough to know if it is a bug or my error.
>
> whenever I open a *.pov file in the povray codemax editor, edit a few
lines,
> save the file, and then click on the run button, I get the following GFP
> error:
> PVENGINE caused an invalid page fault in
> module PVENGINE.EXE at 015f:00420413.
> Registers:
> EAX=00799940 CS=015f EIP=00420413 EFLGS=00010202
> EBX=00000314 SS=0167 ESP=01a5fbf4 EBP=00000000
> ECX=2a2a2a2a DS=0167 ESI=00000000 FS=0faf
> EDX=424f2020 ES=0167 EDI=00000000 GS=0000
> Bytes at CS:EIP:
> 89 51 0c eb dc 8b 46 0c a3 e8 18 4d 00 5e 5a 59
> Stack dump:
> 00000000 00799940 00799958 00000314 00420229 00000000 004388b6 00000000
> 00000000 00000081 0000000c 0000007e 00000000 0041d58e 00000000 0000006e
>
>
> after this happens the only way I can prevent it from happening again is
to
> re-boot, then select/ run the file. further editing after rebooting does
not
> cause another error, unless I edit the file in Moray again.
>
> Why is this happening?
>
> Moray win 3.1build 4325, not sure what version POV and don't know how to
> find out.
>
>

Post a reply to this message

ATI all in wonder pro at 32 bit color now, thanks
srmac <srm### [at] bellsouthnet> wrote in message
news:37bb2cab@news.povray.org...
> I think its a video card problem...you may have an ATI card at 16 bit? If
> so, put it on 32 bit color.
>
> Steven Durham <ste### [at] earthlinknet> wrote in message
> news:37bb2804@news.povray.org...
> > hi group,
> >
> > I know this might should have been posted as a bug report on the proper
> > group, but I really don't know enough to know if it is a bug or my
error.
> >
> > whenever I open a *.pov file in the povray codemax editor, edit a few
> lines,
> > save the file, and then click on the run button, I get the following GFP
> > error:
> > PVENGINE caused an invalid page fault in
> > module PVENGINE.EXE at 015f:00420413.
> > Registers:
> > EAX=00799940 CS=015f EIP=00420413 EFLGS=00010202
> > EBX=00000314 SS=0167 ESP=01a5fbf4 EBP=00000000
> > ECX=2a2a2a2a DS=0167 ESI=00000000 FS=0faf
> > EDX=424f2020 ES=0167 EDI=00000000 GS=0000
> > Bytes at CS:EIP:
> > 89 51 0c eb dc 8b 46 0c a3 e8 18 4d 00 5e 5a 59
> > Stack dump:
> > 00000000 00799940 00799958 00000314 00420229 00000000 004388b6 00000000
> > 00000000 00000081 0000000c 0000007e 00000000 0041d58e 00000000 0000006e
> >
> >
> > after this happens the only way I can prevent it from happening again is
> to
> > re-boot, then select/ run the file. further editing after rebooting does
> not
> > cause another error, unless I edit the file in Moray again.
> >
> > Why is this happening?
> >
> > Moray win 3.1build 4325, not sure what version POV and don't know how to
> > find out.
> >
> >
>
>

Post a reply to this message

Weird.  When I had a *hack* Rage Pro (same chipset as the All in Wonder
Pro), it worked in 16-bit OR 32-bit.  I used 1152x864x16 for modeling and
tracing, because 800x600x32 was the highest res I could go on in 32 bit
color (I only had 2MB video mem).

Now, however, I'm VERY happy with my Rage Fury (Rage 128 chipset) that can
go 1280x1024 in any res.  Now I need a new monitor to go even higher!
hehehehehehehe

-Ian

Steven Durham <ste### [at] earthlinknet> wrote in message
news:37bc163f@news.povray.org...
> ATI all in wonder pro at 32 bit color now, thanks
> srmac <srm### [at] bellsouthnet> wrote in message
> news:37bb2cab@news.povray.org...
> > I think its a video card problem...you may have an ATI card at 16 bit?
If
> > so, put it on 32 bit color.
> >
> > Steven Durham <ste### [at] earthlinknet> wrote in message
> > news:37bb2804@news.povray.org...
> > > hi group,
> > >
> > > I know this might should have been posted as a bug report on the
proper
> > > group, but I really don't know enough to know if it is a bug or my
> error.
> > >
> > > whenever I open a *.pov file in the povray codemax editor, edit a few
> > lines,
> > > save the file, and then click on the run button, I get the following
GFP
> > > error:
> > > PVENGINE caused an invalid page fault in
> > > module PVENGINE.EXE at 015f:00420413.
> > > Registers:
> > > EAX=00799940 CS=015f EIP=00420413 EFLGS=00010202
> > > EBX=00000314 SS=0167 ESP=01a5fbf4 EBP=00000000
> > > ECX=2a2a2a2a DS=0167 ESI=00000000 FS=0faf
> > > EDX=424f2020 ES=0167 EDI=00000000 GS=0000
> > > Bytes at CS:EIP:
> > > 89 51 0c eb dc 8b 46 0c a3 e8 18 4d 00 5e 5a 59
> > > Stack dump:
> > > 00000000 00799940 00799958 00000314 00420229 00000000 004388b6
00000000
> > > 00000000 00000081 0000000c 0000007e 00000000 0041d58e 00000000
0000006e
> > >
> > >
> > > after this happens the only way I can prevent it from happening again
is
> > to
> > > re-boot, then select/ run the file. further editing after rebooting
does
> > not
> > > cause another error, unless I edit the file in Moray again.
> > >
> > > Why is this happening?
> > >
> > > Moray win 3.1build 4325, not sure what version POV and don't know how
to
> > > find out.
> > >
> > >
> >
> >
>
>

Post a reply to this message