RE: parted's cp command for FAT32, and LBA/CHS/NTLDR missing woes

[Andrew A.]

True, but at a minimum NTLDR/NTDETECT are known to need to stay within a 
boundary, might as well at least give it a *chance* to
work.  Your solution of not moving anything up (whenever possible) is also good.

A.

-----Original Message-----
From: Szakacsits Szabolcs [mailto:address@hidden
Sent: Thursday, September 16, 2004 12:18 PM
To: Andrew A.
Cc: address@hidden
Subject: RE: parted's cp command for FAT32, and LBA/CHS/NTLDR missing
woes



On Thu, 16 Sep 2004, Andrew A. wrote:

> So, just to be crystal clear, you feel that the fixes to #1 are
> addressed,

It was definitely addressed and so far it seems to be fixed.

> but that the parted resizing code *could* move NTLDR past cylinder
> 1024?

Andrew could comment, confirm that but that's my guess. When I wrote
ntfsresize then I made sure nothing gets moved upwards due to these
issues.

> Sure would be nice to add some smarts to parted which would
> keep a given list of files within a given boundary :-)

Impossible. Even Microsoft itself couldn't give such a list of files to
commercial vendors (partitioner, defragmenter, etc). I guess any driver
writer can hook anything during boot that's why it's basically impossible
to provide such a list.

        Szaka