Leaderboard

Hi LoneCrusader, Thank you for your donation of $100.00. We look forward to improving the forums and stay online with your donation. MSFN Team

silverlight - this NPAPI plugin https://support.mozilla.org/gl/questions/1176670

For any extensions Firefox 69+, create extensions.checkCompatibility.nightly false extensions.checkUpdateSecurity false For plugins, create plugin.load_flash_only false The browser only looks for application/x-shockwave-flash , it is necessary to correct the plugin and script, example https://dl.dropboxusercontent.com/s/xv8i6fbojvbxlqd/vmp.JPG or wait for a new version of MyPal with a fixed NPAPI if ublock crashes, old version 1.16.20 https://addons.mozilla.org/firefox/downloads/file/1056733/ublock_origin-1.16.20-an+fx.xpi

@Dietmar I will test these acpi.sys on my Ryzen Threadripper system when I have time tomorrow.

@Dietmar I use razzle free offline and to build I just do bcz

@Dietmar awesome! @Mov AX, 0xDEAD Besides that unresolved unknown AMLILoadDDB BSOD have we resolved all known ACPI BSODs?

Looks like someone managed to make MyPal 68 work on Windows 2000 after some file editing: http://mrqash.blogspot.com/2022/04/mypal-68-firefox-68121-on-windows-2000.html Wonder if those edits can help in any way onto running MyPal on 98/ME, would be amazing if it did so.

