Message-Id: <199705081003.MAA23473@grendel.sylaba.poznan.pl> Comments: Authenticated sender is From: "Mark Habersack" Organization: PPP (Pesticide Powered Pumpkins) To: randir Date: Thu, 8 May 1997 12:04:44 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: MS Word 6.0c problems Reply-to: grendel AT hoth DOT amu DOT edu DOT pl CC: opendos-support AT delorie DOT com References: In-reply-to: Precedence: bulk Once upon a time (on 8 May 97 at 0:29) randir said: > > Well I've played with the memory managers & all and it looks > like there is a problem with the OD kernel itself & or > the share program... Nah... it's not the kernel - see my other message. > Anyone have a good idea of how to set up both opendos & msdos? :) Just use the GRUB booter. It allows you to start by reading bootrecord from a file on your HDD. That way the only thing you do is to 1. fdisk /mbr, sys c: under OD and grab the bootrecord to a file (with NU DiskEdit for example) 2. Do the same with M$-DOG 3. Store OD & M$ COMMAND.COMs in different dirs (or just use 4DOS - recommened ;-) 4. Setup a boot menu for GRUB using the two previously created bootsector files This will work fine for M$-DOG and OpenDOS installed on the same partition. To further separate the two systems, use dconfig.sys (I think I remember the name right ;-)) to configure OpenDOS and the usual config.sys for M$-DOG. In autoexec you may differentiate between the two using the OS and VER variables set by OD when booting (or just use SET OPENDOS=1 in dconfig.sys - beware that (d)config.sys SETed variables are case-sensitive under OD). Hope that helps! ---------------------------------------------------------- Doctor said my liver looks like living with my lover - needs another time-out now. Like any sort of hero turning down to zero, standing out in any crowd. [snip] Dr. Finlay: And my advice is if you maintain this lifestyle you won't reach 30... ----