Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
can't find the boot record in ram
0 views
Skip to first unread message
Anon
Oct 20, 2004, 9:26:33 PM10/20/04
to
I used a program called Hexit to check bytes 7C00 and 0600 but
couldn't find anything resembling a boot record. I tried this after
booting from a floppy. And after booting to dos (with command prompt
only) on a win95 box.
couldn't find anything resembling a boot record. I tried this after
booting from a floppy. And after booting to dos (with command prompt
only) on a win95 box.
Robert Redelmeier
Oct 20, 2004, 10:27:30 PM10/20/04
to
You shouldn't expect to find anything. It gets overwritten
by later boot stages. If you want to see a boot record,
read it off a floppy with DEBUG.EXE .
-- Robert
Florian Liebig
Oct 21, 2004, 3:17:13 PM10/21/04
to
dear anon,
have a quick look at you real mode interrupt vector table.
then, you must have a look at int 0x19, what is called "bootstrap"
loader.
in really most cases, this gives you a SEG:OFF to the loader previously
used.
microsoft did this since dos2.x or 3.x upwards 'til todays'
win95-dos7.x.
So it comes, that a int0x19 performs a "quick boot" but doesn't work in
every way!!
florian.
have a quick look at you real mode interrupt vector table.
then, you must have a look at int 0x19, what is called "bootstrap"
loader.
in really most cases, this gives you a SEG:OFF to the loader previously
used.
microsoft did this since dos2.x or 3.x upwards 'til todays'
win95-dos7.x.
So it comes, that a int0x19 performs a "quick boot" but doesn't work in
every way!!
florian.
0 new messages