## LaTeX forum ⇒ WinEdt ⇒ Compilation with WinEdt 7 fails Topic is solved

Information and discussion about WinEdt, a commercial integrated LaTeX environment for Windows
zaqsedc
Posts: 2
Joined: Mon Feb 18, 2013 6:35 pm

### Compilation with WinEdt 7 fails

Hi, I have problem with WinEdt 7. I installed MiKTeX full but the icon for compile is in grey color. If I load the diagnosis I have good response but I can't compile help me please

`File: "C:\Users\Devil00\AppData\Roaming\WinEdt Team\WinEdt 7\TeX.log"Date: Monday, February 18, 2013  17:48 Summary :-)=========== Your TeX installation appears to be fine. If you experience problems after an application has been launched this usually isn't a WinEdt-related matter. In such case, you should test a problematic application from the Command Prompt, consult the documentation that comes with your (TeX) software, and try to locate the real source of your problem...________________________________________________________________________________ WinEdt 7  (v. 7.0)  [Build: 20120329] Caption: WinEdt 7.0 | MiKTeXDefault Mode: TeXDefault Type: .texDefault Path: %P *** OS: Windows 6.2 [Build: 9200] *** Account (UAC) Status: Restricted User*** Configuration: MiKTeX*** TeX System: MiKTeX*** User Profile: Enabled*** %B: C:\Users\Devil00\WinEdt Team\WinEdt 7*** %b: C:\Users\Devil00\AppData\Roaming\WinEdt Team\WinEdt 7 *** WinEdt  PATH: "C:\Users\Devil00\WinEdt Team\WinEdt 7;  C:\Program Files (x86)\PC Connectivity Solution\;  C:\MSC.Software\Patran\20122\bin;  C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;  C:\Program Files (x86)\Intel\iCLS Client\;  C:\Program Files\Intel\iCLS Client\;  C:\Windows\system32;  C:\Windows;  C:\Windows\System32\Wbem;  C:\Windows\System32\WindowsPowerShell\v1.0\;  C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;  C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;  C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;  C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;  C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;  C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;  C:\Program Files\MATLAB\R2010a\runtime\win64;  C:\Program Files\MATLAB\R2010a\bin;  C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\" *** Windows PATH: "C:\Program Files (x86)\PC Connectivity Solution\;  C:\MSC.Software\Patran\20122\bin;  C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;  C:\Program Files (x86)\Intel\iCLS Client\;  C:\Program Files\Intel\iCLS Client\;  C:\Windows\system32;  C:\Windows;  C:\Windows\System32\Wbem;  C:\Windows\System32\WindowsPowerShell\v1.0\;  C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;  C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;  C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;  C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;  C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;  C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;  C:\Program Files\MATLAB\R2010a\runtime\win64;  C:\Program Files\MATLAB\R2010a\bin;  C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\" ________________________________________________________________________________ Searching for Executables:========================== WinEdt will try to locate external executables based on the PATH Environment Variable and Windows Registry. If some components are not found follow the instructions. Some applications such as, for example, gswinn32c.exe or GSView are optional; you can ignore any messages about the "missing" accessories that you are not intending to use... TeX-Root: OK   C:\Program Files (x86)\MiKTeX 2.9TeX-Bin:  OK   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin TeX-Help Folder: OK   C:\Program Files (x86)\MiKTeX 2.9\doc DVIView: OK (PATH yap.exe)*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\yap.exe TeX-Bin (TeX.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\tex.exeTeX-Bin (LaTeX.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\latex.exeTeX-Bin (PDFTeX.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\pdftex.exeTeX-Bin (PDFLaTeX.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\pdflatex.exeTeX-Bin (BibTeX.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\bibtex.exeTeX-Bin (dvips.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\dvips.exeTeX-Bin (ps2pdf.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\ps2pdf.exeTeX-Bin (dvipdfmx.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\dvipdfmx.exeTeX-Bin (mf.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\mf.exeTeX-Bin (mpost.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\mpost.exe MiKTeX-Bin (TeXify.exe): OK*   C:\Program Files (x86)\MiKTeX 2.9\miktex\bin\texify.exe  GS-Bin: (gswin32c.exe): not Found******************************************************************Recent versions of MiKTeX and TeX Live come with their own version Ghostscript and by default WinEdt does not use this application. Unless you have special needs that require custom installed GS you can ignore this message... Ghostscript is used mainly to handle graphics (ps and eps files) and to convert ps files to pdf. Without it your TeX system may have a limited ability to display graphics but the basic functionality is not affected by its absence. If GS is installed make sure that its BIN directory is on your PATH. WinEdt did not find any trace of installed GS in Windows Registry. If necessary, enter the GS Binary Folder manually in the Ghostscript Tab Page of the Execution Modes interface. Depending on your version of GS disable the Auto Detection and enter something like:    C:\Program Files\gs\gs9.00\bin ****************************************************************** GSView: not Found   gsview32.exe******************************************************************PS viewer (GSView) is determined in Startup Macro from the Windows Registry. WinEdt did not find any valid application associated with "*.ps" files. You should make sure that the "*.ps" files are associated with the ps previewer installed on your system. You can start GSView, choose "Options -> Advanced Configure" menu command, associate the ps files with GSView, and then restart WinEdt. Alternatively, you can enter the GSView executable manually in the Ghostscript Tab Page of the Execution Modes interface. Depending on your version of GSView disable the Auto Detection and enter something like:    "C:\Program Files\Ghostgum\gsview\gsview32.exe" Quotes are required if the filename contains spaces... If you are not interested in previewing ps files you can ignore this message.****************************************************************** PDF Viewer (PDF-View): OK (REG)   "C:\Program Files (x86)\Adobe\Reader 10.0\Reader\AcroRd32.exe"   C:\PROGRA~2\Adobe\READER~1.0\Reader\AcroRd32.exe ================================================================================ Help in this interface contains additional guidelines on how to correct the most commonly encountered problems and how to further customize and configure external applications that are launched from WinEdt... ================================================================================`

Tags:

zaqsedc
Posts: 2
Joined: Mon Feb 18, 2013 6:35 pm
Sorry, I resolved my problem, I used before a file text top tesi without all files and WinEdt doesn't work. Now I downloaded a complete packet and it works. Thanks for all