New Installation under miktex, not working

New Installation under miktex, not working

[Todd DeVries]

Hi,

I'm attempting to install context under miktex 2.4. I've updated the
format files and followed other instructions as per the contextgarden
discussions. I'm probably missing something really obvious and would
appreciate any help offered.  I receive this output when running the
following commands:

<<
texexec test.txt

 TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005

unknown file type: texmfscripts
 fixing texformat path : C:/localtexmf/miktex/fmt
fixing engine variable : pdfetex

        total run time : 0 seconds
>>
texexec --version
and
<<
 TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005

unknown file type: texmfscripts
               texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE
1997-2005
               texutil : TeXUtil 9.0.0 - ConTeXt / PRAGMA ADE
1992-2004
                   tex : pdfeTeX, 3.141592-1.21a-2.2 (MiKTeX 2.4)
(preloaded format=cont-en 2006.1.15)  15 JAN 2006 11:32
               context : ver: 2006.01.09
               cont-en : ver: 2006.01.09  fmt: 2006.1.15  mes: english
unknown file type: 'fmt'
unknown file type: 'fmt'
unknown file type: 'fmt'
unknown file type: 'fmt'
unknown file type: 'fmt'
unknown file type: 'fmt'
unknown file type: 'fmt'
unknown file type: 'fmt'

        total run time : 1 seconds

>>

Re: New Installation under miktex, not working

[Taco Hoekwater]

Todd DeVries wrote:
> Hi,
> 
> I'm attempting to install context under miktex 2.4. I've updated the
> format files and followed other instructions as per the contextgarden
> discussions. I'm probably missing something really obvious and would
> appreciate any help offered.  I receive this output when running the
> following commands:
> 
> <<
> texexec test.txt

Are you sure your tex file has extension txt? Your output is precisely
what you get when texexec cannot find the input file, so I am a bit
suspicious that that may be the problem.

For the warnings: You need to tell texexec that you are running
miktex, but I do not know how precisely that is done (I use tetex)

Cheers, Taco

Re: New Installation under miktex, not working

[Christopher G D Tipper]

Some defaults from my old MiKTeX .ini file (local-texmf/scripts/perl/ 
texexec.ini) I can't test this as I have defected to a saner  
platform :-)

enable variable miktex at top of file and some variation of this below.

for  miktex  set  UsedInterfaces    to  en, uk
for  miktex  set  UserInterface     to  uk
for  miktex  set  TeXExecutable     to  pdfetex.exe
for  miktex  set  TeXVirginFlag     to  -initialize
for  miktex  set  TeXBatchFlag      to  -interaction=batchmode
for  miktex  set  TeXFormatFlag     to  &
for  miktex  set  MpToTeXExecutable to  mptotex.exe
for  miktex  set  MpVirginFlag      to  -initialize
for  miktex  set  MpPassString      to
for  miktex  set  MpBatchFlag       to  -interaction=batchmode
for  miktex  set  MpFormat	    to  metafun
for  miktex  set  MpFormatFlag      to  -undump=
for  miktex  set  TeXFormatPath   to "d:\local-texmf\miktex\fmt\"
for  miktex  set  ConTeXtPath     to "d:\local-texmf\tex\context\base\"
for  miktex  set  SetupPath       to "c:\Progra~1\MiKTeX\miktek\base\"
for  miktex  set  TeXScriptsPath  to "d:\local-texmf\scripts\context 
\perl\"
for  miktex  set  TeXProgramPath  to "c:\Progra~1\MiKTeX\miktex\bin\"

Also mptopdf will not work unless you set the TEXSYSTEM environment  
variable to "miktex" as on ContextGarden.

Also it occurs to me that texexec will not recognise test.txt, but  
will expect test and add .tex itself.

Don't forget to update fndb at every opportunity from MikTeX's  
management app.

Christopher

