On Mon, 5 Dec 2011 12:54:15 -0800
some body wrote:
> I sent this to freebsd-drives too but I think that might not be the right
> list for it so here it is: I am starting to learn how the kernel works and
> have started by going through the boot loader and I've noticed that between
> lines 21-32 i
On Mon, Dec 17, 2007 at 07:16:02PM +0530, M.Girish Rao wrote:
> Whats the memory location of start?
I'm going off of memory of my old x86 days, so be kind to me. :-) By
the look of it, it's BOOT_BOOT0_ORG, which is 0x600. I'm basing this on
the flags passed to cc (actually ld) during linktime.
Daniel O'Connor wrote:
I recently reinstalled Windows XP on my laptop (I barely use it but
occasionally it comes in handy :) and when I did the install it made
the base drive E (no idea why, and I couldn't see how to change it).
This is a well-known problem (at least to those who deal with
du
On 28-Oct-2003 Dan Strick wrote:
> On 22 Oct 2003 John Baldwin wrote:
>>
>> On 22-Oct-2003 Dan Strick wrote:
>> > I seem to have stubbed my toe on another nasty little bootstrap problem.
>> > My Gigabyte motherboard AWARD BIOS passes the wrong drive number in the
>> > %dl register when it invokes
On 22 Oct 2003 John Baldwin wrote:
>
> On 22-Oct-2003 Dan Strick wrote:
> > I seem to have stubbed my toe on another nasty little bootstrap problem.
> > My Gigabyte motherboard AWARD BIOS passes the wrong drive number in the
> > %dl register when it invokes the MBR bootstrap program, boot0.
> > Thi
On 22-Oct-2003 Dan Strick wrote:
> I seem to have stubbed my toe on another nasty little bootstrap problem.
> My Gigabyte motherboard AWARD BIOS passes the wrong drive number in the
> %dl register when it invokes the MBR bootstrap program, boot0.
> This forces me to configure the MBR bootstrap wit
On Fri, Oct 17, 2003 at 01:25:04PM +0930, Daniel O'Connor wrote:
> Basically, no. There is no room left in boot0 :(
>
> I think you could do it by squeezing down some text strings, and removing
> other [less common] entries though.
That's what I had to do when I special-cased it for serial conso
On Thursday 16 October 2003 23:41, John Reynolds wrote:
> After rebooting from there I see:
>
> F1 ??
> F2 FreeBSD
>
> at the prompt once the machine boots. My fuzzy memory seems to recall from
> years back that seeing ??'s was "bad" as it meant the boot mgr couldn't
> find out something it wan
On Thu, 20 Dec 2001 11:58:12 +0800 Leslie Jackson <[EMAIL PROTECTED]>
wrote:
> That means that BIOS saves the current drive number in register %dl??
>
> Could you give a hint about _where_ BIOS stores _what_??
> I've searched the google.com, but got no valuable resource.
a great tool for system
Mike Smith has written
>
>If you're confused about what the code is doing there; it's comparing
>the number of hard drives in the system (stored in the BIOS data area
>at 0x475) with the drive number that's in al to verify whether the
>drive number is valid according to the BIOS.
Thanks for your
John Baldwin wrote:
> No. It's the offset in memory of the number of hard drives in the BIOS. The
> BIOS has a data segment at 0x40, and at 0x40:0x75 (whose physical address is
> 0x475) it has a byte which is a count of the number of hard drives installed.
Specifically, Hiten, see:
Pag
On 15-Dec-01 Hiten Pandya wrote:
> hi,
> I found this piece of code in boot0.s, is it possible
> if you could explain me a bit about it.
>
> .set NHRDRV,0x475# Number of hard drives
>
> The hex value comes out to: 1141.
>
> Does that mean, that this is the amound of maximum
> hard driv
Hiten Pandya wrote:
> I found this piece of code in boot0.s, is it possible
> if you could explain me a bit about it.
>
> .set NHRDRV,0x475# Number of hard drives
>
> The hex value comes out to: 1141.
>
> Does that mean, that this is the amound of maximum
> hard drives a user can have o
13 matches
Mail list logo
