Archive for May, 2010

ENTER Webcam Drivers

Posted: May 11, 2010 in Drivers, System Information

Steps to Install the Drivers:

My Computer> (Right Click)> Manage> Device Manager> Select the Webcam With the Warning Icon> Double Click the Icon of the Webcam

Then Click on Re-Install Drivers.

Select This time only.

And select the Path where you have Extracted the Files and proceed with Installation.

The Drivers Will be installed into your computer.

Click Here to DOWNLOAD


Windows Server 2003 uses a service to control the spooling of print jobs. If this service isn’t running, print jobs can’t be spooled. You can check the status of the Print Spooler using the Services utility. Follow these steps to check and restart the Print Spooler service:

  1. In Administrative Tools, click or double-click Computer Management.
  2. Right-click the Computer Management entry in the console tree and select Connect To Another Computer on the shortcut menu. You can now choose the system whose services you want to manage.
  3. Expand the Services And Applications node by clicking the plus sign (+) next to it, and then choose Services.
  4. Select the Print Spooler service. The Status should be Started. If it isn’t, right-click Print Spooler and then select Start. The Startup Type should be Automatic. If it isn’t, double-click Print Spooler and then set Startup Type to Automatic.
  5. If this doesn’t resolve the problem, you might want to check other related services, including
    • TCP/IP Print Server (if installed)
    • Print Server for Macintosh (if installed)
    • Print Server for UNIX (if installed)


    Spoolers can become corrupted. Symptoms include a frozen printer or one that doesn’t send jobs to the print device. Sometimes the print device might print pages of garbled data. In most of these cases stopping and starting the Print Spooler service resolves the problem. Other spooling problems might be related to permissions.


An understanding of how printing works can go a long way when you’re trying to troubleshoot printer problems. When you print documents, many processes, drivers, and devices work together to print the documents. If you use a printer connected to a printer server, the key operations are as follows:

  • Printer driver

    When you print a document in an application, your computer loads a printer driver. If the print device is attached to your computer physically, the printer driver is loaded from a local disk drive. If the print device is located on a remote computer, the printer driver might be downloaded from the remote computer. The availability of printer drivers on the remote computer is configurable by operating system and chip architecture. If the computer can’t obtain the latest printer driver, it’s probably because an administrator hasn’t enabled the driver for the computer’s operating system. For more information, see the section of this chapter entitled “Managing Printer Drivers.”

  • Local print spool and print processor

    The application you’re printing from uses the printer driver to translate the document into a file format understandable to the selected print device. Then your computer passes the document off to the local print spooler. The local spooler in turn passes the document to a print processor, which creates the raw print data necessary for printing on the print device.

  • Print router and print spooler on the print server

    The raw data is passed back to the local print spooler. If you’re printing to a remote printer, the raw data is then routed to the print spooler on the print server. On Windows Server 2003 systems, the printer router, Winspool.exe, handles the tasks of locating the remote printer, routing print jobs, and downloading printer drivers to the local system, if necessary. If any one of these tasks fails, the print router is usually the culprit. See the sections of this chapter entitled “Solving Spooling Problems” and “Setting Printer Access Permissions” to learn possible fixes for this problem. If these procedures don’t work, you might want to replace or restore Winspool.exe.

    The main reason for downloading printer drivers to clients is to provide a single location for installing driver updates. This way, instead of having to install a new driver on all the client systems, you install the driver on the print server and allow clients to download the new driver. For more information on working with printer drivers, see the section of this chapter entitled “Managing Printer Drivers.”

  • Printer (print queue)

    The document goes from the print spooler into the printer stack—which in some operating systems is called the print queue—for the selected print device. Once in the queue, the document is referred to as a print job—a task for the print spooler to handle. The length of time the document waits in the printer stack is based on its priority and position within the printer stack. For more information, see the section of this chapter entitled “Scheduling and Prioritizing Print Jobs.”

  • Print monitor

    When the document reaches the top of the printer stack, the print monitor sends the document to the print device, where it’s actually printed. If the printer is configured to notify users that the document has been printed, you see a message confirming this.

    The specific print monitor used by Windows Server 2003 depends on the print device configuration and type. The default monitor is Localmon.dll. You might also see monitors from the print device manufacturer, such as Hpmon.dll, which is used with most Hewlett-Packard print devices. This DLL (dynamic-link library) is required to print to the print device. If it’s corrupted or missing, you might need to reinstall it.

  • Print device

    The print device is the physical device that prints documents on paper. Common print device problems and display errors include

    • Insert Paper Into Tray X
    • Low Toner
    • Out Of Paper
    • Out Of Toner; Out Of Ink
    • Paper Jam
    • Printer Offline

