Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!sdd.hp.com!spool.mu.edu!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!unido!ira.uka.de!rusmv1!ifistg!ifi!mattes From: mattes@azu.informatik.uni-stuttgart.de (Eberhard Mattes) Newsgroups: comp.text.tex Subject: Re: tex3.1 on MSDOS machine Message-ID: Date: 22 Feb 91 10:30:25 GMT References: <9505@sbsvax.cs.uni-sb.de> Sender: news@ifistg.uucp Followup-To: comp.text.tex Organization: IfI, Univ. Stuttgart, W Germany Lines: 32 In-reply-to: arno@fb14vax.cs.uni-sb.de's message of 21 Feb 91 13:18:47 GMT arno writes: > I'm trying to compile tex3.1 on an IBM compatible machine using > Keisuke Yoshida's gcc C-compiler for MSDOS. I've managed to compile > the program, but, unfortunately, it will not run correctly. To be > more precise: [...] > 2. I obtain a version of VIRTEX. But when starting it with the > lplain.fmt file, it won't give me the LaTeX version number, and > so on. Moreover, it doesn't recognize any LaTeX command. Are you sure you're opening the fmt file in binary mode? > - Is there anyone who got tex3.1 working on a 386-based MSDOS machine > such that tex uses the protected mode and the 386 machine instructions? I got it working. emTeX/386 is in alpha-testing state. > - Does anyone know about bugs of the gcc mentioned above? I've compiled it with gcc (and my own DOS extender) without problems. But I'm not using WEB2C and I'm not using P2C. I'm using my own Pascal-to-C translator. And I am using my own C library. > - Does tex depend on byte ordering? No. > - Are there any functions that have to be changed in order to make tex > work under MSDOS? (Note that I have already changed the code in such > a way that reading and writing of files takes place in binary mode) Look for binary mode when opening binary files (dvi file, format file, tfm files). -- Eberhard Mattes (mattes@azu.informatik.uni-stuttgart.de)