Windows nt 3.1 bad copy help

[imback]

I dunno how this happend, I just finished installing NT 3.1 But then this happend, i would like some help.

[computebrute]

Why don't you use some common sense, and just replace the bad file?

[imback]

How and where?

[rhobariii]

"Please boot the restore disk to repair this problem"
It says it all. (Unless there is no restore disk)

[krosos8]

I think there is a problem with registry (unless something else was stored at this location in older NT systems). Did any interruptions happen during the installation? What VM are you using? You can also try installing from a different copy of NT 3.1.

[Wheatley]

Why don't you use some common sense, and just replace the bad file?

It's hard to replace a screwed-up SYSTEM hive in a freshly installed system....

[computebrute]

Why don't you use some common sense, and just replace the bad file?

It's hard to replace a screwed-up SYSTEM hive in a freshly installed system....

There's a restore disk there. It makes life easier.

[Wheatley]

And where will you pull a perfect SYSTEM hive from? You need to reinstall anyway.

[computebrute]

And where will you pull a perfect SYSTEM hive from? You need to reinstall anyway.

why are you capitalizing SYSTEM? I see the word perfectly.

[user99672]

Probably because that's the name of the file, 'SYSTEM'.

[louisw3]

SYSTEM is one of the registry files.

So your filesystem is corrupt. did you try this on a fat32 disk?

Anyways it's hopeless, you have to format and re-install.

[esc1010]

Old OSes don't take much time to install. Probably 15-20 Minutes on a decent PC.

[yksoft1]

You might be installing NT3.1 using Win9x DOS and installed that on a FAT32 volume.. In NT3.1, both ntldr and fastfat.sys don't support FAT32 (FAT32 is fully supported only on NT 5.x and later).

[3155ffGd]

Are you using Virtual PC and a multi-core system? VPC doesn't like that. Set the affinity to a single core via Task Manager.