Update on my test of WoW6 on Compaq N620c: BSOD on first boot from the CD-ROM. The second boot went fine but Vista is not activated. HP certificate and key are in place. Let me know if you need ACPI report.
Thank you, I went over your report. In it, I find a good HP SLIC in XSDT and looks like made by WOW. Now you need to add HP certificate as shown in first post and key. You need to wait for confirmation box for both things. I also see your bios has NSLI table that looks like half mapped SLIC. If you are not using any other patch/mod then Acer must has added it. We can try and order WOW to use this table for SLIC which might be best solution for you specifically. Thank you, I will make a debug CD so you can see whats happening during boot. Check back later.
THANKS you are the BEST THANKS IT WORKS.... I add HP certificate as shown in first post by Yen and then I put the Vista Home Premium key for HP (thanks to reginakampher)... I reboot my notebook an NOW my VISTA is ACTIVATED....
davco: Congrats! Yen: So far only I confirmed in VMWARE that FADT routine works. Other people here that are testing are tilkov and Eugene Nuke but they get BSOD. Once the try debug version then we can see if its WOW problem or grub. While testing, I found out the latest 0.4.4-2008-11-19 grldr invisible makes VMWARE freeze, so prolly to many NOPs. So in the WoW 6.0 installer I used 0.4.4-2008-08-08 grldr invisible. And from first post WoW5.2.3_NOMBR_HP.exe auto installer freezes my VMWARE, again problem with grldr.
Thank you for your report. So the BSOD only occurs after the first cold boot. (PC switched off and on again). How did you reboot PC after you've got BSOD? Pushed reset button? Or CRTL-alt-del? At reboot from Vista (warm boot) there is no more (NEVER more) BSOD, right? Please confirm. If there is no error at flagmax code (I think so ), we have to find a solution. Hmmmm, I'll read acpi spec. again. DSDT is the most important and complex table, even bios programmer are messing it up sometimes. At VM the relocation of it seems to work, at 'hard' bios not at cold boot. A solution could be: Check for FADT flag, if set, execute FADT routine, exit wow---->execute grub. If not, execute FADT routine. After execution of FADT routine set a flag (I call it FADT flag, must resist reboot) , send reboot.... Sorry I'm no programmer, but sometimes I've got ideas But I don't know what's the difference that causes the BSOD.
No, it may appear after reboot (warm boot). And it may not appear after switching off/on. Windows do reboot after BSOD. No, it may appear. I think it is random...
Eugene Nuke One more question: When exactly occurs the BSOD? After Vista green bar moving? At cold boot it appeared as well? Both random (cold and warm boot doesn't matter?) Sorry for this 'stupid' questions, but I don't get the problem.....
I made some tests. I insert CD with WoW6 and switch off my computer: 1. Switch on -> BSOD -> Switch off 2. Switch on -> OK -> Switch off 3. Switch on -> OK -> Switch off 4. Switch on -> OK -> Switch off 5. Switch on -> OK -> Switch off 6. Switch on -> BSOD -> Switch off 7. Switch on -> OK -> Switch off 8. Switch on -> OK -> Switch off Looks like random... Then I try to boot WoW5, switch off, boot WoW6... 1. Switch on -> boot WoW5 -> OK -> Switch off 2. Switch on -> boot WoW6 -> BSOD -> Switch off 3. Switch on -> boot WoW5 -> OK -> Switch off 4. Switch on -> boot WoW6 -> BSOD -> Switch off 5. Switch on -> boot WoW5 -> OK -> Switch off 6. Switch on -> boot WoW6 -> BSOD -> Switch off 7. Switch on -> boot WoW5 -> OK -> Switch off 8. Switch on -> boot WoW6 -> BSOD -> Switch off 9. Switch on -> boot WoW5 -> OK -> Switch off What you think about it?
Thanks for the effort. It's definitely caused by the relocation of DSDT. But it seems to be at random.....WoW5 isn't able to activate your PC, therefore is made WoW6 The WoW5/WoW6 pattern is interesting...but IMO it must be random as well. How should a switched off machine notice of WoW5 before? How long does it take till RAM data are lost? Hehehe..... I'll wait till flagmax excludes an error at his wowcode (all checksums of tables corrected?).....I don't like random errors I don't have any tools here, have to wait till I'm back at home again.... Thanks again. Anyway, links to WoW 6 at first post updated. Need to know if it's a bios specific error.....