Topic: Compiler Support for LateX / MikTeX (1 of 6), Read 221 times
Conf: Compiler support
From: Peter Rejto
Date: Friday, September 12, 2003 09:10 AM

Hi,
I am running my compiler called Miktex from the Vpw tool menu. It works fine, the DOS window stays open and I can read some of the error messages.

Now I would like to read all of the error messages by scrolling back the window.

--

Comment: use latex.vcs. instructions how to set up compile.cnf can be found at BOF(included since 6.0).

Rest of thread deleted. F.H.

 

Topic: Compiler Support for LateX / MikTeX (2 of 6), Read 61 times
Conf: Compiler support
From: Peter Rejto
Date: Friday, September 26, 2003 04:57 PM

Fritz or Christian:

Thanks to both of you for the latex.vcs file. It has been working like a charm for me for some time! That is to say, it has been working on my fixed drive.

Now the problem. I also have a removable drive and I have just copied my Vedit Home Directory to my removable hard drive. On this removable drive, I can not compile using latex.vcs. I get an error message listing various possible reasons; can not shell to DOS, not enough memory, can not find compiler.

So, I tried the simplest possible version of the System
command from your :COMPILE: subroutine. Specifically,
I escaped into command mode and typed:
System("latex myfile",DOS)
This did the trick.

Now I need your help in doing the next step. I got hung up
on, I believe, the Text Register Address 96. Where does this come from? In short can, you help me with making the vcs.tmp file?

Thanks again,

-peter.

 

Topic: Re: Compiler Support for LateX / MikTeX (3 of 6), Read 57 times
Conf: Compiler support
From: Christian Ziemski
Date: Saturday, September 27, 2003 02:48 PM

On Fri, 26 Sep 2003 16:58:43 , you wrote:

>Now I need your help in doing the next step. I got hung up
>on, I believe, the Text Register Address 96.
>Where does this come from?
>In short can, you help me with making the vcs.tmp file?

T-Reg 96 holds the Project directory.
It's set in C-INIT.VDM. ;-)


BTW: After copying your VEDIT directory to another drive you should
carefully check your VEDIT.INI there to have the correct drive letters
for all entries.

Christian

 

Topic: Re: Compiler Support for LateX / MikTeX (4 of 6), Read 52 times
Conf: Compiler support
From: Peter Rejto
Date: Monday, September 29, 2003 02:20 AM

On 9/27/2003 2:48:40 PM, Christian Ziemski wrote:
>On Fri, 26 Sep 2003 16:58:43 , you
>wrote:

>BTW: After copying your VEDIT directory
>to another drive you should
>carefully check your VEDIT.INI there to
>have the correct drive letters
>for all entries.


Thanks Christian,

You really did put me on the right track. I checked my project directory, E:\Texvols, and noticed that the MSDOS95W.PIF file, or something like that, called a batch file which did set the "wrong path". Now it works like a charm.


Of course, I would prefer to move this batch file to a vedit sub directory. I tried to create a c:\vedit\batch directory and move the file there. However, this gave erratic results.

It seems that a local .pif file used to shell out to DOS,
can call only a local batch file. Is this on purpose?


Thanks again,

-peter.

 

Topic: Re: Compiler Support for LateX / MikTeX (5 of 6), Read 51 times
Conf: Compiler support
From: Christian Ziemski
Date: Monday, September 29, 2003 08:04 AM

On 9/29/2003 2:20:50 AM, Peter Rejto wrote:

>I checked my project directory,
>E:\Texvols, and noticed that the
>MSDOS95W.PIF file, or something like
>that, called a batch file which did set
>the "wrong path". Now it works like a
>charm.

MSDOS95W.PIF calls COMMAND.COM and not any batch file!
What batch file do you mean?
(My crystal glas seems to be damaged.)

In general: Don't alter the distributed PIF files!

Christian

 

Topic: Re: Compiler Support for LateX / MikTeX (6 of 6), Read 60 times
Conf: Compiler support
From: Peter Rejto
Date: Monday, September 29, 2003 07:15 PM

On 9/29/2003 8:04:08 AM, Christian Ziemski wrote:
>On 9/29/2003 2:20:50 AM, Peter Rejto
>wrote:
>
>>I checked my project directory,
>>E:\Texvols, and noticed that the
>>MSDOS95W.PIF file, or something like
>>that, called a batch file which did set
>>the "wrong path". Now it works like a
>>charm.
>
>MSDOS95W.PIF calls COMMAND.COM and not
>any batch file!
>What batch file do you mean?
>(My crystal glas seems to be damaged.)
>
>In general: Don't alter the distributed
>PIF files!

Christian,

MSDOS95W.PIF->properties->program

gave me a pop up window. This window, in turn, gave me the option of running a batch file. In the old days I was using emTeX and it used a lot of environment variables. This is the way Professor Eberhard Mattes wrote it, so I had to set these environment variables Then I switched to MikTex, and I added the MikTeX path. I called my batch file SET_BOTH.BAT,
since I can use it to set the environment variables for both compilers.

Actually, I should have called mu original batch file, SET_BOTHE.BAT since it did set all environment variables for the drive E:. When I copied this batch file, which resides in E:\TeXVols to C:\TeXVols on my removable hard drive it
gave me trouble. When I adapted SET_BOTH.BAT to the drive C:
everything was OK.

I hope that my description makes sense.

Actually, I think that it is really cool, that I can go back and run my old DOS based emTeX in the same project directory.

PS.( I am running Windows 2000 on my office machine. There I also use drive C: for my project directory. There the SETBOTHE_BAT file did not cause any problems.)

-peter.