Problem with NT4 SP3 system volume after reading from WinXP
Hi,
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 :)
Ys
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 :)
Ys
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Now we only need to find out why starting a foxpro app on this computer crashes it to a blue screen :)
Ys