Hi!
12-Сен-2004 14:08 [EMAIL PROTECTED] (Luchezar Georgiev) wrote to
[EMAIL PROTECTED]:
>> I don't understand this. SYS writes 0/FF only into its own images,
>> builtin into SYS executables. And, if _after_ SYS someone will change
>> boot loader, then 0/FF value also will be replaced. Where is trouble?
LG> The trouble is that most SYSes don't bother to set this value - they just
LG> copy the whole data area from the old boot sector and replace only the
LG> code and OEM ID. So the FF remains there. Verified.
_And_ their boot code reuse this field? If not, then this in
unimportant, what those SYSes remain in 24h field.
>> I think, current behavior (use fixed drive# in case of A:/C: and BIOS
>> value in other cases, including HDs), is good and flexible way.
LG> Currently, fixed drive number 0 is used for floppies, but for hard disks,
LG> FF is used, which is troublesome if FreeDOS is replaced by another DOS
LG> later.
Well, right now I look at boot code of MS-SYS6, and found, that it not
uses 24h offset itself, but pass value from there to kernel. I not check
what SYS does with original 24h field, but image inside SYS contains 80h
value, so I doubt that MS-SYS preserves this field.
LG> Now Jeremy added an option to set the boot drive to an arbitrary
LG> value, which solves the issue. But FF is still default for hard disks.
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
