Hello,

I'm trying to run Gilles's library_new.pov file and it's generating
an access violation exception.  I changed the path for the fonts
file to WINNT and changed all the font calls to Arial, since I didn't
have some of the others he used.  I also checked access privileges
on the fonts and they are read-only, but surely that's good enough.

Any help would be appreciated.

Thanks, miker

Post a reply to this message

ZSpider  wrote
> I'm trying to run Gilles's library_new.pov file and it's generating
> an access violation exception.  I changed the path for the fonts
> file to WINNT and changed all the font calls to Arial, since I didn't
> have some of the others he used.  I also checked access privileges
> on the fonts and they are read-only, but surely that's good enough.

***********
I have some more information on the above.  For one, I found that
after I got one access violation, absolutely nothing would run, and,
like it suggested but I at first ignored, I had to shut it down and
restart it to get back to square one.

I found another mistake I was making.  I had gone through all the
make files and searched for *.ttf and replaced it with Arial so that
it wouldn't snag on any of the ones I didn't have.  But I believe that
Gilles (that sneaky devil) put a random call in to the fonts.txt file,
so I slashed the font.txt file down to one single line:

"C:\winnt\fonts\arial.ttf"

It still won't fly.  I get an error called out in the little blue message
window and then an access violation popup.  When I click OK on
the popup, the error in the message window disappears.  Here is
what it says before it disappears:

File:  fonts.txt   Line:  1
#while (defined(fFonts))
                 #read(fFonts,dummy"c:winnt\fonts\arial.ttf"  <----ERROR
Parse Error:  Illegal sequence in string.

Does that throw up any red flags to where somebody can see what
my problem is?

Thanks again, miker

Post a reply to this message

ZSpider wrote:

> File:  fonts.txt   Line:  1
> #while (defined(fFonts))
>                  #read(fFonts,dummy"c:winnt\fonts\arial.ttf"  <----ERROR
> Parse Error:  Illegal sequence in string.



Unless it's just a typo, there is a backslash missing after "c:".

Another possiblity is that you are using ver 3.5 with the read/write 
restrictions turned on. Check the settings under "Options->Script I/O 
restrictions->"

/Ib

Post a reply to this message

ZSpider wrote:

> File:  fonts.txt   Line:  1
> #while (defined(fFonts))
>                  #read(fFonts,dummy"c:winnt\fonts\arial.ttf"  <----ERROR
> Parse Error:  Illegal sequence in string.
> 
> Does that throw up any red flags to where somebody can see what
> my problem is?

If that is a direct copy and paste from your scene file you are missing
a "\" after c:

If so change it to - #read(fFonts,dummy"c:\winnt\fonts\arial.ttf"

-- 
Ken Tyler

Post a reply to this message

In article <3e0f1a35$1@news.povray.org> , "ZSpider" <zsp### [at] gtenet> wrote:

> File:  fonts.txt   Line:  1
> #while (defined(fFonts))
>                  #read(fFonts,dummy"c:winnt\fonts\arial.ttf"  <----ERROR
> Parse Error:  Illegal sequence in string.

It does not say "Illegal sequence in string." but "Illegal escape sequence
in string.".  And this should tell you want is wrong by checking the manual:
The backslash is a reserved character and you have to type "\\".  Of course,
the proper solution would be to add "c:\winnt\fonts\" to your include
paths...

> Does that throw up any red flags to where somebody can see what
> my problem is?

Yes, apparently when printing the error message something in POV-Ray is
trying to interpret your illegal escape sequence and gets confused.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message

Thanks, Ib, Ken, and Thorsten.  I'm going to make the changes today
and see if I can get it rolling.  I've been rerunning all my old stuff
through 3.5 and cleaning it up.  Mostly lack of semicolons at the end
of declares, but a couple orthographic camera shots, and a few ^ for
exponents.  Looks like I'm going to have to have to dig deeper into
the syntax for those.  I tried doing a global replacement of ^ with e,
but once I thought about it I realized that if that's on the end of a
variable it's going to tack the darn e on it instead of knowing it was
a ^.  Haha.  What an idiot.

Oh, and Ken!  Thanks for the hint on the image map rotation.  I got
it working pretty nicely.  A little "artifacting," I believe it's called,
but overall it looks pretty nice.

miker

Post a reply to this message