Hi, I've got a dual boot system, Vista x86 and Vista x64. My x86 copy is legit, and I'm trying to run Vista x64 as a secondary OS. The problem I'm having is that WoW6 doesn't seem to want to work with Vista x64. I'm fairly certain that the problem stems from the legit x86 version being the boot location, whereas the x64 version is not. Is this the problem, and is there anymore information that would be needed?
wywywywy I have looked at your ACPI report. It looks like you are experiencing overwriting of the SLIC. Maybe its bios that does this or Vista, I don't know. To be sure, if you can, upload ACPI report without WoW and run HWDirect in administrator mode and do a memory dump from 7F6DFE8A size 10000. tommiy: Thanks for the info. We found out this overwriting issues recently. I am wondering if we can find some other specific constant offset that bios/vista does not touch, then link to it from RSDT.
Hello Sir, I have some question about WoW. All I need to do is follow the instruction in first reply right? Do I need the Grub.exe? When I extract WoW6_NOMBR_HP to C:\ then the cmd window appears, I see that one line is say "access denined". This line is appears under the bracket with number something like this {1123-141245-1233-........}, so this is completely install or not? And I have some issue with ACER Aspire 4930. I have used Everest to check ACPI on this notebook but I can't see any RSDT or SLIC. In this case WoW can active or not? Thank you very much!! EDIT:: I have completely install WoW and it's works, using Everest and found SLIC RSDT table but the problem happens when restarting computer the SLIC table is gone. I need to shutdown then boot the OS again then it backs. This issue is normally? Please help!
Flagmax, yes the rewrite of memory pending attached devices is an issue to finding an available memory space. When I was originally looking at upper memory there are a few spaces that seem to only get used at boot time and then never used after woulds however this is bios dependent by the looks per manufacturer. There is no easy mechanism of identifying these area's because they are used at boot and hence are not filled with 00 or FF but other values from the boot. Only way I found these is by using HW direct and trying sleep and adding pci cads, usb etc....sorry can;t help much here as I just didn't find a reliable mechanism....even spent hours reviewing the award source code thats available trying to determine where these area's would be but its not easy.
VistaLoader was working for me until today. I knew I shouldn't have updated . Can give me just a little more info on WoW6. I tried it before, but it didn't seem to work, whereas VistaLoader did. Which version should I use? Do I need to do a clean install or can I just use VOATK Tools to uninstall VistaLoader? I tried this before and it didn't show a SLIC table in everest (but showed OEM: HP under RSDT). What could have prevented SLIC showing up (was clean install VistaLoader was not installed)? Has anyone else had this problem?
I apologize if I am covering ground which has already been spoken about. I have also not been on this site for a while. Now that I am out of school for a couple weeks, I have some time to revisit a few problems I had with vista boot loaders. I just upgraded my computer and put in a new motherboard, the Intel DP45SG. I installed Vista however with this motherboard it seems everything works except for loading vista after the patch. It is hanging at a black screen. I also read that some newer motherboards have protection against this type of patching. I tried WoW6, both MBR and NoMBR version and the screen still hangs. The hanging looks the same as when I tried to install any type of boot loader on my friends Mac. My next step is to try the patching with an actual CD ISO, however I have a feeling that won't work either. Any ideas? EDIT:It seems to be a grub problem. Anyone have a viable solution to grub's limitations? I removed the execution of wow.exe from autoexec.bat in the IMG file, however it does not load vista properly I am not sure why Grub4DOS is having a problem. I regularly execute Vista from a boot menu on a Live CD I have, but that uses EasyBoot. I am not sure what to do in this situation.
I haven't had time to read every post in this thread, so I'll share the problem I'm having, in dire hopes that someone can help me solve it: My Vista Ultimate went kaput, is no longer activated, and is asking me to re-enter a authenticity key. Here's what happened: 1. I had Vista Ultimate installed for close to a year now, activated and geniune using VistaLoader 3.0.0.1 2. This weekend I downloaded the Windows 7 beta, and installed it on a separate partition. 3. Once I did that, I realized I screwed up, and had to put in my Vista DVD to repair the boot thingy so I could dual boot both OSes. 4. Once I booted back into Vista, I noticed that my activation thing said "15 days left before you must activate Vista" 5. I tried to uninstall VistaLoader 3.0.0.1, and used the VOATK tools to remove the key and blah blah. 6. Now when I boot back to Vista, and try to log on, I get the prompt asking me to enter a valid key. I downloaded Yen's tools, and burned the ISO, but the disc is blank What the hell am I possibly doing wrong? Please! I can't do a fresh format of vista, as there's tons of stuff I need to back up.
works with Intel dx58so Tnx! WoW6.0.1_NOMBR_HP.exe works with my Intel DX58SO motherboard. Used non-SP1 vista x64 installer and updated to SP1 without any problems.
DK 790FXB-M2RS raid0 great working! but latest version checking (seeking) floppy drive for startup sorry my english bad.
Yen: Please take down WoW6.0. It has a bug in the code. Only 6.0.1 version should be used. x3ro: The Iso actually has the files in boot area which is not visible in Windows Explorer. Burn and tell your PC to boot from CD. mrwilby: The older version has a bug in the code that creates SLIC. Thanks for your help. Sabresite: If EasyBoot works for you, see if it can emulated a virtual floppy. If not, you can try to create a small Dos partition, run wow.exe from it, then boot Vista. I am not familiar with EasyBoot. darthvidor: Thx for feedback.