Alright, i'm all caught up on the email chin. A few differences between our setup:
-- I am running an older series Intel NUC / BOXDCCP847DYE -- I am running Windows 7 on my NUCs but would be willing to try 2012 if I can get my hands on a copy. -- I think the biggest difference between our setups is the fact that I am running a copy of iPXE from a few years ago (chainloading undionly.kpxe dated 07/01/2013). If I can find the time tonight after work, I will try upgrading that to the latest version of iPXE and see if it breaks my setup or not. I will let you know what I find. Steve *Steve Cross* [email protected] On Thu, Oct 30, 2014 at 1:27 PM, Floris Bos <[email protected]> wrote: > Hi Steve, > > On 10/30/2014 05:44 PM, Steve Cross wrote: > >> I'm a little late reading this email, but you say that you are having >> issues with Windows iSCSI on the Intel NUC series. I am curious which exact >> NUC model you are using. I ask because I have three here at my house all >> running completely diskless iSCSI and have been for nearly two years >> without issue. Perhaps I could provide some assistance. I apologize if you >> already provided this information, I managed to lose all emails prior to >> this one. >> >> > My Intel NUC is a DN2820FYK. > Problem might be BIOS version specific. > > iPXE is supposed to store the iBFT containing the iSCSI login information > somewhere in the memory region 512K-1024K for the OS to find, but on my > system that region is already in use... > > Last month's thread: http://lists.ipxe.org/pipermail/ipxe-devel/2014- > September/003798.html > > > > Yours sincerely, > > Floris Bos > > _______________________________________________ > 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
