Did you tried <F6> "trick"? For new hardware without correct proprietary
"OEM" installation media it is usually neccessary.

If you are not aware about <F6> trick - simply hit a few times <F6> key on
your keyboard while the first screen of NT setup is on with message like
"Setup is inspecting hardware...". This action has not any immediate effect,
but it will disable autodetecting of mass storage devices hardware and
autoloading of standard disk drivers. Because of this you will be asked for
these drivers sooner. Do not forget to install CD-ROM driver manually in
case it needs another driver than disks (it is usually autoloaded and
unlisted, but if autoloading is disabled...).

Another thing you shoudl to check is chance of bad HAL detection or even
need of special proprietary HAL driver. In such case OEM installation media
is necessary. There are workarounds - for ex. you can make unattended
installation script.

The most hard problem you will meet later will be fact that youll be not
able to install BDC this way correctly due "inaccessible" network adapter
during setup. WinNT does not recognize motheboard bridges technology untill
at least service pack 3 is applied and all new adapters connected to bus
located "behind bridge" cannot be accessed during setup.  But you cannot
setup BDC without connecting PDC during setup...

One solution is to build standalone (member) server and then use (expensive)
third party tool to promote it to BDC . Other solution is to add
(temporarily) any old fashioned net adapter that is "known" by NT setup to
machine and do network part of setup through this adapter.