[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#379628: Recommend to tag #380226 "etch-ignore"; #379835 downgraded to important

FYI. I received this mail sent to #379628.

Looks like this needs further investigation. I was not aware that XP used 
3.1 too. However, I doubt that I am the person who is going to do it.
I can see if I can tighten the check if the NTFS partition is really Vista 
or an older version of Windows.

On 10/12/06, Frans Pop wrote:
> There are currently three RC bugs open related to the resizing of NTFS
> 3.1 partitions as created by Windows Vista.
> - #379628: ntfsresize - upstream bug, but disputed; I can reproduce it
>            reliably though; needs confirmation by someone else


> I have today uploaded a version of partman-partitioning that includes a
> check for NTFS 3.1 partitions and refuses to resize in that case;
> earlier NTFS partitions (NT, XP, 2000) should still be resizable.

XP use NTFS 3.1 too. You've just blocked resizing of most users' NTFS

> IMO #379628 should not be ignored for Etch and it would be nice if
> someone else would try to either reproduce the bug or prove me wrong.
> There is plenty of information in the BR for that. Without a working
> ntfsresize, resizing NTFS 3.1 partitions is a no-op anyway.

I've done some web searching and I have a wild guess about pcmcia.sys.

After resizing, please boot into Vista's install disk and into the
recovery console. From there, rename "system32\drivers\pcmcia.sys"
(e.g. to "pcmcia.bak") and reboot. Does Vista now boots? What about
Safe mode?

Another solution I found on the net was for Win2003 and was replacing
"ntldr" and "ntdetect.com" with the ones on the install disk. The best
projection on a newly installed Vista would be to replace the files
with files from Win2003 or XP. Does this solve the case?

If any of the above two workarounds help, then this is clearly an MS
bug and should be fixed in Vista. Only if Vista final does not fix it,
we can add a workaround to ntfsresize by checking the MD5 of the
relevant files.


> Cheers,

Yuval Fledel

Attachment: pgp9SJpYvehKB.pgp
Description: PGP signature

Reply to: