It's a magic?! I eject battery from my Notebook. Then disconnect ac adapter. Then wait 10 seconds: 1. WoW5 -> OK -> Shutdown -> disconnect ac adapter -> wait 10 sec 2. WOW6 -> 8 -> BSOD -> Shutdown -> disconnect ac adapter -> wait 10 sec 3. WOW6 -> 8 -> OK -> Shutdown -> disconnect ac adapter -> wait 10 sec 4. goto 1
And again me I try vistaloader 2.0 + dell cert. Vista is activated. So it is possible There is two files from vistaloader. Maybe it can helps you? View attachment data.zip And ACPIReport after vistaloader: View attachment vistaloader.zip
Thanks again for your great effort, I'll have a look at them at weekend. Edit: The two scenarios are verified now and there are 'only' these 2: 1- WoW doesn't find free space, DSDT isn't relocated----> no BSOD--->WoW doesn't work 2- WoW finds free space, DSDT is relocated--->BSOD---->WoW doesn't work. Discussion: IMO it's a matter of time, it seems in front of RSDT there is something happening...... Even scenario 2 seems to be dynamic. DSDT was relocated to 3FEFF034 and 3FFC920A. Why different addresses, a sort of racing duell of routines? The higher the address the faster was wow I think we need real time dump of the area before RSDT........ but I don't get why there sould be any code at boot??? That's strange... Flagmax, can you exclude a bug at search / relocate routine? The DSDT relocation works at VMware, DSDT data was 1:1 copied? I think there is no bug....
Yes I was assure of that! So your problem is the installation of wow. Re-Install WoW, it should really work without CD. Disable UAC and reboot. Copy wow.exe let's say to C:\temp Double click wow.exe, choose C:\ as installation path. reboot without CD... Tell me if it works now. If not, I'll give you manual instructions. Tell me exactly what you have done and what error (if) occurs.... Well here are the manually installation commands just in case the installer didn't work. Disable UAC, reboot, open a CMD as admin and type: cd /D C:\wow6 (hit enter) bootsectgrldr.exe /nt60 C: (hit enter) You have to get this: Updated NTFS filesystem bootcode. The update may be unreliable since the volume could not be locked during the update: Access is denied. Bootcode was successfully updated on all targeted volumes. Reboot.
i removed wow bootable CD. I install WoW6.0_NOMBR_HP.exe on C: and then reboot. nothing happened. still not activate. Then, I try this from picuture and reboot, still the same. picture from cmd here...
Thanks. Vistaloader seems to work completely different. There is no 'real' SLIC. WoW introduces a real SLIC just like it's from bios. WoW is more authentic (if it works) and more difficult to detect.........
IMO it would be the better way to remove Vistaloader completely. I'm sure there is something left that prevents to install WoW6. Search here at forums how to remove Vistaloader, after that WoW should be able to install. You may try VOATK Tools. You may also use this command to remove it: bootrest /nt60 C: (reboot) If you don't mind, reinstall Vista again, REMOVE and recreate all partitions new. I could advise you to install WoW6 another way. But it could interfere with 'old' activators and even cause more issues. A clean install assures a stable OS. WoW6 will work for you (CD version already proved that), don't try Vistaloader anymore after the clean install and don't forget to delete and recreate the partitions.
thanks!!! I have hp compaq 6720s and i tried WoW6.0_NOMBR_HP!!! It works for me!!! thank you guys, you are really amazing.......
Here is it: View attachment dumpreport.zip First - after battery unplug, etc... Second - after Vista reboot (bootmgr). PS: I use grub4dos 4.4 on my flash and boot via hiren's bootcd(from flash).
Hm... i installed VOATK 2.5. and remove activators. this command "bootrest /nt60 C:" doesn't work... maybe im doing something wrong... still doesnt work... what about unistall.bat in wow6 folder? Do i have to remove files from previous wow6 installation... (exe installation) What to try before last option that is "windows party" and reinstalling all over again?
Hi flagmax, good news. I'm sitting in front of an old PC. It's a fujitzu-siemens desktop with Phoenix bios. The relocation worked all two times. The relocation addresses were both the same, no BSOD occured, (booted after to XP via grub since Vista isn't installed.) Will check the other PC later when I'm back home....... Edit: I had a look at Eugene Nuke's dump. WTF? Padding bytes all over, but only 270 differencies.....IMO they will be written at boot (from bios) sometimes WoW finds a free space anyway in between....but DSDT get's padded......----> dump a bigger range.....why is that???? makes no sense... bibo Ok, I'll provide to you the renaming installation later.......you have to exchange the *IMG with a special one and to rename 2 files that's all.......check again later......... Eugene Nuke Would you please remake a bigger dump: memdump /DB:0x3EFFFFFF,0x1000000 /F:none /B:bigone1.bin Then wait 2 minutes do nothing and re-dump again: memdump /DB:0x3EFFFFFF,0x1000000 /F:none /B:bigone2.bin Thanks again, now it's quite clear why WoW doesn't work, but not clear why is your machine that strange...........the approach of DSDT relocation seems to be a good one anyway. Solution: The search for free space routine of WoW needs to be extended and improved. To search block by block, define one block , let's say 80000h. Check if block consists of FFh bytes only then write DSDT into it. Read relocated DSDT from its new location and verify it (to exclude volatile bytes and protected bytes.) If not found free space or DSDT couldn't be verified, make WoW search reversed till found (no range restriction......) or jump a few Mbytes backwards and search again.......and again.... Flagmax, what do you think?