There shouldnt be a message box. All that means is that the program was unable to read the OEM information from the registry (on the "More Options..." form load) and therefore cannot populate the "OEM Info." tab in the "More Options..." window. No big deal... Maybe you have no OEM information on that computer yet? EDIT: Did it crash the program? It shouldn't have any effect on anything, just that will be logged to the log file because the program couldnt find any OEM information. Feel free to create some with the program EDIT2: I should take away the "error" and make it say "warning"
it didnt crash warning would better in my opinion and your right no oem info was installed at the time. i was just wondering about it because i was messing with the keys.ini file and clicked the wrong thing
I changed it for the next release when it comes. I dont need to give people the impression that an error occurred when one didnt... It is just a warning that OEM info couldnt be found in the registry.
Hi Hotcarl, did you make your own grub-loader / bootmgr loader for open 7 activator or did you integrate other peoples loaders? I noticed you gave thanks to Daz. Did you use Daz's Windows 7 Loader in your activator? If not, would you consider integrating his loader into this activator, as I understand it is very popular and top recommended by the 7 repository.
LOL they all use the same grldr grub loader. Zsmins These apps are sort of installers for zsmins bootloader, with a host of other features for activation.
This program may look similar to other programs, but it has more integrated features. I created this program not as a loader program, but as an "activator" program...and then some (sort of like an activation "tool-set"). Therefore it displays information about activation, as well as backs-up your windows activation for restoration without having to reactivate online or re-enter a product key (for retail keys), it has an integrated product key checker so an individual can check a product key they would like to use before installing it, with a click of a button (the product key checker also checks if the key that will be installed will be genuine in your copy of Windows BEFORE installing it). It allows the user to modify/add any OEM information they would like, to customize their installation of Windows (it is not limited to a list of pre-selected OEM vendors, a user can add any info. and bitmap they want (as long as the image is square, or it will look distorted)). It also has a built-in fail-safe that will still activate windows if slmgr.vbs is missing...and I have now modified it to accept an external keys.ini. I am also planning to add more friendly features. And did I mention the full help documentation with pictures... As there are many loaders in existence already, I created this program to go a step or two beyond simple activation.
Added new version 1.1.6 in OP. I have added various things, most importantly being the GUID path implementation into the new O7A. Now O7A will attempt to install the loader file via GUID paths (without mounting anything) first, if that does not work then O7A will default to the normal method of mounting the drive and proceed with the installation without interrupt. Basically, O7A will try to install the loader without mounting anything. If that fails then it will fall back to the normal method as a fail-safe...so it should activate the computer no matter what. Everything is automatic, so if 1 way fails, the other method will be used automatically and the end result of activation should still be attained. Also added all new SLP keys that were leaked since the last release... I left the last version 1.1.5c on the OP as well. Let me know if anyone has any issues or problems.
I have a very strange motherboard (asus m3n78 SE) and it said I have a SLIC, but I don't I have RemoveWAT installed. Just thought I'd let you know. When I click on it it just shows my RSDT as the detected SLIC.
Seemed to have hosed the mbr I have 5 drives with win 7 installed on a different drive than the one with the mbr. Installed the patch. Seemed to go ok until the reboot. Nothing! verifying dmi pool then nothing, just sits there. had to reinstall win 7 to fix. It probably screwed up mbr since after the initial portion of the reinstall, the mbr was ok. No complaint - just FYI cheers
Hmmm, it shouldn't matter how many drives you have, the program should still find the system volume and install the l0ader file there... Did any errors pop up in the error log file? That is very strange...