From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: OS Loader
Date:	14 Dec 2000 16:21:43 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	20
Message-ID:	<91as2n$rtf$1@nets3.rz.RWTH-Aachen.DE>
References:	<917e4i$8in$1 AT serv1 DOT iunet DOT it> <918brs$iri$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <91ak7i$l3h$1 AT serv1 DOT iunet DOT it>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 976810903 28591 137.226.32.75 (14 Dec 2000 16:21:43 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	14 Dec 2000 16:21:43 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

MarcoCorelli AT gtwparc DOT padova DOT ccr DOT it wrote:
> My problem is that the 1st file is my OSLoader and not IO.SYS !!! I can't 
> change this because the MBR Booter load the 1st file and lunch it.
> I need know where and how IO.SYS is loaded for launch MS-DOS!!!

But (even if you write 15 exclamation points after each sentence...)
that still doesn't explain why you insist on loading IO.SYS directly,
rather than a copy of an MSDOS boot block, which is how MSDOS is
supposed to be booted.

If you decide against doing it that way, it also up to you to bear the
consequences.

In principle, you should be able to disassemble the boot code and
understand how it loads and starts IO.SYS, but I wouldn't bet on that
to be easy, or even legal these days. Not with the "Digital Millenium
Copyright Act" stating that reverse engineering is forbidden.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -