WildBill Posted November 6, 2011 Author Posted November 6, 2011 Good One more change: loading bootskin settings (but not doing anything with them):Windows2000-KB2393802-v1-early-c5c5-x86-ENU.exe
tomasz86 Posted November 6, 2011 Posted November 6, 2011 Windows2000-KB2393802-v1-early-c5c5-x86-ENU.exeWorks I have to go now so if you prepare the next one, I'll test it later today.
WildBill Posted November 6, 2011 Author Posted November 6, 2011 Okay.Next change: switching to the larger scroll buffer...Windows2000-KB2393802-v1-early-c5c6-x86-ENU.exe
tomasz86 Posted November 7, 2011 Posted November 7, 2011 Windows2000-KB2393802-v1-early-c5c6-x86-ENU.exeMonitor dies at 80%.
WildBill Posted November 7, 2011 Author Posted November 7, 2011 A-ha! Now we're getting somewhere. Will look at it tonight.
tomasz86 Posted November 7, 2011 Posted November 7, 2011 Yeah, I think so It looks exactly the same as before with c5h and others up to c5o.
WildBill Posted November 7, 2011 Author Posted November 7, 2011 Hmm. I didn't have write access turned on for the larger buffer, so this might be a false alarm. What happens with this one, with writes enabled?Windows2000-KB2393802-v1-early-c5c7-x86-ENU.exe
tomasz86 Posted November 8, 2011 Posted November 8, 2011 Windows2000-KB2393802-v1-early-c5c7-x86-ENU.exeUnfortunately there's no change.
WildBill Posted November 8, 2011 Author Posted November 8, 2011 Actually, that's good news: now I have something to focus on.
WildBill Posted November 9, 2011 Author Posted November 9, 2011 I might have found something. Apparently, at the 80% mark, the kernel decides that it wants to make certain of its memory sections pageable, including the one I'm using to hold the larger scroll buffer. That's fatal to the bootskin code because the buffer must not be pageable. I renamed the section in question from .edata to .xdata to keep the kernel from doing it. Cross your fingers...Windows2000-KB2393802-v1-early-c5c8-x86-ENU.exe
tomasz86 Posted November 9, 2011 Posted November 9, 2011 (edited) Cross your fingers...Windows2000-KB2393802-v1-early-c5c8-x86-ENU.exeThat was it probably. It works now Do you have any idea why this issue was present here and not anywhere else? Could it be hardware specific? Edited November 9, 2011 by tomasz86
WildBill Posted November 9, 2011 Author Posted November 9, 2011 Cross your fingers...Windows2000-KB2393802-v1-early-c5c8-x86-ENU.exeThat was it probably. It works now Do you have any idea why this issue was present here and not anywhere else? Could it be hardware specific?I think so. It looks like it only turns paging on if the memory address is not within a certain area. Maybe your hardware combo is resulting in the kernel being loaded into a different address.
dencorso Posted November 9, 2011 Posted November 9, 2011 Congratulations, to the two of you! That sure was a bug hard to swat! Persistence and method wins the day. You both rock!
WildBill Posted November 9, 2011 Author Posted November 9, 2011 (edited) Okay, here's the acid test. This has all of the bootskin code enabled and has the scroll buffer renamed to .xdata to protect it. If this works, then over the next few days I'll make the same changes to the other three files and release a V4.Windows2000-KB2393802-v1-early-c5p-x86-ENU.exeFor what it's worth, v4 also adds a few more routines:_vsnwprintf_aulldvrmRtlGetVersionKeFlushQueuedDpcs Edited November 9, 2011 by WildBill
tomasz86 Posted November 9, 2011 Posted November 9, 2011 Windows2000-KB2393802-v1-early-c5p-x86-ENU.exeIt works
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now