> Todd DeVries wrote:
>> Hi,
>> I'm attempting to install context under miktex 2.4. I've updated the
>> format files and followed other instructions as per the contextgarden
>> discussions. I'm probably missing something really obvious and would
>> appreciate any help offered.  I receive this output when running the
>> following commands:
>> <<
>> texexec test.txt
>
> Are you sure your tex file has extension txt? Your output is precisely
> what you get when texexec cannot find the input file, so I am a bit
> suspicious that that may be the problem.
>
> For the warnings: You need to tell texexec that you are running
> miktex, but I do not know how precisely that is done (I use tetex)
>
> Cheers, Taco
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context

--------------------------------o00o--------------------------------
   “Since light travels faster than sound, isn’t that why
    some people appear bright until you hear them speak”
                                           — Steve Wright

Re: New Installation under miktex, not working

[Mojca Miklavec]

Todd DeVries wrote:
> Hi,
>
> I'm attempting to install context under miktex 2.4. I've updated the
> format files and followed other instructions as per the contextgarden
> discussions. I'm probably missing something really obvious and would
> appreciate any help offered.  I receive this output when running the
> following commands:

I don't know why I keep using MikTeX (there are problems all the time,
but it is [or at least it should be] easy to update and is already
installed on most computers here), just some points:
- texexec --make --all doesn't work anyway (well, it works, but it
forgets to copy the files to the proper place)
If you want to make formats, go to MikTeX options -> TeX formats ->
choose cont-en -> Edit ...
Here are the values that I have (it may be that I changed any of them
manually, I don't remember):
Format Name: cont-en
Compiler: pdfe-TeX (Extended Mode)
Input File Name: cont-en.tex
Output File Name: cont-en.efmt
Exclude has to be unchecked

- MikTeX updates the formats automatically (if it does). If it
doesn't, the "standard ConTeXt" ways fail anyway and searching for
files doesn't always work either
- I often have problems after upgrading ConTeXt, but I can hardly tell
you what to do. I try all the different tricks (updating filename
database, building the formats, ...) without any success, but after
two days it simply works again by some black magic.

> <<
> texexec test.txt
>
>  TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
>
> unknown file type: texmfscripts
>  fixing texformat path : C:/localtexmf/miktex/fmt
> fixing engine variable : pdfetex
>
>         total run time : 0 seconds
> >>

That's the output that I get if the file doesn't exist.

Can you make a file "test.tex" (not txt) and try to compile that one?
Send the new report then (if there are any differences of course).

> texexec --version
> and
> <<
>  TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
>
> unknown file type: texmfscripts
>                texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE
> 1997-2005
>                texutil : TeXUtil 9.0.0 - ConTeXt / PRAGMA ADE
> 1992-2004
>                    tex : pdfeTeX, 3.141592-1.21a-2.2 (MiKTeX 2.4)
> (preloaded format=cont-en 2006.1.15)  15 JAN 2006 11:32
>                context : ver: 2006.01.09
>                cont-en : ver: 2006.01.09  fmt: 2006.1.15  mes: english
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
> unknown file type: 'fmt'
>
>         total run time : 1 seconds

I also get this output since December (I thought that ConTeXt was
broken at first), but it is harmless and compiling the documents
nevertheless works. Perhaps that extensive use of "unknown file type:
'fmt'" is the new Taco's inclusion that Hans mentioned in some other
mail ;) "unknown file type: texmfscripts" should also be harmless and
will disapear once MikTeX starts to support the new pdfTeX (if I
understood correctly).

Mojca

Re: New Installation under miktex, not working

[Aditya Mahajan]

<--- On Jan 16, Mojca Miklavec wrote --->

> Todd DeVries wrote:
>> Hi,
>>
>> I'm attempting to install context under miktex 2.4. I've updated the
>> format files and followed other instructions as per the contextgarden
>> discussions. I'm probably missing something really obvious and would
>> appreciate any help offered.  I receive this output when running the
>> following commands:
>
> I don't know why I keep using MikTeX (there are problems all the time,
> but it is [or at least it should be] easy to update and is already
> installed on most computers here), just some points:

