Mail Archives: djgpp/2000/12/16/11:08:17
On 14 Dec 2000 16:21:43 GMT, Hans-Bernhard Broeker
<broeker AT physik DOT rwth-aachen DOT de> wrote:
>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.
I think OP is trying to say that either
o the DOS bootloader is not loading io.sys because it isn't in the
first directory entry, or
o OP really wants to load eir own bootloader instead of io.sys, and
then chain to io.sys.
>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.
Only when an "effective access control" (ask your attorney) is
present. Currently, this means encrypting the content with at least
2-bit XOR.
--
<O
( \ GNOME vs. KDE: the game!
X http://pineight.8m.com/nes.htm
This is McAfee VirusScan. Add these two lines to your signature to
prevent the spread of signature viruses. http://www.mcafee.com/
- Raw text -