This afternoon I burned the modified <> to a disc for testing (it passed in the virtual machine), but unexpectedly it wouldn't boot. Because there were too many changes, I couldn't tell what the problem was at first, so I compared it with the previous version and ruled things out one by one...
After burning it no less than ten times (the burner was practically smoking ^^), guess what happened? Switching EMM386.EXE back to UMBPCI.EXE fixed it.... I'm dizzy....
I changed it because everyone said EMM386.EXE had better compatibility....
And that's not all. I took it to test on someone else's machine (CII900+815 system), and unexpectedly it still wouldn't pass with UMBPCI.EXE. Out of several machines, this is the only one that won't pass even with UMBPCI.EXE; do I really have to load no memory management tool at all....
If anyone has a good solution, say something....
(I used EasyBOOT3.5 to make a multi-boot disc, maybe it's an EasyBOOT problem, but it would be best if this could be solved with some other memory management software)
After burning it no less than ten times (the burner was practically smoking ^^), guess what happened? Switching EMM386.EXE back to UMBPCI.EXE fixed it.... I'm dizzy....
I changed it because everyone said EMM386.EXE had better compatibility....
And that's not all. I took it to test on someone else's machine (CII900+815 system), and unexpectedly it still wouldn't pass with UMBPCI.EXE. Out of several machines, this is the only one that won't pass even with UMBPCI.EXE; do I really have to load no memory management tool at all....
If anyone has a good solution, say something....
(I used EasyBOOT3.5 to make a multi-boot disc, maybe it's an EasyBOOT problem, but it would be best if this could be solved with some other memory management software)
欢迎大家访问我的主页!
精品.爱好http://iso.533.net
精品.爱好http://iso.533.net



