Jump to content

crashfly

Members
  • Content Count

    405
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by crashfly


  1. And in that topic you posted, I submitted the following that "should" keep most people from seeing the nag.
     
    Supposedly, the following reg file will make it so the OS does not offer you a Windows 10 upgrade.  [Yes this still allows the updates, but for those computers that you just do not want the end user attempting to upgrade to Windows 10, this should work.]
     
    Save the following as a registry file and have Windows 7 load the file:

    Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Gwx]"DisableGwx"=dword:00000001

  2. Depends on the size of the donation. Also people who have been around for a while and helped out. :)

     

    That is cool. I will probably make another donation anyway.  I am doing better than I used to be (not great, but better).

     

    Edit:  I just realized, how does one make a donation now, or is there an "automated" way or what?


  3. This thread is very informative.  I appreciate the information provided.

     

    For additional useful information, (and those that still want the updates but not windows 10), there is an option to make sure the OS does not offer you a Windows 10 upgrade.  [Yes this still allows the updates, but for those computers that you just do not want the end user attempting to upgrade to Windows 10, this works wonders.]

     

    Save the following as a registry file and have Windows 7 load the file:

    Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Gwx]"DisableGwx"=dword:00000001

  4. I have not been around for a while and have a question about this new pricing scheme.  (Forgive me if someone has asked it already elsewhere.)

     

    If a person made a donation while WTK v1.x was being developed, will that carry over to v2.x?

     

    I just need to determine if I need to save up for a donation on this newer version. (Currently running on limited funds.)


  5. I realize you are working on rebuilding WinToolKit into a better tool.  On your other post,

    Completion:

    • Main Menu: 95%
    • EXE to MSP Converter: 80%
    • Language Pack Converter: 80%
    • MSU to CAB Converter: 80%
    you list the above "completion" percentages.  Does this mean your v2 is working as good as your v1 code (minus the not completed stuff), or do I just need to stick to v1?

  6. bphlpt was right, I was referring to the "SAD2" method.  It allows leaving the drivers or deleting them after completing.  I have used this method myself, and it seems to work well.

     

    You still integrate the basic drivers storage & chipset drivers, but everything else is put on the separate updatable disk/usb.


  7. Do as suggested above, except move all of the non-integrated drivers to their own DVD.  Over at the driverpacks website, there is a solution for an all inclusive install media that will install only what your computer needs.  (It uses a batch file to scan your drivers and only add those that need to be added.)


  8. RT7 is a much older program that removes items from Windows 7 install image in a "non-standard" way.  Therefore any resulting image will likely have some kind of issues due to the "non-standardness" of the removal process.

     

    If you can stand to not remove anything from the install image, and instead create an automated install that can *not* install those components you do not want, then that would be the safer way to create an install image.


  9. Unfortunately, Windows 7 does not have that option with DISM to remove/disable components from the DVD.  That feature was added to the Windows 8 DISM (but also is not able to remove/disable items under Win7).

     

    An alternative way around that is to use an autoattend.xml to install *only* what you want from your install disk. That is about the only way to "not" have some items installed under Windows 7.

     

    SIDE NOTE:  It appears that the "optionalfeatures.exe" does not have any command line options.  (One *might* be able to use an autoit or vbs script to automate an option removal, however this would only be able to be performed on a live working system.)


  10. For some reason i was under the impression i was only able to make 1 directory and that i could only make it directly under the drive letter.

     

    If you were referring to the $OEM$ folders option, you can actually create an unlimited amount of folders (only limited by space/filesystem) with the appropriate variable names for the $OEM$ folder documentation.  Microsoft has had OEMs do it this way for years. That is why many OEM install disks include way too much crapware.

     

     

    SIDE NOTE:  The following link can help with some of the folder 'variable' names you can use: http://technet.microsoft.com/en-us/library/cc766228%28WS.10%29.aspx


  11. To possibly save you some trouble, (or at least move you along when creating your own 7zip support), you might consider using the dlls written for 7zip.  The following is a quote from the 7zip.org faq.  I see no reason for you to "reinvent the wheel" when the code is already available for you.

    How can I add support for 7z archives to my application?

    One way is to use the 7z.dll or 7za.dll (available from sf.net for download). The 7za.dll works via COM interfaces. It, however, doesn't use standard COM interfaces for creating objects. You can find a small example in "CPP\7zip\UI\Client7z" folder in the source code. A full example is 7-Zip itself, since 7-Zip works via this dll also. There are other applications that use 7za.dll such as WinRAR, PowerArchiver and others.


  12. 2. Set up the OEM folder to \$OEM$\C\Users\Public\Desktop\Optional_Programs_to_install. Maybe put a text file with description what the end user should do with this folder and call this file from SetupComplete.cmd

    To be safer for most installations, the \$OEM$\C\Users\Public\Desktop\Optional_Programs_to_install should be rewritten as one of the following:

     

    \$OEM$\$1\Users\Public\Desktop\Optional_Programs_to_install

    or

    \$OEM$\$Docs\Public\Desktop\Optional_Programs_to_install

     

    The first option takes care of those who choose not to use the "C" drive as their install drive.  The second option is for those who also decide to rename their "Documents and Settings" folder.  It keeps your Windows setup working like it should.


  13. While I realize you are using WinToolKit as a project for your final year project, should you continue working on this "project" after you graduate, it would be nice to see some modularity.  Likely it is a bit much for now, but at least allow for the possibility after you have graduated.

     

    Modularity was something I suggested, so I would say table that suggestion for now.  If it is possible later, then I would still like to see that.

×
×
  • Create New...