wildschwein wrote:r54804 has no PCIIDE.SYS hang, and runs until mshtml-bug
M comes before P, so isn't it possible that you never saw the PCIIDE.SYS hang because you got stuck at MSHTML.DLL? Is the hang in the first or second stage?
In my opinion:
-He had ReactOS perfectly working until rX
-Then MSHTML bug striked him in rY
-During MSTHML brokeness a new regression was introduced in rZ(but not noticed as PCI hang comes after MSHTML)
-Now we have fixed MSTHML so he is experiencing the PCI hang.
I hope i don't need to compile whole ROS, i hope it's an patch.exe that i can apply on windows.
There are 2 ways.
"The FAST but not really sure RIGHT way"
1)Here you can find the ntoskrnl patched. Download it: http://www.4shared.com/file/n4WYXjCl/ntoskrnl.html
2)Now, open the ISO which was failing for you 200 revisions or so ago.Replace the ntoskrnl with this patched one. Save the ISO.
3)Install ReactOS, cross your fingers and check if you are able to install perfectly or if you hit PCIIDE.SYS. Follow any of these options:
In case you hit PCIIDE.SYS:
-Download and older revision and patch it again.(try with the first one that stopped working for you because the MSHTML bug)
-----------If with an older revision you are able to install ReactOS perfectly, then you will need to find in which revision PCIIDE.sys bug appears
-----------If wih an older revision you are not able to install ReactOS because the PCIIDE.sys bug, then try this patched ntoskrnl in a working ISO for you. Maybe the patch is the cause of the PCIIDE bug?
In case you didn't hit PCIIDE.sys:
-Congrats you found a revision that doesnt suffer from PCIIDE bug.
-You have now a range [patched non-buggy PCIIDE, patched buggy PCIIDE]. Perform a regression testing, patching all the ISOs needed.
In case you didn't even reach PCIIDE.sys neither MSHTML.dll:
-This ntoskrnl crazyness(using a different kernel ) seems to not work.
- You will have to download the sources, and patch it. But let's try first the patching way first