well timesurfer all i can say well done on v2.1 this is the best method on activating windows 7 that is out there other than some ppl using tools that they do not use right and wwack their system blaming the developers although this method you have to run from a clean install i tried it before on my system i did have hal7600 installed before remove it since its uncompatible with sp1 then reboot then run trilogy but messed up my system now i get it working well thanks for your hard work
lol...If they have WPA key delete for rearm reset again then we will know they like IR5 ...lol IR5 is for testing purposes only
They could go Office style and try to give you no rearms on remaking it. We'll have to look at win 8. Anyway, does the current Trilogy 2.1 IR5 reset the rearm count on Windows 7 SP1 enterprise? As you know I embedded a bunch of PID's in toolkit 2.1.3 but Phazor says some may not work with windows (and my AutoKMS has windows support). Since I cannot backup/restore on the fly in Windows, I thought using the IR5 would help in testing. (Also, I am using a VM so it's probably easier to just snapshot things anyway).
I might get around something like with IR5 but as far as I know SP1 has not affected win 7, Enterprise or R2
Thing I figure is if they start enforcing the "If I start and my registry is deleted then I lock down after I rebuild it" like OSPPSVC, you could still implement a AutoRearm/IORRT like setup by replacing the deleted WPA with a previously backed up state that had rearms available. A bit annoying since you can't mess with WPA inside windows, but still possible.
I'm always up for new ideas but right now I'm about to try to examine carefully how IR5 places and runs IR5.bat file from RE more constantly with perhaps error checking like I've done with IORRT Doesn't seem impossible to better check if IR5.bat was place correctly and should run without a doubt
@ingin7 - Actually, not meaning to correct TS but, Trilogy (the IR5 part, in this case) keeps you in trial without activating. @TS - Still trying to figure out where any IR5 issues are but getting nowhere yet.
I am patient and it's clear my recent past post will be starting point to see if we can do error checking for IR5.bat placement and execution in RE My advice is to do REM's above all 15 lines of install code then one by one we can examine and maybe improve IR5 install success rate given multilple boot config's and whatever else is rarely interfering with IR5 installation And yea IR5 still doesn't activate ...lol
surfer, I must be honest... RE is getting me crazy... During all kind of tries that i did, I couldn't execute IR5.bat from WinRE without looking for it in other HDD, cause it wasn't in C: when in WinRE. I totally cannot understand why in WinRE the HDD order is totally messed up, against the order i have in the regular Logon. My configuration is not so much complicated, even if i have 6 HDD connected : My Win 7 it's installed on an SSD connected to Channel 0 of the primary Intel SATA controller of the MoBo, and i also formatted it before Setup, so i don't even have the 100MB Hidden System Partition. I have another SSD and other 2 HDD SATA connected on the same controller, and then 2 IDE HDD connected to the PATA. If i execute Diskpart from Win 7, this one is the regular order of those HDD : SATA Channel 0 = Disk0 (C: ) Active Partition - and this one is the Boot Disk and System Disk too ; SATA Channel 1 = Disk1 (2nd SSD - no Letter assigned) SATA Channel 2 = Disk2 SATA Channel 3 = Disk3 PATA Master = Disk4 PATA Slave = Disk5 (First Partition is Active, but there are no Boot files on it at all...) ...and this is exactly what i could expect... Now, rebooting in WinRE, it looks like it's a totally different PC in Diskpart... Disk0 = PATA Master Disk1 = PATA Slave Disk2 = SATA Channel 1 (second SSD) Disk3 = SATA Channel 2 Disk4 = SATA Channel 3 Disk5 = SATA Channel 0 (primary SSD) Even if i don't know why, i think this is the real problem, cause we need to execute IR5.bat in WinRE to be able to remove the WAT Registry Section, but it looks like if you just have 2 HDD, you're not sure at all that in WinRE the bat file will be in C: ... It's totally insane, cause to start the Command Prompt, it's asking me My User and Pswrd, but O.S. it's now on H: (as we can see from Diskpart Disk List..) The execution of IR5.bat itself it's not then a problem, cause the "%dl%" variable in it it's calculated using the serialnumber of the HDD, so the other 2 files will be created in the REAL Systemdrive (C: , most of the time...) and executed at next Logon by the RunOnce "C:launch.bat"... So, ATM, the only thing that is upsetting me is that i couldn't find a way (if there's one...) to have WinRE starting from the REAL BOOT Partition... Anyone knows something more about it ?!? Clay