home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: gnu.emacs.help
- Path: sparky!uunet!van-bc!ubc-cs!unixg.ubc.ca!unixg.ubc.ca!gyan
- From: gyan@unixg.ubc.ca (Gyan P. Sinha)
- Subject: Re: DVIVGA incompatible with DEMACS?
- Message-ID: <gyan.715561300@unixg.ubc.ca>
- Sender: news@unixg.ubc.ca (Usenet News Maintenance)
- Nntp-Posting-Host: unixg.ubc.ca
- Organization: University of British Columbia, Vancouver, B.C., Canada
- References: <ARA.92Sep2235248@camelot.ai.mit.edu> <ARA.92Sep3040002@camelot.ai.mit.edu>
- Distribution: comp
- Date: Thu, 3 Sep 1992 23:01:40 GMT
- Lines: 45
-
- In <ARA.92Sep3040002@camelot.ai.mit.edu> ara@zurich.ai.mit.edu (Allan Adler) writes:
-
-
- >In an earlier posting, I reported some difficulties with dvivga, demacs
- >and ansi.sys. on an 80386 MSDOS system. I thought that dvivga was incompatible
- >with ansi.sys, the latter being necessary for me to run demacs.
-
- >Since my earlier posting, I have made some progress. I reinstalled
- >ANSI.SYS or TANSI.SYS and rebooted. Then I went directly into dvivga
- >and it worked fine. Therefore, DVIVGA IS NOT INCOMPATIBLE WITH ANSI.SYS
- >or TANSI.SYS.
-
- >Then I used demacs to edit a TeX file. It let me edit the file but gave
- >me an error message, as it always does, because I don't have the .el file
- >for TeX. Then I exited demacs. I should mention that I have commented out
- >everything in the _emacs file for demacs.
-
- >After exiting demacs, I tried again to look at the dvi file with dvivga
- >and this time the problem returned: the numeric keypad and the arrow
- >keys did not work properly. Therefore, DVIVGA IS INCOMPATIBLE WITH
- >DEMACS.
-
- >In other words, running demacs seems to change something from the way
- >ansi.sys had it to something else that is incompatible with the way
- >dvivga uses the keypad and arrow keys.
-
- >Any insights into this mess will be welcome.
-
- >Allan Adler
- >ara@altdorf.ai.mit.edu
-
- Yes, DEMACS does do screw up the hardware state of the machine. In all
- fairness, it isn't DEMACS but the extender GO32.EXE which is at fault,
- I think. I don't know if this still happens, but an earlier version of
- GO32.EXE would disable the the floating point exception handler after it
- ran, so my fortran program if it came up against an overflow or divide
- by zero, would lock up the machine. In a fresh session, before DEMACS
- was run, a runtime error message would ensue normally.
-
- I suggest you concentrate on GO32 as the likely culprit. I use OS/2
- 2.0 now and am very happy with emacs port available for it. There are
- nice previewers available as well. OK, I've made my pitch. :-).
-
- Gyan P. Sinha
- UBC, Vancouver.
-