Support Requests item #869, was opened at 2007-09-23 06:00 You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=494&aid=869&group_id=106 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Theo Hopman (thopman) Assigned to: Nobody (None) Summary: pdflatex slow to start on Cygwin Initial Comment: I use Cygwin on WinXP pro, with teTex 3.0 installed. I recently built pdftex 1.40 (which went well), manually replaced the old binaries of pdftex, and rebuilt the various formats using fmtutil. Now, however, pdflatex starts up only after a considerable delay (anywhere from a couple of seconds up to half a minute). While pdflatex sits there looking like its doing nothing, it also responds slowly to interrupt (^C) signals. Why might this be? `pdflatex --version`, by contrast, is instantaneous, so the issue is likely something to do with searching or loading formats. THeo ---------------------------------------------------------------------- Comment By: Nobody (None) Date: 2007-09-23 17:26 Message: Logged In: NO Is kpathsea also slow? Was pdftex 1.40 slow when building formats? What do you see in the Windows process viewer (there are two CPU columns, one shows cumulative CPU time and the other current CPU usage, by default only one is shown)? For me, when apps are slow to start it is usually mcafee that is using 98% of CPU. Matlab takes over 2 minutes to start with McAfee running, but only a few seconds with McAfee configured to ignore the Matlab directory. Are there network directories in the search path? I use Win32 at work were the users "HOME" directory is on a network drive, but many users systems don't correctly negotiate the duplex setting with the ethernet switch. When network access is slow, running the network "repair" tool (sometimes takes several attempts) will (usually, eventually) make things better (linux has mii-tool where I can check the duplex setting and force it to full). If "man pdftex" is working, look for: -recorder Enable the filename recorder. This leaves a trace of the files opened for input and output in a file with extension .fls. This still omits a few files, but may give you a hint. Have you tried simplifying the search paths in texmf.cnf? ---------------------------------------------------------------------- You can respond by visiting: http://sarovar.org/tracker/?func=detail&atid=494&aid=869&group_id=106