lol...that is fine to say. His probably activates with FD because his program does not run the bootsect.exe tool after installing the hacked bootmgr, where mine does no matter what type of loader file is installed (to ensure that things are installed properly...but this can interfere with FD). I was thinking about making a command line switch so that a user could run O7A with the "/FD" (or something like that) switch so that when O7A installs the bootmgr file, it will not run the bootsect tool after installing the bootmgr file (it is the running of the bootsect.exe tool by O7A after installing the bootmgr file that disrupts FD, I will look into adding a command line switch so the user can force O7A not to run bootsect.exe after installing bootmgr (for the slic in bootmgr option only)).
Without really testing anything I have a suggestion to this current issue. FD-ISR must install some kind of file on the system right, odds are you can get a hex editor and look for "bootmgr" in the file, so simply rename the loader file to "bootldr" and insert this name into FD-ISR's file, this then making the bootup: Start PC => Power on self test...etc. => FD Loads => FD chain-loads GRLDR => GRLDR chainloads bootmgr The other method is to form a custom menu.lst which chainloads FD-ISR, either way would work but this one (custom menu.lst) is the one that would require no file editing I'm not sure what the command is to insert the SLIC on Carl's version but on my own it would look something like: Code: default 0 timeout 2 title Windows 7 (With loader) init fallback 1 find --set-root --ignore-floppies --ignore-cd /winx.ld chainloader /FD-ISR_file_here title Windows 7 (Without loader) find --set-root --ignore-floppies --ignore-cd /winx.ld chainloader /FD-ISR_file_here title Debug init --debug pause Press any key to boot find --set-root --ignore-floppies --ignore-cd /winx.ld chainloader /FD-ISR_file_here title Grub Command Line commandline
Those are both great ideas! I had thought of the first idea you mention already...but I dont know how comfortable carfal is with using a hex editor, so I didnt mention it... But that is a very valid idea. Just open the FD file that is running when your PC boots with a hex editor and search for "bootmgr" or "b.o.o.t.m.g.r" or something like that. You just have to be sure that the file name you replace "bootmgr" with is the same number of letters long (e.g. "grldrrr", or "bootldr" like Daz said, or something (and make sure you rename your grldr file to "grldrrr"/"bootldr"/whatever you named it, as well )) because you dont want to make the name shorter or longer as that would change the file and cause it to fail a CRC check...so it will not run. The second idea would probably work if FD is ok with being chain-loaded after the grldr file. I dont think FD would have a problem with that, so the second option might be the better route for carfal to go if he ever decides to ditch the "SLIC in bootmgr" setup he has and wants to use grub loader instead... Thanks for the great ideas Daz
No probs bud I have had an issue like this one on someones setup before and the custom menu setup really helps, it's very flexible but not very well documented when it comes to loader usage.
There is no "FD grldr" hehe. FD uses it's own bootloader type program to load up when your PC starts, then loads Windows (I dont know the name of the file FD uses, you would have to find that out). I have been trying to tell you this, but it seems I am not doing a very good job in explaining things In order to hex edit the file that you would need to edit, you will need to find out which file is being run when your PC boots. I would not recommend doing that though unless you are an advanced user, and can figure out which file is loading when your PC starts (it is not a "grldr" file, that is the loader file that programs like mine install and has nothing to do with FD)...and you can easily mess something up that could result in your computer not booting if you do something wrong (and you may have to reinstall Windows, or at the very least FD may get messed up and you will have to disable it and reinstall it), so keep that in mind. You might be better off just sticking with what you are doing now (the hacked bootmgr file) if you want to keep using FD... As far as the command line switch goes, in the next version of O7A that will be released I have added a "/NoBoot" command line switch (you can create a shortcut to the file as well, then edit the short cut to add the "/NoBoot" switch - so the command would be something like "Open 7 Activator.exe /NoBoot") because it will not be a commonly used thing. It is a specialized option for certain people who need it, so making it a selectable option will probably confuse more people than it helps. It will just make it so if you install the loader with the "Insert SLIC into bootmgr" option selected, after the hacked bootmgr file is installed the "bootsect.exe" tool will not be run so that nothing interferes with special programs that need to run at boot before Windows loads/starts...
HotCarl, I'm going to take your advice and stick with the "slic in bootmgr" option. It seems that FD will keep its secrets for now . Setting up the "/NoBoot" command line switch seems to be the better way to go after your explanation for choosing this method. When you release your next version, I will test it out and let you know how it goes.....fingers crossed
Hehe, right on. I always like it when people test my program out with some of the lesser used options, if you have the time of course, as I dont want you to have to feel obligated. It would provide good feedback though. Thank you for your interest! I am getting close to being finished with v1.2.6. I added a few things, changed a little bit...and now I am working on some code that when I get done with it, I should be done with v1.2.6 of O7A. It is just taking me so long because I am back in school now at the university and I am taking some harder classes this quarter, so that takes up a lot of my time...but I get a little closer each day.
@HotCarl Think nothing of it! Testing the changes that you're making for me is the least i can do Ultimately this work will improve the experience for everybody. Thankyou again for all your efforts. @DAZ Thankyou for your efforts as well DAZ. I will immediately try your customized method and report back here. I think that HotCarl wont mind if we borrow his thread for a little while. I know you have your own thread but since this started here it's probably best to finish it here for continuities sake Having more than one choice is good for the user IMO. What works for one may not work for the other as you guys already know. Please, keep up the great work.
@DAZ Your modified bootmgr file failed on my system. I followed your instruction as follows Uninstalled existing activator (assumed this is what should be done first) Installed Asus Cert and serial only (using your activator DAZ v1.7.7r) Took ownership of Bootmgr file Copied over and replaced all files in zip overwriting as required (only bootmgr required an overwrite) Rebooted Looked promising at first. The FD-ISR boot screen appeared. Continued to boot and then black screen with this message flashing at the top "Will Boot GRLDR from drive=0x80, partition=0x0 (hidden sectors=0x3f)" A subsequent reboot showed the same message and would not proceed any further. I have Rollback Rx installed so a simple rollback got me back up and running It may be important to note that i am running W7 x64. Could it be that the bootmgr file you supplied is for x32.
I posted the new version 1.2.6 in the OP! *1.2.6: ---Renamed the "I have modded BIOS" checkbox to "Install Key and Cert only" because of changes to how O7A loads. ---Made it so when you run O7A, the program automatically sets the "Install Key and Cert only" check box if SLIC 2.1 is already present. (For a 1-click activator setup ) ---Added new HP Windows 7 Ultimate product key. ---Added option to dump the SLIC to a file in Advanced Options window (thanks to PAYMYRENT and MasterDisaster!) ---Added option to dump the Certificate in the Advanced Options window. ---Added "/NoBoot" command-line argument (or switch). Using this argument when running O7A will make it so that when a user uses the "Insert SLIC into bootmgr" option, the hacked bootmgr will be installed normally but O7A will not run the "bootsect.exe" tool after. This is done to prevent interference with 3rd party apps like FD that need to run during boot. ---Added the following new SLICs and Certificates: Haier, TongFang. ---Updated help documentation.
lol...it looks like you hit the Uninstall Loader Only button on the Advanced Options form. I will take a closer look at that to see if there is anything wrong...
HotCarl, you've hit the nail on the head. I just tested v1.2.6 using the "/noboot" command line switch and selecting "slic in bootmgr" option. My FD-ISR is still intact and I'm successfully activated. If you would like to further develop this area of your program, I'll be more than glad to be a tester for this cause. Job well done. For me, the only thing your activator is missing now is encryption (which i believe you are working on). The icing on the cake would be to make the loaders (and even the slic in the bootmgrs) encrypted as well as STEALTH. This is something that i believe DAZ has already accomplished but is waiting on the release to the public. I know that you are very busy studying right now so the time constraints might make this not possible at this time. We all understand that your studies come first of coarse. Nevertheless, nobody can say that your activator in not brilliant as it stands. I thank you for all your efforts and support in this project that you have provided with no monitary benefit. I dont know how you do it but I'm glad you do.
Thank's for the new updated version,,, Nice working tool and good to have the new HP Windows 7 Ultimate product key ;-)
WOW, really nice changelog for v1.2.6! I will test it.. really great job HotCarl. I like this o change: