Re: [MiKTeX] 2.5 breaks hyperref package?

[<gn...@gm...>]

On 10/6/06, Alan Ristow <ri...@ec...> wrote:
> Thomas P. Colson wrote:
> > Unfortunately I can't switch to another doc class at this (late) point. The
> > NCSUTHESIS is just the ucthesis renamed, and does a lot of things that no
> > other doc class can do (that I can find), such as the completely
> > un-reasonable and non standard margins , and all the preamble documents
> > (dedication, TOC, etc... page numbering required by the university.

I have some experience with thesis deadlines -- in my case I was using a
formatter running on a CDC Cyber with a 63-character set (so markup
was needed for capitalization!) printing on a discontinued model
daisy-wheel printer.  I had difficulty locating a wheel with math
symbols, but eventually was able to track down the last one in Canada.
 Those printers vibrated like a jackhammer, and had a tendency to
strip the spokes on the daisywheel if the printer head vibrated loose.

> I suspect the only reason Otto switched to the book class is because
> ncsuthesis4 is not available from CTAN -- I don't think he is either
> suggesting that you switch to book.cls or that he has reproduced your
> problems with ncsuthesis4.cls and MiKTeX 2.5 (correct me if I'm wrong,
> Otto).
>
> I downloaded ncsuthesis4.cls from
> http://moocow.csc.ncsu.edu/academics/graduate/degrees/thesis_style/ncsuthesis4.cls
> and ran the example you provided below. I had no problems whatsoever. Is
> this the same ncsuthesis4.cls that you are using? If so, I suspect the
> problem is somewhere in your MiKTeX configuration rather than in MiKTeX
> itself.

The example also works on my linux system (I won't be around any Win32
systems for several days, at which point I'll probably have to spend a
day installing the monthly security patches before I can do any work).
 I use TL2005 updated with MikTeX's latex and tools.  There was an
interesting message:

(/mnt/hdb/opt/tex/texlive/2005/../texmf-updates/tex/latex/tools/array.sty

LaTeX Warning: Command \@xhline  has changed.
               Check if current package is valid.

)

How about posting the log for a run with "\listifiles" for the working
configuration?  Comparing this is one for the broken configuration
should catch many configuration problems.  I often do this and have
found it useful to edit one of the  logs to make the file paths match
the other to reduce the number of meaningless differences.

-- 
George N. White III <aa...@ch...>
Head of St. Margarets Bay, Nova Scotia