--- "Paul A. Rubin" <[EMAIL PROTECTED]> wrote: > John Kane wrote: > > > Obviously, as a student you, did not have the card > > reader shred your computer deck ½ hours before the > > assignment was due and all you needed was a clean > > printout. > > No, but I have the dubious distinction of having > rested a box of punch cards on the roof of my car whilst unlocking it, and > then driving off without bringing them into the car. > (Unsurprisingly, the cards did not drive off as far as I did. Something about inertia, > I believe.)
Simply a human factors problem. I was the victim of the blind malevolence of an IBM keypunch machine. What a way to start a Monday! I am still traumatized. > > I've posted the log and a screen shot of the directory >> athttp://ca.geocities.com/jrkrideau/LyX/sh_configure_output1.pdf > Well, the output from the configuration script is in fact interesting. Note the first three lines. Yes I thought they looked ominous but I didn't know what to do about them except re-install MiKTex. > Best to double check things here. From a DOS> prompt, try the following: > > 1. Type 'path' to get the system path. Make sure that (a) the MiKTeX bin > directory is properly listed and (b) no directory ahead of it contains a file named latex.exe. Appears not to: Path is c:\program files\imagemagick-6.2.5-q16;C:\Perl\bin\;C:\texmf\miktex\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Common Files\MDL Shared\ISIS;C:\msys\1.0\bin and I don't see anything in texmf or miktex that looks suspicious > > 2. I've attached the file used to test your LaTeX > installation. and run 'latex chklatex.ltx'. It should cough up a > log file, that should contain the string 'ThisIsLaTeX2e' > (lack of spaces > If not, there may be a problem with the MiKTeX installation. If that does > work, then we will need to do a small bit of surgery to the installation script to find out > why it doesn't like your latex.exe file. I ran the 'latex chklatex.ltx' file. No sign of 'ThisIsLaTeX2e' as far as I can see. The log is at http://ca.geocities.com/jrkrideau/LyX/LatexLog12nov05.pdf . The annoying thing is that I spend an hour and a half downloading and installing a new copy of MiKTeX and I thought that I had manged to kill off everything from the old installation. Well another clean sweep tomorrow or Monday and I'll see what happens. Below is a quick summary of what I think I have at the moment. Thanks for all the help. I get the feeling that this may not be impossible after all. Installed files and paths Actual according to the LyX installer C:\msys\1.0\bin (sh.exe) C:\Python23 (Python.exe) C:\texmf\miktex\bin (latex.exe) C:\Perl\bin (Perl.exe) C:\Program Files\gs\gs8.51\bin (gswin32c.exe) C:\Program Files\ImageMagick-6.2.5-Q16 (convert.exe) C:\LyX Before installing LyX I checked and all of the above programs loaded including latex.exe. According to computer I also had gswview which also loaded. C:\GSTools\gsview (gsview32.exe) LyX path after installation C:\msys\1.0\bin;C:\Python23;C:\texmf\miktex\bin;C:\Perl\bin;C:\Program Files\gs\gs8.51\bin;C:\Program Files\ImageMagick-6.2.5-Q16 I added the gsview path and reconfigured. New LyX paths C:\msys\1.0\bin;C:\Python23;C:\texmf\miktex\bin;C:\Perl\bin;C:\Program Files\gs\gs8.51\bin;C:\Program Files\ImageMagick-6.2.5-Q16;C:\GSTools\gsview Systems Paths c:\program files\imagemagick-6.2.5-q16;C:\Perl\bin\;C:\texmf\miktex\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Common Files\MDL Shared\ISIS;C:\msys\1.0\bin __________________________________________________________ Find your next car at http://autos.yahoo.ca
