7 replies to this topic

[pppx00]

After selecting all the tweaks a button to export the current tweaks to a reg file.

Sometimes I wish I could apply the same settings in an already Windows 7 installation.

[ar_seven_am]

yupz, I think it's good idea too since we need to use regshot to know what registry changed/deleted after we apply that with W7Toolkit.

+1 for this!

[Legolash2o]

After selecting all the tweaks a button to export the current tweaks to a reg file.

Sometimes I wish I could apply the same settings in an already Windows 7 installation.

Select the tweaks you want, go to options tab, click 'Current OS' and click yes.

That will apply all tweaks to the current OS, you may need to restart

[ar_seven_am]

Select the tweaks you want, go to options tab, click 'Current OS' and click yes.

That will apply all tweaks to the current OS, you may need to restart

but lego, with exporting .reg file user may know what change so incase the tweak doesn't fit in his computer, he can revert back. (more like educational). Offcourse for some advanced user, he can also change back that (use regshot, system monitor etc), but how bout ppl who know minor things about computer?

[Etz]

...but how bout ppl who know minor things about computer?

In my opinion, they wont tinker with registry anyway...

[bphlpt]

Another reason for the reg file is that it could then be imported at another time to re-implement the same tweaks on another run. While those tweaks can already be saved and redone later, the advantage of offering this optional way to do it would be that if you already have another set of tweaks in a reg file that were created by another tool or by hand, then they could still be used by W7T. But I believe this import option is already available among the growing list of W7T options, so just consider it completing the symmetrical optional methods. LOL

Cheers and Regards

[Legolash2o]

Bump

[ianymaty]

Bump