vi incollo qui quello che mi dice nella sezione DIAGNOSIS il configuration wizart
File: “C:\Programmi\WinEdt Team\WinEdt\TeX.log”
Date: domenica, giugno 6, 2010 15.50
Summary 🙁
===========
There are some problems with your TeX installation. Depending on your intended use of WinEdt and TeX you may have to install additional software, or missing TeX Components…
________________________________________________________
WinEdt 5 (v. 5.5) [Build: 20071003]
*** OS: Windows 5.1 [Build: 2600] Service Pack 2
*** Account Status: Power User+
*** Configuration: MiKTeX
*** TeX System: MiKTeX
*** User Profile: Disabled
*** %B: C:\Programmi\WinEdt Team\WinEdt
*** %b: C:\Programmi\WinEdt Team\WinEdt
*** WinEdt PATH:
“C:\Programmi\WinEdt Team\WinEdt;
C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\System32\Wbem;
C:\Programmi\QuickTime\QTSystem\”
*** Windows PATH:
“C:\WINDOWS\system32;
C:\WINDOWS;
C:\WINDOWS\System32\Wbem;
C:\Programmi\QuickTime\QTSystem\”
________________________________________________________
Searching for Executables:
==========================
WinEdt will try to locate external executables based on the information stored in the variables that were imported from Windows Registry in its Startup Macro. If some components are not found follow the instructions. Some applications such as, for example, TtH or HHC are optional; you can ignore any messages about the “missing” accessories that you are not intending to use…
TeX-Root: not Found
:\MiKTeX
****************************************************
WinEdt did not detect your TeX System in Windows Registry. First make sure that TeX System is actually installed on your computer and that you are running a proper WinEdt Configuration (as displayed in this report). If not, load the MiKTeX or TeX Live configuration from the Options -> Configurations Menu and then recreate this report by pressing “Diagnose the System” button. You may also want to enable the “Default Startup Sequence” to ensure a proper (automatic) TeX System detection.
If a TeX System is installed on your computer but the problem persists start the Execution Mode interface. Disable the “Auto Detect” option for the TeX Root folder and manually enter the location, such as:
C:\Program Files\MiKTeX 2.6
Press the “Apply” button and as far as WinEdt is concerned the connection with your TeX System has been established!
WinEdt will not be able to launch any TeX Accessories until the problem is corrected.
****************************************************
TeX-Bin: not Found
:\MiKTeX\miktex\bin
TeX-Help Folder: not Found
:\MiKTeX\doc\latex\help
DVIView: not Found
yap.exe
TeX-Bin (TeX.exe): not Found
TeX-Bin (LaTeX.exe): not Found
TeX-Bin (AMSTeX.exe): not Found
TeX-Bin (PDFTeX.exe): not Found
TeX-Bin (PDFLaTeX.exe): not Found
TeX-Bin (BibTeX.exe): not Found
TeX-Bin (MakeIndex.exe): not Found
TeX-Bin (dvips.exe): not Found
TeX-Bin (dvipdfm.exe): not Found
MiKTeX-Bin (TeXify.exe): not Found
TtH: (tth.exe): not Found
****************************************************
TtH is an optional LaTeX to HTML convertor. If TtH is installed on your system you should modify the PATH to include its location (or else place “tth.exe” to TeX’s Binary folder or somewhere else on WinEdt’s PATH).
For a variety TeX convertors visit http://www.tug.org and follow the information and links on this page. TtH can be found at:
http://hutchinson.belmont.ma.us/tth
Unless you want to convert TeX files into html format you can safely ignore this message because you don’t need this application for TeX-ing…
Please note that TeX convertors are not really a WinEdt-related issue…
****************************************************
GS-Bin: (gswin32c.exe): not Found
****************************************************
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. It is recommended that you install Ghostscript and GSView to enhance the capabilities of your TeX system. A link is available on TUG’s (www.tug.org) site. 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\gs8.54\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…
****************************************************
AcroRead: OK (REG)
“C:\Programmi\Adobe\Reader 9.0\Reader\AcroRd32.exe”
C:\PROGRA~1\Adobe\READER~1.0\Reader\AcroRd32.exe
HHC: not Found
“hhc.exe”
****************************************************
HHC (HTML Help Workshop and Compiler) is determined in Startup.edt from the Windows Registry. WinEdt did not find any valid registry entries pertaining to HHC. If you are planning to use HHC make sure that MS HTML Help Workshop (free download from http://www.microsoft.com) is properly installed on your system. If absolutely necessary, you can edit WinEdt’s Startup Macro and explicitly enter definition of the executable:
// Detect MS HTML Workshop in Windows Registry!
…
// Enter it Manually if not found
Assign(“HHC”,|”C:\…\HTML Help Workshop\hhc.exe”|);
Unless you want to use the HTML Help compiler to create your own “.chm” files you can safely ignore this message because you don’t need this application…
****************************************************
==========================================================
Help in this interface contains additional guidelines on how to correct most commonly encountered problems and how to further customize and configure external applications that are launched from WinEdt…
==========================================================