WinWord2000 Posted December 1, 2022 Posted December 1, 2022 (edited) On 11/29/2022 at 7:26 PM, Mov AX, 0xDEAD said: Win2000 acpi driver sources was not leaked, only acpi.sys binary patch possible, no peoples who can do this job (adding acpi2.0 extended syntax and fixing know acpi incompatibilites on first page of topic) @blackwingcat maybe can do this job , @Mov AX, 0xDEAD can you please put the list of missed functions in acpi.sys of Windows 2000 Edited December 1, 2022 by WinWord2000
Mov AX, 0xDEAD Posted December 1, 2022 Author Posted December 1, 2022 On 11/30/2022 at 6:23 PM, Damnation said: @Mov AX, 0xDEAD Thanks for all your hard work! much appreciated! @Damnation What are results with fixed patch on your board ?
verta Posted December 2, 2022 Posted December 2, 2022 7 hours ago, WinWord2000 said: @blackwingcat maybe can do this job , @Mov AX, 0xDEAD can you please put the list of missed functions in acpi.sys of Windows 2000 = ) 1
Damnation Posted December 2, 2022 Posted December 2, 2022 @Mov AX, 0xDEAD The last 6 processors still say "Processor" but other than that it's working properly now.
R1600 Posted December 3, 2022 Posted December 3, 2022 On 12/2/2022 at 3:56 AM, WinWord2000 said: @blackwingcat maybe can do this job , @Mov AX, 0xDEAD can you please put the list of missed functions in acpi.sys of Windows 2000 NTOSKRNL.EXE (5.0.2195.6902) - InterlockedPopEntrySList InterlockedPushEntrySList HeadlessDispatch ExfInterlockedCompareExchange64 @blackwingcat's Extended Core has IntelockedPopEntrySList, InterlockedPushEntrySList, and ExfInterlockedCompareExchange64.
Damnation Posted December 3, 2022 Posted December 3, 2022 @R1600 @WinWord2000 You forgot the HAL dependencies. Also I already tried to do this and I ran into 1E BSODs and couldn't get past that.
Dietmar Posted December 3, 2022 Posted December 3, 2022 (edited) @Mov AX, 0xDEAD @George King With the new acpi.sys I get this strange BSOD on the Optiplex 780, which I have never seen before. @Mov AX, 0xDEAD Any idea, what this can be? Can you write me more instructions for acpi.sys, how to give more output of this Bsod Dietmar EDIT: In the original 5512 acpi.sys there is no "div" in _ExprOp2 proc near and so no Bsod at this place. Microsoft (R) Windows Debugger Version 6.3.9600.17200 X86 Copyright (c) Microsoft Corporation. All rights reserved. Using NET for debugging Opened WinSock 2.0 Waiting to reconnect... Connected to target 192.168.2.103 on port 50000 on local IP 192.168.2.101. Connected to Windows XP 2600 x86 compatible target at (Sat Dec 3 11:50:12.921 2022 (UTC + 1:00)), ptr64 FALSE Kernel Debugger connection established. ************* Symbol Path validation summary ************** Response Time (ms) Location OK C:\Symbols ************* Symbol Path validation summary ************** Response Time (ms) Location OK C:\symbolssss Symbol search path is: C:\symbolssss Executable search path is: C:\Symbols Windows XP Kernel Version 2600 MP (1 procs) Checked x86 compatible Built by: 2600.xpsp.080413-2133 Machine Name: Kernel base = 0x80a02000 PsLoadedModuleList = 0x80b019e8 System Uptime: not available ************* Symbol Path validation summary ************** Response Time (ms) Location OK E:\binaries.x86fre\Symbols ************* Symbol Path validation summary ************** Response Time (ms) Location OK C:\Symbols ************* Symbol Path validation summary ************** Response Time (ms) Location OK C:\symbolssss OK C:\symbols OK C:\symbolss OK C:\symbolsss OK E:\binaries.x86fre\Symbols Deferred https://msdl.microsoft.com/download/symbols Deferred srv* Break instruction exception - code 80000003 (first chance) nt!DbgBreakPoint: 80ac37e0 cc int 3 kd> g MM: Loader/HAL memory block indicates large pages cannot be used for 80100000->8012777F MTRR feature disabled. KiInitializeMTRR: OS support for MTRRs disabled KiInitializeMTRR: OS support for MTRRs disabled *** Assertion failed: IopInitHalResources == NULL *** Source File: d:\xpsp\base\ntos\io\pnpmgr\pnpinit.c, line 1455 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? i i *** Fatal System Error: 0x0000007f (0x00000000,0x00000000,0x00000000,0x00000000) Break instruction exception - code 80000003 (first chance) A fatal system error has occurred. Debugger entered on first try; Bugcheck callbacks have not been invoked. A fatal system error has occurred. Connected to Windows XP 2600 x86 compatible target at (Sat Dec 3 11:50:22.078 2022 (UTC + 1:00)), ptr64 FALSE Loading Kernel Symbols ..................................... Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 7F, {0, 0, 0, 0} Probably caused by : ACPI.sys ( ACPI!ExprOp2+102 ) Followup: MachineOwner --------- nt!RtlpBreakWithStatusInstruction: 80ac37ec cc int 3 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_0 TRAP_FRAME: b9d2fca4 -- (.trap 0xffffffffb9d2fca4) ErrCode = 00000000 eax=00000001 ebx=80000000 ecx=8acb0158 edx=00000000 esi=8acb1d7c edi=8acb0000 eip=b96e872c esp=b9d2fd18 ebp=b9d2fd1c iopl=0 nv up ei pl zr na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246 ACPI!ExprOp2+0x102: b96e872c f7711c div eax,dword ptr [ecx+1Ch] ds:0023:8acb0174=00000000 Resetting default scope DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: System ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) x86fre LAST_CONTROL_TRANSFER: from 80a30d7b to 80ac37ec STACK_TEXT: b9d2f7f4 80a30d7b 00000003 b9d2fb50 00000000 nt!RtlpBreakWithStatusInstruction b9d2f840 80a319e6 00000003 b96e872c 8acb1d7c nt!KiBugCheckDebugBreak+0x19 b9d2fc20 80a31f52 0000007f 00000000 00000000 nt!KeBugCheck2+0x574 b9d2fc40 80b817b9 0000007f b96e872c 8acb1d7c nt!KeBugCheck+0x14 b9d2fc98 80adfbfa b9d2fca4 b9d2fd1c b96e872c nt!Ki386CheckDivideByZeroTrap+0x41 b9d2fc98 b96e872c b9d2fca4 b9d2fd1c b96e872c nt!KiTrap00+0xaa b9d2fd1c b96eb187 8acb0000 8acb0180 00008000 ACPI!ExprOp2+0x102 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\type2op.c @ 756] b9d2fd38 b96e590a 8acb0000 8acb1d7c 00000000 ACPI!ParseTerm+0xf7 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\parser.c @ 588] b9d2fd60 b96e70a3 8acb0000 8ac5d390 b96f0218 ACPI!RunContext+0x5a [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\ctxt.c @ 588] b9d2fd74 b96e7123 8acb0000 00000000 b96f0218 ACPI!InsertReadyQueue+0xa5 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\sched.c @ 278] b9d2fd8c b96e1d8a 8ac5d390 00000000 8acbe478 ACPI!RestartCtxtPassive+0x28 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\sched.c @ 384] b9d2fdac 80bd81ac 00000000 00000000 00000000 ACPI!ACPIWorker+0x8c [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\nt\worker.c @ 325] b9d2fddc 80ae4212 b96e1cfe 00000000 00000000 nt!PspSystemThreadStartup+0x34 00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16 STACK_COMMAND: kb FOLLOWUP_IP: ACPI!ExprOp2+102 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\type2op.c @ 756] b96e872c f7711c div eax,dword ptr [ecx+1Ch] FAULTING_SOURCE_LINE: e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\type2op.c FAULTING_SOURCE_FILE: e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\type2op.c FAULTING_SOURCE_LINE_NUMBER: 756 FAULTING_SOURCE_CODE: No source found for 'e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\type2op.c' SYMBOL_STACK_INDEX: 6 SYMBOL_NAME: ACPI!ExprOp2+102 FOLLOWUP_NAME: MachineOwner MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys DEBUG_FLR_IMAGE_TIMESTAMP: 63853811 IMAGE_VERSION: 5.1.2600.7777 FAILURE_BUCKET_ID: 0x7f_0_ACPI!ExprOp2+102 BUCKET_ID: 0x7f_0_ACPI!ExprOp2+102 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:0x7f_0_acpi!exprop2+102 FAILURE_ID_HASH: {af20677d-c060-3ffb-ceae-0764beb57b50} Followup: MachineOwner --------- Edited December 3, 2022 by Dietmar
R1600 Posted December 3, 2022 Posted December 3, 2022 1 hour ago, Damnation said: @R1600 @WinWord2000 You forgot the HAL dependencies. Also I already tried to do this and I ran into 1E BSODs and couldn't get past that. I couldn't find any missing exports of halacpi.dll in Dependency Walker. Is there something I haven't found?
Mov AX, 0xDEAD Posted December 3, 2022 Author Posted December 3, 2022 (edited) 2 hours ago, Dietmar said: @Mov AX, 0xDEAD @George King With the new acpi.sys I get this strange BSOD on the Optiplex 780, which I have never seen before. @Mov AX, 0xDEAD Any idea, what this can be? Can you write me more instructions for acpi.sys, how to give more output of this Bsod Dietmar EDIT: In the original 5512 acpi.sys there is no "div" in _ExprOp2 proc near and so no Bsod at this place. Arg1: 00000000, EXCEPTION_DIVIDED_BY_ZERO Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 FOLLOWUP_IP: ACPI!ExprOp2+102 [e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\type2op.c @ 756] b96e872c f7711c div eax,dword ptr [ecx+1Ch] FAULTING_SOURCE_LINE: e:\software\windowssourcecode\microsoft.leaked.source.code.archive_2020-10-04\nt5src\source\xpsp1\nt\base\busdrv\acpi\driver\amlinew\type2op.c FAULTING_SOURCE_LINE_NUMBER: 756 Debug log has enough info about fault source line: Quote case OP_MOD: ENTER(2, ("Mod(Value1=%x,Value2=%x)\n", pterm->pdataArgs[0].uipDataValue, pterm->pdataArgs[1].uipDataValue)); pterm->pdataResult->uipDataValue = pterm->pdataArgs[0].uipDataValue % pterm->pdataArgs[1].uipDataValue; mod = div something wrong with math calculation in DSDT/SSDT EDIT: i forget add "break;" to all cases of switch(), probably this is my code problem, not DSDT issue, check fix: Quote EXIT(2, ("XOr=%x (Result=%x)\n", rc, pterm->pdataResult->uipDataValue)); case OP_MOD: => Quote EXIT(2, ("XOr=%x (Result=%x)\n", rc, pterm->pdataResult->uipDataValue)); break; case OP_MOD: Edited December 3, 2022 by Mov AX, 0xDEAD 2
Damnation Posted December 3, 2022 Posted December 3, 2022 @R1600 Huh, you're right, there isn't any missing imports from hal.dll - I could've sworn there was one though but I guess I was mistaken.
Dietmar Posted December 3, 2022 Posted December 3, 2022 @Mov AX, 0xDEAD I think, that this is the solution. Just now I dont remember all steps for compiling and @George King has also already added the new instructions for the new processor definition, me not. So we have to wait for you (via mail acpi.sys), for him or for me (until tomorrow) Dietmar
Dietmar Posted December 3, 2022 Posted December 3, 2022 @Mov AX, 0xDEAD I add all new changes to the Source Files for acpi.sys and compile it. Yessssa works also on the Optiplex 780 Dietmar https://ufile.io/qwlndr5c 2
George King Posted December 3, 2022 Posted December 3, 2022 (edited) @Dietmar I have added mentioned fix to both source trees, here are updated files for XP and 2003 https://www.mediafire.com/file/cboxm3x9ctb9i1u/ACPI_7777.6_x86+x64_5.1+5.2.7z/file Edited December 4, 2022 by George King 4
WinWord2000 Posted December 3, 2022 Posted December 3, 2022 11 hours ago, R1600 said: NTOSKRNL.EXE (5.0.2195.6902) - InterlockedPopEntrySList InterlockedPushEntrySList HeadlessDispatch ExfInterlockedCompareExchange64 @blackwingcat's Extended Core has IntelockedPopEntrySList, InterlockedPushEntrySList, and ExfInterlockedCompareExchange64. @R1600 @Damnation @Mov AX, 0xDEAD blackwingcat create an new extended core , please search in textbox of wlu site : Extended Core Win2000 Beta Test(KB979683v16b/x86) , this extended core solve to me the problem of graphic driver and new wifi card , it more better than 14b and 12a versions with more added functions in videoprt.sys and ntoskrnl , the version is still beta because BWC wants someone to help him test this version on two Display in one graphic card ,this makes him stop developing the hardware part until he finds someone to try with http://blog.livedoor.jp/blackwingcat/archives/1890134.html It's really bad that the only classic system capable of running in this day and the big brother of XP (5.0/5.1), does not find someone trying to support it and lend a hand to advance it I hope those who want to bring back the memories of the nineties with the classic interface to turn around Windows 2000 and its support
XPRTM Posted December 3, 2022 Posted December 3, 2022 (edited) ^ How about posting your Windows 2000 related questions, requests or whatever, in the Windows 2000 section ? This isn't the place for it. Its blatantly obvious that you are just trying to hijack or derail this thread, since the first pages. Edited December 3, 2022 by XPRTM 1
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