🚀 go-pugleaf

I see a lot of partitions where the partition table and the boot sector
sector length appears to be either 1 or 2 cylinders longer than the actual
disk (as detected by the BIOS).

Perhaps this is a miscalculation by the Windows/DOS install routine.

I see this an awful lot when fix hdds (i.e. partition table data against
BIOS CHS values).

Example:

int 13h get disk info returns

995,31,63     (disk has 2007936 sectors)

but partition table says

128    6    0,1,1 - 996,31,63     63      2009889

and boot sector bpb.huge_sector_count = 2009889

or

128    6    0,1,1 - 997,31,63     63      2011905

and boot sector bpb.huge_sector_count = 2011905

Could it be that this disk has this problem and the disk has become full and
scandisk or DOS is trying to r/w these non-existent clusters (i.e. the last
or penultimate cylinder).

This may or may not be the source of the problem, but in any event I would
be interested to hear of anyone who knows why this happens (and it happens
an awful lot).

Kindest regards,

Jem

David Harley wrote in message <7a0u7p$vt$1@bliss.lif.icnet.uk>...
>David Longley (David@longley.demon.co.uk) wrote:
>: I've  had  a problem on a few machines (some IDE and  some  SCSI)
>: which  makes me suspect a virus. Scandisk reports that  it  can't
>: read  the last cluster on the drive .. I have ended up having  to
>: FDISK and reformat. I scanned with DR SOl and Nortion and neither
>: detected anything..
>
>I see this quite often on systems with large disks partitioned into
>two. I wouldn't personally trash a drive because of a trivial
>SCANDISK message: it's a very limited tool. Run something more
>powerful like NDD as a diagnostic, but be careful if it actually
>detects a possible problem.
>
>--
>David Harley
>D_Harley@iname.com
>http://webworlds.co.uk/dharley/
>"Opinions are free: advice is free: consultancy costs...."
>