Hi Szaka, On Sat, 2006-11-11 at 21:43 +0200, Szakacsits Szabolcs wrote: > Hi, > > On Sat, 11 Nov 2006, Andree Leidenfrost wrote: > > > I had another look and used F6->F8->Safe Mode with Command Prompt. In > > the attached screenshot you can see that it stops after it loaded > > crcdisk.sys. > > > > Google says other people experience the same. > > Thanks, I've checked some Google posts. > > There are quite many different scenarios when boot hangs at crcdisk.sys. > This is how the drivers should be loaded usually around crcdisk.sys: > > Loaded driver \Windows\System32\Drivers\spldr.sys > Loaded driver \Windows\System32\Drivers\Mup.sys > Loaded driver \Windows\system32\drivers\disk.sys > Loaded driver \Windows\system32\drivers\CLASSPNP.SYS > Loaded driver \Windows\system32\drivers\crcdisk.sys > Loaded driver \SystemRoot\system32\drivers\Wdf01000.sys > Loaded driver \SystemRoot\system32\drivers\intelppm.sys > Loaded driver \SystemRoot\system32\drivers\uagp35.sys > > One can notice the path change right after loading crcdisk.sys. What is > SystemRoot? There isn't such directory on NTFS. Microsoft says "Set the > current directory to the systemroot folder of the Windows installation you > are logged on to." > > There is also one important thing to know. The windows boot process is an > old legacy. It's not a modern one, for example, what Linux has. In the > early boot phrase a mini ntfs driver loads the real drivers and at some > point the boot process starts to use them. > > Apparently this point is right after crcdisk.sys, so that's why so many > people have problem there. Millions of things can go wrong during the > driver "switch" and they indeed do go wrong but the fault will always point > to crcdisk.sys. > > All posts I've seen was old, or if it wasn't then it used old Vista Beta. > > GParted was used with Vista RC1 in the below article. Same hang but chkdsk > fixed the boot problem: > http://opensource.apress.com/article/163/taking-a-look-at-vista-part-iii > > If one could send me the two ntfs images, before and after running chkdsk,
The problem for me is how to run chkdsk after the resize. If you can tell me how I'll do it. > then I could add the needed support, suppose the problem is indeed due NTFS > changes. Instructions how to create the images are here: > > http://wiki.linux-ntfs.org/doku.php?id=ntfsclone#store_only_ntfs_metadata How about I do this before and after the resize? > But the most important thing would be still to reproduce the problem with > the latest Vista, so we could confirm that we indeed have a problem. Which > means that we still haven't received any information how ntfsresize works > with the latest Vista. > > > Just in case anybody reading this would be interested: If anyone has a > > Vista installation that I could destroy in Sydney in order to confirm > > the issue on the final version, drop me a message! > > Btw, it would be also nice to test ntfsclone, if one is interested: > > 1) ntfsclone --overwrite vista.img vista_partition > > 2) zero the entire vista partition (not the disk!): > > dd if=/dev/zero of=vista_partition > > 3) ntfsclone --overwrite vista_partition vista.img > > 4) vista should boot fine Yep, tried that and it works fine. :-) > Cheers, > Szaka -- Andree Leidenfrost @ Debian Developer Sydney - Australia
signature.asc
Description: This is a digitally signed message part
