[U]EFI+GPT: There is a Microsoft article about switching motherboard mfrs from
BIOS to [U]EFI, and possibly about removing BIOS emulation. EFI uses GPT (see
wikipedia) for partitioning and only includes MBR as a "signature" to show that
the GPT is there, and for some compatibility with older programs that only
recognize MBR. currently it is in use in 64-bit systems from what I have read
(but exactly what kind?).
EFI can be partially in ROM and the rest possibly on Disk, if there are enough
features. the partition EFI resides on is hidden from view by partitioning
programs unless you use the MOUNTVOL program (might be a windows program). EFI
tends to be large - too large to fit on ROM. I know it is currently used on
Itanium servers.
removing BIOS means no INT 10H functions, no INT21H functions, no INT13H
functions, probably no DPMI, etc.
I was unable to read the messages about SEABIOS, but if that means UEFI could
be replaced with it so we could still use a BIOS (?) maybe this is a
possibility? sure sould be interesting customizing the bios to the motherboard
though.
UEFI+GPT is supported in Vista and 7, though that is probably irrelevant here.
In another article, Microsoft said it would not switch over to UEFI until it
had established itself as a standard. so it may be quite a while yet.
LARGE SECTOR DRIVES: There is also the issue of large-sectored disks coming
after the 2TB drive, if anyone plans on purchasing one of those. by
large-sectored I mean drives that have 1024, 2048, 4096 byte sectors. Microsoft
has warned of this. large-sectored drives allow you to use the existing
32-bit-LBA MBR until the UEFI+GPT becomes established as a standard.
what large sectors affects is disk management utilities such as fdisk and
chkdsk and defrag, and partition growing utilities that have hard-coded
512-byte sectors into their code (like I used to).
expect the next size up from 2TB to break the 2TiB barrier in several months.
http://www.microsoft.com/whdc/system/platform/firmware/uefireg.mspx
"Future Requirements to Enable UEFI Platforms without CSM
First-generation 64-bit UEFI platforms typically contain some form of limited
BIOS emulation such as a CSM to preserve the ability to run 32-bit operating
systems and operating systems that do not support EFI. Existing Windows
dependencies on INT 10 video BIOS functions also require a CSM.
To reduce the need for a CSM and improve boot times in the future, we are
collaborating with the industry to eliminate this dependency and encourage
changes to system firmware.
We have already identified the following future firmware requirements:
• GOP. Windows uses the GOP to obtain a frame buffer pointer at boot time
for use during operating system runtime. GOP support is essential to replace
VGA support and avoid the requirement for a CSM in future versions of Windows.
• EFI Capsule Services. Future versions of Windows can use the EFI
UpdateCapsule() service to persist information across a system restart and pass
that information to the firmware. This would potentially let the system report
and/or respond to certain error conditions if the boot device or operating
system were damaged or otherwise unavailable."
Jim Michaels<jmich...@yahoo.com>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
