"To enable the Compatibility tab in Windows 2000 just like in WinXP/2003, all you have to do is start a command prompt, type this and hit Enter:
regsvr32 %windir%\apppatch\slayerui.dll
To be on the safe side you need to have already installed Service Pack 2 (SP2) or newer."
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows
Right-click in the right hand pane ->
select New -> DWORD Value [REG_DWORD] -> right-click on it -> select Rename -> change its name to read NoPopUpsOnBoot
-> click OK -> double-click on it -> select Decimal box -> type 1 -> click OK.
To reenable the display of boot
popup error messages, type 0 in the Decimal box above, or simply delete the NoPopUpsOnBoot DWORD
Value.
Close the Registry Editor when done.
The changed setting will take effect next time you (re)boot Windows.
More info @ Windows 2000 Resource Kits (RK).
"If you don't like the mouse shadow and have disabled it in Windows 2000/XP/2003, you may
notice that it's still there during login, before your personal settings are applied.
To get rid of it for good, open
Regedit and go to:
HKEY_USERS\.Default\Control Panel\Desktop
Right-click on the
"UserPreferenceMask" Binary Value [REG_BINARY] and choose Modify. In the four sets of numbers after the 0000 place
the mouse cursor behind the first two numbers, hit Backspace once and type in 30. Do the same with the second set and
enter 10. It should read 30 10 00 80. Then hit OK and close the Registry Editor.
Now the mouse shadow should
be gone from the login screen."
"When you connect to a web site, your computer is sent DNS -> IP resolver data from your DNS (Domain Naming System) server. This data is stored in a local data cache on your machine so that when you go to a web site more than once, your machine doesn't have to ask for that location every time. Although Windows has a pretty efficient DNS cache, you may want to increase its overall performance by increasing its size. To do this, run Regedit and go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters
In
the right hand pane create (if not present) or modify (if present) these DWORD [REG_DWORD] values (no quotes):
"CacheHashTableBucketSize", "CacheHashTableSize", "MaxCacheEntryTtlLimit",
"MaxSOACacheEntryTtlLimit", "NegativeCacheTime", "NetFailureCacheTime" and
"NegativeSOACacheTime".
The Decimal values that seem to work well are (consecutively): 40 (default: 10 ;
range: 0 - 50), 307 (default: 211 ; range: use ONLY prime numbers except 0!), 43200 (default: 86400 seconds =
24 hours ; range: 0 - 4294967295) and 90 (default: 120 seconds = 2 minutes ; range: 0 - 4294967295), 0
(default: 300 seconds = 5 minutes ; range: 0 - 4294967295), 0 (default: 30 seconds ; range: 0 - 4294967295) and
0 (default: 120 seconds = 2 minutes ; range: 0 - 4294967295).
There are other parameters within this key, but
unless you fully understand how the TCP/IP and DNS systems function, you should leave them unchanged."
More info @ MS TechNet.
"Windows 2000 is designed to run applications and services at different priorities.
System priorities are how much CPU time a program gets. For example, a high priority program gets more processing time than
a low priority program and will thereby run faster.
While application priorities can be set from the command line by
typing:
START /[priority] [program]
I have created an Explorer context menu add-on which allows you to change a program's priority. Simply save the following as a .REG file, merge it into the Registry, and then right-click on your desired application to select its priority level from the menu:
-----Begin cut & paste here----- REGEDIT4 [HKEY_CLASSES_ROOT\exefile\shell] [HKEY_CLASSES_ROOT\exefile\shell\XQSHP] @="Start &Realtime priority" [HKEY_CLASSES_ROOT\exefile\shell\XQSHP\Command] @="CMD.EXE /C START \"XQSHP\" /realtime \"%1\"" [HKEY_CLASSES_ROOT\exefile\shell\XQSHQ] @="Start &High priority" [HKEY_CLASSES_ROOT\exefile\shell\XQSHQ\Command] @="CMD.EXE /C START \"XQSHP\" /high \"%1\"" [HKEY_CLASSES_ROOT\exefile\shell\XQSHR] @="Start &Below Norm priority" [HKEY_CLASSES_ROOT\exefile\shell\XQSHR\Command] @="CMD.EXE /C START \"XQSHP\" /belownormal \"%1\"" [HKEY_CLASSES_ROOT\exefile\shell\XQSHS] @="Start &Low priority" [HKEY_CLASSES_ROOT\exefile\shell\XQSHS\Command] @="CMD.EXE /C START \"XQSHP\" /low \"%1\"" ------End cut & paste here------"
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TelnetServer\1.0
Modify the "MaxConnections" DWORD
[REG_DWORD] Value.
This value is also found in Windows 2000 Professional, but makes no difference, as you are allowed only
2 concurrent connections (hard limit).
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TelnetServer\1.0\Performance
Modify the "NumThreadsPerProcessor" DWORD [REG_DWORD] Value. A good choice is between 16 and 32."
"The default Windows 2000/XP shell font (for Explorer windows) is Tahoma, and the default system font (for System Properties, Device Manager etc) is MS Sans Serif. If you're bored with the defaults, the only way to change them is to alter the Registry. Open Regedit and go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes
Edit the "MS Shell
Dlg" String Value [REG_SZ] in the right hand pane and modify its "Microsoft Sans Serif" default value to match any
other font name installed on your system (i.e. Tahoma).
Then close Regedit and restart your computer for the change
to take effect."
IMPORTANT:
This
applies ONLY to the U.S. English final/Gold/RTM Windows 2000 + XP releases, NOT Beta/RCx, and CAN be achieved EXACTLY as
described below.
WARNING:
By replacing Microsoft files you may VOID the EULA,
warranty and/or support (if any).
You do all this at your OWN risk.
ALWAYS BACKUP FIRST!
To disable WFP in Windows 2000/XP, just follow these steps:
SFC /cachesize=0
and then:
SFC /purgecache
Here we go:
WARNING: If the actual bytes found in your DLL file DO NOT MATCH these values EXACTLY DO NOT make ANY changes!
"To disable WFP, start Regedit or Regedt32 and go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Add/modify the
"SFCDisable" DWORD [REG_DWORD] Binary entry to read FFFFFF9D.
Reboot when done.
To (re)enable WFP modify
"SFCDisable" to read 0."
These are all allowed "SFCDisable" values:
More info:
"In Windows NT4, 2000 and XP it is possible to initialize Windows in Error Mode, a
special debugging mode of the "stripped down" Safe Mode.
In Error Mode a small popup window (basically a core dump) shows
up whenever an application crashes, similar (but more detailed) to the well known "This program performed an illegal
operation" error message.
To enable this feature, run Regedit and go to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Windows
Modify the "ErrorMode" DWORD
[REG_DWORD] Decimal value from 0 to 1.
Reboot when done.
ErrorMode valid Decimal values:
Get File Manager 32-bit from Windows NT 4.0 SP6a, compatible with all Windows 2000/XP/2003 releases [free].
By default every time a directory is accessed or displayed, its "Last Access" date + time stamp is updated
by the OS.
To stop this time wasting annoyance and speed up the interface, run Regedit and go to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
In the right hand pane look for the
"NtfsDisableLastAccessUpdate" DWORD [REG_DWORD] Value.
If present: edit the Decimal Value to read 1.
If
absent: create a new DWORD Value: right-click on an empty spot in the right hand pane -> select New -> DWORD Value
-> name it "NtfsDisableLastAccessUpdate" -> double-click on it -> check the Decimal box -> type
1 -> click OK.
To revert to the OS default setting (always update NTFS "Last Access"): change 1 to read
0 in the Decimal box or delete "NtfsDisableLastAccessUpdate".
Close the Registry editor and reboot to see
the change.
Finally, click OK/Apply to save the new PIF settings.
BONUS [;-)]:
If connected to a network, and would like your DOS applications to be able to print to a network printer, add this command line to the batch file used to start your DOS program, or type this into a DOS box before running your DOS app:
NET USE LPTx: \\ComputerName\ShareName /PERSISTENT:YES
Replace "x" with the printer port number, "ComputerName" with your computer name and "ShareName" with your shared name for the specific network you are logging into... and don't type the quotes. :)
"This tip explains how to run Windows Explorer as a separate proccess in Windows NT
4.0, 2000, XP and 2003.
As many people know, Explorer is both a Windows shell as well as a file manager. While this is a
good design in terms of usability, it's not so good when it comes to memory usage. Under normal usage, Explorer may take as
much as 8 MB of vital RAM from your Windows system. This is due to a memory allocation problem in which Windows uses twice
the total memory for Explorer because it thinks it's using two separate programs. :( To solve this "integration" problem,
you need to make Explorer run as two separate proccesses instead of one. To do this, run Regedit and go to:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced
Look for the "SeparateProcess" DWORD [REG_DWORD] Value. Change its value from 0 to 1. After rebooting, Explorer will now run the shell and its file manager as two separate proccesses and will not try to allocate more memory than neccesary."
FYI: "There's an easier way to do this without modifying the Registry: in Windows
Explorer -> Tools -> Folder Options -> View -> Advanced Settings -> check the "Launch folder windows in a separate
process" box."
[Thank you Julio!]
"The "Open with Notepad" Registry trick [see "OPEN WITH", also in REGISTRY.TXT (part of W95-11D.EXE), for details]: adding a shell\Notepad command under this Registry key:
HKEY_CLASSES_ROOT\*
does NOT work properly in Windows 2000/XP.
The entry shows up, but the
generic "Open with..." insists on being the default. :(
But if you open Regedit, navigate to the CLSID listed at:
HKEY_CLASSES_ROOT\*\shellex\ContextMenuHandlers\OpenWith
and delete or rename the "MayChangeDefaultMenu" subkey, then Notepad becomes the default file opener."
"By default, Windows (and every other OS) uses port 21 for
FTP transfers. For most people, this is perfectly fine. But if you run an FTP Server like I do, problems could arise from
conflictions.
To resolve port conflicts, you'll want to enable "Web Based FTP". Basically this means that MS
Windows/MS IE will use the HTTP port 80 to access FTP, as will programs which take port settings directly from the
system itself.
To do this, open Regedit (or Regedt32) and go to:
HKEY_CURRENT_USER\Software\Microsoft\Ftp
There locate the "Use Web Based FTP" String value.
Change its value from "no" (default) to "yes" [no quotes].
After rebooting, your port problems should be
taken care of."
UPDATE: "This is slightly incorrect. Web Based FTP means that when you go to an
FTP site, Internet Explorer connects (on the regular FTP port) and gets whatever directory listing you need, then renders an
HTML page with the proper links automagically and displays it. This is compared to getting a DOS box with the ftp command
running, or, if you have the "Folder View of FTP sites" installed, Explorer style View. In other words, this setting will not
cause any conflicts with local ftp servers.
Example: when you make a client connection to a port, let's say, 21, the
actual connection isn't from your port 21 to their port 21. There is a random local port chosen, generally one above 10,000.
For example when I open a SSH connection, the actual connection I make is from me.foo.net:37388 to ssh.mysite.org:22
."
[Thank you Matt!]
If you have any ATA/66 (UDMA/66), or even better, any newer ATA/100 (UDMA/100) or ATA/133 (UDMA/133) EIDE hard disk(s) properly connected (using good quality 80 conductor IDE DMA66 ribbon cables) to the UltraDMA EIDE controller on your motherboard, it is strongly recommended to enable this setting, to take full advantage of the faster transfer rates these drives are capable of, which are (theoretically) close to 66 (ATA/66), 100 (ATA/100) or 133 (ATA/133) MB/second.
NOTE: This does NOT work with SCSI controllers/hard drives OR IF your (E)IDE/(U)ATA hard disks are connected to 3rd party/add-on/proprietary (E)IDE/(U)ATA/RAID drive controllers!
You must be logged on as Administrator to be able to do all this.
This option is disabled by default in
all Win2000/XP releases, no matter what (Intel X86 platform) controller/chipset you have.
Note that this setting is
NOT activated just by enabling the DMA item from: right-click on your My Computer icon -> click Properties -> Hardware
tab -> Device Manager -> IDE ATA/ATAPI controllers item -> select Primary and/or Secondary IDE Channel Properties -> click
Advanced Settings tab -> look under Transfer Mode for the "DMA if available" setting (you must also have "Ultra DMA
Mode" active under Current Transfer Mode for this to work). Then you need to repeat these steps for ALL your other IDE
Devices (drives) found here, numbered this way: Device 0, Device 1 etc. If you only have one IDE Device, select
"None" for all others to decrease bootup time. Now reboot when done, so the change(s) can take effect.
To activate
the ATA/66 (UDMA/66) setting, you need to run Regedit and go to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Class\{4D36E96A-E325-11CE-BFC1-08002BE10318}\0000Note
that the "0000" key above might show as "0001", "0002" and/or "0003" on your machine, depending
on your particular hardware settings. Select the key(s) appropriate to your case.
Right-click to create a new DWORD
[REG_DWORD] Value, call it "EnableUDMA66" (no quotes), and type 1 in the Decimal box to enable ATA/66 (UDMA/66)
support.
To disable it, change the Decimal value to 0, or delete "EnableUDMA66" altogether.
IMPORTANT: You also need to make sure the "EnableBigLba" DWORD [REG_DWORD] Value is turned ON under this Registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Atapi\Parameters
If "EnableBigLba" is set to
0, run Regedit, right-click on it and modify the Decimal box to read 1.
This requires 48-bit LBA (Logical
Block Addressing) motherboard BIOS support!
Reboot when done.
A MUST: To properly enable the UDMA/66 setting you MUST have your ATA/66/100/133 capable drive(s) hooked up to a SEPARATE IDE channel, OTHER than the one your older (E)IDE fixed/CD/DVD/removable drive(s) [even if ATA/33 (UDMA/33) capable] are connected to (if any)!
More info + fixes:
"I have a cable modem, but this also works great with xDSL modems.
I used the Registry values below
(and then rebooted for the new settings to take effect) to boost my modem throughput performance over the Internet
(TCP/IP).
Previously I was getting approximately 2500 kb/sec using Windows default values.
My current tweaked settings
[as shown in a REG file]:
-----Begin cut & paste
here----- [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters] ------End cut & paste
here------
REGEDIT4
"SackOpts"=dword:00000001
"TcpWindowSize"=dword:0005ae4c
"Tcp1323Opts"=dword:00000003
"DefaultTTL"=dword:00000040
"EnablePMTUBHDetect"=dword:00000000
"EnablePMTUDiscovery"=dword:00000001
"GlobalMaxTcpWindowSize"=dword:0005ae4c
More info @ MSKB.
To benchmark your modem speed gain use one of these online Speed Tests."
"I found these settings by playing with Microsoft TweakUI Power Toy for
Windows 9x/NT4/2000/ME [110 KB, free, unsupported].
I used Windows 2000 Professional in these examples, but this works
also with Windows XP and ME.
To do this, run Regedit (or Regedt32) and go to:
HKEY_CURRENT_USER\Control Panel\Desktop
Purpose: application window grabbing focus.
When a window
that doesn't have the focus (in the background) is updated by its parent program, Win2K by default prevents it from becoming
the topmost window. Instead it flashes the taskbar button. This is governed by these DWORD [REG_DWORD] Values:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Kbdclass\Parameters
Look for (or create if not
present) the "KeyboardDataQueueSize" DWORD [REG_DWORD] Value in the right hand pane -> double-click on it -> check the
Decimal box -> double the value shown there (default is 100) -> type in the new integer number -> click
OK.
Then, under the same Registry key, find/create the "PollStatusIterations" DWORD Value, and increase it from
1 (default) to 2 or 4, by performing same steps above, until your keyboard no longer exhibits
interruptions.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Mouclass\Parameters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Sermouse\Parameters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Busmouse\Parameters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Inport\Parameters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msi8042\Parameters
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\mouhid\Parameters
In the right hand pane,
find (or create if not present) the "MouseDataQueueSize" DWORD Value -> double-click on it -> check the Decimal box ->
double the value shown there (default is 100) -> type in the new integer number -> click OK.
Also, if you
notice that your mouse clicks randomly WITHOUT you touching it, find/create the "MouseSynchIn100ns" DWORD Value ->
double-click on it -> check the Decimal box -> increase the value shown (default is 20000000 = 2 seconds) to let's say
30000000 (3 seconds), or even higher if necessary -> type in the new integer number -> click OK.
More info @ MSKB:
CAUTION: This will affect system security, leaving your computer unprotected!
Start
by BACKING UP your Registry files!
Then run Regedit and go to:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
In the right hand pane look
for the "AutoAdminLogon", "AutoLogonCount" {DWORD [REG_DWORD] Value}, "DefaultDomainName",
"DefaultUserName" and "DefaultPassword" String [REG_SZ] Values.
Highlight "AutoAdminLogon" ->
right-click on it -> select Modify -> change its value to 1 -> click OK.
Highlight "AutoLogonCount" ->
right-click on it -> select Modify -> check the Decimal box -> change its value to 4294967295 (maximum allowed) ->
click OK. This is MANDATORY to be able to take advantage of the auto login feature more than once. [4294967295 times
should be plenty. :)]
Now highlight "DefaultUserName" -> right-click on it -> select Modify -> change the text to
match your UserName (default is "Administrator" if you haven't changed it) -> click OK.
Repeat same steps for
"DefaultPassword". [Choose your Password wisely! :)]
If you are not logging into or do not have a (Network) Domain
account, you can leave the "DefaultDomainName" String Value empty, or delete it altogether.
If any of these Strings
do not exist, you need to create them: right-click on an empty spot in the Regedit right hand pane -> select New -> String or
DWORD Value -> assign it one of the names above -> press Enter -> right-click on it -> type in the appropriate text string
(as described above) -> click OK -> restart Windows when done.
If you are unwilling to "mess" with your Registry, you can also achieve this by using one of these Registry tweaking tools:
control userpasswords2
Hit Enter or click OK -> make sure there is NO check mark beside Users -> enter the User Name and Password you wish -> click Apply/OK/Yes until all following dialog boxes are closed -> restart Windows.
Optionally, if you need to log on into a NetWare Domain/Network, go to (using Regedit):
HKEY_LOCAL_MACHINE\Software\Novell\NWGINA\Login
In the right hand pane look for the
"NetWareAutoAdminLogon", "DefaultNetWareUserName" and "DefaultNetWarePassword" String Values.
Repeat
the same operations above for these entries: type 1 in the "NetWareAutoAdminLogon" box, and respectively your
NetWare UserName and Password. Restart Windows when done.
BEWARE that all these Password strings are kept in the Registry as plain text: unencrypted! Therefore anybody with access to your computer, who knows how to change the Registry [this includes you now :)], CAN alter/delete them at will!
UPDATE: "There is another way to accomplish the same task without modifying the Registry: Start menu ->
Settings -> Control Panel -> Users and Passwords. Here you will find the "Users must enter a user name and password to use
this computer" option. When this is checked the user must enter a user name and password every time to access the
computer. If unchecked the user will be required to enter a user name and password only once after which the computer will
use this as the default and automatically log on for you."
[Thank you Al!]
CD DO
and then hold Ctrl and hit D.
All directories containing D and O as their first 2 letters will be listed (if any).
Run:
CMD /F:ON
to enable file/directory name completion temporarily, only for the current DOS session.
To disable this
feature for the current DOS session, type:
CMD /F:OFF
To enable this feature permanently, for all DOS sessions, you need to run Regedit or Regedt32, and go to:
HKEY_CURRENT_USER\Software\Microsoft\Command Processor
for the current user on your machine, or to:
HKEY_LOCAL_MACHINE\Software\Microsoft\Command Processor
for all users on your computer.
Second Registry key above takes precedence.
Now look in the right hand pane for these two DWORD [REG_DWORD] values (create
them if not present): "CompletionChar" and "PathCompletionChar". These contain the hex values for the custom
"key combos" to use as file (1st DWORD above) and respectively directory (2nd DWORD above) completion hot keys.
Default
values are (you may need to type them in if not present): 0x4 (to use Ctrl+D for file completion) and 0x6 (to
use Ctrl+F for directory completion). A value of 0 turns them off. Any other value (ranging from 0x1 to
0x1F, to match the ASCII code of a valid key) turns them on.
It is possible to use other key combos, or even single
keys to perform this function. Example: type 0x9 to use the Tab key.
If there are more than one file/directory
match on your system, the first one is displayed when you activate the key "combo". If you press the hot key(s) again, the
next match appears, and so on.
To cycle backwards through multiple matches, use Shift+F or Shift+D, if you
are using the default DWORD values (see above).
More info:
"I have spent 2 weeks, countless hours, and $20 on a new sound card,
and then jockeying cards around trying to "debug" the cause of spontaneous reboots on my Win2000 Pro PC.
Turns out there
is a setting in: Start -> Settings -> Control Panel -> System -> Advanced -> Start Up and Recovery -> uncheck
Automatically Reboot (Restart) on system failure, that may be the culprit.
More info.
PS: I am using WinMag Wintune video test features to torture test and attempt to
cause another spontaneous reboot. Before clearing this checkbox, I could force a reboot just by loading Wintune's system and
video benchmarks. Haven't gotten this to work again since I cleared the checkbox so I may be on to something."
UPDATES: