URGENT !! C_1252.nls error on NT TS:

[bstanbu]

After installing Office 2000 on one of our Terminal Servers (using the ORK recource tools) the server will not now boot;
With an error stating that the 'C_1252.nls' is missing or corrupt.

as we cannot locate a recovery disk for this server ( I know.... Doh ! ) I am wary about using the recovery option on the terminal Server CD to repair this file -

Any advice whatsoever would be very greatly appreciated !!

Regards,
Ben.

[shadow1]

nls is a local font file that can not just be copied. Needs to be installed. Hate to say it but if tou can't boot to reinstall, recovery might be your only option.

[bstanbu]

Shadow 1, thanks for your advice - I have however found the soloution - just incase anyone else finds this of interest:

SYMPTOMS
========

When you try to install Microsoft Office 2000, you receive the following
error
message when you restart the computer:

OS Loader V4.01

Disk I/O Error Stats=00000001

Windows NT could not start because the following file is missing or
corrupt:
c:\winnt\system32\c_1252.nls

The operating system will not start.

CAUSE
=====

This behavior occurs when all the following conditions are true:

- Your computer's operating system is Microsoft Windows NT 4.0 Workstation.

- The system partition or the boot partition of the Windows NT 4.0
Workstation
installation is greater than 7.8 gigabytes.

- The partition in question is formatted in the NTFS file system.

NOTE: This behavior may also occur with Microsoft Windows 2000 Professional
if
the computer BIOS does not support INT 13 extensions.

RESOLUTION
==========

Decrease the boot partition size and the system partition size below 7.8
gigabytes.

MORE INFORMATION
================

Office Setup replaces National Language Support files (C_*.nls). Microsoft
Windows NT 4.0 Workstation is limited to 7.8 gigabytes or less for the
system
partition and the boot partition. If one of these National Language Support
files is placed outside of the 7.8 gigabyte range, you receive an error
message
similar to the one in the "Symptoms" section of this article.

NOTE: This problem is not unique to Office 2000. This problem may occur
after you
install any software that replaces system files, and the conditions in the
"Cause" section of this article are met.

[shadow1]

Thanks for the info!! Learn something new everyday.