I am not familiar with a self-generated WinPE image, not exactly sure what it is. But sure, I'd love a copy of the script and check it out. It would be great if it did what I needed to in order to get my iSCSI support working on nVidia NICs.
Just for a good (short) read, check out http://etherboot.org/wiki/hardwareissues. If you scroll down to nForce, there is an explanation of how nVidia NICs act differently than all the others in regards to communication with the PCI bus. This was the only info I could find that even remotely explained the strange situation I was seeing. -Steve On Thu, Jan 3, 2013 at 4:31 AM, Marek Salwerowicz <[email protected]> wrote: > W dniu 2012-12-31 17:19, Steve Cross pisze: > >> My next goal is to attempt to roll in the actual nVidia drivers and >> requires services into the WinPE to see if I can add support for the >> iSCSI installation on a nVidia chipset. I've got two HTPCs that both >> run nVidia ethernet onboard and I would really like to switch them to >> iSCSI. If I do manage to pull it off somehow, I'll writeup something >> and send it back in here so that others can know in the future. > > > Have you tried booting a self-generated WinPE image (using the ADK)? > You should be able to add additional drivers (for your nVidia NIC) to the > image. > If you would like, I could provide you my script used for booting the WinPE > > The only difference is that usually I'm using the Intel hardware (chipset > and NICs) > > -- > Marek Salwerowicz > > _______________________________________________ > ipxe-devel mailing list > [email protected] > https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel _______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
