On Sat, 28 Oct 2000, Bob Nestor wrote:

> The "void" entries in the map seem to be a new approach in Apple CDs.  I 
> don't recall seeing anything like that before on the Apple CDs I've 
> dumped.

Right. It's because there has been a lot of confusion about what to do on
non-512-byte-block devices. Also, part of the problem is that MacOS at
certain levels only deals with 512-byte blocks. So drivers have to have
translation layers to go from 2K to 512-byte blocks & back. When MacOS is
looking at the 512-byte block side, it expects a 512-byte block partition
map. Icky, isn't it? :-)

> >Since when is this an error??? :-)
> 
> The code in this utility has the ability to sort the Map Entries by 
> starting block number. Then if there is space no accounted for on the 
> device it issues this error.  According to the Apple doumentation all 
> space (other than Block Zero) should be covered by an entry in the Map.  

Right. You have to cover the whole disk.

> Sorting the entries made it easier to force an order that would match the 
> way NetBSD/mac68k finds the partitions.  So the answer is it's not really 
> an error, but if there are gaps that aren't mapped on the disk it is a 
> potential error.

Ahhh....

Take care,

Bill