> You wouldn’t need to have the OS on a hard drive, so, partition would no
longer
need to exist. All the flash system needs to know is the disk geometry.
The words “disk geometry” are obsolete. They are nothing more then a trick to
support the obsolete BIOS API of int 13h (well, even BIOSes - not EFI -
obsoleted them by int 13h/43h long ago) and obsolete MS-DOS and its remnants.
The disk CAPACITY is a true word.
Also the idea of abolishing partitions does not look good.
The OS
could be distributed in compact flash or similar. Also, the chipset would
belong to
the flash and it shouldn’t be visible from the outside except via a compact
API.
So, I will not be able to reinstall the OS or to have several OSes co-installed
with a boot choice?
the hardware manufacturer would need to know the hardware detail of the
motherboard.
It is correct, and thus we have ACPI and AML bytecode.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
Actually, the “geometry” is whatever interface the disk subsystem
gives you. A series of blocks is a geometry too.
Alberto.
On 2 Jan 2004 at 10:23, Maxim S. Shatskih wrote:
> You wouldn’t need to have the OS on a hard drive, so, partition
> would no
longer
> need to exist. All the flash system needs to know is the disk
> geometry.
The words “disk geometry” are obsolete. They are nothing more then a
trick to support the obsolete BIOS API of int 13h (well, even BIOSes -
not EFI - obsoleted them by int 13h/43h long ago) and obsolete MS-DOS
and its remnants.
The disk CAPACITY is a true word.
Also the idea of abolishing partitions does not look good.
>The OS
> could be distributed in compact flash or similar. Also, the chipset
> would
belong to
> the flash and it shouldn’t be visible from the outside except via a
> compact
API.
So, I will not be able to reinstall the OS or to have several OSes
co-installed with a boot choice?
> the hardware manufacturer would need to know the hardware detail of
> the motherboard.
It is correct, and thus we have ACPI and AML bytecode.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@ieee.org
To unsubscribe send a blank email to xxxxx@lists.osr.com
‘Disk Geometry’ in the PC OS world generally refers to the obsolete CHS
information that the old DOS-compatible hard drives used along with DOS and
the BIOS to access the disk. As Max stated, this is obsolete, and current
drives have a ‘capacity’ a ‘block size’ and a linear ‘block address space’,
and hide any ‘geometry’, that is any knowledge of physical platters, heads,
cylinders etc. from normal access methods.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@ieee.org
Sent: Friday, January 02, 2004 6:47 AM
To: Windows System Software Devs Interest List
Subject: Re: Re:[ntdev] An interesting artibcle on EFI
Actually, the “geometry” is whatever interface the disk
subsystem gives you. A series of blocks is a geometry too.
Alberto.
On 2 Jan 2004 at 10:23, Maxim S. Shatskih wrote:
> > You wouldn’t need to have the OS on a hard drive, so, partition
> > would no
> longer
> > need to exist. All the flash system needs to know is the disk
> > geometry.
>
> The words “disk geometry” are obsolete. They are nothing
more then a
> trick to support the obsolete BIOS API of int 13h (well,
even BIOSes -
> not EFI - obsoleted them by int 13h/43h long ago) and
obsolete MS-DOS
> and its remnants.
>
> The disk CAPACITY is a true word.
>
> Also the idea of abolishing partitions does not look good.
>
> >The OS
> > could be distributed in compact flash or similar. Also,
the chipset
> >would
> belong to
> > the flash and it shouldn’t be visible from the outside
except via a
> > compact
> API.
>
> So, I will not be able to reinstall the OS or to have several OSes
> co-installed with a boot choice?
>
> > the hardware manufacturer would need to know the hardware
detail of
> > the motherboard.
>
> It is correct, and thus we have ACPI and AML bytecode.
>
> Maxim Shatskih, Windows DDK MVP
> StorageCraft Corporation
> xxxxx@storagecraft.com
> http://www.storagecraft.com
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@ieee.org To
> unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as:
xxxxx@hollistech.com To unsubscribe send a blank email to
xxxxx@lists.osr.com
Mark, remember I’m a computer science teacher. When I talk about design
subjects, I never restrict myself to what’s available in a Wintel environment. What
I mean by “geometry” is whatever the disk subsystem presents itself as:
cylinder/head/track, sequence of blocks, whatever. So, to me, “capacity”, “block
size”, and “address space” are what I’d call the “geometry” or a disk.
It actually doesn’t need to have platters and heads to have geometry. Even a
compact flash has a geometry.
Alberto.
On 2 Jan 2004 at 8:17, Mark Roddy wrote:
‘Disk Geometry’ in the PC OS world generally refers to the obsolete
CHS information that the old DOS-compatible hard drives used along
with DOS and the BIOS to access the disk. As Max stated, this is
obsolete, and current drives have a ‘capacity’ a ‘block size’ and a
linear ‘block address space’, and hide any ‘geometry’, that is any
knowledge of physical platters, heads, cylinders etc. from normal
access methods.
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of
> xxxxx@ieee.org
> Sent: Friday, January 02, 2004 6:47 AM
> To: Windows System Software Devs Interest List
> Subject: Re: Re:[ntdev] An interesting artibcle on EFI
>
> Actually, the “geometry” is whatever interface the disk
> subsystem gives you. A series of blocks is a geometry too.
>
> Alberto.
>
>
> On 2 Jan 2004 at 10:23, Maxim S. Shatskih wrote:
>
> > > You wouldn’t need to have the OS on a hard drive, so, partition
> > > would no
> > longer
> > > need to exist. All the flash system needs to know is the disk
> > > geometry.
> >
> > The words “disk geometry” are obsolete. They are nothing
> more then a
> > trick to support the obsolete BIOS API of int 13h (well,
> even BIOSes -
> > not EFI - obsoleted them by int 13h/43h long ago) and
> obsolete MS-DOS
> > and its remnants.
> >
> > The disk CAPACITY is a true word.
> >
> > Also the idea of abolishing partitions does not look good.
> >
> > >The OS
> > > could be distributed in compact flash or similar. Also,
> the chipset
> > >would
> > belong to
> > > the flash and it shouldn’t be visible from the outside
> except via a
> > > compact
> > API.
> >
> > So, I will not be able to reinstall the OS or to have several OSes
> > co-installed with a boot choice?
> >
> > > the hardware manufacturer would need to know the hardware
> detail of
> > > the motherboard.
> >
> > It is correct, and thus we have ACPI and AML bytecode.
> >
> > Maxim Shatskih, Windows DDK MVP
> > StorageCraft Corporation
> > xxxxx@storagecraft.com
> > http://www.storagecraft.com
> >
> >
> > —
> > Questions? First check the Kernel Driver FAQ at
> > http://www.osronline.com/article.cfm?id=256
> >
> > You are currently subscribed to ntdev as: xxxxx@ieee.org To
> > unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as:
> xxxxx@hollistech.com To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@ieee.org
To unsubscribe send a blank email to xxxxx@lists.osr.com