Gaav
Content Type
Profiles
Forums
Events
Posts posted by Gaav
-
-
Just a little question to the heroes who compile all these tweaks into one big .ZIP file:
Can you add a version/date to the zipfile?
Like: RegTweaks_v2005_05_31.zip, so you know how 'recent' the file is.
Thnx!
0 -
Firewall: your router, and Windows SP2 built-in firewall.
Anti-Virus: PC Cillin Internet Security 2005
Advanced Windows Tuning (software like tweakXP): none, tweak them in your silent install.
Download Utilities: none, it's in firefox. if you need one, GetRight will do fine.
E-Mail: MS Outlook 2003
Webdesign: Macromedia Dreamweaver MX 2004
Graphics Development: Adobe Photoshop CS
Hard-Drive optimization tools (defraggers for example): none
Windows error Checking (Like Norton Utilities): none
Antything else that comes to mind:
TotalCommander as filemanager
WhereIsIt for database
MSN Desktop search for finding files
FlashFXP for FTP
some newsgroup/p2p/irc tools
not to mention Office, Nero and some dictionairies, if you're building an office computer.
0 -
There will be a problem with your cleanup, cause in the Norwegian windows XP it is not called desktop.
my path to desktop is
%userprofile%\Skrivebord
(Dekstop is called Skrivebord).
This value is stored in the windows' registry. You can find it at:
HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
Don't know if it's possible to read out the registry using WPI, but if it is, you'll know where to find that, for 100% non-english compatiblity.
0 -
I miss the ultimate file-management tool Total Commander.
For free (shareware) download @ http://www.ghisler.com/
0 -
Comment out the shutdown code, and add 'PAUSE' at the end, so you can check/troubleshoot the error message.
0 -
Well, you just have to understand how .INF files are made.
After that, it's mad easy to setup.
A little bit quoted from the 'Microsoft Windows XP Registry Guide':
Installing INF FilesSetup Information files have the .inf extension; I call them INF files. The Windows XP setup API (Application Programming Interface) uses INF files to script installations. Most people associate INF files with device−driver installation, but applications often use them, too. Most actions that you associate with installing device drivers and applications are available through INF files. You can copy, remove, and rename files. You can add, change, and delete registry values. You can install and start services. You can install most anything using INF files. For example, you can use them to customize registry settings—obviously. You can also create INF files that users can uninstall using Add Or Remove Programs.
INF files look similar to INI and REG files. They're text files that contain sections that look like [section]. Each section contains items, sometimes called properties, that look like Name = Value.
Windows XP happens to come with the perfect INF−file editor: Notepad. When you create a new INF file using Notepad, make sure that you enclose the file name in quotation marks or choose All Files in the Save As Type list in the Save As dialog box. That way, your file will have the .inf extension instead of the .txt extension. Installing an INF file is straightforward: Right−click the INF file, and then click Install. To deploy an INF file and prevent users from having to install it manually,
use the following command, replacing Filename with the name of your INF file. (This is the command line that Windows XP associates with the .inf file extension in the registry.)
“rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 c:\windows\config.inf”
Listing 9−1 shows a simple INF file. The first section, [Version], is required. The name of the second section is arbitrary but usually [DefaultInstall] so that users can right−click the file to install it. The linkage to this section is through the command line you saw just before this paragraph. The command is rundll32.exe, which executes the API in Setupapi.dll called InstallHinfSection. The next item on the command line, DefaultInstall, is the name of the section to install. The 132 you see before the file name tells the setup API to prompt the user before rebooting the computer, if necessary. The last item on the command line is the name of the INF file to install. Like I mentioned, because this is the command that Windows XP associates with the .inf file extension, you should usually name this section [DefaultInstall]. Within this section you see two directives, AddReg andDelReg. the directive AddReg=Add.Settings adds the settings contained in the section [Add.Settings].
The directive DelReg=Del.Settings deletes the settings listed in the section [Del.Settings]. The names of these sections are arbitrary; you should adopt names that make sense to you and stick with them so you don't confuse yourself down the road.
Now you've had my two−dollar tour of an INF file. The sections that follow describe how to write the different parts of an INF file. I'm focusing on using INF files to edit the registry, but you can do much more with them. The ultimate resource for writing INF files is http://msdn.microsoft.com/library/en−...format_7soi.asp on Microsoft's Website. This is the INF File Sections and Directives section of the Windows Driver Development Kit (DDK). Don't let the fact that this information is in the DDK scare you; it's really straightforward and useful for much more than installing device drivers.
Using Strings in INF Files
You can make your INF files far easier to read if you use the [strings] section. Each line in this section is a string in the format name ="string". Then you can use that string elsewhere in the INF file by referencing it as %name%. This makes INF files easier to read in numerous ways (see Listing 9−4, which is also a good example of using the BitReg directive):
The [strings] section collects strings at the bottom of your INF file so that you can see them in one place.
The [strings] section enables you to type a string one time and then use that string in numerous places. The string is consistent throughout your INF file.
The [strings] section makes translating INF files easier because localizable strings are at the bottom of the file.
[Version]
Signature=$CHICAGO$
[DefaultInstall]
BitReg=Bits.Set
AddReg=Add.Settings
DelReg=Del.Settings
[Add.Settings]
HKCU,%HK_DESKTOP%,ActiveWndTrkTimeout,0x10001,1000
HKLM,%HK_SETUP%,RegisteredOwner,,%OWNER%
[Del.Settings]
HKCU,%HK_EXPLORER%\MenuOrder
HKCU,%HK_EXPLORER%\RunMRU
HKCU,%HK_EXPLORER%\RecentDocs
HKCU,%HK_EXPLORER%\ComDlg32\LastVisitedMRU
HKCU,%HK_SEARCH%\ACMru
HKCU,%HK_INTERNET%\TypedURLs
[Bits.Set]
HKCU,%HK_DESKTOP%,UserPreferencesMask,1,0x01,0
HKCU,%HK_DESKTOP%,UserPreferencesMask,1,0x40,0
[Strings]
HK_DESKTOP="Control Panel\Desktop"
HK_EXPLORER="Software\Microsoft\Windows\CurrentVersion\Explorer"
HK_SEARCH="Software\Microsoft\Search Assistant"
HK_INTERNET="Software\Microsoft\Internet Explorer"
HK_SETUP="SOFTWARE\Microsoft\Windows NT\CurrentVersion"
OWNER=" Fuzzy Wuzzy Was a Bear"I used this [strings] part for A LOT of options. So you only have to change the string value, instead of looking at the registry key.
Ie. in the AddReg section I have some lines called:
[Reg.Settings]
...
HKCU,"Software\Microsoft\Office\11.0\Outlook\Preferences","MinToTray",0x10001,"%Outlook.MinToTray%"
HKCU,"Software\Microsoft\Internet Explorer\Main","Disable Script Debugger",0x00000,"%IE.DisableScriptDebugger%"
HKCU,"Software\Microsoft\Ftp","Use PASV",0x00000,"%IE.FTPPassive%"
...Because they use variables, you have to edit the variable value instead of hard-code the desired value. This can be done at the [strings] section.
The [strings] section looks like this:
[Strings]
...
Outlook.MinToTray = 1
IE.FTPPassive = yes
IE.DisableScriptDebugger = Yes
...It's a little bit more work to enter a tweak for the first time, but after that you can change it's value EASIER than with .REG files.
Because you don't have to worry for REG_SZ, REG_DWORD values, you can just enter what you want [and besides, I added descriptions for almost all values]
0 -
Google: http://www.google.nl/search?q=cache:NKGPwd...02B30309D&hl=nl
Want to use Windows 2000 or Windows XP as a kiosk and you want to remove My Computer from the Desktop and Start Menu? Set {20D04FE0-3AEA-1069-A2D8-08002B30309D} = 1 in HKCU and HKLM :
Hive: HKEY_CURRENT_USER
Key: Software\Microsoft\Windows\CurrentVersion\Policies\NonEnum
Name: {20D04FE0-3AEA-1069-A2D8-08002B30309D}
Type: REG_DWORD
Value: 1 remove
Hive: HKEY_LOCAL_MACHINE
Key: Software\Microsoft\Windows\CurrentVersion\Policies\NonEnum
Name: {20D04FE0-3AEA-1069-A2D8-08002B30309D}
Type: REG_DWORD
Value: 1 remove
I bet you have to remove this rule from your regtweak thing:[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\NonEnum]
"{20D04FE0-3AEA-1069-A2D8-08002B30309D}"=dword:00000001
0 -
OK!
My first version of an VERY easy to change TWEAKS.INF.
How it works
It is an INF file, this is way more flexible than .REG files, and easier to maintain.
OK, so why all this?
Because I want all the tweaks in one file, with an easy option to enable/disable them.
What makes it different from all other .INF files, or even all other .REG files?
MUCH! I wanted some kind of 'linux-like' setup options. That is: edit a config file, and set the proper flags in order to get a thing working.
Since I created variables for most of the options, all you have to do is edit the part below the [strings] line.
Saves you enormous amounts of searching WHERE a certain setting is (I probably guess you don't care much anyway), so you can focus on WHAT you can change instead of HOW do I change option X or option Y.
It's missing some items!
Yeah? I KNOW! But this is the very first version, and don't expect all the regtweaks posted in this thread to be in this file already.
0
UA Registry Tweakage DOTNET (0.4 Released)
in Unattended Windows 2000/XP/2003
Posted · Edited by Gaav
Holy sh*t, this looks great!
I tried something as well with .INF files, but this one does a greater job with a nice GUI.
Since I don't know how you internally stored your tweaks, maybe you can use my .INF file for a little inspiration? I don't know how flexible your tool is coded, but an option to export to INF instead of REG would make your tool by far the #1 long-term-tweak-tool!
Thumbs up!
---
Found few minor bugs:
- Multimedia --> HKCU button is not selecting the 4th one.
- Context menus --> HKLM button is not selecting anything.
Suggestion:
- Appearance --> Default Desktop Wallpaper --> Add a 'browse' button next to the textfield
- All fields --> Make a 'direct link' next to the checkbox, which points you to a URL which explains the tweak, i.e. to a Winguides.com link or to some MS Knowledgebase article.
- All fields --> Add 'hover' text to the labels, which describes the tweak.
Major suggestion:
- Compile to INF file as well.
TWEAKS.rar