Name: aniljo4u Date: June 13, 2005 at 07:19:38 Pacific Subject: NTFS partition OS: Windows NT CPU/Ram: Xeon 2.0 MHZ
Comment:
Guys, I have strange problem. One of the nls files from windows NT box got corrupted. So i was running out of time was not having erd and bootable cd, i put the nt hard disk on a windows 2000 box. I could reinstall the nls file back. Now the nt box is running fine and working problem but only problem is it throws a message that system32 folder is corrupt and unreadable run chkdsk utility. When i run the chkdsk utility it shows a message the ntfs version is changed so cannot run this utility. When i look at system32 folder it shows only certain files. But the files required for running windows nt is getting loaded as seen in the taskbar.
My guess is that Windows 2000 converted your version of NTFS from 4 to 5 on the NT drive while it was reading it. Windows 2000 is particularly rude about doing this without asking.
W2K forcibly converts any ntfs4 to ntfs5 on any drive/partition it finds in a given system. You have no say in the matter...
NT4 requires sp4 or later to be installed in order to access ntfs5. Problem is that (usually) the sp must be installed before W2K converts the ntfs4 to ntfs5...
If the system is working OK apart from this error message(?) I'd be inclined to live with it - pending a re-install of NT (or an overwrite/repair installation)?
Possibly you may be able add in sp4 (perhaps even sp6a) and it will come right...; although I'm guessing you already sp4 or later already installed?
Yes guys the ntfs version has been changed. I already have sp6 installed. Will reinstalling sp6 resolve the problem. Has anyone encountered similar problem and resolved the same successfully.
I'm inclined to doubt that re-appying sp6 will resolve it; but it might not hurt to try?
Failing which I guess a re-install of NT4 is required; which is what initial discussions re' NT4 and W2K suggested in 2000 (Windows 2000 Magazine - Summer edition) - when W2K has effectively disabled/wrecked NT4 (the ntfs4 to ntfs5 event...).
As already moted by folks here, it won't hurt to try ? The worst that can happen is that the situation remains unchanged/unresolved, that things remain as now?
Otherwise the repair-install (as mooted by Wanderer) may resolve it.
The windows2000mag articles were not that hopefull about resolving this type of problem other than by full re-install of NT4. Which having said I am inclined to think the repair-installation may work nonetheless; it is after all (more or less) a fresh installation going over an existing one?
The only issue that "may" crop up (during a repair-instllation) is that of NT4 being "unable" to overwrite the system32 folder (if by some chance it's now a version that NT doesn't like as it were)? No real logic in this last thought I know but then???
Try sp6a; if it fails then go the repair-installation?
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE