I need to install NT 4.0 server on new hardware (2.0 higher processor, 1GB
memory, Intel motherboard, 80GB hard drive). The purpose is to put together
a new server as a BDC in our domain so we can replicate all domain
information. We will then promote it to the PDC and upgrade to an AD
environment. Our current PDC hardware is too old to support AD.
When I run the install setup disks, disk 1 runs fine. However, during Disk
2 setup..... as soon as it begins the FAT File System setup the computer
reboots and gives me a system disk error. I've used 2 different sets of
setup disks and I also tried the CD Rom - same result. I also swapped the
hard drive witha different one. I backed the server down from 1GB memory to
512K. What are the hardware limitations of NT 40 server or might this be a
different problem? Thank you.
Calvin - 07 Apr 2006 11:47 GMT
Hi KLW,
have a read here:
http://nt4ref.zcm.com.au/bigdisk.htm
This will get you started on the right track. The large HDD will be part of your
problem.
What is the motherboard chipset? I have heard reports of Intel chipsets above
the i845 family being 'troublesome' although I don't have any personal
experience to confirm or deny these rumours.
The RAM size may also be part of your problem. I know Microsoft have reported
problems relating to installing with a system with a large amount of RAM in
Knowledgebase article 177652 - "STOP 0x78 During Setup on a System With More
Than 1.792GB of Memory" but I doubt this is relevant in your system at 1GB of RAM.
Any additional info you can provide may help us solve your problem.
Calvin.
Klw - 07 Apr 2006 13:33 GMT
HI Calvin:
Thank you for the great response. The MB is an Intel D101GGC.
I'm not sure that the HDD is the problem - I'm not even getting that far in
the setup routine but I am in the process of swapping to 6GB drives to see if
that helps.
> Hi KLW,
>
[quoted text clipped - 17 lines]
>
> Calvin.
Klw - 07 Apr 2006 16:10 GMT
Changing the HDD made no difference so I swapped boxes (thereby downgrading
to an Asus Cubx-E MB. That worked. Must have been a chipset problem.
Thanks for your help.
> HI Calvin:
>
[quoted text clipped - 24 lines]
> >
> > Calvin.