Hi Daniel, 1. Something is wrong in your no_error.txt: by the presence of "iscsiboot.sys" in your log (old version of sanbootconf), I'm getting a strong feeling that you didn't perform a clean install of Windows. if your attaching a second log for comparison purposes, you should use the same installation in both iSCSI and physical disk, to clone the installation, you can use Microsoft ImageX.
2. You're mistaken. sanbootconf is NOT among the last drivers to load in no_error.txt, note that ndisuio.sys is the last driver to load in no_error.txt. 3. what's effecting the order is primary the value of: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sanbootconf:Group which should be "Base", Base should be the 6th group to be loaded, as specified in: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder:List this list is modified by sanbootconf setup program, if the setup has been executed successfully, you should have Base as the 6th item, after System Bus Extender, NDIS Wrapper and NDIS, and before PNP_TDI (Note that the manual installation method I suggested earlier does NOT execute sanbootconf's setup program, however, it should still make sanbootconf be loaded, which doesn't happen) I also can't recognize any network adapter driver in error.txt. 4. I suggest you install VMWare 1.0.x, select the E1000 network adapter, and experiment with making the machine iSCSI bootable, I have a strong feeling you're missing something, and it would be easier to track with a VM. 5. Are you using an original installation media with the latest service pack already integrated? Regards, Tal 2011/10/17 Daniel García <[email protected]> > Hi, > > I've reinstalled the driver as i've been told. I've also activated the > "Verbose output" option. But it still reboots. I've attached to this mail > the error report. > > I've connected the physical disk to my client computer and it boots > correctly. But if you look in the WinDbg report, it seems to load the > sanbootconf driver, but it's almost the last driver to load. Maybe is that > the problem? How I can change the loading order of the modules? I've also > attached this report of a correct booting (no_error.txt) > > Thanks to everyone. > > Daniel García. > > > 2011/10/7 Tal Aloni <[email protected]> > >> ** >> Hi Daniel, >> From the log it seems that indeed sanbootconf is not initialized, (I'm not >> sure if it's loaded or not because you didn't turn on "View > Verbose >> output" in WinDbg to show additional information) >> maybe you've installed sanbootconf improperly somehow, or perhaps you have >> some kind of agressive anti-virus program that block the file-copying or >> registry changes. >> make sure you have sanbootconf.sys under Windows\System32\Drivers, and >> that you have a registry key called "sanbootconf" under >> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services >> >> - You can also manually install sanbootconf using Control Panel > Add >> Hardware, and then selecting "I have already connected the hardware" > "Add >> a new hardware device" > "Install the hardware that I manually select" > >> "System Devices" and then point to the directory where sanbootconf.inf is >> located. (this will only install sanbootconf without applying some critical >> configuration) >> >> Regards, >> Tal Aloni >> >> ----- Original Message ----- >> >> *From:* Daniel García <[email protected]> >> *To:* [email protected] >> *Sent:* Friday, October 07, 2011 2:01 PM >> *Subject:* Re: [ipxe-devel] Windows XP just reboots all time in the logo >> screen >> >> Hi, >> >> I've re-installed Windows XP and sanbootconf 1.0. It still giving me the >> same problem: windows reboots itself when the logo screen appears. >> >> Looking at the WinDbg report, i think the problem migth be that >> sanbootconf driver doesn´t load in the boot secuence. >> >> Anybody can tell me why it happends? Thanks for yout time. >> >> Daniel Garcia. >> >> El 5 de octubre de 2011 16:20, Daniel García >> <[email protected]>escribió: >> >> Thanks for the info, Shao >>> >>> I've followed your advice and checked if sanbootconf driver was loaded, >>> and it looks like it wasn't. I don't know why this happend, I installed the >>> last version of sanbootconf with no error. >>> >>> I attach the new WinDbg capture with the result of the "lm" command. >>> >>> Daniel Garcia. >>> >>> El 5 de octubre de 2011 15:26, Daniel García >>> <[email protected]>escribió: >>> >>> Hi again, >>>> >>>> I've upgraded to iPXE and to the new version of sanbootconf too, but I'm >>>> getting the same error: the client machines conects to the iscsi target and >>>> starts booting windows xp, until it reboots itself, giving a 0x00007b error >>>> in the WinDbg. >>>> >>>> I attach the WinDbg output file. I'd appreciate any kind of help. I've >>>> been looking hard for any solution, but I found nothing... >>>> >>>> Daniel. >>>> >>>> El 4 de octubre de 2011 13:51, Daniel García >>>> <[email protected]>escribió: >>>> >>>> Hi, >>>>> >>>>> I've followed the how-to and I get the error report from WinDbg >>>>> attached to this mail. I'd appreciate any information you can give me. >>>>> >>>>> It seems like sanbootconf driver doesn't load. >>>>> >>>>> >>>>> Daniel. >>>>> >>>> >>>> >>> >> >> ------------------------------ >> >> _______________________________________________ >> ipxe-devel mailing list >> [email protected] >> https://lists.ipxe.org/mailman/listinfo/ipxe-devel >> >> >> _______________________________________________ >> ipxe-devel mailing list >> [email protected] >> https://lists.ipxe.org/mailman/listinfo/ipxe-devel >> >> > > _______________________________________________ > ipxe-devel mailing list > [email protected] > https://lists.ipxe.org/mailman/listinfo/ipxe-devel > >
_______________________________________________ ipxe-devel mailing list [email protected] https://lists.ipxe.org/mailman/listinfo/ipxe-devel
