Jump to content


  • Content Count

  • Joined

About Uncle_Gadget

  • Rank

Profile Information

  • Gender
  • Location
    U.S.A. - Georgia
  • OS
    Windows 7 x64
  • Country
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I'd be completely lost without it, Rick. It's definitely used and appreciated by me!
  2. If I wanted to remove .NET 1.1 support, I could: 1) Delete the 'DNF11' folder and 2) Remove lines 63 and 64 (see below) from install.cmd, correct? START /WAIT DNF11\netfx.msi TRANSFORMS=NETFX11SP1.MST %VERBOSITY% /norestartSTART /WAIT WaitNET.exe %VERBOSITYSHORT%
  3. Rick, I'm not certain I follow the above. What do I do if I only want the GDR version? Is there a separate installer available?
  4. Fantastic, Rick! I'm looking forward to giving it a test drive later this week.
  5. Still blocked for me on IE9, FF19.0, and Chrome 25. It probaly works for you since you're logged into your account. Here's the link that returns in every case: http://www.mediafire.com/error.php?errno=393 Here's what's displayed:
  6. It appears that MediaFire is blocking the download link :rtfm: . Anxiously awaiting your fix.... :doh:
  7. If anyone's interested, I wrote a fairly sophisticated AutoIt script to add/remove to/from %PATH% using the registry. If you run it silently, it will generate an ERRORLEVEL if it encounters any errors while executing. Feel free to use or modify as needed. #region ;**** Directives created by AutoIt3Wrapper_GUI **** #AutoIt3Wrapper_Outfile=C:\Users\Public\Desktop\Uninstall.exe #AutoIt3Wrapper_Compression=4 #AutoIt3Wrapper_UseX64=n #AutoIt3Wrapper_Res_Description=Append or Remove elements from %PATH% #AutoIt3Wrapper_Res_Fileversion= #AutoIt3Wrapper_Res_Fileversion_AutoIncrement=p #Aut
  8. I was doing a bit more research and found the Registry Data Types below. Is there a difference between NOCLOBBER and APPEND? ; REG_MULTI_SZ_APPEND = 0x0001000A ; REG_MULTI_SZ_NOCLOBBER = 0x00010002 I know it doesn't help me with a REG_EXPAND_SZ, but wouldn't the line below work as an uninstall data type for REG_MULTI_SZ? ; REG_MULTI_SZ_DELVAL = 0x00010006
  9. Thanks. Even this helps. I'll probably write a simple AutoIt executable and execute it during RunPostSetupCommands=
  10. Once again I'm stuck on an inf problem. Does anyone know of a way to append to the %PATH% using an INF installer? I know that the path is stored in the registry at: HKLM,"SYSTEM\CurrentControlSet\Control\Session Manager\Environment","Path" And I know it would be easy to replace the path. The question is can I append to the existing path in the registry? And, then, to really complicate matters... Would there be a way to uninstall the appended path portion ONLY on an uninstall? I'm probably asking for too much, now. :albert:
  11. Rick, I've written my own Runtime installer and recently added the ability to uninstall older versions in the process. While I'm certain what I'm sharing is probably not new to you, I thought I'd pass it along, just in the off chance you might be able to use it. Below is the installer script I'm using. The GUID's were gathered through looking through old verions and are by no means exhaustive: ;Standard Dialog Box Installation RunProgram="hidcon:cmd /c FOR %i IN (837b34e3-7c30-493c-8f6a-2b0f04e2912c,a0fe116e-9a8a-466f-aee0-625cb7c207e3,710f4c1c-cc18-4c49-8cbf-51240c89a1a2) Do MsiExec /qn
  12. Sorry for not getting back sooner... I'm having the same issues as Thiersee, above. I've tried changing the Temp folder to "D:\Temp", "D:\WinToolkit", "D:\Temp\WinToolkit", and "D:\WinToolkit\Temp". I've even tried manually editing Settings.txt to these same folders. However, once I start Win Toolkit, it reverts back to "C:\WinToolkit" every single time. I have also verified that setttings.txt is not read-only. It doesn't change back until the program is restarted, but I have not tested it further because my concern is that it's going to use the C: drive no matter what the setting for "Win
  13. I've tried changing the "Win Toolkit Temp Folder" to a folder (I've tried several) on my drive D: and it ALWAYS reverts back to "C:\WinToolkit" every time I start the program. It's critical for me that Win Toolkit not use drive C: as it's an SSD drive on my system.
  14. I guess it's probably best for me just to wait until you do the updates. Thanks, again.
  15. Just to clarify, then.... The CleanSlimMSIs.7z contains the same msi's as Solor's dotNetFx40_Full_x86_x64_Slim.7z - with the exception that you have PRE-added the registry entries into the his msi's? So, if I replace Solor's msi's with your Clean MSI's, download the updates from Solor, and run his ApplyHotfixes.cmd, I should end up with basically the same result as using your slim installer from the OP? Do I have that correct?
  • Create New...