Client boots, loads consisting of a tiny Linux Kernel and network driver, and a script or program [Non-NVRAM setup]<br>Client listens for predefined broadcast from Emu(server)<br>When found, Kernel contacts Emu and establishes connection
<br>Emu starts logging all activity<br>Kernel reads local bios to Emu [Non-NVRAM setup]<br>Emu executes received bios (emulated), directing all output to Kernel<br>Kernel directs/passes received output to hardware, directs/passes hardware results to Emu
<br>Assuming the Kernel does not get overwritten or lose control of system (crash), we now have a log of all neccesary and expected results of that bios on boot on that hardware. This would allow reverse engineering bioses and developing bioses for hardware legally?
<br><br> BIOS<br> |<br> v<br>A) Emu<->network<->Kernel OR B) ROM Image->Emu<->network<->Kernel Bios<->system/devices
<br> ^<br> |<br> v<br> system/devices<br><br>If the above ascii depiction is off, bios is above kernel is above system/devices
<br><br>Also, as in B) Client can be burned to Flash NVRAM, and ROM images can be fed through Emu to Kernel (Bios)<br>One possibility for A) is loading Client via PXE/bootp/Network boot.<br>