Hello all
I just started using beamer on Texmaker. I have all necessary packages installed via. Tex Live. The configuration for quick build is pfdlatex and then view pdf.
Every time I try running it, I run into the following problem
"! I can't write on file `new.snm'.
<to be read again>
\relax
l.17 \end{document}"
My .tex file is named "new.tex"
Any suggestions?
General ⇒ I can't write into filename.snm problem
-
- Posts: 4
- Joined: Fri Apr 10, 2009 11:26 pm
NEW: TikZ book now 40% off at Amazon.com for a short time.

-
- Posts: 4
- Joined: Fri Apr 10, 2009 11:26 pm
Re: I can't write into filename.snm problem
I hope my question is clear enough for the experts to post an answer.
I eventually figured a workaround out. I go to the command line and do "pdtlatex new.tex" and when it gives me the same error, I provide another file name, weirdly if I just type "new" without any extension, it works, but if I type in say, "somethingelse.snm", it doesn't work.
Unfortunately, everytime this happens, inasmuch as I get a new.pdf file that holds the presentation, the new.tex file is corrupted. So I have to manually copy it elsewhere before every compile.
Any help is much appreciated.
! I can't write on file `new.snm'.
<to be read again>
\relax
l.278 \end{document}
(Press Enter to retry, or Control-Z to exit; default file extension is `.tex')
Please type another output file name: new
(./new.aux)
LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.
){c:/Program Files/texlive/2008/texmf-dist/fonts/enc/dvips/base/8r.enc}<c:/Pro
gram Files/texlive/2008/texmf-dist/fonts/type1/urw/courier/ucrr8a.pfb><c:/Progr
am Files/texlive/2008/texmf-dist/fonts/type1/urw/helvetic/uhvr8a.pfb><c:/Progra
m Files/texlive/2008/texmf-dist/fonts/type1/urw/helvetic/uhvro8a.pfb>
Output written on new.pdf (23 pages, 169578 bytes).
Transcript written on new.log.
C:\Documents and Settings\Desktop\Presentations\new>
I eventually figured a workaround out. I go to the command line and do "pdtlatex new.tex" and when it gives me the same error, I provide another file name, weirdly if I just type "new" without any extension, it works, but if I type in say, "somethingelse.snm", it doesn't work.
Unfortunately, everytime this happens, inasmuch as I get a new.pdf file that holds the presentation, the new.tex file is corrupted. So I have to manually copy it elsewhere before every compile.
Any help is much appreciated.
! I can't write on file `new.snm'.
<to be read again>
\relax
l.278 \end{document}
(Press Enter to retry, or Control-Z to exit; default file extension is `.tex')
Please type another output file name: new
(./new.aux)
LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right.
){c:/Program Files/texlive/2008/texmf-dist/fonts/enc/dvips/base/8r.enc}<c:/Pro
gram Files/texlive/2008/texmf-dist/fonts/type1/urw/courier/ucrr8a.pfb><c:/Progr
am Files/texlive/2008/texmf-dist/fonts/type1/urw/helvetic/uhvr8a.pfb><c:/Progra
m Files/texlive/2008/texmf-dist/fonts/type1/urw/helvetic/uhvro8a.pfb>
Output written on new.pdf (23 pages, 169578 bytes).
Transcript written on new.log.
C:\Documents and Settings\Desktop\Presentations\new>
-
- Posts: 4
- Joined: Fri Apr 10, 2009 11:26 pm
Re: I can't write into filename.snm problem
any thoughts guys?
-
- Site Moderator
- Posts: 814
- Joined: Tue Jul 01, 2008 2:19 pm
Re: I can't write into filename.snm problem
Something is opening the .snm file and locking it. You see the same thing if you open a PDF with Acrobat then try runnning PDFLaTeX on the source .tex file: TeX complains. Alternatively, you might have marked the file read-only somehow. Have you tried deleting all of the auxilliary files before compiling?
Joseph Wright
-
- Posts: 4
- Joined: Fri Apr 10, 2009 11:26 pm
Re: I can't write into filename.snm problem
Thanks Joseph. Yeah I have seen the .pdf problem before, which was trivially solved by making sure the .pdf file wasn't open. Weirldy, there IS no .snm file that I can see before compile. I have tried deleting all the files.
I am still generating outputs(very painfully) using the workaround I mentioned in post #2.
I am still generating outputs(very painfully) using the workaround I mentioned in post #2.