Jump to content

ricktendo

Members
  • Posts

    8,715
  • Joined

  • Last visited

  • Days Won

    444

Everything posted by ricktendo

  1. Really? I dont see anything, I use AdBlock Plus To you it might be a scam but to me its a life saver, I dont make much (aprox $5 a month) but I managed to save up to buy a refurbished E2500 router to replace my old WRT54G, now I am trying to save to buy a SSD (dont get much hardware donations so I have to improvise)
  2. Way ahead of ya 11-13-2012 Add: 2737083 Upd: SFX (removed /ain) BTW I removed /ain switch, because I noticed by default the installer runs ngen so I see no need in running it twice
  3. I know, because I missed a update but the new update was added, here is the true changelog (link should be working now) 11-13-2012 Add: 2729449, 2737019 Rem: 2328751, 2645609
  4. 11-13-2012 Add: 2729449
  5. 7z.dll 9.30.0.0 7z.exe 9.30.0.0 pea.exe TrIDDefs.TRD (4925 file types, 08/11/12) unarc.exe 0.67 (October 15, 2012)
  6. The problem is you are making a sfx with a sfx, why dont you use my sfx builder and repack it (remvoving any visual j stuff)
  7. I cant speak about the light bulbs but LED flashlights sure are good and bright
  8. Thats because visual j needs .net 2.0 to be installed, this is not a svcpack addon BTW you only need those if you are creating your own installers. You would apply the mst to the msi package so you are not forced by Microsoft Update to download a older version of the runtimes, this is the command you would use MsiTran.Exe -a <transform>.MST <installer>.MSI And yes, you are using the wrong sfx maker
  9. Updated with vc runtimes 2012 v11.0.51020.3 and apparently its now compatible with XP (also updated both sfx makers)
  10. Updated v11 (will do polish tomorrow)
  11. You will find the answer right under his post
  12. Maybe it does not work at that stage of the setup, try RunOnce
  13. Yea, but you may have to do a x86/x64 xml by hand
  14. You can use autounattended and still have the option, just dont fill out certain parts
  15. I would put a checkmark/warning somewhere (this will save time and detect & update the lowest and delete/replace the highest sku's,) then use imagex to detect the lowest edition in the wim, update it, see what editions it can be upgraded as, commit changes, export it as many times that are necessary (maybe also have a checkbox to what editions you want it to (re)create,) mount/change edition/commit/rename/re-flag all the images Or maybe put a thing in settings, where when you select the wim it will not ask you what image you want to update instead it will give you a popup warning saying that only the lowest will be updated and the highest will be recreated (also give an option what versions to rebuild)
  16. Use autounattend.xml to disable it and system restore (the toolkit may have those options in unattended)
  17. If you look in EVERY %WinDir%\ folder of an image you will see they all started off as being starter, because the all have a Starter.xml + <current_edition>.xml
  18. No, every version of Windows has all the necessary the files in the winsxs folder, this is why you can integrate ALL updates into any sku, the files are waiting there for you in case you ever upgrade your edition with anytime upgrade Use /Get-TargetEditions on a mounted image and it will let you know what versions it can be upgraded to, here is starter: Editions that can be upgraded to: Target Edition : Ultimate Target Edition : Professional Target Edition : HomePremium Target Edition : HomeBasic
  19. You know someting that could work lego, you could integrate the updates into the lowest sku and export it many times and then use dism to convert the next higher "target edition" (same way method used to turn Windows 8 Pro to ProfessionalWMC) Integrate the updates into Starter (for x86 iso's) or into Home Basic (for x64,) then you export it multipple times, mount each image and covert & rename them BTW off topic but you should see this new feature in Windows 8, its very, very cool you should find a way of adding this command to your tool http://www.msfn.org/board/topic/153742-dism-improvements-in-windows-8/page__view__findpost__p__1015509
  20. I just tested and it worked fine here. Are you sure you have pkey.txt in the same dir as the installer and are you sure it was not the original installer you were using?
  21. Correct, 4.5 replaces it. 4.0 is only still around for XP users
  22. Updated Note: may require you have openssl installed
  23. I would remove the (reg copy/add/delete) semicolon from ONLY the default RunProgram or (one of) the AutoInstall sections...use one for SVCPACK and then add or take away -ai(?) when installing WPI
×
×
  • Create New...