RIS BSOD

  • Thread starter Thread starter Joe
  • Start date Start date
J

Joe

Ok,

A little pre and post thank yous to everyone here for
helping me so far... thank you!

Worked out that last problem of my .inf NIC drivers not
getting properly installed, and even managed to get the
SCSI drivers loaded on my own after that, wow!

Next problem, I have our PowerEdge 1750's PXE booting
like crazy fools, its great! So I figure I am a
*&^#$@^'ing expert by now right... And then Moore
strikes back as I plug the NIC drivers for our Precision
650's into the i386 folder and point the new
Workstation .sif file to those drivers, so now I can use
separate installs for my Render Nodes and Workstations.
Cool. 650 PXE boots fine, slower than the 1750's. I
point it to the right install and it starts up the
installation, loads all the drivers in the windows setup,
gets RIGHT up to the Starting Up Windows part and a super
fat BSOD hits me...

I have no idea where the hell this came from or why, so
far I havent even seen a post with BSOD and RIS in the
same sentence. Anyways, I am trying to avoid creating an
entire new i386 folder and with that a copy of the node
installer, since I am not using, and dont want to use
imaging..

Anyone know the answer to this one?

Joe
 
DAMN... damn damn damn damn.

Well, I figured out the problem, the OTHER 1750 is using
the txtsetup.oem and the whole TEXTMODE directory and
loading the SCSI drivers for the scsi drive its using,
whereas my Precision 650s have no scsi and as such BSOD
when they try and load that driver. wow, how crappy.

Anyone have links/workarounds for this?

Joe
 
Back
Top