Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!decvax!harpo!seismo!hao!hplabs!sri-unix!PCarah.ES@PARC-MAXC.ARPA
From: PCarah.ES@PARC-MAXC.ARPA
Newsgroups: net.micro.pc
Subject: Re: DOS 2.0
Message-ID: <13594@sri-arpa.UUCP>
Date: Thu, 10-Nov-83 22:10:00 EST
Article-I.D.: sri-arpa.13594
Posted: Thu Nov 10 22:10:00 1983
Date-Received: Mon, 14-Nov-83 23:57:41 EST
Lines: 30

In answer to your message in Info-IBMPC # 85..

1. No, you can't install or remove device drivers within the design of
the operating system without rebooting.  The system does maintain links
and if you know where the list head is, you can add or remove character
device drivers.  This would result in memory getting badly disorganized,
however.  The same for block device drivers would be very difficult,
since at INIT time the DOS allocates several tables that are not part of
the driver for each block device, and it uses these tables rather than
the device driver headers to find out what devices exist and which
driver to use, etc.

2. You may be losing COMMAND.COM because of the bug in the PASCAL
library routine ENTX6S (which has been referred to before in this list).
The JLE finding out whether there is 64K available should be a JBE.
This applies to PAS1, PAS2, FOR1, FOR2, the PASCAL library, and any
program written using that library.  The FORTRAN library ENTX6S has that
bug fixed a different way.  There are two general symptoms from this -
the compilers will often not work at all on a machine with more than
512K of memory, and they always cover up COMMAND.COM.  Fixes for this
have been detailed before on this list, if you need help send me a
message, since I have found a much easier way to fix it than IBM
documents (which will also work in general for patching .EXE files from
DEBUG).

3. I can't help you - I have never tried a redirection on a program that
terminates and stays resident, but I am sure the problem comes from
that.

-- Pete Carah