Everything posted by ricktendo
-
[Repack] 7-Zip 9.38 beta AiO x86-x64
Hey, welcome...Tip: if you want to rebuild MSI with InstEd: Go to Media table, right click on the CAB and choose Rebuild selected CABs, now go to Tables menu, Sumary Info... change Image type from Admin external long to Compressed long BTW I customize my personal 7zip MSI installer using this MST, it allows the installer to keep the language support but they only install on non English systems (it also adds a add/remove programs icon)
-
[Slim] .NET Framework 4.6.1 Full x86/x64 (2-27-2016)
Microsoft integrated updates uses the subkey \Microsoft .NET Framework 4.5, when we install/integrate a patch it uses \[ProductName] So the whatever is written as the ProductName in the Property table is used as the subkey SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4.5\KB#SOFTWARE\Microsoft\Updates\[ProductName]\KB#
-
[Slim] .NET Framework 4.6.1 Full x86/x64 (2-27-2016)
What it means by cumulative is you dont need 4.x, if you are on Windows 7 you already have .net 2.0/3.0/3.5, only on Vista will you need 3.x because it has 2.0 and on XP this is not compatible and already included in Windows 8.1 tistou77, why not do a repack? (you can find the links to the repack tools/resources on the 1st post) Extract the files from the installer, open the MSI in InstEd, go to the Property table and change the ProductName, recompress with 7zip and drag & drop the <archive>.7Z ont the <drag&drop>.CMD
-
[Slim] .NET Framework 4.6.1 Full x86/x64 (2-27-2016)
Dont use spaces before/after =
-
[Slim] .NET Framework 4.6.1 Full x86/x64 (2-27-2016)
Start, Run, type: cmd, hit Enter (this opens cmd.exe) You can also hold the SHIFT key, right click on empty space in folder of <installer>.exe and there will be an option to "Open command window here" Now type the name of the installer (or hit Tab button to automatically fill) followed by the command line, it should look like so X:\>installer.exe ProductName="whatever"
-
[Slim] .NET Framework 4.6.1 Full x86/x64 (2-27-2016)
Its a command line
-
[Rebuilt] .NET Framework 4.5.2 Full x86/x64 (9-19-2014)
Updated
-
[Slim] .NET Framework 4.6.1 Full x86/x64 (2-27-2016)
<installer>.exe ProductName="Your Product Name Here"
-
Windows XP Service Pack 4 [Unofficial]
Pined
-
[Slim] .NET Framework 4.6.1 Full x86/x64 (2-27-2016)
I prefer not to change as much as possible from the original, but if it bothers you, you can install it with ProductName="Your Product Name Here" and it should change that to whatever you wish
-
[Slim] .NET Framework 4.6.1 Full x86/x64 (2-27-2016)
Done!!! Hey Cipherfx2, do you know the KB# of the "All OS" package with the Windows 8/8.1 hotfix included? I prefer to use this installer for my other "Repack"
-
[Slim] .NET Framework 4.6.1 Full x86/x64 (2-27-2016)
It appears so, thanks
-
[QUESTION] Office 2013 Updates Integrated
SP1 is out so you can remove all those and add just the sp BTW you dont really need the xml files, also you need to keep the proof es-es and fr-fr
- All-In-One Integrator
-
All updates integration to windows 8.1 fails
Correct, from a Windows 8.1 to service another 8.1 (or lesser) you don't need to install ADK. Only if you are on 7/8.0
-
All updates integration to windows 8.1 fails
Download and install ADK for 8.1, open WinTK and go to Options - Misc and set a Custom DISM path (browse for the one in the ADK folder) Like I suggested, WinTK should detect that you are on Win7 integrating into Win8/8.1 and let you know that you need to upgrade your version of DISM in order for integration to work
-
sir how to enable/add gadgets by default in windows 8.1 iso image?
There is a sidebar installer ported from a Win8 Beta, maybe somebody should make a WinTK addon for it BTW http://winaero.com/download.php?view.60
-
[Slim] .NET Framework 4 Full x86/x64 (1-10-2016)
It is for Windows Vista/7 as well, I just dont see any reason to use it on them when there exists 4.5 and now 4.5.1
-
DAEMON Tools Pro - 5.8.0.0388 (SPTD - 1.86)
Updated
-
DAEMON Tools Lite - 4.49.1.356 (SPTD - 1.86)
Updated
-
Driver Integration Makes Installation Fail
Anything *USB* BTW no, I cannot get past the oobe...I integrate the older chipset driver (v9.0.0.1005,) then after setup I install the new one (v9.1.9.1006)
-
Driver Integration Makes Installation Fail
I have the same problem when I integrate my chipset drivers, I cannot use my mouse & kb during oobe...I have to integrate the older usb chipset drivers and after setup I install the latest I have ICH10 chipset (ichausb.inf) 02/25/2008, 9.0.0.1005 ***WORKING FINE*** 07/31/2013, 9.1.9.1006 ***USB BROKEN ON 1ST BOOT*** Curious, what is the hadware id of your usb chipset in the i5? (so I can tell you what INF it is)
-
Hello to every one here!..
De nada, Welcome
-
Driver Integration Makes Installation Fail
Start with excluding Mass Storage, they are usually to blame
-
Silent Install + keyboard language settings + Autounattended XML
You have to put your keyboard settings in oobe section BTW quick tip, to know what number to enter. Configure your keyboard just the way you want it (via the control panel,) then open a cmd prompt and enter dism /online /get-intl