monkee

Actually modify it, repack it, and re-distribute it.
Don't get me wrong, I like the idea. It's what Microsoft SHOULD do monthly. But they don't, since they have many people in management positions with an acute lack of vision. Apple's success of putting the consumer first, at least when it comes to the software ''experience'', sadly doesn't mean anything to Microsoft.

v1.4.0 is officially finished and will no longer be worked on. I've now started v1.5.0!!!
So far i've been improving old code and once i've done with the rest of the program, I will start getting all of those requests done. I've renamed v1.4.0 on the main downloads page to [sTABLE] and will also be available whilst the beta is available.
Download BETA
Requests and bug reports do NOT go in here, this is for general v1.5.0 discussion only!
News
I've made further improvements to Win Toolkit startup. Win Toolkit roughly took upto 12 seconds to load up especially if it got stuck on 'Checking for updates'. Win Toolkit has moved that task to the background and moved another few startup items around and will now bring you the main Win Toolkit screen in less than 0.2 seconds. Quicker than me blinking!!
In fact it was so quick, i couldn't read a single progress status before the main form appeared. If a new version appears a balloon notification will appear near your clock which you can click on to see what's new.
How does it work?
Previously, Win Toolkit had to wait until the update check procedure was completed before it would continue to show you the main screen. Now update checking has it's own thread which means Win Toolkit no longer has to wait for it to finish. The update checking will continue even when the main form is loaded which means you can get things done abit quicker!
Experimenting
I'm also going to be experimenting with AIO Integrator eventually. Adding a few more threading maybe, so it can for example integrate drivers and updates at the same and a bunch of other stuff simultaneously!

Although Windows 7 product activation function will keep reminding user how many days left to input a product key and activate the system in order to continue using the operating system beyond 30 days. In reality, Windows 7 also equip with a secret ‘rearm’ key in order to reset the free 30-day evaluation period limitation, which allows user to extend the activation-free usage or evaluation expiry date of Windows 7 for another 30 days legally.
Best of all, Microsoft provides 3 times of available ‘rearm’ count, as part of tool for system administrator to reset and restore activation state of Windows 7 to factory state during initial OOB (out of box) grace period. So, by using the ‘rearm’ hack, user can reset and extend the activation grace period (aka evaluation trial period) for up to 3 times, effectively running Windows 7 without product key without activation for up to 120 days, or 4 months. The trick is, the rearm hack must be done only when the 30 days trial period or activation grace period is about to expire.
‘Rearm’ trick on Windows 7 is done using the similar commands and steps with Windows Vista. Follow these steps to reset and extend activation grace period from 30 days to 120 days in Windows 7:
1.Install Windows 7 without any product activation key.
2.After installation is completed, use the Windows 7 for 30 days and wait for the remaining days left to activate Windows counting down to 0, or almost zero.
3.When the activation grace period (or evaluation trial period) is almost expired or ended, log on to Windows 7 desktop, and open a Command Prompt window (i.e. type Cmd in Start Search and hit Enter).
4.Type any of the following commands into the command prompt, and then hit Enter:
sysprep /generalize
slmgr.vbs –rearm
rundll32 slc.dll,SLReArmWindows
slmgr /rearm
5.Reboot Windows 7 to enjoy another 30 days of free usage without worrying about activation nor even need to crack Windows 7.
6.When the activation grace period countdown timer almost running down to 0 again, repeat the ‘rearm’ trick to enjoy another 30 days of Windows 7 for free. User can run the rearm command for maximum of 3 times.
As rearm only works for 3 times, make sure the command is only been run when the 30 days countdown of evaluation period is almost expired.
This gives you @ 4 months of "evaluation"...

Hey, I use Universal USB Installer for every single "system-installation-to-USB" work. Sure, it's focused on Linux distributions but at the bottom of your choices there are Windows Vista/7/8 Installer options. And the drive path is always formatted into FAT32.Works for me. Give it a try and tell me what you think.

1. Install Windows 7 to VHD from DVD
-----------------------------------------------------
With Windows 7, you now have the option to boot the OS from a VHD, a virtual disk file, instead of a partition. This way, you don't have to reconfigure your hard drive partitions.
Limitations: Hibernate is not supported.
Here are the simplified instructions:
1) Start Windows 7 installation from DVD.
2) Press Shift+F10 to start the command prompt.
3) Start diskpart.
4) Use the "create vdisk file=D:\Win7.vhd maximum=xxxxx" to create a virtual hard disk. Choose your drive and filename accordingly. xxxxx is in MB.
5) Type "select vdisk file=D:\Win7.vhd".
6) Type "attach vdisk". You will get a confirmation that it was attached.
7) Type "exit" to exit diskpart. And then close the command prompt.
8) Click on "Install Now" and install as you would normally by clicking on "Custom Install". Choose your attached vdisk as the location.
The installation takes care of adding the boot option to bcd. You don't have to do anything.
See Virtual Hard Disk Booting on a tutorial for VHD booting.
also check this out: Install Windows 7 to a VHD and add boot option to Vista's menu.
Basically, instead of installing windows 7 to your physical HDD by getting rid of Vista or even dual booting off another partition, you can install to a virtual HDD (in VHD format), and boot off the VHD so you actually get the hardware functionality to play with!!
Build 7068 does not allow calculation of the WEI score.
2. Install Existing VHD to Boot Menu of Windows 7
-------------------------------------------------------------------
If you already have a VHD that you want to boot from, you can simply add it to the boot menu rather than going through the above steps. If you have a Virtual PC image, for example, you can syprep it, then add it to Windows 7 menu. Vista's boot manager will not work - you have to update it to Windows 7 boot manager if you want this to work.
First, here how to add the vhd to the boot menu:
Open elevated command prompt, then type the following commands in sequence:
CODE
C:\>bcdedit /copy {current} /d "My New VHD Description"
C:\>bcdedit /set <guid> device vhd=[driveletter:]\<directory>\<vhd filename>
C:\>bcdedit /set <guid> osdevice vhd=[driverletter:]\<directory>\<vhd filename>
C:\>bcdedit /set <guid> detecthal on
Note: The first command will Return the GUID of the Loader Object that you will use to replace <guid> below
Note: vhd=[driveletter:]\<directory>\<vhd filename> is the new syntax supported for BCDEdit.exe to locate VHD File and Bootmgr will locate the partition containing the VHD File to boot from.
Type bcdedit /v to check the bcd store.
3. How to Boot VHD without Windows 7 Installed
-----------------------------------------------------------------
If you have Vista and want to boot a Window 7 VHD, then you need to copy the boot manager of Windows 7 to Vista's partition. You need to copy C:\bootmgr and C:\windows\system32\bcdedit.exe to an external source from Windows 7. You could extract these files from the Windows 7 VHD using WinImage or another program.
Then, open an elevated command prompt in Vista and unhide bootmgr (attrib -h -r -s bootmgr) and replace it with Windows 7's. Do same for bcdedit. You might consider making backup copies of these files before replacing them.
Then, add the VHD item to the boot menu using #2 above.
4. How to Remove
-------------------------
To remove, run the following command in a elevated command prompt:
CODE
bcdedit /delete {guid} /cleanup
Delete the vhd file.
Greets to spacesurfer!

If you move the page file from a system drive, system won't be able to create crash dumps in case of a system failure ex. blue screen.
I would use at least minimum page file on the system drive and use the 1.5X of RAM size on the second drive.