dvips doesn't find config.ps under (my setup with) Win 98

[John Hillas]

Thanks Eli,

I have more information, but dvips still isn't finding
config.ps.

This message is a bit long.  Sorry.

> -----Original Message-----
> From: Eli Zaretskii [mailto:eliz@is.elta.co.il]
> Sent: Sunday, 13 June 1999 20:52
> To: John Hillas
> Cc: Fptex Mail List
> Subject: Re: dvips doesn't find config.ps under (my setup with) Win 98
>
>
>
> On Sun, 13 Jun 1999, John Hillas wrote:
>
> > I have two copies of config.ps in my TeX tree,
> > at c:/TeX/texmf.local/dvips/config
> > and at c:/TEX/texmf/dvips/config
> [snip]
> > but this made no difference to the behaviour of dvips.
>
> Does your ls-R file mention these files?  If not, Kpathsea won't find
> them, because when a texmf tree has an ls-R file, the filesystem is
> never searched.  If ls-R does NOT have those files, running mktexlsr
> would solve the problem.

Not running mktexlsr is my most common mistake.  So whenever
I have difficulty that's the first thing I do.  I'd run it
many times, but after your advise I also checked the ls-R
files in a text editor.  config.ps, and all the other files
I was looking for are there.

The method you suggested for checking reveals that kpsewhich
does find config.ps

  C:\TeX\texmf>kpsewhich --format="dvips config" config.ps
  c:/TeX/texmf.local/dvips/config/config.ps

However dvips isn't using it.  Can one check what
configuration files dvips is using.  Copying config.ps to
config.xxx in the current directory and using -Pxxx doesn't
seem to have dvips use config.xxx as I had hoped.

Using -d128 which I assumed would tell me about the
configuration files gives me a long list of messages of the
form

Alloc 142
Alloc 12
Alloc 3132
Alloc 17
Alloc 142
Alloc 142
Alloc 142
Alloc 142
Alloc 142
Alloc 142
Alloc 142
Alloc 142
Alloc 142
Alloc 142
Alloc 816
Alloc 21
Alloc 23

before the regular output.

All the expected files are in the ls-R databases.  In
particular bsr.map is in ls-R for the texmf tree.  However

C:\TeX\texmf>kpsewhich --format="map" bsr.map

just returns me the empty command line.  Should it?

using also

C:\TeX\texmf>kpsewhich --debug=-1 --format=map bsr.map | more

1) didn't work the way I'd hoped.  the "| more" didn't seem
to have any effect.  (Does anyone know how to manage the
command consol in Win 98?  The documentation seems a little
incomplete.)

and

2) didn't seem to find bsr.map, though it is both in the ls-R
database and on the disk.

The last part of the output was (remember I can't work | more
or work out how to send the screen output to a file)

kdebug:hash_lookup(TEXMF.kpsewhich) => (nil)
kdebug:hash_lookup(TEXMF) => {!!$TEXMFLOCAL,!!$TEXMFMAIN,!!$TEXMFEXTRA}
kdebug:hash_lookup(TEXMFLOCAL.kpsewhich) => (nil)
kdebug:hash_lookup(TEXMFLOCAL) => C:/TeX/texmf.local
kdebug:hash_lookup(TEXMFMAIN.kpsewhich) => (nil)
kdebug:hash_lookup(TEXMFMAIN) => $SELFAUTOPARENT/texmf
kdebug:hash_lookup(TEXMFEXTRA.kpsewhich) => (nil)
kdebug:hash_lookup(TEXMFEXTRA) => C:/TeX/texmf.extra
kdebug:Search path for map files (from texmf.cnf)
kdebug:  =
.;!!C:/TeX/texmf.local/fontname;!!C:/TEX/texmf/fontname;!!C:/TeX/texm
f.extra/fontname
kdebug:  before expansion = .;$TEXMF/fontname
kdebug:  application override path = (none)
kdebug:  application config file path = (none)
kdebug:  texmf.cnf path = .;$TEXMF/fontname
kdebug:  compile-time path = .;c:/TeX/texmf/fontname
kdebug:  default suffixes = .map
kdebug:  other suffixes = (none)
kdebug:  search only with suffix = 0
kdebug:  numeric format value = 11
kdebug:  runtime generation program = (none)
kdebug:  extra program args = (none)
kdebug:  program enabled = 0
kdebug:  program enable level = 0
kdebug:start search(file=bsr.map, must_exist=0, find_all=0,
path=.;!!C:/TeX/texm
f.local/fontname;!!C:/TEX/texmf/fontname;!!C:/TeX/texmf.extra/fontname).
normalize_filename returned (0) .
normalize_filename returned (0) .
normalize_filename returned (0) .
path . is a directory
kdebug:path element . => ./
normalize_filename returned (0) ./bsr.map
normalize_filename returned (3) c:/TeX/texmf.local/fontname
kdebug:hash_lookup(bsr.map) => (nil)
kdebug:hash_lookup(bsr.map) => c:/TEX/texmf/dvips/config/
kdebug:db:match(c:/TEX/texmf/dvips/config/bsr.map,c:/TeX/texmf.local/fontnam
e) =
 0
normalize_filename returned (3) c:/TEX/texmf/fontname
kdebug:hash_lookup(bsr.map) => (nil)
kdebug:hash_lookup(bsr.map) => c:/TEX/texmf/dvips/config/
kdebug:db:match(c:/TEX/texmf/dvips/config/bsr.map,c:/TEX/texmf/fontname) = 0
normalize_filename returned (3) c:/TeX/texmf.extra/fontname
kdebug:hash_lookup(bsr.map) => (nil)
kdebug:hash_lookup(bsr.map) => c:/TEX/texmf/dvips/config/
kdebug:db:match(c:/TEX/texmf/dvips/config/bsr.map,c:/TeX/texmf.extra/fontnam
e) =
 0
kdebug:search(bsr.map) =>


This means that it didn't find any bsr.map that it was willing
to use, right?



>
> > Should kpsewhich find config.sp?
>
> It should, if you tell it to look for DviPS config files, like this:
>
>   kpsewhich --format="dvips config" config.ps
>
> If this doesn't work, run it again after you set KPSE_DEBUG=-1, then
> look at the output (redirecting it to a file is a good idea, since it
> is very voluminous).
>

Setting KPSE_DEBUG=-1 doesn't seem to have any effect.
Certainly not the same effect as the --debug=-1.  Is this
another problem with my setup?  I really haven't made many
changes to the newly installed version.  (I did add
my old texmf.extra and some of my old texmf.local trees
back.)

Thanks for any help.

John