Texmaker (Windows version) - first use - Error: Log file not found!Latex Error “log file not found”Error...
Why is that max-Q doesn't occur in transonic regime?
How much mayhem could I cause as a fish?
Categorical Unification of Jordan Holder Theorems
How vim overwrites readonly mode?
Which RAF squadrons and aircraft types took part in the bombing of Berlin on the 25th of August 1940?
How are the system health extended events files rolling over?
Broad Strokes - missing letter riddle
How to not let the Identify spell spoil everything?
Non-Cancer terminal illness that can affect young (age 10-13) girls?
The No-Straight Maze
Plausible reason for gold-digging ant
Book where a space ship journeys to the center of the galaxy to find all the stars had gone supernova
Why is it that Bernie Sanders is always called a "socialist"?
Custom shape shows unwanted extra line
How do I prevent a homebrew Grappling Hook feature from trivializing Tomb of Annihilation?
Stuck on a Geometry Puzzle
How do you funnel food off a cutting board?
Why didn't Tom Riddle take the presence of Fawkes and the Sorting Hat as more of a threat?
How can I have probability increase linearly with more dice?
Potential client has a problematic employee I can't work with
Find the smallest value of the function
What is the wife of a henpecked husband called?
Critique vs nitpicking
Why do neural networks need so many training examples to perform?
Texmaker (Windows version) - first use - Error: Log file not found!
Latex Error “log file not found”Error : could not start the command : pdflatex -synctex=1 -interaction=nonstopmode “main”.texcannot compile with texmakerWhat are the advantages of TeX Live over MiKTeX?How do I update my TeX distribution?Texmaker-log file not foundTeX Distribution and EngineUnable to compile TeXmaker 4.0.2 with MiKTeX 2.9Error when compiling xcolor.ins in TeXmaker to generate xcolor.sty fileLatex Error “log file not found”Texmaker-log file not found“Log file not found” error with MacTeX and TexmakerTexMaker - “File not found” when selecting section in structure viewChoosing version of MikTex to use in TexMaker?File not found with TexmakerCompiling: Log file not found! LaTeX Error: File `multirow.sty' not foundNo log file in Texmaker after Miktex last update (2.9.6615 version)Problem compiling: Log file not found
This is my first time using a LaTeX editor.
I installed Texmaker allowing it to use the default directory on the C drive.
Software Versions
- Windows: 7 Ultimate 64-bit
- Texmaker 3.4.1 for Windows
I then did A Local guide for using Texmaker (There use to be a link to this but it is now dead)
Basically create a simple Hello World document and save it.
When I went to process the file
Tools -> PDFLaTeX
I received
Error: Log file not found!
What I checked
I checked the configuration (Options -> configure Texmaker) and found no option for log files.
I checked for a log file under the C:Program Files (x86)Texmaker and found none.
I checked for a log path in the Windows registry using regedit and found none.
I checked the Texmaker issues and found Issue 97 but it does not help.
Any ideas?
After reading answer
I installed MiKTeX as an administrator (didn't work as user) and chose the default options. After MiKTeX installed I was able to create a PDF file using Texmaker.
Also, correctly setting the PDF viewer options
Options -> Configure Texmaker -> Commands -> PDF Viewer
Built-in Viewer and Embed
I was able to preview the pdf in Texmaker
View -> PDF Viewer
What I learned
Texmaker is a LaTeX editor which generates a file containing LaTeX markup.
MiKTeX is a program that converts the LaTeX markup into an output format such as PDF.
errors texmaker
add a comment |
This is my first time using a LaTeX editor.
I installed Texmaker allowing it to use the default directory on the C drive.
Software Versions
- Windows: 7 Ultimate 64-bit
- Texmaker 3.4.1 for Windows
I then did A Local guide for using Texmaker (There use to be a link to this but it is now dead)
Basically create a simple Hello World document and save it.
When I went to process the file
Tools -> PDFLaTeX
I received
Error: Log file not found!
What I checked
I checked the configuration (Options -> configure Texmaker) and found no option for log files.
I checked for a log file under the C:Program Files (x86)Texmaker and found none.
I checked for a log path in the Windows registry using regedit and found none.
I checked the Texmaker issues and found Issue 97 but it does not help.
Any ideas?
After reading answer
I installed MiKTeX as an administrator (didn't work as user) and chose the default options. After MiKTeX installed I was able to create a PDF file using Texmaker.
Also, correctly setting the PDF viewer options
Options -> Configure Texmaker -> Commands -> PDF Viewer
Built-in Viewer and Embed
I was able to preview the pdf in Texmaker
View -> PDF Viewer
What I learned
Texmaker is a LaTeX editor which generates a file containing LaTeX markup.
MiKTeX is a program that converts the LaTeX markup into an output format such as PDF.
errors texmaker
@GuyCoder See What are the advantages of TeX Live over MikTeX for some good advice on the choice between the two main distributions for Windows. You really can't go wrong with either one. See also TeX distribution and engine for more info on what a distribution is. See also How do I update my distribution.
– Alan Munn
Jul 19 '12 at 23:59
add a comment |
This is my first time using a LaTeX editor.
I installed Texmaker allowing it to use the default directory on the C drive.
Software Versions
- Windows: 7 Ultimate 64-bit
- Texmaker 3.4.1 for Windows
I then did A Local guide for using Texmaker (There use to be a link to this but it is now dead)
Basically create a simple Hello World document and save it.
When I went to process the file
Tools -> PDFLaTeX
I received
Error: Log file not found!
What I checked
I checked the configuration (Options -> configure Texmaker) and found no option for log files.
I checked for a log file under the C:Program Files (x86)Texmaker and found none.
I checked for a log path in the Windows registry using regedit and found none.
I checked the Texmaker issues and found Issue 97 but it does not help.
Any ideas?
After reading answer
I installed MiKTeX as an administrator (didn't work as user) and chose the default options. After MiKTeX installed I was able to create a PDF file using Texmaker.
Also, correctly setting the PDF viewer options
Options -> Configure Texmaker -> Commands -> PDF Viewer
Built-in Viewer and Embed
I was able to preview the pdf in Texmaker
View -> PDF Viewer
What I learned
Texmaker is a LaTeX editor which generates a file containing LaTeX markup.
MiKTeX is a program that converts the LaTeX markup into an output format such as PDF.
errors texmaker
This is my first time using a LaTeX editor.
I installed Texmaker allowing it to use the default directory on the C drive.
Software Versions
- Windows: 7 Ultimate 64-bit
- Texmaker 3.4.1 for Windows
I then did A Local guide for using Texmaker (There use to be a link to this but it is now dead)
Basically create a simple Hello World document and save it.
When I went to process the file
Tools -> PDFLaTeX
I received
Error: Log file not found!
What I checked
I checked the configuration (Options -> configure Texmaker) and found no option for log files.
I checked for a log file under the C:Program Files (x86)Texmaker and found none.
I checked for a log path in the Windows registry using regedit and found none.
I checked the Texmaker issues and found Issue 97 but it does not help.
Any ideas?
After reading answer
I installed MiKTeX as an administrator (didn't work as user) and chose the default options. After MiKTeX installed I was able to create a PDF file using Texmaker.
Also, correctly setting the PDF viewer options
Options -> Configure Texmaker -> Commands -> PDF Viewer
Built-in Viewer and Embed
I was able to preview the pdf in Texmaker
View -> PDF Viewer
What I learned
Texmaker is a LaTeX editor which generates a file containing LaTeX markup.
MiKTeX is a program that converts the LaTeX markup into an output format such as PDF.
errors texmaker
errors texmaker
edited Oct 4 '17 at 20:57
Guy Coder
asked Jul 19 '12 at 23:24
Guy CoderGuy Coder
288147
288147
@GuyCoder See What are the advantages of TeX Live over MikTeX for some good advice on the choice between the two main distributions for Windows. You really can't go wrong with either one. See also TeX distribution and engine for more info on what a distribution is. See also How do I update my distribution.
– Alan Munn
Jul 19 '12 at 23:59
add a comment |
@GuyCoder See What are the advantages of TeX Live over MikTeX for some good advice on the choice between the two main distributions for Windows. You really can't go wrong with either one. See also TeX distribution and engine for more info on what a distribution is. See also How do I update my distribution.
– Alan Munn
Jul 19 '12 at 23:59
@GuyCoder See What are the advantages of TeX Live over MikTeX for some good advice on the choice between the two main distributions for Windows. You really can't go wrong with either one. See also TeX distribution and engine for more info on what a distribution is. See also How do I update my distribution.
– Alan Munn
Jul 19 '12 at 23:59
@GuyCoder See What are the advantages of TeX Live over MikTeX for some good advice on the choice between the two main distributions for Windows. You really can't go wrong with either one. See also TeX distribution and engine for more info on what a distribution is. See also How do I update my distribution.
– Alan Munn
Jul 19 '12 at 23:59
add a comment |
7 Answers
7
active
oldest
votes
You also need to install a TeX distribution, i.e. MiKTeX or TeX Live. The TeX distribution contains all the machinery needed to process source code and produce typeset documents; Texmaker is just a front end.
Even with MikTex installed, I still get the error. However, I have had success, albeit inconsistently, that running ALL of the updates through the MikTex console resolves the problem. I am guessing there is/are packages that might be contributing to this - even with a bare minimal documentclass begindocument ...
– elika kohen
1 hour ago
add a comment |
It is not enough to just have the TeX distribution installed, it is also necessary to add the MiKTeX bin to the path or else change the commands in the configuration to use the full path to each executable (i.e., if you look at the actual commands being called they are just "latex", "pdflatex", etc. without the path to the executable).
In my case I had MiKTeX installed and working with another editor, but it would not work with TeXMaker - adding the path to the bin to my window Path environment variable resolved the issue for me. For me this path is:
C:Program FilesMiKTeX 2.9miktexbinx64
2
Welcome to TeX.sx! Feel free to visit our TeX.SX starter guide to get the most out of this site.
– Peter Jansson
May 13 '13 at 21:32
add a comment |
If you still get error: Log file not found!, when using Texmaker when you have done everything (installed MiKTex, installed Texmaker, and checked if the binary for MiKTeX is already in your windows environment varible) then simply close the Texmaker and reopen it as an administrator. Right click on the executable for Texmaker and "Run as administrator".
This worked for me!
This does not sound at all safe to me! (Is this safe on Windows? I know Windows is different...)
– cfr
May 17 '14 at 21:41
@cfr - yeah, it is a really bad idea to run programs like this as admin. And, it should be reported as a defect if necessary.
– elika kohen
1 hour ago
add a comment |
It is possible in when using a version of Texmaker based on QT5 that you get this error even with you Tex framework available on the path.
Make sure that the document you are trying to compile has a .tex prefix, it will not work otherwise.
3
Welcome to TeX.SX! You can have a look on our starter guide to familiarize yourself further with our format.
– Claudio Fiandrino
Jul 19 '13 at 18:38
add a comment |
I was using a portable version of miktex with texmaker. Before using the texmaker you need to click on the Miktex box, then a blue box appears at the bottom of your page. Then you can reopen the texmaker and it will work.
add a comment |
This also occurs if you already have an install of MikTex but for some reason it gets broken. As happened to me this morning :S The fix is to simply as MikTex to update. It will then tell you there is a problem as it can't find itself, but offers to fix the problem. Update any files you want to update eh Presto, problem solved.
add a comment |
I found a work-around!
I have had this problem with both TeXStudio and TeXMaker. I have manually updated all kinds of environment variables, uninstalled, reinstalled, and updated every Miktex package, etc.
And yet, I still have the error - which means it's not really either a TexMaker or TexStudio error …
What seems to be working for me, now, is reseting the config, creating a bare minimum document, and then recompiling with the regular latex compiler, and moving through them until I get to XelaTeX and final LuaLateX.
I have no idea why, but I am guessing the plain Latex compiler is doing some initializing stuff that the other compilers I have trouble with, (XeLatex and LUALaTeX are not doing. I call Voodoo.
Hope this helps.
add a comment |
protected by Kurt Oct 21 '15 at 20:55
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
You also need to install a TeX distribution, i.e. MiKTeX or TeX Live. The TeX distribution contains all the machinery needed to process source code and produce typeset documents; Texmaker is just a front end.
Even with MikTex installed, I still get the error. However, I have had success, albeit inconsistently, that running ALL of the updates through the MikTex console resolves the problem. I am guessing there is/are packages that might be contributing to this - even with a bare minimal documentclass begindocument ...
– elika kohen
1 hour ago
add a comment |
You also need to install a TeX distribution, i.e. MiKTeX or TeX Live. The TeX distribution contains all the machinery needed to process source code and produce typeset documents; Texmaker is just a front end.
Even with MikTex installed, I still get the error. However, I have had success, albeit inconsistently, that running ALL of the updates through the MikTex console resolves the problem. I am guessing there is/are packages that might be contributing to this - even with a bare minimal documentclass begindocument ...
– elika kohen
1 hour ago
add a comment |
You also need to install a TeX distribution, i.e. MiKTeX or TeX Live. The TeX distribution contains all the machinery needed to process source code and produce typeset documents; Texmaker is just a front end.
You also need to install a TeX distribution, i.e. MiKTeX or TeX Live. The TeX distribution contains all the machinery needed to process source code and produce typeset documents; Texmaker is just a front end.
answered Jul 20 '12 at 9:45
Ian ThompsonIan Thompson
32k379154
32k379154
Even with MikTex installed, I still get the error. However, I have had success, albeit inconsistently, that running ALL of the updates through the MikTex console resolves the problem. I am guessing there is/are packages that might be contributing to this - even with a bare minimal documentclass begindocument ...
– elika kohen
1 hour ago
add a comment |
Even with MikTex installed, I still get the error. However, I have had success, albeit inconsistently, that running ALL of the updates through the MikTex console resolves the problem. I am guessing there is/are packages that might be contributing to this - even with a bare minimal documentclass begindocument ...
– elika kohen
1 hour ago
Even with MikTex installed, I still get the error. However, I have had success, albeit inconsistently, that running ALL of the updates through the MikTex console resolves the problem. I am guessing there is/are packages that might be contributing to this - even with a bare minimal documentclass begindocument ...
– elika kohen
1 hour ago
Even with MikTex installed, I still get the error. However, I have had success, albeit inconsistently, that running ALL of the updates through the MikTex console resolves the problem. I am guessing there is/are packages that might be contributing to this - even with a bare minimal documentclass begindocument ...
– elika kohen
1 hour ago
add a comment |
It is not enough to just have the TeX distribution installed, it is also necessary to add the MiKTeX bin to the path or else change the commands in the configuration to use the full path to each executable (i.e., if you look at the actual commands being called they are just "latex", "pdflatex", etc. without the path to the executable).
In my case I had MiKTeX installed and working with another editor, but it would not work with TeXMaker - adding the path to the bin to my window Path environment variable resolved the issue for me. For me this path is:
C:Program FilesMiKTeX 2.9miktexbinx64
2
Welcome to TeX.sx! Feel free to visit our TeX.SX starter guide to get the most out of this site.
– Peter Jansson
May 13 '13 at 21:32
add a comment |
It is not enough to just have the TeX distribution installed, it is also necessary to add the MiKTeX bin to the path or else change the commands in the configuration to use the full path to each executable (i.e., if you look at the actual commands being called they are just "latex", "pdflatex", etc. without the path to the executable).
In my case I had MiKTeX installed and working with another editor, but it would not work with TeXMaker - adding the path to the bin to my window Path environment variable resolved the issue for me. For me this path is:
C:Program FilesMiKTeX 2.9miktexbinx64
2
Welcome to TeX.sx! Feel free to visit our TeX.SX starter guide to get the most out of this site.
– Peter Jansson
May 13 '13 at 21:32
add a comment |
It is not enough to just have the TeX distribution installed, it is also necessary to add the MiKTeX bin to the path or else change the commands in the configuration to use the full path to each executable (i.e., if you look at the actual commands being called they are just "latex", "pdflatex", etc. without the path to the executable).
In my case I had MiKTeX installed and working with another editor, but it would not work with TeXMaker - adding the path to the bin to my window Path environment variable resolved the issue for me. For me this path is:
C:Program FilesMiKTeX 2.9miktexbinx64
It is not enough to just have the TeX distribution installed, it is also necessary to add the MiKTeX bin to the path or else change the commands in the configuration to use the full path to each executable (i.e., if you look at the actual commands being called they are just "latex", "pdflatex", etc. without the path to the executable).
In my case I had MiKTeX installed and working with another editor, but it would not work with TeXMaker - adding the path to the bin to my window Path environment variable resolved the issue for me. For me this path is:
C:Program FilesMiKTeX 2.9miktexbinx64
edited May 13 '13 at 21:31
Peter Jansson
5,75083550
5,75083550
answered May 13 '13 at 21:13
BrianBrian
13112
13112
2
Welcome to TeX.sx! Feel free to visit our TeX.SX starter guide to get the most out of this site.
– Peter Jansson
May 13 '13 at 21:32
add a comment |
2
Welcome to TeX.sx! Feel free to visit our TeX.SX starter guide to get the most out of this site.
– Peter Jansson
May 13 '13 at 21:32
2
2
Welcome to TeX.sx! Feel free to visit our TeX.SX starter guide to get the most out of this site.
– Peter Jansson
May 13 '13 at 21:32
Welcome to TeX.sx! Feel free to visit our TeX.SX starter guide to get the most out of this site.
– Peter Jansson
May 13 '13 at 21:32
add a comment |
If you still get error: Log file not found!, when using Texmaker when you have done everything (installed MiKTex, installed Texmaker, and checked if the binary for MiKTeX is already in your windows environment varible) then simply close the Texmaker and reopen it as an administrator. Right click on the executable for Texmaker and "Run as administrator".
This worked for me!
This does not sound at all safe to me! (Is this safe on Windows? I know Windows is different...)
– cfr
May 17 '14 at 21:41
@cfr - yeah, it is a really bad idea to run programs like this as admin. And, it should be reported as a defect if necessary.
– elika kohen
1 hour ago
add a comment |
If you still get error: Log file not found!, when using Texmaker when you have done everything (installed MiKTex, installed Texmaker, and checked if the binary for MiKTeX is already in your windows environment varible) then simply close the Texmaker and reopen it as an administrator. Right click on the executable for Texmaker and "Run as administrator".
This worked for me!
This does not sound at all safe to me! (Is this safe on Windows? I know Windows is different...)
– cfr
May 17 '14 at 21:41
@cfr - yeah, it is a really bad idea to run programs like this as admin. And, it should be reported as a defect if necessary.
– elika kohen
1 hour ago
add a comment |
If you still get error: Log file not found!, when using Texmaker when you have done everything (installed MiKTex, installed Texmaker, and checked if the binary for MiKTeX is already in your windows environment varible) then simply close the Texmaker and reopen it as an administrator. Right click on the executable for Texmaker and "Run as administrator".
This worked for me!
If you still get error: Log file not found!, when using Texmaker when you have done everything (installed MiKTex, installed Texmaker, and checked if the binary for MiKTeX is already in your windows environment varible) then simply close the Texmaker and reopen it as an administrator. Right click on the executable for Texmaker and "Run as administrator".
This worked for me!
answered May 14 '13 at 21:37
maxmmaxm
411
411
This does not sound at all safe to me! (Is this safe on Windows? I know Windows is different...)
– cfr
May 17 '14 at 21:41
@cfr - yeah, it is a really bad idea to run programs like this as admin. And, it should be reported as a defect if necessary.
– elika kohen
1 hour ago
add a comment |
This does not sound at all safe to me! (Is this safe on Windows? I know Windows is different...)
– cfr
May 17 '14 at 21:41
@cfr - yeah, it is a really bad idea to run programs like this as admin. And, it should be reported as a defect if necessary.
– elika kohen
1 hour ago
This does not sound at all safe to me! (Is this safe on Windows? I know Windows is different...)
– cfr
May 17 '14 at 21:41
This does not sound at all safe to me! (Is this safe on Windows? I know Windows is different...)
– cfr
May 17 '14 at 21:41
@cfr - yeah, it is a really bad idea to run programs like this as admin. And, it should be reported as a defect if necessary.
– elika kohen
1 hour ago
@cfr - yeah, it is a really bad idea to run programs like this as admin. And, it should be reported as a defect if necessary.
– elika kohen
1 hour ago
add a comment |
It is possible in when using a version of Texmaker based on QT5 that you get this error even with you Tex framework available on the path.
Make sure that the document you are trying to compile has a .tex prefix, it will not work otherwise.
3
Welcome to TeX.SX! You can have a look on our starter guide to familiarize yourself further with our format.
– Claudio Fiandrino
Jul 19 '13 at 18:38
add a comment |
It is possible in when using a version of Texmaker based on QT5 that you get this error even with you Tex framework available on the path.
Make sure that the document you are trying to compile has a .tex prefix, it will not work otherwise.
3
Welcome to TeX.SX! You can have a look on our starter guide to familiarize yourself further with our format.
– Claudio Fiandrino
Jul 19 '13 at 18:38
add a comment |
It is possible in when using a version of Texmaker based on QT5 that you get this error even with you Tex framework available on the path.
Make sure that the document you are trying to compile has a .tex prefix, it will not work otherwise.
It is possible in when using a version of Texmaker based on QT5 that you get this error even with you Tex framework available on the path.
Make sure that the document you are trying to compile has a .tex prefix, it will not work otherwise.
answered Jul 19 '13 at 18:20
Maxime LavigneMaxime Lavigne
111
111
3
Welcome to TeX.SX! You can have a look on our starter guide to familiarize yourself further with our format.
– Claudio Fiandrino
Jul 19 '13 at 18:38
add a comment |
3
Welcome to TeX.SX! You can have a look on our starter guide to familiarize yourself further with our format.
– Claudio Fiandrino
Jul 19 '13 at 18:38
3
3
Welcome to TeX.SX! You can have a look on our starter guide to familiarize yourself further with our format.
– Claudio Fiandrino
Jul 19 '13 at 18:38
Welcome to TeX.SX! You can have a look on our starter guide to familiarize yourself further with our format.
– Claudio Fiandrino
Jul 19 '13 at 18:38
add a comment |
I was using a portable version of miktex with texmaker. Before using the texmaker you need to click on the Miktex box, then a blue box appears at the bottom of your page. Then you can reopen the texmaker and it will work.
add a comment |
I was using a portable version of miktex with texmaker. Before using the texmaker you need to click on the Miktex box, then a blue box appears at the bottom of your page. Then you can reopen the texmaker and it will work.
add a comment |
I was using a portable version of miktex with texmaker. Before using the texmaker you need to click on the Miktex box, then a blue box appears at the bottom of your page. Then you can reopen the texmaker and it will work.
I was using a portable version of miktex with texmaker. Before using the texmaker you need to click on the Miktex box, then a blue box appears at the bottom of your page. Then you can reopen the texmaker and it will work.
answered Sep 20 '13 at 13:40
MolsonMolson
111
111
add a comment |
add a comment |
This also occurs if you already have an install of MikTex but for some reason it gets broken. As happened to me this morning :S The fix is to simply as MikTex to update. It will then tell you there is a problem as it can't find itself, but offers to fix the problem. Update any files you want to update eh Presto, problem solved.
add a comment |
This also occurs if you already have an install of MikTex but for some reason it gets broken. As happened to me this morning :S The fix is to simply as MikTex to update. It will then tell you there is a problem as it can't find itself, but offers to fix the problem. Update any files you want to update eh Presto, problem solved.
add a comment |
This also occurs if you already have an install of MikTex but for some reason it gets broken. As happened to me this morning :S The fix is to simply as MikTex to update. It will then tell you there is a problem as it can't find itself, but offers to fix the problem. Update any files you want to update eh Presto, problem solved.
This also occurs if you already have an install of MikTex but for some reason it gets broken. As happened to me this morning :S The fix is to simply as MikTex to update. It will then tell you there is a problem as it can't find itself, but offers to fix the problem. Update any files you want to update eh Presto, problem solved.
answered Mar 12 '14 at 14:13
ic_fl2ic_fl2
19717
19717
add a comment |
add a comment |
I found a work-around!
I have had this problem with both TeXStudio and TeXMaker. I have manually updated all kinds of environment variables, uninstalled, reinstalled, and updated every Miktex package, etc.
And yet, I still have the error - which means it's not really either a TexMaker or TexStudio error …
What seems to be working for me, now, is reseting the config, creating a bare minimum document, and then recompiling with the regular latex compiler, and moving through them until I get to XelaTeX and final LuaLateX.
I have no idea why, but I am guessing the plain Latex compiler is doing some initializing stuff that the other compilers I have trouble with, (XeLatex and LUALaTeX are not doing. I call Voodoo.
Hope this helps.
add a comment |
I found a work-around!
I have had this problem with both TeXStudio and TeXMaker. I have manually updated all kinds of environment variables, uninstalled, reinstalled, and updated every Miktex package, etc.
And yet, I still have the error - which means it's not really either a TexMaker or TexStudio error …
What seems to be working for me, now, is reseting the config, creating a bare minimum document, and then recompiling with the regular latex compiler, and moving through them until I get to XelaTeX and final LuaLateX.
I have no idea why, but I am guessing the plain Latex compiler is doing some initializing stuff that the other compilers I have trouble with, (XeLatex and LUALaTeX are not doing. I call Voodoo.
Hope this helps.
add a comment |
I found a work-around!
I have had this problem with both TeXStudio and TeXMaker. I have manually updated all kinds of environment variables, uninstalled, reinstalled, and updated every Miktex package, etc.
And yet, I still have the error - which means it's not really either a TexMaker or TexStudio error …
What seems to be working for me, now, is reseting the config, creating a bare minimum document, and then recompiling with the regular latex compiler, and moving through them until I get to XelaTeX and final LuaLateX.
I have no idea why, but I am guessing the plain Latex compiler is doing some initializing stuff that the other compilers I have trouble with, (XeLatex and LUALaTeX are not doing. I call Voodoo.
Hope this helps.
I found a work-around!
I have had this problem with both TeXStudio and TeXMaker. I have manually updated all kinds of environment variables, uninstalled, reinstalled, and updated every Miktex package, etc.
And yet, I still have the error - which means it's not really either a TexMaker or TexStudio error …
What seems to be working for me, now, is reseting the config, creating a bare minimum document, and then recompiling with the regular latex compiler, and moving through them until I get to XelaTeX and final LuaLateX.
I have no idea why, but I am guessing the plain Latex compiler is doing some initializing stuff that the other compilers I have trouble with, (XeLatex and LUALaTeX are not doing. I call Voodoo.
Hope this helps.
answered 28 mins ago
elika kohenelika kohen
1136
1136
add a comment |
add a comment |
protected by Kurt Oct 21 '15 at 20:55
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
@GuyCoder See What are the advantages of TeX Live over MikTeX for some good advice on the choice between the two main distributions for Windows. You really can't go wrong with either one. See also TeX distribution and engine for more info on what a distribution is. See also How do I update my distribution.
– Alan Munn
Jul 19 '12 at 23:59