Xref: utzoo comp.sys.ibm.pc:32275 comp.binaries.ibm.pc.d:3978
Path: utzoo!attcan!utgpu!watmath!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc.d
Subject: Re: Help with strange partitioning--logical drive setup
Message-ID: <8466@bsu-cs.bsu.edu>
Date: 28 Jul 89 20:05:51 GMT
References: <3216@uwovax.uwo.ca>
Reply-To: dhesi@bsu-cs.bsu.edu (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 47

In article <3216@uwovax.uwo.ca> 2014_5001@uwovax.uwo.ca writes:
>I have my hard drive partitioned into a DOS3.3 partition and a DOS2.11
>partition (Why?  Simply as DOS2.11 gives me more free RAM, which I do need).

Here is an alternative way of using both MS-DOS 2.11 and 3.3 on the
same machine.

Use only one big partition for both.

Install 2.11 on the hard disk.

Create a boot floppy for booting 3.3.  On the boot floppy, in the
config.sys file, specify

	  shell = C:\msdos3\command.com C:\msdos3 /e:2000 /p

(assuming C: is your hard disk).  (Adjust parameters as needed.)  On
the C: disk copy the COMMAND.COM from MS-DOS 3.3 to the \MSDOS3
subdirectory.  In the autoexec.bat file on the boot disk, set PATH to
include directories on the hard disk that contain MS-DOS 3.3 programs,
not 2.11 programs.

When you boot from the hard disk, you get 2.11.  When you boot from the
boot floppy, you get 3.3.  In either case you use the same files.  If
you have trouble making 2.11 read a hard disk formatted by 3.3 (might
happen, might not), just use 2.11 to format the hard disk.

If you format using 2.11, you may get big clusters on the disk causing
more fragmentation.  If at all possible format with 3.3, or use one of
the patch schemes that I've seen floating around here and there to get
smaller clusters with 2.11.

An alternative is to boot 3.3 from the hard disk and boot 2.11 from a
floppy.  This is not so good, because 2.11 has a bug that causes it to
always reload COMMAND.COM from the boot disk no matter what the shell=
statement says in config.sys.  This will then require you to keep the
boot disk in drive A: all the time, or be annoyed by messages asking
you to insert COMMAND.COM disk in drive A:.

On some machines you can extend available memory to a little more than
640K by using some of the empty memory space.  This is highly
system-specific and may require changing jumpers in your system, and I
have no idea how to do it, but I know that some people have done it
successfully.
-- 
Rahul Dhesi <dhesi@bsu-cs.bsu.edu>
UUCP:    ...!{iuvax,pur-ee}!bsu-cs!dhesi