Group Policy can affect your ability to install and manage printers. If you’re having problems and believe they’re related to Group Policy, the key policies you’ll want to examine are those in

  • Computer Configuration\Administrative Templates\Printers
  • User Configuration\Administrative Templates\Control Panel\Printers
  • User Configuration\Administrative Templates\Start Menu And Taskbar

In most network environments, it’s a good idea to document the reasons for shutting down or restarting computers. With unplanned shutdowns, you can document the shutdown in the computer’s system log by expanding the syntax to include the following parameters:

/e /c "UnplannedReason" /d MajorCode:MinorCode

where /C “UnplannedReason” sets the detailed reason (which can be up to 127 characters in length) for the shutdown or restart, and /D MajorCode:MinorCode sets the reason code for the shutdown. Reason codes are arbitrary, with valid major codes ranging from 0 to 255 and valid minor reason codes ranging from 0 to 65,535. Consider the following example:

shutdown /r /e /m \\Mailer1 /c "System Reset" /d 5:15

In this example, you are restarting MAILER1 and documenting the reason for the unplanned restart as a “System Reset” using the reason code 5:15.

With planned shutdowns and restarts, prefix the reason codes with p: to indicate a planned shutdown, as shown here:

/e /c "PlannedReason" /d p:MajorCode:MinorCode

For instance, consider the following code:

shutdown /r /e /m \\Mailer1 /c "Planned Application Upgrade" /d p:4:2

With remote systems, you need to specify the UNC name or IP address of the system you want to shut down or restart using the /M parameter. Thus, the basic syntax for shutdown, restart, and cancel delayed shutdown become

Shutdown remote system:

shutdown /s /t ShutdownDelay /l /f /m \\System

Restart remote system:

shutdown /r /t ShutdownDelay /l /f /m \\System

Cancel delayed shutdown of remote computer:

shutdown /a /m \\System

In this example, MAILER1 is restarted after a 30-second delay:

shutdown /r /t 30 /m \\Mailer1

In this example, the system with the IP address is restarted immediately and running applications are forced to stop running:

shutdown /r /f /m \\

On a local system, you can manage shutdown and restart using the following commands:

Shutdown local system:

shutdown /s /t ShutdownDelay /l /f

Restart local system:

shutdown /r /t ShutdownDelay /l /f

Cancel delayed shutdown of local computer:

shutdown /a

where /T ShutdownDelay is used to set the optional number of seconds to wait before shutdown or restart, /L optionally logs off the current user immediately, and /F optionally forces running applications to close without warning users in advance. In this example, the local system is restarted after a 60-second delay:

shutdown /r /t 60

As an administrator, you’ll often have to start, stop, or pause Windows services. The related SC commands and their syntaxes are

Start a service:

sc start ServiceName

Pause a service:

sc pause ServiceName

Resume a paused service:

sc continue ServiceName

Stop a service:

sc stop ServiceName

where ServiceName in each case is the abbreviated name of the service you want to work with, such as

sc start w3svc

As with all SC commands, you can also specify the name of the remote computer whose services you want to work with. For example, to start the w3svc on MAILER1, you would use the following command:

sc \\Mailer1 start w3svc

