maharmstone
Bug fixes and code updates wanted!
I really appreciate your project, it's very creative! It may be the pioneer of Windows on "non-NTFS (and exFAT)".
But it seems that the road is not easy to walk, there are too few successes, and there are no very active development dynamics and commits to be found. And there has been no trace of developers in the code and issues for a long time. Politely ask, is this project still W.I.P, or has it been R.I.P? :(
I was very surprised when I first saw this project, but the results seem to have been teasing me and making me very sad. I invested so much time, but the only success was to boot Windows on the NTFS partition under QEMU, which was meaningless. On my and my friend's physical machines, all we could get was "Booting Windows", "EFI_INVALID_PARAMETER", "Loaded HAL.dll at xxx", "IRQL_NOT_EQUAL_OR_LESS BSOD", etc.
As @maharmstone said in the Readme, I also tried Virtualbox v7.0.0/v7.1.2, but still "Booting Windows" (Windows10), "IRQL BSOD" (Windows 8.1).
I spent 3 days studying and trying it wholeheartedly, hoping to break the terrible curse of NTFS, but it seems that the curse severely punished me, and I got nothing except the passing of time. I went from 20H2 to 8.1, then 1909, and finally LTSB In 2016, I even thought about Win7 and XP (64bit), but I really don't have time.
I am disappointed, but I am still looking forward to this project. If I can continue to see its updates and new releases in the future, I will definitely come back and try again.
Semi-good project, love from Lenovo Zhaoyang E52-80.
I've not abandoned it, I've been busy with other things. The chief problem is that the testing matrix is insane (i.e. every motherboard manufacturer multiplied by every versions of Windows), and there's pretty much no way to debug faulty firmware (of which there's many). When I touch this again, I'm thinking that I need to add a kexec mode, which should at least cut down half the problem.
I've not abandoned it, I've been busy with other things. The chief problem is that the testing matrix is insane (i.e. every motherboard manufacturer multiplied by every versions of Windows), and there's pretty much no way to debug faulty firmware (of which there's many). When I touch this again, I'm thinking that I need to add a kexec mode, which should at least cut down half the problem.
Then I feel relieved. I will continue to follow up the test, hoping that the possibility of success will be greater in the future.