There's a reason why the Joggler will only boot from certain hubs and ports for Windows, and maybe Linux too. Just have to dig and see what can be found. It would be good if the logging, that is built into the code, could be turned on. Or maybe it is on all the time and a log file is produced somewhere ?hawsey wrote:Totally over my head but following with interest.
Actually, having been in there a bit, it will be a great exercise to learn about EFI, XP booting and other internals, and get back into C/C++.
I need to find my old copies of MSDN from about 12 years ago that had Visual Studio 6 on them and that would be good to see if I can build it and to put some extra debugging in there, if needed. There actually doesn't seem to be a lot of code, but its low level stuff in places. One thing that really got me wondering what was going on is when I looked at the XOJ.efi file in a hex editor - there is a whole load of machine instruction mnemonics in there ( like xor, jmp and so on) in readable text,
I dread installing Visual Studio though - it gets everywhere. Maybe someone has made a nice portable version... Actually, thinking about it, the code will never really run properly on the build machine, because it is a completely different environment to the Joggler. So, logging is really the main way to find out what is happening, as stepping through the code on the build machine will be fairly pointless.
I'm beginning to wonder why MS C++ 6 has to be used ? Maybe it could be ported to GCC / MINGW. There will probably be a whole lot of broken code... Mmmmhh - think I'll leave that one alone.