Index
> OS Construction > All-in-one vs. one-for-each bootstrap loader |
| Author |
|
|
mikegonta 17 Jan 2009, 00:26
[ Post removed by author. ]
Last edited by mikegonta on 28 Jan 2009, 09:04; edited 1 time in total |
|||
17 Jan 2009, 00:26 |
|
|
baldr 17 Jan 2009, 21:15
mikegonta,
BIOSes already use FAT12 FS, for flash functions (so BPB is used by BIOS  ).
If boot loader is a BIOS concept, why Windows checks for 55 AA @ 1FE and EB xx 90/E9 xx xx @ 0? OK, enough rant. That's what I meant: bootstrap loader is a part of file system, thus it can be hard-coded to boot specifically using corresponding disk geometry and file system. I don't see much sense to copy bootstrap loader between different disks (with different geometry and/or file system). Another big question is: will BIOS boot from 1024/2048/…/16k bytes-per-sector floppy? I'll check it later. _________________ "Don't belong. Never join. Think for yourself. Peace." – Victor Stone. |
|||
|
17 Jan 2009, 21:15 |
|
|
mikegonta 17 Jan 2009, 22:11
[ Post removed by author. ]
Last edited by mikegonta on 28 Jan 2009, 09:04; edited 1 time in total |
|||
|
17 Jan 2009, 22:11 |
|
|
neville 17 Jan 2009, 23:00
The answers:
1. No, the bootloader has nothing to do with any filesystem. Yes, it should be versatile e.g. loading FAMOS
2. It can. For example, booting a CD using floppy emulation. The BIOS thinks its a FD with a storage capacity of 18 MiB (18,874,368 bytes). The usual gemoetry assumed is CHS=256/2/18 with 2048-byte sectors. 3. Yes. As mikegonta has said, the BPB is pretty much ignored by the BIOS. _________________ FAMOS - the first memory operating system |
|||
|
17 Jan 2009, 23:00 |
|
< Last Thread | Next Thread > |
Forum Rules:
|