I
Ian Douthwaite
I hope you guys can help with this because it's driving me nuts.
It's the old "The operating system image does not contain..." blah blah
problem.
I've just inherited a network of non-brand PCs and I want to deploy a RIS
image from a Windows 2000 server. The server is running SP4 and I built an
RISETUP image on it using a Windows 2000 Professional (SP4) CD, (I've also
tried with the SP3 hotfix files as well).
The PC's have an Intel 82562 NIC chip on them which, when you install the
supplied drivers works fine as an Intel Pro 100 VM connection.
The PCs don't have PXE boot ROMs. Of course the Win2000 RBFG won;t recognise
them either but I got a third-party floppy-based MBA boot agent which boots
up fine and connects to RIS for log on and image selection. I should add
that if I install one PC from the Win2K Pro (SP4) CD it does not manage to
install a network driver even though it recongises there is an Ethernet
device present.
I've done all the things I can find to do with respect to making sure I've
got the latest drivers for the Intel NIC and the .inf file specially inteded
by Intel for use with RIS installations. I've got this in both the i386
directory and the $OEM$ chain for the image (there's only one image, but I
tried earlier with two -- no change)
I've stopped and started BINL, SIS, removed and reinstalled RIS and even
demoted and re-promoted the DC which is also the RIS server (though that
was for fun really). I've deleted al the PNF files and anyhting else I could
find with the DEV_2449 device id in it apart from e100bnt5.inf.
The behaviour is always the same:
- can boot ok using the thrid-party MBA floppy
- contacts the RIS server, gets logged on and select os image
- starts to load Machine Identification Data and then fails with the good
old message after three minutes or so.
I'm guessing three possibilities:
1. I just haven't done everything in the right order (though this seems
remote)
2. The network device id is not being correctly passed to the loader which
runs as part of the text mode setup (but how can you possibly figure this
out?
3. It's something else.
I know there's a few contributors here who really know this stuff well so
I'd be gratefuyl if anyone has an inspiration.
Cheers
Ian
It's the old "The operating system image does not contain..." blah blah
problem.
I've just inherited a network of non-brand PCs and I want to deploy a RIS
image from a Windows 2000 server. The server is running SP4 and I built an
RISETUP image on it using a Windows 2000 Professional (SP4) CD, (I've also
tried with the SP3 hotfix files as well).
The PC's have an Intel 82562 NIC chip on them which, when you install the
supplied drivers works fine as an Intel Pro 100 VM connection.
The PCs don't have PXE boot ROMs. Of course the Win2000 RBFG won;t recognise
them either but I got a third-party floppy-based MBA boot agent which boots
up fine and connects to RIS for log on and image selection. I should add
that if I install one PC from the Win2K Pro (SP4) CD it does not manage to
install a network driver even though it recongises there is an Ethernet
device present.
I've done all the things I can find to do with respect to making sure I've
got the latest drivers for the Intel NIC and the .inf file specially inteded
by Intel for use with RIS installations. I've got this in both the i386
directory and the $OEM$ chain for the image (there's only one image, but I
tried earlier with two -- no change)
I've stopped and started BINL, SIS, removed and reinstalled RIS and even
demoted and re-promoted the DC which is also the RIS server (though that
was for fun really). I've deleted al the PNF files and anyhting else I could
find with the DEV_2449 device id in it apart from e100bnt5.inf.
The behaviour is always the same:
- can boot ok using the thrid-party MBA floppy
- contacts the RIS server, gets logged on and select os image
- starts to load Machine Identification Data and then fails with the good
old message after three minutes or so.
I'm guessing three possibilities:
1. I just haven't done everything in the right order (though this seems
remote)
2. The network device id is not being correctly passed to the loader which
runs as part of the text mode setup (but how can you possibly figure this
out?
3. It's something else.
I know there's a few contributors here who really know this stuff well so
I'd be gratefuyl if anyone has an inspiration.
Cheers
Ian