Nova verze emtexu (Beta9)
Petr Sojka
sojka at erebor.ics.muni.cz
Wed Jan 12 16:53:51 CET 1994
Dobry den,
drtiva vetsina z Vas pouziva TeX (emTeX) pod OS MSDOS ci OS/2
a proto Vas bude zajimat nasledujici novorocni darecek:
On Thu, 30 Dec 1993, Eberhard Mattes wrote:
> emTeX beta 9 is now available:
>
> ftp.uni-stuttgart.de:/pub/tex/systems/msdos/emtex/betatest/texb9.zip
>
emTeX beta 9 je k dispozici na ftp.muni.cz:pub/tex/emtex/em.beta/texb9.zip
(soubor obsahuje binarky pro vsechny procesory a ma asi 1 MB).
Na emtex listu bylo komentovany nektere problemy s touto novou verzi
a byly zverejneny i nektere opravy chyb. Relevantni zpravy
z emtex listu prikladam nize.
Zdravi
Petr Sojka <sojka at muni.cz>
P.S. Z duvodu chyby v konfiguraci maileru (sendmail) na MU
mi nebyla dorucovana veskera posta v obdobi 21/12/93 -- 11/1/94 :-(.
Tem, kteri mi v teto dobe psali (i prostrednictvim techto disk.
skupin) prosim o znovuposlani posty.
A ted uz nasleduje avizovana posta z emtex listu:
>From owner-emtex-user at chemie.fu-berlin.de Tue Jan 11 20:22:53 1994
From: Eberhard Mattes <mattes at azu.informatik.uni-stuttgart.de>
Date: Sat, 8 Jan 94 21:07:33 +0100
To: emtex-user at methan.chemie.fu-berlin.de
Subject: Re: Unexpected change of behaviour in /openin w.e.f emTeX-beta9
Philip Taylor writes:
> The following TeX program has run without problem for some time, but
> failed to run w.e.f. emTeX-beta9; the problem lies in the \openin
> statement at l.~08, which used to successfully open a file located
> in a parallel sub-directory, ..\scr; this no longer works and I have
> had to move the file to the working directory, and to replace l.~08
> with the modified \openin as shewn; could anyone explain this change
> in behaviour, please, or is it a bug?
It's a bug, to be fixed in beta 10. emTeX thinks that "../scr/life.all"
contains a name with two dots (such as chapter3.tex.aux) and refuses
to open the file. In one place, I forgot to make ".." an exception to
that rule. I think it works correctly under OS/2.
Eberhard Mattes (mattes at azu.informatik.uni-stuttgart.de)
--------------
>From owner-emtex-user at chemie.fu-berlin.de Tue Jan 11 20:21:50 1994
From: Eberhard Mattes <mattes at azu.informatik.uni-stuttgart.de>
Date: Sat, 8 Jan 94 21:07:45 +0100
To: emtex-user at methan.chemie.fu-berlin.de
Subject: Fix for VSHIELD /SWAP (emTeX386 beta 9)
Here's a fix for the problem with VSHIELD /SWAP of emTeX386 beta 9.
Even if you don't use VSHIELD /SWAP, you should apply this fix. Copy
the following lines to a file named EMXLFIX.BAT:
------------------------------- cut here -------------------------------------
@echo off
if "%1"=="" goto usage
if not exist %1 goto usage
if "%2"=="" goto start
:usage
echo Usage: emxlfix PROGRAM.EXE
echo.
echo Note: PROGRAM.EXE must be in the current working directory
goto end
:start
if exist emxlfix.tmp del emxlfix.tmp
ren %1 emxlfix.tmp
if not exist emxlfix.tmp goto usage
echo e 10a 21 00 21 >emxlfix.dbg
echo e 111 02 >>emxlfix.dbg
echo w >>emxlfix.dbg
echo q >>emxlfix.dbg
debug emxlfix.tmp <emxlfix.dbg
ren emxlfix.tmp %1
del emxlfix.dbg
echo Done
:end
------------------------------- cut here -------------------------------------
You should put the file into a directory which is listed in the PATH,
for instance c:\emtex. Then, change to the emTeX directory:
cd \emtex
and let EMXLFIX.BAT patch TEX386.EXE:
emxlfix tex386.exe
If you have other programs that use EMXL.EXE to load EMX.EXE, you
might want to apply EMXLFIX.BAT to these programs, too. However,
EMXLFIX.BAT does not check whether it's patching EMXL.EXE or something
else (EMX.EXE, for instance). Do not apply EMXLFIX.BAT to programs
which don't contain EMXL.EXE!!!
Note that EMXLFIX.BAT needs DEBUG.COM. I don't know whether later DOS
versions come with DEBUG.COM or not -- I tried EMXLFIX.BAT with MS-DOS
3.31 and with OS/2 2.1.
Thanks to Dan Luecking for analyzing the problem!
Eberhard Mattes (mattes at azu.informatik.uni-stuttgart.de)
-------------------
>From owner-emtex-user at chemie.fu-berlin.de Tue Jan 11 19:46:03 1994
Date: Mon, 10 Jan 1994 09:50:48 +0200
From: tp1jhei at pkvx2.physik.uni-erlangen.de
To: emtex-user at fu-berlin.de
Subject: rsx and emtex b9
Hi emTeXers,
I have bound emtex386 with emxl as discribed by EM and put rsx in the
emtex directory. Everything seemed to work fine: I could use tex386
with dos/emx and with windows/rsx. But ... when I run tex386 from windows
the time tex get from the operating system is incremented 8 hours.
This sometimes produces a wrong date when using \today in a tex file.
Has somebody observed this, too?
Juergen
----------------
>From owner-emtex-user at chemie.fu-berlin.de Tue Jan 11 21:44:44 1994
From: Eberhard Mattes <mattes at azu.informatik.uni-stuttgart.de>
Date: Fri, 7 Jan 94 14:58:05 +0100
Subject: Re: Final report: emx/texb9
Dan Luecking writes:
> -- installing vshield WITH the /swap option causes my machine to freeze
> when I try to run tex386 without modification.
Does vshield swap programs out of low memory when another program is
called? That will break emxl.
Eberhard Mattes (mattes at azu.informatik.uni-stuttgart.de)
----------------------
>From owner-emtex-user at chemie.fu-berlin.de Wed Jan 12 13:51:20 1994
Date: Wed, 12 Jan 1994 08:59:22 +0100
From: Thomas Herter <Thomas.Herter at mch.sni.de>
Subject: Re: EMX and related programs
Roland Schilling writes:
> Looking at the postings made during the last 2 weeks there was a lot of
> discussion about EMX and related programs in connection with the new
> beta 9 release of EmTeX. Can somebody be so kind to explain what the
> purpose of EMX etc is? There is nothing about this in the EMX.DOC that
> was comming together with the beta 9 release. The only explanation I
> could find in the servers is that EMX is a DOS extender (what is this?)
> and that the EMX programs are used for porting UNIX programs to the PC.
> But what is then the advantage of having EMX loaded together with EmTeX
> (e.g. tex386) under MS-DOS?
>
> Many thanks in advance for any helpful hints and explanations.
Hallo Roland,
as you know, DOS has still the historic, bizarre barrier of 640KB
space room. The huge number of installations makes this really
unparalleled badly designed system to the first choice for the
(partly absolutely non-computer oriented) users. For developers
DOS is a nightmare with pseudo science about ``kinds od memories''
etc. A DOS extender is roughly speaking a program able to switch
DOS into a mode using a linear and large address area mostly of
the 386 or later processor. Bigger DOS application use commonly
some extender or other method to access the couple of megabytes
today's every personal computer have. The well known
commertial products come from PharLap and Rational. The Metaware
C-Compiler bases on PharLap's extender, the Watcom C-Compiler bases
on the Rational's extender.
In the public domain exist a coulple of extenders.
The probably most important extenders are:
go32: from D.J. Delorie
emx: from E. Mattes
Both extenders were used to port the GNU software to DOS (and in case of
EMX to OS/2). The 32-bit Versions of emTeX were compiled with
the EMX-system. Since EMX can not run with MS-Windows, it is possible
now that EMX under Windows invoke implicitely another extender called
RSX for the so called DPMI-interface. Of course, you have to obtain
and properly install RSX-extender in addition to the emTeX-Package.
This is the reason for the discusion about EMX and extenders.
I hope this short info helps.
Thomas
Thomas Herter, SNI Muenchen (thomas.herter at mch.sni.de) tel +89 636 49973
------------------
>From owner-emtex-user at chemie.fu-berlin.de Tue Jan 11 19:51:06 1994
Date: Wed, 5 Jan 1994 12:36:20 -0600 (CST)
From: "Daniel H. Luecking" <luecking at uafhp.uark.edu>
Subject: Re: emTeX 3.1415 beta 9 now available
On Thu, 30 Dec 1993, Eberhard Mattes wrote:
> emTeX beta 9 is now available:
>
> ftp.uni-stuttgart.de:/pub/tex/systems/msdos/emtex/betatest/texb9.zip
>
I posted a message yesterday saying this was an unbound version. It
almost certainly is not (at least in a sense).
Apparently my problem is that (unlike beta 8) it is bound to emxl rather
than emx. Thus, when invoked, tex386.exe looks for emx.exe somewhere in my
PATH. My problem was three-fold: (1) I had set up a test installation of
beta 9, where the required version of emx.exe was in c:\temp\emtex which
was not in my PATH; (2) I had not set the variable EMX, and (3) there was a
version of emx.exe in my PATH, but it was the wrong version.
I tried setting EMX, but I still couldn't get things to work. Perhaps
I did something else wrong after that. In any case, I finally have things
in an acceptable state (tex386 bound with emx.exe into a stand-alone
executable) with the following sequence of acts:
(1) I acquired emxrt.zip from
ftp.uni-stuttgart.de::pub/systems/os2/emx_0.8h
(this is from memory, use the command "quote site index emxrt" to get
the exact directory)
(2) I invoked emxbind.exe with the following command lines:
<path>emx.exe <path>emxbind.exe -x tex386.exe tex386.out
<path>emx.exe <path>emxbind.exe -b <path>emx.exe tex386.out tex386.exe
Here <path> is the path to the current directory, which contained the
correct version (0.8h) of emx.exe as well as the program emxbind.exe
which came in emxrt.zip and tex386.exe. This is not necessarily the most
efficient way to proceed (that is, there might be a single command
line that will do it).
It somewhat surprised me (but maybe it shouldn't have) that emxbind
requires emx.exe in order to run. Certainly I never found it in the
documentation. Probably it is much like tex386 beta 9 in that it needs to
be able to find the correct version of emx.exe to run and it is assumed
that you have things properly configured to begin with. I only guessed how
to proceed after several trials caused my machine to reboot. There are
about a dozen UNsuccessful acts between (1) and (2) that I do not
reproduce here for reasons of space.
Thanks to those who responded.
Dan Luecking
_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
luecking at comp.uark.edu || Department of Mathematical Sciences
DL24794 at uafsysb.uark.edu || University of Arkansas
|| Fayetteville, Arkansas 72701-1201
More information about the csTeX
mailing list