It's cool, I just prefer to install software at the setupcomplete stage, as it installs in the context of the default user which means it should be installed for all users of the machine, even when some apps install for this user only.
I had this little doubt regarding integrating the updates..As all the versions of windows might have different updates..I am not talking about the general ones but specific version updates..In that case would it be wise to integrate them through this kit?
excellent ongoing progress with this project ability to add programs in different folders very good addition. one caution .... REG entries run from the REG Folder .... entries seem to apply OK except for HKEY_CURRENT_USER (I have a fair ammount of serials that need applied here) I have to use runonce entry to get them to apply just before desktop. HKEY_LOCAL_MACHINE and other entries seem to apply from that folder ... just the above KEY that skips.
I'll check into it, but my first guess is if they created an update for starter or home basic only, that is IF, it would check version during integration and fail to integrate into ultimate. Luckily Microsoft is describing these situations clearly in the KB articles, and if I miss it, JUD, Johnny23 or someone else will catch it. One thing I noticed is that the opposite is happening, the MSXML update and the silverlight update were the same file for both x86 and x64. So far your concern hasn't been an issue yet.
I think CURRENT_USER has not been created at SetupComplete, I have had to use the runonce trick for CURRENT_USER settings since XP
put *.exe, *.msi, *.cmd, *.bat, *.reg, *.vbs, *.ps1 in Code: pre-activation_kit_v2.6.4\extras the make script now copies to the $OEM$ folder only .reg and .cmd are run at setupcomplete so you need to put your commands to launch the *.exe, *.msi, *.bat, *.vbs, *.ps1 in a .cmd
I don't know man, i'm guessing for whatever reason it mistakenly detects PQSERVICE as windows 7 partition. I haven't tried the latest version though, will give it a shot today and report back.
I`want to create a auto AIO activation disk with this program. I downloaded a ontouched nl_windows_7_ultimate_x64_dvd_x15-65920 + nl_windows_7_ultimate_x86_dvd_x15-65919 DVD. Whatever i do the application won`t past the first Check. i even changed the settings of the Make_AIO_DVD.cmd with the right SHA1 and .iso name. The program still said that the checksum is failed, what can i do to bypass this check? I use Hashcheck shell extension to read the sha1.
I havent changed anything that would make a diffrence for you, if it were me I would delete the partition. you could try marking diffrent partitions active.
the check is case sensitive that might be the problem, your sum should be lower case. delete this part if you are sure your iso is OK Code: IF EXIST "%~dp0%iso_file%" ( CLS ECHO checking 32 bit ISO... "%~dp0bin\sha1.exe" "%~dp0%iso_file%" | findstr %sha1_sum% >nul if errorlevel 1 ECHO checksum failed & PAUSE & EXIT) ELSE ( ECHO ISO not found & PAUSE & EXIT) CLS ECHO checking 32 bit ISO...OK IF EXIST "%~dp0%iso_file2%" ( CLS ECHO checking 32 bit ISO...OK ECHO checking 64 bit ISO... "%~dp0bin\sha1.exe" "%~dp0%iso_file2%" | findstr %sha1_sum2% >nul if errorlevel 1 ECHO checksum failed & PAUSE & EXIT) ELSE ( ECHO ISO not found & PAUSE & EXIT) CLS ECHO checking 32 bit ISO...OK ECHO checking 64 bit ISO...OK
Thanks for clarifying...so you are sure that those updates which are version specific will only be integrated if the version is correct..
there realy not that much diffrence between the editions, I have dissassembled a lot of the Windows 7 OS most of the time a .dll or .exe checks to see what edition is is running on and disables features based on that. it's likely that if an update was installed on the wrong edition it wouldnt do anything harmful.
I made the AIO DVD, the automatic activation function is working great, But i put in de specified folders the update`s with the updates_all.cmd for AIO, i also put a couple of drivers in de driver folders. The AIO have not instal these update`s and drivers. Maybe i do something wrong, must i put these folders in the $OEM$?? Or must i do something else?
first of all excuse my bad english. i hope everyone understands what i`m trying to say. i`ve tried it many times. now i`ve got a solution that works fine for me. i`ve got 11GB free space and the updates did not install. i`ve moved the pagefile.sys to another partition and resize my c: partition to get at least 15GB free space. what should i say? now everything works fine. hope this could help.