From:	leathm AT solwarra DOT gbrmpa DOT gov DOT au (Leath Muller)
Message-Id:	<199701200621.QAA19579@solwarra.gbrmpa.gov.au>
Subject:	[opendos] Re: OpenDOS to be released next week! (fwd)
To:	geneb AT deltasoft DOT com (Gene Buckle)
Date:	Mon, 20 Jan 1997 16:21:11 +1000 (EST)
Cc:	opendos AT mail DOT tacoma DOT net
In-Reply-To:	<3.0.32.19970119202302.00692934@mail.wa.net> from "Gene Buckle" at Jan 19, 97 08:23:05 pm
Sender:	owner-opendos AT mail DOT tacoma DOT net

> >Problem 1:  The boot sector loads the kernel so to boot from the opendos
> >kernel, it would have to be called something else instead of MSDOS.SYS and
> >IO.SYS.  I assume it will be DRDOS.SYS and DRIO.SYS or OPENDOS.SYS,
> >OPENIO.SYS.  However this still leaves the problem of the bootsector
> >loading the kernel.  Looks like we're going to be installing LILO or some
> >other boot manager.
 
> The kernel files are IBMIO.SYS and IBMDOS.SYS.
 
> There should be no problems with normal boot managers.
 
> One thing that DOES need to be kept in mind is that OpenDOS goes nuts over
> Win95 long file names.  CHKDSK thinks they're lost clusters.  Don't use
> CHKDSK /F, the disk optimizer or the backup software if you're dual booting
> win95.  It won't ruin the disk, but it sure will screw up the long file
> name tables. ;)

Question: what is considered a normal boot manager? 95's? NT's? Lilo?
Is installing OpenDOS going to kill my other bootable stuff?

At the moment, the only way to have everything on my system is to install
in the following order:

DOS 6.22	- Used for compatibility if required
Win 95	- Used for DirectX 3 programming
Win NT	- Used for all other Win Programming
Linux		- Using UMSDOS for compatibility. As this does'nt have a boot
			  loader in this form, I don't think this really counts... :)

Can I just install the OpenDOS from here, without losing _full_ functionality
to all the other software???

Leathal.

- Raw text -