Bradley Miller wrote:
> 
> Actually I'm making progess:
> 
> /dev/hdb1   *         1      1652  13269658+   c  Win95 FAT32 (LBA)
> 
> Looking a bit closer:
> 
> Disk /dev/hdb1: 255 heads, 63 sectors, 1651 cylinders
> Units = cylinders of 16065 * 512 bytes
> 
>      Device Boot    Start       End    Blocks   Id  System
> /dev/hdb1p1   ?    120513    235786 925929529+  68  Unknown
> Partition 1 does not end on cylinder boundary:
>      phys=(288, 101, 46) should be (288, 254, 63)
> /dev/hdb1p2   ?     82801    116350 269488144   79  Unknown
> Partition 2 does not end on cylinder boundary:
>      phys=(0, 13, 10) should be (0, 254, 63)
> /dev/hdb1p3   ?     33551    120595 699181456   53  OnTrack DM6 Aux3
> Partition 3 does not end on cylinder boundary:
>      phys=(324, 77, 19) should be (324, 254, 63)
> /dev/hdb1p4   ?     86812     86813     10668+  49  Unknown
> Partition 4 does not end on cylinder boundary:
>      phys=(335, 78, 2) should be (335, 254, 63)
> 
> Partition table entries are not in disk order
> 
> So I don't know for sure, but I'm sure that ontrack disk manager might be
> causing a problem.  Not a problem . . . preparing to blow that away now.
> 
> -- Bradley Miller

I recommend cfdisk for a console partition tool.  It is the most picky
about stuff, and if it doesn't complain, your partitions should be 
useable by nearly anything.

Hal