Problem with NT4 SP3 system volume after reading from WinXP


I know this is a pretty esoteric topic, but a mate at work decided he would backup the system partition with Windows NT 4 Server Servicepack 3 from a newly acquired computer file by file on his Windows XP Home and now it just doesn't start up anymore in the original computer.

How to reproduce:
1. Install Windows NT 4 Server on a new harddrive
2. Put the harddrive with the system volume in a Windows XP Home computer (eg. USB-IDE Interface) and access it (just reading is sufficient).
3. Put the harddrive back into the original computer.
4. Stop 0x0000007B (last line is ntfs.sys).

So my ideas on why WinNT4 fails are:
a) Windows XP Home set some NTFS v5 specific flags on the NTFS v4 (v3.1 according to Partitionmagic) system volume causing the ntfs.sys (NT4 SP3) to hickup.
b) Windows XP Home set the LDID in the bootsector of the partition and now the LDID on the disk doesn't match the LDID saved in the registry.
On a sidenote: Where is the system volume identified in the registry of Windows NT 4 SP 3? All I can find are entries pertaining to the harddrive itself (eg. Type of HDD, Manufacturer, Model type as reported by HDD, Serial number as reported by HDD, Code number as reported by HDD).

Any other ideas?

Or any ideas on how to get this thing booting in the original computer again?

I'm really out of ideas here :)

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
The problem is clear... the solution is POSSIBLY Easy.

By putting the drive in a system that supports NTFS 5, the drive was effectively upgraded to NTFS 5.
Windows NT required Service Pack 4 or later to read NTFS 5 drives.

What MIGHT fix this is to get a copy of NTFS.SYS from Service Pack 4, 5, or 6 for NT and replace the existing one.  Then, UPGRADE TO SERVICE PACK 6a IMMEDIATELY!  (Yell at your friend for not doing this a LONG time ago).

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ysreAuthor Commented:
Hehe, thanks a lot, works like a charme.
Now we only need to find out why starting a foxpro app on this computer crashes it to a blue screen :)

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.