Leaderboard

EXE install_wim_tweak.exe install_wim_tweak_NET4.6.exe SOURCE win6x_registry_tweak_src_v1.4.7.zip ----------------------------------------------------------------------------------------------------- Before i start i have to say that this tool was originally released by wnuku and that i have just updated it with extra features, colours and bug fixes. The original concept was by Aviv00. This little tool un-hides "packages" like Windows Media Center/Player, IE, IIS, Games, etc... so you can lower the size of your install.wim Top left is un-hiding a specific package, top right is writing the log of available files to a txt file, bottom left is un-hiding all components of an image and finally the bottom right is un-hiding all the packages from current installed OS. install_wim_tweak.exe /? This will show all available options.. install_wim_tweak.exe /p <MountPath> This will unhide all the packages in the selected image install_wim_tweak.exe /o This will unhide all the packages on the currently installed OS install_wim_tweak.exe /p <MountPath> /l This will list all the packages available in the selected image and write them to a text file in the same directory. install_wim_tweak.exe /o /l This will list all the packages available on the installed OS and write them to a text file in the same directory. install_wim_tweaks.exe /p <MountPath> /c Microsoft-Windows-......... This will just inhide the selected component from the selected image, can also be used with /o. If you add /r at the end it will remove the package. Changes made from the original version by wnuku */h will restore them to default (must use without /h first) */n will not create backups (faster) */d will not delete owners keys. */m is no longer needed, will do the task by default */l will output a list of all packages to a text file. */o will use currently installed image. *fixed a bug where it did not work if there was a space in the mountpath. */c <PackageName> will un-hide specific package * using /r with /c will remove the package *Win32Security.dll file is no longer needed *Added new colours, errors are displayed in Red *Fixed bug crashing at end of running *Fixed bug where it cannot unmount registry if something fails *Added specific component selection *Fixed some other bugs *Added an appropriate small icon for the app Also normally you will have to put the specific component name i.e. "/c Microsoft-Hyper-V-Common-Drivers-Package~31bf3856ad364e35~x86~~6.1.7601.17514" but if for example you put "/c Microsoft-Hyper-V-Common-Drivers-Package" it will show all packages starting with that. F.A.Q If you have any questions let me know...

512MB Graphics Cards have proven to be problematical when used with Windows 9x. I ran some tests with a nVidia 7200GS and a nVidia 7950GT on various Motherboards to determine why. Apparently nVidia decided to change their design approach after releasing some 512MB Cards. Previously they provided access to the entire Video RAM through the Memory Mapped I/O Space. This approach unfortunately limits the amount of System RAM that can be used by 32-Bit OSes. With the later 512MB Cards they decided to Bank Memory access through a smaller MMIO Space, typically 256MB. Starting with the 8xxx series they also implemented a Memory Page Mapper similar to the MMU in the CPU. The 7200GS is an example of the earlier design. The 7950GT is an example of the later one. The 82.69 nVidia Driver does not recognize the difference between the reported amount of Video RAM and the size of the MMIO Space allocated to the Card. The Driver overwrites the MMIO Space above the Video Card's allocation. Depending upon what is in the next 256MB of MMIO Space, your Computer can crash or other Devices, such as USB, can malfunction. A few people have been lucky enough not to have anything important in this space so they have been able to use a 7950GT although they only get 256MB. Others have not been so lucky. I have developed two solutions for this problem. 1. A Patch to the 82.69 Driver to make it recognize the smaller MMIO Space. 2. A BIOS Patcher for the nVidia BIOS ROM to increase the amount of MMIO Space it claims. The first is more universal but limits the Video RAM typically to 256MB. The second provides the full 512MB Video RAM of the Card. I am preparing a Package to put on my Website.

I use windows XP pro SP2 on my PC, my mac and my netbook, so I want all of you to tell me is it obsolete with SP2 and should I get SP3.

Ukrainian language for WinNTSetup 3.8.5.1 - https://yadi.sk/d/BSvXfdV1jfQcK

@All There is currently an issue with ALL board attachments, xper is looking into the matter, most probably a configuration change of some kind: http://www.msfn.org/board/topic/174609-attachment-system-flawed/ Wait until the problem is (hopefully) solved, keep an eye on the above thread... jaclaz

Worryingly, A client was talking to me yesterday about her laptop. Win8.1, running slowly since holidays..... do you still fix computers?..... She said, "Oh its the Windows 8 that everyone hates, I'm thinking about getting 10 since a friend told me it has a start MENU". I quickly advised her of classic shell and that I'd install it as soon I saw the machine. Also she told of how even though living with the new Windows 8 for some time... it still made no sense, and she gets completely lost. Sanity will be restored. A little SSD could wake up this decent Sandy Bridge Celeron, but not in the budget apparently, and hard to argue. Just another day.

Of course, I'm aware that the current model cannot fit anyone but any model never will. At the beginning, I didn't expect so great interest in my piece of software, so I didn't want to spend time with developing some complex licensing model and I just used simple code (which I had already developed and tested before) to have at least some benefits for individual donations. Because users were complaining that it is not so good to have a key locked to HW, I did a helpful step and have allowed to deactivate and generate a new key once a time. I believe that this must fit to the majority users and it is shown that only a few users criticize this. Sure, I could change this model completely but why to do it, when these rare situations are just artificial? Such users do not need the special license at all and they only use their plastic situation to criticize... just ask - how many users will ever need to change HDD/SSD twice a day and will require Aero Glass license just to test disk functionality? Also, there is some criticism about forcing donations and guessing the minimum amount. So, nobody forces anyone to donate, nobody forces anyone to use my software - if you don't like my model then simply do not use my software, nobody is forcing you. Also, guessing the minimum amount is not true - as I said many times - if you don't limit your donation to extreme small value (e.g. 0.001 €), you will get a key for any value. And if still talking about guessing then you should probably look at my website and you can see that there are value hints. So, no guessing but exact values are provided. And the last thing, the most criticism is in a form "I would buy this software but I don't like its licensing model so I will rather use a crack". So I am asking - if such user is really interested in buying my software why don't he contact me directly but he rather spends his time with waiting for and searching for a crack and then criticising (mostly in vulgar form) ? My answer - such user is not interested in buying at all, he would crack it regardless the licensing model and he just need some excuse why he uses the crack... and also my opinion is that the real reason for complaining is that there is still no usable crack for my software.