I use latex a lot, and for windows+latex Miktex is one of the best 
distribution. Most of the packages get installed on the fly and it can 
be updated easily. Once you get used to it, it is hard to try other 
latex distributions.

> - texexec --make --all doesn't work anyway (well, it works, but it
> forgets to copy the files to the proper place)

It also happens with me and the solution that you describe below 
works. You need to update the formats from Miktex Options. I *guess* 
the reason texexec fails to place the format in proper place is 
because it simply does not know where the localtexmf tree is. I am not 
sure if it has a way of finding it out without the user specifying an 
environment variable.


> If you want to make formats, go to MikTeX options -> TeX formats ->
> choose cont-en -> Edit ...
> Here are the values that I have (it may be that I changed any of them
> manually, I don't remember):
> Format Name: cont-en
> Compiler: pdfe-TeX (Extended Mode)
> Input File Name: cont-en.tex
> Output File Name: cont-en.efmt
> Exclude has to be unchecked
>
> - MikTeX updates the formats automatically (if it does). If it
> doesn't, the "standard ConTeXt" ways fail anyway and searching for
> files doesn't always work either


> - I often have problems after upgrading ConTeXt, but I can hardly tell
> you what to do. I try all the different tricks (updating filename
> database, building the formats, ...) without any success, but after
> two days it simply works again by some black magic.


Here is what I do (I am not sure even if this is the correct thing to 
do, but seems to work)

Make a tree called pragma-texmf. Download cont-tmf.zip and 
cont-fnt.zip and unzip them in pragma-texmf. Go to MikTex options and 
add pragma-texmf as a tree. Move it up so that it is the first tree. 
This way whenever any program searches for a context related file, it 
finds it in the pragma-tree. Now go and recreate the formats. 
Everything works (well except mptopdf the program, but that is not 
critical for me). To keep in sync with context's pace of development, 
simply download the entire cont-tmf tree whenever a newer version is 
released. I have not managed to convince texsync to just download 
texmf tree, and I do not really care about downloading a big zip.

This makes me feel whether it is a good idea to have miktex and 
context for windows (from the pragma site) in parallel. I use cygwin 
and context for windows only seems to work from cmd.exe and not 
bash.exe. I tried to convert setuptex.sh to setuptex.bash, but could 
not get to work. So, I settled with the method of downloading the 
relevant trees and things work (by black magic, as you said)

Aditya

Re: New Installation under miktex, not working

[Mojca Miklavec]

Aditya Mahajan wrote:

> Make a tree called pragma-texmf. Download cont-tmf.zip and
> cont-fnt.zip and unzip them in pragma-texmf. Go to MikTex options and
> add pragma-texmf as a tree. Move it up so that it is the first tree.
/.../
> This makes me feel whether it is a good idea to have miktex and
> context for windows (from the pragma site) in parallel. I use cygwin
> and context for windows only seems to work from cmd.exe and not
> bash.exe. I tried to convert setuptex.sh to setuptex.bash, but could
> not get to work. So, I settled with the method of downloading the
> relevant trees and things work (by black magic, as you said)

I have them (MikTeX and the stand-alone from Pragma) in parallel
without any problem. I created "pragmatex.bat" (visible by PATH) which
calls the setuptex.bat (or whatever the script in the stand-alone
distr. is called). The two distros don't interfere at all. Once I call
"pragmatex", all the sources and executables are chosen from the
stand-alone tree when I compile the documents. (But thanks for the
idea of making another texmf-pragma tree! I always managed to break
something when mixing MikTeX and original files from Pragma, that's
why I preferred to leave things as they are and use another distro
instead.)

I'm not sure, but I guess that you would need tetex to run it from
bash. Don't ask me about the numerous (still unsolved) problems I had
just because the ruby executable is only available under cygwin at the
university.

Mojca

Re: New Installation under miktex, not working

[Todd DeVries]

Thanks to all who responded  to my question yesterday. Not sure why,
but documents are compiling and formats are found. Perhaps I'll do a
stand-alone install to make updates easier in the future.

Todd

On Mon, 16 Jan 2006 10:35:29 -0500 (EST), you wrote:

><--- On Jan 16, Mojca Miklavec wrote --->
>
>> Todd DeVries wrote:
>>> Hi,
>>>
>>> I'm attempting to install context under miktex 2.4. I've updated the
>>> format files and followed other instructions as per the contextgarden
>>> discussions. I'm probably missing something really obvious and would
>>> appreciate any help offered.  I receive this output when running the
>>> following commands:
>>
>> I don't know why I keep using MikTeX (there are problems all the time,
>> but it is [or at least it should be] easy to update and is already
>> installed on most computers here), just some points:
>
>I use latex a lot, and for windows+latex Miktex is one of the best 
>distribution. Most of the packages get installed on the fly and it can 
>be updated easily. Once you get used to it, it is hard to try other 
>latex distributions.
>
>> - texexec --make --all doesn't work anyway (well, it works, but it
>> forgets to copy the files to the proper place)
>
>It also happens with me and the solution that you describe below 
>works. You need to update the formats from Miktex Options. I *guess* 
>the reason texexec fails to place the format in proper place is 
>because it simply does not know where the localtexmf tree is. I am not 
>sure if it has a way of finding it out without the user specifying an 
>environment variable.
>
>
>> If you want to make formats, go to MikTeX options -> TeX formats ->
>> choose cont-en -> Edit ...
>> Here are the values that I have (it may be that I changed any of them
>> manually, I don't remember):
>> Format Name: cont-en
>> Compiler: pdfe-TeX (Extended Mode)
>> Input File Name: cont-en.tex
>> Output File Name: cont-en.efmt
>> Exclude has to be unchecked
>>
>> - MikTeX updates the formats automatically (if it does). If it
>> doesn't, the "standard ConTeXt" ways fail anyway and searching for
>> files doesn't always work either
>
>
>> - I often have problems after upgrading ConTeXt, but I can hardly tell
>> you what to do. I try all the different tricks (updating filename
>> database, building the formats, ...) without any success, but after
>> two days it simply works again by some black magic.
>
>
>Here is what I do (I am not sure even if this is the correct thing to 
>do, but seems to work)
>
>Make a tree called pragma-texmf. Download cont-tmf.zip and 
>cont-fnt.zip and unzip them in pragma-texmf. Go to MikTex options and 
>add pragma-texmf as a tree. Move it up so that it is the first tree. 
>This way whenever any program searches for a context related file, it 
>finds it in the pragma-tree. Now go and recreate the formats. 
>Everything works (well except mptopdf the program, but that is not 
>critical for me). To keep in sync with context's pace of development, 
>simply download the entire cont-tmf tree whenever a newer version is 
>released. I have not managed to convince texsync to just download 
>texmf tree, and I do not really care about downloading a big zip.
>
>This makes me feel whether it is a good idea to have miktex and 
>context for windows (from the pragma site) in parallel. I use cygwin 
>and context for windows only seems to work from cmd.exe and not 
>bash.exe. I tried to convert setuptex.sh to setuptex.bash, but could 
>not get to work. So, I settled with the method of downloading the 
>relevant trees and things work (by black magic, as you said)
>
>Aditya
>_______________________________________________
>ntg-context mailing list
>ntg-context@ntg.nl
>http://www.ntg.nl/mailman/listinfo/ntg-context

Re: New Installation under miktex, not working

[Ralph Roberts]

Thanks! That worked for me.

--Ralph
>
>> If you want to make formats, go to MikTeX options -> TeX formats ->
>> choose cont-en -> Edit ...
>> Here are the values that I have (it may be that I changed any of them
>> manually, I don't remember):
>> Format Name: cont-en
>> Compiler: pdfe-TeX (Extended Mode)
>> Input File Name: cont-en.tex
>> Output File Name: cont-en.efmt
>> Exclude has to be unchecked
>>
>> - MikTeX updates the formats automatically (if it does). If it
>> doesn't, the "standard ConTeXt" ways fail anyway and searching for
>> files doesn't always work either
>
>
>


-- 
--------------------------
Ralph Roberts, CEO
aBOOKS / 1VIDeo / Creativity, Inc.
65 Macedonia Road
Alexander, North Carolina 28701

828-252-9515, 828-255-8719 fax
800-472-0437 orders only
websites: http://abooks.com
            http://1vid.com

Re: New Installation under miktex, not working

[Aditya Mahajan]

<--- On Jan 16, Mojca Miklavec wrote --->

> Aditya Mahajan wrote:
>
>> Make a tree called pragma-texmf. Download cont-tmf.zip and
>> cont-fnt.zip and unzip them in pragma-texmf. Go to MikTex options and
>> add pragma-texmf as a tree. Move it up so that it is the first tree.
> /.../
>> This makes me feel whether it is a good idea to have miktex and
>> context for windows (from the pragma site) in parallel. I use cygwin
>> and context for windows only seems to work from cmd.exe and not
>> bash.exe. I tried to convert setuptex.sh to setuptex.bash, but could
>> not get to work. So, I settled with the method of downloading the
>> relevant trees and things work (by black magic, as you said)
>
> I have them (MikTeX and the stand-alone from Pragma) in parallel
> without any problem. I created "pragmatex.bat" (visible by PATH) which
> calls the setuptex.bat (or whatever the script in the stand-alone
> distr. is called). The two distros don't interfere at all. Once I call
> "pragmatex", all the sources and executables are chosen from the
> stand-alone tree when I compile the documents. (But thanks for the
> idea of making another texmf-pragma tree! I always managed to break
> something when mixing MikTeX and original files from Pragma, that's
> why I preferred to leave things as they are and use another distro
> instead.)

I once again tried to install the standalone context distribution and 
it works :-). So, I deleted context from the miktex distribution and 
now use the standalone distribution. Hopefully, it will be more 
stable than in miktex.

> I'm not sure, but I guess that you would need tetex to run it from
> bash. Don't ask me about the numerous (still unsolved) problems I had
> just because the ruby executable is only available under cygwin at the
> university.

I had a similar problem. I needed cygwin ruby because there are 
certain ruby packages (e.g. narray) that I could get to work with 
cygwin ruby without any hassle but do not work with the ruby one click 
installer. But cygwin ruby and context do not go together. I was 
actually following your thread on comp.lang.ruby hoping that someone 
will come up with a solution, but no suggestion worked. What I finally 
did was, download and install the one click installer, but removed it 
from the PATH. So when I am working on other projects, I get the 
cygwin ruby which works fine. I added a line to setuptex.bat that adds 
the one-click windows ruby to the front of the path. So when a context 
program asks for a ruby, it gets the windows version and everything 
works fine. The only drawback is that I can not use rxvt+bash, and 
have to use cmd.exe

Aditya
-- 
Aditya Mahajan, EECS Systems, University of Michigan
http://www.eecs.umich.edu/~adityam || Ph: 7342624008

Re: New Installation under miktex, not working

[Hans Hagen]

Aditya Mahajan wrote:

> I had a similar problem. I needed cygwin ruby because there are 
> certain ruby packages (e.g. narray) that I could get to work with 
> cygwin ruby without any hassle but do not work with the ruby one click 
> installer. But cygwin ruby and context do not go together. I was 
> actually following your thread on comp.lang.ruby hoping that someone 
> will come up with a solution, but no suggestion worked. What I finally 
> did was, download and install the one click installer, but removed it 
> from the PATH. So when I am working on other projects, I get the 
> cygwin ruby which works fine. I added a line to setuptex.bat that adds 
> the one-click windows ruby to the front of the path. So when a context 
> program asks for a ruby, it gets the windows version and everything 
> works fine. The only drawback is that I can not use rxvt+bash, and 
> have to use cmd.exe


why the one-click installer, just take the 2-4 meg version compiled with 
the native ms compiler; that's the one i use and it works perfectly (for 
years now)

http://ftp.ruby-lang.org/pub/ruby/binaries/mswin32/

Hans