Root System Description Pointer: 0x000FEBF0 52 53 44 20 50 54 52 20 51 44 45 4C 4C 20 20 00RSD PTR QDELL . 55 CB 0F 00 U... Signature"RSD PTR " Checksum0x51 (81) OEM ID"DELL " Revision0x00 (0) - ACPI 1.0 RSDT Address0x000FCB55 The other tabs are RSDT FACP SSDT APIC BOOT ASF! MCFG HPET FACS DSDT
Yes. ttaiw: Please install Hwdirect (at 64 bit press f8 and disable driver signing enforcement before). Goto memory dump enter physical address: 3F7DEE40, size 1500. Press dump. Right click into window, select all, right click again and select copy. Please without wow running. Paste it into, lets say notepad, save and upload it please. We need that to improve WoW. Thanks for your cooperation.
eradicator006: Thank you for the info. At this time WOW will not work for you. Stick with Loader 2. The reason WOW does not work is because your bios uses RAM space 0xF0000 for ACPI tables which is Write Protected. Yen Right, but you can remove Write protection. The Northbridge is what controls it. PCI Bus 0, Device 0, Function 0 to be exact. There is 1 bit somewhere from offset 50h to A0h that needs to be set that will enable Writes to 0xF0000. You can use RW Everything to set the bit. However, I don't know how to code it in Assembly to be used in WOW. Are you using VMWARE, what version?
Sorry, I don't have vmware installed. Oh yes, at the other thread you've demonstrated to remove write protection. It was at Vmware? Is the way bios specific?
Yes, its bios specific. On VMWARE 6 and 6.5, For PCI 0, 0, 0 at offset 59h, set bit 5 to 1. Now RSD PTR is Write Enabled. With trial and error you can find the bit for other machines. Sometimes you will reboot while finding the bit. If you can find the datasheet for your Northbridge chipset, the info is there.
Hello. I have Notebook HP Compaq nc6000. WoW5 don't work on my computer. (And other activators too) Here is ACPIScope report: View attachment hp_compaq_nc6000.zip I will wait for your help. Thanks for your job!
@Eugene Nuke: I reviewed your bios report. Currently WOW does not support your bios Technical reasons: Your bios does not have a halfmapped SLIC, no MCFG, no BOOT tables, Table DSDT after RSDT is not linked from RSDT and no free space at end RSDT. I will need to update WOW for it to work with your bios. When new WoW6 comes out, it should work for you. ETA: 1 week.
Hi, I have a Compaq N620c, a machine quite similar to the NC6000 above. Latest WOW cannot activate Vista for me too. I am guessing the two BIOSes to be the same and looking forward for WOW6. Anyway, I am attaching ACPIScope report with WOW installed. Regards
You are correct. Your bios ACPI tables layout and nc6000 are the same. Thanks for the report and WoW6 can be your working solution. ETA 1 week.
Newbie Question I'm just a newbie trying to find WS08 activation solution. I'm running my WS08 VM guest test server on VM WKS 6.5 under Vista x64. I've followed the instructions in WoW5.2.3_NOMBR_HP.exe and successfully activated WS08. However when I reboot the VM guest it just hanged in the boot prompt. If I use WOWfloppy_5.2.3_auto_HP.img boot floppy it can successfully boot into WS08. I then run c:\wow5\uninstall.bat and then WoW5.2.3_NOMBR_HP_visible.exe and this time it can boot up successfully without the WOWfloppy_5.2.3_auto_HP.img boot floppy. What have I done wrong? IM
In other words: WoW visible and the bootfloppy is working for you, the invisible one not, right? Please confirm. It's not your fault. .......... it's probably something wrong with the 'invisible' grldr. Flagmax is writing new wow6, grub will be updated as well, please stick with visible wow till it's done. Btw: Have you tried a modified VM bios already?
Yen: This is what I am adding to WOW as last resort option. Check if FADT is in RSDT, then check if DSDT is right after RSDT: Then relocate DSDT to free space before RSDT, patch FADT, create SLIC and extend RSDT for SLIC entry. Let me know what you think, thanks.
DSDT is always linked from FADT and seems to be the largest table. And often DSDT is right behind RSDT. Sometimes there is free space between them, sometimes not. That sounds good. Relocation of tables is the better way, better than to replace a call of one To place in between 'Table after RSDT linked from RSDT?' and 'MCFG?'