Good day Marc, In regards to your Windows XP via iSCSI BSoD shortly after logging in:
A firewall or "Internet protection" provided by an anti-virus product might be cutting off iSCSI. You could attempt to edit the SYSTEM hive on the SAN to disable these. Windows' firewall is the "SharedAccess" service. You'd have to try to determine the service for some other anti-virus or firewall product. I'm not sure that the BSoD is due to the NIC's re-installation; I would expect Windows to prompt you to reboot if it wished to update the device configuration with different driver parameters, since the device is critical to the running system. I could be mistaken, however. You could have a look at C:\Windows\SetupAPI.log on the SAN and see what Windows was up to near the time of the BSoD. If you _really_ suspect that this is the problem, you can rename the C:\Windows\INF\ directory to C:\Windows\INF.orig\ so that Windows will not be able to install _any_ devices. If you have Remote Desktop enabled, you could then Remote Desktop to the computer and have a chance to look around (at your unknown devices in Device Manager, for instance). Good luck. - Shao Miller _______________________________________________ gPXE mailing list gPXE@etherboot.org http://etherboot.org/mailman/listinfo/gpxe