The state listed in the results should show START_PENDING. With stop, pause, and continue you’ll see STOP_PENDING, PAUSE_PENDING, and CONTINUE_PENDING respectively as well. If an error results, the output states FAILED and error text is provided to describe the reason for the failure in more detail. If you are trying to start a service that is already started, you’ll see the error

An instance of the service is already running.

If you are trying to stop a service that is already stopped, you’ll see the error

The service has not been started.

To delete subkeys and values from the Windows registry, use REG delete. REG delete has several different syntaxes. If you want to delete a subkey and all subkeys and entries under the subkey, use the following syntax:

reg delete KeyName

where KeyName is the name of the subkey you want to delete. Although the subkey path can include the UNC name or IP address of a remote computer, a remote source subkey can use only the HKLM or HKU root keys. Consider the following example:

reg delete \\Mailer1\HKLM\SYSTEM\CurrentControlSet\Services\DNS2

Here you delete the DNS2 subkey and all subkeys and entries under the subkey on MAILER1.

If you want to limit the scope of the deletion, specify that only a specific entry under the subkey should be deleted using the following syntax:

reg delete KeyName /v ValueName

where KeyName is the name of the subkey you want to work with and ValueName is the name of the specific entry to delete. As before, the subkey path can include the UNC name or IP address of a remote computer. However, a remote source subkey can use only the HKLM or HKU root keys. In this example, you delete the Description entry for the DNS2 subkey on MAILER2:

reg delete \\Mailer2\HKLM\SYSTEM\CurrentControlSet\Services\DNS2 /v 

Using REG copy, you can copy a registry entry to a new location on a local or remote system. The basic syntax for REG copy is

reg copy KeyName1 KeyName2

where KeyName1 is the path to the subkey you want to copy and KeyName2 is the path to the subkey destination. Although the subkey paths can include the UNC name or IP address of a remote computer, REG copy is limited in scope with regard to which root keys you can use when working with remote source or destination keys, as follows:

  • A remote source subkey can use only the HKLM or HKU root keys.
  • A remote destination subkey can use only the HKLM or HKU root keys.

In the following example, you copy the DNS subkey on the local system to the DNS subkey on MAILER2:

reg copy HKLM\SYSTEM\CurrentControlSet\Services\DNS

By adding the /S parameter, you can copy the specified subkey as well as all subkeys and key entries under the specified subkey. In this example, the DNS subkey and all related subkey and values are copied:

reg copy HKLM\SYSTEM\CurrentControlSet\Services\DNS
    \\Mailer2\HKLM\SYSTEM\CurrentControlSet\Services\DNS /s

If values exist at the destination path, REG copy will prompt you to confirm that you want to overwrite each existing value. Press Y or N as appropriate. You can also press A to overwrite all existing values without further prompting.

To add subkeys and values to the Windows registry, use REG add. The basic syntax for creating a key or value is

reg add KeyName /v ValueName /t DataType /d Data

where KeyName is the name of the key you want to examine, ValueName is the subkey or key value to create, DataType is the type of data, and Data is the actual value you are inserting. That seems like a lot of values, but it is fairly straightforward. Consider the following example:

reg add HKLM\SYSTEM\CurrentControlSet\Services\DNS /v DisplayName
/t REG_SZ /d “DNS Server”

Here, you add a key value called DisplayName to the DNS key in the registry. The key entry is a string with the “DNS Server” value. Note the double-quotation marks. The quotation marks are necessary in this example because the string contains a space.

When you set expandable string values (REG_EXPAND_SZ), you must use the caret (^) to escape the percent symbols (%) that designate the environment variable you use. Consider the following example:

reg add HKLM\SYSTEM\CurrentControlSet\Services\DNS /v ImagePath
/t REG_EXPAND_SZ /d ^%SystemRoot^%\System32\dns.exe

Here, you enter ^%SystemRoot^% so that the SystemRoot environment variable is properly entered and interpreted.

When you set non-string values, you don’t need to use quotation marks, as shown in this example:

reg add HKLM\SYSTEM\CurrentControlSet\Services\DNS /v ErrorControl
/t REG_DWORD /d 0x00000001