@daniel_k@Mov AX, 0xDEAD I asked @Dietmar to test this code else if (! ((PDEVICE_EXTENSION)Pdo->DeviceExtension)->Flags & DEV_CAP_PCI_DEVICE ) { // return STATUS_NOT_FOUND; } he reported that he still got a 7E BSOD, so this did not work. edit: I see now @Mov AX, 0xDEAD posted an update with an extra ( bracket, that might be why the above code didn't work.

My last words to you @WinWord2000: Good luck.

@Dietmar odd, I commented out line 3526 yet it still says assert failed for // ASSERT(PciInterfacesInstantiated) ? I'm tired, I'll try something else tomorrow. Thanks for testing.

@Dietmar I commented out ASSERT(PciInterfacesInstantiated) still BSOD? https://anonfiles.com/34u6daW9x3/acpi_checked_crackprt_test5_7z

@Dietmar hopefully this one is different~ https://anonfiles.com/raZ1cfW1x5/acpi_checked_crackprt_test3_7z

@Dietmar and this one? https://anonfiles.com/73gdc4W8x6/acpi_checked_crackprt_test2_7z

@Dietmar Can you test this checked acpi.sys to see if 7E BSOD still happens? https://anonfiles.com/V2A4b2Wex5/acpi_checked_crackprt_test1_7z

There is, using ProxHTTPSProxyMII Rev3e apparently.

Other than not needing to apply your hack to acpi.sys every time we build it I'm not sure, I don't recall ever making use of the GPIO.

@Mov AX, 0xDEAD @daniel_k Could we use code from reactos for unsupported opcodes?

@Dietmar I downloaded the BIOS for the ASRock B550 Steel Legend (board I chose for a build, still waiting for it on backorder) checked it's DSDT, it also has Device (GPIO) { Name (_HID, "AMDI0030") // _HID: Hardware ID Name (_CID, "AMDI0030") // _CID: Compatible ID Name (_UID, Zero) // _UID: Unique ID Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings { Name (RBUF, ResourceTemplate () { Interrupt (ResourceConsumer, Level, ActiveLow, Shared, ,, ) { 0x00000007, } Memory32Fixed (ReadWrite, 0xFED81500, // Address Base 0x00000400, // Address Length ) }) Return (RBUF) /* \_SB_.GPIO._CRS.RBUF */ } I think perhaps all AMD Ryzen boards use this DSDT code.

@Dietmar maybe try this? if (((PDEVICE_EXTENSION)Pdo->DeviceExtension)->Flags & DEV_CAP_PCI) { // // It's a PCI PDO, which means a root PCI bus, // which means that we should just handle this // as an ISA device. // return STATUS_NOT_FOUND; } elseif (((PDEVICE_EXTENSION)Pdo->DeviceExtension)->Flags & DEV_CAP_ISA) { // return STATUS_NOT_FOUND; }

May I kindly ask you if this thread has been changed its title to "How to activate Windows XP with a key of doubtful or rather illegal origin"? The last three pages are about activation problems with such keys. I thought the title of this thread is "On decommissioning of update servers for 2000, XP, (and Vista?) as of July 2019". Do the poster of these contents really know that? I don't think so. This thread is totally bloated and polluted with off-topic comments. I am no longer interested in posting new solutions or fixes here in this thread. PS: BTW I think there are other places to talk about such kind of stuff!

@Dietmar Just an idea - for ACPIArbCrackPRT can you try this out? // if (((PDEVICE_EXTENSION)Pdo->DeviceExtension)->Flags & DEV_CAP_PCI) { if (!((PDEVICE_EXTENSION)Pdo->DeviceExtension)->Flags & DEV_CAP_PCI) { // // It's a PCI PDO, which means a root PCI bus, // which means that we should just handle this // as an ISA device. // return STATUS_NOT_FOUND; } } ASSERT(PciInterfacesInstantiated); still 7E BSOD? or something else?

@Dietmar do you mean having ULONG64 for CreateQWordField instead of ULONG? after this is changed A5 0x02 is gone?

@Mov AX, 0xDEAD So is acpi.sys expecting DEV_CAP_PCI to be a PDO but it is something else?

@WinWord2000 I'm taking a break from working on it for now.

@Dietmar Looking at the logs there, I'm a bit more confident that if (((PDEVICE_EXTENSION)Pdo->DeviceExtension)->Flags & DEV_CAP_PCI) is the cause I think try commenting it out, compile and test.

@Dietmar In source code we just comment out entire function and return all OK?

@Andalu I have this same problem on my AMD Threadripper System, I even get this A5 0x11 0x08 BSOD on Windows 8.0 as of right now the best we can do for this case is to tell acpi.sys to ignore failed DDB Load.

@Dietmar I recall the problem was somewhere near PciInterfacesInstantiated I think the problem in ACPIArbCrackPRT might be this if (((PDEVICE_EXTENSION)Pdo->DeviceExtension)->Flags & DEV_CAP_PCI) { // // It's a PCI PDO, which means a root PCI bus, // which means that we should just handle this // as an ISA device. // return STATUS_NOT_FOUND; } try commenting this out and see if that works?

@Mov AX, 0xDEAD I would like to try and see if I can implement 64bit integer support. what functions should I be focusing on to properly implement this? which acpi.sys version has a proper 64bit integer support?

I bought my first AMD Ryzen 5000 series desktop system today (previous desktop was older 2000 series with 300 chipset) I'll compile and test this when the system is ready. I went with an ASRock motherboard, for whatever reason they use an iASL compiler from 2012 for their AMD boards and they seem to be the only vendor doing this. I wonder if this might be more ACPI friendly for XP because of it?

@Dietmar But isn't that hack just skipping over the error rather than actually resolving the issue?

@Dietmar there is an ACPIDebugResourceRequirementsList function, maybe that can help?

@George King As far as I know there isn't an easy way to convert assembly back into C code, at best you can get some psuedo code with a dissassembler. Everything would be so much easier if there was a reliable way to convert to C code.

@Mov AX, 0xDEAD Concerning the CreateQwordfield implementation, would doing something like this work better? pbf->FieldDesc.dwNumBits = 8*sizeof(ULONGLONG); pbf->FieldDesc.dwFieldFlags = ACCTYPE_QWORD;

@Mov AX, 0xDEAD Nice Work! much appreciated! thanks!

I recall needing AHCILDR at least for the 1st part of setup, I also tried PATCHMEM to see if that would get past the error but it didn't help.

@windows2 Out of curiosity, why 2000 and not XP?

I ran into this problem on my AMD Threadripper 3960x system, gave up after running into the VCACHE error despite rloew's patches. It runs just fine on my AB350 2700x system with rloew's patches.

@windows2 Damn! Unfortunately it seems the only viable solution for this at the moment would be to install XP. Sorry.

Is there some other way to get in contact? I'd rather not join twitter.

@windows2 OK, will do, thanks. @Ximonite Have you heard of the ntoskrnl extender for XP? I can confirm that it works, I used it to install XP on my AMD Ryzen system, it works well, very stable. Interested in doing the same for 2000?

@Dietmar If you're still active on this forum - do you remember if there was a way to safely switch from "ACPI Uniprocessor PC" to "ACPI multiproccessor PC" ?

@Dave-H It's odd that you got a 7B BSOD with option 1 - that's usually the driver that works. It works for my Threadripper 3960x machine, so it's odd that it does not work for you. Fortunately the integrator has alternative options for this reason. This time try options H, 3,4,5

@Dave-H In your registry, do a search for CC_0106 does it find anything?

@Dave-H First Check in device manager under "Computer" - If it says something other than "ACPI Multiprocessor PC" then ACPI isn't properly enabled.

@Dave-H Yes it will work - did you copy ntoskrn8.sys across to system32\drivers too? that is needed for it to work. ntoskrn8.sys is in \Integrator Files\Patches\Miscellaneous

@Dave-H I'm very interested in helping you solve this. So you want to get ACPI enabled on your system but without doing a fresh install is that right? TBH the easiest solution is to do a fresh install with XP integral edition using the Optional patch integrator which can be found here - https://www.zone94.com/downloads/software/operating-systems/123-windows-xp-professional-sp3-x86-integral-edition Applying the patches to an existing install is the more difficult route. Is preserving the existing installation a must? a new install is much easier thats why all the existing guides prefer it.

Has anyone taken a look at the uploaded source code? also, the source code for the AHCILDR.COM program and AHCI.PDR driver is still missing

I'd just use my B350 K4 motherboard and 2700x CPU instead.

I can confirm that USB-2 PCI-e cards do work in windows 98 SE https://www.ebay.com/itm/USB-2-0-to-PCI-e-x1-expansion-Card-4-External-USB2-0-PCI-express-Adapter-Moschip/223262224944?hash=item33fb773230:g:ilEAAOSwaBZZmNXa