Mood:
don't askNow Playing: Full Throttle
Hello! World.... How are You Doing Today......
 |
 |
 |
 |
|
You are not logged in.
Log in
|
|
My Blog
Friday, 18 September 2009
Techincal Checks
Mood: don't askNow Playing: Full Throttle
Techincal Checks
Mood: don't askNow Playing: Full Throttle eonot Editions for personal computers [edit] Comparison chart
Notes Upgrade paths from Windows XP and between different Vista editions. Dotted lines indicate the need for a "clean install".Users can sometimes upgrade from Windows XP to Windows Vista, or upgrade from one version of Windows Vista to another. However, not all potential upgrade combinations exist. The accompanying chart indicates the possible upgrade paths: Note: If the user is running a 32bit version of the original operating system, the user must upgrade to a 32bit version of the new operating system or do a clean install.
[edit] Disk interface families used in personal computers
In order to overcome the volume size limit of FAT16, while still allowing DOS real mode code to handle the format without unnecessarily reducing the available conventional memory, Microsoft implemented a newer generation of FAT, known as FAT32, with cluster values held in a 32-bit field, of which 28 bits are used to hold the cluster number, for a maximum of approximately 268 million (228) clusters. This allows for drive sizes of up to 8 terabytes with 32KB clusters, but the boot sector uses a 32-bit field for the sector count, limiting volume size to 2 TB on a hard disk with 512 byte sectors. The maximum possible size for a file on a FAT32 volume is 4 GB minus 1 byte (232−1 bytes). Video applications, large databases, and some other software easily exceed this limit. Larger files require another formatting type such as NTFS. Physical Memory Limits: Windows Vista
Aero- Min 1 GB of RAM Min HDD Size-15 GB
Windows Vista Home Premium, Windows Vista Business, Windows Vista Enterprise, and Windows Vista Ultimate |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Setup Phase | Shift+F10 path | Important Log Files | Possible location(s) for user files and settings |
Downlevel | D:\Sources\ | C:\WINDOWS\setup*.log C:\$WINDOWS.~BT\Sources\Panther\setup*.log C:\$WINDOWS.~BT\Sources\Panther\PreGatherPnPList.log | No changes |
REBOOT | |||
WinPE | Install from downlevel: Boot-from-DVD install: | Install from downlevel: Boot-from-DVD install: | C:\Documents and Settings C:\$INPLACE.~TR\Machine\DATA\Documents and Settings\ C:\$WINDOWS.~Q\DATA\Documents and Settings |
REBOOT | |||
Online Config (Firstboot) | C:\Windows\System32\ | C:\WINDOWS\PANTHER\setup*.log C:\WINDOWS\INF\setupapi*.log C:\$WINDOWS.~BT\Sources\Panther\PostGatherPnPList.log | C:\$INPLACE.~TR\Machine\DATA\Documents and Settings\ C:\$WINDOWS.~Q\DATA\Documents and Settings\ C:\Users\ |
REBOOT | |||
Windows Welcome (OOBE) | C:\Windows\System32\ | C:\WINDOWS\PANTHER\setup*.log C:\WINDOWS\INF\setupapi*.log C:\WINDOWS\Performance\Winsat\winsat.log | C:\$INPLACE.~TR\Machine\DATA\Documents and Settings\ C:\$WINDOWS.~Q\DATA\Documents and Settings\ C:\Users\ |
Note: If setup rolls back in the event of a fatal error during setup (upgrade), include the log location $windows.~bt\sources\rollback
Download Virtual Machine Path
EMP Code :- Y-1624
Windows Vista Boot Process
* Sys is powered on
* Cmos loads the bios and then runs POST
* Looks for the MBR on the bootable devcie
* Through the MBR the Boot sector is located and the BOOTMGR is loaded
* BOOTMGR looks for active partition
* BOOTMGR reads the BCD files from \boot directory on the active partition
* The BCD (Boot Configuration Database) contains various config parameters, ( this info was previously stored in the boot.ini)
* When windows vista is selected, BOOTMGR transfer control to the Windows Loader
(winload.exe) or winresume.exe in case the sys was in hibernated.
* Winloader loads drivers that are set to start at boot and then transfers the control to the windows Kernel
* There is not msgina.dll in windows vista( the shell draws the login screen)
POST --> MBR --> Booting --> BCD --> Kernel --> Registry Hives
Kernel Mode:- Hardware & Software/Date (Registry---Services), HAL.dll(Hardware Abstraction Layer)
User Mode:- Software Config
Hibernation files are saved in HDD as (hyberfil.sys in Xp ) and as (winresume.exe in Vista)
Windows Vista Repair
WinRE Options
*Startup Repair
* System Restore
* Windows Complete PC Restore
* Windows Memory Diagnostic Tool
* Command Prompt
There is no Recovery Console in Vista but called Command Prompt
(Automated System Recovery in XP)
rstrui.exe(Command for restore)
Backup and Restore Center to Backup Entire PC or Files and restore points
FILE Indexing
CHKDSK /F
CHKDSK /V
CHKDSK /R
CHKDSK /L:size
CHKDSK /X
CHKDSK /I
CHKDSK /C
CHKDSK /B
The /I or /C switch reduces the
REVERTING Windows.Old
C:\Ren windows Windows.vista1
C:\xcopy /s c:\windows.old\*.* c:\
cd Drive:\boot\bootsect /nt52 c:
Expand cddrive:\i386\vgaoem.fo_ c:\windows\system\
My Computer-> C ->Folder option ->uncheck show hidden file
Rename boot.bak to boot.ini
WINRE Usage
No boot situations
New hardware/SW -> Stop errror
Rollback to Previous OS
Memory Diagnostics
System Restore
Coverting FAT to NTFS
Convert C:\ /FS:NTFS
C:\(P)
Article:- 315338
Clean Installation
Copying Files
Expanding files
Installing Features
Installing Updates
Completing Installations
UPGRADING PROCESS
Copying Windows Files
Gathering Files
Expanding Files
Instaling features and Updates
Completing Upgrades
REGISTRY HIVES
Most of the supporting files for the hives are in the %SystemRoot%\System32\Config directory. These files are updated each time a user logs on. The file name extensions of the files in these directories, or in some cases a lack of an extension, indicate the type of data they contain.
The following table lists the standard hives and their supporting files.
| Registry hive | Supporting files |
|---|---|
| HKEY_CURRENT_CONFIG | System, System.alt, System.log, System.sav |
| HKEY_CURRENT_USER | Ntuser.dat, Ntuser.dat.log |
| HKEY_LOCAL_MACHINE\SAM | Sam, Sam.log, Sam.sav |
| HKEY_LOCAL_MACHINE\Security | Security, Security.log, Security.sav |
| HKEY_LOCAL_MACHINE\Software | Software, Software.log, Software.sav |
| HKEY_LOCAL_MACHINE\System | System, System.alt, System.log, System.sav |
| HKEY_USERS\.DEFAULT | Default, Default.log, Default.sav |
A list of all active hives can be found at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\hivelist
HKEY_LOCAL_MACHINE\HARDWARE has no corresponding file because it is a volatile key that is created (and built) by the kernel at system start.
FILE INDEXING
What is the index?
Supported File Replacement Mechanisms
Replacement of protected system files is supported using the following mechanisms:
| • | Windows Service Pack installation (UPDATE.EXE) |
| • | Hotfix distributions installed using HOTFIX.EXE |
| • | Operating system upgrade (WINNT32.EXE) |
SFCDllCacheDir
Value: <location of dllcache directory>
Default: %Systemroot%\system32\dllcache
Specifies the location of the dllcache directory. This path must be a local path.
Example: SFCDllCacheDir = "C:\Winnt\System32\dllcache"
Disabling Windows File Protection
You may disable WFP by setting the value SFCDisable (REG_DWORD) in HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows NT\ CurrentVersion\ Winlogon. By default, SFCDisable is set to 0, which means WFP is active. Setting SFCDisable to 1 will disable WFP. Setting SFCDisable to 2 will disable WFP for the next system restart only (without a prompt to re-enable).
Important: You must have a kernel debugger attached to the system via null modem cable (for example:I386kd.exe or Windbg.exe) to use SFCDisable = 1 or SFCDisable = 2.
After WFP is disabled using the SFCDisable = 1 setting, the following message will appear after logon:
Warning! Windows File Protection is not active on this system. Would you like to enable Windows File Protection now? This will enable Windows File Protection until the next system restart. <Yes> <No>.
Clicking Yes will reactivate WFP until the next system restart. This message will appear at every successful logon until SFCDisable is set to 0.
NOTE: The above message will only be presented to Administrators.
Additional Registry Settings
All registry settings for WFP/System File Checker are located in HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows NT\ CurrentVersion\ Winlogon. By default, only Administrators and System will be able to modify these settings.
SFCDisable (REG_DWORD)
0 = enabled (default).
1 = disabled, prompt at boot to re-enable (debugger required).
2 = disabled at next boot only, no prompt to re-enable (debugger required).
SFCScan (REG_DWORD)
0 = do not scan protected files at boot (default).
1 = scan protected files at every boot.
2 = scan protected files once.
SFCQuota (REG_DWORD)
n = size (in megabytes) of dllcache quota.
FFFFFFFF = cache-protected system files on the local hard drive.
SFCShowProgress (REG_DWORD)
0 = System File Checker progress meter is not displayed.
1 = System File Checker progress meter is displayed (default).
SFCDllCacheDir (REG_EXPAND_SZ)
Path = local location of dllcache directory (default is %Systemroot%\system32\dllcache).
Registry Hives
A hive is a logical group of keys, subkeys, and values in the registry that has a set of supporting files containing backups of its data.
Each time a new user logs on to a computer, a new hive is created for that user with a separate file for the user profile. This is called the user profile hive. A user's hive contains specific registry information pertaining to the user's application settings, desktop, environment, network connections, and printers. User profile hives are located under the HKEY_USERS key.
Registry files have the following two formats: standard and latest. The standard format is the only format supported by Windows 2000. It is also supported by later versions of Windows for backward compatibility. The latest format is supported starting with Windows XP. On versions of Windows that support the latest format, the following hives still use the standard format: HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE\SAM, HKEY_LOCAL_MACHINE\Security, and HKEY_USERS\.DEFAULT; all other hives use the latest format.
Most of the supporting files for the hives are in the %SystemRoot%\System32\Config directory. These files are updated each time a user logs on. The file name extensions of the files in these directories, or in some cases a lack of an extension, indicate the type of data they contain. The following table lists these extensions along with a description of the data in the file.
| Extension | Description |
|---|---|
none | A complete copy of the hive data. |
.alt | A backup copy of the critical HKEY_LOCAL_MACHINE\System hive. Only the System key has an .alt file. |
.log | A transaction log of changes to the keys and value entries in the hive. |
.sav | Copies of the hive files as they looked at the end of the text-mode stage in Setup. Setup has two stages: text mode and graphics mode. The hive is copied to a .sav file after the text-mode stage of setup to protect it from errors that might occur if the graphics-mode stage of setup fails. If setup fails during the graphics-mode stage, only the graphics-mode stage is repeated when the computer is restarted; the .sav file is used to restore the hive data |
The following table lists the standard hives and their supporting files.
| Registry hive | Supporting files |
|---|---|
| HKEY_CURRENT_CONFIG | System, System.alt, System.log, System.sav |
| HKEY_CURRENT_USER | Ntuser.dat, Ntuser.dat.log |
| HKEY_LOCAL_MACHINE\SAM | Sam, Sam.log, Sam.sav |
| HKEY_LOCAL_MACHINE\Security | Security, Security.log, Security.sav |
| HKEY_LOCAL_MACHINE\Software | Software, Software.log, Software.sav |
| HKEY_LOCAL_MACHINE\System | System, System.alt, System.log, System.sav |
| HKEY_USERS\.DEFAULT | Default, Default.log, Default.sav |
Backup and Restore
Internet Options
PC Tuneup
Delete Cookies
Clear SSL
Disable any addons not required
Restore All Setings
Remove third Party extensions
Clear Temp Files...
Temp
%temp%
Prefetch
IE Optimization
Disk Cleaner(Cleanmgr)
Check for Virtual Memory(Increan Virtual memory)
Clear Startup items
Unistall any expired Softwares
Check CPU Usage(If more than 10% Run Spyware/Malware tools)
Clear event log files(Event Viewer)
Setting Default Programs
Control Panel ->Set Program Access and Computer Defaults ->Choose The Program to Run as Default Program
Control Panel ->Set Your Defaults Program
Control Panel ->Associate a File Type or Protocol with a Program
Control Panel -> Change AutoPlay Settings
VEN_ Vendor Id
DEV_ Device Id
Using memory in your storage device to speed up your computer
Some universal serial bus (USB) storage devices contain both slow and fast flash memory, and Windows can only use fast flash memory to speed up your computer. So if your device contains both slow and fast memory, keep in mind that you can only use the fast memory portion for this purpose.
The recommended amount of memory to use for Windows ReadyBoost acceleration is one to three times the amount of random access memory (RAM) installed in your computer. For instance, if your computer has 512 megabytes (MB) of RAM and you plug in a 4 gigabyte (GB) USB flash drive, setting aside from 512 MB to 1.5 GB of that drive will offer the best performance boost. The minimum size for any USB flash drive to work with Windows ReadyBoost is 256 MB.
Although with Vista, Microsoft has made great strides in the stability of its Windows operating system, things can still go wrong.
What happens when a key driver goes missing or a system disk fails? How would you go about recovering the system and especially, all your precious data?
Problem: How do you recover a damaged Vista system?
There are basically two ways to recover a damaged Windows Vista system: the installation DVD or the Windows Recovery Environment (WinRE).
Solution #1: Use your installation DVD to boot up your system.
This is the simplest method. All you have to do is locate your installation DVD and use it to boot up your damaged system. This launches the Windows Vista installation.
Don’t worry, you’re not going to reinstall Vista. All you want is to get to the “Install now” screen.
The process begins by launching the Windows Preinstallation Environment (Windows PE), a simplified version of Windows that runs in memory only and is designed to replace DOS. Then it presents a screen which asks for three things:
- Language to install
- Time and currency format
- Keyboard or input method
Making a selection and clicking Next will bring you to the “Install now” screen. What you’re looking for is the two options in the lower left corner of the screen:
- What to know before installing Windows
- Repair your computer
Clicking “Repair your computer” will move you to another screen that lets you choose your existing system partition. When you click Next, you’ll get a series of choices for system repair. From there on, just follow the prompts.
Solution #2: Use the WinRE console to diagnose and repair the problem.
The problem with using the installation DVD is that you might not always have the disk on hand. If you want to make sure your system is always running but don’t want to depend on the installation media, then you can use WinRE.
The WinRE console is new to Windows Vista and is specifically designed to support the recovery or repair of a system. It is based on WinPE and offers features such as:
- Automatic diagnosis and repair of boot problems with the Startup Repair tool
- A centralized platform for advanced recovery tools
You can even use WinRE to reinstall Windows without damaging your data, since the image-based setup Vista uses protects data during an upgrade process.
The ideal way to install WinRE is to create two disk partitions as you install Vista on your system: one for Vista and one for WinRE.
This way, WinRE will be accessible if you run into system disk problems and Vista won’t start. The WinRE partition only requires 1GB of space, since WinRE is a very small system. Both partitions must be primary and active.
To install WinRE, you have to create a system image that you can install on your system.
For this, you’ll need the Windows Automated Installation Kit, which kit gives you the tools you need to customize a WinPE image and turn it into a WinRE image.
Once the image is ready, you simply apply it to your WinRE partition. Full instructions for this operation are located in this step by step.
Once you’re done, you’ll never be caught off guard if things go wrong on your Vista PC.Although with Vista, Microsoft has made great strides in the stability of its Windows operating system, things can still go wrong.
What happens when a key driver goes missing or a system disk fails? How would you go about recovering the system and especially, all your precious data?
Problem: How do you recover a damaged Vista system?
There are basically two ways to recover a damaged Windows Vista system: the installation DVD or the Windows Recovery Environment (WinRE).
Solution #1: Use your installation DVD to boot up your system.
This is the simplest method. All you have to do is locate your installation DVD and use it to boot up your damaged system. This launches the Windows Vista installation.
Don’t worry, you’re not going to reinstall Vista. All you want is to get to the “Install now” screen.
The process begins by launching the Windows Preinstallation Environment (Windows PE), a simplified version of Windows that runs in memory only and is designed to replace DOS. Then it presents a screen which asks for three things:
- Language to install
- Time and currency format
- Keyboard or input method
Making a selection and clicking Next will bring you to the “Install now” screen. What you’re looking for is the two options in the lower left corner of the screen:
- What to know before installing Windows
- Repair your computer
Clicking “Repair your computer” will move you to another screen that lets you choose your existing system partition. When you click Next, you’ll get a series of choices for system repair. From there on, just follow the prompts.
Solution #2: Use the WinRE console to diagnose and repair the problem.
The problem with using the installation DVD is that you might not always have the disk on hand. If you want to make sure your system is always running but don’t want to depend on the installation media, then you can use WinRE.
The WinRE console is new to Windows Vista and is specifically designed to support the recovery or repair of a system. It is based on WinPE and offers features such as:
- Automatic diagnosis and repair of boot problems with the Startup Repair tool
- A centralized platform for advanced recovery tools
You can even use WinRE to reinstall Windows without damaging your data, since the image-based setup Vista uses protects data during an upgrade process.
The ideal way to install WinRE is to create two disk partitions as you install Vista on your system: one for Vista and one for WinRE.
This way, WinRE will be accessible if you run into system disk problems and Vista won’t start. The WinRE partition only requires 1GB of space, since WinRE is a very small system. Both partitions must be primary and active.
To install WinRE, you have to create a system image that you can install on your system.
For this, you’ll need the Windows Automated Installation Kit, which kit gives you the tools you need to customize a WinPE image and turn it into a WinRE image.
Once the image is ready, you simply apply it to your WinRE partition. Full instructions for this operation are located in this step by step.
Once you’re done, you’ll never be caught off guard if things go wrong on your Vista PC.
Kernel Errors
Kernel Mode is the processor access mode in which the operating system and privileged programs run. Kernel Mode code has permission to access any part of the system, and is not restricted like User Mode code. It can gain access to any part of any other process running in either User Mode or Kernel Mode.
Kernel Mode errors involve software components that reside in Kernel or System Memory. This usually means drivers, file Systems, and operating system components. When a Kernel Mode component fails, it can cause the most catastrophic of problems since it is a “trusted” component with access to all of the system resources. Kernel Mode failures are the types of failures that can generate what is known as the Stop Screen or blue screen in Windows XP.
Windows XP displays a STOP error message and halts when the Kernel detects an unrecoverable error or the CPU detects an unrecoverable hardware error. Figure 33 illustrates a stop error and some of the information it displays (more details on this type of error follows later in this lesson).
Figure 33. Kernel Mode Error (Stop Error)
Note: Program errors in processes running in User Mode should not be able to crash XP, that is, generate a Stop Error. Only device drivers and other Kernel level programs cause Stop Errors, so you can determine whether an error occurred in User Mode or Kernel mode. Kernel mode errors display Stop Errors or blue screens. User Mode errors display Dr. Watson alerts. Hardware failures are displayed as failures of the Kernel. The real problem is that the Kernel is no longer able to properly communicate with the hardware, not that the Kernel is bad.
In the case of Kernel Mode Errors, the operating system must shut down to preserve system integrity. Windows XP automatically restarts your computer by default when it encounters one of these Kernel errors.
Note: Allowing the system to continue operating (even if it is possible) after a Kernel Error will more than likely result in further corruption of data, which is why Windows shuts the system down. This process should not be altered.
You may also see error information on the blue-character screen, including a message code that provides information about the crash. This is known as the Stop Error (Figure 33).
Stop Messages
When Microsoft Windows XP Professional detects a problem from which it cannot recover, it displays a Stop message, which is a Text Mode error message that reports information about the condition. Stop messages contain specific information that can help you diagnose and possibly resolve the problem detected by the Windows Kernel. When a Stop message occurs as a result of a problem, there is certain information you will want to record in order to effectively troubleshoot the issue and cause.
Important: The information contained within a Stop message may be lost after you initiate a reboot. It is important that you record this information from the customer before restarting.
Before looking at a checklist of what information to record, let’s look at the sections which make up a Stop message.
As shown in Figure 35, a Stop message screen has four major sections, which display the following information:
œ Bugcheck information
œ Recommended user action
œ Driver information
œ Debug port and dump status information
Figure 35– Kernel Mode Error - Stop Error
Bugcheck Information
This Bugcheck information section includes the Stop error number, also known as the bugcheck code, followed by up to four developer-defined parameters (enclosed in parentheses) and the symbolic name of the error. Stop error codes contain a "0x" prefix, which indicates hexadecimal numerical format. For example, in Figure 35, the Stop error hexadecimal code is 0x000000D1 and its symbolic name is DRIVER_IRQL_NOT_LESS_OR_EQUAL.
As shown in Figure 35, the Bugcheck information section frequently includes a line that lists the specific hexadecimal memory address of the Stop error's source, along with the name of the driver or device.
Note: Under certain conditions, the Kernel cannot fully display all of the Stop message content; only the first line is visible. This occurs if the problem has caused video display services to stop functioning.
Recommended User Action
The Recommended user action section provides a list of suggestions for recovery. In some cases, restarting the computer might be sufficient because the problem is not likely to recur. But if the Stop error persists even after you restart the system, you must determine the root cause to return the system to an operable state. This might involve undoing recent changes, replacing hardware, or updating drivers to eliminate the cause of the problem.
Driver Information
The Driver information section identifies the driver associated with the Stop error. If a file is specified by name, you can use RC or Safe Mode to verify that the driver is signed or has a date stamp that coincides with other drivers. If necessary, you can replace the file manually, or use Driver Rollback.
IMPORTANT: Drivers mentioned by name on a blue screen do not necessarily indicate the problem component. In many cases a blue screen will show the name of a driver which was not at fault. As a result, be cautious of drawing firm conclusions based on such a listing unless the KB indicates a more direct connection.
Debug Port and Status Information
While beyond the scope of this discussion, the Debug port and status information section lists Common Object File Format (COM) port parameters that a Kernel debugger uses if enabled. If you have enabled memory dump file saves, this section also indicates whether one was successfully written.
Deleting the following files and/or folders will save you even more space:
C:\HIBERFIL.SYS (hidden, as big as the available RAM memory)
The hibernation file is a copy of the total RAM memory, which is used to recover the computer from sleep (also known as hibernation). Hibernation is especially used for laptop computers to save battery power, bus frequently used on desktop computers as well. Enabling and disabling the hibernation is done in the task pane of Power Options in the Control Panel. If hiberantion is not used, it is safe to disable it (if not done already). The filesize of HIBERFIL.SYS equals the total of RAM memory, so deleting the file will save a lot of space! Deleting the hibernation file is done most easily by the above mentioned tool Disk Cleanup.
TIP: When the hibernation file has been deleted, but you would like to apply the hibernation feature? The command POWERCFG /hibernate ON in the Command Prompt (start menu, All programs, Accessories) will bring back the hibernation file. Start the Command Prompt with additional administrator rights by right clicking it and to select Run as administrator!
C:\System Volume Information (hidden)
This folder is necessary for the Windows Vista System Restore (and the use of shadow copies to restore previous versions of files). By default, the system recovery is only applied to the Windows partition (in most cases C:), but it is also possible to enable it for the other partitions (by System in the Control Panel, task Advanced system settings in the taskpane, tab System Protection).By disabling System Restore for every partition/disk, the earlier created restore points (necessary for the recovery of unwanted system changes) are deleted and the folder System Volume Information will be emptied (but not deleted!). After disabling System Restore and deleting the restore points as a result, it is no longer possible to recover from any unwanted system changes! If System Restore has been turned on again, a new restore point is created by clicking the button Create.
C:\PAGEFILE.SYS (virtual memory)
The paging file (the 'virtual memory') is stored on the hard disk and is therefore slower then the RAM memory. The paging file is only used in addition to the available RAM memory in case there is not enough RAM memory to run the tasks of that moment. The paging file PAGEFILE.SYS is stored on the root of the Windows partition by default. If there is a lot of RAM memory available (2 Gb or more), and there are no programs requiring a lot of memory (like picture and video editing software), it is safe to restrict the use (or even disable) the page file. It is also possible to move the paging file to a (faster) partition. Changing the paging file settings is discussed on the page about optimizing the Windows Vista settings.
C:\Windows\SoftwareDistribution
The folder SoftwareDistribution stores the Windows/Microsoft Update information including the downloaded and already installed updates. In time this folder will become larger and larger as a result of many updates. Although this information is not that important, it is not that easy to empty this folder. Before deleting the folder SoftwareDistribution, it is necessary to stop the service Windows Update first (right click the service and select Stop, for more information visit the page about optimizing the Windows services). After a few seconds the whole folder C:\Windows\SoftwareDistribution (subfolders included) can be deleted, folowed by a restart of the service (or a restart of Windows). After the service is active again, this folder is recreated. Because the update history and settings are gone, start Windows update to make sure the update procedure still works fine. To upgrade Windows update to Microsoft Update, to receive updates of more Microsoft products, click the option Get updates for more products and accept the terms of use. Be aware that this procedure solves many Windows Update problems!
Delete the service pack undo files
When the installation of both SP1 and SP2 are finished and working properly, then the files to undo the installation of the service packs can be deleted to saves a few Gb's of disk space! Deleting these files is done with the command COMPCLN (enter this command in the area Start Search of the Start Menu) followed by the Y-key to confirm the definitive deletion of the undo-files of Service Pack 1 and Service Pack 2. Attention: COMPCLN is only available after installing Service Pack 2 replacing the cleanup tool VSP1CLN from Service Pack 1.
The most important folders
The most important folders with (possibly hidden) files to delete are on the following locations:
C:\Users\loginname\AppData\Local\Microsoft\Windows\Temporary Internet Files
C:\Users\loginname\AppData\Local\Microsoft\Windows\History
C:\Users\loginname\AppData\Local\Temp
C:\Users\loginname\AppData\Roaming\Microsoft\Internet Explorer\UserData\Low
C:\Users\loginname\AppData\Roaming\Microsoft\Office\Recent
C:\Users\loginname\AppData\Roaming\Microsoft\Windows\Cookies
C:\Users\loginname\AppData\Roaming\Microsoft\Windows\Recent
C:\Users\loginname\Searches
C:\Windows\Temp
The most important folders with (possibly hidden) files to delete are on the following locations:
C:\Users\loginname\AppData\Local\Microsoft\Windows\Temporary Internet Files
C:\Users\loginname\AppData\Local\Microsoft\Windows\History
C:\Users\loginname\AppData\Local\Temp
C:\Users\loginname\AppData\Roaming\Microsoft\Internet Explorer\UserData\Low
C:\Users\loginname\AppData\Roaming\Microsoft\Office\Recent
C:\Users\loginname\AppData\Roaming\Microsoft\Windows\Cookies
C:\Users\loginname\AppData\Roaming\Microsoft\Windows\Recent
C:\Users\loginname\Searches
C:\Windows\Temp
- The System.ini file
- The Win.ini file
- The Boot.ini file
- Programs that are set to load during the startup process (these programs are specified in the Startup folder and in the registry)
- Environment settings
- International settings
Back to the top
Method 1: Diagnostic and Selection startup modes
Diagnostic startup
Diagnostic startup enables Windows to determine the basic device drivers and software to load when you start Windows. When you use this method, the system temporarily disables Microsoft services such as Networking, Plug and Play, Event Logging, and Error Reporting. Also, you permanently delete all restore points for the System Restore utility.Note Do not use this method if you want to save your restore points for System Restore or if you must use a Microsoft service to test a problem.
To perform a diagnostic startup, follow these steps:
- Click Start, click Run, type msconfig, and then click OK.
- On the General tab, click Diagnostic Startup, and then click OK.
- Restart your computer.
Selective startup
Selective startup enables you to select the files and the settings that you want the computer to load when you restart the computer. Select from the following options:- Process System.ini File
- Process Win.ini file
- Load System Services
- Load Startup Items
- When you select the check box, the configuration file is processed when you restart the computer.
- When you clear the check box, the configuration file is not processed when you restart the computer.
- When the check box is selected, and you cannot select the check box because it appears dimmed, some items are still loading from that configuration file when you restart the computer.
- When the check box is not selected, and you cannot select the check box because it appears dimmed, the configuration file is not present on the computer.
- You cannot change the Use Original BOOT.INI option button.
To perform a selective startup, follow these steps:
- Click Start, click Run, type msconfig, and then click OK.
- On the General tab, click Selective Startup.
- Select or clear the available settings.
- Click OK.
- Restart your computer.
- Repeat steps 1 through 5 until you find the problem.
Change individual file settings
If you know the different settings in each configuration file, you can enable or disable individual settings in the file that has the tab for that file in the System Configuration utility. To prevent individual items in a configuration file from loading when you restart your computer, follow these steps:- Click Start, click Run, type msconfig, and then click OK.
- Click a tab: System.ini, Win.ini, Boot.ini, Services, or Startup.
- Select or clear the available settings.
- Click OK.
- Restart your computer.
- Repeat steps 1 through 5 until you find the problem.
System.ini and Win.ini options
The SYSTEM.INI and WIN.INI tabs in the System Configuration utility have the following options:- Check boxes enable you to enable or to disable an option. To enable an option so that it loads at startup, select the check box or select the option, and then click the Select button. To disable an option so that it does not load at startup, clear the check box or select the option, and then click the Disable button.
- Move Up and Move Down buttons enable you to move through the different options when you do not have a mouse.
- The New button enables you to create a new entry in the System.ini or in the Win.ini file. Click the button, and type your entry.
- The Edit button enables you to edit an existing line in the System.ini or in the Win.ini file. Click the button, and edit the line.
Note When you click to clear a check box for an item or a line, the Selective Startup option on the General tab is automatically selected.
Manually extract a file
What Is WINSOCK.DLL?
WINSOCK.DLL is a dynamic-link library that provides a common application programming interface (API) for developers of network applications that use the Transmission Control Protocol/Internet Protocol (TCP/IP) stack.
This means that a programmer who develops a Windows-based TCP/IP application, such as an FTP or Telenet client, can write one program that works with any TCP/IP protocol stack that provides Windows Socket Services (WINSOCK.DLL).
Other applications that depend on a Windows Socket provider include Eudora (a mail package) and Mosaic (a browser for the Internet World Wide Web).
This means that a programmer who develops a Windows-based TCP/IP application, such as an FTP or Telenet client, can write one program that works with any TCP/IP protocol stack that provides Windows Socket Services (WINSOCK.DLL).
Other applications that depend on a Windows Socket provider include Eudora (a mail package) and Mosaic (a browser for the Internet World Wide Web).
Where Can I Get WINSOCK.DLL?
WINSOCK.DLL is shipped with TCP/IP network protocol stacks that are Windows Socket compliant. A WINSOCK.DLL file developed for one implementation of TCP/IP may not necessarily work with another TCP/IP stack.
Microsoft includes a WINSOCK.DLL file with its TCP/IP stacks for Windows for Workgroups and Windows NT Workstation and Server.
Microsoft includes a WINSOCK.DLL file with its TCP/IP stacks for Windows for Workgroups and Windows NT Workstation and Server.
Renew the IP address
- Click Start, click Run, type command, and then click OK.
- Type ipconfig /renew at the command prompt, and then press ENTER.
Information that is related to the new IP address appears in the Command Prompt window. - Close the Command Prompt window.
APIPA
1. Power Cycle
2. netsh(netshell) Winsock Reset
3. Safemode with Networking
4. Force IP
5. Reset Modem/Conference with ISP
Manual steps to determine whether the Winsock2 key is corrupted for Windows XP users
- Click Start, click Run, type Command, and then click OK.
- Type netdiag /test:winsock, and then press ENTER.
The Netdiag tool will return the test results for several network components, including the Winsock. For more details about the test, use /v at the end of the netdiag command: netdiag /test:winsock /v
Method 2: Use the Msinfo32 program
Note Use this method only if you do not have a Windows XP Setup CD and you do not have Support Tools installed.
- Click Start, click Run, type Msinfo32, and then click OK.
- Expand Components, expand Network, and then click Protocol.
- You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
- MSAFD Tcpip [TCP/IP]
- MSAFD Tcpip [UDP/IP]
- RSVP UDP Service Provider
- RSVP TCP Service Provider
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.
Use a manual method to reset TCP/IP
Note This section is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, ask someone for help or contact Support. For information about how to contact Support, see the Microsoft Help and Support contact information Web site:
http://support.microsoft.com/contactus (http://support.microsoft.com/contactus)
The reset command is available in the IP context of the NetShell utility. Follow these steps to use the reset command to reset TCP/IP manually: - To open a command prompt, click Start and then click Run. Copy and paste (or type) the following command in the Open box and then press ENTER: cmd
- At the command prompt, copy and paste (or type) the following command and then press ENTER: netsh int ip reset c:\resetlog.txtNote If you do not want to specify a directory path for the log file, use the following command:netsh int ip reset resetlog.txt
- Reboot the computer.
Resolving DNS Problem
Start system in Safemode with Networking
IE Optimization
Download 3rd Party Browser(using FTP)
ipconfig /flushDNS
ipconfig /registerDNS
We can also rename the following Files incase the problem persist(resolution rate is low)
Host Files
LMHOST.sam.old
Check for invalid entry in Host file
Forcing DNS is also applicable...
Uninstall Antivirus application as last resort for resolution.
Rollback IE8 from Programmes & Features
C:\windows\IE8\Spunist
Article: 957700
http://gur.in/ , varun.notlong.com
Alternative steps for Windows Vista or for Windows Server 2008
To uninstall Internet Explorer 8, follow these steps:
- Carefully select and then copy the following command: FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-8*.mum /c "cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /norestart"
- Click Start, and then type Cmd.exe in the Start Search box.
- In the list of programs, right-click Cmd.exe, and then click Run as administrator.
Note If you are prompted for an administrator password or for confirmation, type the password, or click Continue. - Right-click inside the Administrator: Command Prompt window, and then click Paste to paste the command that you copied in step 1.
- Press ENTER to uninstall Internet Explorer 8.
- When the uninstall program is finished, restart your computer.
Alternative steps for Windows XP or for Windows Server 2003
To uninstall Internet Explorer 8, follow these steps:- Carefully select and then copy the following command: %windir%\ie8\spuninst\spuninst.exe
- Click Start, and then click Run.
- In the Open box, type Cmd.exe, and then press ENTER.
- Right-click inside the Cmd.exe window, and then click Paste to paste the command that you copied in step 1.
- Press ENTER to uninstall Internet Explorer 8.
- When the uninstall program is finished, restart your computer.
Repairing IE7
1. IE Optimization
2. Reset IE
3. Un-Register and Re-Register DLL file
4. SFC /Scannow
Regsvr32 (dllfilename) /u
Regsvr32 (dllfilename) /s
Data transfer rates
Most of us prefer faster everything for the most efficient work and play possible. Higher data transfer rates mean that data is transferred faster and work done quicker. Currently the three most popular wireless networking standards are as follows:
802.11a
802.11a is an IEEE wireless networking standard that specifies a maximum data transfer rate of 54Mbps and an operating frequency of 5GHz.
802.11b
802.11b is an IEEE wireless networking standard that specifies a maximum data transfer rate of 11Mbps and an operating frequency of 2.4GHz.
802.11g
802.11g is an IEEE wireless networking standard that specifies a maximum data transfer rate of 54Mbps and an operating frequency of 2.4GHz. And it is backward compatible with 802.11b.
Important note: In a wireless network the data transfer rate between the wireless AP/router and adapter is the lower rate of the two wireless network devices. For instance, if the wireless adapter supports a higher data transfer rate than the wireless AP/router, the transfer rate will be the lower of the two devices as the router cannot operate above the wireless standard it supports, but the adapter (or any wireless equipment) will be backwards compatible. The wireless network adapter and the wireless AP/router must both support the same transfer standard to work at the transfer rate specified.
Currently some manufacturers also provide products supporting higher data transfer rates, such as 108Mbps, 125Mbps, 140Mpbs or even higher. To ensure the high transfer rates are realized please make sure that both the wireless AP/router and adapters support it.
Security protocols
Security is a vital important consideration for wireless networks. Wireless network security protocols may be capable of safeguarding data against during transfers across a wireless network. Here are the most commonly security protocols:
WEP
WEP (Wired Equivalent Privacy) is a security mechanism for wireless networks. It aims to protect data via encryption over radio waves with point-to-point transmission. A shared key (similar to a password) is used to allow communication between the wireless adapter and the wireless AP/router.
WPA
WPA (Wi-Fi Protected Access) is built on the foundation of WEP. WPA also protects wireless data transmission via a key similar to WEP, but the added strength of WPA is in its automatic encryption key changes making it much more difficult for a hacker to invade a wireless network.
WPA2
As the successor to WPA, WPA2 (Wi-Fi Protected Access 2) is offered to users requiring the highest level of wireless security and is capable of offering a stronger encryption mechanism over WPA via AES (Advanced Encryption Standard).
The Different Types of Wireless Adapters Available
The first thing that you need to understand is the different types of wireless adapters available. The following are the main types of wireless adapters that you cna purchase:
- PCI
- USB
- PCMCIA
- Mini PCI
- Compact Flash
- Ethernet Port
Remote Desktop & Remote assistance.
Windows Remote Assistance is a feature of Windows XP and later that allows a user to temporarily control a remote Windows computer over a network or the Internet to resolve issues. As it can be inconvenient for system administrators to personally visit the affected computer, Remote Assistance allows them to diagnose and often repair problems with a computer without ever personally visiting it.
In computing, the term Remote Desktop refers to a software or an OS feature allowing graphical applications to be run remotely on a server, while being displayed locally. Remote desktop applications have varying features. Some allow attaching to an existing user's session (i.e. a running desktop) and "remote controlling" it in front of the user's eyes. Taking over a desktop remotely is a form of remote administration.
MSTSC
Microsoft Terminal Service Client.
Error Running Defender
Article ID: 931849
If this issue is not resolved after you complete step 2, follow this step:
Click Start, click Run, type regsvr32 file name, and then click OK.
Note In this step, file name is a placeholder for the following files.
Repeat this procedure for the following files:
- wuapi.dll
- wuaueng.dll
- wucltui.dll
- wups.dll
- wuweb.dll
- atl.dll
- softpub.dll
- wintrust.dll
- initpki.dll
- mssip32.dll
SubInACL.exe
Brief Description
SubInACL is a command-line tool that enables administrators to obtain security information about files, registry keys, and services, and transfer this information from user to user, from local or global group to group, and from domain to domain. For example, if a user has moved from one domain (DomainA) to another (DomainB), the administrator can replace DomainA\User with DomainB\User in the security information for the user's files. This gives the user access to the same files from the new domain.
SubInACL enables administrators to do the following:
SubInACL enables administrators to do the following:
- Display security information associated with files, registry keys, or services. This information includes owner, group, permission access control list (ACL), discretionary ACL (DACL), and system ACL (SACL).
- Change the owner of an object.
- Replace the security information for one identifier (account, group, well-known security identifier (SID)) with that of another identifier.
- Migrate security information about objects. This is useful if you have reorganized a network's domains and need to migrate the security information for files from one domain to another.
This update addresses the following issues:
- Fixed bug where subinacl.exe failed to process command line arguments
- Fixed bug where subinacl.exe failed to function correctly with cluster file shares
First backup the registry
The issue you are experiencing is caused by a permission related problem with one
of the registry keys on your computer. Please follow the steps listed below to
install the subinacl tool on your computer so we can modify the registry to provide
the appropriate permissions:
Step 1: Download and install the subinacl tool.
1. Click the link below to download the Subinacl tool:
http://www.microsoft.com/downloads/details.aspx?FamilyID=e8ba3e56-d8fe-4a91-93cf-ed6
985e3927b&DisplayLang=en
2. Once you have reached the site, please click on the Download button.
3. Select the option to Install the software (usually done by clicking on the Run
button).
4. In the setup wizard, click Next.
5. click on the "I accept" portion of the license and click on Next.
6. Click on the Install Now button and then click on Finish.
7. Close your web browser.
Step 2: Creating the Batch File
1. Click Start, Run and type notepad. You should see a blank page in the notepad
application.
2. Copy the lines listed between the dotted lines below and paste them into notepad
(Note: Do not select the dotted lines, only the lines listed between them):
------------------------
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=system=f
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=user_name=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=user_name=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=user_name=f
subinacl /subdirectories %SystemDrive% /grant=user_name=f
exit
------------------------
3. In the last five lines which contain "user_name", replace these "user_name"
entries with your windows user account name.
Note: If you are not sure about the name of your user account you can verify the
name by entering your control panel, double clicking on User Accounts and looking
at the list of User Account names available on the system (at this point there will
likely only be two - your currently used User Account and the Guest account). Once
you have verified the user account name you can use it instead of the "user_name"
entry above.
4. Once all modifications have been done, click File and Save As.
5. In the "Save As" window, go to c:\program files\windows resource kits\tools 6.
In the "File Name" field, type sub.bat.
7. In the "Save as Type" field, select "All Files".
8. Click Save and close Notepad.
Step 3: Running the Batch file
1. Click Start and then Run.
2. Type cmd and click OK.
3. In the Command Prompt window type the following lines (pressing Enter after each
line):
cd program files
cd windows resource kits
cd tools
sub
Note: Once the sub command is entered it will execute the batch file. The batch
file may take between 20 to 30 minutes to complete. During this time please do not
close the command prompt window as this will interrupt the process. Once the batch
file is done running on the system the window will close on its own.
4. When the command window has disappeared please restart the computer.
Windows update error code 80070490
Registry hives like
\SAM,
\Security,
\Software,
\System,
\Default
are stored in two locations in windows once its installed for the first time in following paths...
c:\windows\system32\config
c:\windows\restore
Clearing Upper-Lower Filter in registry
For CD Drive...
HKEY_LOCAL_MACHINE-> System-> CurrentControlSet -> Control -> Class -> {4D36E965-E325-11CE-BFC1-08002BE10318}
Floppy Drive...
HKEY_LOCAL_MACHINE-> System-> CurrentControlSet -> Control -> Class -> {4D36E969-E325-11CE-BFC1-08002BE10318}
IDE ATA/ATAPI controllers
HKEY_LOCAL_MACHINE-> System-> CurrentControlSet -> Control -> Class -> {4D36E96A-E325-11CE-BFC1-08002BE10318}
Task Manager has been disabled by your administrator
HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Policies\ System
Start -> Run and Paste this Registry Root
REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System /v DisableTaskMgr /t REG_DWORD /d 0 /f
If Regedit is Disable too then use GPEDIT.MSC Using Group Policy Editor - for Windows XP Professional
User Configuration / Administrative Templates / System / Ctrl+Alt+Delete Options / Remove Task Manager
shut down without logon in WinXP
CAUTION: Use Registry Editor at your own risk. Any change using Registry Editor may cause severe and irreparable damage and may require you to reinstall your operating system. Internet Security Systems cannot guarantee that problems caused by the use of Registry Editor can be solved.
- Open Registry Editor. (From the Windows NT Start menu, select Run, type regedt32, and click OK.)
- Go to the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon registry key.
- Change the value of the ShutdownWithoutLogon value to 0.
- Restart your system for this change to take effect.
For a Windows 2000 domain:
- Start Microsoft Management Console (MMC).
- Add Group Policy Snap-in.
- Browse Group Policy Objects.
- Select the Domain Policy of interest.
- Traverse the following path:
Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options, and Allow system to be shut down without having to log on. - Set the Allow system to be shut down without having to log on option to the desired setting, according to your administration policy.
For a stand-alone Windows 2000 computer:
- On the computer of interest, start gpedit.msc. The focus is local computer by default.
- Traverse the following path:
Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Option, and Allow system to be shut down without having to log on. - Set the Allow system to be shut down without having to log on option to the desired setting according to your administration policy.
How to Download from Command Prompt
c:\FTP FTP.mozilla.org
FTP> User name is anonymous
FTP> Password: (any email address)
FTP> CD PUB
FTP> CD FireFox
FTP> CD Releases
FTP> CD (Latest Firefox available)
FTP> CD win32
FTP> CD en-US
FTP> GET "Firefox Setup (latest version).exe"
MSINFO32
MSINFO32 displays a comprehensive view of your hardware, system components, and software environment. This article contains an overview of the available switches that can be used with the MSINFO32 command in Windows Vista and in Windows XP.
REGEDIT & REGEDIT32
Windows NT 3.x
Regedit.exe
Regedit.exe is the registration editor for 16-bit Windows. It is used to modify the Windows registration database. The database is located in the Windows directory as Reg.dat. The database contains information about 16-bit applications, and is used by File Manager for opening and printing files. It is also used by applications that support Object Linking and Embedding (OLE). Reg.dat is used and maintained by Windows on Windows (WOW) and 16-bit Windows applications. The WOW layer resides on top of theVirtual DOS Machine (VDM).Regedit.exe is a 16-bit application that is included in Windows NT for compatibility with previous 16-bit applications. Regedit provides a method for examining Reg.dat under Windows NT. You can migrate the Reg.dat database file to the Windows NT registry during the first logon to aninitial installation of Windows NT.
Regedt32.exe
Regedt32.exe is the configuration editor for Windows NT. It is used to modify the Windows NT configuration database, or the Windows NT registry. This editor allows you to view or modify the Windows NT registry.The editor provides views of windows that represent sections of the registry, named hives. Each window displays two sections. On the left side, there are folders that represent registry keys. On the right side, there are the values associated with the selected registry key. Regedt32 is a powerful tool. You must use extreme caution when you use it to change registry values. Missing or incorrect values in the registry can make the Windows NT installation unusable.Windows NT 4.0 and Windows 2000
Regedit.exe
Regedit.exe is included with Windows NT 4.0 and Windows 2000 primarily for its search capability. You can use Regedit.exe to make changes in the Windows NT 4.0 and Windows 2000 registry, but you cannot use it to view or edit all functions or data types on Windows NT 4.0 and Windows 2000.The following limitations exist in the Regedit.exe version that is included with Windows NT 4.0 and Windows 2000:
- You cannot set the security for registry keys.
- You cannot view, edit, or search the value data types REG_EXPAND_SZ and REG_MULTI_SZ. If you try to view a REG_EXPAND_SZ value, Regedit.exe displays it as a binary data type. If you try to edit either of these data types, Regedit.exe saves it as REG_SZ, and the data type no longer performs its intended function.
- You cannot save or restore keys as hive files.
Regedt32.exe
Regedt32.exe is the configuration editor for Windows NT 4.0 and Windows 2000. Regedt32.exe is used tomodify the Windows NT configuration database, or the Windows NTregistry. This editor allows you to view or modify the Windows NT registry.The editor provides views of windows that represent sections of theregistry, named hives. Each window displays two sections. On the leftside, there are folders that represent registry keys. On the right side,there are the values associated with the selected registry key. Regedt32 isa powerful tool, and you must use it with extreme caution when you changeregistry values. Missing or incorrect values in the registry can make theWindows installation unusable.Note Unlike Regedit.exe, Regedt32.exe does not support importing and exporting registration entries (.reg) files.
Windows XP and Windows Server 2003
Regedit.exe
Regedit.exe is the configuration editor for Windows XP and Windows Server 2003. Regedit.exe is used tomodify the Windows NT configuration database, or the Windows NT registry. This editor allows you to view or modify the Windows NT registry. It supports setting security on registry keys, viewing and editing REG_EXPAND_SZ and REG_MULTI_SZ, and saving and restoring hive files. On the left side, there are folders that represent registry keys. On the right side, there are the values associated with the selected registry key. Regedit is a powerful tool. You must use extreme caution when you use it to change registry values. Missing or incorrect values in the registry can make theWindows installation unusable.Regedt32.exe
In Windows XP and Windows Server 2003, Regedt32.exe is a small program that just runs Regedit.exe.
Techincal Checks
Mood: don't ask
Now Playing: Full Throttle
Topic: Paste
eonot
When you use the System Configuration utility, you can easily reset or change the configuration settings in Windows to include preferences for the following files and settings:
Note Do not use this method if you want to save your restore points for System Restore or if you must use a Microsoft service to test a problem.
To perform a diagnostic startup, follow these steps:
To perform a selective startup, follow these steps:
Note When you click to clear a check box for an item or a line, the Selective Startup option on the General tab is automatically selected.
This update addresses the following issues:
Regedit.exe is a 16-bit application that is included in Windows NT for compatibility with previous 16-bit applications. Regedit provides a method for examining Reg.dat under Windows NT. You can migrate the Reg.dat database file to the Windows NT registry during the first logon to aninitial installation of Windows NT.
The following limitations exist in the Regedit.exe version that is included with Windows NT 4.0 and Windows 2000:
Note Unlike Regedit.exe, Regedt32.exe does not support importing and exporting registration entries (.reg) files.
Mood:
don't askNow Playing: Full Throttle
Topic: Paste
eonot
Editions for personal computers
[edit] Comparison chart
Starter | Home Basic1,2 | Home Premium2 | Business1,2,3 | Enterprise1,2 | Ultimate2 | |
Availability | Emerging Markets Only | Retail & OEM Licensing | Retail & OEM Licensing | |||
Running application limit | 3 | Unlimited | Unlimited | Unlimited | Unlimited | Unlimited |
No | Yes | Yes | Yes | Yes | Yes | |
No | Partial | Yes | Yes | Yes | Yes | |
No | Yes | Yes | Yes4 | Yes | Yes | |
No | No | Yes | No | No | Yes | |
Premium games5 | No | No | Yes | Yes | No | Yes |
Joining Windows Server domains | No | No | No | Yes | Yes | Yes |
Remote Desktop Host | No | No | No | Yes | Yes | Yes |
No | No | No | Yes | Yes | Yes | |
No | No | No | No | Yes | Yes | |
No | No | No | No | Yes | Yes | |
No | No | No | No | No | Yes | |
No | No | No | Yes | Yes | Yes | |
Notes
Upgrade paths from Windows XP and between different Vista editions. Dotted lines indicate the need for a "clean install".
Users can sometimes upgrade from Windows XP to Windows Vista, or upgrade from one version of Windows Vista to another. However, not all potential upgrade combinations exist. The accompanying chart indicates the possible upgrade paths:
Note: If the user is running a 32bit version of the original operating system, the user must upgrade to a 32bit version of the new operating system or do a clean install.
| Vista Home Basic | Vista Home Premium | Vista Business | Vista Ultimate | |
|---|---|---|---|---|
| XP Home | ||||
| XP Professional | ||||
| XP Media Center | ||||
| XP Tablet PC | ||||
| XP Professional x64 | ||||
| Windows 2000 |
[edit] Disk interface families used in personal computers
| Acronym or abbreviation | Meaning | Description |
|---|---|---|
| SASI | Shugart Associates System Interface | Historical predecessor to SCSI. |
| SCSI | Small Computer System Interface | Bus oriented that handles concurrent operations. |
| SAS | Serial Attached SCSI | Improvement of SCSI, uses serial communication instead of parallel. |
| ST-506 | Seagate Technology | Historical Seagate interface. |
| ST-412 | Seagate Technology | Historical Seagate interface (minor improvement over ST-506). |
| ESDI | Enhanced Small Disk Interface | Historical; backwards compatible with ST-412/506, but faster and more integrated. |
| ATA | Advanced Technology Attachment | Successor to ST-412/506/ESDI by integrating the disk controller completely onto the device. Incapable of concurrent operations. |
| SATA | Serial ATA | Modification of ATA, uses serial communication instead of parallel. |
In order to overcome the volume size limit of FAT16, while still allowing DOS real mode code to handle the format without unnecessarily reducing the available conventional memory, Microsoft implemented a newer generation of FAT, known as FAT32, with cluster values held in a 32-bit field, of which 28 bits are used to hold the cluster number, for a maximum of approximately 268 million (228) clusters. This allows for drive sizes of up to 8 terabytes with 32KB clusters, but the boot sector uses a 32-bit field for the sector count, limiting volume size to 2 TB on a hard disk with 512 byte sectors.
The maximum possible size for a file on a FAT32 volume is 4 GB minus 1 byte (232−1 bytes). Video applications, large databases, and some other software easily exceed this limit. Larger files require another formatting type such as NTFS.
Physical Memory Limits: Windows Vista
Version | Limit in 32-bit Windows | Limit in 64-bit Windows |
Windows Vista Ultimate | 4 GB | 128 GB |
Windows Vista Enterprise | 4 GB | 128 GB |
Windows Vista Business | 4 GB | 128 GB |
Windows Vista Home Premium | 4 GB | 16 GB |
Windows Vista Home Basic | 4 GB | 8 GB |
Windows Vista Starter | 1 GB | Not applicable |
Aero- Min 1 GB of RAM
Min HDD Size-15 GB
-
- 800-megahertz (MHz) 32-bit (x86) processor or 800-MHz 64-bit (x64) processor
- 512 megabytes (MB) of system memory
Note On system configurations that use system memory as graphics memory, at least 448 MB of system memory must be available to the operating system after some memory is allocated for graphics. - DirectX 9-class graphics card
- 32 MB of graphics memory
- 20-gigabyte (GB) hard disk that has 15 GB of free hard disk space
- Internal or external DVD drive
- Internet access capability
- Audio output capability
- 1-gigahertz (GHz) 32-bit (x86) processor or 1-GHz 64-bit (x64) processor
- 1 GB of system memory
- Windows Aero-capable graphics card
Note This includes a DirectX 9-class graphics card that supports the following: - A WDDM driver
- Pixel Shader 2.0 in hardware
- 32 bits per pixel
- 128 MB of graphics memory (minimum)
- 40-GB hard disk that has 15 GB of free hard disk space (the 15GB of free space provides room for temporary file storage during the install or upgrade.)
- Internal or external DVD drive
- Internet access capability
- Audio output capability
Windows Vista Home Basic
Windows Vista Home Premium, Windows Vista Business, Windows Vista Enterprise, and Windows Vista Ultimate
Note A Windows Aero-capable graphics card is a graphics card that meets the following requirements: - Supports a Windows Display Driver Model (WDDM) driver
- Has a DirectX 9-class graphics processor unit (GPU) that supports Pixel Shader 2.0
- Supports 32 bits per pixel
- Passes the Windows Aero acceptance test in the Windows Driver Kit (WDK)
- 800-megahertz (MHz) 32-bit (x86) processor or 800-MHz 64-bit (x64) processor
- 512 megabytes (MB) of system memory
Note On system configurations that use system memory as graphics memory, at least 448 MB of system memory must be available to the operating system after some memory is allocated for graphics. - DirectX 9-class graphics card
- 32 MB of graphics memory
- 20-gigabyte (GB) hard disk that has 15 GB of free hard disk space
- Internal or external DVD drive
- Internet access capability
- Audio output capability
- 1-gigahertz (GHz) 32-bit (x86) processor or 1-GHz 64-bit (x64) processor
- 1 GB of system memory
- Windows Aero-capable graphics card
Note This includes a DirectX 9-class graphics card that supports the following:- A WDDM driver
- Pixel Shader 2.0 in hardware
- 32 bits per pixel
- 128 MB of graphics memory (minimum)
- 40-GB hard disk that has 15 GB of free hard disk space (the 15GB of free space provides room for temporary file storage during the install or upgrade.)
- Internal or external DVD drive
- Internet access capability
- Audio output capability
Windows Vista Home Premium, Windows Vista Business, Windows Vista Enterprise, and Windows Vista Ultimate
Windows Vista minimum supported system requirements
Home Basic / Home Premium / Business / Ultimate
800 MHz processor and 512 MB of system memory
20 GB hard drive with at least 15 GB of available space
Support for Super VGA graphics
Windows Vista Business, Windows Vista Enterprise, Windows Vista Home Premium, and Windows Vista Ultimate.
Aero is not included in Windows XP or earlier versions of Windows.
Check that your computer meets the minimum hardware requirements for running Aero:
• 1-gigahertz (GHz) 32-bit (x86) or 64-bit (x64) processor
• 1 gigabyte (GB) of random access memory (RAM)
• 128-megabyte (MB) graphics card
Aero also requires a DirectX 9 class graphics processor that supports a Windows Display Driver Model Driver, Pixel Shader 2.0 in hardware, and 32 bits per pixel.
For best results, you might also want to follow these graphics processor recommendations:
• 64 MB of graphics memory to support a single monitor with a resolution that is less than 1,310,720 pixels (for example, a 17–inch flat panel LCD monitor that has a 1280 × 1024 resolution)
• 128 MB of graphics memory to support a single monitor with a resolution from 1,310,720 to 2,304,000 pixels (for example, a 21.1–inch flat panel LCD monitor that has up to a 1600 × 1200 resolution)
• 256 MB of graphics memory to support a single monitor with a resolution greater than 2,304,000 pixels (for example, a 30–inch wide-screen flat panel LCD monitor that has up to a 2560 × 1600 resolution)
XP Boot Process Vs Vista Boot Process
If you see both the boot process you will find the difference starts at MBR in Windows Vista NTLDR is replace by three boot loader components. These components are;
qWindows Boot Manager (Bootmgr.exe) - It reads the boot configuration data (BCD) and display an operating system menu.
qWindows OS Loader (Winload.exe) - It is the operating system boot loader. It invokes the windows boot manager in order to load the operating system kernel (NTOS KERNEL.exe) and boot class device drivers.
qWindows Resume Loader (Winresume.exe) - Hiberfil.sys used during hibernate mode is been replaced as Winresume.exe in Vista.
qMsgina.dll used to show the custom login screen in XP is ignored in Windows Vista boot process.
Setup Media is not Recognized or not Bootable
Symptoms of this issue could include the following:
The disk is not recognized at all or shows up as empty.
You are not seeing the message “Press any key to boot from CD” when boot with media in the ROM drive.
Cause
Any of the following could contribute to this issue:
BIOS boot configuration – device boot sequence
Defective or damaged media
Invalid media – burned copy
ROM drive firmware issues
DVD media is placed in a CD-ROM drive
Other media compatibility issue
Resolution
To resolve this issue, use the following steps:
Ensure that the media you are using has a hologram “genuine media”.
Check for physical damage on the media, such as scratches or other visible defects.
If possible, try to install from a different CD/DVD-ROM drive.
If the media is accessible in the installed OS, copy the contents of the DVD to a folder on the hard drive and attempt a flat install.
For issues booting from the DVD:
Ensure that system is booting from the CD/DVD-ROM drive. To configure your computer to boot from the media refer to the documentation that is included with your computer or contact the computer manufacturer. Test with another bootable disc, if possible, such as a Windows XP retail CD, or disc that was provided by the computer manufacturer for reinstalling the operating system. Check for updates, and if available upgrade the firmware on the ROM drive.
Try to install from the CD set instead, if available.
This issue provides information on why setup may be blocked early in setup, during the “collecting information” stage.
Cause
Any of the following could contribute to this issue:
The system does not meet the minimum requirements.
Invalid product keys
SMART failure is detected on the installation drive.
Resolution
To resolve these issues, perform the relevant step from the following list:
Validate hardware: replace or upgrade hardware.
Update hardware firmware if possible.
Retype the product key.
Upgrade is Blocked
This issue discusses the symptoms, cause and resolution for situations where you are unable to perform an upgrade installation of Windows Vista.
Message: Upgrade Disabled
•When prompted for the type of installation the upgrade option is grayed out.
•The following message is displayed: “Upgrade has been disabled”.
Cause
Any of the following could contribute to this issue:
•No operating system is currently installed.
•You booted from the Windows Vista media.
•You are upgrading a legacy OS installed on a FAT32 Volume.
•The installed operating system does not support an upgrade to Windows Vista.
•You are upgrading from a legacy OS of a different locale (language).
•You launched setup from Safe Mode in the legacy OS.
•The legacy OS does not meet the software update requirements: Service Pack 2 for Windows XP.
Resolution
To resolve these issues, check for the potential causes listed above, and then perform the relevant resolution from the following list:
•Start setup within a valid legacy OS.
•Convert current file system to NTFS.
•To convert a FAT partition to NTFS, refer to the following knowledge base article:
How to Use Convert.exe to Convert a Partition to the NTFS File System (314097)
From the Article 314097:
Message: Must Remove Folder
Upgrade is grayed out.
The following message is displayed “You must remove Folder before upgrade can continue”, where folder is \Windows, \Users or \ProgramData.
Cause
The issue occurs if either of the following conditions are true:
You are upgrading from Windows XP
Your current Windows folder is not named as \Windows (for example:\WinXP) and another folder named Windows exists.
A folder named \Users exists on your Windows drive
A folder named \ProgramData exists on your Windows drive.
Resolution
To resolve this issue, check for the potential existence of the folders listed above, and then perform the following steps:
Rename the folder.
Delete the folder. When deleting the folder, use the necessary precautions to prevent data lost.
Message: Multiple Operating Systems
Upgrade is grayed out. The following message is displayed “Your upgrade partition has multiple operating systems”.
Cause
This issue occurs if all of the following conditions are true:
The Windows drive has multiple operating systems.
The BOOT.INI file has multiple entries for multiple operating systems on the same drive.
Resolution
The recommendations to resolve this issue are as follow:
Move the other operating system files to another partition, or remove them if they are unused.
Note: Placing each operating system in a separate partition is highly recommended.
Edit the BOOT.INI to modify the references to the other operating systems.
For more information on how to edit the BOOT.INI file, see the following article:
Knowledge Base: How to edit the Boot.ini file in Windows XP (289022)
Stop Errors During Setup
STOP 0x0000007B (INACCESSIBLE_BOOT_DEVICE)
The most common cause of this error is an incompatible or missing driver for the mass storage controller. Other causes also include the following:
•Bad or loose cabling on the hard disk
•Faulty hard disk
•Boot sector virus
•Bios firmware
•The master boot record is in use by another program
Resolution:
To resolve this issue use the following recommendations:
•This error is most likely a driver issue if it occurs when trying to boot into the First Boot phase of setup. If this occurs, restart and rollback the installation.
•When back in the downlevel OS, update to the latest driver available for the disk controller on the computer.
•Then attempt the upgrade again.
•If the failure continues,
Also refer to the outlined methods in the two following articles:
•Limited OEM driver support is available with F6 during Windows XP and Windows Server 2003 setup (314859)
How to troubleshoot "Stop 0x0000007B" errors in Windows XP (324103)
STOP 0x00000050, 0x0000007E, 0x0000007F, 0x0000008E, 0x0000009c, 0x0000009F, and 0x000000A3
Cause:
Any of the following could contribute to this issue:
Insufficient disk space
Faulty physical memory
Incompatible device driver
Incompatible file system driver: A driver that is installed by an antivirus, CD/DVD authoring software, or backup program.
Incompatible 3rd party service
Incompatible BIOS firmware
BIOS in the computer is not fully compliant with Advanced Configuration and Power Interface (ACPI)
Overheating and over-clocking
Try to use the default clock speed settings for your motherboard and processor at which it is designed to run. For more information about how to do this see your hardware documentation or contact the motherboard manufacturer.
Faulty hardware: RAM, CPU, motherboard, power supply
To resolve these issues:
•Use memory diagnostic tool to test physical memory.
•Evaluate your PC hardware and drivers using the Windows Vista Upgrade Advisor.
Follow the recommended actions as advised by the tool.
•Check with the hardware vendor for any updated hardware drivers or BIOS updates, or both.
•Remove unnecessary hardware if possible.
•Additional troubleshooting methods are outlined in the following articles:
1."STOP 0x0000007E" error message after you upgrade to Windows XP (330182)
2."STOP 0x0000008e" error message during Windows XP setup (315335)
3.“How to perform advanced clean-boot troubleshooting in Windows XP” (316434)
From the article 316434, steps to remove unsigned drivers:
From the article 316434, steps to remove unsigned drivers:
4.Troubleshooting a Stop 0x9F Error in Windows XP (315249)
5.Error Message: STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL (293077)
General causes of "STOP 0x0000007F" errors (137539)
Revert using WINDOWS.OLD
Boot into WinRE using the Windows Vista Media and open a Command Prompt. To do this:
qInsert the Windows Vista media in the computer’s DVD/CDROM drive, and then restart the computer.
qWhen the "Press any key to boot from CD" message is displayed on the screen, press a key.
qSelect the System Recovery Options.
qSelect the Command Prompt.
Rename the following folders:
qWindows
qProgram Files
Assuming that Windows Vista is installed on the C: volume, type the following lines, pressing ENTER after you type each line:
C:
ren Windows Windows.vista
ren “Program Files” “Program Files.Vista”
Remove the “Documents and Settings” junction. The folder should be empty if Window Vista was a clean install. Assuming that Windows Vista is installed on the C: volume, type the following line, pressing ENTER after you type the line:
As alternative method, you can rename the folder by using the ren command.
rd “Document and Settings”
Copy the content of the WINDOWS.OLD folder to the root:
Xcopy /s c:\WINDOWS.OLD\*.* c:\
Restore the boot sector for the legacy OS. Assuming that E: is the ROM drive and C: is the system partition (the partition containing the BCD and BootMGR files), type the following line, pressing ENTER after you type the line:
E:\boot\bootsect /nt52 c:
Close the Command Prompt window and click on Restart.
Create Boot Sector for XP
cd drive:\> d:\boot\bootsect /nt52 c:\
-----------------------------
Downlevel Details
The following key actions take place in this phase:
œ Validate the Windows Vista product key.
œ Create a $WINDOWS.~BT folder on the system drive. This is the Boot folder, which contains the files from which the Windows Preinstallation Environment (WinPE) will boot when the computer restarts. Setup copies the WinPE files to this folder during the Downlevel phase.
œ Create a $WINDOWS.~LS folder on the system drive. This is the “Local Source” folder, which is used to store a local copy of the setup files (install.wim and others). Setup copies the installation files during Downlevel.
œ Create a Boot folder. Copy the boot files to this folder.
œ Application and Hardware compatibility checks
œ Malware scan using the Microsoft Malware Removal Tool: C:\$WINDOWS.~BT\Sources\mrt.exe"
œ Driver package reassembly for migration:
› The driver reassembly engine scans the %SystemRoot%\inf folder
› Reassembled driver packages are copied to \$WINDOWS.~BT\Sources\Panther\ReassembledDrivers\
œ Dynamic Update (optional)
œ Modify the boot configuration:
› Switch to BOOTMGR from NTLDR.
› Set WinPE as the default boot OS for next reboot.
œ Disable system restore on the legacy O/S. As a result all restore points will be deleted from this point on.
œ The setup log files for this phase are located here:
%systemdrive%\$WINDOWS.~BT\Sources\Panther\setup*.log
Note: When you boot from the DVD to perform a clean install, some of the above steps are performed in the WinPE phase.
WinPE Details
The following key actions take place in this phase:
œ Execute setup.exe from x:\$WINDOWS.~BT\
œ For clean install only:
› Prepare the destination install disk.
› Validate product key.
Note that the option to install without entering a product key exists in WinPE phase just as it does during the Downlevel phase. The same considerations apply.
› Expand and mount the install WIM file.
› If this is a clean install the following folders, if they exist, are moved to %systemdrive%\Windows.OLD
¡ Windows
¡ Document and Settings
¡ Program Files
œ If this is an upgrade install, the following folders are moved to %systemdrive%\$Windows.~Q\ and %systemdrive%\$INPLACE.~TR\Machine\DATA
› Windows
› Document and Settings
› Program Files
œ Apply the install.win file.
œ Apply patches downloaded via Dynamic Update.
œ Migrate Security Settings
Online Configuration (FirstBoot) Details
The following key actions take place in this phase:
œ First boot into the new OS: Windows Vista.
œ Hardware Specialization: configure the HAL and minimal Plug and Play configuration. The driver are provided by the following possible sources:
› Vista inbox (included on the install media)
› Reassembled drivers from the previously installed OS
› Dynamic Update
œ For an upgrade install only:
› Create user profiles for migrated user accounts
› Migrate user and application data and settings
Setup Phases Reference Table
Use the following table as a guide to identify the setup phases. In the event of a setup failure, refer to this table to locate user files and log files needed for troubleshooting and recovery purposes.
Note: The folder paths listed below assume that the system drive (%systemdrive%) is C:, and the DVD-ROM drive is D:
Setup Phase | Shift+F10 path | Important Log Files | Possible location(s) for user files and settings |
Downlevel | D:\Sources\ | C:\WINDOWS\setup*.log C:\$WINDOWS.~BT\Sources\Panther\setup*.log C:\$WINDOWS.~BT\Sources\Panther\PreGatherPnPList.log | No changes |
REBOOT | |||
WinPE | Install from downlevel: Boot-from-DVD install: | Install from downlevel: Boot-from-DVD install: | C:\Documents and Settings C:\$INPLACE.~TR\Machine\DATA\Documents and Settings\ C:\$WINDOWS.~Q\DATA\Documents and Settings |
REBOOT | |||
Online Config (Firstboot) | C:\Windows\System32\ | C:\WINDOWS\PANTHER\setup*.log C:\WINDOWS\INF\setupapi*.log C:\$WINDOWS.~BT\Sources\Panther\PostGatherPnPList.log | C:\$INPLACE.~TR\Machine\DATA\Documents and Settings\ C:\$WINDOWS.~Q\DATA\Documents and Settings\ C:\Users\ |
REBOOT | |||
Windows Welcome (OOBE) | C:\Windows\System32\ | C:\WINDOWS\PANTHER\setup*.log C:\WINDOWS\INF\setupapi*.log C:\WINDOWS\Performance\Winsat\winsat.log | C:\$INPLACE.~TR\Machine\DATA\Documents and Settings\ C:\$WINDOWS.~Q\DATA\Documents and Settings\ C:\Users\ |
Note: If setup rolls back in the event of a fatal error during setup (upgrade), include the log location $windows.~bt\sources\rollback
Download Virtual Machine Path
EMP Code :- Y-1624
Windows Vista Boot Process
* Sys is powered on
* Cmos loads the bios and then runs POST
* Looks for the MBR on the bootable devcie
* Through the MBR the Boot sector is located and the BOOTMGR is loaded
* BOOTMGR looks for active partition
* BOOTMGR reads the BCD files from \boot directory on the active partition
* The BCD (Boot Configuration Database) contains various config parameters, ( this info was previously stored in the boot.ini)
* When windows vista is selected, BOOTMGR transfer control to the Windows Loader
(winload.exe) or winresume.exe in case the sys was in hibernated.
* Winloader loads drivers that are set to start at boot and then transfers the control to the windows Kernel
* There is not msgina.dll in windows vista( the shell draws the login screen)
POST --> MBR --> Booting --> BCD --> Kernel --> Registry Hives
Kernel Mode:- Hardware & Software/Date (Registry---Services), HAL.dll(Hardware Abstraction Layer)
User Mode:- Software Config
Hibernation files are saved in HDD as (hyberfil.sys in Xp ) and as (winresume.exe in Vista)
Windows Vista Repair
WinRE Options
*Startup Repair
* System Restore
* Windows Complete PC Restore
* Windows Memory Diagnostic Tool
* Command Prompt
There is no Recovery Console in Vista but called Command Prompt
(Automated System Recovery in XP)
rstrui.exe(Command for restore)
Backup and Restore Center to Backup Entire PC or Files and restore points
FILE Indexing
CHKDSK /F
CHKDSK /V
CHKDSK /R
CHKDSK /L:size
CHKDSK /X
CHKDSK /I
CHKDSK /C
CHKDSK /B
The /I or /C switch reduces the
REVERTING Windows.Old
C:\Ren windows Windows.vista1
C:\xcopy /s c:\windows.old\*.* c:\
cd Drive:\boot\bootsect /nt52 c:
Expand cddrive:\i386\vgaoem.fo_ c:\windows\system\
My Computer-> C ->Folder option ->uncheck show hidden file
Rename boot.bak to boot.ini
WINRE Usage
No boot situations
New hardware/SW -> Stop errror
Rollback to Previous OS
Memory Diagnostics
System Restore
Coverting FAT to NTFS
Convert C:\ /FS:NTFS
C:\(P)
Article:- 315338
Clean Installation
Copying Files
Expanding files
Installing Features
Installing Updates
Completing Installations
UPGRADING PROCESS
Copying Windows Files
Gathering Files
Expanding Files
Instaling features and Updates
Completing Upgrades
REGISTRY HIVES
Most of the supporting files for the hives are in the %SystemRoot%\System32\Config directory. These files are updated each time a user logs on. The file name extensions of the files in these directories, or in some cases a lack of an extension, indicate the type of data they contain.
The following table lists the standard hives and their supporting files.
| Registry hive | Supporting files |
|---|---|
| HKEY_CURRENT_CONFIG | System, System.alt, System.log, System.sav |
| HKEY_CURRENT_USER | Ntuser.dat, Ntuser.dat.log |
| HKEY_LOCAL_MACHINE\SAM | Sam, Sam.log, Sam.sav |
| HKEY_LOCAL_MACHINE\Security | Security, Security.log, Security.sav |
| HKEY_LOCAL_MACHINE\Software | Software, Software.log, Software.sav |
| HKEY_LOCAL_MACHINE\System | System, System.alt, System.log, System.sav |
| HKEY_USERS\.DEFAULT | Default, Default.log, Default.sav |
A list of all active hives can be found at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\hivelist
HKEY_LOCAL_MACHINE\HARDWARE has no corresponding file because it is a volatile key that is created (and built) by the kernel at system start.
FILE INDEXING
What is the index?
Supported File Replacement Mechanisms
Replacement of protected system files is supported using the following mechanisms:
| • | Windows Service Pack installation (UPDATE.EXE) |
| • | Hotfix distributions installed using HOTFIX.EXE |
| • | Operating system upgrade (WINNT32.EXE) |
SFCDllCacheDir
Value: <location of dllcache directory>
Default: %Systemroot%\system32\dllcache
Specifies the location of the dllcache directory. This path must be a local path.
Example: SFCDllCacheDir = "C:\Winnt\System32\dllcache"
Disabling Windows File Protection
You may disable WFP by setting the value SFCDisable (REG_DWORD) in HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows NT\ CurrentVersion\ Winlogon. By default, SFCDisable is set to 0, which means WFP is active. Setting SFCDisable to 1 will disable WFP. Setting SFCDisable to 2 will disable WFP for the next system restart only (without a prompt to re-enable).
Important: You must have a kernel debugger attached to the system via null modem cable (for example:I386kd.exe or Windbg.exe) to use SFCDisable = 1 or SFCDisable = 2.
After WFP is disabled using the SFCDisable = 1 setting, the following message will appear after logon:
Warning! Windows File Protection is not active on this system. Would you like to enable Windows File Protection now? This will enable Windows File Protection until the next system restart. <Yes> <No>.
Clicking Yes will reactivate WFP until the next system restart. This message will appear at every successful logon until SFCDisable is set to 0.
NOTE: The above message will only be presented to Administrators.
Additional Registry Settings
All registry settings for WFP/System File Checker are located in HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ Windows NT\ CurrentVersion\ Winlogon. By default, only Administrators and System will be able to modify these settings.
SFCDisable (REG_DWORD)
0 = enabled (default).
1 = disabled, prompt at boot to re-enable (debugger required).
2 = disabled at next boot only, no prompt to re-enable (debugger required).
SFCScan (REG_DWORD)
0 = do not scan protected files at boot (default).
1 = scan protected files at every boot.
2 = scan protected files once.
SFCQuota (REG_DWORD)
n = size (in megabytes) of dllcache quota.
FFFFFFFF = cache-protected system files on the local hard drive.
SFCShowProgress (REG_DWORD)
0 = System File Checker progress meter is not displayed.
1 = System File Checker progress meter is displayed (default).
SFCDllCacheDir (REG_EXPAND_SZ)
Path = local location of dllcache directory (default is %Systemroot%\system32\dllcache).
Registry Hives
A hive is a logical group of keys, subkeys, and values in the registry that has a set of supporting files containing backups of its data.
Each time a new user logs on to a computer, a new hive is created for that user with a separate file for the user profile. This is called the user profile hive. A user's hive contains specific registry information pertaining to the user's application settings, desktop, environment, network connections, and printers. User profile hives are located under the HKEY_USERS key.
Registry files have the following two formats: standard and latest. The standard format is the only format supported by Windows 2000. It is also supported by later versions of Windows for backward compatibility. The latest format is supported starting with Windows XP. On versions of Windows that support the latest format, the following hives still use the standard format: HKEY_CURRENT_USER, HKEY_LOCAL_MACHINE\SAM, HKEY_LOCAL_MACHINE\Security, and HKEY_USERS\.DEFAULT; all other hives use the latest format.
Most of the supporting files for the hives are in the %SystemRoot%\System32\Config directory. These files are updated each time a user logs on. The file name extensions of the files in these directories, or in some cases a lack of an extension, indicate the type of data they contain. The following table lists these extensions along with a description of the data in the file.
| Extension | Description |
|---|---|
none | A complete copy of the hive data. |
.alt | A backup copy of the critical HKEY_LOCAL_MACHINE\System hive. Only the System key has an .alt file. |
.log | A transaction log of changes to the keys and value entries in the hive. |
.sav | Copies of the hive files as they looked at the end of the text-mode stage in Setup. Setup has two stages: text mode and graphics mode. The hive is copied to a .sav file after the text-mode stage of setup to protect it from errors that might occur if the graphics-mode stage of setup fails. If setup fails during the graphics-mode stage, only the graphics-mode stage is repeated when the computer is restarted; the .sav file is used to restore the hive data |
The following table lists the standard hives and their supporting files.
| Registry hive | Supporting files |
|---|---|
| HKEY_CURRENT_CONFIG | System, System.alt, System.log, System.sav |
| HKEY_CURRENT_USER | Ntuser.dat, Ntuser.dat.log |
| HKEY_LOCAL_MACHINE\SAM | Sam, Sam.log, Sam.sav |
| HKEY_LOCAL_MACHINE\Security | Security, Security.log, Security.sav |
| HKEY_LOCAL_MACHINE\Software | Software, Software.log, Software.sav |
| HKEY_LOCAL_MACHINE\System | System, System.alt, System.log, System.sav |
| HKEY_USERS\.DEFAULT | Default, Default.log, Default.sav |
Backup and Restore
Internet Options
PC Tuneup
Delete Cookies
Clear SSL
Disable any addons not required
Restore All Setings
Remove third Party extensions
Clear Temp Files...
Temp
%temp%
Prefetch
IE Optimization
Disk Cleaner(Cleanmgr)
Check for Virtual Memory(Increan Virtual memory)
Clear Startup items
Unistall any expired Softwares
Check CPU Usage(If more than 10% Run Spyware/Malware tools)
Clear event log files(Event Viewer)
Setting Default Programs
Control Panel ->Set Program Access and Computer Defaults ->Choose The Program to Run as Default Program
Control Panel ->Set Your Defaults Program
Control Panel ->Associate a File Type or Protocol with a Program
Control Panel -> Change AutoPlay Settings
VEN_ Vendor Id
DEV_ Device Id
Using memory in your storage device to speed up your computer
Some universal serial bus (USB) storage devices contain both slow and fast flash memory, and Windows can only use fast flash memory to speed up your computer. So if your device contains both slow and fast memory, keep in mind that you can only use the fast memory portion for this purpose.
The recommended amount of memory to use for Windows ReadyBoost acceleration is one to three times the amount of random access memory (RAM) installed in your computer. For instance, if your computer has 512 megabytes (MB) of RAM and you plug in a 4 gigabyte (GB) USB flash drive, setting aside from 512 MB to 1.5 GB of that drive will offer the best performance boost. The minimum size for any USB flash drive to work with Windows ReadyBoost is 256 MB.
Although with Vista, Microsoft has made great strides in the stability of its Windows operating system, things can still go wrong.
What happens when a key driver goes missing or a system disk fails? How would you go about recovering the system and especially, all your precious data?
Problem: How do you recover a damaged Vista system?
There are basically two ways to recover a damaged Windows Vista system: the installation DVD or the Windows Recovery Environment (WinRE).
Solution #1: Use your installation DVD to boot up your system.
This is the simplest method. All you have to do is locate your installation DVD and use it to boot up your damaged system. This launches the Windows Vista installation.
Don’t worry, you’re not going to reinstall Vista. All you want is to get to the “Install now” screen.
The process begins by launching the Windows Preinstallation Environment (Windows PE), a simplified version of Windows that runs in memory only and is designed to replace DOS. Then it presents a screen which asks for three things:
- Language to install
- Time and currency format
- Keyboard or input method
Making a selection and clicking Next will bring you to the “Install now” screen. What you’re looking for is the two options in the lower left corner of the screen:
- What to know before installing Windows
- Repair your computer
Clicking “Repair your computer” will move you to another screen that lets you choose your existing system partition. When you click Next, you’ll get a series of choices for system repair. From there on, just follow the prompts.
Solution #2: Use the WinRE console to diagnose and repair the problem.
The problem with using the installation DVD is that you might not always have the disk on hand. If you want to make sure your system is always running but don’t want to depend on the installation media, then you can use WinRE.
The WinRE console is new to Windows Vista and is specifically designed to support the recovery or repair of a system. It is based on WinPE and offers features such as:
- Automatic diagnosis and repair of boot problems with the Startup Repair tool
- A centralized platform for advanced recovery tools
You can even use WinRE to reinstall Windows without damaging your data, since the image-based setup Vista uses protects data during an upgrade process.
The ideal way to install WinRE is to create two disk partitions as you install Vista on your system: one for Vista and one for WinRE.
This way, WinRE will be accessible if you run into system disk problems and Vista won’t start. The WinRE partition only requires 1GB of space, since WinRE is a very small system. Both partitions must be primary and active.
To install WinRE, you have to create a system image that you can install on your system.
For this, you’ll need the Windows Automated Installation Kit, which kit gives you the tools you need to customize a WinPE image and turn it into a WinRE image.
Once the image is ready, you simply apply it to your WinRE partition. Full instructions for this operation are located in this step by step.
Once you’re done, you’ll never be caught off guard if things go wrong on your Vista PC.Although with Vista, Microsoft has made great strides in the stability of its Windows operating system, things can still go wrong.
What happens when a key driver goes missing or a system disk fails? How would you go about recovering the system and especially, all your precious data?
Problem: How do you recover a damaged Vista system?
There are basically two ways to recover a damaged Windows Vista system: the installation DVD or the Windows Recovery Environment (WinRE).
Solution #1: Use your installation DVD to boot up your system.
This is the simplest method. All you have to do is locate your installation DVD and use it to boot up your damaged system. This launches the Windows Vista installation.
Don’t worry, you’re not going to reinstall Vista. All you want is to get to the “Install now” screen.
The process begins by launching the Windows Preinstallation Environment (Windows PE), a simplified version of Windows that runs in memory only and is designed to replace DOS. Then it presents a screen which asks for three things:
- Language to install
- Time and currency format
- Keyboard or input method
Making a selection and clicking Next will bring you to the “Install now” screen. What you’re looking for is the two options in the lower left corner of the screen:
- What to know before installing Windows
- Repair your computer
Clicking “Repair your computer” will move you to another screen that lets you choose your existing system partition. When you click Next, you’ll get a series of choices for system repair. From there on, just follow the prompts.
Solution #2: Use the WinRE console to diagnose and repair the problem.
The problem with using the installation DVD is that you might not always have the disk on hand. If you want to make sure your system is always running but don’t want to depend on the installation media, then you can use WinRE.
The WinRE console is new to Windows Vista and is specifically designed to support the recovery or repair of a system. It is based on WinPE and offers features such as:
- Automatic diagnosis and repair of boot problems with the Startup Repair tool
- A centralized platform for advanced recovery tools
You can even use WinRE to reinstall Windows without damaging your data, since the image-based setup Vista uses protects data during an upgrade process.
The ideal way to install WinRE is to create two disk partitions as you install Vista on your system: one for Vista and one for WinRE.
This way, WinRE will be accessible if you run into system disk problems and Vista won’t start. The WinRE partition only requires 1GB of space, since WinRE is a very small system. Both partitions must be primary and active.
To install WinRE, you have to create a system image that you can install on your system.
For this, you’ll need the Windows Automated Installation Kit, which kit gives you the tools you need to customize a WinPE image and turn it into a WinRE image.
Once the image is ready, you simply apply it to your WinRE partition. Full instructions for this operation are located in this step by step.
Once you’re done, you’ll never be caught off guard if things go wrong on your Vista PC.
Kernel Errors
Kernel Mode is the processor access mode in which the operating system and privileged programs run. Kernel Mode code has permission to access any part of the system, and is not restricted like User Mode code. It can gain access to any part of any other process running in either User Mode or Kernel Mode.
Kernel Mode errors involve software components that reside in Kernel or System Memory. This usually means drivers, file Systems, and operating system components. When a Kernel Mode component fails, it can cause the most catastrophic of problems since it is a “trusted” component with access to all of the system resources. Kernel Mode failures are the types of failures that can generate what is known as the Stop Screen or blue screen in Windows XP.
Windows XP displays a STOP error message and halts when the Kernel detects an unrecoverable error or the CPU detects an unrecoverable hardware error. Figure 33 illustrates a stop error and some of the information it displays (more details on this type of error follows later in this lesson).
Figure 33. Kernel Mode Error (Stop Error)
Note: Program errors in processes running in User Mode should not be able to crash XP, that is, generate a Stop Error. Only device drivers and other Kernel level programs cause Stop Errors, so you can determine whether an error occurred in User Mode or Kernel mode. Kernel mode errors display Stop Errors or blue screens. User Mode errors display Dr. Watson alerts. Hardware failures are displayed as failures of the Kernel. The real problem is that the Kernel is no longer able to properly communicate with the hardware, not that the Kernel is bad.
In the case of Kernel Mode Errors, the operating system must shut down to preserve system integrity. Windows XP automatically restarts your computer by default when it encounters one of these Kernel errors.
Note: Allowing the system to continue operating (even if it is possible) after a Kernel Error will more than likely result in further corruption of data, which is why Windows shuts the system down. This process should not be altered.
You may also see error information on the blue-character screen, including a message code that provides information about the crash. This is known as the Stop Error (Figure 33).
Stop Messages
When Microsoft Windows XP Professional detects a problem from which it cannot recover, it displays a Stop message, which is a Text Mode error message that reports information about the condition. Stop messages contain specific information that can help you diagnose and possibly resolve the problem detected by the Windows Kernel. When a Stop message occurs as a result of a problem, there is certain information you will want to record in order to effectively troubleshoot the issue and cause.
Important: The information contained within a Stop message may be lost after you initiate a reboot. It is important that you record this information from the customer before restarting.
Before looking at a checklist of what information to record, let’s look at the sections which make up a Stop message.
As shown in Figure 35, a Stop message screen has four major sections, which display the following information:
œ Bugcheck information
œ Recommended user action
œ Driver information
œ Debug port and dump status information
Figure 35– Kernel Mode Error - Stop Error
Bugcheck Information
This Bugcheck information section includes the Stop error number, also known as the bugcheck code, followed by up to four developer-defined parameters (enclosed in parentheses) and the symbolic name of the error. Stop error codes contain a "0x" prefix, which indicates hexadecimal numerical format. For example, in Figure 35, the Stop error hexadecimal code is 0x000000D1 and its symbolic name is DRIVER_IRQL_NOT_LESS_OR_EQUAL.
As shown in Figure 35, the Bugcheck information section frequently includes a line that lists the specific hexadecimal memory address of the Stop error's source, along with the name of the driver or device.
Note: Under certain conditions, the Kernel cannot fully display all of the Stop message content; only the first line is visible. This occurs if the problem has caused video display services to stop functioning.
Recommended User Action
The Recommended user action section provides a list of suggestions for recovery. In some cases, restarting the computer might be sufficient because the problem is not likely to recur. But if the Stop error persists even after you restart the system, you must determine the root cause to return the system to an operable state. This might involve undoing recent changes, replacing hardware, or updating drivers to eliminate the cause of the problem.
Driver Information
The Driver information section identifies the driver associated with the Stop error. If a file is specified by name, you can use RC or Safe Mode to verify that the driver is signed or has a date stamp that coincides with other drivers. If necessary, you can replace the file manually, or use Driver Rollback.
IMPORTANT: Drivers mentioned by name on a blue screen do not necessarily indicate the problem component. In many cases a blue screen will show the name of a driver which was not at fault. As a result, be cautious of drawing firm conclusions based on such a listing unless the KB indicates a more direct connection.
Debug Port and Status Information
While beyond the scope of this discussion, the Debug port and status information section lists Common Object File Format (COM) port parameters that a Kernel debugger uses if enabled. If you have enabled memory dump file saves, this section also indicates whether one was successfully written.
Deleting the following files and/or folders will save you even more space:
C:\HIBERFIL.SYS (hidden, as big as the available RAM memory)
The hibernation file is a copy of the total RAM memory, which is used to recover the computer from sleep (also known as hibernation). Hibernation is especially used for laptop computers to save battery power, bus frequently used on desktop computers as well. Enabling and disabling the hibernation is done in the task pane of Power Options in the Control Panel. If hiberantion is not used, it is safe to disable it (if not done already). The filesize of HIBERFIL.SYS equals the total of RAM memory, so deleting the file will save a lot of space! Deleting the hibernation file is done most easily by the above mentioned tool Disk Cleanup.
TIP: When the hibernation file has been deleted, but you would like to apply the hibernation feature? The command POWERCFG /hibernate ON in the Command Prompt (start menu, All programs, Accessories) will bring back the hibernation file. Start the Command Prompt with additional administrator rights by right clicking it and to select Run as administrator!
C:\System Volume Information (hidden)
This folder is necessary for the Windows Vista System Restore (and the use of shadow copies to restore previous versions of files). By default, the system recovery is only applied to the Windows partition (in most cases C:), but it is also possible to enable it for the other partitions (by System in the Control Panel, task Advanced system settings in the taskpane, tab System Protection).By disabling System Restore for every partition/disk, the earlier created restore points (necessary for the recovery of unwanted system changes) are deleted and the folder System Volume Information will be emptied (but not deleted!). After disabling System Restore and deleting the restore points as a result, it is no longer possible to recover from any unwanted system changes! If System Restore has been turned on again, a new restore point is created by clicking the button Create.
C:\PAGEFILE.SYS (virtual memory)
The paging file (the 'virtual memory') is stored on the hard disk and is therefore slower then the RAM memory. The paging file is only used in addition to the available RAM memory in case there is not enough RAM memory to run the tasks of that moment. The paging file PAGEFILE.SYS is stored on the root of the Windows partition by default. If there is a lot of RAM memory available (2 Gb or more), and there are no programs requiring a lot of memory (like picture and video editing software), it is safe to restrict the use (or even disable) the page file. It is also possible to move the paging file to a (faster) partition. Changing the paging file settings is discussed on the page about optimizing the Windows Vista settings.
C:\Windows\SoftwareDistribution
The folder SoftwareDistribution stores the Windows/Microsoft Update information including the downloaded and already installed updates. In time this folder will become larger and larger as a result of many updates. Although this information is not that important, it is not that easy to empty this folder. Before deleting the folder SoftwareDistribution, it is necessary to stop the service Windows Update first (right click the service and select Stop, for more information visit the page about optimizing the Windows services). After a few seconds the whole folder C:\Windows\SoftwareDistribution (subfolders included) can be deleted, folowed by a restart of the service (or a restart of Windows). After the service is active again, this folder is recreated. Because the update history and settings are gone, start Windows update to make sure the update procedure still works fine. To upgrade Windows update to Microsoft Update, to receive updates of more Microsoft products, click the option Get updates for more products and accept the terms of use. Be aware that this procedure solves many Windows Update problems!
Delete the service pack undo files
When the installation of both SP1 and SP2 are finished and working properly, then the files to undo the installation of the service packs can be deleted to saves a few Gb's of disk space! Deleting these files is done with the command COMPCLN (enter this command in the area Start Search of the Start Menu) followed by the Y-key to confirm the definitive deletion of the undo-files of Service Pack 1 and Service Pack 2. Attention: COMPCLN is only available after installing Service Pack 2 replacing the cleanup tool VSP1CLN from Service Pack 1.
The most important folders
The most important folders with (possibly hidden) files to delete are on the following locations:
C:\Users\loginname\AppData\Local\Microsoft\Windows\Temporary Internet Files
C:\Users\loginname\AppData\Local\Microsoft\Windows\History
C:\Users\loginname\AppData\Local\Temp
C:\Users\loginname\AppData\Roaming\Microsoft\Internet Explorer\UserData\Low
C:\Users\loginname\AppData\Roaming\Microsoft\Office\Recent
C:\Users\loginname\AppData\Roaming\Microsoft\Windows\Cookies
C:\Users\loginname\AppData\Roaming\Microsoft\Windows\Recent
C:\Users\loginname\Searches
C:\Windows\Temp
The most important folders with (possibly hidden) files to delete are on the following locations:
C:\Users\loginname\AppData\Local\Microsoft\Windows\Temporary Internet Files
C:\Users\loginname\AppData\Local\Microsoft\Windows\History
C:\Users\loginname\AppData\Local\Temp
C:\Users\loginname\AppData\Roaming\Microsoft\Internet Explorer\UserData\Low
C:\Users\loginname\AppData\Roaming\Microsoft\Office\Recent
C:\Users\loginname\AppData\Roaming\Microsoft\Windows\Cookies
C:\Users\loginname\AppData\Roaming\Microsoft\Windows\Recent
C:\Users\loginname\Searches
C:\Windows\Temp
- The System.ini file
- The Win.ini file
- The Boot.ini file
- Programs that are set to load during the startup process (these programs are specified in the Startup folder and in the registry)
- Environment settings
- International settings
Method 1: Diagnostic and Selection startup modes
Diagnostic startup
Diagnostic startup enables Windows to determine the basic device drivers and software to load when you start Windows. When you use this method, the system temporarily disables Microsoft services such as Networking, Plug and Play, Event Logging, and Error Reporting. Also, you permanently delete all restore points for the System Restore utility.Note Do not use this method if you want to save your restore points for System Restore or if you must use a Microsoft service to test a problem.
To perform a diagnostic startup, follow these steps:
- Click Start, click Run, type msconfig, and then click OK.
- On the General tab, click Diagnostic Startup, and then click OK.
- Restart your computer.
Selective startup
Selective startup enables you to select the files and the settings that you want the computer to load when you restart the computer. Select from the following options:- Process System.ini File
- Process Win.ini file
- Load System Services
- Load Startup Items
- When you select the check box, the configuration file is processed when you restart the computer.
- When you clear the check box, the configuration file is not processed when you restart the computer.
- When the check box is selected, and you cannot select the check box because it appears dimmed, some items are still loading from that configuration file when you restart the computer.
- When the check box is not selected, and you cannot select the check box because it appears dimmed, the configuration file is not present on the computer.
- You cannot change the Use Original BOOT.INI option button.
To perform a selective startup, follow these steps:
- Click Start, click Run, type msconfig, and then click OK.
- On the General tab, click Selective Startup.
- Select or clear the available settings.
- Click OK.
- Restart your computer.
- Repeat steps 1 through 5 until you find the problem.
Change individual file settings
If you know the different settings in each configuration file, you can enable or disable individual settings in the file that has the tab for that file in the System Configuration utility. To prevent individual items in a configuration file from loading when you restart your computer, follow these steps:- Click Start, click Run, type msconfig, and then click OK.
- Click a tab: System.ini, Win.ini, Boot.ini, Services, or Startup.
- Select or clear the available settings.
- Click OK.
- Restart your computer.
- Repeat steps 1 through 5 until you find the problem.
System.ini and Win.ini options
The SYSTEM.INI and WIN.INI tabs in the System Configuration utility have the following options:- Check boxes enable you to enable or to disable an option. To enable an option so that it loads at startup, select the check box or select the option, and then click the Select button. To disable an option so that it does not load at startup, clear the check box or select the option, and then click the Disable button.
- Move Up and Move Down buttons enable you to move through the different options when you do not have a mouse.
- The New button enables you to create a new entry in the System.ini or in the Win.ini file. Click the button, and type your entry.
- The Edit button enables you to edit an existing line in the System.ini or in the Win.ini file. Click the button, and edit the line.
Note When you click to clear a check box for an item or a line, the Selective Startup option on the General tab is automatically selected.
Manually extract a file
What Is WINSOCK.DLL?
WINSOCK.DLL is a dynamic-link library that provides a common application programming interface (API) for developers of network applications that use the Transmission Control Protocol/Internet Protocol (TCP/IP) stack.
This means that a programmer who develops a Windows-based TCP/IP application, such as an FTP or Telenet client, can write one program that works with any TCP/IP protocol stack that provides Windows Socket Services (WINSOCK.DLL).
Other applications that depend on a Windows Socket provider include Eudora (a mail package) and Mosaic (a browser for the Internet World Wide Web).
This means that a programmer who develops a Windows-based TCP/IP application, such as an FTP or Telenet client, can write one program that works with any TCP/IP protocol stack that provides Windows Socket Services (WINSOCK.DLL).
Other applications that depend on a Windows Socket provider include Eudora (a mail package) and Mosaic (a browser for the Internet World Wide Web).
Where Can I Get WINSOCK.DLL?
WINSOCK.DLL is shipped with TCP/IP network protocol stacks that are Windows Socket compliant. A WINSOCK.DLL file developed for one implementation of TCP/IP may not necessarily work with another TCP/IP stack.
Microsoft includes a WINSOCK.DLL file with its TCP/IP stacks for Windows for Workgroups and Windows NT Workstation and Server.
Microsoft includes a WINSOCK.DLL file with its TCP/IP stacks for Windows for Workgroups and Windows NT Workstation and Server.
Renew the IP address
- Click Start, click Run, type command, and then click OK.
- Type ipconfig /renew at the command prompt, and then press ENTER.
Information that is related to the new IP address appears in the Command Prompt window. - Close the Command Prompt window.
APIPA
1. Power Cycle
2. netsh(netshell) Winsock Reset
3. Safemode with Networking
4. Force IP
5. Reset Modem/Conference with ISP
Manual steps to determine whether the Winsock2 key is corrupted for Windows XP users
- Click Start, click Run, type Command, and then click OK.
- Type netdiag /test:winsock, and then press ENTER.
The Netdiag tool will return the test results for several network components, including the Winsock. For more details about the test, use /v at the end of the netdiag command: netdiag /test:winsock /v
Method 2: Use the Msinfo32 program
Note Use this method only if you do not have a Windows XP Setup CD and you do not have Support Tools installed.
- Click Start, click Run, type Msinfo32, and then click OK.
- Expand Components, expand Network, and then click Protocol.
- You will have ten sections under Protocol. The section headings will include the following names if the Winsock2 key is undamaged:
- MSAFD Tcpip [TCP/IP]
- MSAFD Tcpip [UDP/IP]
- RSVP UDP Service Provider
- RSVP TCP Service Provider
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
- MSAFD NetBIOS [\Device\NetBT_Tcpip...
If you have a third-party add-on installed, the name of the add-on will replace the letters "MSAFD" in the list.
Use a manual method to reset TCP/IP
Note This section is intended for advanced computer users. If you are not comfortable with advanced troubleshooting, ask someone for help or contact Support. For information about how to contact Support, see the Microsoft Help and Support contact information Web site:
http://support.microsoft.com/contactus (http://support.microsoft.com/contactus)
The reset command is available in the IP context of the NetShell utility. Follow these steps to use the reset command to reset TCP/IP manually: - To open a command prompt, click Start and then click Run. Copy and paste (or type) the following command in the Open box and then press ENTER: cmd
- At the command prompt, copy and paste (or type) the following command and then press ENTER: netsh int ip reset c:\resetlog.txtNote If you do not want to specify a directory path for the log file, use the following command:netsh int ip reset resetlog.txt
- Reboot the computer.
Resolving DNS Problem
Start system in Safemode with Networking
IE Optimization
Download 3rd Party Browser(using FTP)
ipconfig /flushDNS
ipconfig /registerDNS
We can also rename the following Files incase the problem persist(resolution rate is low)
Host Files
LMHOST.sam.old
Check for invalid entry in Host file
Forcing DNS is also applicable...
Uninstall Antivirus application as last resort for resolution.
Rollback IE8 from Programmes & Features
C:\windows\IE8\Spunist
Article: 957700
http://gur.in/ , varun.notlong.com
Alternative steps for Windows Vista or for Windows Server 2008
To uninstall Internet Explorer 8, follow these steps:
- Carefully select and then copy the following command: FORFILES /P %WINDIR%\servicing\Packages /M Microsoft-Windows-InternetExplorer-8*.mum /c "cmd /c echo Uninstalling package @fname && start /w pkgmgr /up:@fname /norestart"
- Click Start, and then type Cmd.exe in the Start Search box.
- In the list of programs, right-click Cmd.exe, and then click Run as administrator.
Note If you are prompted for an administrator password or for confirmation, type the password, or click Continue. - Right-click inside the Administrator: Command Prompt window, and then click Paste to paste the command that you copied in step 1.
- Press ENTER to uninstall Internet Explorer 8.
- When the uninstall program is finished, restart your computer.
Alternative steps for Windows XP or for Windows Server 2003
To uninstall Internet Explorer 8, follow these steps:- Carefully select and then copy the following command: %windir%\ie8\spuninst\spuninst.exe
- Click Start, and then click Run.
- In the Open box, type Cmd.exe, and then press ENTER.
- Right-click inside the Cmd.exe window, and then click Paste to paste the command that you copied in step 1.
- Press ENTER to uninstall Internet Explorer 8.
- When the uninstall program is finished, restart your computer.
Repairing IE7
1. IE Optimization
2. Reset IE
3. Un-Register and Re-Register DLL file
4. SFC /Scannow
Regsvr32 (dllfilename) /u
Regsvr32 (dllfilename) /s
Data transfer rates
Most of us prefer faster everything for the most efficient work and play possible. Higher data transfer rates mean that data is transferred faster and work done quicker. Currently the three most popular wireless networking standards are as follows:
802.11a
802.11a is an IEEE wireless networking standard that specifies a maximum data transfer rate of 54Mbps and an operating frequency of 5GHz.
802.11b
802.11b is an IEEE wireless networking standard that specifies a maximum data transfer rate of 11Mbps and an operating frequency of 2.4GHz.
802.11g
802.11g is an IEEE wireless networking standard that specifies a maximum data transfer rate of 54Mbps and an operating frequency of 2.4GHz. And it is backward compatible with 802.11b.
Important note: In a wireless network the data transfer rate between the wireless AP/router and adapter is the lower rate of the two wireless network devices. For instance, if the wireless adapter supports a higher data transfer rate than the wireless AP/router, the transfer rate will be the lower of the two devices as the router cannot operate above the wireless standard it supports, but the adapter (or any wireless equipment) will be backwards compatible. The wireless network adapter and the wireless AP/router must both support the same transfer standard to work at the transfer rate specified.
Currently some manufacturers also provide products supporting higher data transfer rates, such as 108Mbps, 125Mbps, 140Mpbs or even higher. To ensure the high transfer rates are realized please make sure that both the wireless AP/router and adapters support it.
Security protocols
Security is a vital important consideration for wireless networks. Wireless network security protocols may be capable of safeguarding data against during transfers across a wireless network. Here are the most commonly security protocols:
WEP
WEP (Wired Equivalent Privacy) is a security mechanism for wireless networks. It aims to protect data via encryption over radio waves with point-to-point transmission. A shared key (similar to a password) is used to allow communication between the wireless adapter and the wireless AP/router.
WPA
WPA (Wi-Fi Protected Access) is built on the foundation of WEP. WPA also protects wireless data transmission via a key similar to WEP, but the added strength of WPA is in its automatic encryption key changes making it much more difficult for a hacker to invade a wireless network.
WPA2
As the successor to WPA, WPA2 (Wi-Fi Protected Access 2) is offered to users requiring the highest level of wireless security and is capable of offering a stronger encryption mechanism over WPA via AES (Advanced Encryption Standard).
The Different Types of Wireless Adapters Available
The first thing that you need to understand is the different types of wireless adapters available. The following are the main types of wireless adapters that you cna purchase:
- PCI
- USB
- PCMCIA
- Mini PCI
- Compact Flash
- Ethernet Port
Remote Desktop & Remote assistance.
Windows Remote Assistance is a feature of Windows XP and later that allows a user to temporarily control a remote Windows computer over a network or the Internet to resolve issues. As it can be inconvenient for system administrators to personally visit the affected computer, Remote Assistance allows them to diagnose and often repair problems with a computer without ever personally visiting it.
In computing, the term Remote Desktop refers to a software or an OS feature allowing graphical applications to be run remotely on a server, while being displayed locally. Remote desktop applications have varying features. Some allow attaching to an existing user's session (i.e. a running desktop) and "remote controlling" it in front of the user's eyes. Taking over a desktop remotely is a form of remote administration.
MSTSC
Microsoft Terminal Service Client.
Error Running Defender
Article ID: 931849
If this issue is not resolved after you complete step 2, follow this step:
Click Start, click Run, type regsvr32 file name, and then click OK.
Note In this step, file name is a placeholder for the following files.
Repeat this procedure for the following files:
- wuapi.dll
- wuaueng.dll
- wucltui.dll
- wups.dll
- wuweb.dll
- atl.dll
- softpub.dll
- wintrust.dll
- initpki.dll
- mssip32.dll
SubInACL.exe
Brief Description
SubInACL is a command-line tool that enables administrators to obtain security information about files, registry keys, and services, and transfer this information from user to user, from local or global group to group, and from domain to domain. For example, if a user has moved from one domain (DomainA) to another (DomainB), the administrator can replace DomainA\User with DomainB\User in the security information for the user's files. This gives the user access to the same files from the new domain.
SubInACL enables administrators to do the following:
SubInACL enables administrators to do the following:
- Display security information associated with files, registry keys, or services. This information includes owner, group, permission access control list (ACL), discretionary ACL (DACL), and system ACL (SACL).
- Change the owner of an object.
- Replace the security information for one identifier (account, group, well-known security identifier (SID)) with that of another identifier.
- Migrate security information about objects. This is useful if you have reorganized a network's domains and need to migrate the security information for files from one domain to another.
This update addresses the following issues:
- Fixed bug where subinacl.exe failed to process command line arguments
- Fixed bug where subinacl.exe failed to function correctly with cluster file shares
First backup the registry
The issue you are experiencing is caused by a permission related problem with one
of the registry keys on your computer. Please follow the steps listed below to
install the subinacl tool on your computer so we can modify the registry to provide
the appropriate permissions:
Step 1: Download and install the subinacl tool.
1. Click the link below to download the Subinacl tool:
http://www.microsoft.com/downloads/details.aspx?FamilyID=e8ba3e56-d8fe-4a91-93cf-ed6
985e3927b&DisplayLang=en
2. Once you have reached the site, please click on the Download button.
3. Select the option to Install the software (usually done by clicking on the Run
button).
4. In the setup wizard, click Next.
5. click on the "I accept" portion of the license and click on Next.
6. Click on the Install Now button and then click on Finish.
7. Close your web browser.
Step 2: Creating the Batch File
1. Click Start, Run and type notepad. You should see a blank page in the notepad
application.
2. Copy the lines listed between the dotted lines below and paste them into notepad
(Note: Do not select the dotted lines, only the lines listed between them):
------------------------
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=administrators=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=administrators=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=administrators=f
subinacl /subdirectories %SystemDrive% /grant=administrators=f
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=system=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=system=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=system=f
subinacl /subdirectories %SystemDrive% /grant=system=f
subinacl /subkeyreg HKEY_LOCAL_MACHINE /grant=user_name=f
subinacl /subkeyreg HKEY_CURRENT_USER /grant=user_name=f
subinacl /subkeyreg HKEY_CLASSES_ROOT /grant=user_name=f
subinacl /subdirectories %SystemDrive% /grant=user_name=f
exit
------------------------
3. In the last five lines which contain "user_name", replace these "user_name"
entries with your windows user account name.
Note: If you are not sure about the name of your user account you can verify the
name by entering your control panel, double clicking on User Accounts and looking
at the list of User Account names available on the system (at this point there will
likely only be two - your currently used User Account and the Guest account). Once
you have verified the user account name you can use it instead of the "user_name"
entry above.
4. Once all modifications have been done, click File and Save As.
5. In the "Save As" window, go to c:\program files\windows resource kits\tools 6.
In the "File Name" field, type sub.bat.
7. In the "Save as Type" field, select "All Files".
8. Click Save and close Notepad.
Step 3: Running the Batch file
1. Click Start and then Run.
2. Type cmd and click OK.
3. In the Command Prompt window type the following lines (pressing Enter after each
line):
cd program files
cd windows resource kits
cd tools
sub
Note: Once the sub command is entered it will execute the batch file. The batch
file may take between 20 to 30 minutes to complete. During this time please do not
close the command prompt window as this will interrupt the process. Once the batch
file is done running on the system the window will close on its own.
4. When the command window has disappeared please restart the computer.
Windows update error code 80070490
Registry hives like
\SAM,
\Security,
\Software,
\System,
\Default
are stored in two locations in windows once its installed for the first time in following paths...
c:\windows\system32\config
c:\windows\restore
Clearing Upper-Lower Filter in registry
For CD Drive...
HKEY_LOCAL_MACHINE-> System-> CurrentControlSet -> Control -> Class -> {4D36E965-E325-11CE-BFC1-08002BE10318}
Floppy Drive...
HKEY_LOCAL_MACHINE-> System-> CurrentControlSet -> Control -> Class -> {4D36E969-E325-11CE-BFC1-08002BE10318}
IDE ATA/ATAPI controllers
HKEY_LOCAL_MACHINE-> System-> CurrentControlSet -> Control -> Class -> {4D36E96A-E325-11CE-BFC1-08002BE10318}
Task Manager has been disabled by your administrator
HKEY_CURRENT_USER \ Software \ Microsoft \ Windows \ CurrentVersion \ Policies\ System
Start -> Run and Paste this Registry Root
REG add HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System /v DisableTaskMgr /t REG_DWORD /d 0 /f
If Regedit is Disable too then use GPEDIT.MSC Using Group Policy Editor - for Windows XP Professional
User Configuration / Administrative Templates / System / Ctrl+Alt+Delete Options / Remove Task Manager
shut down without logon in WinXP
CAUTION: Use Registry Editor at your own risk. Any change using Registry Editor may cause severe and irreparable damage and may require you to reinstall your operating system. Internet Security Systems cannot guarantee that problems caused by the use of Registry Editor can be solved.
- Open Registry Editor. (From the Windows NT Start menu, select Run, type regedt32, and click OK.)
- Go to the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon registry key.
- Change the value of the ShutdownWithoutLogon value to 0.
- Restart your system for this change to take effect.
For a Windows 2000 domain:
- Start Microsoft Management Console (MMC).
- Add Group Policy Snap-in.
- Browse Group Policy Objects.
- Select the Domain Policy of interest.
- Traverse the following path:
Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options, and Allow system to be shut down without having to log on. - Set the Allow system to be shut down without having to log on option to the desired setting, according to your administration policy.
For a stand-alone Windows 2000 computer:
- On the computer of interest, start gpedit.msc. The focus is local computer by default.
- Traverse the following path:
Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Option, and Allow system to be shut down without having to log on. - Set the Allow system to be shut down without having to log on option to the desired setting according to your administration policy.
How to Download from Command Prompt
c:\FTP FTP.mozilla.org
FTP> User name is anonymous
FTP> Password: (any email address)
FTP> CD PUB
FTP> CD FireFox
FTP> CD Releases
FTP> CD (Latest Firefox available)
FTP> CD win32
FTP> CD en-US
FTP> GET "Firefox Setup (latest version).exe"
MSINFO32
MSINFO32 displays a comprehensive view of your hardware, system components, and software environment. This article contains an overview of the available switches that can be used with the MSINFO32 command in Windows Vista and in Windows XP.
REGEDIT & REGEDIT32
Windows NT 3.x
Regedit.exe
Regedit.exe is the registration editor for 16-bit Windows. It is used to modify the Windows registration database. The database is located in the Windows directory as Reg.dat. The database contains information about 16-bit applications, and is used by File Manager for opening and printing files. It is also used by applications that support Object Linking and Embedding (OLE). Reg.dat is used and maintained by Windows on Windows (WOW) and 16-bit Windows applications. The WOW layer resides on top of theVirtual DOS Machine (VDM).Regedit.exe is a 16-bit application that is included in Windows NT for compatibility with previous 16-bit applications. Regedit provides a method for examining Reg.dat under Windows NT. You can migrate the Reg.dat database file to the Windows NT registry during the first logon to aninitial installation of Windows NT.
Regedt32.exe
Regedt32.exe is the configuration editor for Windows NT. It is used to modify the Windows NT configuration database, or the Windows NT registry. This editor allows you to view or modify the Windows NT registry.The editor provides views of windows that represent sections of the registry, named hives. Each window displays two sections. On the left side, there are folders that represent registry keys. On the right side, there are the values associated with the selected registry key. Regedt32 is a powerful tool. You must use extreme caution when you use it to change registry values. Missing or incorrect values in the registry can make the Windows NT installation unusable.Windows NT 4.0 and Windows 2000
Regedit.exe
Regedit.exe is included with Windows NT 4.0 and Windows 2000 primarily for its search capability. You can use Regedit.exe to make changes in the Windows NT 4.0 and Windows 2000 registry, but you cannot use it to view or edit all functions or data types on Windows NT 4.0 and Windows 2000.The following limitations exist in the Regedit.exe version that is included with Windows NT 4.0 and Windows 2000:
- You cannot set the security for registry keys.
- You cannot view, edit, or search the value data types REG_EXPAND_SZ and REG_MULTI_SZ. If you try to view a REG_EXPAND_SZ value, Regedit.exe displays it as a binary data type. If you try to edit either of these data types, Regedit.exe saves it as REG_SZ, and the data type no longer performs its intended function.
- You cannot save or restore keys as hive files.
Regedt32.exe
Regedt32.exe is the configuration editor for Windows NT 4.0 and Windows 2000. Regedt32.exe is used tomodify the Windows NT configuration database, or the Windows NTregistry. This editor allows you to view or modify the Windows NT registry.The editor provides views of windows that represent sections of theregistry, named hives. Each window displays two sections. On the leftside, there are folders that represent registry keys. On the right side,there are the values associated with the selected registry key. Regedt32 isa powerful tool, and you must use it with extreme caution when you changeregistry values. Missing or incorrect values in the registry can make theWindows installation unusable.Note Unlike Regedit.exe, Regedt32.exe does not support importing and exporting registration entries (.reg) files.
Windows XP and Windows Server 2003
Regedit.exe
Regedit.exe is the configuration editor for Windows XP and Windows Server 2003. Regedit.exe is used tomodify the Windows NT configuration database, or the Windows NT registry. This editor allows you to view or modify the Windows NT registry. It supports setting security on registry keys, viewing and editing REG_EXPAND_SZ and REG_MULTI_SZ, and saving and restoring hive files. On the left side, there are folders that represent registry keys. On the right side, there are the values associated with the selected registry key. Regedit is a powerful tool. You must use extreme caution when you use it to change registry values. Missing or incorrect values in the registry can make theWindows installation unusable.Regedt32.exe
In Windows XP and Windows Server 2003, Regedt32.exe is a small program that just runs Regedit.exe.
Newer | Latest | Older
