mrjrt

Hello...have you had any more thoughts on releasing the prototype that loads updates?

The UEFI/FAT32 side of things is more for having a stick that can be booted in multiple ways. I've not reached that point yet, but it is my cursory understanding...

_sigh_ scratch most of that. I've just wasted a large part of my day...very frustrating. At some point earlier today I tested the original aoe32 driver WinVBlk was based on...

Yes. Post iPXE, booted from G4D, loaded the ISO into RAM, then booted it. Relevant equivalent bit of log from 2ebc053a0152f98013281bbe94f8dd07888398f4: ``` g:\temp\coding\winvblock\src\aoe\driver.c: DriverEntry() @ line 226: Entry g:\temp\coding\winvblock\src\aoe\registry.c: AoeRegSetup()...

Had another poke at it this evening. Still no joy, but thought I'd mention that when I turn on IRP debugging (to see if that shines any light on things)...

If you think it will help, I'll certainly do as you ask. Though I should mention, I just tried again (both on VMWare and on a physical machine) with 2ebc053a0152f98013281bbe94f8dd07888398f4...

Alrighty then, as requested, here's a trace from my build with those other drivers stripped out: http://pastebin.com/3a0Kv5fr ...and for completeness, here's a trace from the working revision with those drivers...

...the stable version works fine (AoE-wise, and with all the other drivers). I'm just trying to help you out with some testing by letting you know your changes since 2ebc053a0152f98013281bbe94f8dd07888398f4...

Ok, threw the stable version into my test build anyway (and disabled the nic boot driver), and I'm not getting any messages now - the system just hangs on the...

Ok, adding the NIC Boot Config driver back in makes 0.0.1.8 work - no hanging: http://pastebin.com/apMUwrPT It may be of relevance that I should mention the load order I'm using...